I'm documenting the restore procedure for a customer site. For offsite media, I am backing up the catalogue to the offsite media, and then purging the records for that media from the catalog (so that subsequent virtualfull backups don't try and use the offsite media as a source, which leads to all sorts of confusion).
There are several TB of onsite Bacula storage, which will cover 99% of restore scenario's, but if a user did want a file that had fallen off the end of the onsite storage and I needed to restore from archived media, I think the procedure might go like: 1. bextract the catalogue from the offsite media (I save the bsr file too so this should be quick) 2. load the catalogue into a different mysql database (or sqlite3 maybe, with an appropriate dump converter?) 3. create a restore job that uses this new catalogue 4. restore the file Is my idea of using a different restore job with a different catalogue to what Bacula uses normally going to work? The config file appears to allow for this but that doesn't mean it works in practice... Thanks James ------------------------------------------------------------------------------ Sponsored by Intel(R) XDK Develop, test and display web and hybrid apps with a single code base. Download it for free now! http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
