Object Lock, S3, and Versions
This topic provides information about the use of Object Lock with ActiveScale or AWS in conjunction with StorNext.
-
StorNext does not fully support Object Lock or Object versions in an object store such as ActiveScale or AWS cloud.
-
You can enable the S3 Object Lock feature in AWS or the object store without StorNext being aware of it.
-
S3 Object Lock is not controlled by StorNext; you must understand the implications outlined below.
-
With AWS S3 support for Object Lock, if a retention period is configured with the Object Lock, then StorNext does not upload to the bucket. Quantum must confirm or deny this is an issue with ActiveScale.
How do deletes work with versions and behave without StorNext?
-
On an Amazon system, when you enable versioning, then a simple DELETE does not permanently delete an object. Instead, Amazon S3 inserts a delete marker in the bucket, and that marker becomes the current version of the object with a new ID.
-
When you try to GET an object whose current version is a delete marker, Amazon S3 behaves as though the object has been deleted (even though it has not been erased) and returns a 404 error (object not found). For more information, see Working with delete markers.
-
To delete a versioned object permanently, you must use DELETE Object versionId.
Note: StorNext does not issue a delete specifying the version ID, this is not supported in StorNext.
While the list above is specific to AWS, ActiveScale, and S3 compatible destinations only, contact Quantum Technical Support (see Contacting Quantum Support) to determine how it relates to Azure and Google.
Object Lock and versioning behavior implications if it is turned on for a bucket being managed by StorNext
-
If you configure a retention period with Object Lock, then StorNext does not upload to the bucket.
-
If you execute the fsclean command on a bucket with Object Lock enabled, then the command completes successfully, but any object is tagged with a delete marker and the object remains in the bucket either indefinitely or, if configured, until the retention period has expired.
-
Although a deleted version of an object might be found in the bucket, the fsclean process removes the metadata needed to reference the object and it is no longer accessible or recoverable by Storage Manager.
-
The fsobjimport command only imports the current version of an object found in a bucket. It does not import the previous version of an object or any object tagged with a delete marker.
