One more thing to consider is the Run Before Job directive. I had the
problem that a downed client meant Bacula would hang for something like 40
minutes before giving up. I solved that by pinging the client three times
with Run Before Job -- if it failed the job rescheduled, if not it ran.
~Kyle
On 7/24/07, Charles Sprickman <[EMAIL PROTECTED]> wrote:
On Tue, 24 Jul 2007, Brian Debelius wrote:
> ohhh, ahhh, is this new?
>
> brian-
>
> Junior Cunha wrote:
>> Steve Poulsen wrote:
>>
>>> I am backing up several machines, but a couple of them are only on
>>> about 10% of the day. Is there any kind of option on the daily
>>> backups to have it retry every hour so that when the machine comes
>>> back up it can get backed up?
>>>
>> Hi Steve,
>>
>> You can use this options in your Job definition:
>>
>> Reschedule On Error, Reschedule Interval and Reschedule Times.
>>
>> Below, a full example:
>>
>> Job {
>> Name = dns1
>> Type = Backup
>> Client = dns1
>> FileSet = Full
>> Messages = messages
>> Storage = StorageServer
>> Maximum Concurrent Jobs = 5
>> Pool = Default
>> Full Backup Pool = Full
>> Incremental Backup Pool = Incremental
>> Schedule = Daily
>> Priority = 1
>> Prune Jobs = yes
>> Write Bootstrap = /var/db/bacula/dns1.bsr
>> Reschedule On Error = yes
>> Reschedule Interval = 2 hour
>> Reschedule Times = 6
>> }
This is excellent! I was just going to post a question about how to deal
with network problems during the backup window, and I think this is my
answer...
I have about 20-some remote machines. What kind of havoc might I cause by
using those directives with smaller timeframes on all those machines?
Thanks,
Charles
>> []s
>>
>> Junior Cunha
>>
>>
>>
-------------------------------------------------------------------------
>> This SF.net email is sponsored by: Splunk Inc.
>> Still grepping through log files to find problems? Stop.
>> Now Search log events and configuration files using AJAX and a browser.
>> Download your FREE copy of Splunk now >> http://get.splunk.com/
>> _______________________________________________
>> Bacula-users mailing list
>> Bacula-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bacula-users
>>
>
>
>
-------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
