>>>>> On Mon, 25 Feb 2008 13:18:31 +0200, Timo Neuvonen said: > > I'm running full backups at certain intervals, and incremental ones > meanwhile, all these to pools dedicated for "everyday backups". > > Then, occasionally, I also run full backups that are stored into different > pool, and the tapes are taken off-site to be used in real emergency only. > These "emergency backups" are run using the same job and fileset definitions > as the full "everyday backups", since they both basically are ment to > contain everything from certain computers. > > So, the problem: > Now, the incremental backups after the "emergency backup" will be against > the "emergency backup", not the last "everyday backup" like I'd like to. If > a need for a restore arises, this will cause problems since the "emergency > backup" is more difficult to access due to its distant off-site location. > > I wouldn't care to write double job definitions or filesets to workaround > this. But is there currently any other way to run an "extra" full backup > that wouldn't be noticed when running the following differential / > incremental backups? Due to some practical reasons these emegency backups > are also difficult to shedule for the night before the next regular full > backup.
A couple of approaches: - Delete the job from the catalog before the next incremental backup. - Use a separate catalog, defining the volumes in the emergency backup pool and the jobs. __Martin ------------------------------------------------------------------------- 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
