Applies to ONTAP 9 Storage VM disaster recovery (SVM DR) Issue SVM DR initialization fails with error: Failed to apply the source Vserver configuration. Reason: Apply failed for Object: cifs_domain_se...Applies to ONTAP 9 Storage VM disaster recovery (SVM DR) Issue SVM DR initialization fails with error: Failed to apply the source Vserver configuration. Reason: Apply failed for Object: cifs_domain_server_discovery_mode_view Method: baseline. Reason: Default site needs to be configured if CIFS discovery mode is set to "site".
Applies to ONTAP 9 SnapMirror SVM DR Issue SVM DR relationship initialization is failing with an error: Transfer for volume <SVM constituent volume> failed. Reason: Detected a restart of existing inco...Applies to ONTAP 9 SnapMirror SVM DR Issue SVM DR relationship initialization is failing with an error: Transfer for volume <SVM constituent volume> failed. Reason: Detected a restart of existing incomplete initialize with a different Snapshot copy <Snapshot_Name> than used in the original request. Restart initialize with Snapshot copy "Snapshot_Name".
Applies to CIFS SVM DR ONTAP 9 Issue Users cannot access CIFS shares via Windows File Explorer after SVM DR migration from ONTAP 9.8 to ONTAP 9.11. The following error appears: "Windows cannot access ...Applies to CIFS SVM DR ONTAP 9 Issue Users cannot access CIFS shares via Windows File Explorer after SVM DR migration from ONTAP 9.8 to ONTAP 9.11. The following error appears: "Windows cannot access \\xx.xx.xx\x Check the spelling of thes pelling of the name otherwise there might be a problem with your network. Try to Identify and resolve network problem, click diagnose."
Applies to OnCommand Unified Manager (OCUM) prior 9.4P1 Storage Virtual Machine Disaster Recovery (SVM DR) Issue OCUM generates a false "SVM stopped" event even if the production peer SVM is running a...Applies to OnCommand Unified Manager (OCUM) prior 9.4P1 Storage Virtual Machine Disaster Recovery (SVM DR) Issue OCUM generates a false "SVM stopped" event even if the production peer SVM is running and after the following workflow is followed A test or true disaster recovery incident occurred A recovery or fail back occurred
Applies to SVM DR ONTAP 9.9+ FlexGroup (FG) Issue SVM DR shows unhealthy: cluster2::> snapmirror show -expand Progress Source Destination Mirror Relationship Total Last Path Type Path State Status Pro...Applies to SVM DR ONTAP 9.9+ FlexGroup (FG) Issue SVM DR shows unhealthy: cluster2::> snapmirror show -expand Progress Source Destination Mirror Relationship Total Last Path Type Path State Status Progress Healthy Updated ----------- ---- ------------ ------- -------------- --------- ------- -------- svm2_cluster1: XDP svm2_cluster1_dp: Snapmirrored Idle - false - Internal Error on the SVM DR: Last transfer error: Transfer for volume "FG2" failed. Reason: Internal error.
Applies to ONTAP 9.x Issue SVM DR replication failed with error: Failed to apply the source Vserver configuration. Reason: Apply failed for Object: root_volume_view Method: baseline. Reason: Caching p...Applies to ONTAP 9.x Issue SVM DR replication failed with error: Failed to apply the source Vserver configuration. Reason: Apply failed for Object: root_volume_view Method: baseline. Reason: Caching policy "Standard" does not exist. Execute "snapmirror show -destination-vserver Dest_SVM -fields last-transfer-error,unhealthy-reason -expand" to check if the constituent volumes have encountered errors.
Applies to ONTAP 9.x SVM DR Snapmirror Description If two clusters have SVMs with identical names, configure and use the -local-name parameter when creating vserver peer and snapmirror relationships.
Reason: Failed to delete ruleset: This operation is not permitted on a Vserver that is configured as the destination for identity preserve Vserver DR.Execute "snapmirror show -destination-vserver DR_S...Reason: Failed to delete ruleset: This operation is not permitted on a Vserver that is configured as the destination for identity preserve Vserver DR.Execute "snapmirror show -destination-vserver DR_SVM -fields last-transfer-error,unhealthy-reason -expand" to check if the constituent volumes have encountered errors. Reason: Failed to delete ruleset: This operation is not permitted on a Vserver that is configured as the destination for identity preserve Vserver DR.