|
Re: [Bacula-users] Inconsistent backups of windows clients
2014-10-22 16:00:06
|
On 14-10-22 01:17 AM, Florian wrote:
Am 21.10.2014 um 01:31 schrieb Jean Sébastien HEDERER ASPerience:
Hi,
And if you make backups at 4 differents hours, do you have the
problem?
The thing is that there could be multiple additional clients in
the future and I'd like to keep additional configuration per
client at a minimum.
Florian,
Can you put a sleep between the Powerwake script and the
backup start, just for test purposes?
Mabe a ClientRunBeforeJob only with sleep. I suspect
maybe the lag to the machine (and bacula-fd) start is
failing the jobs.
Regards,
====================================================================
Heitor Medrado de Faria
=====================================================================
The backups ran with a 30 seconds sleep command after powerwake
today. All jobs finished successfully.
That's a start, but I will have to observe this a bit more. Like I
said: It doesn't always happen that a job fails.
De:
"Florian" <florian.splett AT web DOT de>
Para: bacula-users AT lists.sourceforge DOT net
Enviadas: Segunda-feira, 20 de outubro de 2014
3:57:34
Assunto: [Bacula-users] Inconsistent backups of
windows clients
Hello everyone.
So, I am backing up 4 windows clients at the moment, using
the 5.2.10 windows FD.
over the last two weeks I noticed that jobs relatively often
end with an error, meaning up to 2 clients per day.
It's not even the same clients. Some days, everything works,
then client 1 ends with an error, the next day maybe client
4 does, while client 1 runs completely fine. I cannot see
any pattern in the occurence of these errors. I just know it
is always the same problem:
ubuntu-dir JobId XXX: Fatal error: bsock.c:118 Unable to connect to Client: <Client> on XXX.XXX.XXX.XXX:9102. ERR=No route to target machine
ubuntu-dir JobId XXX: Fatal error: FD did not reaturn a Job status.
This is very bizarre, because the second line of the message above
does not exist in any Bacula that I am aware of.
Some more information that might help:
The 4 backup jobs for the clients are started at the same
time.
Each job starts by activating the machine using powerwake.
Each client has its personal backup device in the storage
daemon's config.
I hope anybody can help me out here, because the
backup-system is just too unreliable like this...
From the above error messages, I would say that your wakeup on WAN
is not really working or you are not giving the machine enough time
to come up and Bacula is timing it out. Trying to backup sleeping
Clients is probably an unreliable way of running backups -- or you
must find some way to fully wake up the machine before having Bacula
try to contact it. Perhaps simply upping the FD Connect Timeout
would solve your problem.
Best regards,
Kern
------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
------------------------------------------------------------------------------
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
|
|
