Hi,
Daniel Holtkamp wrote:
Hello !
Thanks for the quick response !
Arno Lehmann wrote:
Well, I don't know which section in the manual you refer to, but this
is a network timeout problem and that's rather long in bacula - 2
hours, I think.
Ouch, 2 hours is hard ... but i guess i can configure around this
problem with allowing concurrent backups ... (for example one process
hanging and waiting for timeout and the other is backing up fine)
Now, I don't know if you can configure this timeout - I only find SD|FD
connect timeout directives.
But, running multiple concurrent jobs would be one usefol workaround, I
think.
Consider to use spooling in this case.
...
I'm not sure I can follow your thought
Indeed you couldn`t ;-)
:-)
I noticed an error in my example tho, the retention time for the example
should be two weeks.
The question is about the volumes and their retention time.
On the second sunday bacula would try to make a backup, check for
available volumes in the full-pool and see two volumes (remember ? 2
volumes maximum), both in the used state (one 6 days old and ok, one 7
days old and damaged from the client-crash during the backup).
At least i got the impression that a failed backup leads to a closed,
used volume ... does bacula notice that this volume is incomplete and
flag it for recycling immediately ignoring the retention time ? (as the
data in the file is incomplete anyway).
Ah, ok, now I understand.
I don't know if a failed job will mark a tape as Used. But when a pool
holds no available tapes when bacula needs one you get a message that
you have to prepare a new volume. And no, I don't know what bacula
reports in case it would need a new volume in a pool where you limit the
number of volumes. If nobody else knows, you'll have to try it - and it
would be nice if you reported your results.
Limiting the number of volumes is useful only when you let bacula create
volumes itself, I think, because if you prepare the volumes manually you
already control the number of volumes.
So, my conclusion: With tapes, I wouldn't limit the number of volumes
inside bacula. Rather, in a case you described you could simply purge
the volume that's not actually used.
After all, we're talking about error situations here, and these
shouldn't occur regularly. :-)
With disk based volumes, that's a little different, because using
automatic volume creation is quite useful then. (Of course I could
imagine scenarios with tapes, too, but that's something different.)
Arno
--
IT-Service Lehmann [EMAIL PROTECTED]
Arno Lehmann http://www.its-lehmann.de
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
