Synchronize a Migrated Region

If you plan to synchronize the region you are migrating with other regions, review the information and complete the tasks in the following sections.
nwmscl122
If you plan to synchronize the region you are migrating with other regions, review the information and complete the tasks in the following sections.
Unless noted otherwise, each section applies to all CA NetMaster products, except 
CA SOLVE:FTS
.
Important Considerations Prior to Linking
Consider the following points before linking:
  • The first region that is linked in migration mode must be used to perform all monitor, command, and control functions across the entire multi-system environment.
  • Migration mode does not support database synchronization between the old and new product regions. We recommend that you do not perform database maintenance while operating in migration mode.
  • If database maintenance is unavoidable, apply the maintenance in an old region and again in a new region. With this process, changes are propagated to all linked regions.
Link in Migration Mode
You can link your first migrated product region to your existing product regions in migration mode.
Migration mode lets you migrate your existing product regions in an orderly fashion while maintaining visibility and control of your entire multi-system environment.
  • Apply the relevant maintenance to your product region.
  • If the RUNSYSIN member for your existing product region specifies the NMSUP parameter, specify this parameter in the RUNSYSIN member for your new product region. The NMSUP parameter helps to decrease the number of unique background user IDs that must be defined if you are using an external security package.
For more information, see Security.
 
To link a migrated product region to an existing product region, complete the following steps:
 
  1. Enter 
    =/MADMIN.MM
     in the new product region.
  2. Specify the name of an existing focal region in your multi-system network.
  3. Press F6 (Action).
Migrate Subsequent Regions
When a subsequent product region is migrated to the new release, you can use this procedure to link it to the first migrated product region.
 
To link the subsequent product region, complete the following steps:
 
  1. Enter 
    =/MADMIN.SD
    .
  2. Specify the first Release 12.2 product region as the remote region.
  3. Specify the role for this region (focal or subordinate).
  4. Press F6 (Action).
  5. Repeat these steps for all of the remaining subordinate and focal regions. Migrate is the focal region that you first linked using migration mode last.
    This migration sequence retains the visibility to the multi-system network throughout the migration process.
A Multi-system Network Migration Example
The following diagram shows a multi-system network with two focal regions and four subordinate regions:
 The illustration shows the network to be migrated. 
 
To migrate a multi-system network
 
  1. Unlink Focal 2 from the existing multi-system network, as shown in the following diagram:
 The illustration shows the Focal 2 region unlinked from the network. 
2. Upgrade Focal 2 to Release 12.2.
3. Link Focal 2 to Focal 1 in migration mode, as shown in the following diagram:
 The illustration shows the upgraded Focal 2 region linked to the Focal 1 region in migration mode. 
4. Unlink Subordinate 1 from the multi-system network and upgrade it to Release 12.2.
5. Link and synchronize Subordinate 1 to Focal 2, as shown in the following diagram:
The illustration shows the upgraded Subordinate 1 region linked to the upgraded Focal 2 region. 
6. Repeat Steps 4 and 5 for Subordinates 2-4 and Focal 1.
How to Run Your Old Region in Parallel with the New Region
If your existing region uses global mode AUTOMATED to perform desired state management, you can ease your new product regions into production as described in this section.
If you do not want to move directly from your existing regions to the new regions, you can do the following:
  1. Create an equivalent region for each of your existing regions, so that you have a mirrored pair on each system.
  2. Initially, have the existing region performing automation, and the new region running in the global mode of MANUAL (that is, merely monitoring) but using the same data.
  3. Gradually, reverse the global mode of operation between the mirrored pairs until the new regions are performing automation.
This suggested scenario provides you with a hot backup, letting you instantly swap from a new region to the established region if you experience any problems. You can then correct the problem before swapping back to try the new region again