Commvault | Zata Docs

Commvault can write backups to a Zata bucket. You add the bucket as S3-compatible cloud storage in the Commvault Command Center, then point a plan (storage policy) at it.

Before you start

A bucket for the backups. See Create a bucket.
An access key from the same region as the bucket. It needs list, read, write and delete access to the bucket. See Access keys.
Access to the Commvault Command Center.

Connection settings

Setting	Value
Storage type	S3-compatible storage
Service host (endpoint)	`idr01.zata.ai` for Indore, `bom01.zata.ai` for Mumbai
Access key / Secret key	From Access Keys in the Zata console. The key must be from the same region as the bucket.
Bucket	Your bucket name, for example `my-bucket`

Set up Commvault

Add cloud storage

Sign in to the Commvault Command Center, open the Storage section, and add a new cloud storage library. Choose S3-compatible storage as the type.

Enter the Zata details

Enter the endpoint, bucket, access key and secret key from the table above, and save. Commvault checks the connection.

Use it in a plan

Create or edit a plan (storage policy) so that its backup destination is the Zata storage, and set the retention you need.

Test it

Run a small backup job with that plan, check that data appears in your bucket in the Zata console, then restore one file to confirm the backup can be recovered.

Troubleshooting

Problem	Fix
Signature or authentication error	Copy the keys again from Access Keys. The key must be from the same region as the endpoint.
Bucket not found	Check that the bucket exists in that region and that the key can use it.
Error about the storage class	Zata has one storage class. Choose the standard class or leave the setting empty.
Connection timeout	Allow outbound HTTPS (port 443) from the MediaAgent to the Zata endpoint.

For other errors, see Access denied and Endpoint and region.