Start a Conversation

Unsolved

This post is more than 5 years old

985

March 20th, 2012 14:00

Partial RecoverPoint Failover w/ SRM

Hi Guys,

I have a customer who already has some CX4s & CX3s running through a couple RP appliances to a remote site which work great.

They have a new VNX5500 they want to replicate to the same remote site through the same appliances to a new VNX5500 on the other site.  I assume this is supported (assuming sufficient power remaining on the RP appliances).

But my big question is this:  Can SRM control the failover of just the VNX's and do the right thing without affecting the CX replications?  I would think we can, but want to check.

Thanks.

1K Posts

March 20th, 2012 17:00

I'm not quite sure I follow this: "They have a new VNX5500 they want to replicate to the same remote site through the same appliances to a new VNX5500 on the other site"

Are you saying that you have two VNX5500 at the same site?

2 Intern

 • 

199 Posts

March 20th, 2012 18:00

I think Matt means he has 2 VNX5500 on different sites.

Matt, I believe you need to set VNX volumes as one CG, CX volumes as a different CG. You can certianly only do the SRM failover only on VNX CG and leave CX CG replicating from PR site to DR site.

61 Posts

March 21st, 2012 13:00

Jingyi is correct - two VNX5500s, one at each site.

As long as RP can do the failover individually for the individual CGs, I should be good.

2 Intern

 • 

199 Posts

March 27th, 2012 00:00

I have checked some RP documents and found the following statement "The process of changing the replication direction between the production copy and a replica copy. Failing over a consistency group to a local or remote replica allows system operations to continue as usual from the replica. "

It suggested CGs are working separately,  you can go to the following link for more information.

http://powerlink.emc.com/km/appmanager/km/secureDesktop?_nfpb=true&_pageLabel=servicesDocLibPg&internalId=0b014066800f5181&_irrt=true

RecoverPoint Internal Glossary of Terms  -- A05

No Events found!

Top