Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

1332

November 10th, 2012 05:00

Recoverpoint/SE 3.5P1 and svmotion

We are currently running RP/SE 3.5P1 using CRR. The LUN is on vmfs 3.546 and we are creating a new vmfs 5.x lun to migrate the vmdks to it. We'll be using svmotion to move the vmdks, but I wasn't sure the best way tro handle the current replication going on. Ideally, I would like to be able to have RP provide protection during the svmotion. I'm not sure if that's possible, since the LUN will be changing dramatically. The question to me is how do I freeze the current, latest replication, just prior to svmotion so that if any problems occur I can revert to it? Once the svmotion has completed I would setup a consistency group to incorporate the new lun.Thank you in advance.

2 Intern

 • 

1.1K Posts

November 11th, 2012 11:00

Hi there,

RecoverPoint will continue to replicate whatever resides on the datastore source LUN irrespective of the svmotion activity, therefore there is no reversion from a RecoverPoint perspective.

Regards,

Richard Forshaw

Principal Corporate Systems Engineer - RecoverPoint (EMEA)

Data Mobility Business Unit - Enterprise Storage Division

EMC2 Computer Systems (UK) Ltd

No Events found!

Top