RecoverPoint for VMs with VxRail

We get data protection options with every VxRail solution

Firstly, you get the hardware:

and you get the software bundle:

From the software bundle, we get 2 data protection options and the two are RecoverPoint for VMs and VMware vSphere Replication. For the E, P, V and S Series nodes, we get 5 RP4VM licenses for each node. For the G Series, we get 15 RP4VM licenses for each chassis.

This is how RP4VM compares to our other options of running stretched cluster, vSphere replication and PowerProtect.

For this blog, we are going to focus on RP4VM.

What’s RecoverPoint for Virtual Machine (RP4VM) :

  • Disaster recovery and operational recovery with VM level granularity
  • Integrated management and orchestration with VMware’s vCenter GUI
  • Test, failover, failback and production recovery to any point in time per VM
  • Software only hypervisor based replication solution
  • Storage agnostic
  • Continuous data protection (CDP) and/or continuous remote replication (CRR)

Some highlights of using RP4VM:

  • No single point of failure
  • vRPA cluster high availability, each M can be replicated by any vRPA on any ESXi
  • Minimize bandwidth cost
  • Utilize compression and deduplication
  • Flexible deployment
  • vRPAs can be deployed on separated ESXi clusters than the protected VMs
  • Fast recovery time
  • No data copying when accessing image, just roll the journal, disk are attached to replica
  • DVR like roll back
  • Scroll between point in time when testing recovery, fastest image to the latest point in time

Use cases for RP4VM:

  • Disaster recovery
  • Natural disasters
  • Accidents
  • Utility outages
  • Technical malfunctions
  • Operational
  • Human errors
  • Data corruptions
  • Virus attacks
  • Malicious attacks
  • Ransomware
  • Data Migration and reuse
  • Data center move
  • Tech refresh
  • Test & dev
  • Backup

At a glance:

Architecture for RP4VM:

On the production site, we will setup the recover-point cluster which will deploy the vRPA VMs. Each ESXi host will then be configured with a splitter. We will then setup the recover-point cluster on the disaster recovery site. Once both site have established connection, we can start to select VMs for replication.

The VM’s data is then written at the production site, split and transferred via WAN to the disaster recovery site, where is it distributed.

We can protect each VM up to 5 destination, including it’s own cluster.

The benefit of replicating to it’s own cluster is that you can recover back to a point in time. For example, if you set a 4hr journal, you can recover back to up to 4hrs. When a VM get corrupted or if data is accidentally deleted, you can roll the VM back to say 30mins ago, before the VM got corrupted or before the data got deleted.

To see a demo or RP4VM in action, please visit our demo site at:

To find out more about RP4VM, please visit:

Share the Post:

Related Posts

%d bloggers like this: