In the midst of the year end of 2014, we have launched a brand new replication technology which is based on our proven RecoverPoint engine and fully integrates with VMware.
I’ve had the first chance to play with it. As a specialist for traditional storage replication I was most impressed by how easy it is to startup and test the replicated Virtual Machine(VM).
First things first, to protect a Virtual Machine, simply select “protect” from its properties:
Next you can choose your desired RPO, the target cluster and the host and storage resource for the replicated VM:
How easy is that? Now your VM is protected and the replica VM is automatically deployed. In our test on the same cluster:
RecoverPoint for VM is for everybody
The new RP4VM is completely storage agnostic. You don’t protect and failover/failback full datastores but the protection is software defined and a property of each VM. It works with any storage type (SAN, NAS, DAS) and is fully integrated and managed in vSphere.
The “RecoverPoint for VM” replication engine
The replication engine of RP4VM offers integrated continuous data protection which allows to travel back in time and recover the VM or just some data from the latest or any other previous point in time. And also after you access on old image, you can still forward the replica VM back to the future.
For me some other important features are
- dynamic change between sync and async replication
- replication data reduction through compression and deduplication
- vApp based fully redundant scale-out cluster
- the support for Consistency Groups (CG) of up to 16VMs
With CGs, you can startup or recover all VMs of this CG in one go. This makes it very convenient to run/perform DisasterRecovery Tests or recover a complete application landscape with several VMs.
Let’s go back to the demo, here’s a screenshot from the DR VM startup wizard – choose desired time:
Or to startup the replica VM from the latest PIT (point in time):
In the next step you specify the network. We don’t want to cause an IP conflict with the production VM 😉
Next the replica VM is booted and can be used to run tests, resume production or restore files:
This makes DR, DR testing and operation recovery much simpler. All the manual DR steps we know from array based replication are history. Like login to array, failover volume, provision volumes, rescan the cluster, browse datastore, find your VM, add the VM to inventory, adjust network configuration and finally start the VM. All these steps are abstracted and fully automated.
RecoverPoint for VM is Software Defined protection and means
- storage vMotion your VM between any storage devices while replication continuous
- test your replication VM or restore files while production and replication are ongoing
- recover from the latest image or travel back to any previous point in time
- control your RPO per VM or group of VMs and only replicate what’s needed