Avamar image backup and restore for VMware Cloud on AWS best practices
Consider the following best practices when using Avamar to protect virtual machines running in VMware Cloud on AWS.
When deploying or configuring the Avamar server or proxy, ensure that you specify the DNS server IP address that points to the internal DNS server running in the vCenter inventory.
Ensure that both forward and reverse lookup entries in the internal DNS server are in place for all the required components, such as the Avamar Server, Avamar proxy appliance, and Data Domain Virtual Edition (DDVE).
If using NSX-T, configure the DNS to resolve to the internal IP address of the vCenter server. Navigate to
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. Additionally, ensure that you open TCP port 443 of the vCenter server in both the management gateway and the compute gateway.
Also, using NSX-T for file-level restore operations requires you to update the
axionfs.cmd file on the proxy appliances with the IPv4 address of the Avamar server. After you register and activate the Avamar proxy appliances in the Avamar server, log into each of the Avamar proxy appliances as
root, and then open the
/usr/local/avamar/var/axionfs.cmd file in a UNIX text editor. Within the file, locate the
--server entry key and update the corresponding value to the IPv4 address of the Avamar server. For example,
--server=192.168.2.150.
Add the vCenter server to the Avamar server by using one of the following options:
Public FQDN of the vCenter server
Public IP address of the vCenter server.
It is recommended that you use the FQDN.
When adding the vCenter server to the Avamar server, specify the login credentials for the cloudadmin user.
When accessing the
AUI by using vCenter authentication, add the following parameter in the
/usr/local/avamar/var/mc/server_data/prefs/application-production.properties file, and then restart the mcs service:
vmc.vcenters=VMware Cloud vCenter FQDN
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\