White Papers
Best Practices for Oracle 11g Backup and Recovery using RMAN and Dell EqualLogic Snapshots
25
5. Start up the database in mount state.
6. Restore the database to a specific previous time using the System Change Number
7
7. Once the flashback operation is complete, open the database using resetlogs.
(SCN).
Configuration Notes:
• The FLASHBACK DATABASE feature uses flashback logs to track database changes. If the
flashback feature is enabled, then flashback logs are generated and are written sequentially to
flash recovery area during normal database operation.
• When enabling the FLASHBACK DATABASE feature, the flash recovery area should be planned
such that it can accommodate these logs. When we executed Quest Benchmark factory TPC-
C tests simulating 4000 concurrent transactions, approximately 30GB of flashback logs were
generated per hour.
6.2 Point-in-time recovery using EqualLogic snapshots
In this section we provide an outline of the steps necessary to complete a point-in-time recovery of
the database using EqualLogic snapshots instead of using the Oracle FLASHBACK DATABASE feature.
On the production database server:
1. Dismount the Oracle database and redo log ASM disk groups.
2. Logout from the iSCSI initiators on the production database servers.
Using the EqualLogic Group Manager:
3. Set the Oracle database and redo log volumes offline on the EqualLogic group.
4. Perform a snapshot restore of the volumes on the EqualLogic group.
On the production database server:
5. Re-discover the iSCSI targets on the production database servers.
6. Login to the discovered iSCSI targets.
7. Rescan the Oracle ASM disks.
8. Shut down and then restart the ASM database instance on the production database servers.
9. Mount the Oracle database and the redo log ASM disk groups.
10. Bring the database instance to the mounted state.
11. Recover the database using the archived REDO logs.
12. Once the database recovery is complete, open the database.
7
From http://www.orafaq.com/wiki/SCN: “A number, internal to Oracle that is incremented over time as change
vectors are generated, applied, and written to the Redo log.”