Hi !
Firstoff: My company is still willing to support a developer that
implements data migration into bacula.
I have a few questions considering tape handling.
Let`s say i have a Tape that gets changed every day. Three servers
backup to it (spooling of course) and i have set Maximum Volume Jobs to
3 for that pool.
Is there a way to automatically eject the tape after the last server
finished spooling his data ? Maybe with the Run After Job directive ? I
could do it by hand with the console but thats not what i want.
What happens if one backup fails and i remove the tape so that maximum
volume jobs is not fulfilled ... will it ask for the old tape on the
next backup or will it happily use the new tape that has been inserted ?
The relabel command only works on tapes already in the catalogue ... i
re-initialized my database a few times and it rejected relabeling the
old tapes. It also rejected USING the old tapes ... had to do "mt weof"
to fix that.
Do i need to set the Drive Index option in bacula-sd.conf when i don`t
have a tapechanger ? I only have 4 standalone LTO-1 drives but no changer.
Best regards
--
Daniel Holtkamp Riege Software International GmbH
System Administration Mollsfeld 10
40670 Meerbusch, Germany Phone: +49-2159-9148-41
mail: holtkamp [at] riege.com Fax: +49-2159-9148-11
--------------------------------------------------------------------
-------------------------------------------------------
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
