We tested the RMAN crosscheck command when testing DR replication and although I thought we were going to need it, we didn't. If I can remember correctly, the RMAN database holds some information about the image the data is on, and the location of that image (MediaID or DSSU location), however when you go to do a restore, it requests the image, not the location, and Netbackup is responsible for supplying the correct source. To make our DR work, we only have to make two changes. 1) Change the client name to the original source client (our DR servers have different names then Prod) and reboot (if windows) 2) Account for any time difference when issuing the RMAN restore commands (Our DR site is 3 time zones behind, so we have to add 3 hours to the restore requests.) Hope that helps. -Jonathan ________________________________
From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Wheeler, Gideon Sent: Thursday, September 24, 2009 10:15 AM To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] Netbackup 6.5 Oracle agent using RMAN crosscheckcommand Has anyone had experience using the RMAN crosscheck command to keep the oracle RMAN catalogue in sync, particularly when duplication is involved. Its highly probable that the original RMAN entry will point to an expired image ( although the 2nd copy is still active) Regards Gideon
_______________________________________________ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
