Data is deleted on Cloud storage even when Object lock and WORM are enabled
Use case:
I have enabled Object lock on the Cloud storage bucket (Hitachi Content Platform for Cloud Scale (S3)).
Enabled WORM on Commvault and set the retention for the storage policy.
Result:
Once the data is backed up I am able to delete the data manually in the Hitachi Content Platform for Cloud Scale (S3) bucket.
Does Commvault does not leverage Object lock ?
Also Can we enable Object lock on Hitachi Content Platform for Cloud Scale (HCPCS) and WORM on Commvault or its Either or case.
Page 1 / 1
Hello @Lahari
Did you enable WORM via the workflow or manually? If the workflow, did it fail when it ran? If manually, did you configure the Object Lock on the storage side or just within Commvault?
The workflow does support enabling Object Lock for HCP storage so it should have set the policy on the HCP side. The Settings within Commvault only prevent changes to the configuration or deleting jobs via the GUI. The Storage Object Lock is what actually prevents deletion of data physcially.
Thank you, Collin
Hello @Collin Harper We enabled WORM manually as Workflow is not supported in 11.30 version.
If manually, did you configure the Object Lock on the storage side or just within Commvault?
We configured Object lock on Storage side and WORM within Commvault.
Could you let us know how to implement storage object lock feature via commvault.
According to the documentation Manual process shall also set bucket level retention but we are able to delete the data inside our buckets.
Could you please clarify on above statement?
Hello @Lahari
Due to changes in 11.30 with how WORM Storage is managed the workflow cannot be used to set up WORM. Additionally setting object lock manually on S3 storage and WORM Copy in Commvault will not set up the Object Locking either.
To enable CommVault WORM Storage Lock and Compliance Lock please follow this documentation: