Versions Compared

Old Version 3

changes.mady.by.user Peter Lafler

Saved on

compared with

New Version Current

changes.mady.by.user Aaron Fistler

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. BRMS network feature must be installed and systems must be added to the BRMS network.
  2. 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.
    • WRKPCYBRM TYPE(*SYS)
    • 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 the Local Receives to *LIB    LIB    
  3. 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.
  4. 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.
  5. 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).
  6. DUPMEDBRM goes through regular volume selection to find an output volume and takes ownership of it.
  7. 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.
  8. After duplication, both the input and output volumes are reassigned to SYSA

...

  1. The system running the remote DUPMEDBRM must be at the same release or higher than the system that owns the media.
  2. Both the from device (FROMDEV) and to device (TODEV) must have a physical connection to the system performing the DUPMEDBRM.
  3. 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.
  4. Starting at V5R4M0, it 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.
  5. The source system where the saves were done on has to be up and remain up until the remote duplication is complete.
  6. BRMS can only duplicate media if there is active history for the volume(s) in the BRMS data base (WRKMEDIBRM)
  7. 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.

...