To back up your virtual machines, you must first download and install a backup proxy in your virtual infrastructure environment and then register it from the Management Console. This article describes how to get the backup proxy and activation token and register your servers.
Download OVA to deploy Proxmox backup proxy
You must download the latest version of the Proxmox backup proxy. Visit the Downloads page using the following link:
https://downloads.druva.com/phoenix/#proxmox
OR
Perform the following steps to download the backup proxy from the Register New Node setup:
Log in to the Management Console.
Select the workload from the Protect menu. Note that if the All Organizations menu is enabled, you have to first select an organization and then select the workload.
Click Register New Node.
The Register Proxmox Node page is displayed.
Click Download to download the Proxmox Backup Proxy (OVA). You are redirected to the Downloads page.
Select your cloud type as Public Cloud or GovCloud.
Download the appropriate OVA to deploy the Proxmox backup proxy.
Deploy the Proxmox backup proxy
Step 1: Select the source OVA
Select the source OVA file that you have downloaded from the Downloads page.
Navigate to your Proxmox web UI and select your target node.
In the Storage tab, click on the local storage or designated import storage (for example, local on
node <node_name>ddsplsrv244).Click the Import tab on the left-hand menu.
Click Upload to upload your
.ovafile from your local computer, or click Download from URL to paste a direct link to the.ovafile.
Once the file has finished uploading, select the
.ovafile from the list.Click the Import button at the top of the interface to open the configuration wizard. A guest import wizard will appear. Proxmox will automatically map most configurations from the source VM.
Step 2: Configure General Settings
In the General tab of the pop-up window, verify and adjust the core compute resource allocations. Configure the Default Storage to LVMThin or ZFS, and the Import Working Storage any file-level storage type.
Step 3: Optimize Disk Storage Settings
Switch to the Advanced tab at the top of the wizard.
Locate the Disks section. The appliance includes a pre-configured
scsi0disk of42.00 GiB.Click the dropdown menu next to SCSI Controller and change it to
VirtIO SCSI singlefor better I/O performance. Map the Network Interfaces to the available Linux network bridge within your setup.
Step 4: Configure Network Interfaces
Still inside the Advanced tab, scroll down to the Network Interfaces section to configure the virtual network adapters. Currently, only one virtual network adapter (net0) is configured.
Step 5: Finalize the Import
Review the Resulting Config tab to ensure all your manual adjustments are correctly registered.
Click Import in the bottom right corner of the window to build the virtual machine. The VM will then appear under the assigned node.
Ensure that the QEMU Guest Agent is enabled.
Agent installation and proxy setup
Once the VM is running, you must install the backup agent.
Perform the following steps to download the backup proxy from the Register Proxmox Node setup:
Log in to the Management Console.
Select the workload from the Protect menu. Note that if the All Organizations menu is enabled, you have to first select an organization and then select the workload.
On the All Nodes page, click Register New Node.
In the Register Proxmox Node dialog box, under Download the backup proxy image, click Download to download the latest OVA package.
(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>📝 Note
Only HTTP web-proxy is supported.
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.
Log in to the Management Console.
From the top menu bar, select your organization if organizations are enabled. Otherwise, proceed to the next step.
Click Protect > Proxmox.
Click Register New Node.
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>
EnterpriseWorkloadsAgent proxmox activate --token <TOKEN> -c <GOV DIRECTORY SERVICE URL>(For Gov cloud)
Configure node credentials: Provide the IP/FQDN and credentials of the Proxmox node:
To skip certificate verification:
EnterpriseWorkloadsAgent proxmox setproxmoxcred --fqdn <ip/fqdn of node server> --user <pam root user / custom user of node> -kOR
EnterpriseWorkloadsAgent proxmox setproxmoxcred --fqdn <ip/fqdn of node server> --user <pam user of node / custom user> --skipCertVerify
To provide certificate verification:
EnterpriseWorkloadsAgent proxmox setproxmoxcred --fqdn <ip/fqdn of node server> --user <pam user of node / custom user> -cOR
EnterpriseWorkloadsAgent proxmox setproxmoxcred --fqdn <ip/fqdn of node server> --user <pam user of node / custom user> --caCertsBundlePath
📝 Note
You can download the certificate (
/etc/pve/pve-root-ca.pem) from the node.
To use a custom user account for backup and restore operations, pass the custom user credentials in the setproxmoxcred command. For more information on how to set a custom user account, see Proxmox User Permissions.
📝 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> -P <CUSTOM_PORT>
Once activated, the registered node will appear on the All Nodes page of the Management Console. If the registered node belongs to a cluster, all nodes within that cluster will be visible on the All Nodes page. However, the deployed proxy will only be installed on the specific node that was registered.