Oracle database and consistency group disaster recovery
Contributors
Suggest changes
PDFs
Consistency group replication can be can be as simple as scheduling replication of a single volume via SnapMirror. This includes datafiles, controlfiles, archive logs, and redo logs. Every SnapMirror update results in a new copy of the database at the destination site that is consistent and ready for activation by breaking the mirror.
Where a database must span volumes, a consistency group snapshot (cg-snapshot) is required.
An additional benefit of this strategy when used with SnapMirror in block- level replication mode is complete replication of all snapshots on the source storage system. The full complement of backups is replicated in addition to the disaster recovery copy.