This post is more than 5 years old
15 Posts
0
5522
March 22nd, 2013 13:00
Removing device group and dissolving R1/R2 relationship
I have a device group that is no longer need. I removed all the devices from the device group and deleted the device group. I unmasked and unmapped all the devices that were in the device group (Standard volumes and R1-BCV's). Now I want to dissolve the R1/R2 relationship so I can reuse these volumes as standard RAID+5 volumes. The R1-BCV volumes need to be converted to Standare RAID+5 volumes. What is the correct procedure to accomplish this? This is what I have tried:
symrdf -file aaa -sid 1033 -RDFG 4 deletepair -force
Where aaa consistes of the local R1-BCV and the remote R2-STD in the form of 05cf 0133
This worked fine. Then when I tried to convert the R1-BCV to a STD RAID+5 through Control Center, it would give me an error:
SYMAPI Error - SYMAPI_C_CFG_COMMIT_FAILED
SYMAPI_C_SRVR_INVALID_CONFIG
Configuration Server Error Num - 0x8703
Configuration Server Error - The state of a snap session is
blocking the activation of the new configuration. Please see
the API log file
Check the SYMAPI Log for more details and call EMC Customer Support
I called customer support and they told me to cancel the session using the following command:
symmir -sid 1033 -f bbb cancel
Where bbb consist of the R2-STD R1-BCV in the form of 0133 05cf
This worked on the first volume of the device group so I tried it again on another volume from the old device group. I did the same steps and when I did the symmir -sid 1033 -f bbb cancel with the new R2-STD R1-BCV in the file bbb consisted on 0134 05d0 it gave me this error:
Cannot operate on the device because it is a 'META MEMBER'
This device is not a META device. I have tried several other devices using this procedure and get the same error. Am I not using the proper procedure to delete the R1/R2 relationship in order to convert the R1-BCV to a STD
cincystorage
2 Intern
•
467 Posts
0
March 23rd, 2013 04:00
symmir is specific to the BCV relationship - not the srdf pairing. Just to verify, here is the setup for the first lun:
DEV: 0385
BCV R1: 05d0
R2: 0134
Is that right? Which relationship are you trying to break, the BCV -> R2 SRDF pairing or the R1 -> BCV pairing?
If you want to break the RDF pairing between 05d0 and 0134 you should be able to do this:
symrdf -sid 1033 -f devicemap.cfg -rdfg 4 split -force
Where device map.cfg " " is:
05d0 0134
That will force srdf it into split mode. You aren't using dynamic srdf, so you need to use symconfigure to convert the device to the mode you want. If you want it to be just an BCV (maintain the relationship between 0385 and 05d0) you need to make a test config file as such:
convert dev 05d0 to BCV+R5
If you want to destroy the relationship between 0385 and 05d0 as well, you create you config file like this:
convert dev 05d0 to 2-way-mir
Then to run your symconfigure, start with a preview:
symconfigure -sid 1033 -f configfileyoujustmade.text preview
If it works do a prepare / commit and you should be good to go - but keep in mind all data on the BCV and R2 will be lost, so make sure you really want to do this.
jnaylor
15 Posts
0
March 22nd, 2013 13:00
Vipin,
I am new to this forum. How do I move this discussion to Symmetrix Support Forum? I have posted the symdev show for both volumes.
symdev -sid 1033 show 05d0
Device Physical Name : Not Visible
Device Symmetrix Name : 05D0
Device Serial ID : N/A
Symmetrix ID : 000190301033
Attached VDEV TGT Device : N/A
Vendor ID : EMC
Product ID : SYMMETRIX
Product Revision : 5773
Device WWN : 60060480000190301033533030354430
Device Emulation Type : FBA
Device Defined Label Type: N/A
Device Defined Label : N/A
Device Sub System Id : 0x0001
Cache Partition Name : DEFAULT_PARTITION
Device Block Size : 512
Device Capacity
{
Cylinders : 9207
Tracks : 138105
512-byte Blocks : 17677440
MegaBytes : 8632
KiloBytes : 8838720
}
Device Configuration : RDF1-BCV+R-5 (Non-Exclusive Access)
Device is WORM Enabled : No
Device is WORM Protected : No
SCSI-3 Persistent Reserve: Disabled
Dynamic Spare Invoked : No
Dynamic RDF Capability : None
STAR Mode : No
STAR Recovery Capability : None
STAR Recovery State : NA
Device Service State : Normal
Device Status : Ready (RW)
Device SA Status : N/A (N/A)
Mirror Set Type : [RAID-5,R2 Remote,RAID-5,N/A]
Mirror Set DA Status : [RW,NR,RW,N/A]
Mirror Set Inv. Tracks : [0,8,0,0]
Back End Disk Director Information
{
Hyper Type : RAID-5
Hyper Status : Ready (RW)
Disk [Director, Interface, TID] : [N/A,N/A,N/A]
Disk Director Volume Number : N/A
Hyper Number : N/A
Hyper Type : R2 Remote
Hyper Status : Not Ready (NR)
Disk [Director, Interface, TID] : [N/A,N/A,N/A]
Disk Director Volume Number : N/A
Hyper Number : N/A
Hyper Type : RAID-5
Hyper Status : Ready (RW)
Disk [Director, Interface, TID] : [N/A,N/A,N/A]
Disk Director Volume Number : N/A
Hyper Number : N/A
}
RAID-5 Device Information
{
Number of Tracks in a Stripe : 4
Overall Ready State of RAID-5 Device : ReadyNoOtherMirror
Overall WriteProtect State of RAID-5 Device : EnabledNoOtherMirror
Member Number of the Failing Device : None
Member Number that Invoked the Spare : None
Disk Director (DA) that Owns the Spare : Inv
Copy Direction : N/A
RAID-5 Hyper Devices (3+1):
{
Device : 05D0
{
--------------------------------------------------------------
Disk DA Hyper Member Spare Disk
DA :IT Vol# Num Cap(MB) Num Status Status Grp# Cap(MB)
--------------------------------------------------------------
01A:C0 66 66 2878 3 RW N/A 1 286102
15A:C0 66 66 2878 4 RW N/A 1 286102
02B:D1 650 66 2878 2 RW N/A 1 286102
16B:D1 650 66 2878 1 RW N/A 1 286102
}
}
}
BCV Pair Information
{
Standard (STD) Device Symmetrix Name : 0385
Standard (STD) Device Serial ID : Not Visible
Standard (STD) Device Group Name : Not/Grouped
Standard (STD) Composite Group Name : Not/Grouped
BCV Device Symmetrix Name : 05D0
BCV Device Serial ID : Not Visible
BCV Device Associated Group Name : Not/Associated
BCV Device Associated CG Name : Not/Associated
BCV Device Status : Ready (RW)
State of Pair ( STD <=\=> BCV ) : Split
Time of Last BCV Action : Fri Aug 24 19:08:47 2012
State of BCV Mirrors : Synchronized
BCV State Flags : (AllReady)(Emulation)
Percent Split : 100%
Number of Inv. Tracks for STD Device : 0
Number of Inv. Tracks for BCV Device : 0
}
RDF Information
{
Device Symmetrix Name : 05D0
RDF Type : R1
RDF (RA) Group Number : 4 (03)
Remote Device Symmetrix Name : 0134
Remote Symmetrix ID : 000190300840
R2 Device Is Larger Than The R1 Device : False
RDF Pair Configuration : Normal
RDF STAR Mode : False
RDF Mode : Adaptive Copy
RDF Adaptive Copy : Enabled: Disk Mode
RDF Adaptive Copy Write Pending State : N/A
RDF Adaptive Copy Skew (Tracks) : 65535
RDF Device Domino : Disabled
RDF Link Configuration : Fibre
RDF Link Domino : Disabled
Prevent Automatic RDF Link Recovery : Enabled
Prevent RAs Online Upon Power ON : Enabled
Device RDF Status : Ready (RW)
Device SA Status : N/A (N/A)
Device RA Status : Ready (RW)
Device Link Status : Not Ready (NR)
Device Suspend State : Offline
Device Consistency State : Disabled
RDF R2 Not Ready If Invalid : Disabled
Device RDF State : Ready (RW)
Remote Device RDF State : Write Disabled (WD)
RDF Pair State ( R1 <- -> R2 ) : Suspended
Number of R1 Invalid Tracks : 0
Number of R2 Invalid Tracks : 8
RDFA Information:
{
Session Number : 3
Cycle Number : 0
Number of Devices in the Session : 99
Session Status : Inactive
Session Consistency State : N/A
Minimum Cycle Time : 00:00:30
Average Cycle Time : 00:00:00
Duration of Last cycle : 00:00:00
Session Priority : 33
Tracks not Committed to the R2 Side: 0
Time that R2 is behind R1 : 00:00:00
R2 Image Capture Time : N/A
R1 Side Percent Cache In Use : 0
R2 Side Percent Cache In Use : 0
Transmit Idle Time : 00:00:00
R1 Side DSE Used Tracks : 0
R2 Side DSE Used Tracks : 0
}
}
root@docvault:[/usr/emc/tmp/cmdfiles]
#
# symdev -sid 0840 show 0134
Device Physical Name : Not Visible
Device Symmetrix Name : 0134
Device Serial ID : N/A
Symmetrix ID : 000190300840
Attached BCV Device : N/A
Attached VDEV TGT Device : N/A
Vendor ID :
Product ID :
Product Revision :
Device WWN : 60060480000190300840533030313334
Device Emulation Type : FBA
Device Defined Label Type: N/A
Device Defined Label : N/A
Device Sub System Id : 0x0001
Cache Partition Name : DEFAULT_PARTITION
Device Block Size : 512
Device Capacity
{
Cylinders : 9207
Tracks : 138105
512-byte Blocks : 17677440
MegaBytes : 8632
KiloBytes : 8838720
}
Device Configuration : RDF2+R-5 (Non-Exclusive Access)
Device is WORM Enabled : No
Device is WORM Protected : No
SCSI-3 Persistent Reserve: Disabled
Dynamic Spare Invoked : No
Dynamic RDF Capability : None
STAR Mode : No
STAR Recovery Capability : None
STAR Recovery State : NA
Device Service State : Normal
Device Status : Write Disabled (WD)
Device SA Status : Ready (RW)
Front Director Paths (3):
{
----------------------------------------------------------------------
POWERPATH DIRECTOR PORT LUN
--------- ---------- ---- -------- ---------
PdevName Type Type Num Sts VBUS TID SYMM Host
----------------------------------------------------------------------
Not Visible N/A FA 01C:0 RW 001 03 001 N/A
Not Visible N/A FA 16C:0 RW 001 03 001 N/A
Not Visible N/A FA 16C:1 RW 001 03 001 N/A
}
Mirror Set Type : [R1 Remote,RAID-5,RAID-5,N/A]
Mirror Set DA Status : [NR,RW,RW,N/A]
Mirror Set Inv. Tracks : [0,0,0,0]
Back End Disk Director Information
{
Hyper Type : R1 Remote
Hyper Status : Not Ready (NR)
Disk [Director, Interface, TID] : [N/A,N/A,N/A]
Disk Director Volume Number : N/A
Hyper Number : N/A
Hyper Type : RAID-5
Hyper Status : Ready (RW)
Disk [Director, Interface, TID] : [N/A,N/A,N/A]
Disk Director Volume Number : N/A
Hyper Number : N/A
Hyper Type : RAID-5
Hyper Status : Ready (RW)
Disk [Director, Interface, TID] : [N/A,N/A,N/A]
Disk Director Volume Number : N/A
Hyper Number : N/A
}
RAID-5 Device Information
{
Number of Tracks in a Stripe : 4
Overall Ready State of RAID-5 Device : Ready
Overall WriteProtect State of RAID-5 Device : Enabled
Member Number of the Failing Device : None
Member Number that Invoked the Spare : None
Disk Director (DA) that Owns the Spare : Inv
Copy Direction : N/A
RAID-5 Hyper Devices (3+1):
{
Device : 0134
{
--------------------------------------------------------------
Disk DA Hyper Member Spare Disk
DA :IT Vol# Num Cap(MB) Num Status Status Grp# Cap(MB)
--------------------------------------------------------------
01A:D3 522 13 2878 1 RW N/A 1 286102
02A:C5 217 13 2878 2 RW N/A 1 286102
01B:D4 604 13 2878 3 RW N/A 1 286102
15B:D4 604 13 2878 4 RW N/A 1 286102
}
}
}
BCV Pair Information
{
Standard (STD) Device Symmetrix Name : 0134
Standard (STD) Device Serial ID : Not Visible
Standard (STD) Device Group Name : Not/Grouped
Standard (STD) Composite Group Name : Not/Grouped
BCV Device Symmetrix Name : 01FA
BCV Device Serial ID : Not Visible
BCV Device Associated Group Name : Not/Associated
BCV Device Associated CG Name : Not/Associated
BCV Device Status : Ready (RW)
State of Pair ( STD <=\=> BCV ) : Split
Time of Last BCV Action : Fri Aug 24 19:19:16 2012
State of BCV Mirrors : Synchronized
BCV State Flags : (AllReady)(Emulation)
Percent Split : 100%
Number of Inv. Tracks for STD Device : 0
Number of Inv. Tracks for BCV Device : 0
}
RDF Information
{
Device Symmetrix Name : 0134
RDF Type : R2
RDF (RA) Group Number : 4 (03)
Remote Device Symmetrix Name : 05D0
Remote Symmetrix ID : 000190301033
R2 Device Is Larger Than The R1 Device : False
RDF Pair Configuration : Normal
RDF STAR Mode : False
RDF Mode : Adaptive Copy
RDF Adaptive Copy : Enabled: Disk Mode
RDF Adaptive Copy Write Pending State : N/A
RDF Adaptive Copy Skew (Tracks) : 65535
RDF Device Domino : Disabled
RDF Link Configuration : Fibre
RDF Link Domino : Disabled
Prevent Automatic RDF Link Recovery : Enabled
Prevent RAs Online Upon Power ON : Enabled
Device RDF Status : Ready (RW)
Device SA Status : Ready (RW)
Device RA Status : Write Disabled (WD)
Device Link Status : Not Ready (NR)
Device Suspend State : Offline
Device Consistency State : Disabled
RDF R2 Not Ready If Invalid : Disabled
Device RDF State : Write Disabled (WD)
Remote Device RDF State : Ready (RW)
RDF Pair State ( R1 <- -> R2 ) : Suspended
Number of R1 Invalid Tracks : 0
Number of R2 Invalid Tracks : 0
RDFA Information:
{
Session Number : 3
Cycle Number : 0
Number of Devices in the Session : 99
Session Status : Inactive
Session Consistency State : N/A
Minimum Cycle Time : 00:00:30
Average Cycle Time : 00:00:00
Duration of Last cycle : 00:00:00
Session Priority : 33
Tracks not Committed to the R2 Side: 0
Time that R2 is behind R1 : 00:00:00
R2 Image Capture Time : N/A
R1 Side Percent Cache In Use : 0
R2 Side Percent Cache In Use : 0
Transmit Idle Time : 00:00:00
R1 Side DSE Used Tracks : 0
R2 Side DSE Used Tracks : 0
}
}
root@docvault:[/usr/emc/tmp/cmdfiles]
jnaylor
15 Posts
0
March 22nd, 2013 13:00
Vipin,
I believe I figured out how to move it and I did move it. Thanks.
Vipin VK
2 Intern
•
812 Posts
0
March 22nd, 2013 13:00
Please move this discussion to Symmetrix Support Forum,. It is always better to post in product support forums to get suggestion from experts.
Can you post the symdev show output for 0134 and 05d0 ? So that we can confirm those are not part of any meta.
dynamox
9 Legend
•
20.4K Posts
0
March 23rd, 2013 06:00
data will be lost when converting/deleting relationship between devices ? Since when ?
cincystorage
2 Intern
•
467 Posts
0
March 23rd, 2013 09:00
You're right, I wasn't thinking that early in the morning!
jnaylor
15 Posts
0
March 25th, 2013 06:00
Ok. I did the split, I converted to dynamic rdf, then converted from rdf to BCV+R-5. Not problems. Since this is a RAID-5 and not a 2-way-mir, I did convert dev 5d0 to RAID-5. It ran through the preview and the prepare but on the commit on step 08 I get this error:
Validating configuration changes..........................Validated.
Initiating PREPARE of configuration changes...............Prepared.
Initiating COMMIT of configuration changes................Queued.
COMMIT requesting required resources......................Obtained.
Step 008 of 028 steps.....................................Executing.
Step 008 of 028 steps.....................................Executing.
COMMIT monitoring failed
Error occurred while Committing
The state of a snap session is blocking the activation of the new configuration. Please see the API log file
Closing configuration change request......................Closed.
Terminating the configuration change session..............Done.
The configuration change session has failed.
The API log file give the same error message.
jnaylor
15 Posts
1
March 25th, 2013 07:00
I figured out why I was getting the snap error. I had to run the command symmir -sid 1033 -f bbb cancel, where bbb consisted of the local standard and the local bcv 05d0 0385. After I did that then I was able to convert 05d0 to a standard RAID-5. Thank for your help on the rest of the procedure.