Best practice for migrating AWS Cloud Library from S3 Standard-IA to S3 Standard + Secondary Copy in another AWS Region

Team,

I’m looking for some guidance on the best approach for redesigning our Commvault AWS cloud library.

Current environment

* Commvault version: 11.40
* Primary AWS Region: us-east-1 (N. Virginia)
* Current storage class: S3 Standard-IA
* We have 2 AWS accounts configured for Commvault.
* Across the accounts, we currently have 2 and 5 S3 buckets, mainly separated between Prod and Non-Prod.
* Only a few Storage Policies currently have an Auxiliary Copy to an air-gapped location.
* We already have DDBs associated with the existing cloud libraries.

Planned design

We are planning to change the architecture to:

Primary Copy

* Region: us-east-1
* S3 Storage Class: S3 Standard
* Retention: 2–3 days
* Intended for frequent restores and Commvault data-read operations.

Secondary Copy

* Region: us-east-2 (Ohio)
* S3 Storage Class: S3 Standard-IA
* Retention: up to 30 days
* Intended as the secondary copy.

The proposed flow is:

Backup → S3 Standard (us-east-1) → Auxiliary Copy → S3 Standard-IA (us-east-2)

Questions

1. Existing buckets or new buckets?

Can we continue using the existing S3 buckets in us-east-1 and change/use them with S3 Standard, or is it recommended to create new buckets for the new primary cloud library?

1. Existing DDB or new DDB?

Can the existing DDBs continue to be used with the new S3 Standard primary configuration?

Or should we create new DDBs?

What is the recommended Commvault best practice when changing the cloud library/storage design?

2.Media Agents and DDB for the secondary copy

For the new us-east-2 S3 Standard-IA secondary copy, do we need dedicated Media Agents and DDBs?

Or can we use the existing Media Agents in us-east-1 and configure a new DDB for the secondary copy?

Are there any specific Commvault considerations for cross-region Auxiliary Copy?

Any recommendations from Commvault experts would be greatly appreciated.

Thanks!