- ページ 21

サーバー Dell DX6000GのPDF 設定・構成マニュアルをオンラインで閲覧またはダウンロードできます。Dell DX6000G 23 ページ。 Rack installation instructions — static rails
Dell DX6000G にも：ユーザーマニュアル (48 ページ), リリースノート (7 ページ), ラックの設置 (2 ページ), ラックの設置 (2 ページ)

ページを印刷する

# cfs-admin metadata --delete --name=Department --value=Legal /mnt/legal

3.6.2. DX Storage Lifecycle Policies

In addition to custom metadata, the 'cfs-admin policy' utility allows a root user to administer the

content storage constraint policy for newly created files that are ready to be stored in DX Storage

(last file close plus 5 seconds). To add a new policy to a mountpoint, the following command can be

executed:

$ sudo su -

# cfs-admin policy --add [action-options]<mount-root>

where <mount-root> is the full path for the CFS mountpoint to which the policy should be attached.

The available action-options for a policy are:

• --reps=# : The number of file replicas that should be created in DX Storage. Valid entries are

between 1 and 16.

• --del=yes|no: Whether or not the file should be deletable within DX Storage. Value can be either

"yes" or "no". Immutable DX Storage objects can not be deleted via the background CFS delete

cleanup process (garbage collection).

• --lifepoint=#: The number of the lifepoint to affect with a particular action. This number is not

indicative of the order in which a lifepoint will be considered but simply a naming mechanism to

distinguish one lifepoint from another. You can use the 'print' command to determine what lifepoint

number is associated with a particular policy.

• --span=TIME: When, measured from when the file is stored, the lifepoint will cease to be in effect,

specified as a number followed by the unit of measure where allowable units are: d = day, w =

week, m = month, y = year (e.g. "2y" for two years). This option should be omitted for lifepoints

that should not have an end date. There can be only one such lifepoint.

All times are measured from the date the file is created in DX Storage and are not relative to each

other when using multiple lifepoints. For instance a lifecycle policy that states a file should have

3 replicas for the first year and 2 replicas for a year after that would require two lifepoints: the first

with a span=1y and the second with a span=2y, representing the cumulative time from the point

the file was stored.

To provide a specific example, a single policy that set all files as not deletable with 2 replicas for one

year for the legal mountpoint would be implemented as follows:

# cfs-admin policy --add --reps=2 --del=no --span=1y

Confirmation of a policy will be printed at the end of every addition but you can view the policies in

effect at any time by using the print command, as follows:

# cfs-admin policy --print /mnt/legal

To modify an existing lifepoint, use the same action options detailed above for the 'add' command

and just include the change to the updated attribute. The lifepoint option is required with a modify

command to ensure the correct lifepoint is updated when more than one is in effect. If the specified

lifepoint does not exist, the system will return an 'IndexError'. Existing attributes not specified in

the modify command will remain the same as previously stored. For instance, to lengthen only the

span for the lifepoint set in the example above but leave the replica and delete policy the same, the

following command would be executed:

--lifepoint=1 /mnt/legal

Version 2.6

February 2011