Unsolved

This post is more than 5 years old

1224

August 27th, 2009 06:00

Can a SRDF DG have devs replicating using different RDFG's ?

My first post here :-)

Following is my setup...

1. This is SRDF/A
2. Server-A's devices are in DG-A and the devs are replicating via rdfg # X
3. Server-B's devices are in DG-B and the devs are replicating via rdfg # Y
4. Now I need to move a couple of devs from server-A to server-B and eventually will also need to move them from DG-A to DG-B

This will result in a situation where DG-B will have devs from two different RDFG's - X and Y.

Is it possible first of all ?

If Yes, are there any disadvantages ?

If No, I think I should do a deletepair for those two devices and then createpair using rdfg # Y. Am I correct here ?

6 Operator

 • 

2.8K Posts

August 27th, 2009 06:00

Hi MahendranVijay, welcome to our forums !! :D
Please spend a few minutes and explore our Coffee Break area and eventually introduce yourself in the "Who I am" thread :-)

If you have 2 hosts, each with its own DG and its own RDFG, I'd suggest that you move the pairs from RDFGX to RDFGY and while deleting/creating pairs you also move the devices from DG-A to DG-B.

If you are running code 5773 or later you can also use the "movepair" feature.

August 27th, 2009 07:00

Hi Stefano...many thanks...that answers my questions.......

So unless I have 5773, I need to manually remove devs from DG-A ,deletepair, createpair(using RDFG-Y) and then add to DG-B.

Movepair is really a good one :-)

Thanks again.

I did not expect my questions will be answered so soon...I appreciate.

6 Operator

 • 

2.8K Posts

August 27th, 2009 07:00

1) no, I'm simply saying you have to move devices between RDFGs :-) ... thus moving devices from DG-A to DG-B is simply another command you have to issue between deletepair and createpair ;-)

2) symrdf movepair will move devices between different RDFGs without requiring a deletepair and a subsequent createpair (with the associated full establish)

3) symrdf movepair requires code 5773. And please always use recent S.E. (7.0 onward)

6 Operator

 • 

2.8K Posts

August 27th, 2009 07:00

You can always wait a few more hours.. Right now US is waking up (ahemmm they are already up and awake to be honest) and possibly someone else may give you better/different answers... :-)

I agree, movepair is really useful!

August 27th, 2009 07:00

Thanks very much Stefano...yeah lemme check out the coffee break forum...

1. So in essence, do you mean a single DG cannot have devs from different RDFG's ?

2. "movepiar" will move devices between DG's or RDFG's ?

3. which symcli version is having this "movepair" feature ?

6 Operator

 • 

2.1K Posts

August 28th, 2009 13:00

I would have to test to confirm, but I believe you CAN have devices from different RDF groups in the same DG. The problem is that in SRDF/A mode (we don't use SRDF/S so I'm not sure about that) having the devices in the same group basically means you can't issue RDF commands against that group. Most (if not all) RDF commands require that you act on an entire RDF Group if it is in Async mode.

Unless this has changed with 5773 and SE 7... the last time I tried this was with 5771 and SE 6.3.x

August 28th, 2009 20:00

Curious to know the results .... :-)

30 Posts

August 28th, 2009 21:00

Allen is correct. Once you change the RDF group for one of the pairs in your device group, you will not be able to issue an SRDF/A establish, etc. SRDF/A executes on an entire RDF group, for consistency. Having a single pair out of all the pairs in the group not in the same state is not a valid situation.

You do not want to be able to issue an establish on a device group when only a portion of an RDF group is in that device group. That would be a bad thing. The device group is merely a mechanism for issuing a command against a group of devices.

My suggestion is, if your Enginuity code level supports a movepair operation, do that, then remove the pair from the old group, then delete them from the old device group and add them to the new group. If it does not, then perform a delete pair, then createpair, then do your device group manipulation.

By the way, this only applies to SRDF/A. Sync, ACP, semi-sync, all operate on a pair-by-pair basis.

6 Operator

 • 

2.8K Posts

August 31st, 2009 01:00

The problem is that in SRDF/A mode having the
devices in the same group basically means you can't
issue RDF commands against that group. Most (if not
all) RDF commands require that you act on an entire
RDF Group if it is in Async mode.


And that's exactly why I'm suggesting what I suggested ;-)
Let's use KISS philosophy and move devs between DGs while creating pairs :D

BTW with SRDF/S you can susp/resume/failover/failback any device in a RDFG, regardless of what you do with other devices. In a single RDFG you can have a few devices failed over to their R2 side, a few other actively pushing data to R2 and another set of devices suspended on the link.

September 1st, 2009 04:00

Stefano/Scott/Allen,

Thanks all for your valuable inputs.
No Events found!

Top