Configuration of the deployed vRPAs is performed with the RecoverPoint Deployment Manager. This is a tool on your laptop that, using a multi-step process, assigns IP addresses to the RecoverPoint appliances and their various networks and connects these appliances to the VNX array. The previous part of this series discussed the first steps to get into the tool: now it’s time to start entering some configuration data.
If you’ve met the prerequisites described in part one of this series, deploying the virtual RecoverPoint appliances in your VMware environment should be a straightforward task. Download the latest OVF of the vRPA from the EMC support website and deploy it using the vCenter management console.
It has been a while since I’ve written anything about RecoverPoint since my original post on RecoverPoint 4.0 several years ago. To my delight I was recently put on a couple of projects to deploy new virtual RecoverPoint clusters for two customers. Several things had changed since the first appearance of the virtual RecoverPoint Aplliance (RPA), so why not write a small series on the deployment of these appliances? Gotcha’s included!
EMC has just announced a new version of RecoverPoint – 4.0. With this new version comes a truckload of new and exciting features. I will not cover all these features but will instead pick out a couple of features that score high on my list. But first of all: what is RecoverPoint and why should you consider replicating with it?
The RecoverPoint family replicates block data on a SAN/storage level. It can do both local replication inside an array or remote replication to another array. There are multiple flavours of RecoverPoint (SE, EX, CL): which one you need depends on the size of your environment and the storage systems you are using. The strong point of RecoverPoint is that it offers continuous replication instead of only the traditional asynchronous or synchronous replication.