Skip to main content
NetApp Knowledge Base

What does volume level snapmirror replicate?

  1. Last updated
  2. Save as PDF
Views:
847
Visibility:
Public
Votes:
0
Category:
snapmirror
Specialty:
dp
Last Updated:

Applies to

  • ONTAP 9.x
  • Data ONTAP 8.x
  • Data ONTAP operating in 7-mode

Answer

  • Volume-level SnapMirror replicates the source volume (data), its snapshots, source volume options, CIFS ACLs
  • Volume level SnapMirror preserves NTFS ACLs, including the SIDs within them. However, SnapMirror does not replicate or recreate the underlying user or group identities associated with those SIDs  
  • Volume-level SnapMirror preserves NTFS ACLs, including SIDs, but does not replicate access to data, such as CIFS shares, NFS exports, junction paths, or SAN configuration. The data SVM serves the data, and the data SVM configuration is needed to provide this access.
  • SnapMirror does not replicate or recreate the underlying user or group identities associated with replicated ACLs and SIDs. 
    • To replicate both the volume data as well as all or part of the SVM's configuration, consider replicating at the SVM level with SVM DR
    • In WORKGROUP environments, each SVM maintains its own local domain with unique domain SIDs. When volume-level SnapMirror replicates NTFS ACLs to a destination SVM: 
      •  The ACL data (including SIDs) is physically replicated; however, the destination SVM has a different local domain SID.
      • Local users/groups created on the destination SVM will have different SIDs, even if they share the same name.
      • Therefore, replicated ACLs referencing source SVM's local users/groups cannot be resolved on the destination SVM. Note: Creating a user with the same name on the destination SVM does NOT result in the same SID. SID = SVM domain SID + RID.
  • Volume-level SnapMirror replicates qtrees that exist in a volume, but sub-volume, qtree level SnapMirror is no longer supported 
  • To check the SACL on the destination volume, auditing must be enabled on the destination SVM; if not, run vserver audit create and vserver audit enable first.

Additional Information

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.