Moving the BRMS Database from One System to Another

Troubleshooting

Problem

This document provides instructions for moving a BRMS database from one system to another.

Resolving The Problem

To move the BRMS database from one system to another, users may use one of the following scenarios:

Scenario 1 - Target system does not have BRMS on it or is not actively used.

On the source system, save QUSRBRM, and Q1ABRMSF* libraries.

If the product is already installed on the target system, and the source and target systems are at different releases, save (SAVLICPGM) then delete (DLTLICPGM) LPP 57xxBR1. (Options *BASE ,1 and 2, if installed).
Note: Target system has to be the same or higher release than the source system.

On the target system, delete library QUSRBRM if it exists.

On the target system, restore libraries saved in Step 1.

5.

6.

On the target system, install (RSTLICPGM) the 57xxBR1 LPP saved in Step 2 or from PID. If installing from PID, PTFs must be reloaded for LPP 57xxBR1.

On the target system, run INZBRM OPTION(*DATA)

If the name of the target system is different, do one of the following options:

Option A

a. GO BRMS
b. Select Option 11
c. Select Option 1
d. Select Option 4
e. Type 4 next to the source system, and press the Enter key one time. Then, change Remove Media Information to *RENAME, and press the Enter key.

Option B

If the network Feature is not installed (57xxBR1 Option 1), and the user is on V5R2M0 or higher, they can run the following command:
INZBRM OPTION(*CHGSYSNAM) PRVSYSNAM(old_LCLNETID.old_LCLLOCNAME) NEWSYSNAM(*LCL)

Scenario 1 Notes

1.	When moving a BRMS data base to another system and the source system is in a BRMS network, the system that the data base is being restored to will recognize all the other systems in the BRMS network (WRKPCYBRM TYPE(SYS), Option 4). If you do not want the target system to communicate with any of the other systems in a BRMS network, remove the systems from the system policy. Refer to Rochester Support Center knowledgebase document, BRMS Networking: Adding, Removing, or Renaming a System:* . The *RENAME option should not be used unless the target system is going to replace the source system.
2.	These steps can also be used to synchronize the BRMS data base when migrating from one system to another.
3.	This process can be used when migrating from one system to another and the target system is at the same or higher release than the source system.
4.	At V5R3M0 and higher, BRMS cannot be used until the product has being initialized.
5.	This document assumes that the target system has all LPPs and PTFs already installed.
6.	This process cannot be used to upgrade systems from one release to another. The OS/400 Backup and Recovery guide, SC41-5304, is used for this. BRMS saves can still be used to do this restore; however, users must use RSTLIB SAVLIB(IBM) and RSTLIB SAVLIB(ALLUSR) rather than RSTLIB SAVLIB(*NONSYS).

Scenario 2 -Target system does not have BRMS on it or is not actively used and source and target system are on the same release

1. On the source system, save QUSRBRM, and Q1ABRMSF* libraries.
2. If the product is already installed on the target system, and the source and target system are at the same release, save (SAVLICPGM) for BR1 option *BASE , 1 and 2 if installed
3. On the target system, clear library QUSRBRM if it exists.
4. On the target system, do the following: WRKREGINF EXITPNT(QIBM_QTA*)
Select Option 8 on each of the listed exit points and delete any listed programs
5. On the target system, restore libraries saved in Step 1.
6. On the target system, run INZBRM OPTION(*DATA)

7.	If the name of the target system is different, do one of the following options: Option A a. GO BRMS b. Select Option 11 c. Select Option 1 d. Select Option 4 e. Type 4 next to the source system, and press the Enter key one time. Then, change Remove Media Information to RENAME, and press the Enter key. Option B* If the network Feature is not installed (57xxBR1 Option 1), and the user is on V5R2M0 or higher, they can run the following command: *INZBRM OPTION(CHGSYSNAM) PRVSYSNAM(old_LCLNETID.old_LCLLOCNAME) NEWSYSNAM(LCL)*

Scenario 3 - Target system already has BRMS on it.

1.	On the source system, save QUSRBRM, and Q1ABRMSF* libraries.
2.	On the target system, restore libraries saved in Step 1. Restore QUSRBRM to a different library.
3.	On the target system, run the following commands *INZBRM OPTION(MERGE) FROMLIB(OLDLIB) TOLIB(QUSRBRM) where OLDLIB is the library QUSRBRM was restored to in Step 2. INZBRM OPTION(CHGSYSNAM) PRVSYSNAM(OLD_NAME) NEWSYSNAM(LCL)**

Detailed step-by-step instruction for Scenario B are available in Rochester Support Center knowledgebase document N1012088, Merging BRMS data to Target System with Existing BRMS:

Scenario 3 Notes:

1.	When running the INZBRM OPTION(*MERGE) , it is very important that no other BRMS activity occurs on this system. This includes other systems in the BRMS network sending updates to this system.
2.	Merging systems requires that the target system be removed from any BRMS network first.
3.	All changes will be rolled back if the *MERGE is cancelled before completion.
4.	The source system needs to be removed from any BRMS network before the QUSRBRM library is saved. Refer to Rochester Support Center knowledge base document New, BRMS Networking: Adding, Removing, or Renaming a System: . The *YES option should be used so that the system only knows about it's own media and history.
5.	At V5R3M0 and higher, BRMS cannot be used until the product has being initialized.
6.	This process assumes that the target system has all LPPs and PTFs already installed.
7.	This process can be used when migrating from one system to another and the target system is at a higher release than the source system.
8.	This process cannot be used to upgrade systems from one release to another. The OS/400 Backup and Recovery guide, SC41-5304, is used for this. BRMS saves can still be used to do this restore; however, users must use RSTLIB SAVLIB(IBM) and RSTLIB SAVLIB(ALLUSR) rather than RSTLIB SAVLIB(*NONSYS).

Scenario 1 2 & 3 Notes:

After completing any of these processes, SETUSRBRM may need to run for any user profile that will be using BRMS.
If the source system is using a BRMS user-defined system name and do not want the target to use this user-defined system name, refer to BRMS user-defined system name support to display and change the system name from a BRMS network perspective.

[{"Type":"MASTER","Line of Business":{"code":"LOB68","label":"Power HW"},"Business Unit":{"code":"BU070","label":"IBM Infrastructure"},"Product":{"code":"SWG60","label":"IBM i"},"ARM Category":[{"code":"a8m0z000000cwpBAAQ","label":"Save Restore-\u003EBRMS"}],"ARM Case Number":"","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"All Versions"}]

Historical Number

27253243

Was this topic helpful?

Document Information

Modified date:
12 November 2024

UID

nas8N1019378

Tips