Skip to main content
Druva Documentation

Register a standalone ESXi

Phoenix Editions: File:/tick.png Business File:/cross.png Enterprise File:/tick.png Elite

Before you begin

Before you begin, ensure you have:

Note: For additional help on deploying OVF templates, see the associated VMware documentation depending on the version of your VMware setup. For example, see Deploying OVF Templates from the vSphere 5 documentation library. 

You can deploy backup proxy  on a vCenter  server whose virtual machines you want to back up. If you have not deployed a vCenter server, you can deploy backup proxy on a standalone ESXi host. You must deploy backup proxy on the same vCenter server or the ESXi host from where virtual machines are to be backed up.

Watch video

 

Deploy backup proxy

  1. Log on to ESXi using vSphere Client. 
  2. From the File menu, click Deploy OVF Template.
  3. In the Deploy from a file or URL box, type or select the full path to the OVF template that you downloaded and click Next.
  4. Verify the OVF template details, and click Next
  5. Click Accept to accept the End User License Agreement (EULA), and click Next
  6. In the Name box, type a name for the template and click Next.
  7. From the list of resource pools, click the Resource Pool that you want to assign to this virtual machine and click Next.
  8. Select a destination storage, and click Next
    If you created storage profiles, click the storage profile that you want to assign to the virtual machine.
    From the list of storage, select a storage that you want to set as destination storage for this virtual machine.  
  9. Select from the following provisioning format, and click Next
    • Thick Provisioned Lazy Zeroed: If you select this format, a thick virtual disk is created, and the existing data is lazy zeroed (existing data on the provisioned storage are cleared when the virtual machine writes to the storage for the first time). 
    • Thick Provisioned Eager Zeroed: If you select this format, a thick virtual disk is created, and the existing data is eager zeroed (existing data on the provisioned storage is overwritten with zeroes at the time of creating the virtual machine).
    • Thin Provisioned: If you select this format, a thin virtual disk is created. 
Note: Backup proxy uses the default network mapping settings of the vCenter Server or ESXi hypervisor. 
  1. To start the virtual machine after deployment, select Power on after deployment.
  2. Verify the summary, and click Finish.  

Before configuring backup proxy, ensure that:

  • You have the ESXi  root credentials handy. You can either set the fully qualified domain name (FQDN) or the IP address of ESXi Server. ESXi  root credentials handy. You can either set the fully qualified domain name (FQDN) or the IP address of ESXi Server. 

    Note: Backup proxy stores these credentials in an encrypted format. 

  • Ensure port 443 on ESXi host is configured for http/https traffic. ESXi host is configured for http/https traffic. The backup proxy communicates with the registered ESXi host on the port 443.

Note: You can configure backup proxy settings for Standalone ESXi only through CLI. The process of configuring backup proxy through vCenter is applicable only through vCenter desktop/web client and not in case of standalone ESXi because vCenter has the capability to temporarily store the parameters received during the OVF deployment.

