Unsolved

This post is more than 5 years old

2 Intern

 • 

70 Posts

1220

October 7th, 2009 08:00

Question about concurrent SRDF

I have 2 DMX-4 arrays and I want to make 2 separate SRDF copies of the same lun on our primary site. So, I have a database on our primary site and an SRDF copy in our DR site. I want to create a second SRDF copy on the DR site.

We're going to do DR testing. My plan is to split the current SRDF pair so I can mount the copy up on a machine in our DR site. This process is all configured already. The devices are paired, mapped and masked in DR and we've confirmed that this process works. The only problem is that for the weekend of testing, if I do a split of the database, during the entire time of the split we are working without a fully up to date copy of our production database. So, my plan was to create a second SRDF copy that will stay established through the weekend. That way, if there is a true failure during testing, we'll still have that up-to-the-minute copy sitting in DR that we can access and no data will be lost.

Someone mentioned that we can use concurrent SRDF, but all of the docs I've seen talk about this being used in a 3 array configuration where each SRDF copy is on a separate array.

6 Operator

 • 

2.8K Posts

October 10th, 2009 10:00

Touphaz unfortunatly I don't have a testbed available .. But I guess you can create concurrent RDF pairs with two different R2 devices in the same remote frame.

I guess you have to create new RDF groups (and use different RDFg for new pairs) but with recent codes it's quite easy and cheap ;-)

2 Intern

 • 

1.3K Posts

October 11th, 2009 03:00

Not configured the concurrent RDF on the same remote frame so far. So it would be interesting to know the result..

6 Operator

 • 

2.8K Posts

October 12th, 2009 07:00

If you have a couple of RDF paired boxes and want to borrow me an access to your network I'd run a couple of tests with you ;-)

1 Message

October 12th, 2009 16:00

if i understand this correctly you want a copy of your production data available to perform a DR test against and still have a replicating copy of the data. The way we accomplish that is to create a BCV of the R2. Establish the BCV to the R2, once in sync, quiesce the DB on the R1 side, split the BCV, mount the BCV to your DR host and test away once done you can blow the BCV away.

6 Operator

 • 

2.8K Posts

October 13th, 2009 08:00

Hi RAW! Welcome to our forums. Please introduce yourself in the Coffee break area as soon as you have a few spare minutes :-)

You are suggesting the good old "golden copy" that EMC is pushing since ages. But the real issue here is that existing procedures manage directly the R2 devices and changing the procedures to manage BCV devices may be a pain...
And considere that the "golden copy" is mostly used when you restart the replica after a real disaster since you are trying to keep a consistent copy of your R2 devices while you mangle them with adaptive copy ;-)

1 Message

October 22nd, 2009 02:00

What is about using the cloning feature, instead of BCVs or concurrent SRDF? All you need is an active cloning license. So you are able to use the actual working SRDF-pair in a desaster and you will have a relevant copy of your data an the DR-site.
We use this feature to automate our SAP-systemcopies from the R2-site.

2 Intern

 • 

292 Posts

October 27th, 2009 15:00

redfly, welcome to the forums. Be sure to introduce yourself in the coffee break area when you get the chance.

2 Intern

 • 

155 Posts

November 3rd, 2009 09:00

The following document may help you to acheive what you need after creating a consistency group. using SRDF/S and SRDF/A consider territial site C as another R2copy.

http://www.dg.com/collateral/hardware/white-papers/300-006-714-srdf-zero-data-loss-solutions-ext-distance-replication.pdf
No Events found!

Top