MIMIX-specific steps for an OS upgrade on a backup system - assure_mimix - 10.0

Use this procedure to upgrade the operating system on the backup system.

Notes: 

• If you plan to upgrade both the production and backup systems during the same scheduled maintenance period, upgrade the backup system first.

• In the following steps, the terms production and backup always refer to the original roles of the systems before upgrading the operating system on either system. The icons at the beginning of some steps show the state of the systems and replication as a result of the action in the step. The arrow in the icon indicates the direction and state of replication for a classic production to backup environment.

When performing an operating system upgrade of a backup system in a MIMIX environment, do the following:

1. Ensure that you have completed any prerequisite tasks for your upgrade scenario. See IBM i operating system upgrade scenarios and recommended processes for handling MIMIX during the upgrade  for a list of required tasks for different upgrade scenarios.

2. End all user applications, user interfaces, and operations actively running on the backup system.

3. End MIMIX including the MIMIX managers and end the RJ links using the following command:

   ENDMMX ENDOPT(*IMMED) ENDRJLNK(*YES) SYSDFN(*LOCAL) ENDSMRJ(*YES)

   For more information about the ENDMMX command, see Commands for ending replication.

4. If the Assure Unified Interface server is running on the system you are about to upgrade, use the following command to end the Assure Unified Interface server:

   VSI001LIB/ENDVSISVR

5. 

   Ensure that all MIMIX jobs are ended before performing this step. End the MIMIX subsystem on the system you are about to upgrade. Type the following on a command line and press Enter:

   ENDSBS SBS(MIMIXSBS) OPTION(*IMMED)

   Note: If you are running Assure Unified Interface in the MIMIX subsystem for any product, be aware that all Assure Unified Interface processes will end.

6. Complete the operating system upgrade. Allow any upgrade conversions and access path rebuilds to complete before continuing with the next step.

   Note: During the IBM i upgrade, make sure you perform a system save on the system being upgraded. This step will provide you with a backup of existing data.

7. Ensure the names of the journal receivers match the journal definitions:

   1. From the backup system, specify the command:

       installation-name/WRKJRNDFN JRNDFN(QAUDJRN *LOCAL)

   2. Next to the JRNDFN(QAUDJRN *LOCAL) journal definition, specify 14 (Build) and press F4. Type *JRNDFN for the Source for values parameter and press Enter.
8. Start the MIMIX subsystems on both the production and backup systems using the following command from each system:

   STRSBS SBSD(MIMIXQGPL/MIMIXSBS)

9. Verify the communication links start, using the Verify Communications Link (VFYCMNLNK) command. For more information about the VFYCMNLNK command, see Verifying a communications link for system definitions.

   If the communications link is not active, you may need to start the port job. On a command line type the following and press Enter:

    STRSVR HOST(host-name-or-address) PORT(port-number)

10.  

    Perform a normal start of data groups and application groups from any system using the STRMMX command. This step also starts the MIMIX managers.

11. Perform your normal process for validating the IBM i release upgrade.

    Notes: 

    • At your convenience, schedule a switch to verify that your applications function on the new operating system on the backup system.

    • MIMIX supports replication for up to two version level differences. If running different OS versions, Precisely recommends that the backup node run the higher OS. The following restrictions and limitations may also apply:

      • All objects must be compiled using the Target Release parameter to specify the IBM i version of the lower level operating system.

      • Possible inherent restrictions include those specific to new functionality in the OS. There may be features in a higher OS release that would not be available in a lower one, such as new command parameters or APIs.

      • Some errors may be encountered during or following a role swap due to the different OS versions.

12. If you ended the Assure Unified Interface server, restart it using the following command:

    VSI001LIB/STRVSISVR