Deleting Large Buckets

Deleting Large Buckets in Zata

In Zata, buckets that contain a very large number of objects or multiple object versions cannot always be deleted directly through the user interface or by simple API calls. Due to the nature of distributed object storage systems, deleting buckets with large volumes of data requires a controlled and managed process to ensure safety, reliability, and system stability.

Process

1. Submit a Support Ticket: If you need to delete a bucket that contains a large number of objects or object versions, raise a support ticket and provide the following information:

• Full bucket name

• Approximate number of objects stored in the bucket

• Any relevant details regarding the bucket’s contents or usage

2. Support Team Verification: The Zata support team will review the request to verify that:

• The requester has the required permissions to delete the bucket

• There are no operational dependencies or regulatory or compliance constraints preventing deletion

3. Deletion Execution and Timeline Confirmation: After successful verification, the support team will perform the deletion using backend procedures optimized to handle large object counts efficiently. Based on the size of the bucket and the volume of objects, the team will communicate the estimated time required to complete the deletion.

Summary

To delete a large bucket in Zata:

• Raise a support ticket with all required bucket details

• The Zata support team will verify the request and carry out the deletion

• The estimated completion time will be shared after verification

This controlled approach ensures that large bucket deletions are handled in a secure, reliable, and well-governed manner.