The NetApp Snaplock device can operate in aligned or unaligned retention mode.
Retention is controlled by both the Content Platform Engine and the NetApp Snaplock fixed content device.
The following table compares the Content Platform Engine object retention setting for an object with the corresponding NetApp Snaplock retention setting that is applied to the object content.
Content Platform Engine object retention setting | NetApp Snaplock object content retention setting |
---|---|
Not set | The object content is not committed to WORM. This differs from using a zero length retention period in legacy retention mode. In that case, the object content is committed to WORM and the retention date is set to the current date and time of the Content Platform Engine server. The retention date is subject to the minimum and maximum values allowed by the NetApp Snaplock volume. |
Permanent | The retention setting is set to the maximum setting permitted by the NetApp Snaplock volume. |
Indefinite | The NetApp Snaplock device does not support the indefinite retention setting. The request to set the retention setting to indefinite is rejected. |
Date value | The retention setting is set to a specific date and time value within the minimum and maximum values allowed by the NetApp Snaplock volume. A request outside this range is rejected. |
Retention is enforced by Content Platform Engine and is not applied to content stored on the NetApp Snaplock device. Object content created on the NetApp Snaplock device is not committed to WORM. For this reason, object content is not subject to the minimum and maximum retention values allowed for the NetApp Snaplock volume. Although the object retention setting on the Content Platform Engine can be set to any valid value, the retention setting for the corresponding object content is not changed on the fixed content device.