Some of VMware features and permissions are not granted by default at the start of VMware Cloud on AWS (VMC). Thus, some depending Veeam Backup & Replication features will be limited or not operating. Depending on VMware update releases for VMware Cloud on AWS, the situation may change and the features from the table below may become available. Please contact your VMware administrator for timely update.
|Affected Veeam Feature||Limitation||Workaround|
Instant VM Recovery
Currently, VMware Cloud on AWS (VMC) does not allow for NFS usage
Use IVMR from a backup copy on-premises.
Other OS File Level Recovery
Currently, VMC does not allow for NFS
Start Linux File-Level Recovery from a backup copy on-premises
Quick Migration cannot migrate VMs to VMC if they are running
Use Veeam Replication and permanent failover to achieve similar functionality
SureBackup, Sure Replica, OnDemand Labs, Virtual Lab
Currently, VMC does not allow NFS and network manipulation
As for SureReplica, you can perform it if the replication target is a non-VMC vSphere environment (e.g., replicate VM from VMC to on-premises)
VM Guest Interaction and Windows File Restore by VIX or WebService API
Currently, VMC does not allow usage of VMware Webservice API
If you want to perform Veeam Guest processing or Windows File-Level Recovery, then connect to a VM over the network from Veeam Backup & Replication
VM Replication ReIP
ReIP is not available on VMC
Windows Dynamic disks are not supported
Currently, VMC does not allow to process dynamic disks at Hot-Add (Virtual Appliance mode) backup
VMware will provide a hotfix for this soon
Non-Unicode VM names
Currently, VMC does not allow non-Unicode characters for VM names within their APIs used ad VMC
VM Replication based File Level Recovery
Use file restore from backups or use a VM replica on a non VMC environment to start the File recovery
Impossible to add the VMware Cloud on AWS vCenter server to the managed server, or VMs within this vCenter are not visible in the list of VMs.
- Create a vCenter User with required rights (Active Directory linked mode) described here, or use the firstname.lastname@example.org user.
- When adding a vCenter server, specify the fully qualified domain name (FQDN) that ends with vmc.vmware.com.
When working with Restore or VM Replication wizard, users may face some issues accessing VMware Cloud on AWS vCenter server.
By design, VMware does not provide customers access to the background infrastructure and used datastores.
For proper operation, you can select the specific areas marked as “Workload” or “Compute”. Avoid using the non-accessible areas, for example:
- vsanDatastore datastore
- Management VMs folder
- Mgmt-ResourcePool resource pool
VMware Cloud on AWS Firewall ConfigurationThe Veeam Backup and Replication Server and Veeam proxy server should be connnected to the VMware vCenter using HTTPS through TCP port 443. At VMware Cloud on AWS there is no need to open ports to the ESXi hosts itself.
All Veeam servers residing within VMware Cloud on AWS need to communicate with the Linux Repository Server on AWS via ports TCP 22 and TCP 2500-5000 open for VMware Cloud (this will be a transport ports in both directions).