Skip to main content

BRMS for V5R4M0 continues to extend existing capability and provide new functions for improving automation, minimizing backup windows, and providing additional backup, recovery, and media management flexibility.

VIRTUAL TCP/IP INTERFACE(VIPA) SUPPORT FOR RESTRICTED STATE BACKUP

BRMS will start multiple TCP/IP interfaces during a restricted state backup. This will allow SAVSYS and other saves to be performed from control group to 3494 Tape libraries while in restricted state.

WORM (WRITE ONCE READ MANY) DEVICE SUPPORT

A new media class attribute now lets you specify write once media type. File sequences on the WORM media cannot be reused. Only new file sequences can be added to the WORM media until the volume is filled.

FLASH COPY

BRMS integration with SAN for FlashCopy solution will provide a way to copy your system data from the production system to another system and have that system perform the backup as if the production system had done the backup.


BACKUP


RECOVERY


MEDIA MANAGEMENT


NETWORK FEATURE


BRMS IBM i NAVIGATOR CLIENT


V5R4 USAGE NOTES:

Restore operations using the Navigator client: *MEDCLS processing on restore operations using Operations Navigator on V5R4M0 have been changed to provide more flexibility when the user inserts the desired cartridges into standalone devices. We will no longer restrict the location of the standalones to the location of the volume, and will always check the mounted volumes on standalones first. However, as this might become a performance issue in some customer configurations, the standalone check can be disabled. If the data area "QUSRBRM/Q1ANOMNTCK" exists we will skip the standalone check.

Virtual tape support: The first time a virtual tape is duplicated to a physical tape, the virtual tape will become the duplicate and the physcial tape will become the original. When saving and restoring online Domino databases to Virtual Tape, the user profile QNOTES needs to have authority to the image catalogs which contains the entries used by BRMS during the operation. QNOTES should have *USE or *CHANGE authority to the image catalog.

Remote duplication: When using the remote DUPMEDBRM function the system that is doing the duplication for another system, has to be equal to or less than the release of the system which owns the media and data being duplicated or the customer will recieve a CPF9898.

INZBRM *MERGE function: Merging BRMS data to a Target System with Existing BRMS will not merge save file history because of possible naming collisions on the target system. When consolidating systems and removing the source system from the BRMS network, if the target system is not changed to own the media and history from the source system by running the INZBRM *CHGSYSNAM function, then history will be removed during a run of maintenance. BRMS does not allow history from another system on the local system if the systems are not networked.

We're here to help

Easy ways to get the answers you need.


or call us at
1-866-883-8901
Priority code:
101AR13W