commitCoherentBackup
commitCoherentBackup();
The commitCoherentBackup method of the JadeDatabaseAdmin class signals the successful completion of a database backup transaction on an SDS secondary.
This method arranges a database quietpoint on the primary to establish a commit‑coherent (consistent) end backup recovery state that is stored in the database control file. This is then backed up to the default backup directory specified in the beginBackup method. Backup recovery will stop tracking at end backup, saving replay state. (This method, which can be called only from a secondary, replicates the creation of an RPS database on the primary server.)
This SDS secondary commit‑coherent 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; that is, it replaces the commitBackup method.
The commit‑coherent checkpoint processing on the primary performs a checkpoint within a database quietpoint. The primary
You may encounter an exception 3077 (Maximum time to wait for a quiet point was exceeded), in which case, the backup remains active and you can retry the commitCoherentBackup method call or you can call the abortBackup method. The backup terminates with the exception if it is unhandled. Other errors (for example, the 3221 (SDS primary not connected) or 3212 (SDS a response was not received within a reasonable timeframe) error) terminate the backup with that exception.
2016.0.01 and higher
