Deleting Large Buckets
In Zata, buckets that contain a large number of objects or object versions cannot always be deleted directly through the user interface or by simple API calls. Deleting a bucket that contains very large amounts of data is not always supported as a simple direct action due to how distributed object storage systems operate. To ensure a safe and reliable deletion, a controlled process is required. Process
Submit a Support Ticket If you need to delete a bucket that contains a large number of objects or object versions, open a support ticket and include the following details:
Full bucket name
Approximate number of objects stored in the bucket
Any relevant context regarding the bucket’s contents or usage
Support Team Verification The Zata support team will review the request to confirm that:
The requester has the required permissions to delete the bucket
There are no operational dependencies or regulatory constraints that would prevent deletion
Deletion Execution and Timeline Confirmation After verification, the support team will execute the deletion using backend procedures designed to handle high object counts efficiently. Based on the bucket size and object volume, the team will also communicate the estimated time required to complete the deletion.
Summary To delete a large bucket in Zata:
Raise a support ticket with the required bucket details
The Zata support team will verify the request and perform the deletion
The estimated time required for completion will be shared after verification
This approach ensures that large bucket deletions are handled in a controlled, secure, and reliable manner.
Last updated