Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 2 results
    • https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/SVM-DR_Fails_to_apply_the_source_Vserver_configuration_vserver_ui_entry_doesnt_exist
      Applies to SVM-DR SnapMirror Initialize/Update/Resync fails with the error: Failed to apply the source Vserver configuration. Reason: Apply failed for Object: Reason: entry doesn't exist. Source SVM i...Applies to SVM-DR SnapMirror Initialize/Update/Resync fails with the error: Failed to apply the source Vserver configuration. Reason: Apply failed for Object: Reason: entry doesn't exist. Source SVM is assigned with non-default policy and the SVM DR SnapMirror policy with type mirror-vault source_cluster::> vserver show -vserver source_vserver -fields snapshot-policy vserver snapshot-policy destination_cluster::> snapmirror show -destination-path destination_vserver: -fields policy-type
    • https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/Solaris_Host_support_recommended_settings_in_SnapMirror_active_sync_formerly_SM_BC_configuration
      In case of a disaster scenario, when the site hosting the primary cluster experiences a disaster, the host multipathing software marks all paths through the primary cluster as down and as part of the ...In case of a disaster scenario, when the site hosting the primary cluster experiences a disaster, the host multipathing software marks all paths through the primary cluster as down and as part of the site failover, I/O resumes via the secondary cluster paths. In the event of a disaster, the SCSI failover characteristics (ALUA) on various paths to the same LUN toggle between Active Optimized (AO) and Active Non-Optimized (ANO)