Celerra Migration options using Celerra Replicator V2

Question

We are having four Celerras A,B, C and D. Presently we have a Replication running on Production site A and its DR is B. Now we need to Migrate the File systems to the other two Celerras with C being the New Production and D its DR site. C and D are brand new Celerras. So, i would like to ask what is the best way to migrate the file systems to the new Celerras C and its DR celerra D with minumun impact on the Production. We presented 3 options

Option 1

1) Establish a replication from B to C

2) Cutover production to C and reverse replication to B.

3) Establish Replication from C to D

4) Cutover DR to D.

Option 2

1) Establish a Replication from A to C and also from C to D ( two hops)

2) On cutover Switch production to C and DR to D.

Option 3

1) Establish Replication from B to C and aslo from C to D ( three Hops)

2) Cutover Prod to C and DR to D.

We are using Celerra Replicator V2 . DART Code is 5.44.408 on all celerras. I think option 3 is not possible as V2 supports only 2 hops. I would like to hear from which option is best with minumum impact on Production and are there any other options we can go for.

ral67_xyz · Answer

I would suggest to create a small test file system and try the different options

you could try:

keep A -> B

add A -> C

add C -> D

delete A -> B

failover A -> C

delete C -> A

you need to carefully read the manual on what happens with multi-hop replications on switchover / failover - I'm not a 100% sure this will work

Rainer

vimad · Answer

Rainer,

Thanks for the info. So you are asking me to go with option 2, but if i go with this option will this effect the Production, since we are adding another replication session from A -> C as A is in Production. Also i am referring to the document using celerra replicator V2 are there any other documents or manuals which can give a better understanding on the multi-hop replication (V2.

Rainer_EMC · Answer

yes 'Using Celerra Replicator V2' is what I meant no, adding another replication doenst have an impact on the production A

billstl · Answer

I have a similar situation to the poster, but I have a pretty small pipe between the current Celerra and the Celerra at the DR site. We've installed new Celerras at both sites and plan to migrate from system A to system C using Replicator v2. That will mean we have replication sessions for each file system from A->C and from A->B in place at the same time. Is there some way I can "silver" the new DR Celerra, D, using the old DR Celerra, B?

At the present time, we're planning to use Celerra A as the swing box by replicating to it, then shipping it to the DR site using the "disk copy" method mentioned in the Replicator v2 manual. But with the data already replicated to the DR site, sure would be nice to avoid having to do the physical copy.

I might add that we can take an outage on the primary site over the weekend and make the source file system read only, something that may make this idea more practical.

Thanks!

storagelives · Answer

Does this impact bandwidth of the replication channel? As we are running two replications, A-->B and C-->D ?

Celerra

Celerra Migration options using Celerra Replicator V2

Was this post helpful?