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 »
While creating the FreeBSD package for 5.0.0, I noticed a few new things to be aware of. With 5.0.0 comes a new backup catalog script. It parses the bacula-dir.conf file and extracts what it needs from that. This means you only need to specify the database connection information in one place and it is not passed to a script via the command line. If you see this error while running that script: 25-Jan
Bacula – errors with 5.0.0 backup catalog Read More »
Bacula uses flat text files for configuration. From time to time, people, usually new to the project, ask: why isn’t the configuration in the database? Bacula uses the database to store information about what files were backed up, from what client, and when. This information is useful when you need to know how if you have a copy of a file from last Tuesday before you wrote crap into it but after you
Bacula Configuration Read More »
Bacula is a backup system with three different retention periods: Volume Job File I set all three to the same value. It is important to note that these values affect only the Catalog. It determines how long a given record is held in the database. For example, if you set File Retention to be 45 days, it means that there are no records in the database for any files backed up in any
Bacula Retention Periods Read More »
Both BSDCan and PGCon use Pentabarf for accepting and reviewing proposals for talks. An issue raised in 2009 highlighted the ability to see the speaker name when review the list of submissions. It is a bit of very useful information. This year, I’ve found out that we can see that vital data. Provided the speaker role has been set to confirmed. I think Pentabarf design assumes that you have created a talk, and
Pentabarf – seeing the speakers Read More »
NOTE: this problem may not be a problem. After rebooting the system while having the tape library powered up, the problem went away. This may or may not be coincident. Note to self: mtx-changer needs more customization than I thought. Today showed great progress in completing the integration of my tape library into my Bacula system. I have been writing the testing and configuration of supporting tools. I had moved onto a new
mtx-changer script catches me Read More »
Backups come in three flavors: Full – backup everything Differential – backup everything since the last Full backup Incremental – backup everything since the last backup (Full or Incremental) I took the above from What Is Bacula? Most systems use mtime to determine if a file has changed. Thus, any file that has been modified since the last backup will be picked up in the next incremental or differential backup. Full backups are
I noticed that one of our disk-based Volumes used a label name similar to that of our tape-based Volumes. To avoid confusion, I will rename that Volume. But, renaming a Volume is not simple, nor recommended if the Volume contains data. It is better to migrate the data instead. The Volume in question has MediaId = 42 (seriously!): | 42 | PEQ574L4 | Append | 1 | 4,144,705,431 | 0 | 31,536,000 |
Migrating some Bacula jobs Read More »