The Relationship: All Relationships view displays information about protection relationships on the storage system.
If the message Resource-key not discovered is displayed, this might indicate that the SVM exists on the cluster but has not yet been added to the Unified Manager inventory, or that the SVM was created after the cluster's last refresh. You must ensure that the SVM exists, or perform a rediscovery on the cluster to refresh the list of resources.
If the message Resource-key not discovered is displayed, this might indicate that the volume exists on the cluster but has not yet been added to the Unified Manager inventory, or that the volume was created after the cluster's last refresh. You must ensure that the volume exists, or perform a rediscovery on the cluster to refresh the list of resources.
Specifies the priority at which a transfer runs for asynchronous operations. The transfer priority is Normal or Low. Normal priority transfers are scheduled before low priority transfers. The default is Normal.
Applies only to SnapVault relationships. This specifies whether incremental transfers ignore files which have only their access time changed. The values are either True or False. The default is False.
Specifies the action ONTAP performs when a synchronous relationship is not able to be synchronized. StrictSync relationships will restrict access to the primary volume if there is a failure to synchronize with the secondary volume. Sync relationships do not restrict access to the primary if there is a failure to synchronize with the secondary.
Specifies the maximum number of times to attempt each manual or scheduled transfer for a SnapMirror relationship. The default is 8.
Provides a text field for comments for specific to the selected policy.
Specifies the SnapMirror label for the first schedule associated with the Snapshot copy policy. The SnapMirror label is used by the SnapVault subsystem when you back up Snapshot copies to a SnapVault destination.
Specifies how long backups are kept, based on the time or the number of backups.
Specifies the number of Snapshot copies on this volume that match the specified label.
Specifies the number of SnapVault Snapshot copies that are not deleted automatically even if the maximum limit for the policy is reached. The values are either True or False. The default is False.
Specifies the Snapshot copy limit at which a warning is sent to indicate that the maximum retention limit is nearly reached.
The lag duration should be close to, or equal to, 0 seconds for StrictSync relationships.
The lag duration is greater than or equal to the lag error threshold.
The lag duration is greater than or equal to the lag warning threshold.
The lag duration is within normal limits.
The lag status is not applicable for synchronous relationships because a schedule cannot be configured.
The last successful update is not applicable for synchronous relationships.
SnapMirror transfers are enabled; however, a transfer abort operation that might include removal of the checkpoint is in progress.
The destination volume is undergoing a diagnostic check and no transfer is in progress.
SnapMirror transfers are enabled. The volume is currently in the post-transfer phase for incremental SnapVault transfers.
Transfers are enabled and no transfer is in progress.
The data in the two volumes in the synchronous relationship are synchronized.
The data in the destination volume is not synchronized with the source volume.
SnapMirror transfers are enabled. The volume is currently in the pre-transfer phase for incremental SnapVault transfers.
SnapMirror transfers are enabled. No transfers are in progress.
SnapMirror transfers are disabled. No transfer is in progress.
A SnapMirror transfer is in progress. Additional transfers are disabled.
SnapMirror transfers are enabled and a transfer is in progress.
The asynchronous transfer of data from the source to the destination volume is complete, and the transition to synchronous operation has started.
A SnapMirror transfer has been initiated, but some associated tasks are waiting to be queued.
The transfer duration is not applicable for StrictSync relationships because the transfer should be simultaneous.
The transfer size is not applicable for StrictSync relationships.
The transfer priority is not applicable for synchronous relationships because all transfers are treated with the same priority.
The schedule is not applicable for synchronous relationships.