Merge consolidation planning

Before merging BRMS data, you need to consider the following items:

DASD utilization

BRMS data can use a fair amount of DASD when object level detail is saved as part of your backup strategy. Ensure that the target system has sufficient free storage space. The more systems merged, the greater the DASD utilization.

Job scheduler entries

BRMS related job scheduler entries are not transferred during a merge or migration of BRMS data. You need to create new job scheduler entries on the target system if required.

Backup window

Having a single system with data from multiple systems can increase the time to do backups. Users should be aware that their backup routines may contain additional processes after merging BRMS data.

BRMS maintenance

Running BRMS maintenance take longer to run after the merge is completed if more data is involved.

Different time zones

If a donor system is in an earlier time zone than the target system, do not merge BRMS data onto the target system until the time the data was saved on the donor system has been reached. This prevents the possibility of overwriting current data on the target system.

Primary and secondary languages

BRMS data is not affected by different language codes; however, it is possible that menus and reports generated within BRMS are of another language on the target system.

Auxiliary storage pools

If your donor system has more basic user auxiliary storage pools (ASPs) than the target system, be aware that BRMS has created a library for save file backups for each ASP. The libraries are named Q1ABRMSFnn, where nn is the auxiliary storage pool identifier. Make sure the Q1ABRMSFnn library that resides in an ASP that does not exist on the target system, is empty before the merge.

Note: Never restore Q1ABRMSFnn libraries to a target system where the library already exists. Restore only the objects within the library.

Spooled files

If spooled files are required from a donor system, save the spooled files on the donor system and then restore the saved spooled files to the target system. This can be done using a spool list. Create and run a backup control group containing the QALLSPLF spooled file list to back up all spooled files on the donor system or use the Work with Lists using BRM (WRKLBRM) command to create a spooled file list specifying the spooled files you want to back up.

Coexistence with other systems

If the donor system is a server, point the clients to the target system if it is to be the new server.

Same or backward releases

Merging from a higher release of BRMS to a lower release is not supported by BRMS.

Multiple systems

Do not attempt to merge multiple donor systems to a system at the same time. If multiple systems are to be merged into one or more systems, merge one system at a time.

Policies in BRMS

Review all BRMS policies prior the to merge and note similarities between the donor and the target systems. Consider printing and comparing the policies of both systems. Only non-unique policies will be merged and only if all references objects exist. Delete any unused policies and rename redundant policies.

Note: The System Policy, Backup Policy, Archive Policy, Recovery Policy, Retrieve Policy and Migration Policy are never merged.

Omit lists

Compare omit lists between the donor and target systems to determine whether omitted items and the lists are still valid for the target system. Delete any unused list and rename redundant lists.

Compatible media types

Drives on the target system should be compatible with media coming from the donor system.

Print the backup plan prior to merging

Print the current backup plan for BRMS on the donor system and target systems. The report (QP1ABP) can be printed using the following command:

   DSPBKUBRM OUTPUT(*PRINT)

This report lists all backup control groups on the systems and can be used to compare backup control group entries.

Review the archive groups, migration groups and lists on the display. No print option is currently available.

Media Storage Extensions (MSE 5770-SS1, option 18)

Install Media Storage Extensions on the target system. Be aware of any other backup applications which may use MSE.

Network donor systems

Remove donor systems from the BRMS network. Refer to Removing a system from a network.

Use BRMS to perform a full system backup of all systems

It is advised that full system backups are processed prior to any system change.

No activity on any BRMS system

To ensure a successful BRMS data merge, cease all activity on any networked BRMS system.

Software Encryption

When merging two systems together, there might be a need to translate the BRMS keystore file. You should only have to do this if using Software Encryption. To determine whether to translate these files refer to the Translating Key Store Files topic.