Deploy backup proxies with vCenter credentials to protect VMs hosted on vCenter-managed ESXi. For standalone ESXi hosts, deploy a separate proxy. Multiple proxy instances can be deployed for a single ESXi or vCenter server, but one proxy can only be mapped to either an ESXi or a vCenter server, not both.

Expand to watch the video to understand the process.

Step 1: Review the prerequisites

Check Prerequisites to install the backup proxy.

Step 2: Download the Druva Proxy Deployer

📝 Note

For VMC, the system on which you install the Druva Proxy Deployer must connect to the ESXi through private IP. Files are uploaded to the datastore through the ESXi.Thus, download the Druva Proxy Deployer on a virtual machine deployed in the VMC environment.

On the Management Console, click Protect > VMware.
Click Register New Setup.
From the Register VMware Setup dialog box, download the Druva Proxy Deployer. You can also download the Druva Proxy Deployer from the Downloads page.
Copy the activation key.
On your local system, run the Druva Proxy Deployer and launch the deployer.

Step 3: Deploy the first backup proxy and register your setup

Launch the Druva Proxy Deployer.
Browse to the location where you want to download the OVA template.
Ensure that the download location has a minimum of 7 GB free disk space.
Click Get Started.

VMware setup connection details

Provide details of the vCenter where you want to deploy the backup proxy.

vCenter IP/FQDN: Provide the IP/FQDN of the vCenter.
Port: Port through which vCenter communicates with Druva Cloud. Port 443 is used to connect to Druva Cloud.
Username and Password: Provide vCenter credentials. Ensure the user has the required permissions.
Using VMC: Select this check-box if your vCenter is deployed in VMC. For more information, see Druva and VMC integration.

Backup proxy location details

Provide details of where the first backup proxy must be deployed.

Backup Proxy Name: Enter the name of the backup proxy. The name must be unique and should not be in use by any other backup proxy. The backup proxy name can contain alphabets, numbers, and hyphens. The only special character that is supported is the hyphen. All other special characters are unsupported.
Data Center: (Available only for vCenter) Select the data center to which the pool will belong to.
ESXi Host: (Available only for vCenter) Select the ESXi host.
Datastore: Select the datastore. Ensure that the datastore has at least 110 GB of free space.
Time Zone: The time zone by default is picked up from the local system time zone. Select the time zone based on the region where the backup proxy is going to reside. The backups are triggered as per the selected time zone.

Network connection details

Provide details of where you want to connect to in your VMware environment.

Static IP: Update the following details:
- IP address - Mandatory
- Netmask - Mandatory
- Gateway - Mandatory
- VM Network - Mandatory
  You can select VM networks or Distributed Switch Port groups in the VM network field.
- Primary DNS - Mandatory
- Secondary DNS - Optional
  
  Consideration for VMC
  - You cannot directly assign public IPs to virtual machines in VMC. You must:
  - Deploy the backup proxy on VMC using the DHCP option.
    On VMC set up, create a NAT rule and request for public IP against the newly deployed backup proxy virtual machine.
- DHCP: The IP address is dynamically assigned. Select the VM network.
- Add NIC 2: You need to configure 2 NIC cards, if you have two different networks to communicate with the VMware infrastructure and for external communication.
  - Update the following details:
  - IP address - Mandatory
  - Netmask - Mandatory
  - Default gateway - Optional
  - VM Network - Mandatory
  - Primary DNS - Optional
  - Secondary DNS - Optional

Activation details

Provide details of where you want to connect to in the Druva environment

Activation Token: Provide the activation token you had copied from the Management Console.
Using GovCloud: Select the check-box if you want to connect over Druva GovCloud.
Web Proxy: Choose the authentication type:
- None: Select for unauthenticated proxy.
- Basic
- Kerberos: If you select a Kerberos authentication method, provide the following details:
  - Enter KDC server name: Provide the FQDN of the Key Distribution Center (KDC) server.
  - Enter KDC user name: Provide a username that the KDC can authenticate.
  - Enter KDC Password: Provide the password of the user entered in the KDC user name field.
  - Enter KDC port: Provide the KDC port.
  - Enter FQDN of DNS Server Name: Provide the FQDN of the DNS server.
  - Enter DNS Server User Name: Provide a DNS server username to let the backup proxy virtual machine use the domain you provided in the DNS Server Name field.
  - Enter DNS Server User Password: Provide the password of the user entered in the DNS Server User Name field. Ensure that the FQDNs of the KDC, DNS server, and the web proxy host resolves to the appropriate servers. If the FQDNs do not resolve, add the FQDNs and the respective IP addresses in the /etc/hosts file of the backup proxy virtual machine.
  - Proxy Type: Druva supports the following proxy types:
    http
    socks4
    socks5
  - Proxy Server IP: Valid IP of the proxy server.
  - Proxy Port: Respective proxy port number.
  - Username: Valid proxy username.
  - Password: Valid proxy password.

Click Deploy Now.
The proxy deployment progresses through the following stages. Various validations are made during the respective stage. To troubleshoot validations issues, see Troubleshoot deployment issues.

OVA download: OVA template is downloaded on the local system. The OVA template is cleaned up after the backup proxy is deployed successfully.
Deployment: The first backup proxy is deployed and the backup proxy VM is created.
VM power on: The backup proxy virtual machine is powered on.
Network configuration: The backup proxy VM network is configured.
Connection to Druva Cloud: Setup is registered with Druva

After the backup proxy is deployed and registration is complete, the OVA template file is cleaned up from the system.
Provide the following details:

📝 Note

After cancelation, if the cleanup fails due to network connectivity issues, you need to manually clean up the VM and its disk.