Legacy Backups Manual Migration to Bacula
"Joseph inherited Greek gift: a proprietary backup legacy created by the Backupator software!"
The solution of backups generated by other tools, notably those with a proprietary writting format (Spectrum/TSM, Arcerve, Netbackup, etc.), is often complex and companies end up choosing to maintain the legacy structure (software + hardware) while the retention of these backups does not expire.
An alternative to migrating to Bacula is the following strategy: restore the main backups performed by the previous tool (preferably to the Client server in a temporary x directory), and back up this information from a Bacula client.
After performing the new backup with Bacula, you can make a small change to the Catalog, in order to modify the backup date to match the date of the original backup made by the previous tool. We can also change the name of the backup (job name) so that it is the same as the original. This can be done right in the bacula database, or through bconsole, sqlquery:
update job set starttime='2018-09-28 18:50:16' where jobid='309'; update job set name='legacy-backup-name' where jobid='309';
In this example, I modified the date and time of execution of the Job of Id 309, as if it had been executed at the turn of the year.
If you have already installed the Bacula client on the Backup Client that owns the original data, you can also rename the backup client to match that configured on Bacula:
update job set client='legacy-client-fd' where jobid='309';
To restore backups later, you can use the restore options to remove the temporary "x" directory from which you restored the legacy backups from the paths. restore ... mod ... 10: File Relocation, 1: Strip prefix.