Installation manual

Shadowing a Volume
Configuring a Shadow-Copy Rule (Source Switch)
CLI Storage-Management Guide 15-15
For example, the following command sequence disables reporting for the rule,
“buHome:”
bstnA6k(gbl)# namespace archives
bstnA6k(gbl-ns[archives])# volume /home
bstnA6k(gbl-ns-vol[archives~/home])# shadow-copy-rule buHome
bstnA6k(gbl-ns-vol-shdwcp[archives~/home~buHome])# no report
bstnA6k(gbl-ns-vol-shdwcp[archives~/home~buHome])# ...
Supporting Local Groups (CIFS)
A Windows filer can support Global Groups, which are managed by Domain
Controllers, and/or Local Groups, which are unique to the filer. Local groups have
their own Security IDs (SIDs), unknown to any other Windows machine. When filers
behind a source volume use local groups, they have SIDs that are unrecognized at the
target volume’s filers. This invalidates any Access Control Entries (ACEs) with these
SIDs on the shadow volume; members of the local groups lose their privileges on the
shadow volume. To resolve this problem, you must first prepare all of the target filers
before you enable the shadow-copy rule:
• all local-group and local-user names must be configured on all filers behind both
volumes, and
• all groups must contain the same users on those filers.
For example, if filers behind the source volume have a local group named “doctors,”
you must add a new “doctors” local group to all filers behind the target volume. The
membership of these groups must match at all of the filers. This preparation is
required so that all doctors can access the files at the source and shadow volumes.
This problem is similar for a volume with multiple CIFS filers behind it; recall
“Supporting Filers with Local Groups” on page 9-18.
If the source and shadow volumes are in two different Windows domains, SID
translation may require customized preparation. Contact Acopia Support before using
this command for inter-domain shadow-copy rules.