• 1.  Migration via Storage Replication

    Posted Mon November 09, 2020 08:56 AM
    We were planning on perform a relocation of an i7.4 LPAR between two sites using storage replication (via Storwize Storage array function), however we were surprised to find out that it is not a supported method of migration; even through there appears to be a product VM Recovery Manager for DR which seems to provide the orchestration for such a task.

    Is there no way of performing such a migration manually? It seems only tape is supported, which is not feasible for us.


  • 2.  RE: Migration via Storage Replication

    Posted Tue November 10, 2020 04:15 AM

    Hi, good morning.  Is it a case that (IBM?) simply don't support this approach even though, technically, it is do-able OR is there a valid reason why such a method cannot be used I wonder?

    Thinking about it from a "DR" perspective then surely such an approach is exactly what you'd be doing in order to stand up the LPAR "at the DR facility" so it does seem a strange stance they're taking.


    Thanks, Steve

    Steve Munday
    AIX, IBM i, PowerVM

  • 3.  RE: Migration via Storage Replication

    Posted Tue November 10, 2020 06:28 PM

    Thank you for your response. I am not sure what the story is; I keep getting pointed to as the only official supported DR method by the IBM i support team; i.e. use Tape for DR

    That's despite, Labs services being able to perform and IBM having a product Recovery Manager for DR that does it (officially). I also see there is a response from Glenn that is works with some minor config (which is what I'd expect).

    I'm not an IBM i person but on other platforms, it's no big deal if you keep source/target hardware the same. 

    thank you


  • 4.  RE: Migration via Storage Replication

    Posted Tue November 10, 2020 11:38 AM

    This works absolutely fine.

    Power down the source LPAR. Start the replication consistency group, start the source LPAR again.

    When the replication has completed synchronising, stop the replication consistency.

    Now stop the source LPAR and start the target LPAR.

    You will get a message on the LPAR saying disks are missing. This is because the UUIDs have changed so hit F10 to continue.

    You'll now need to add in the LICKEYs for the LPAR as the serial number has changed.

    VMR does exactly the same but automates it.

    Glenn Robinson
    IBM Power Systems and Storage specialist
    RSI Consulting Limited
    M: +44 (0) 7930 946274

  • 5.  RE: Migration via Storage Replication

    Posted Tue November 10, 2020 06:38 PM

    Thank you very much Glenn.

    Our IBM i SME has managed to get this to work for our one-off migration. But a shame we cannot use this as a DR solution without VMR... Not having IBM officially support it, complicates things.

    [John] [Londos]
    [IBM Infrastructure Architect]

  • 6.  RE: Migration via Storage Replication

    Posted Tue January 19, 2021 03:28 PM
    Hi John,

    Typically the only operation for migration that IBM Support will fully support is a full system save/full system restore.

    However, there are many IBM i users that have migrated using full system replication, and it is used on a regular basis. While this can be achieved manually, due to the number of questions that can come up related to the hardware and environment, to have the migration fully supported by IBM (should something go wrong), it is usually an IBM Lab Services engagement.

    As far as your question goes for using Full System Replication for DR. For similar reasons as the migration support statement, I believe there are currently two primary options for IBM i that are supported by IBM:

    1. Using the IBM Lab Services Full System Replication Tools for IBM i:
    2. Using VM Recovery Manager as you have previously mentioned

    Hopefully this helps some.

    Brian Nordland
    Technical Product Manager for PowerHA and Robot HA at HelpSystems