1. Start the installation file and click on Modify:
   
   (!) During initial installation, you simple can choose this via component selection.
2. Mark the Agent for VMware vSphere ESX(i) (Windows) for installation and click Next:
   
3. Specify the access credentials of vCenter or ESX(i) server and click Next:
   
4. View the summary and click on Modify:
   
5. See confirmation, that installation has completed:
   
6. After successful installation, you can see the new added hosts:
   
7. See the list of available virtual machines for backup:
   

The Virtual Appliance has to obtain an IP address so it can communicate with the vCenter server, therefore the DHCP is required. If DHCP is not in use or not available, it’s possible to manually assign IP addresses to the virtual appliances. Please read the following section:

1. Start the installation file and click on Modify:
   
   (!) During initial installation, you simple can choose this via component selection.
2. Mark the Agent for VMware vSphere ESX(i) (Windows) for installation and click Next:
   
3. Select where to install the components and click Next:
   
4. View the summary and click on Modify:
   
   (!) The components for Virtual Appliance are not installed in Windows. The components are stored for installation on vCenter or ESX(i) host.
5. To install the Virtual Appliance launch Acronis Management Server:
   
6. In Management Console, right-click on Virtual machines -> Configure VMware vCenter integration:
   
7. Specify the IP address and credentials and click OK:
   
8. Select list of hosts and settings for Agent for ESX(i) deployment and click on Deploy Agent for ESX(i):
   
9. After successful installation, you can see the new added hosts:
   
10. See the list of available virtual machines for backup:
    

Many companies, especially those with distributed infrastructure components or with large numbers of ESX(i) hosts, have a need to manage backup and recovery for virtual machines residing within clusters on several vCenter Server instances from a single AMS (Acronis Management Server). Therefore, Acronis is providing this guide as a tool to assist these organizations with the design and implementation of ESX(i) Agent for VMware vSphere using a centralized AMS server. See this sample environment:

(!) Notice that Site B only has one ESXi Agent for VMware vSphere. This is possible only by following the procedures in this guide. Also, to achieve LAN-Free backups you could move the ESXi Agent for VMware vSphere to the ASN servers which have access to the vSphere Datastores instead of deploying the agent to the hosts.

When using more than one vCenter (e.g. Cluster configuration) you need to deploy the virtual appliance to every vCenter. 

(!) When backing up more than one vCenter host, you need to disable the vCenter integration feature before installing additional virtual appliances.
(!) It is recommended to use vCenter credentials instead of ESX(i) host credentials.

To install additional virtual appliances follow these steps:

1. In the Acronis Management Console, connect to the Acronis Management Server and click at the left navigation tree on Virtual Machines -> Deploy Agent for ESX(i):
   
2. Click on Add ESX(i) host and enter the vCenter server FQDN or IP and a user account with the required privileges:
   
3. Configuring Agents
   
   1. Select each host by selecting the respective check boxes next to each host name;
   2. Select the Deploy Agent for ESX(i) on this host check box for each host;
   3. Customize the VA Name according to your naming conventions. It is highly recommended to leave the [N] variable intact as this will ensure unique naming of the appliance within the AMS;
   4. Click Network Configuration and set accordingly.
      (!) DHCP is required for the Obtain TCP/IP settings automatically option;
   5. Repeat these steps for each host selected to ensure they are all assigned the appropriate name and network settings:
      
   6. After all of the naming, credentials and network settings have been verified the Agents can be deployed. Click Deploy Agent for ESX(i). Monitor the progress until agents have been deployed successfully:
      
      (!) Most common failures are the result of selecting Obtain TCP/IP settings automatically when there is no DHCP service available on the selected subnet, specifying an IP that is already in use, or using the incorrect credentials.
4. Configuring Bindings
   In cases where less Agents have been deployed than there are hosts or where more granular control of Agent to VM workloads is desired Agent bindings can be customized.
   
   1. Right-click Virtual Machines in the Navigation pane and select Configure Agent for ESX(i) bindings:
      
   2. Select an Agent and click either Bind with virtual machines or Unbind virtual machines:
      
   3. Select the virtual machine(s) to be bound or unbound and select OK:
      
      (!) Once bindings have been completed you should be able to see all of the virtual machines under the All virtual machines group in the Navigation pane. If any VMs appear greyed out it is typically because they have not been bound to an Agent.