ALERT

This message occurs when a Vserver DR subsystem does not enable inline deduplication on the destination volume. Inline deduplication is not enabled when the destination volume is on neither an AFF system nor a hybrid aggregate.

If inline deduplication is required on the destination volume, move the volume to a hybrid aggregate, and then enable inline deduplication. For more information, refer to TR-4476.

Vserver DR: The volume %s of the Vserver %s is on neither an AFF system nor a hybrid aggregate. Therefore, inline deduplication is not enabled on the volume.

destination_volume (STRING): Name of the destination volume of the Vserver DR relationship.
destination_vserver (STRING): Name of the destination Vserver of the Vserver DR relationship.

ALERT

This message occurs during configuration replication, when the aggregate on which the volume needs to be created or modified is either offline or not in the cluster.

Log in to the cluster and bring the aggregate online by using the "storage aggregate online" command. If the node that owns the aggregate is down, bring it back up.

Configuration replication for volume "%s" in Vserver "%s" has failed because the aggregate "%s" is offline.

volume_name (STRING): Volume on which this error occurred.
aggregate_name (STRING): Name of the aggregate.
vserver_name (STRING): Vserver name for which configuration replication is happening.

ERROR

This message occurs during configuration replication, when the the volume creation fails because the aggregate is not accessible because the cluster logical interface (LIF) is down.

Log in to the source cluster and run the "network interface show" command to see the state of the cluster LIFs and to identify the down LIFs.Verify that port connectors, cabling, and cluster switch ports are correctly installed and configured.

Configuration replication for volume "%s" in Vserver "%s" has failed because the cluster LIF is operationally down.

volume_name (STRING): Volume on which this error occurred.
vserver_name (STRING): Vserver name for which configuration replication is happening.

ALERT

This message occurs when a Vserver DR subsystem discovers a mismatch between the compression types of the source and destination volumes, and therefore do not apply the compression type setting of the source volume to the destination volume.

Undo all off the compression savings on the destination volume, and then modify the compression type of the volume. For more information, refer to TR-4476.

Vserver DR: Compression type of destination volume %s of Vserver %s is %s, which is different from the source volume compression type %s. Therefore, the compression type of the source volume was not applied on the destination volume.

destination_volume (STRING): Name of the destination volume of the Vserver DR relationship.
destination_vserver (STRING): Name of the destination Vserver of the Vserver DR relationship.
destination_compression_type (STRING): Compression type of the destination volume.
source_compression_type (STRING): Compression type of the source volume.

ERROR

This message occurs when the configuration of a metadata volume cannot be replicated because there exists another metadata volume with the same name on the destination cluster.

Contact NetApp technical support to remove one of the duplicate metadata volumes.

Configuration replication for metadata volume "%s" in Vserver "%s" has failed because there exists another metadata volume with the same name on the destination cluster.

volume_name (STRING): Volume on which this error occurred.
vserver_name (STRING): Name of the Vserver for which configuration replication is happening.

ALERT

This message occurs when an encrypted volume at the source of a Vserver-DR setup is replicated as a non-encrypted volume at the destination. This can happen if: 1) the key management capability is not enabled at the destination Vserver; 2) the destination Vserver does not have an aggregate that supports encrypted volumes; or 3) the volume of the source Vserver has undergone a conversion operation from non-encrypted to encrypted.

If necessary, set up the key management capability at the destination by using the "security key-manager setup" command. Ensure that the destination Vserver contains an aggregate that supports encrypted volumes. Use the "snapmirror show" command to determine the type of relationship. If the displayed type is "XDP", encrypt the destination volume by performing a conversion operation from non-encrypted to encrypted using the "volume encryption conversion start" command. However, if the type is "DP", encrypt the destination volume by performing a volume move operation using the "volume move start -encrypt-destination true" command.

Source volume for volume "%s" in Vserver "%s" is encrypted, but it is replicated as a non-encrypted volume at the destination.

dest_volume_name (STRING): Name of the destination volume.
source_vserver_name (STRING): Name of the source Vserver.
dest_vserver_name (STRING): Name of the destination Vserver.

ERROR

This message occurs when the system detects a conflict in the junction path between the volumes of a source and destination Vserver during a SnapMirror resync operation.

Unmount the destination volume or mount it at a different path, and then try the operation again.

