Dell EMC Avamar for VMware 19.7 User Guide

You can use Avamar to seamlessly deploy and manage VMware workloads across all VMware on-premises and AWS environments.

Consider the following points:

• VMware vSphere 6.5 or greater is required.
• There is no network connection between the ESXi host and the Avamar proxy on VMware Cloud on AWS. A vCenter is required for communication.
• User privileges are limited on VMware Cloud on AWS.
• Supports virtual machines that reside in a workload service pool.
• Avamar Virtual Edition support for VMware tags with SSO service.

Prerequisites

Review the following item before you begin:

• If you use NSX-T, configure DNS to resolve to the internal IP address of the vCenter server. Click SDDC Management > Settings > vCenter FQDN and select the private vCenter IP address so that you can directly access the management network over the built-in firewall. Open TCP port 443 for the vCenter server in both the management gateway and the compute gateway. VMware KB article 70846 provides more information.

Limitations

The following features are not supported:

• Application consistent backup
• File-level restore from an image-level backup if using NSX-V. Note that this is not a limitation if using NSX-T.
• Proxy deployment manager. Proxies must be deployed manually.
• Instant access recovery of an image-level backup
• Emergency restores (image restore directly to an ESXi host, bypassing the vCenter).
• Image-level backups and restores using NBD, NBDSSL, or SAN transport mode. Only HotAdd is supported.
• Advanced policy-based data protection for MS-SQL using Avamar.
• Application-aware image backups for MS-SQL and MS-Exchange.
• Image backup and restore when the data center is under a folder.
• Data exclusion
• Proxy appliance that is configured with dual-stack or IPv6-only.
• Restore to new vApp.
• IPV6

Workarounds

• If you use NSX-T and perform an image restore with Select Post Restore Options set to Power on VM with NICs enabled, the VM network adapter may not connect. To work around this limitation without restarting the VM:

  1. Right-click the VM and select Edit Settings > Network adapter.
  2. Change the network to VM Network.
  3. Click Apply.
  4. Click Edit Settings > Network adapter.
  5. Change the network to NSX-T Network.
  6. Click Connect.