Adrian Moisey wrote:
> Hi
> 
> I'm busy setting up my bacula to write to tape.  The problem I've come 
> across now is that it seems to take forever to do so and it takes more 
> then 1 tape.
> 
> What happens is I've got spooling enabled.  When the backup runs it 
> spools machine A, writes machine A to tape, spools machine B, writes 
> machine B to tape.  I understand that you can't write concurrent backups 
> to tape.  How can I get my bacula to spool *everything* before it writes 
> to tape?

I don't think there's a simple directive to say "Spool every outstanding
job before you put anything to tape", or for that matter a directive to
say "While you're putting job A to tape, you might as well start
spooling job B" but you could always set up a separate disk pool, backup
your servers to the disk pool and then run a migration job to get the
data to tape.

Bacula will write concurrent backups to tape quite happily, but it's not
recommended as you'll wind up with very fragmented backups which will
require a lot of seeking which is even less efficient with tapes than it
is with disks.

-- 
James Cort

IT Manager
U4EA Technologies Ltd.

-- 
U4EA Technologies
http://www.u4eatech.com


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users