Source Vserver "%s" has volume "%s" and junction path "%s" that conflicts with destination Vserver "%s", volume "%s" and the same junction path "%s". Reason: The destination volume is excluded from Vserver DR protection in the reverse direction.

source_vserver_name (STRING): Name of the source Vserver.
src_volume_name (STRING): Name of the source volume.
src_volume_junction_path (STRING): Junction path of the source volume.
dest_vserver_name (STRING): Name of the destination Vserver.
dest_volume_name (STRING): Name of the destination volume.
dest_volume_junction_path (STRING): Junction path of the destination volume.

ERROR

This message occurs when a clone volume is moved in a Vserver DR setup. As a direct consequence, an implicit clone split occurs. The parent volume no longer has any relation with the child volume. Snapshots(tm) copies of the parent volume are unlocked and can get deleted, thereby affecting the SnapMirror® replication.

Run "volume move" command to move the volume to the corresponding aggregate.

The volume "%s" of Vserver "%s" has been moved. It is a clone volume. Move the clone volume as well.

volume_name (STRING): Volume that has to be manually moved.
vserver_name (STRING): Vserver name for which configuration replication is happening.

ERROR

This message occurs when the parent of a clone volume is moved in a Vserver disaster-recovery (DR) configuration. If the moved volume is deleted or its Snapshot® copies are deleted, the SnapMirror® transfer fails.

Run the "volume move" command to move the volume to an appropriate aggregate. If the volume was deleted at the source and the transfer failed, additionally run "snapmirror resync".

The volume "%s" of Vserver "%s "has been moved. The mirroring of this volume is at risk as it is the parent of a clone volume.

volume_name (STRING): Volume that has to be manually moved.
vserver_name (STRING): Name of the Vserver for which configuration replication is happening.

ERROR

This message occurs when the source Vserver contains a volume with the same name as one on the destination Vserver, and the volume at the destination is excluded from Vserver Disaster Recovery(DR) Protection in the reverse direction. Future resynchronization attempts might fail unless the problem is resolved.

Rename the source or the destination volume, and then try the operation again.

The source Vserver "%s" has a volume with name "%s" while the destination Vserver "%s" has a volume with the same name "%s" that is excluded from Vserver DR Protection in the reverse direction.

source_vserver_name (STRING): Name of the source Vserver in a Vserver DR setup.
src_volume_name (STRING): Name of the volume on the source Vserver.
dest_vserver_name (STRING): Name of the destination Vserver in a Vserver DR setup.
dest_volume_name (STRING): Name of the volume on the destination Vserver.

ERROR

This message occurs when the volume that needs to be created on the destination cluster has a parent volume that did not get replicated. The possible types of volumes for which this error can occur are LS, FlexCache®, and FlexClone®.

Log in to the cluster and unlock the Vserver by using "vserver unlock" command at a diag privilege level, and then create the parent volume by using the "volume create" command. Lock the Vserver by using the "vserver lock" command, and start the configuration replication with a resync.

Configuration replication for volume "%s" of type %s in Vserver "%s" has failed because the parent volume for this volume has not been replicated.

volume_name (STRING): Volume on which this error occurred.
volume_type (STRING): Type of volume. Possible values could be LS, FlexCache, or FlexClone.
vserver_name (STRING): Vserver name for which configuration replication is happening.

ERROR

This message occurs when there is no space left in the aggregate for new volumes to be created during configuration replication.

Log in to the cluster and assign more disks to the aggregate.

Configuration replication for volume "%s" in Vserver "%s" has failed because the aggregate "%s" does not have enough space.

volume_name (STRING): Volume on which this error occurred.
vserver_name (STRING): Vserver name for which configuration replication is happening.
aggregate_name (STRING): Name of the aggregate.

ERROR

This message occurs when there is not enough space left in the fabric pool aggregate for new volumes to be created during configuration replication.

Log in to the cluster and assign more disks to the perf tier of fabric pool aggregate.

Couldn't place volume "%s" of Vserver "%s" in fabric pool aggregate as there is not enough spece left in perf tier.

volume_name (STRING): Volume on which this error occurred.
vserver_name (STRING): Vserver name for which configuration replication is happening.

ERROR

