Hello everyone, I am new to the world of Bacula and I have succeeded in setting
up my server and some agents on some local windows machines to play around with
it. Now I got it to the point where it is successfully completing backups and
saving them to the Bacula server. I can view all the files
We are using Bacula 5.2.5 to backup a server with a huge amount of files.
After a full backup was done (It took 3+ days), the incremental took 10+ hours.
Notice the lines in the log:
27-Jan 23:10 server-xxx-fd JobId 1157: /run is a different filesystem.
Will not descend from / into it.
28-J
Dear Bacula Users,
Does anyone know if Bacula (coommunity / enterprise) supports this OCFS2
FileSystem?
Regards,
Heitor Medrado de Faria - LPIC-III | ITIL-F
Need Bacula training?
https://www.udemy.com/bacula-backup-software/?coup
On 01/28/2015 10:46 AM, dweimer wrote:
> host file is default, only has the default local host entries.
> root@bacula:/ # cat /etc/hosts | grep -v "^#"
> ::1 localhost localhost.my.domain
> 127.0.0.1 localhost localhost.my.domain
>
> It isn't just this one hostna
On 01/28/2015 9:09 am, Cejka Rudolf wrote:
> dweimer wrote (2015/01/27):
>> ...
>
> Interesting. What did you do right before "suddenly" actually?
> Nothing, or something and somewhere? :o)
>
>> > It had me scratching my head for a while, because it was still half
>> > working. My nagios and bacu
dweimer wrote (2015/01/27):
> ...
Interesting. What did you do right before "suddenly" actually?
Nothing, or something and somewhere? :o)
> > It had me scratching my head for a while, because it was still half
> > working. My nagios and bacula daemons couldn't find any *.local names
> > anymore,
I have been having crashes with the latest version of Bacula director (v7.0.5-1
x86_64 from slaanesh repo on RHEL6) off and on and just discovered what was the
sequence of events that is causing the problem. If there is an incremental
job currently running and the same job is started as FULL o
On 01/28/2015 1:28 am, Luc Van der Veken wrote:
> On 27 January 2015 21:18, dweimer wrote:
>
>> it appears to already have determined the IP prior to it hanging.
>>
>> Putting it back to IP instantly connects.
>
> Yes, but I see it's connecting to another IP address (...5.4 instead of
> ...1.4)
