You need to add an ESX(i) host for backup, replication and other activities and bypass a vCenter.
To launch the New VMware Server wizard, do one of the following:
• Open the Backup Infrastructure view, select the Managed servers node in the inventory pane and click Add Server on the toolbar or right-click the Managed servers node and select Add server. In the Add Server window, select VMware vSphere.
• Open the Virtual Machines view, select the VMware vSphere node in the inventory pane and click Add Server on the toolbar or right-click the VMware vSphere node in the inventory tree and select Add Server.
• Open the Virtual Machines or Files view, right-click anywhere in the inventory pane and select Add server. In the Add Server window, select VMware vSphere.
Enter a full DNS name or IP address of the standalone ESX(i) host. If an ESX(i) host is added to a vCenter Server by IP, you will need to add it to Veeam by DNS, and vice versa (see More Information in this article for details). Provide a description for future reference. The default description contains information about the user who added the server, as well as the date and time when the server was added.
From the Credentials list, select credentials for the account that has administrator privileges on the added VMware server. If you have not set up credentials beforehand, click the Manage accounts link or click Add on the right to add necessary credentials. The user name should be specified in the format of user: root and password: ****.
The default port number for VMware web service communication is 443. If the connection with the ESX(i) host over this port cannot be established, you can customize the port number on the ESX(i) host settings and specify the new port number in this field.
The next step is available only if you are adding an ESX host. When adding an ESXi host, the wizard will skip this step and move on to the next
If necessary, you can use a SSH connection for file copying operations and file copying jobs. These settings are optional. If you do not want to use SSH, clear the Use service console connection to this server check box. In this case, Veeam Backup & Replication will work with the ESX host in the agentless mode.
1. Make sure that the Use service console connection to this server check box is selected.
2. From the Credentials list, select credentials to connect to the service console of the ESX host. If you have not set up credentials beforehand, click the Manage accounts link or click Add on the right to add necessary credentials.
a. To use non-root account If you are running version 7.x:
b. To use non-root account If you are running version 8.x:
Click Add – Linux account
3. To configure advanced SSH settings, click Advanced.
b. In the Data transfer options section of the Network Settings window, specify connection settings for file copy operations. Provide a range of ports that will be used as transmission channels between the source host and target host (one port per task). By default, Veeam Backup & Replication uses port range 2500-5000. If your virtual environment is not large and data traffic will not be significant, you can specify a smaller range of ports: for example, 2500-2510 to run 10 concurrent jobs at the same time.
c. If the ESX host is deployed outside NAT, select the Run server on this side check box in the Preferred TCP connection role section. In the NAT scenario, the outside client cannot initiate a connection to the server on the NAT network. As a result, services that require initiation of connection from outside can be disrupted. With this option selected, you will be able to overcome this limitation and initiate a ‘server-client’ connection: that is, a connection in the direction of the ESX host.
To find out what the hosts are listed as under vCenter you can expand it under the backup infrastructure pane. Managed Servers > VMware vSphere > vCenter Servers > (name of vCenter)
If you don’t have a vCenter server already added and you plan to do so, make sure to add it prior to adding a standalone host.
Please be aware that we’re making changes which will restrict access to product updates for users without an active contract.