Dear Team,
Our VMware backups for AWS VMs are running successfully in Metallic, with an AWS S3 bucket as the primary (disk library) and a secondary copy to Metallic Cold Storage—no issues observed.
We now have similar VMs in Azure and would like to configure backups in Metallic as follows:
-
Primary copy: AWS S3 bucket (disk library)
-
Secondary copy: Metallic Cold Storage
-
Licensing: We have sufficient Metallic licenses for these VMs.
Questions / Request
-
Can we use the existing S3 bucket as the primary copy for the Azure VMs as well? If this isn’t recommended, please advise the best practice (e.g., dedicated bucket, separate prefixes, or segregated retention/encryption).
-
Please confirm prerequisites and constraints—cross-cloud connectivity (Azure → AWS), firewall rules, IAM/KMS requirements, bandwidth/egress considerations, and any incremental cost impacts.
-
If feasible, kindly share an implementation plan and a proposed change window.
Regards,
Mani D
