Christian Reiss wrote:
> Problem 1:
> *NO* client is online 24/7 or even at foreseeable times. Thus, my
> question: I made a small ping-script that pings the host in question.
> Because it is "ping", it exits with !=0 on unreachable, thus, the
> backup will never commence. I also added "Rerun Failed Levels" and
> "Reschedule On Error" as well as "Reschedule Interval = 15m". My
> understanding is this: On a backup job, the server pings the client.
> If the client is down, the ping fails and so does the job, which,
> because it failed (Reschedule On Error) it is to be rescheduled in
> 15 minutes from now, for an unlimited retries until the host comes
> up again. Thus, a (not-so-elegant but) working solution for my
> problem?
You can also approach this problem by providing a script by which
clients can initiate their own backups using a restricted Console.
I think Kern covered the other questions.
--
Phil Stracchino [EMAIL PROTECTED]
Renaissance Man, Unix generalist, Perl hacker
Mobile: 603-216-7037 Landline: 603-886-3518
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
