Primary Storage

  • 1.  volume migration between IO groups

    Posted Mon March 09, 2020 12:28 PM
    Hello.   We will be removing two SVC nodes from our cluster that make up IO Group 2 and we need to migrate all the current volumes that are in that IO group to our other IO Groups.

    What is the best way to accomplish that no impact to the client hosts?

    Our SVC cluster is currently at version 8.2.1.8.

    The documentation says to use 'addvdiskaccess' and then 'movevdisk'.  Then check the client host to see if it detected the new path and volume.

    One point in the documentation that I want to verify is "If there are any host mappings for the volume, the hosts must be members of the target I/O group or the migration fails.".

    So if my client host currently does not have any volumes from IO_grp0 or IO_grp1 (These are the Target IO Groups) should we present one to the client host before hand to make sure the host has access to the Target IO Groups?   
    Alternatively is there a command that would show if I host has access to those Target IO Groups?   (maybe if they had a volume from IO_grp0/1 in the past, but not currently do).

    Thanks!




    ------------------------------
    Brian Brichta
    Storage Engineer Senior
    University of Michigan
    Ann Arbor MI
    ------------------------------

    #PrimaryStorage
    #StorageManagementandReporting
    #Storage


  • 2.  RE: volume migration between IO groups
    Best Answer

    Posted Tue March 10, 2020 07:36 AM

    If your hosts is zoned to nodes for IOGRP1 you should be fine.  The SVC wizard pauses after mapping the volumes.  You will have 4 additional paths to the volume and can verify before continuing the wizard.

    This gives you a chance to verify.  If you can't get zoning verification prior, adding a temp volume from IOGRP1 to verify wouldn't hurt.  Just likely not necessary if your zoning is correct.

    Windows and linux have proven to be a little quicker with recognizing additional paths.  AIX would likely need a kick (cfgmgr) to discover things and validation.

    If moving a boot volume, verify your boot settings and adjust if needed.

     

    Jason Buhr

    Manager Systems Engineer

    Phone: (952) 897-8104

    Cell: (612) 516-6689

    7600 France Ave South
    Edina, MN 55435

    Jason.Buhr@spartannash.com

     

    Image result for facebook logo Image result for linkedin

     


    CONFIDENTIALITY NOTICE: The contents of this email message and any attachments are intended solely for the addressee(s) and may contain confidential and/or privileged information and may be legally protected from disclosure. If you are not the intended recipient of this message or their agent, or if this message has been addressed to you in error, please immediately alert the sender by reply email and then delete this message and any attachments. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibited.



    Original Message


  • 3.  RE: volume migration between IO groups

    Posted Tue March 10, 2020 09:29 AM
    Thanks Jason!   Yes, we zone each of our hosts to all nodes.   Also, lately we have noticed that our windows and linux hosts adapt quickly when there are changes, which is great :)

    -Brian

    ------------------------------
    Brian Brichta
    Storage Engineer Senior
    University of Michigan
    Ann Arbor MI
    ------------------------------

    Original Message


  • 4.  RE: volume migration between IO groups

    Posted Mon October 05, 2020 10:26 AM
    Hi Many of the possible migrations options is covered in the excellent ;-)
    http://www.redbooks.ibm.com/abstracts/sg248470.html?Open

    ------------------------------
    ROGER ERIKSSON
    ------------------------------

    Original Message