I am searching for a way of making my copy jobs stick around for a
longer period of time then the original jobs.
Intended goal, original jobs are backups to file system, copy jobs go to
tape and are taken offsite. I intend to keep the file backups for a
couple of months for fast restores of accidentally deleted files. The
copy jobs however I intend to keep for at least a year and be able to
search the database for files on them. So that in the event I do have
to restore from one of the offsite tape backups, I can find the file and
give the local operator the specific volume to go and retrieve.
I don't see any obvious method of setting a longer retention period on
the copy jobs. I tried setting longer periods in the tape pool
resource, but don't see any messages in the job logs stating that it was
indeed extended from the original jobs.
What is the best way to accomplish this?
Will setting a longer file/job retention periods with a shorter volume
retention allow the volumes of the disk pool to recycle, while the job
and file information stay intact on the tape pool volumes?
Or do I need to use a SQL selection admin job to purge the disk volumes
thereby promoting the offsite copy jobs to backup jobs?
--
Thanks,
Dean E. Weimer
http://www.dweimer.net/
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
