Using device holds

Device holds

Device holds prevent content deletion or modification until the hold is released. A typical use case is during litigation when content must be protected from deletion.

After device holds are enabled on a fixed storage area, Content Platform Engine places a device hold on any new content that is created in that fixed storage area. Holds are not placed on content that was created before you enabled the device holds feature.

Device support and restrictions

Content Platform Engine supports the device holds feature for selected fixed content devices. For Content Platform Engine to enable the device holds feature for a fixed storage area, the associated fixed content device must support device holds.

Content Platform Engine supports device holds for the following fixed content devices with the following restrictions and notes:

Hitachi Content Platform

• Privileged data access permissions are required.
• A device hold on Hitachi stored content prevents privileged users from deleting the content.

IBM Cloud® Object Storage

• The IBM Cloud Object Storage bucket must be protection (compliance) enabled.
• The IBM Cloud Object Storage account must have the access rights to add, list, and remove legal holds on objects.

Amazon S3

• The S3 bucket must be object lock enabled at creation time.
• The S3 account must have the access rights to add, list, and remove legal holds on objects.

Centera/ECS (CAS API)

• The Centera/ECS server must hold the Advanced Retention Management license and support retention hold feature.

For the most recent list of supported devices, see Software Product Compatibility Report.

Enabling the device hold capability

In Administration Console for Content Platform Engine, enable device holds for a storage area by clicking Apply Device Holds when you create a new or update an existing fixed storage area.