Installation and configuration problems and solutions
Common installation and configuration problems and solutions are described below.
Problems adding vCenter Server as Avamar client
If you encounter problems adding a vCenter Server as an Avamar client, ensure that:
vCenter hostname, username, and password are correct.
Port 443 is open between the Avamar server and the vCenter.
If this step does not resolve the problem, turn off certificate authentication for all vCenter-to-Avamar MCS communications.
Proxy network settings
If a proxy is deployed with an incorrect IP address or DNS entry, it might have registered with the Avamar server as localhost instead of the correct hostname.
Because proxies are virtual appliances that are managed by vCenter, once a proxy registers with the Avamar server, it is difficult to change network settings. Otherwise, this step would involve deleting it from the Avamar server, changing the network settings in vCenter, then reactivating it with the Avamar server.
In most cases, the most efficient remedy is to deploy a new proxy with the correct settings, then delete the old proxy from both Avamar and vCenter.
The vCenter documentation provides instructions for changing virtual appliance network settings.
Error when registering guest backup or Windows recovery target client
If a virtual machine has been added to the Avamar server because it resides in a vCenter domain, and you want to also protect that same virtual machine using guest backup, or use that same virtual machine as a recovery target for mounting Windows VMDKs, then you must change the
mcserver.xmlallow_duplicate_client_names preference setting to true.
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: <>()\