On 1/26/2016 5:08 PM, Michael Munger wrote:
Wanderlei:
Thanks for the reply!
I’ll upgrade. I was just using the Debian repo versions because that
was what was there.
I already had to downgrade the Windows client because it wouldn’t
connect to 5.6.2.
So, now, I’ll re-upgrade everything
On 01/22/16 12:56, Martin Simmons wrote:
> I don't see how it could use an IPv6 address if --disable-ipv6 is specified.
> Did you recompile and reinstall the bacula-client port or just bacula-server?
> The IPv6 support is in bacula-client, which installs libbac.so.
Doh! That's the problem!
I didn
Not sure where to report this, so, please someone reply so I can submit the
corrected files.
I downloaded the latest version of Bacula, and compiled from source. After
running the various scripts to create the MySQL databases, I got a few errors,
but ignored them at first.
Then, when trying to
Just as a follow up, moving to 7.4.x solved the problem. The secret is FD
Storage Address.
For future searchers / Googlers:
The FD Storage Address is defined for a given client, and that client will
then use it to send all the storage requests to.
Thus:
If FD Storage Address is defined
Configure cannot find libpq-fe.h.
On your system, execute the following (as root):
1. updatedb
2. locate libpq-fe.h
This should show you where the devel files are installed on your system. Once
you have that, you can make a symlink that points a “standard” location to
where your files actually
Then you need to download the source for postgres 9.4 and compile from source,
making sure that it installs the headers in the appropriate place.
Michael Munger, dCAP, MCPS, MCNPS, MBSS
High Powered Help, Inc.
Microsoft Certified Professional
Microsoft Certified Small Business Specialist
Digium
I had a lot of problems getting my setup to work over NAT too. If you
want email me directly and I can provide my full configs/help out. I
think what ended up fixing it for me was updating all of the Bacula
components to 7.2.0. I had a real struggle trying to get it to work
with 5.x too
TLDR; = what can I safely exclude from a bacula backup of a Linux server and
still be able to fully recover (bare metal) from a disaster?
Details:
I am looking for a best practice here, and I am working from two sources:
1.
http://www.bacula.org/5.0.x-manuals/en/main/main/Disaster_Recovery_Usin
This is REALLY helpful.
I have it working on some public services that are physically attached to our
network, so I haven't enabled SSL (because it never leaves the office), but my
next step is to do it with some remote datacenter boxes, and the SSL configs
you have just sent are invaluable ti
On 01/27/2016 03:42 PM, Michael Munger wrote:
> TLDR; = what can I safely exclude from a bacula backup of a Linux
server and still be able to fully recover (bare metal) from a disaster?
Not an answer to your question, but we are
- using raid-1s for system disks,
- using SSDs for system disks,
- dd
Having setup and just tested, I ran into the "will not descend into different
file systems" issue as mentioned in this post:
http://bacula.10910.n7.nabble.com/Will-not-descend-from-into-dev-td57408.html,
and it gives a very good reason for explicitly defining what to include.
So, I have amended
Your answer is appreciated. And, I was trying to keep my question limited to
what I wanted to know, but you bring up a good point: bacula is only part of
the strategy. These systems are cloned with Clonezilla, the image of which sits
on the shelf as a base. We use RAID 5/6/10 depending on how cr
> what can I safely exclude from a bacula backup of a Linux server and still
be able to fully recover (bare metal) from a disaster?
I would think with bare metal recovery you couldn't afford to exclude
anything. As for myself, I tend to replace the failed part and install from
scratch, then restor
> what can I safely exclude from a bacula backup of a Linux server and
> still be able to fully recover (bare metal) from a disaster?
Oh, and don't forget mysql.
--
Site24x7 APM Insight: Get Deep Visibility into App
Hello Michael: bacula director client stock fileset exlude is a good starting
point if you want to restore a full linux box (/tmp, /proc, /.journal etc.).
Already did full restores this way.
Regards,
===
Heitor Medrado de Far
Good reminder. I am using a ClientBeforerunJob script to dump all the
databases to .sql files before backing up.
On 01/27/2016 06:57 PM, compdoc wrote:
>> what can I safely exclude from a bacula backup of a Linux server and
>> still be able to fully recover (bare metal) from a disaster?
> Oh, an
16 matches
Mail list logo