Skip to main content

 

Druva Documentation

Register a VMware on AWS (VMC) setup

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

To backup and restore virtual machines hosted on your VMware Cloud setup, you have to deploy the Phoenix backup proxy. The Phoenix backup proxy is the client-side component that detects the virtual machines running on your setup and executes the backup and restore requests from the Phoenix Cloud. You can see the Phoenix architecture below:

Phoenix-VMC-Architecture.png

Before you begin, ensure that you download the backup proxy and keep the activation token handy. For more information, see Download backup proxy and generate activation token.

Note: To get the VMware on cloud backup proxy, contact Druva support.

Deploy backup proxy

Perform the following steps to deploy the backup proxy:

  1. Log on to the VMware Cloud vCenter setup. 

  2. After logging in, the vCenter WebSphere client opens on the HTML5 platform.   

  3. On the web client page, click Menu > VMs and Templates.

  4. In the left pane select the datacenter.

  5. After you select the data center, click  Actions > Deploy OVF Template. A deployment wizard appears.
    You can also right-click on the data center and click Deploy OVF Template to launch the deployment wizard.

  6. In the Select an OVF template section, provide a URL to the OVF template or browse and select the OVF template saved locally on your computer and click Next.

  7. In the Select a name and folder section, provide a virtual machine name, select a folder on the datacenter, and click Next.

  8. From the list of resource pools, click the resource pool that you want to assign to this virtual machine, and click Next. You can select provisioning format.
    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 is 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 zeros at the time of creating the virtual machine).
    Thin Provisioned: If you select this format, a thin virtual disk is created.

  9. Review the template details and click Next. The details also show the disk provisioning format.  

  10. Accept the End User License Agreement (EULA), and click Next.

  11. Select a destination storage. From the storage list, click a storage that you want to set as the destination storage for this virtual machine. After selecting the storage, click Next.

    Note: Backup proxy uses the default network mapping settings of the VMC setup.
  12. Select a network for the backup proxy and click Next.

  13. Verify the summary, and click Finish.

Configure backup proxy

Before configuring the Phoenix backup proxy, ensure that:

  • You have the cloudadmin role credentials for vCenter.

  • Port 443 is enabled for http/https traffic

    • Traffic from <compute gateway IP> to the vCenter server over 443.

    • Traffic from <compute gateway IP> to Phoenix master node.

    • Traffic from <compute gateway IP> to Phoenix storage node.

Perform the following steps to configure the deployed Phoenix backup proxy:

  1. Start the backup proxy virtual machine and launch its command line terminal.

  2. Log in to the backup proxy using the default username and password. The default username is root, and the default password is druvaphoenix.

  3. When prompted, reset the password.

  4. On the Welcome screen, select Phoenix Public Cloud.
     proxyconf1.png

  5. On the type of VMware setup page, select VMware on AWS cloud (VMC).
    proxyconf2-1.png

  6. On the Backup Proxy settings page, enter the required page number and provide the following details: 
    proxyconf3.png

    The options in the command line menu are described below:

    Option

    Description

    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.

    To 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.

    Change hostname

    After the network configuration is complete, you can choose to change the CentOS hostname. To change the hostname, you have to provide the new hostname.

    To leave the hostname unchanged, press Enter.

    Provide vCenter/ESXi FQDN (or IP address) and credentials ESXi FQDN (or IP address) and credentials

    The FQDN or IP address of the vCenter server.

    Provide activation token

    You have to enter the activation token that Phoenix generates when you register the VMware setup. You have to 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.

    Change the time zone

    You can change the timezone on your system:

    1. Type yes, to change the time zone.

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

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

    4. Type 1, to set the selected time zone.
      The backup proxy will reboot after you change the timezone. Type no, to keep the default time zone.

    Note: You can also set the time zone manually.

    Exit

    Wait for the synchronization to complete and exit.

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. Start the backup proxy virtual machine and launch its command line terminal. Log on to the virtual machine with the default username and the changed password.  

  2. 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.

  2. 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

  3. Comment the existing NTP server entries and add the following entry to the /etc/ntp.conf file.

    server <internal_ntp_server_fqdn> iburst
  4. Restart the ntpd service using the following command:

    service ntpd restart
  5. Verify that the /var/log/messages file now synchronizes with the new NTP server without any errors.

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.

VMware Cloud on AWS Network configuration

  • You have the cloudadmin role credentials for vCenter.

  • Port 443 is enabled for http/https traffic

    • Traffic from <compute gateway IP> to vCenter server over 443.

    • Traffic from <compute gateway IP> to Phoenix master node.

    • Traffic from <compute gateway IP> to Phoenix storage node.

Managemenet-Network.jpg

  • Was this article helpful?