[VMC on AWS] Using third-party backup or replication solutions with VMware Cloud on AWS

Products

• VMware Cloud on AWS
• VMware Cloud on Dell EMC

Issue/Introduction

To better understand the recommended or required configurations for most third-party backup and replication solutions when using VMC on AWS.

Symptoms:
Attempting to use a custom role with a third-party backup or replication solution with VMware Cloud on AWS (VMC on AWS) does not work. The custom role cannot be created or assigned to users or groups.

Resolution

When working with most third-party backup and replication solutions outside of VMC on AWS, a custom account is required to be created. These vendors require the "[email protected]" account to be used when working with VMC on AWS. Each vendor documents the recommended or required configuration needed when backing up or replicating workloads within VMC on AWS. While not a full list, below are the most common third-party solutions seen. 

• Veeam
• Avamar (starting on page 129)
• Druva Phoenix for VMware Cloud on AWS
• PowerProtect Data Manager on VMC
• Rubrik Cloud Data Management for VMware Cloud
• IBM Spectrum Protect for VMware Cloud on AWS Virtual Environments
• Metallic Backup as a Service for VMware Cloud on AWS
• Cohesity Platform for Data Protection of VMware Cloud on AWS
• Dell EMC PowerProtect for VMware Cloud on AWS

Note: The above articles are not VMware articles and are not managed or updated by VMware. If there are questions regarding the configuration process documented in these articles, please reach out to the specific vendor. 

Additional Information

VMware Knowledge Base articles covering common third-party backup and replication solutions:
Dell EMC Avamar 18.1 for VMware Cloud on AWS
Certified backup solutions on VMware Cloud on AWS: Commvault Version 11

Impact/Risks:
When configuring third-party backup or replication solutions with VMC on AWS, there may be feature limitations. These limitations will be included in the vendor documentation.