Before you begin
Before you begin, ensure you have:
- Installed the vSphere Client for desktop on a server
- The vCenter name does not contain any space or special characters
- Downloaded the backup proxy virtual appliance on the same server as the vSphere Client or a shared server
- The activation key
- Read the prerequisites and resource sizing for backup proxy.
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.
Deploy backup proxy
- Log on to ESXi using vSphere Client.
- From the File menu, click Deploy OVF Template.
- 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.
- Verify the OVF template details, and click Next.
- Click Accept to accept the End User License Agreement (EULA), and click Next.
- In the Name box, type a name for the template and click Next.
- From the list of resource pools, click the Resource Pool that you want to assign to this virtual machine and click Next.
- 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.
- 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.
- To start the virtual machine after deployment, select Power on after deployment.
- 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.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
- From the vSphere Client console, start the backup proxy virtual machine.
- Log on to the virtual machine with the default username and password.
Note: The default username is root, and the default password is druvaphoenix.
- When prompted, reset the password.
- On the Welcome screen, select GovCloud or Phoenix Public Cloud.
- On the type of VMware setup page, select VMware on-premise.
- On the Backup Proxy settings page, enter the required page number and provide the following details:
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
- Primary DNS Secondary DNS Domain
- Secondary DNS
- 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.
3. Provide vCenter/ESXi FQDN (or IP address) and credentialsESXi 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:
- Type yes, when prompted "Do you want to use Network Proxy Setting". Provide the following details:
Druva supports the following proxy types:
Proxy Server IP Valid IP of proxy server. Proxy Port Corresponding proxy port number. Username Valid proxy user name. Password Valid proxy password.
- Type No to continue.
- Druva only supports basic authentication with Web proxy.
- If you want to configure web proxy setting at a later stage, follow the steps listed under Configure Web proxy.
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 backup proxy, follow the steps in To 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.
From the displayed list of continents and oceans, type the number corresponding to the server location.
From the displayed list of country, type the number corresponding to the country in which the server is located.
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.
- If you select the Static IP, provide the following details:
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:
- From the vSphere Client console, click VMs and Templates, and start the backup proxy virtual machine.
- Log on to the virtual machine with the default username and the changed password.
- Run the following command to activate backup proxy:
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.
- 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]
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
- Comment the existing NTP server entries and add the following entry to the /etc/ntp.conf file.
server <internal_ntp_server_fqdn> iburst
- Restart the ntpd service using the following command:
service ntpd restart
- Verify that the /var/log/messages file now synchronizes with the new NTP server without any errors.