Search
- Filter results by:
- View attachments
- https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Linux_NFS_client_lost_connection_after_SVM_migration_by_SnapMirror_volume_replicationApplies to ONTAP 9 SnapMirror Storage Virtual Machine Disaster Recovery (SVM DR) Issue Linux NFS clients lost connection to export volumes after SVM migration by SnapMirror volume replication A reboot...Applies to ONTAP 9 SnapMirror Storage Virtual Machine Disaster Recovery (SVM DR) Issue Linux NFS clients lost connection to export volumes after SVM migration by SnapMirror volume replication A reboot of the NFS client could restore the connection
- https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/In_an_SVM_DR_relationship_after_modifying_source_volume_does_destination_volume_automatically_resizeApplies to ONTAP 9 SVM-DR Answer In an SVM-DR relationship, after modifying source volume, changes will be incrementally reflected in the destination volume, when it will reach the configured autosize...Applies to ONTAP 9 SVM-DR Answer In an SVM-DR relationship, after modifying source volume, changes will be incrementally reflected in the destination volume, when it will reach the configured autosize-grow-threshold-percent parameter Additional Information How to modify SnapMirror destination volume size and other attributes What is volume autosize in Data ONTAP?
- https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/How_to_delete_CIFS_server_without_deleting_the_machine_account_from_ADApplies to Data ONTAP 8 ONTAP 9 CIFS Snapmirror SVM Replication Description In case of Snapmirror SVM replication, destination SVM has same CIFS server name as the source SVM. If you have deleted that...Applies to Data ONTAP 8 ONTAP 9 CIFS Snapmirror SVM Replication Description In case of Snapmirror SVM replication, destination SVM has same CIFS server name as the source SVM. If you have deleted that Snapmirror relationship and have requirement to create new CIFS server in the destination SVM without deleting the original CIFS server account from AD, this procedure can be followed.
- https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/SVM-DR_SystemManager_shows_error_after_unprotecting_a_Volume_via_CLIApplies to ONTAP 9.x SVM-DR Issue System Manager shows an error in the Protection Tab for a Volume which has been unprotected Remote cluster or remote vserver not reachable or relationship is deleted ...Applies to ONTAP 9.x SVM-DR Issue System Manager shows an error in the Protection Tab for a Volume which has been unprotected Remote cluster or remote vserver not reachable or relationship is deleted but not released No issue found with the SVM-DR replication
- https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/After_delete_of_SVM-DR_relationship_the_destination_SVM_cannot_be_deleted_due_to_CIFS_serverAfter decommissioning of a relationship, the destination vserver deletion fails with the following error: Reason: The Vserver is associated with Active Directory configured CIFS server "XXX" The delet...After decommissioning of a relationship, the destination vserver deletion fails with the following error: Reason: The Vserver is associated with Active Directory configured CIFS server "XXX" The deletion is partially complete. Delete the CIFS server using "cifs delete" and retry to complete the deletion. CIFS cannot be stopped or deleted or stopped: Error: command failed: This operation is not permitted on a Vserver that is configured as the destination for Vserver DR.
- https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/SVM_DR_config_replication_failed_due_to_missing_FlexClone_licenseApplies to ONTAP 9.6 SVM DR FlexClone license Issue Snapmirror Error: Failed to apply the source Vserver configuration. Reason: Unrecoverable error during configuration replication, requires manual in...Applies to ONTAP 9.6 SVM DR FlexClone license Issue Snapmirror Error: Failed to apply the source Vserver configuration. Reason: Unrecoverable error during configuration replication, requires manual intervention. Error: Flexclone license missing.
- https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/Why_is_a_destination_volume_on_SVM-DR_smaller_then_its_source_volumeDue to this, when source volume size increases, destination volume size remain the same, unless auto size feature activates. By default, data protection volumes are set to the grow_shrink autosize mod...Due to this, when source volume size increases, destination volume size remain the same, unless auto size feature activates. By default, data protection volumes are set to the grow_shrink autosize mode, which enables the volume to grow or shrink in response to the amount of used space. If volume autosize is not enabled for the snapmirror destination, consider enabling it and setting it to grow_shrink.
- https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/SVM-DR_not_transferring_Snapshots_as_per_SnapMirror_policyApplies to ONTAP 9 SVM-DR Issue Snapshots are missing on the destination volume
- https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/Can_I_use__Fan-out_to_migrate_an_Identity_preserve_SVM_DR_to_a_new_ClusterApplies to In ONTAP 9.3 and earlier, only one identity-preserve true relationship is allowed per source-SVM Starting with ONTAP 9.4, SVM-DR allows fanout to two destinations, with considerations Use v...Applies to In ONTAP 9.3 and earlier, only one identity-preserve true relationship is allowed per source-SVM Starting with ONTAP 9.4, SVM-DR allows fanout to two destinations, with considerations Use volume SnapMirror to migrate the data to an SVM of the New Cluster Break and release the original SVM-DR Convert the new volume SnapMirror to SVM-DR Converting volume replication relationships to an SVM replication relationship SVM-DR cannot create the second destination relationship
- https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/Missing_Snapshots_on_middle_cluster_of_cascadeCustomer original environment was a production cluster to DR cluster. They used a surrogate cluster on source acting as a tertiary (A->C) of a cascade. Customer relocated the tertiary (A->C) to the DR...Customer original environment was a production cluster to DR cluster. They used a surrogate cluster on source acting as a tertiary (A->C) of a cascade. Customer relocated the tertiary (A->C) to the DR site and attempted to reestablish replication (C->B). This failed with the not common snapshot error. The common snapshots were on the (A->C) cluster but the snapmirror transfer with mirrorallsnapshot did not transfer the common snapshot or daily snaps.
- https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/SVM-DR_stopped_working_if_one_source_MDV_CRS_is_deleted_and_the_other_is_abandonedSVM-DR MDV (Meta Data Volume) SVM-DR updates are failing with error: Metadata volume is not available on cluster "source". Run "snapmirror config-replication status show" for more details.” Source::*>...SVM-DR MDV (Meta Data Volume) SVM-DR updates are failing with error: Metadata volume is not available on cluster "source". Run "snapmirror config-replication status show" for more details.” Source::*> snapmirror config-replication status show Storage Status: warning Storage In Use: Unavailable Storage Remarks: Unable to free resources Source::*> debug cps storage-area-group show Abandoned Volumes: MDV_CRS_2104458f258d11e454cd123478563456_A Standby Recreate Retry Count: 0