Installation manual

Adding a Managed Volume
Adding a Share
9-34 CLI Storage-Management Guide
Allowing File Renames in Import
If the share allows file renames, the volume renames its colliding files as specified by
the
modify command.
import rename-files
This is the default setting.
For example, the following command sequence returns the ‘bills’ share to its default:
bstnA6k(gbl)# namespace wwmed
bstnA6k(gbl-ns[wwmed])# volume /acct
bstnA6k(gbl-ns-vol[wwmed~/acct])# share bills
bstnA6k(gbl-ns-vol-shr[wwmed~/acct~bills])# import rename-files
bstnA6k(gbl-ns-vol-shr[wwmed~/acct~bills])# ...
Enabling SID Translation for a Share (CIFS)
This section only applies to a share that supports CIFS; skip to the next section if this
share is in an NFS-only namespace.
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 you
aggregate shares from these filers into a single volume, some files tagged for
local-group X are likely to migrate to another filer, which does not recognize the SID
for that group (SID X). This invalidates any Access Control Entries (ACEs) with SID
X while the file resides on that filer; members of group X lose their privileges. To
resolve this problem, you must first prepare all of the filers before you aggregate them
into a namespace volume. This was discussed earlier; recall “Supporting Filers with
Local Groups” on page 9-18.
Once the filers are prepared, you can use the CLI to tag their shares for SID
translation. This causes the volume to translate SIDs for all files that migrate to or
from these shares: it finds the group name at the source share (such as “nurses” on
filer B), then looks up the SID for that group name (“nurses”) at the destination share
(on filer A).