Unsolved
This post is more than 5 years old
20 Posts
0
2766
March 7th, 2013 08:00
Can expand TDEV striped meta while this is masked to the host and accessed?
Hi
I'm using the protected meta expansion to add a new member to a striped one.
I was seeing that rules permit that the meta device remain mapped during operation, but just was testing it, and I have no possibility to have the lun masked, accessed and modified by the host in this environment. But need to know if it's permitted, and also, if exist any risk doing it.
Obviously, tried to do it mapping the aggregated member, and then failed
SE is 7.5.0.7 and code 5876.159.102.
061D Not Visible ???:? NA:NA TDEV N/Grp'd (M) RW 192000
061E Not Visible ???:? NA:NA TDEV N/Grp'd (m) RW -
061F Not Visible ???:? NA:NA TDEV N/Grp'd NR 96000
0620 Not Visible ???:? NA:NA BCV+TDEV N/Asst'd NR 96000
0621 Not Visible ???:? NA:NA BCV+TDEV N/Asst'd (M) RW 192000
0622 Not Visible ???:? NA:NA BCV+TDEV N/Asst'd (m) RW -
0623 Not Visible ???:? NA:NA BCV+TDEV N/Asst'd NR 96000
0624 Not Visible ???:? NA:NA BCV+TDEV N/Asst'd NR 96000
Situation 1: the meta is mapped.
[ipmroot@ggcbck01:/]symconfigure -sid 0006 -cmd "add dev 61f to meta 61D, pro>
Execute a symconfigure operation for symmetrix '000298700006' (y/ ) ? n
The symconfigure operation will not be executed.
[ipmroot@ggcbck01:/]E, bcv_meta_head=621;" preview <
Execute a symconfigure operation for symmetrix '000298700006' (y/ ) ? y
A Configuration Change operation is in progress. Please wait...
Establishing a configuration change session...............Established.
Processing symmetrix 000298700006
Performing Access checks..................................Allowed.
Checking Device Reservations..............................Allowed.
Locking devices...........................................Locked.
Validating configuration changes..........................Validated.
Closing configuration change request......................Closed.
Terminating the configuration change session..............Done.
The configuration change session has completed successfully.
[ipmroot@ggcbck01:/], bcv_meta_head=621;" prepare <
Execute a symconfigure operation for symmetrix '000298700006' (y/ ) ? y
A Configuration Change operation is in progress. Please wait...
Establishing a configuration change session...............Established.
Processing symmetrix 000298700006
Performing Access checks..................................Allowed.
Checking Device Reservations..............................Allowed.
Locking devices...........................................Locked.
Validating configuration changes..........................Validated.
Closing configuration change request......................Closed.
Terminating the configuration change session..............Done.
The configuration change session has completed successfully.
Situation 2:Both meta and added member are mapped
[ipmroot@ggcbck01:/], bcv_meta_head=621;" prepare <
Execute a symconfigure operation for symmetrix '000298700006' (y/ ) ? y
A Configuration Change operation is in progress. Please wait...
Establishing a configuration change session...............Established.
Error occurred while Defining change number 1:
The specified device must be unmapped before the configuration change can be applied.
Device 061F generated the failure
Terminating the configuration change session..............Done.
The configuration change session has failed.
[ipmroot@ggcbck01:/]symconfigure -sid 0006 -cmd "add dev 61f to meta 61D, pro>
[ipmroot@ggcbck01:/]symconfigure -sid 0006 -cmd "add dev 61f to meta 61D, protect_data=TRUE, bcv_meta_head=621;" prepare
Execute a symconfigure operation for symmetrix '000298700006' (y/ ) ? y
A Configuration Change operation is in progress. Please wait...
Establishing a configuration change session...............Established.
Error occurred while Defining change number 1:
The specified device must be unmapped before the configuration change can be applied.
Device 061F generated the failure
Terminating the configuration change session..............Done.
The configuration change session has failed.
[ipmroot@ggcbck01:/]symconfigure -sid 0006 -cmd "add dev 61f to meta 61D, protect_data=TRUE, bcv_meta_head=621;" prepare
Execute a symconfigure operation for symmetrix '000298700006' (y/ ) ? y
A Configuration Change operation is in progress. Please wait...
Establishing a configuration change session...............Established.
Error occurred while Defining change number 1:
The specified device must be unmapped before the configuration change can be applied.
Device 061F generated the failure
Terminating the configuration change session..............Done.
The configuration change session has failed.
Situation 3: Unmap 61f
[ipmroot@ggcbck01:/]symconfigure -sid 0006 -cmd "add dev 61f to meta 61D, protect_data=TRUE, bcv_meta_head=621;" prepare
Execute a symconfigure operation for symmetrix '000298700006' (y/ ) ? y
A Configuration Change operation is in progress. Please wait...
Establishing a configuration change session...............Established.
Processing symmetrix 000298700006
Performing Access checks..................................Allowed.
Checking Device Reservations..............................Allowed.
Locking devices...........................................Locked.
Validating configuration changes..........................Validated.
Closing configuration change request......................Closed.
Terminating the configuration change session..............Done.
The configuration change session has completed successfully.
[ipmroot@ggcbck01:/]symconfigure -sid 0006 -cmd "add dev 61f to meta 61D, protect_data=TRUE, bcv_meta_head=621;" commit
Execute a symconfigure operation for symmetrix '000298700006' (y/ ) ? y
A Configuration Change operation is in progress. Please wait...
Establishing a configuration change session...............Established.
Processing symmetrix 000298700006
Performing Access checks..................................Allowed.
Checking Device Reservations..............................Allowed.
Locking devices...........................................Locked.
Initiating COMMIT of configuration changes................Started.
Committing configuration changes..........................Queued.
COMMIT requesting required resources......................Obtained.
Step 004 of 094 steps.....................................Executing.
Step 010 of 094 steps.....................................Executing.
Step 010 of 094 steps.....................................Executing.
Step 055 of 094 steps.....................................Executing.
Step 060 of 094 steps.....................................Executing.
Step 060 of 094 steps.....................................Executing.
Step 066 of 096 steps.....................................Executing.
Step 066 of 096 steps.....................................Executing.
Step 066 of 096 steps.....................................Executing.
Step 066 of 096 steps.....................................Executing.
Step 066, substep 1.......................................Executing.
Step 066, substep 1.......................................Executing.
Step 066, substep 1.......................................Executing.
Step 066, substep 1.......................................Executing.
Step 066, substep 2.......................................Executing.
Step 066, substep 2.......................................Executing.
Step 066, substep 2.......................................Executing.
Step 066, substep 2.......................................Executing.
Step 066, substep 3.......................................Executing.
Step 066, substep 3.......................................Executing.
Step 066, substep 3.......................................Executing.
Step 066, substep 3.......................................Executing.
Step 066, substep 4.......................................Executing.
Step 066, substep 4.......................................Executing.
Step 066, substep 4.......................................Executing.
Step 066, substep 4.......................................Executing.
Step 066, substep 5.......................................Executing.
Step 066, substep 5.......................................Executing.
Step 066, substep 5.......................................Executing.
Step 066, substep 5.......................................Executing.
Step 066, substep 6.......................................Executing.
Step 066, substep 6.......................................Executing.
Step 066, substep 6.......................................Executing.
Step 066, substep 7.......................................Executing.
Step 066, substep 7.......................................Executing.
Step 066, substep 7.......................................Executing.
Step 066, substep 7.......................................Executing.
Step 066, substep 8.......................................Executing.
Step 066, substep 8.......................................Executing.
Step 066, substep 8.......................................Executing.
Step 066, substep 8.......................................Executing.
Step 066, substep 9.......................................Executing.
Step 066, substep 9.......................................Executing.
Step 066, substep 9.......................................Executing.
Step 066, substep 9.......................................Executing.
Step 074 of 096 steps.....................................Executing.
Step 083 of 096 steps.....................................Executing.
Step 083 of 096 steps.....................................Executing.
Step 083 of 096 steps.....................................Executing.
Step 083 of 096 steps.....................................Executing.
Step 083 of 096 steps.....................................Executing.
Step 083, substep 1.......................................Executing.
Step 083, substep 1.......................................Executing.
Step 083, substep 1.......................................Executing.
Step 083, substep 1.......................................Executing.
Step 083, substep 2.......................................Executing.
Step 083, substep 2.......................................Executing.
Step 083, substep 2.......................................Executing.
Step 083, substep 2.......................................Executing.
Step 083, substep 3.......................................Executing.
Step 083, substep 3.......................................Executing.
Step 083, substep 3.......................................Executing.
Step 083, substep 3.......................................Executing.
Step 083, substep 4.......................................Executing.
Step 083, substep 4.......................................Executing.
Step 083, substep 4.......................................Executing.
Step 083, substep 4.......................................Executing.
Step 093 of 096 steps.....................................Executing.
Local: COMMIT............................................Done.
Terminating the configuration change session..............Done.
The configuration change session has successfully completed.
[ipmroot@ggcbck01:/]
061D Not Visible ***:* NA:NA TDEV N/Grp'd (M) RW 288000
061E Not Visible ***:* NA:NA TDEV N/Grp'd (m) RW -
061F Not Visible ***:* NA:NA TDEV N/Grp'd (m) RW -
0620 Not Visible ???:? NA:NA BCV+TDEV N/Asst'd NR 96000
0621 Not Visible ???:? NA:NA BCV+TDEV N/Asst'd (M) RW 192000
0622 Not Visible ???:? NA:NA BCV+TDEV N/Asst'd (m) RW -
0623 Not Visible ???:? NA:NA BCV+TDEV N/Asst'd NR 96000
0624 Not Visible ???:? NA:NA BCV+TDEV N/Asst'd NR 96000
Can anyone confirm the way to do it without risk?
With regards
AlanZ1
790 Posts
0
March 7th, 2013 08:00
Your question has been moved to the Symmetrix Support Forum where it has a better chance of being seen and answered
SYMCLIGuy
98 Posts
0
March 7th, 2013 13:00
There is only one way to do this while keeping the original device online. The device(s) being added to the striped meta need to be unmapped/unmasked - they should not be in use anywhere. The BCV being used to protect the data should also not be in use anywhere. The meta configuration of the BCV should match that of the production meta pre-expansion, in terms of meta members and meta member size. If the BCV being used is also a thin device, it needs to be persistently preallocated prior to the expansion being started.
This process is followed by many customers and has been performed successfully many, many times.
The process is not 100% risk free, but there is no additional risk to doing it online vs taking the production device offline and running the expansion.
xsalvia_24eea4
20 Posts
0
March 8th, 2013 02:00
Thanks for the reply, I was asking it via support chat, but I think that we had a confussion about offline device, because the requirement is that the added member must be offline, not the production device.
If to have the production dev offline was mandatory, I should lose credibility with Symmetrix products ... right? Since under VNX environments this is a usual task and online task too....
With regards
sauravrohilla
859 Posts
0
March 8th, 2013 03:00
It was too much of reading for me
what i understand that you are trying to expand the thin meta online? The new member that you want to add should not be mapped/masked. Thats why u got the failure in situation 2.
regards,
Saurabh
xsalvia_24eea4
20 Posts
0
March 11th, 2013 03:00
Hi Saurabh
Yes, it was just demonstration about that device to be added to the meta needs to be unmasked/unmapped.
In fact, question was about the meta to be expanded, if could be masked/mapped and accessed by the host during the expansion..
Thanks for your reply.
sauravrohilla
859 Posts
0
March 11th, 2013 22:00
Yes, the meta expansion is an online process now but recommendations is to try when there are less IOs on the device as mentioned bySYMCLIGuy
regards,
Saurabh