This message occurs when a protected volume is mounted under an unprotected volume on the source of a Storage Virtual Machine (SVM) disaster recvoery (DR) relationship and a SnapMirror® transfer is subsequently initiated. Data continues to be served from this volume, but the volume is not protected by the DR relationship.

Execute any of the following operations on the source cluster to ensure that parent and child volumes have matching protection types, and then invoke the "snapmirror resync" command. 1. Mount the volume under a protected volume. 2. Change the protection type of the parent volume in the junction-path to protected. 3. Change the protection type of the volume to unprotected. To change the protection type, use the command "volume modify -vserver vserver_name -volume volume_name -vserver-dr-protection".

Unable to mount the volume %s:%s under an unprotected volume.

vserver_name (STRING): Name of the SVM for which the SnapMirror transfer was initiated.
volume_name (STRING): Name of the volume that the system is trying to replicate on the destination SVM.

ALERT

This message occurs when a Vserver DR subsystem fails to disable quotas on the destination volume.

Disable quotas on the volume by using the "volume quota off".

Vserver DR: Failed to disable quotas on volume %s of Vserver %s. Reason: %s

destination_volume (STRING): Name of the destination volume of the Vserver DR relationship.
destination_vserver (STRING): Name of the destination Vserver of the Vserver DR relationship.
reason (STRING): Reason.

ALERT

This message occurs when a Vserver DR subsystem fails to enable quotas on the destination volume.

Enable quotas on the volume by using the "volume quota on" command.

Vserver DR: Failed to enable quotas on volume %s of Vserver %s. Reason: %s

destination_volume (STRING): Name of the destination volume of the Vserver DR relationship.
destination_vserver (STRING): Name of the destination Vserver of the Vserver DR relationship.
reason (STRING): Reason.

ALERT

This message occurs when a Vserver DR subsystem does not enable data compaction on the destination volume. Data compaction is not enabled when the destination volume space guarantee setting is not set to "none".

Set the space guarantee of the volume to "none", and then enable data compaction. For more information, refer to TR-4476.

Vserver DR: Volume space guarantee setting for volume %s of Vserver %s is not set to "none". Therefore, data compaction is not enabled on the volume.

destination_volume (STRING): Name of the destination volume of the Vserver DR relationship.
destination_vserver (STRING): Name of the destination Vserver of the Vserver DR relationship.

ALERT

This message occurs when a Vserver DR subsystem does not enable cross volume inline deduplication on the destination volume. Inline deduplication is not enabled when the destination volume space guarantee setting is not set to "none".

Set the space guarantee of the volume to "none", and then enable cross volume inline deduplication. For more information, refer to TR-4476.

Vserver DR: Volume space guarantee setting for volume %s of Vserver %s is not set to "none". Therefore, cross volume inline deduplication is not enabled on the volume.

destination_volume (STRING): Name of the destination volume of the Vserver DR relationship.
destination_vserver (STRING): Name of the destination Vserver of the Vserver DR relationship.

ALERT

This message occurs when a Vserver DR subsystem fails to replicate the efficiency configuration from the source volume to the destination volume.

Manually enable the efficiency configuration on the destination volume. For more information, refer to TR-4476.

Vserver DR: Failed to replicate the efficiency configuration on volume %s of Vserver %s. Reason: %s

source_volume (STRING): Name of the source volume of the Vserver DR relationship.
source_vserver (STRING): Name of the source Vserver of the Vserver DR relationship.
reason (STRING): Reason for the failure.

ALERT

This message occurs when a Vserver DR subsystem fails to apply the efficiency configuration on the destination volume.

Manually apply the efficiency configuration on the volume. For more information, refer to TR-4476.

Vserver DR: Failed to apply the efficiency configuration on volume %s of Vserver %s. Reason: %s

destination_volume (STRING): Name of the destination volume of the Vserver DR relationship.
destination_vserver (STRING): Name of the destination Vserver of the Vserver DR relationship.
reason (STRING): Reason.

ALERT

This message occurs when the volume location database (VLDB) goes offline during configuration replication. None of the volume services can commence without bringing it online.

Retry the SnapMirror® operation by running the "snapmirror resync" command. If the problem persists, contact NetApp technical support.

Configuration replication for volume "%s" in Vserver "%s" has failed because the VLDB is offline.

volume_name (STRING): Volume on which this error occurred.
vserver_name (STRING): Vserver name for which configuration replication is happening.