In this topic, you must know hot to perform your backups from your physical standby databases. With this, you will reduce the overhead and concurrency of reading your datafiles in the primary as well as avoiding the incrementing of the redo generation caused by full block being written while in backup mode. To make your backups even faster, you can also activate block tracking there.
So train this:
- Enable BCT in the standby DB.
- Make a full backup.
- Make incremental backups.
When I first read this topic, I though it was about "Rolling Forward Physical Standby Database using RMAN incremental backup". So, I would also recommend practicing a bit of that. It's not a easy thing to do, specially if your DG is all in one single server.
So practice:
- Shutdown your standby and delete all archives in the primary (including the not shiped ones).
- Bring your standby back online and recover it using the incremental backups (this is not easy).
Path to Documentation:
Backup and Recovery User's Guide -> 9 Backing Up the Database -> Making and Updating Incremental Backups
Data Guard Concepts and Administration -> 11.10 Using RMAN Incremental Backups to Roll Forward a Physical Standby Database
Click here to go back to the Main OCM 11g Preparation page.
Have you enjoyed? Please leave a comment or give a 👍!
