Skip to main content

Create backup proxy VM and install proxy packages

Updated today


πŸ“ Note

​This feature is currently available under the Early Access program. To know more about the Early Access program and sign up for this feature, contact Support or your Account Executive.


Follow these steps to register a Proxmox node and set up your backup environment.

Step 1: Deploying the backup proxy VM

To register a Proxmox node, you must first create a dedicated Virtual Machine (VM) on that node to serve as the backup proxy.
​

VM Specifications

Ensure the VM is configured with the following minimum requirements:

  • Operating System: Ubuntu 22.04

  • OS Disk Size: 32 GB

  • Memory: 8 GB (8192 MiB)

  • CPU Cores: 8

Creation steps in Proxmox

  1. Initiate Creation: Right-click the specific Proxmox Node and select Create VM, or use the Create VM button in the top right corner of the interface.
    ​

  2. General Settings: Provide a Name for the proxy (for example, proxmox-backup-proxy) and assign a VM ID.
    ​

  3. Operating System: Select the Ubuntu 22.04 ISO image.
    ​

  4. System Settings: Ensure that the Qemu Agent is enabled. (Recommended) Enable the Qemu agent.
    ​

  5. Disks: Set the Storage type to LVM-Thin (recommended) with a minimum disk size of 32 GB.
    ​

  6. CPU: Configure the CPU for a minimum of 8 total cores.
    ​

  7. Memory: Set the memory to a minimum of 8192 MiB.
    ​


    ​

  8. Network: Use the Linux Bridge of the node for network connectivity.
    ​


    ​

  9. Confirm and Finish: Review the details. Ensure that the Start after created option is selected, and click Finish.
    ​


    ​

  10. Verification: The Create VM task is triggered. Wait for the task status to show OK.
    ​


    ​

  11. The VM will then appear under the assigned node.
    ​​

Step 2: Agent installation and proxy setup

Once the VM is running, you must install the backup agent.

  1. Install agent: Access the VM terminal and install the Debian package using the command:
    ​dpkg -i <DEBIAN PACKAGE>
    ​

  2. (Optional) Configure Web proxy: If your environment requires a web proxy to reach the Druva Cloud, use the following command:
    ​/opt/Druva/EnterpriseWorkloads/bin/EnterpriseWorkloadsAgent web-proxy-config -s -t http -i <WEB-PROXY-IP> -u <USERNAME> -p <PASSWORD>

Step 3: Node activation and registration

Link the backup proxy to the Management Console to complete the node registration.

Generate activation token

To register your Proxmox setup, an activation token is required. Perform the following to generate an activation token.

  1. Log in to the Management Console.

  2. From the top menu bar, select your organization if organizations are enabled. Otherwise, proceed to the next step.

  3. Click Protect > Proxmox.

  4. Click Register New Node.

  5. From the Register Proxmox Node dialog box, select the Copy Token icon under the Activate backup proxy and set node credentials section. The activation token is copied successfully.
    This token is valid for 25 servers and 7 days. This is required for connecting with the Druva Cloud during proxy deployment.


πŸ“ Note

​If this token has expired, click Generate New Token. Enter the required details in the Generate Token dialog box and click Generate. Alternatively, if you have generated an activation token earlier, you can copy it from the Manage Activation Tokens page.


Activate and set credentials

Run the following commands on the backup proxy VM:

  • Activate the agent:
    ​EnterpriseWorkloadsAgent proxmox activate --token <TOKEN>

  • Configure node credentials: Provide the IP/FQDN and credentials of the Proxmox node:
    ​EnterpriseWorkloadsAgent proxmox setproxmoxcred --fqdn <ip/fqdn of node server> --user <pam user of node>
    ​


    πŸ“ Note​

    If your Proxmox VE port is other than 8006, then add a flag:

    EnterpriseWorkloadsAgent proxmox setproxmoxcred --fqdn <ip/fqdn of node server> --user <pam user of node>-l <CUSTOM_PORT>


Once activated, the registered node will appear on the All Nodes page of the Management Console.

Did this answer your question?