Shredding service

Shredding, also called secure deletion, is the process of overwriting the places where all the copies of the data, secondary metadata, and custom metadata for an object were stored in such a way that the object cannot be reconstructed.

The Shredding service shreds deleted objects that are marked for shredding. If the object is a multipart object, the Shredding service shreds each part of the object. The Shredding service also shreds unused parts of multipart uploads that were initiated in namespaces where the default shred setting is true.

The primary metadata for a shredded object is deleted from HCP after all of these events have happened:

The object is removed from the metadata query engine index, if applicable.

The object deletion is replicated, if applicable.

For old versions of objects, the version is pruned or purged.

The deletion record for the object is deleted from the transaction log. If the Garbage Collection service is configured never to delete deletion records from the transaction log, the primary metadata for the object remains in the system indefinitely.

For information about the transaction log, see Transaction log cleanup.

The shredding policy for each object determines whether that object is shredded. For information about the shredding policy, see Shredding policy.

Note: The Shredding service does not shred object data if:

The data is stored in a namespace that uses a service plan that has S Series storage set as the ingest tier. For information about ingest tiers, see Choose the ingest tier.

The data is stored on extended storage. For information about extended storage, see Storage for HCP systems.

© 2015, 2020 Hitachi Vantara LLC. All rights reserved.