RMAN cold backup of Data Guard primary database
edited Nov 5, 2010 2:41PM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 5 commentsAnswered
Hi folks,
I'm doing some testing with RMAN - one of the scenarios I need to test is having a Data Guard implementation (physical standby) where I take a cold backup of the primary.
As you'll know, an RMAN cold backup requires the database to be MOUNTed. However, it seems that with DG implemented, if I MOUNT the primary database, shortly thereafter it is opened (seemingly by the QMNC process but not guaranteed - that's just the closest entry to the "alter database open" in the alert log).
So does anyone take cold RMAN backups of a primary DG database? How do you do this? Or is this behaviour unusual?
I'm doing some testing with RMAN - one of the scenarios I need to test is having a Data Guard implementation (physical standby) where I take a cold backup of the primary.
As you'll know, an RMAN cold backup requires the database to be MOUNTed. However, it seems that with DG implemented, if I MOUNT the primary database, shortly thereafter it is opened (seemingly by the QMNC process but not guaranteed - that's just the closest entry to the "alter database open" in the alert log).
So does anyone take cold RMAN backups of a primary DG database? How do you do this? Or is this behaviour unusual?
0