DUPMEDBRM works when duplicating media that is owned by another system in the BRMS network . In this example, there are two systems: SYSA and SYSB.
- BRMS network feature must be installed and systems must be added to the BRMS network.
- SYSA and SYSB must have the Receive media information in the system policy set to *LIB.
- Note: This must be set before the save on SYSA is done.
- Press the Enter key. Then, select Option 4.
- IBM i 6.1 and earlier:
- Change Receive media info to *LIB
- IBM i 7.1 and later:
- F11 and change Local Receives to *LIB
- The save is done on SYSA and once complete, the volume is owned by SYSA. The information will be synched or networked to the other systems in the BRMS network.
- The remote
DUPMEDBRM is started on SYSB, specifying a volume owned by SYSA, and SYSA is specified as the remote system. On the operating system command line, type the following:
DUPMEDBRM VOL(BRM001) FROMDEV(TAPMLB01) TODEV(TAPMLB02) FROMVOL(BRM001) FROMSYS(SYSA)
- Press the Enter key.
- Under the covers, SYSB takes ownership of the input volume and starts to duplicate to it, using local data (which is why receiving *LIB information is important).
DUPMEDBRM goes through regular volume selection to find an output volume and takes ownership of it.
- During duplication on SYSB, the history records are also duplicated and placed into SYSB's database. Then, they are synched back to SYSA by the network synchronization job.
- After duplication, both the input and output volumes are reassigned to SYSA
- The system running the remote
DUPMEDBRM must be at the same release or higher than the system that owns the media.
- Both the from device (FROMDEV) and to device (TODEV) must have a physical connection to the system performing the
- It is important that BRMS maintenance or the Reclaim Wizard is not run on the owning system or the system during the duplication. History will be lost if this occurs.
- Starting at V5R4M0, it is possible to save the BRMS recovery information at the end of the duplication. However, this is intended for local duplications only. When doing remote
DUPMEDBRM, the SAVMEDINF parameter needs to be set to *NONE.
- The source system where the saves were done on has to be up and remain up until the remote duplication is complete.
- BRMS can only duplicate media if there is active history for the volume(s) in the BRMS data base (
- When using IASP FlashCopy - Specific System Synchornization, the volume(s) need to be duplicated on the system that did the backup as the duplicate history ownership will be lost when remote duplicates are done.
- Nothing is duplicated on SYSB.
- Q1ABRMNET subsystem is not running on SYSB
- QBRMSYNC job is hanging
- Receive media Information is system policy is not *LIB on SYSB
- BRM15A2 - Volume &1 cannot be duplicated by this system.
DUPMEDBRM command did not specify a remote system name.
WRKMEDIBRM VOL(duplicate volume) does not list anything on SYSA.
- QBRMSYNC job not running or is still sending data to SYSA
- SYSA does not have Receive Media Information in the system policy set to *LIB
- Volumes are owned by SYSB.
- Reassignment failed and did not change volumes back to SYSA because the
DUPMEDBRM was cancelled by user.
- When using this command, users must be aware that they cannot run the
DUPMEDBRM command for a remote system and the
DUPMEDBRM VOL(*SEARCH) command for the local volumes at the same time. This causes the
DUPMEDBRM of the local volumes to fail with message CPF412F.
RMVMEDIBRM command should not be run on the system doing the duplication or on the system that owns the media while the
DUPMEDBRM command is running . If this occurs, the save history on the system owning the volumes will be removed and running the
WRKMEDBRM command, Option 13 on the original volume will not list anything.
DUPMEDBRM requires that BRMS has history of the volume in it's history files on the system running the duplication. If this history is missing, the duplication will complete successfully (BRM1566 will be posted) but nothing is duplicated. A common reason the system performing the remote
DUPMEDBRM operation did not get it's history updated can be a result of not following Step 2 of this knowledgebase document.
- Ensure DDM is running on both servers.