Configure backup proxy

  1. From the vSphere Client console, start the backup proxy virtual machine.
  2. Log on to the virtual machine with the root username and password. 
    Note: The default username is root, and the default password is druvaphoenix. If you are configuring the backup proxy for the first time, reset the password and use it for all subsequent logins. 
  3. On the Welcome screen, select GovCloud or Phoenix Public Cloud.
    proxyconf1.png
  4. On the type of VMware setup page, select VMware on-premise.
    proxyconf2.png
     
  5. On the Backup Proxy settings page, enter the required page number and provide the following details:
    proxyconf3.png
    Field  Description

    1. Network Configuration

    Phoenix backup proxy provides two network interface cards for configuration. When you select a card for configuration, backup proxy provides an option to enable the card. After you enable the card, you can configure the network settings. 

    Configure the network settings (Static/DHCP).

    • If you select the Static IP,  provide the following details:
      • IP Address
      • Netmask
      • Gateway
      • Primary DNS Secondary DNS Domain
      • Secondary DNS
      • Domain
    • If you select DHCP, the DHCP IP is set.

    Note:  Before selecting DHCP setting, verify that no dhclient is running on the backup proxy.

    2. Change hostname After the network configuration completes, you can choose to change the CentOS hostname. 
    • To change the hostname, provide the new hostname when prompted.
    • To leave the hostname unchanged, only press Enter.
    • Ensure that you do not enter a special character in the hostname or space.
    3. Provide vCenter/ESXi FQDN (or IP address) and credentials When prompted, provide the FQDN or IP address of ESXi server.

    4. Network Proxy Settings

    If you are using a web proxy in your environment, enter Yes when you are prompted with Do you want to use Network Proxy Setting. To continue without using a proxy, enter No

    If you enter Yes, provide the following details:

    • Choose one of the following authentication methods. Enter:
      0 for None
      1
      for Kerberos
      2
      for Basic 
      If you select Kerberos authentication method, provide the following details:
      • Enter FQDN of DNS Server Name: Enter the FQDN of the DNS server. 
      • Enter DNS Server User Name: Enter a DNS server user name to let the backup proxy virtual machine use the domain you provided in the DNS Server Name field. 
      • Enter DNS Server User Password: Enter the password of the user entered in the DNS Server User Name field. 
        After you provide the DNS server details, the Phoenix backup proxy attempts to connect to the DNS server. If the connection is successful, provide the following details. 
      • Enter KDC server name: Enter the FQDN of the Key Distribution Center (KDC) server. 
      • Enter KDC port: Enter the KDC port. 
      • Enter KDC user name: Enter a user name that the KDC can authenticate. 
      • Enter KDC Password: Enter the password of the user entered in the KDC user name field.
        After you provide the KDC server details, the Phoenix backup proxy tries to connect to the KDC server and generate an authentication ticket. If the ticket is generated successfully, the Phoenix backup proxy can connect to the web proxy. 
    • Proxy Type: Druva supports the following proxy types:
      • http
      • socks4
      • socks5
        Enter one of the supported proxy types. 
    • Proxy Server: Enter the valid proxy server FQDN
    • Proxy port: Enter the corresponding proxy port number
    • Username: Enter a valid proxy username. For a proxy that does not require authentication, enter *.
    • Password: Enter the valid proxy password. For a proxy that does not require authentication, enter *.

    Note: Ensure that the FQDNs of the DNS server, KDC server, and the web proxy host resolve 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.  

    5. Provide activation token

    At the prompt, type the activation token that Phoenix generated while registering the VMware setup. Wait till the virtual machine synchronizes with the NTP server. By default, the Phoenix backup proxy synchronizes with the CentOS NTP servers. To configure custom NTP server, see Configuring custom NTP server.

    Note: If you choose to activate backup proxy at a later time, press Enter key thrice to exit the configuration. To activate the backup proxy later, see perform a standalone activation of backup proxy

    6. Change the time zone

    You can change the time zone on your system:

     Type yes, to change the time zone.

    1. From the displayed list of continents and oceans, type the number corresponding to the server location.

    2. From the displayed list of country, type the number corresponding to the country in which the server is located.

    3. Type 1, to set the selected time zone.

    The backup proxy will reboot after you change the time zone.

    Type no, to keep the default time zone.

    Note: You can also manually set the time zone.

    7. Exit Wait for the synchronization to complete and exit.

Note: After you reset the default password of the backup proxy virtual machine, the ProxyConf utility available at /opt/Druva/Phoenix/bin/ is invoked. The ProxyConf utility prompts you for inputs while performing tasks 4 through 6, thus completing the configuration of backup proxy.

Perform a standalone activation of backup proxy

If you want to activate the backup proxy at a later stage, use the following steps for activation:

  1. From the vSphere Client console, click VMs and Templates, and start the backup proxy virtual machine. 
  2. Log on to the virtual machine with the default username and the changed password.  
  3. Run the following command to activate backup proxy:
    PhoenixActivate <token>

Configuring custom NTP server 

You can configure Phoenix VMware backup proxy to use custom  NTP server. The NTP requests are serviced through a pool of NTP servers. Currently, the backup proxy uses the *.centos.pool.ntp.org pool

  1. Open the /etc/ntp.conf file to configure your NTP server.
    The NTP server configuration file contains NTP server entries in the following format:
    server <ntp_server_fqdn> [options]
    For example:
    server 0.centos.pool.ntp.org iburst
    server 1.centos.pool.ntp.org iburst
    server 2.centos.pool.ntp.org iburst
    server 3.centos.pool.ntp.org iburst
  2. Comment the existing NTP server entries and add the following entry to the /etc/ntp.conf file.
    server <internal_ntp_server_fqdn> iburst
  3. Restart the ntpd service using the following command:
    service ntpd restart
  4. Verify that the /var/log/messages file now synchronizes with the new NTP server without any errors.