Acopia Networks 810-0044-00 Installationshandbuch PDF herunterladen (Seite 208)

100

101

Adding a Managed Volume

Allowing the Volume to Modify on Import

9-14 CLI Storage-Management Guide

Allowing Renames on Collision

An auto-sync job may discover a file that collides with another file in the volume (that

is, in another share). By default, this prevents the operation from synchronizing that

file; a managed volume cannot support two or more files whose path names collide.

To work around these collisions, you can configure the volume to rename these files

before using them. The volume uses the following pattern to rename the file:

filename_share-jobid.ext

where

filename is the file’s original name, without its extension (for example,

“zapFiles” from “zapFiles.exe”),

share is the name of the volume share (described below),

jobid is an integer identifying the job that synchronized the volume, and

.ext is the file’s original extension (for example, “.exe”), if there is one.

If there is more than one redundant file, an index is added:

filename_share-jobid-index.ext

where index is a number starting at 1.

This renaming convention is the same one that is used for file collisions on import

(recall “Allowing the Volume to Modify on Import” on page 9-9).

From gbl-ns-vol mode, use the

rename-files flag at the end of the auto sync files

command to allow the volume to rename any collision files:

auto sync files rename-files

For example, the following command sequence allows sync-file renames in the

“medarcv~/rcrds” volume:

bstnA6k(gbl)# namespace medarcv

bstnA6k(gbl-ns[medarcv])# volume /rcrds

bstnA6k(gbl-ns-vol[medarcv~/rcrds])# auto sync files rename-files

bstnA6k(gbl-ns-vol[medarcv~/rcrds])# ...

1 2 ... 203 204 205 206 207 208 209 210 211 212 213 ... 491 492

Kommentare zu diesen Handbüchern

Keine Kommentare

Acopia Networks 810-0044-00 Installationshandbuch Seite 208

Kommentare zu diesen Handbüchern