Cfs-Grab - Dell DX6000 Deployment Manual

Dell DX Object Storage – File Gateway Deployment Guide
• --lifepoint=#: The number of the lifepoint to affect with a particular action. This number
does not indicate 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 Dell DX Object 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 CFS-legal mount point would be implemented as follows:
# cfs-admin policy --add --reps=2 --del=no --span=1y \
--lifepoint=1 /mnt/CFS-legal
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/CFS-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:
# cfs-admin policy --modify --span=2y --lifepoint=1 /mnt/CFS-legal
Finally, to delete a policy, the 'delete' action can be executed as follows by specifying which lifepoint
to delete. If the specified lifepoint does not exist, the system will return a 'No such lifepoint' error. If
more than one lifepoint is in effect, you should be sure to validate the remaining lifepoints printed
after the delete to ensure the end-to-end lifecycle policy is as intended. If you delete a lifepoint in the
middle of a series of lifepoints, you may need to adjust other lifepoints to rearrange their order.
# cfs-admin policy --delete --lifepoint=1 /mnt/CFS-legal

CFS-Grab

CFS-grab is a command-line tool that collects runtime environment information to assist with support
ticket submissions. From a command line, logged in as the root user, type CFS-grab to utilize the tool.
Page 66