Configuring the WORM Storage Mode on Cloud Storage
Cloud storage vendors can support WORM functionality using one of the following methods:
- Vendors that support a WORM policy at the bucket level
To achieve WORM functionality for such vendors, the WORM policy has to be enabled at the bucket level in the Cloud storage vendor's interface. For example, vendors like Amazon Glacier using Vault Lock Policy, EMC ECS Storage and Microsoft Azure using Immutable Blob Storage functionality can configure the WORM policy.
As these WORM policies are usually based on number of days or months of retention from the time the data was written on the storage, make sure that the retention settings established at the Storage Policy Copy is higher than or equal to the bucket level retention established in the cloud. Otherwise some of the pruning operations might fail due to the WORM retention setting on the storage side. (For more information on establishing the retention rules, see Setting Up the Basic Retention Rule.)
- Vendors that support retention at the object level
To achieve WORM functionality on cloud storage vendors who support retention at object level, you can enable the Mark Archive files as Read-Only option from the Cloud Library Properties dialog box. Vendors like like Hitachi and Caringo storage support this function. (For more information on marking the archive files as read-only, see Configuring Files as Read-Only.)
Last modified: 1/24/2019 3:02:55 PM