Isilon SmartLock fixed content device
A Content Platform Engine fixed storage area can use Isilon SmartLock as the fixed content device for storing content element files. The content can belong to documents from different object stores. In addition, different Content Cortex domains can access the same fixed content device.
The Content Platform Engine component that migrates the content element files to the Isilon SmartLock device is the fixed content provider. When you check in an object, the fixed content provider stores each content element of that object as a separate file on the SmartLock device, as if the device were a standard file system.
The content files on the Isilon SmartLock device are stored in a directory tree. This directory tree stores content files in a manner similar to a Content Platform Engine file storage area. When you create the fixed content device, you select a structure for the directory tree. If certificate validation is enabled on the Isilon fixed content device, the structure is created when you create the fixed storage device. Note that creating a large structure can take a long time. If certificate validation is not enabled, the directories are created as needed when content is added to the Isilon fixed content device.
- The SmartLock directory must be used in both nonaligned and aligned storage modes.
- Unless the configuration is compatible with Content Platform Engine, setting the SmartLock directory with minimum, maximum, or default retention settings is not suggested.
- Overriding the retention date can prevent Content Platform Engine from being able to remove the data that was overwritten with the new WORM setting.
- Do not configure the SmartLock directory with the autocommit option. This setting unexpectedly commits data to the WORM state.
- When the SmartLock directory is configured with the privileged delete option, Content Platform Engine cannot recover data that was unexpectedly deleted through use of the command-line interface.