KB ID: | 2414 |
Product: | Veeam Backup & Replication |
Version: | 10 |
Published: | 2017-12-14 |
Last Modified: | 2020-10-26 |
VMware Cloud on AWS and VMware Cloud on Dell EMC are vSphere environments running on AWS and Dell EMC hardware, that needs some specific preparation to allow Veeam Backup & Replication v10 or newer to work with it. Besides the below-listed preparation and limitations, you can interact with it within Backup & Replication like any other vSphere environment to backup, restore and replicate VM workloads.
Some of VMware features and permissions are not granted by default at the start of these VMware offerings. Thus, some depending Veeam Backup & Replication features will be limited or not operating. Depending on VMware update releases, the situation may change and the features from the table below may become available. Please contact your VMware administrator for timely update.
The Veeam Backup and Replication Server and Veeam proxy server should be connected to the VMware vCenter using HTTPS through TCP port 443. At VMware Cloud on AWS/DellEMC there is no need to open ports to the ESXi hosts itself. As the vCenter Server is by design of VMware Cloud on AWS/DellEMC on another network (Management Network), you need to configure one of the following 3 options:
Go to your SDDC Management – Settings – vCenter FQDN and select the Private vCenter IP address.
Hint: If you configure the vCenter DNS record for the internal IP address, you will lose VMC connection from Backup and Replication Server outside of VMC. You can use the local hosts file or any other DNS method to resolve the vCenter FQDN with the public IP address on the Veeam Server outside of VMC. Optionally, use the Public IP address for the VMC internal and external Veeam Server.
On the Management Network
On the Compute Gateway
Add vCenter to the Veeam console as described here:
https://helpcenter.veeam.com/docs/backup/vsphere/add_vmware_server.html?ver=95
Create a vCenter User with required rights (Active Directory linked mode) described here, or use the cloudadmin@vmc.local user.
When adding a vCenter server, specify the fully qualified domain name (FQDN) that ends with vmwarevmc.com or vmc.vmware.com (depending on the URL shown in the VMC interface for the vCenter).
For any VMware Cloud on AWS/DellEMC SDDC Cluster, roll out at least one Veeam Proxy Server to be able to process HotAdd / Virtual Appliance Backup Mode. The Backup & Replication itself can be used when installed at the SDDC Cluster (Proxy preinstalled). Please look at the Veeam documentation for details: https://helpcenter.veeam.com/docs/backup/vsphere/add_vmware_proxy.html?ver=95
Veeam Linux based Proxy Server can not be used with VMware Cloud on AWS/DellEMC as they do not enable specific mandatory VMware VDDK settings.
VMware Cloud on AWS/DellEMC has only one accessible vSAN disk. It would not make sense to use that disk for production workloads and backups. An external Backup device needs to be added. Depending on the use case there are several ways to achieve this with different economic factors. For VMware Cloud on DellEMC a Windows or Linux Server plus storage on a separate on-premises environment can be used. Please find below an example of an Amazon S3 EC2 Linux Server (e.g. EC2 C4 Server with EBS ST1 storage) used as a backup target over the VMware Cloud on AWS integrated ENI network connection.
To connect the EC2 Server(s) used as Veeam Repositories the following Firewall configuration is needed:
On the Compute Network:
Open TCP 22 (SSH) port from Veeam Backup server and Veeam proxy server to the Amazon VPC where the EC2 Server was installed. You can as well define the exact IP addresses of the repository server as Destination.
Open TCP 2500-5000 ports for Veeam Data Transport in both directions for same servers. It is recommended to use the VMware Cloud on AWS/DellEMC integrated high throughput/low latency ENI network connection to avoid any traffic costs.
It is suggested to create a backup copy to an additional place. Depending on the use case there are several ways to achieve this with different economic factors. Among other ways the following technologies can be used:
Additional Scenarios
VMware internal monitoring reports access violations to ESXi host hardware sensors when Veeam ONE is used.
Contact support to obtain registry key fix.
There is no option to select a network at Veeam “Entire VM” restore to a new VM name wizard when VMware Cloud on AWS is used with VMware NSX-t.
To solve the issue upgrade to Veeam Backup & Replication v10.
Impossible to add the VMware Cloud on AWS/DellEMC 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. …”
When working with Restore or VM Replication wizard, users may face some issues accessing VMware Cloud on AWS/DellEMC 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:
Problem
Backup & Replication stop working after VMware Cloud on AWS/DellEMC was automatically updated.
Some of the Backup & Replication Features are not working correctly because of limitations of the VMware Cloud on AWS/DellEMC environment (compared with a standard vSphere environment).
Affected Veeam Feature | Limitation | Workaround |
---|---|---|
Instant VM Recovery |
Currently, VMware Cloud on AWS (VMC) does not allow for NFS usage |
Use a combination of a Veeam backup job and replication job for proactive restore capabilities |
Other OS File Level Recovery |
Currently, VMC does not allow for NFS usage |
Start Linux File-Level Recovery from a backup copy on-premises |
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 Replication ReIP |
ReIP is not available on VMC |
|
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 |
Replication (where EC2-based repository is used to store replica metadata) | Due to lack of permissions, the repository Data Mover is not able to connect to the Veeam Server | Enable "Run server on this side" option for the repository. For Windows repositories it can be found under Ports configuration, for Linux - under Advanced settings in the server configuration wizard. |
See also:
VMware Cloud on AWS and Veeam – VMware KB
VMware Cloud on AWS SDDC – VMware Compatibility Guide Listing
KB ID: | 2414 |
Product: | Veeam Backup & Replication |
Version: | 10 |
Published: | 2017-12-14 |
Last Modified: | 2020-10-26 |