IBM i Global

 View Only
  • 1.  Migration of systems using SAN

    IBM Champion
    Posted Fri January 20, 2023 08:02 AM
    Let's say I was using SAN (as I will be in the very near future).
    Let's say I was migrating from a P8 or P9 to P10's (as I will be in the very near future).
    When moving from one to the other will there be an issue with the SRM?
    If you do not know what SRM is prompt the following:  RSTCFG SRM(*ALL) and press F1 on System Resource Management . . . SRM.  You will see:
    ATTENTION Unless the system you are restoring to has exactly the
    same hardware configuration as the system that the original
    configuration was saved on, you must specify SRM(*NONE) on this
    command to prevent the restore of the SRM information. If the SRM
    information is restored on a system with a different hardware
    configuration, the configuration objects may become unusable.

    I'm thinking things like 
    On the Specify Command Defaults display, enter the name of the tape drive that you are using for the restore.
    1. Set Prompt for command to N.
    2. Set Message queue delivery to *NOTIFY.
    3. Set Restore to different system to Y.   <<<------------  Changes RSTCFG to SRM(*NONE)
    I realize there may be some resource names on configuration descriptions which need fixing.  For example, the communication resource associated with your ethernet line.

    I asked IBM via feedback to add this as a scenario to:
    Scenarios: Data migration - IBM Documentation

    I've been through many migrations over the years.  SAN is all new to me.


    Robert Berendt IBMChampion

  • 2.  RE: Migration of systems using SAN

    IBM Champion
    Posted Fri January 20, 2023 07:01 PM
    Edited by Satid Singkorapoom Fri January 20, 2023 07:03 PM
    Dear Robert

    I see that you have provided the answer to your question of how to deal with SRM!  I also used it

    Personally, I never had to deal with RSTCFG + SRM at all in my entire career (and I have done many instances of save entire system followed by restore entire system to move from one machine to another) because when I do restore entire system, I never manually run each type of restore command individually but instead I use GO RESTORE menu and do the same as you described in the 3 parameters and the manual change of LAN resource name in your post above. Then I do additional manual housekeeping after the restore entire system using this method from SST provided here : Correcting problems with the system resource management information   


    When you restore your configuration to a different system, you should not restore the SRM information because it will not match the hardware on the target system. Sometimes during a system upgrade, you are instructed to restore the SRM information to your system even though some of your hardware has changed.

    If you have restored the SRM information and the hardware configuration does not match, use the following procedure to correct the SRM information:

    1. Type STRSST and press the Enter key to access system service tools (SST).
    2. Select Option 1 (Start a service tool) from the System Service Tools menu and press Enter.
    3. Select Option 7 (Hardware service manager) from the Start a Service Tool menu and press Enter.
    4. Select Option 2 (Logical hardware resources) from the Hardware Service Manager menu and press Enter.
    5. Select Option 1 (System bus resources) from the Logical Hardware Resources menu and press Enter.
    6. Select F10 (Non-reporting resources) to display any nonreporting resources.
      Any hardware resources that did not report during the last initial program load (IPL) or that were created during the last Restore Configuration (RSTCFG) command will be displayed.
    7. Type a 4 (Remove) in the Option column to delete any entry you are certain is not valid for this system's configuration.

    When I did Partition Mobility to migrate my customer from an old to a new POWER server, there is no save and restore entire system involved and the manual housekeeping method using SST above was the only choice to use.

    Right action is better than knowledge; but in order to do what is right, we must know what is right.
    -- Charlemagne

    Satid Singkorapoom

  • 3.  RE: Migration of systems using SAN

    IBM Champion
    Posted Mon January 23, 2023 09:30 AM
    Thank you. I'll keep that 'correcting problems' link in mind.

    Robert Berendt

  • 4.  RE: Migration of systems using SAN

    Posted Mon January 23, 2023 08:52 AM

    When doing a full system migration via tape, I always check the Restore to different system. Using SAN or internal disk does would not make a difference on this setting. 
    Once you are on SAN and doing a migration, there will not be a "Restore" so this parameter does not come into play. 

    Steve Pavlichek