SAN_AK

updated

16 years ago

S

SAN_AK

2 Intern

125 Posts

0

4178

November 12th, 2010 16:00

Migrating to V-Max

Planning to migrate from HP EVA6000, DS4800 to VMAX SE with brocade fabric, suggestions, experiences..best practices..and possible approaches..?

  • dynamox

    11 Legend

    20419 Posts

    87439 Points

    2056

    0

    Posted November 15th, 2010 17:00

    AIX - use internal mirroring, piece of cake for any AIX admin and system never goes down. Do make sure you have the latest ODM and PowerPath installed.

    ESX and Windows - use Open Replication. Windows will not care that storage change, ESX altought will, be prepared to export all VMs from the inventory , re-signature VMFS file systems and re-register all VMs.  Also make sure to set connect FA/host_hba flags on VMAX. Download Open Replicator manual and they have a lot of examples to walk you step by step through zoning requirements, hot pull vs cold pull ..etc

  • dynamox

    11 Legend

    20419 Posts

    87439 Points

    2057

    1

    Posted November 14th, 2010 19:00

    what OS ?

  • xe2sdc

    6 Operator

    2831 Posts

    2057

    1

    Posted November 15th, 2010 03:00

    I bet the tool may be Open Replicator. But as Dynamox said, it depends on the OS. A few OS's can mirror their data online. If your OSs supports online mirroring (and un-mirroring) you can easily migrate without disruptions. If your OS don't support mirroring, you pull data from old storage to VMax with Open Replicator, change zoning from old storage to new storage and reboot the servers... Looks easy? It isn't easy at all. But you are talking about storages, luns and similar things. :-)

  • emcsanadmin

    54 Posts

    2056

    0

    Posted November 15th, 2010 06:00

    1. you can OS level copy as well using rsync in unix .

    2. array level migration using Open replicator if u r willing to buy the license or using open migrator it is also a emc tool u need to purchase.......

  • xe2sdc

    6 Operator

    2831 Posts

    2056

    1

    Posted November 15th, 2010 06:00

    AFAIK there is no need to pay for OM (or even OR) licenses. At least if the following is still true:

    http://thestorageanarchist.typepad.com/weblog/2009/09/2022-free-migrations.html

  • SAN_AK

    2 Intern

    125 Posts

    2056

    0

    Posted November 15th, 2010 10:00

    Thanks for the replies, here is the more information  on OSs (Total hosts sum up to 28 and fall into below types)

    1. AIX 5.3 ML 07
    2. ESX 4.0.0
    3. Windows 2003 [x86] Standard Edition SP2

    I am not sure, at this environment the host based tools, but still good to know about it. how the overall migrationn can be planned, executed and confirm that migration is succesful.

  • SAN_AK

    2 Intern

    125 Posts

    2056

    0

    Posted November 15th, 2010 17:00

    Do you have any procedure for AIX internal mirroring, like from storage side...we just give out the (SAME or Greater size LUN ?)..then AIX admin will take from there?......what's good to suggest AIX guys..regarding the whole scope of migration..like onething I've got to know is to have the latest ODM and PowerPath installed. I believe internal mirroring uses, host cpu cycles so when it comes tradeoff b/w downtime and performance..w.r.t the LUN sizes to be mirrored..what can be the best approach... ?

  • krsram

    25 Posts

    1018

    0

    Posted November 15th, 2010 18:00

    Open Migrator installs and runs without license,,,I think it's free if you have Powerpath.

  • dynamox

    11 Legend

    20419 Posts

    87439 Points

    2056

    0

    Posted November 15th, 2010 19:00

    From storage side give them any size LUN you like as long as it either equal or greater total capacity of the volume group. I mean really AIX mirroring is very easy. So once the box got installed with ODM and PowerPath, you present the LUNs. AIX admin will rescan with cfgmgr, at that point he/she will need to perform these steps:

    1) add new devices to the volume group (hdiskpower devices)

    2) mirror volume group

    3) unmirror volume group (this pretty much break mirror pairing between EVA and VMAX devices)

    4) reduce volume group (in this step you remove EVA devices from the volume group)

    5) last step is to remove EVA devices from the system (rmdev -dl )

    yes, mirroring takes CPU cycles but it's negligible as it runs as a background process. Try to mirror during lightest time of the day (maybe after business day but before backups or early mornings after backups). Mirror one or two volume groups at a time.

  • dynamox

    11 Legend

    20419 Posts

    87439 Points

    413

    0

    Posted November 15th, 2010 20:00

    sorry but i don't have experience with VIO ..but i am sure a call to IBM will get your questions answered (unless other guys can jump in)