With Bacula, a great piece of backup software [disclosure: I wrote the PostgreSQL module for Bacula], you can copy a Job after it has run. This is often used to backup first to disk, and then Copy that Job to tape. That is exactly what I’ve been doing recently. NOTE: You can also migrate a Job, which is very similar to a Job Copy. With a Job Copy, the original Job remains and […]
*run A job name must be specified. The defined Job resources are: 1: BackupCatalog 2: RestoreFiles 3: MigrateDiskToTape 4: CopyMegaFileToTape 5: laptop 6: laptop-vpn 7: laptop-wifi-5.3 8: laptop-verify 9: laptop-websites 10: laptop-xp 11: wocker 12: bast basic 13: bast home 14: dbclone basic 15: dbclone home 16: polo basic 17: polo 18: kraken basic 19: kraken 20: nyi maildir 21: nyi maildir tarball 22: nyi basic 23: nyi 24: supernews basic 25: supernews
Why not use the tape that’s there? Read More »
Over the past few months, I’ve been getting ready to copy Bacula backups from disk to tape, via a Copy Job. Tonight was my first attempt. I failed. And I think I know why. Concurrency. The output so far: *run job=CopyMegaFileToTape Using Catalog “MyCatalog” Run Copy job JobName: CopyMegaFileToTape Bootstrap: *None* Client: wocker-fd FileSet: wocker files Pool: MegaFile-wocker (From Job resource) Read Storage: MegaFile-wocker (From Pool resource) Write Storage: DigitalTapeLibrary (From Storage from
Running a Bacula Copy Job Read More »