Special Considerations For Md3200I Spooler; File Revisions And Dell Dx Object Storage File Deletion; Dell Dx Object Storage Metadata And Policies - Dell DX6000 Deployment Manual

Dell DX Object Storage – File Gateway Deployment Guide

Special Considerations for MD3200i Spooler

When a CFS node using MD3200i external spooler storage is being shut down, the following procedure
must be used to avoid a possible hang during shutdown. If these steps are not followed, the system may
hang and need to be powered down or reset manually.
1. Unmount any spool directories mounted from the MD3200i.
# umount /var/cache/cns
# umount /var/spool/cfs/<spool1>
And so forth for any other spools
2. Log out iscsi sessions.
# iscsiadm –m node –u
3. Flush multipath cache:
# multipath –F
4. Shut down or restart the system.

File Revisions and Dell DX Object Storage File Deletion

Each modification to a file stored in CFS creates a new object in Dell DX Object Storage, with CNS
keeping track of the modification revision that is current for each file. Old revisions are quickly deleted
from the Dell DX Object Storage via a background garbage collection process. Files that are explicitly
deleted from the CFS mount are removed from Dell DX Object Storage via the same background
process. CFS 2.0 does not support revision history for files.

Dell DX Object Storage Metadata and Policies

Along with the standard file system attributes that are associated with a file stored in CFS, additional
metadata and lifecycle policies can be stored with files when they are stored in Dell DX Object
Storage. This metadata can assist with storage management and data movement through various life
cycles. All metadata and policies are specific to the Dell DX Object Storage are not visible from within
the file system.
Metadata and policies are specific to each mount point so it is advisable to configure separate mount
points in cases where distinct metadata values would be helpful. For instance, to distribute content
based on the branch office a file originated from, set up a mount point for each branch office and add
a custom metadata attribute with the branch office name that would be added to each file stored.
Similarly, to store more replicas of files needed by the Media department due to frequent read
activity, setup a separate mount point for the Media department with a Lifecycle policy for additional
Page 63