
Shadowing a Volume
Configuring a Shadow-Copy Rule (Source Switch)
CLI Storage-Management Guide 15-17
bstnA6k(gbl-ns-vol-shdwcp[insur~/claims~insurDR])# ...
Disabling SID Translation
You can stop the shadow-copy rule from translating SIDs. This implies one of two
scenarios:
• none of the filers behind the source volume use local groups, or
• clients do not require read access at the shadow volume.
This is the default for shadow-copy rules. Use
no sid-translation to stop SID
translation:
no sid-translation
For example, the following command sequence disables SID translation for the
“insurDR” rule:
bstnA6k(gbl)# namespace insur
bstnA6k(gbl-ns[insur])# volume /claims
bstnA6k(gbl-ns-vol[insur~/claims])# shadow-copy-rule insurDR
bstnA6k(gbl-ns-vol-shdwcp[insur~/claims~insurDR])# no sid-translation
bstnA6k(gbl-ns-vol-shdwcp[insur~/claims~insurDR])# ...
Copying Files Opened through CIFS
By default, the shadow-copy rule opens each file for read-only access, thus blocking
any other applications from writing to the file. This ensures the integrity of the copied
file. However, the back-end filer does not allow the shadow-copy rule to open the file
for read-only access if any other application already has the file open for writes, or for
an impending deletion. The shadow-copy rule cannot copy these open files if they are
Some filer servers can be configured to return an error for an invalid SID
(STATUS_INVALID_SID, STATUS_INVALID_OWNER, and/or
STATUS_INVALID_PRIMARY_GROUP) but accept the file or directory anyway. You
may want to discount these errors from these particular file servers. You can set this up
for each errant file server from gbl-ns-vol-shr mode, using the
sid-translation
ignore-sid-errors
command (recall “Ignoring SID Errors from the Filer (CIFS)” on
page 9-36).
Kommentare zu diesen Handbüchern