Unsolved
This post is more than 5 years old
50 Posts
1
1510
SRDF/A question about reusing target devs
I am trying to reuse the target R2 devs for another SRDF/A group as below. Not sure if this is possible and I hope someone can answer this.
1. I have SRDF/A group(say group1) with 5 devs. Both source and target devs are on DMX4. It has been running fine and dev pair looks something like this.
Source(DMX4-X) Target(DMX4-Y)
dev1 dev1a
dev2 dev2a
dev3 dev3a
dev4 dev4a
dev5 dev5a
2. Recently moved 3 source devs(dev3, dev4,dev5) to VMAX Tdevs.
3. Deleted the 3 pairs from group1. So group1 has only dev1 & dev2 pairs at present.
4. Now, I am trying to create another SRDF/A group,(say group2) between the VMAX Tdevs and same target devs as in step1.
i.e.,
Source(VMAX) Target(DMX4-Y)
tdev1 dev3a
tdev2 dev4a
tdev3 dev5a
I have the command file as below
convert dev tdev1 to RDF1+R-5,ra_group=XXX,remote_dev=dev3a,invalidate=R2,start_copy=NO;
convert dev tdev2 to RDF1+R-5,ra_group=XXX,remote_dev=dev4a,invalidate=R2,start_copy=NO;
convert dev tdev3 to RDF1+R-5,ra_group=XXX,remote_dev=dev4a,invalidate=R2,start_copy=NO;
But, this fails with below error.
A Configuration Change operation is in progress. Please wait...
Establishing a configuration change session...............Established.
Error occurred while Defining change number 1:
The existing device configuration cannot be converted to the new configurati
on
Device tdev1 generated the failure
Terminating the configuration change session..............Requested.
Terminating the configuration change session..............Done.
The configuration change session has failed.
sauravrohilla
859 Posts
1
October 17th, 2011 05:00
Looks confusing to me..
Few questions for you:
1) Are devices dev3a, 4a, 5a in existing SRDF pairing with other devices?
2) What is the device attribute on these devices? (are these dyn_rdf, rdf2 or none?)
3) Is there a specific reason you are trying to convert tdevs to rdf1 raid 5?
4) What is the existing configuration of tdevs? are these tdevs raid 5?
regards,
Saurabh
RobertDudley
448 Posts
0
October 17th, 2011 06:00
Why not just turn them into dynamic rdf devices with:
set dev xxx:yyy attribute=dyn_rdf;
ADD SRDF GROUP:
symrdf addgrp -label xyz -rdfg # -sid 1234 -dir XX -remote_rdfg # -remote_sid 000123456789 -remote_dir xy
MODIFY SRDF GROUP (To add a director):
symrdf -sid 1234 modifygrp -add -rdfg # -dir xy -remote_dir xy
creating srdf group pairing:
symrdf -sid 1234 createpair -f filename -rdfg # -invalidate r2 -type rdf1 -g groupname
JPP2
50 Posts
0
October 17th, 2011 20:00
Hi Robert,
When I try the command you suggested, it throws this error.
The requested feature is not supported for this microcode or SYMAPI version
SYMCLI Version is as follow.
Symmetrix Command Line Interface (SYMCLI) Version V7.1.1.0 (Edit Level: 1026)
built with SYMAPI Version V7.1.1.0 (Edit Level: 1026)
Thanks,
Julia P.
JPP2
50 Posts
0
October 17th, 2011 20:00
1) Are devices dev3a, 4a, 5a in existing SRDF pairing with other devices?
No. They are not participating in any SRDF.
2) What is the device attribute on these devices? (are these dyn_rdf, rdf2 or none?)
dyn_rdf
3) Is there a specific reason you are trying to convert tdevs to rdf1 raid 5?
Thats a typo. I am trying to convert to RDF1 Tdev.
4) What is the existing configuration of tdevs? are these tdevs raid 5?
Tdev
JPP2
50 Posts
0
October 17th, 2011 22:00
Thanks to both Saurabh and Robert,
I am able to setup the srdf/a between the devs. There were 2 reasons that prevented earlier.
- By mistake, I was converting to RDF1+R-5 instead of RDF1+TDev
- SE 7.1.1 wasn't supporting this setup as I think i am replicating from thin devs to thick devs. So, tried with SE 7.3.0.1 and it worked.
-Julia P.