Hi.
Brice Figureau wrote:
Hi,
I'm happily running Bacula 1.36.1 (switching to 1.36.2 asap), but I have the following problem. My bacula director backups a few windows user workstations every evening. Some of the employees of the company forget to leave their workstation up and running before leaving in the evening, and thus shutdown them.
Why is the director spending those large amount of time to retry this host ?
Basically, there arereasons for it. You will find some answers in the list archive, and you can change the directors configuration.
From the manual for 1.36.0:
FD Connect Timeout = <time>
where time is the time that the Director should continue attempting to contact the File daemon to start a job, and after which the Director will cancel the job. The default is 30 minutes.
Why is he waiting that amount of time between each access ?
And finally how can I control: 1) the amount of time between unsuccessfull attempts
Reschedule On Error = <yes/no>
If this directive is enabled, and the job terminates in error, the job will be rescheduled as determined by the Reschedule Interval and Reschedule Times directives. If you cancel the job, it will not be rescheduled. The default is no (i.e. the job will not be rescheduled).
This specification can be useful for portables, laptops, or other machines that are not always connected to the network or switched on.
Reschedule Interval = <time-specification>
If you have specified Reschedule On Error = yes and the job terminates in error, it will be rescheduled after the interval of time specified by time-specification. See the time specification formats in the Configure chapter for details of time specifications. If no interval is specified, the job will not be rescheduled on error.
Reschedule Times = <count>
This directive specifies the maximum number of times to reschedule the job. If it is set to zero (the default) the job will be rescheduled an indefinite number of times.
Priority = <number>
2) the number of unsuccessfull attempts before giving a fatal error
Also helpful in a scenario like yours:
Rerun Failed Levels = <yes/no>
If this directive is set to yes (default no), and Bacula detects that a previous job at a higher level (i.e. Full or Differential) has failed, the current job level will be upgraded to the higher level. This is particularly useful for Laptops where they may often be unreachable, and if a prior Full save has failed, you wish the very next backup to be a Full save rather than whatever level it is started as.
Basically, many of the factors influencing the timeouts can be controlled. In the manual for 1.36.2, you will probably find other options or more detailed explanatons.
To completely disable timeouts, you can also use a Run Before Script which tries to ping the clients and immediately aborts with an exit code >0 and probably some useful output. That's what I use.
Arno
30-Mar 22:12 arsenic-dir: Start Backup JobId 118, Job=emmanuelle.2005-03-30_21.30.04 30-Mar 22:18 arsenic-dir: emmanuelle.2005-03-30_21.30.04 Warning: bnet.c:767 Could not connect to File daemon on 192.168.0.9:9102. ERR=Connection timed out Retrying ... 31-Mar 00:01 arsenic-dir: emmanuelle.2005-03-30_21.30.04 Warning: bnet.c:767 Could not connect to File daemon on 192.168.0.9:9102. ERR=Connection timed out Retrying ... 31-Mar 01:44 arsenic-dir: emmanuelle.2005-03-30_21.30.04 Warning: bnet.c:767 Could not connect to File daemon on 192.168.0.9:9102. ERR=Connection timed out Retrying ... 31-Mar 03:27 arsenic-dir: emmanuelle.2005-03-30_21.30.04 Warning: bnet.c:767 Could not connect to File daemon on 192.168.0.9:9102. ERR=Connection timed out Retrying ... 31-Mar 05:10 arsenic-dir: emmanuelle.2005-03-30_21.30.04 Warning: bnet.c:767 Could not connect to File daemon on 192.168.0.9:9102. ERR=Connection timed out Retrying ... 31-Mar 06:52 arsenic-dir: emmanuelle.2005-03-30_21.30.04 Warning: bnet.c:767 Could not connect to File daemon on 192.168.0.9:9102. ERR=Connection timed out Retrying ... 31-Mar 08:09 arsenic-dir: emmanuelle.2005-03-30_21.30.04 Fatal error: bnet.c:773 Unable to connect to File daemon on 192.168.0.9:9102. ERR=Connection timed out 31-Mar 08:09 arsenic-dir: emmanuelle.2005-03-30_21.30.04 Error: Bacula 1.36.1 (26Nov04): 31-Mar-2005 08:09:17 [snip]
Thanks,
-- IT-Service Lehmann [EMAIL PROTECTED] Arno Lehmann http://www.its-lehmann.de
------------------------------------------------------- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/Info/Sentarus/hamr30 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
