Page Comparison

There are specific steps needed to be followed to move BRMS from a donor system to a target system when the target system has BRMS installed. BRMS is running backup policies on the target system, so there exists on this system history and media information owned by the target system. The merge operation basically consists of combining the BRMS data from the donor system with the BRMS data on the target system.  Because BRMS is already installed on the target system, no installation of BRMS is required.

The merge steps are as follows:

...

1. Verify you are signed on with a user profile with *SECOFR authority.

2. If donor system is part of a BRMS network group, use the following command to display the active records for this system:

   • DSPPFM FILE(QUSRBRM/QA1ANET2)  
         Verify the QUSRBRM/QA1ANET2 file is empty.

3. If you want to differentiate the media of the donor system from that of the target system, you can update the media records with unique text using a SQL command similar to the following example:

   • UPDATE QUSRBRM/QA1AMM SET TMTEXT = 'unique-text' WHERE TMSYID = 'donor’ AND TMCNET = 'network-ID’

   • Using network-ID.donor as specified in the System column when viewing locally owned media with WRKMEDBRM SYSNAME(*LCL)

4. If you want to differentiate the save history of the donor system from that of the target system, you can update the history records with a unique control group using the following SQL command:

   • UPDATE QUSRBRM/QA1AHS SET BKHGRP=’new-control-group-name’ WHERE BKHGRP=’old-control-group-name’
         
     This step is optional and may not even be necessary if the save on the donor system was performed using control groups which do not exist on the target system.  Once you have completed the rename and merge the data to the target system, you will be able to view these older saves using the following command:
         
         WRKMEDIBRM CTLGRP(new-control-group-name)

5. Save the QUSRBRM and Q1ABRMSF* libraries on donor system by using the following command:

   • SAVLIB LIB(QUSRBRM Q1ABRMSF*) DEV(tape_device)

...

1. If the data has been saved to save files, the history will only be merged on a system that has no other BRMS history.

2. If the target and source system have IFS (*LNK) data that have the same save date/time stamp, the records will not be added to the history file.

3. Object level detail for IFS data will not be added if the target and source systems have the same save date/time stamp or the same named object.

4. Some directories will not be listed from the source system when a WRKLNKBRM is run after the merge is complete.

5. Systems should have the List of BRMS Service Packs for the specific release applied

6. No BRMS activity can occur on any system in the BRMS network while the merge is running.  It is recommended that the system running the merge be removed from the BRMS network and then added back in, once the merge is complete.

7. BRMS does not verify if there is sufficient space on the system to merge the BRMS files. It is the users responsibility to ensure that there is enough space on the system for the restore of the QUSRBRM library from the donor system and additional space to merge the files into the current QUSRBRM library.

8. If it is desired to merge only history information (not using MERGE(*ALL)), merge options *DEV, *MED and *HST must all be specified. If *DEV is not included with the merge and the BRMS devices are not the same on the source and target systems, all BRMS history data may not be merged. *MED is required because if only history exists with no volume information, BRMS may delete the history.   For example, use the following command to merge all BRMS media and history information:

   • INZBRM OPTION(*MERGE) FROMLIB(OLDLIB) TOLIB(QUSRBRM) MERGE(*MED *DEV *HST)  -  where OLDLIB is the library containing QUSRBRM/QA1AHS from the previous system.

...