Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
VMware Cloud on AWS is an integrated cloud offering developed by AWS and VMware. It requires specific preparation to enable Veeam Backup & Replication to function with it. Apart from the preparation process and the limitations mentioned at the end of this article, you can interact with VMware Cloud on AWS using Veeam Backup & Replication, just as you would with any other vSphere environment, to back up, restore, and replicate VM workloads. However, not all VMware features and permissions are granted by default with these VMware Cloud offerings. Consequently, some Veeam Backup & Replication features may be limited or non-functional. Depending on updates released by VMware, this situation may change, and the features listed in the table below may become available. Please consult with your VMware administrator for timely updates.
Implementation Step 1 - Prepare the Veeam Backup Server If you do not have a Veeam Backup Server, use a new Windows Server and install the latest version of Veeam Backup & Replication. The Server can run within any VMware Cloud on AWS SDDC, the ENI-connected AWS environment, or on-premises datacenter environments if the network connection to the VMC vCenter/Veeam Servers and potentially the VMs (for Guest processing) is possible. Add DNS network settings so that the Veeam Backup Server can resolve Internet DNS names to resolve the fully qualified domain name of the VMC vCenter server. Check the below information carefully for any known limitations and configuration steps before you proceed.
VMware internal monitoring reports access violations to ESXi host hardware sensors when Veeam ONE is used. Contact support to obtain registry vale to correct this. When performing an Entire VM restore, using the Restore to a new location mode, to VMware Cloud on AWS with VMware NSX-t, the Network tab's Networks... selector is empty. To solve the issue, upgrade to Veeam Backup & Replication 11.0.0.837 P20210525 or later. Impossible to add the VMware Cloud on AWS vCenter server to the managed server. VMs within this vCenter are not visible in the list of VMs, or an Error is displayed in the Veeam Jobs “Processing SQL Error: File does not exist or locked. …” Create a vCenter User with the required rights (Active Directory linked mode) described here, or use the cloudadmin@vmc.local user. When adding the vCenter server, specify the fully qualified domain name (FQDN) that ends with either vmwarevmc.com or vmc.vmware.com, depending on the URL displayed in the VMC interface for the vCenter. When working with the Restore or VM Replication wizard, users may face 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 Veeam Backup & Replication stops working after VMware Cloud on AWS is automatically updated. Please check this article for the minimum required Veeam Backup & Replication version or Patches. For customers with socket-based licensing, ensure that the automatically generated new ESXi hosts can receive Veeam licenses. Potentially, older ESXi hosts need to be revoked from the license. We recommend using Veeam Universal Licensing to avoid any license-specific issues with VMware Cloud on AWS. Some of the Veeam Backup & Replication Features are not working correctly because of limitations of the VMware Cloud on AWS environments (compared with a standard vSphere environment).
See also: Veeam Backup & Replication 11 on VMware Cloud on AWS (85239) VMware Cloud on AWS SDDC – VMware Compatibility Guide Listing