📝 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.
The following are the prerequisites:
The user setting up the proxy server must have Cloud Administrator for Enterprise Workloads privileges.
The virtual machine must be configured with the minimum requirements. For more information, see VM Specifications.
The IP address / Network being provided to the Druva Backup Proxy must be able to communicate to Cloud on port 443.
Configure your antivirus and any third-party encryption programs to authorize the latest Druva applications and Druva and S3 URLs. For more information, see Firewall, Antivirus and Network Configuration for Druva Enterprise Workloads.
Ensure the PAM authentication credentials have the required permissions to perform backup and restore operations. For more information, see Proxmox user permissions.
Ensure the backup proxy VM can establish an SSH connection to the Proxmox node using Linux PAM authentication.
Log in to the Proxy VM and execute the following command to verify access:
ssh <pam_user>@<proxmox_node_ip>
Example:ssh root@172.16.1.10Enter the password after the prompt.
You must have the Web proxy credentials configured (If you use a Web proxy in your environment).
It is recommended to install the Qemu agent in your Proxmox VMs. This agent provides application consistency, crash consistency, and quiescing by default.
📝 Note
To verify application consistency, check the logs on the node using the following command:
sudo journalctl -u qemu-guest-agent | grep -i "freeze"
Expected Response:
If the freeze was successful, the output will include a line similar to:
guest-fsfreeze calledFor more information, see Steps for backup proxy deployment and activation.