When you create a copy of the secondary backup on a remote CCR node, SnapManager performs a particular sequence of steps.
- Connects to another CCR node to rename backups and updates the backup timestamp if there is a more recent backup.
- Creates a copy of database backup on the remote CCR node and deletes the older backups.
Note: SnapManager does not regroup the backups on the remote CCR node based on the CCR node volume that is used by the databases.
- Creates a full database backup on the CCR node on which the full backup was initialized and performs verification of the backup sets, if you select the Run Verification option.
- Connects to the remote CCR node and copies the extra log files, which might be truncated from the primary node to the remote node.
Note: The secondary backup created on the remote is always standard. The secondary backup created on the remote node is not verified even if the primary backup is verified.
