Well.... How about if you are performing BCV snapshots of the storage under Box-A (prod server) and then mounting those BCVs on Box-B, mounting (not opening!) the database on Box-B, and performing RMAN backups?
That would remove any resource consumption from the all-important Box-A as far as backups are concerned. Of course, archived redo log backups should continue to be performed from Box-A, but the datafile backups can be performed from Box-B. I'm not sure, but perhaps Box-B would even be able to perform the "re-silvering" operation to re-mirror the BCV volumes back into the main RAID-1 set, thus truly relieving Box-A of the burdens of backups... It would be highly advisable to use a centralized "recovery catalog" database in this situation (instead of NOCATALOG mode). Since both database images on both servers will have the same DBID, the "recovery catalog" database should record both types of backups (datafile on Box-B and everything else on Box-A) as if they were all performed from Box-A... Just an idea... -Tim > Hi, > > Can anyone think of a reason(s) why one WOULD want to > backup a database from a box other than the database box > itself? Are there any advantages to this kind of > configuration? > > For example: > > Box-A (production db server) > Box-B (rman db server) > > A cron job runs on Box-B which backups up the database > from Box-A. > > > Thanks in advance! > > -w > -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Tim Gorman INET: [EMAIL PROTECTED] Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services --------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
