>> On Thu, 25 Jan 2007 08:17:47 -0500, Joni Moyer <[EMAIL PROTECTED]> said:
> I would now like to run a second dbb that will go to disk which is > then replicated to our disaster recovery site. And create a 2nd DRM > plan after this dbb is run as well. I spent a few years cutting snapshots here, fulls there, etc. Where I ended up was doing my database backups to virtual volumes, written to a TSM server which was itself local, but had remote copy pools. This meant that: 1) I could write to disk for concurrency's sake, but still store data on tape 2) I could generate multiple physical copies of a DB Backup, without multiple intensive BACKUP DB processes. 3) The DB backups I have offsite are -actual copies- of the onsite, rather than "snapshots taken at approximately similar times". This may be merely an aesthetic concern, but it always bothered me to have my offsite different from my onsite DBB. I ended up also using the server that got DBBs as library manager, too. Here's a pretty detailed discussion of it, last updated (dang!) beginning of 2005 I should fix that. http://open-systems.ufl.edu/services/NSAM/whitepapers/design.html - Allen S. Rout
