02-17-2009 07:50 AM
02-17-2009 08:14 AM
You mean to say: Writting catalog images to a CD for offsite backup?
Normally catalog backup destination should be tape or disk.
So In ur case, you should configure disk catalog backup and then write the disk catalog images to a cd and send that to a offsite
02-17-2009 10:52 AM
What would you expect to use that catalog for in the future? Would you want to merge it into an existing server, or would you want to bring up a blank server that only had that tape in the catalog?
You can copy the image files for the the files on that tape to whatever you want, but I don't know any way to keep a mergeable copy of the volume/media database.
--
Darren
02-17-2009 11:01 AM
Basically there are bunch of backup policies and tapes, but only a couple policies and one tape are used for the offsite backup, because the offsite backup only holds a portion (the most critical data) of the total that is backed up.
The catalogue would be so I restore the files from this one particular offsite tape.
But from what you guys are saying, I need to keep a copy of the entire catalogue that contains mostly unrelated information to this particular policy with the one tape?
02-17-2009 01:20 PM
But what is the expected state of the machine that you want to recover this tape on? Will you build it from scratch at the time of the recovery, or will it already exist?
You always have the option of running bpimport on the tape. For small data sets, that might be fast enough for you. Then you don't need the catalog at all.
I can also imagine a case where you fake the file image of the catalog, and only suppy the portion you need. That would be annoying though.
For many DR sites, it's common to just keep the remote catalog in sync with the primary. It might be bigger than you need, but if it's already in sync you don't have to recover it from tape.
--
Darren