When you run integrity verification on the SnapMirror destination volume, SnapManager requests SnapMirror updates using SnapDrive, verifies the backup, and monitors the SnapMirror update activity through SnapDrive.
When you run integrity verification on the SnapMirror destination volume, SnapManager performs the following operations:
- Backs up the databases
- Requests a SnapMirror update through SnapDrive to replicate the data across destination volumes
- Verifies the integrity of databases and transaction logs from LUNs that are located in the selected destination volumes
- Updates verification results to the SnapInfo directory
- Updates the SnapMirror instance after the operation, to replicate verification results to the SnapInfo volume
- When the SnapMirror update replicates the backup to the selected destination, SnapManager continuously monitors the SnapMirror update activity through SnapDrive, as follows:
- SnapDrive provides the SnapMirror update progress information continuously to SnapManager during the update.
- SnapManager logs the SnapMirror update activity to the Windows Application event log and to the backup report at every defined interval.
Note: If you have passthrough LUNs on a hyperV client, you must either run the verification operation on a separate host that has direct connection to the destination filer, or you must create a direct connection on the local machine for verification.
Note: If the SnapMirror update operation does not have any progress within a defined interval, SnapManager aborts monitoring it and leaves the backup unverified.
