Troubleshooting integrity verification failure on SnapMirror destination volumes

SnapManager for Exchange integrity verification on volume SnapMirror destination fails when the destination filer is no longer available or it has changed. If the volume SnapMirror destination filer is no longer available, SnapManager for Exchange will provide the following error:

The destination volume filer2:vol1 of the source Logical Disk e does not have valid FlexClone state or SnapMirrored state. FlexClone State is Unknown and SnapMirror State is Unknown. Please check the SnapMirror relationship filer1:vol1 filer2:vol1_dest. Unable to mount snapshot, abort verification.

If you have changed the volume SnapMirror relationship by mirroring data to a new destination filer (for example filer3), SnapManager for Exchange might still try to contact filer2 which may not necessarily exist. This is very likely to happen when you perform a filer hardware upgrade and replace an old filer head with a new one. When you run the SnapMirror update command on new destination filer it will work, but SnapManager for Exchange may not be up to date with the new destination filer.

To resolve this problem, ensure that the following requirements are met.

• SnapMirror status on both the volume SnapMirror source and the volume SnapMirror destination filer is updated with the new destination and that you have run at least one successful manual update (from filer console) after the volume SnapMirror destination has changed.
• For releases of SnapManager for Exchange prior to 4.0, the (new) destination filer is reachable via RSH. Grant RSH access to the SnapManager user by editing the destination filer's \etc\hosts.equiv file or by editing the option rsh.access.
• The new destination filer holds the SnapManager for Exchange user in its built in Administrators group.

Complete the following steps to set the new path as a volume SnapMirror destination for verification purposes.