Unsolved
This post is more than 5 years old
106 Posts
1
24835
VMAX luns: Increasing capacity/migration not an option?
I have a 1.2 TB Raid5 meta device on a VMAXe and I simply wanted to increase the capacity from 1.2TB to 2TB. This seems to be impossible in SMC. I know there "may" be SYMCLI commands to migrate the luns but from what I understand since it's protected via Raid5 the best option I have is to migrate to a Raid 10 or Raid 6 device and then migrate it back to the larger 2TB Raid5 device. This doesn't make logical sense.
Since it's a meta, why can't I simply add in more same-sized meta devices? It's absolutely easy-as-pie on a CX array in Unisphere to increase a lun's capacity without causing any issues to end-users or the server itself. I know the VMAX is an "Enterprise" class array and there are SYMCLI commands to get around this but it seems that this funcationality should be apart of the SMC console to help storage engineers and admins respond to urgent requests when a lun is reaching capacity and needs to be expanded.
ashes1
8 Posts
0
June 5th, 2012 10:00
I think in SMC under provisioning tasks, there is an option called "Add/Remove meta members" whihc you cna use for expanding your meta device.
Or alternatively you can use SYMCLI to expand the meat device. Use the following in the command file :
add dev to meta for conacatnetaed meta.
or
add dev to meta , protect_data=TRUE for striped meta.
jarbarian
106 Posts
0
June 5th, 2012 10:00
In SMC, even though I have already created the same-sized devices that already exist in the META device, they do not appear as an option when trying to expand the meta device in SMC. There’s some issue with protected devices, from what I understand, that you cannot just “expand” a thin lun anytime you want on the VMAX (far different than a CX array). Wondering if someone has any insight if this is true or if I have to go full SYMCLI commands to do something like what I’ve mentioned.
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
June 5th, 2012 12:00
I am not sure what you mean by “protected”
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
June 5th, 2012 12:00
Ok, there have been multiple threads in this forum how to expand devices/metas online while preserving data (using symcli)
jarbarian
106 Posts
0
June 5th, 2012 12:00
Do you have the instructions for this somewhere?
jarbarian
106 Posts
0
June 5th, 2012 12:00
But not through SMC?!
ashes1
8 Posts
0
June 5th, 2012 12:00
Here it is from SMC help pages:
You can add/remove meta members from the meta head level or the Tasks view.
Before you begin
To expand a bound stripped thin metadevice on a Symmetrix array running an Enginuity version earlier than 5875, you must first unbind the device from the pool. This operation is allowed on Symmetrix arrays running Enginuity 5875 or later without having to unbind the device, however, you must select the Protect Data option.
Procedure
To add/remove meta members:
From the Tasks view: In the Operations panel, under Provisioning, click Form FBA Meta to open the Select a Symmetrix and a Meta Device dialog box. Select the Symmetrix array and the Meta Devices on which you want to perform the operation, and click OK.
The Add/Remove Meta Members dialog box opens.
The default values for Reserve and Comments are set in Symmetrix Preferences for device reservations. If the devices are not automatically reserved you can optionally reserve them here.
jarbarian
106 Posts
0
June 5th, 2012 12:00
Negative. Local “file share” meta device. 1.2TB currently and need to expand to 2TB. So far, having trouble using SMC to do it and though I can use SYMCLI, it appears EMC doesn’t want you to expand or modify “protected” devices.
ashes1
8 Posts
0
June 5th, 2012 12:00
What version of SMC are you using?
I am able to expand by R5 protected meta devices using SMC.
I am uing SMC 7.3.2.2
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
June 5th, 2012 12:00
is this device a source for SRDF/Timefinder operations ?
jarbarian
106 Posts
0
June 5th, 2012 12:00
That’s what the devices are. Raid5 protected. I always create the devices as protected devices to keep people from possibly destroying business critical data.
RobertDudley
448 Posts
0
June 6th, 2012 06:00
What type of meeta volumes do you have you are adding to stripped or concatenated? The devices you are trying to add are they just created or have you bound them to a pool? If they are bound to a pool I dont think they will show in the list of devices you can add to a meta.
jarbarian
106 Posts
0
June 6th, 2012 06:00
Not working. Using SMC 7.3.3 now and I’ve created the same size devices to add to the Meta. However, when I follow the steps and get to Step 4, the same sized devices DO NOT show up as available in SMC. In fact when you click the filter there are no devices available even though CLEARLY I can see them as unallocated devices on the array. It doesn’t matter if I change the protection level to Yes or No, SMC still does not show the additional devices to add to the meta. Same size devices that are unallocated so they technically SHOULD show up but do not.
jarbarian
106 Posts
0
June 6th, 2012 07:00
Correct. Striped META bound to the F/C pool. That’s the major issue. This should be something as simple as Unisphere and telling the lun “Go from 1.2TB to 2.0TB”. I know on the old DMX-3s I could easily expand a Meta lun but it wasn’t “pooled” like the VMAX is. It will not let me change the protection level either and yes, we’re running 5875 microcode, latest version.
RobertDudley
448 Posts
0
June 7th, 2012 06:00
Check this primus solution: emc269273 "Symmetrix VMAX: What are the restrictions on thin meta expansion?"
With Solutions Enabler 7.3 and Enginuity 5875.198.148 (or later), EMC will support the use of a thin BCV meta volume while expanding striped thin meta volumes.
Again, prior to Solutions Enabler 7.3, users are not allowed to use thin BCV devices for data protection when expanding thin striped meta volumes (due to an Enginuity limitation).