Re: [Bacula-users] migration jobs (was: Re: Job spooling)

[Kern S. <ke...@si...>]

On Thu, 2004-01-29 at 21:46, Jesse Guardiani wrote:
> Kern Sibbald wrote:
> 
> > On Sun, 2004-01-18 at 14:02, Alan Brown wrote:
> >> On Sun, 18 Jan 2004, Luca Berra wrote:
> >> 
> >> > I believe the two main reasons for enabling disk spooling are:
> >> > fast devices that suffer from starting/stopping the motor (i.e.
> >> > Ultriums) so i'd like to be able to enable it by sd device.
> >> 
> >> > Slow clients (either because they have a slow network or a slow disk),
> >> > so also setting it by Client or by job.
> >> 
> >> Add: Multiple small clients dumping to a large device (ultrium/SAIT)
> >> 
> >> By dropping incrementals to disk, then flushing to tape, one gains the
> >> ability to decrease the backup window, _plus_ if the disk imiages are
> >> kept before aging out, when someone manages to delete a file they've been
> >> working on, it can be recovered quickly, rather than waiting for tape
> >> runs or pulling items from the safe.
> > 
> > Just so that you are not disappointed, the above features are not part
> > of my job spooling project. Job spooling will not record the disk
> > location in the catalog while the spooling is going on as it is assumed
> > to be very temporary.
> > 
> > To get what you want, you will need to write the backups to disk Volume
> > then run a Migration job (to be implemented) to move the backups from
> > disk to tape or to run a Copy job that will duplicate the disk
> > information on tape.
> 
> Will migration jobs work for disk->tape?

Yes.

> 
> tape->tape?

Yes, if you have two tape drives.

> 
> How about tape->disk?

Yes.

The Bacula disk and tape data formats are bit for bit identical -- there
are just media differences at a low level such as blocking factors and
EOF marks ....

Regards, Kern