UNSOLVED

jarbarian

updated

14 years ago

J

jarbarian

1 Rookie

•

106 Posts

1

25542

June 5th, 2012 10:00

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

    1973

    0

    Posted 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

    1 Rookie

    •

    106 Posts

    1973

    0

    Posted 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

    11 Legend

    •

    20419 Posts

    •

    87439 Points

    1973

    0

    Posted June 5th, 2012 12:00

    I am not sure what you mean by “protected”

  • dynamox

    11 Legend

    •

    20419 Posts

    •

    87439 Points

    1972

    0

    Posted 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

    1 Rookie

    •

    106 Posts

    1610

    0

    Posted June 5th, 2012 12:00

    Do you have the instructions for this somewhere?

  • jarbarian

    1 Rookie

    •

    106 Posts

    1341

    0

    Posted June 5th, 2012 12:00

    But not through SMC?!

  • ashes1

    8 Posts

    979

    0

    Posted 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:

    1. From the meta head: Right-click the meta head device and select FBA Meta Device Configuration, 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.

    1. For striped metas only: Set Protect Data to Yes or No to indicate whether the original striped meta data needs to be protected.
    2. Optional: Filter the Available Unmapped Devices list by clicking the funnel icon filter_button.gif. This will display the Device Filter dialog box, from which you can specify the filter criteria.
    3. Select one or more members from the Available list and click Add to move them to the Selected list, or click Add All to move all members from the Available list to the Selected list.  
    4. Remove members by selecting the devices from the Target list and clicking the <-Remove button to move them to the Available list. Or click <-Remove All to move all the devices to the Available list.
    5. Optional: Reserve the devices by selecting Reserve and entering Comments and an Expiration Date.

      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.
    6. Click Add to Config Session List, and refer to Executing the task list.
  • jarbarian

    1 Rookie

    •

    106 Posts

    1973

    0

    Posted 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

    1972

    0

    Posted 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

    11 Legend

    •

    20419 Posts

    •

    87439 Points

    1973

    0

    Posted June 5th, 2012 12:00

    is this device a source for SRDF/Timefinder operations ?