Commit-coherent Backup
The SDS secondary commit‑coherent (consistent) backup mechanism enables you to create a backup of a secondary that when recovered, stops tracking and is in a commit‑coherent state. This provides an SDS secondary native backup that you can use to create (re‑clone) an SDS secondary RPS node.
It signals the successful completion of a database backup transaction on an SDS secondary and arranges a database quietpoint on the primary to establish a commit‑coherent end backup recovery state that is stored in the database control file. Backup recovery stops tracking at end backup, saving replay state. (This mechanism can be called only from a secondary, to replicate the creation of an RPS database on the primary server.)
For more details and the exceptions that can be raised, see the
