Critical databases usually are backed up using high end storage backup solutions like EMC's bcv or srdf, or Netapp snapshots.
Both solutions are available to be used with RAC 10g R2 and ASM.
Here you can find the steps to both backup and recover a 10g RAC on ASM.
Always test your implementations before moving them to production.
This procedure combines Storage, EMC related actions, and Database Administration Actions. All Storage related actions are highlighted to diferentiate them.
On prod we have a set of scripts for each step that are run from the enterprise scheduler.
Steps in Brief:
1. Synchronize the Device Groups (establish)
2. On ASM set balance power = 0
3. Archive current on both instances
4. Place database on backup mode
5. Perform consistent split for disk group DATADG
6. End backup mode on the database
7. Create control files backup on disk group ARCHDG
8. Perform consistent split for disk group ARCHDG that contain archived logs and control file copies
9. Optionally backup the snapshot site to tape
1. Prepare the remote host Oracle Homes (optional)
You may configure a remote site to mount and check the backup consistency.2. Identify the LUN's in ASM Datadg disk group:
This step is only required at implementation, afterwards do not require maintainance unless there are structural changes.
a) copy ASM init.ora parameter file: init+ASM.ora to ASM home, dbs directory
b) copy ASM password file orapw+ASM to ASM home, dbs directory
c) copy Database init.ora parameter file: initTSTASM1.ora to Oracle home, dbs directory
d) copy Database password file orapwTSTASM1 to Oracle home, dbs directory
e) update hostname on parameter files to reflect target hostname.
f) create dump directories for database and asm instance
This information needs to be passed to the Storage Manager in order to configure the Symmetrix Device Groups and is required at the implementation stage, afterwards needs to be updated only if there are structural changes.3. Create Symmetrix Device Groups and Associate BCV devices:
GROUP_NUMBER PATH NAME
------------ ------------------------------ --------------------
1 /dev/emcpowera ARCHDG
3 /dev/emcpowere DATADG
3 /dev/emcpowerg DATADG
Two groups are required because the group containing the redo logs require to be split after the group containing the data. 4. Establish (synchronize) The Device Groups:
Make sure de Device Groups are established.5. Online Backup on Production Host:
a) Turn rebalance power to 0 on ASM instance 6. Perform a Consistent Split Snapshot for Database Files:
b) Force a log switch using archive log current
c) Place the database in backup mode
Perform a point in time snapshot of DATADG 7. End Backup Mode:
f) Take the database out of backup mode 8. Create Backup of control files:
g) Force a log switch
h) Create 2 controlfile backups, "control_start" and 9. Perform a Consistent Split Snapshot of the Recovery Area to capture the Archive Log:
control_backup on ARCHDG
i) Prepare an init ora pointing the control file to
control_start on ARCHDG if not ready from point 1.
j) Perform a snapshot of the volumes containing the 10. Start ASM instance on Backup Host and perform checks. (Optional)
archived logs ARCHDG
If you did configure a backup server to check the R2 then follow these steps:
k) Startup the ASM instance on the Backup Host
l) Check that all diskgroups are successfully mounted
m) Startup and mount the database using the parfile
created on "i" , that points to control_start
n) recover and startup readonly
Optional Backup the Backup Steps:
o) Optionally use Backup EMC snapshots of the r2 copy
p) Optionally make EMC snapshots of r2 to be used as report instances, development or tests environments.
q) Optionally backup r2 to tape using RMAN.