Skip to main content
Quick start guide to Nutanix AHV backup proxy deployment
Updated over 4 months ago

Enterprise Workloads Editions: βœ… Business | βœ… Enterprise | βœ… Elite

Overview

The following infographic provides an overview of the process of setting up Nutanix AHV with Enterprise Workloads.

Quickstart_backupproxy.png


Step 1: Decide what you want to protect

Decide if you want to protect VMs in a Prism Element, or Prism Central.
You can protect:

  • VMs in a Prism Element
    If you deploy a Backup proxy in a Prism Element and register it, Druva will only backup VMs managed by the Prism Element.

  • VMs in a Prism Central
    If you deploy a Backup proxy in a Prism Central environment and register it, Druva backs up VMs in all clusters managed by the Prism Central.

Step 2: Deploy the Backup proxy and register Prism Element or Prism Central.

Backup proxy is the key component that sits between your Nutanix AHV data center and Druva Cloud and is responsible for performing backup and restore of virtual machines. See Deploy Backup Proxy for more information.

Step 3: Configure your virtual machines for backup

Once your Prism Element or Prism Central is registered with Druva, the Backup proxy discovers the virtual machines in your Nutanix AHV environment and lists them on the Management Console. You can then go ahead and configure the virtual machines for backup. See Configure Virtual Machines for backup for more information.

Step 4: Scale-out by deploying additional backup proxies

You can deploy additional backup proxies by following the same steps as deploying the first Backup proxy. You must, however, associate every additional Backup proxy with the same Prism Element or Prism Central. See Deploy Backup Proxy for more information.

Step 5: Load balance by adding backup proxies to the default pool

You can achieve load balancing through a Backup proxy pool. A Backup proxy pool consists of multiple backup proxies. Even if one Backup proxy goes down, the other proxies in the pool can take over. A Backup proxy is a stateless entity.

Druva creates a single Backup proxy pool called the Default Pool. All the deployed backup proxies are a part of this pool.

Did this answer your question?