Frank Sweetser wrote: > A little more work to get out, but no, lack of the catalog data does not make > the volumes useless at all. Even if you had some disaster which physically > destroyed everything but the backup volumes, you can still get your data back. > > The brute force method is to use bls and bextract. These are simple command > line utilities that can list and extract data straight from volumes. They're > much less convenient, but can save you in a pinch. > > The other option is to re-create a Bacula setup, and use bscan. This command > will take inventory of all data on a volume, and populate a catalog with it. > You can then run a normal restore command to get data back. > Oh ok, thats good to know. The more I get in to bacula, the more I like it ! > I do here, yes, out of simplicity. Also the fact that the main Bacula server > has good redundancy (RAID, multiple PSU, etc) which reduces my risk a little. > Our bacula server also has raid/multiple psu etc.. I think after the backup as finished using the RunAfterJob, I'll rsync the bsr and catalog files to another server offsite and archive them. I'll also go with the burning to a cd/dvd once a week as well, to keep them with the rest of the tapes. > As long as you do it with a separate job, it shouldn't be a problem. Will be through a separate job.
Thanks everyone for your help, starting to make a bit more sense! Cheers, SG ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
