Versions Compared

Key

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

Enhancements for the IBM Backup, Recovery, and Media Services (BRMS) for i solution are listed below. Many of these enhancements are delivered using the IBM i PTFs listed for each release. "Base" indicates that the enhancement is included in the base release.

2022-05-13

7.5 SI78291, 7.4 SI78290, 7.3 SI78289

In Version 7.3 and later:

  • BRMS recovery report has been enhanced to provide improved reporting for H/A environments.  This support will provide a way to generate a single BRMS recovery report using tapes from your backup and production systems in an H/A environment. 

  • BRMS using IBM Cloud Storage for i has been enhanced to improve BRMS network support.  The purpose of this support is to ensure duplicate volume names are not generated when any system in the BRMS network is in restricted state or when the BRMS network synchronization job is not working. 

  • BRMS has been enhanced with new SQL services for the BRMS log message distribution and log omits, media library management, and backup control group information. 

  • BRMS has been enhanced to migrate control groups with GUI object omits to use object list omits.

7.3 SI78289

  • BRMS enhancements have been made to change the GUI only control group attributes for Allow activity overrides, Allow retention overrides, Lotus servers, Integrated Windows servers, and Guest partitions. More information at Interface to change GUI only control group attributes

...

  • BRMS has been enhanced to provide BRMS SQL Services to view, order, and subset BRMS media.

  • BRMS move policy has been enhanced to support the movement of full volumes to a new location.

  • WRKOBJBRM command has been enhanced with a START() parameter to specify which saved object entries to display first.

  • STRMNTBRM with parameter PRTRCYRPT(*ALL) or PRTRCYRPT(*SAVEXCP) was enhanced to log message BRM1571 in the BRMS log with severity 0 if zero objects were not saved.

2020-06-12

7.4 SI72867, 7.3 SI72866, 7.2 SI72865

...

2020-03-13

7.4 SI71975, 7.3 SI73048, 7.2 SI71973

...


2020-01-13

7.4 SI71876, 7.3 SI71875, and 7.2 SI71874

  • Changes were made in BRMS to address potential security concerns. Existing user profiles used to perform BRMS operations may require additional authority to allow proper access.  Additional authority may be granted using the SETUSRBRM command with the new USAGE(*AUT) parameter option. Note: *SECADM authority is required to use the SETUSRBRM command.

  • BRMS enhanced the INZBRM OPTION(*FLASHCOPY) STATE(*STRPRC) processing to end the BRMS Enterprise subsystem named Q1ABRMENT.

  • BRMS now provides a Reclaim Media (Q1ARCLMED) API to reclaim a single tape volume.

  • Improved the IFS backup outfile processing performance.

  • BRMS support for DRDA/DDM Conjoined Mutual Authentication

  • To display the cloud Retain Media After Transfers retention period the following command can be run:
    CALL PGM(QBRM/Q1AOLD) PARM('CLOUD ' 'RETAINDATA' 'S' 'mmmmmmmmmm' '*DSP')
    where 'mmmmmmmmmm' is the move policy name.

2019-09-13

7.4 SI70626 - 7.3 SI70625 - 7.2 SI70624

2019-07-19

7.4 SI70368 - 7.3 SI70367 - 7.2 SI70366

2019-06-21

7.4 -  Base Release

  • Turn-key cloud control group deployment which allows customers to easily set up custom cloud control groups.

  • Enable the green screen command to change control group attributes which were previously only available in the GUI.

  • Backup for journaled objects changes is now the default setting: the default parameter value for SAVLIBBRM command has been changed to OBJJRN(*YES).

  • New *OBJ list named QALLSPLF to backup all spooled files which improves restore performance.

  • Support for the 3592-60F tape drive with *FMT3592A6 and FMT3592A6E densities.

  • Enhanced log information: uses the system timestamp to preserve message order when messages are logged at the same second are displayed using DSPLOGBRM.

           

2019-03-13

7.3 SI68856- 7.2 SI68855


2018-12-13

7.3 SI68846- 7.2 SI68845

  • The BRM log information has been enhanced to use the system timestamp to preserve message order when messages logged at the same second are displayed using DSPLOGBRM.

  • BRMS has been enhanced to support the new 3592-60F tape drive with new *FMT3592A6 and FMT3592A6E densities.

  • BRMS has enhanced the cloud turnkey solution to allow customers to create their own disaster recovery turnkey control groups.

  • BRMS has enhanced the green screen to change the previously GUI only control group attributes for TCP/IP servers, to unmount user-defined file systems, and run maintenance after backup. More information at Interface to change GUI only control group attributes.

  • BRMS now creates an *OBJ list named QALLSPLF to backup all spooled files. More information at Improving performance when restoring spooled files

  • SAVLIBBRM command default for Journaled objects has been changed to OBJJRN(*YES).

2018-09-12

7.3 SI68073- 7.2 SI68072

  • In 7.2 and later, INZBRM OPTION(*VFYSYS) was enhanced to check if the flash copy state allows communication.

  • BRMS has been enhanced, providing cloud archive support. More information at Using Cloud Storage Solutions for i with BRMS.

2018-06-13

7.3 SI67946- 7.2 SI67312- 7.1 SI67311

  • BRMS cloud support has been enhanced. BRMS now uses ASP and IASP storage for cloud transfers which enables virtual media access in HA environments. See the section, Using Cloud Storage Solutions for i with BRMS to learn more

  • BRMS volume selection has been enhanced to ensure WORM media are only returned if the media class being used is set with the Write once media value set to *YES.

7.3 SI67946- 7.2 SI67312

  • The DSPLOGBRM command has been enhanced to support a list of message identifiers on the MSGID() parameter to display or include in the report.


2018-03-15

7.3 SI66900- 7.2 SI66899- 7.1 SI66898


2017-12-15

7.3 SI66286- 7.2 SI66285- 7.1 SI65888

  • Added support for Ultrium 8 (LTO8) tape drives and media


2017-09-15

7.3 SI65676- 7.2 SI65675- 7.1 SI65674

  • WRKMEDBRM has been enhanced to list all active volumes that are full. In order to list the full volumes, use the following command:

    • WRKMEDBRM TYPE(*FULL)

  • BRMS has been enhanced to support a FlashCopy time stamp when doing Full System Flash Copies. More information can be found here


2017-06-15

7.3 SI64250 - 7.2 SI64248

7.3 SI64250 - 7.2 SI64248 - 7.1 SI64249

  • BRMS has been enhanced to support the new 3592 densities: *FMT3592B5 and FMT3592B5E


2017-03-15

7.3 SI64276

  • The BRMS recovery report [STRRCYBRM ACTION(*REPORT) ], includes instructions to change the QSYSOPR message queue after the sign on in the 'Update System Name in BRMS Media Information' step.

7.3 SI64276 - 7.2 SI64275

  • To improve recovery times, the BRMS recovery report [STRRCYBRM ACTION(*REPORT) ] with Domino recovery has been enhanced to remove an IPL step

7.3 SI64276 - 7.2 SI64275- 7.1 SI64274

  • The Analyze Libraries using BRM (ANZLIBBRM) report has been enhanced to better estimate the amount of time Intergrated File System (*LINK) data will take to save.


2017-01-10 - HIPER

7.3 SI63592 - 7.2 SI63591- 7.1 SI63590

7.3 SI63592 - 7.2 SI63591


2016-10-28

7.3 SI61153 - 7.2 SI61152- 7.1 SI61151

  • BRMS has been enhanced to use IBM Cloud Storage Solutions for i.

  • The BRMS GUI client now allows special value *NONE or blanks to be specified for the Library fields in the System Policy submitted jobs section.

  • Performance of command STRMNTBRM has been improved when RGZBRMDB(*YES) is specified.

  • After loading this PTF or superseding PTF, users may see message CPI9E75- "Grace period expires in &5 days on &4" for 5770BR1 FC5101 or FC5102 that do not have valid license

2016-06-15

7.3 SI59997 - 7.2 SI59998 - 7.1 SI59996

  • Recovery report (QP1ARCY) steps "Recovery Operating System" and "Verify System Information" have been enhanced to include system value information from the saved system.

  • Journal recoveries that require more than 3250 journal objects to be restored will fail with a specific error, message MSGBRM9999 and reason code RC0001.

  • When a save file, that is in use by another job, is specified on command SAVSAVFDTA, the job log will now include message MSGCPF3218 to indicate the save file is in use.

  • Save performance has been improved when libraries are saved with object level detail and the FlashCopy time is set.

  • More than 9999 spooled files can now be selected when F16 is pressed to select all spooled files for recovery using command WRKSPLFBRM.

7.1 SI59996


2016-05-03 - HIPER

7.3 SI60601 - 7.2 SI60600 - 7.1 SI60599

  • If parallel BRMS saves that generate media sets that span volumes, BRMS restores from these media sets can fail with one of several different messages, for example: MSGCPF387C, MSGBRM3015, MSGCPF3780, MSGCPA6798, etc.

  • BRMS Enterprise report definitions have been enhanced to allow values other than *LCL to be specified for the From system (FROMSYS) parameter on the Print Report using BRM (PRTRPTBRM) command.

  • BRMS has been enhanced to support volume selection priority for output volumes used during BRMS operations.

  • The Duplicate Media using BRM (DUPMEDBRM) command has been enhanced to clarify why the value specified on the To volume (TOVOL) parameter is changed to *MOUNTED if the original TOVOL value is not used during the duplication.

  • The Libraries to omit (OMITLIB) parameter and the Objects to omit (OMITOBJ) parameter have been added to the Restore Library using BRM (RSTLIBBRM) command and the Objects to omit (OMITOBJ) parameter has been added to the Restore Object using BRM (RSTOBJBRM) command. Note: Use of these omit parameters also requires the following PTFs or superseding PTFs:

    7.2 SI59682

    7.1 SI59681


2015-12-15

7.2 SI57831 - 7.1 SI57830 - 6.1 SI57829

  • BRMS email notifications have been enhanced to support a user specified 'from address' for emails.

  • During a backup, if a volume can not be loaded and message MSGCPF6751 is sent, BRMS has been enhanced to handle the message and the backup will attempt to use other media to complete the backup.

  • The Initialize BRMS (INZBRM) command with *VFYENT (7.1 and later), *VFYNET or *VFYSYS specified for the Option (OPTION) parameter has been enhanced to include verification of BRMS communications running under user profile QBRMS.

  • Performance of save operations to large tape sets has been improved.

7.2 SI57831 - 7.1 SI57830

  • BRMS has been enhanced to support saving more than a million document library objects (DLO).

7.2 SI57831


2015-10-02 - HIPER

7.2 SI57980 - 7.1 SI57979 - 6.1 SI57978

  • Possible data integrity problems have been corrected when a system is removed from a BRMS network.


2015-08-24

7.2 SI57214 - 7.1 SI57213

  • The BRMS GUI client will now support more than 100 entries on the Enterprise Backup Status panel.

  • BRMS has been enhanced to support LTO7 tape offerings.

6.1 SI57212

  • None.


2015-06-10

7.2 SI56278 - 7.1 SI56275 - 6.1 SI56277

  • CHKEXPBRM adds additional messages to the BRMS log.

  • Recovery reports (QP1ARCY) will include BRMS user defined system names.

  • Parallel restores will try more than five alternate media sets when the Allow alternate input media field is set to *YES in system policy.

  • Avoid long delays during media movement so other BRMS jobs will not experience delays.

7.1 SI56275 - 6.1 SI56277

  • Recovery reports (QP1ARCY) will list libraries from IASPs that have not been saved using BRMS. Note: No PTF is required for 7.2.


2015-03-11

7.2 SI55731 - 7.1 SI55621 - 6.1 SI55730

  • Backups will now add message CPF3741 to the BRMS log when an object is not saved.

  • API Q1AADDCGE will now allow IASP values for the ASP Device field on *IBM control group entries.

  • Backup and archive lists displayed in the BRMS GUI client will now allow multiple items to be selected so they can be moved together.

  • The CHGMEDBRM command now supports Location and Container parameters that can be used to move a single volume to a different location or container.

  • Backups will use other available volumes before retrying media that was rejected during a previous save in the same job to improve backup performance.

  • Remote operations in a BRMS network will now do additional error recovery processing if the connection to the remote system is lost.

  • When a connection cannot be established to system in the BRMS, messages are periodically added to the BRMS log based on the value specifed for the Notify period field in the system policy. The default value for Notify period has been changed from 30 seconds to one hour.

  • Restores have been enhanced to prompt the user to load required volumes when they are not available instead of failing with a message indicating the volumes are not available.

  • BRMS operations that send message CPI3822 to the job log will now also add the message to the BRMS log.

  • Media movement has been enhanced to eject media library volumes on remote systems

7.2 SI55731

  • Additional information for IASPs has been added to the recovery report (QP1ARCY) created using the STRRCYBRM command.


2014-12-17

7.2 SI54787 - 7.1 SI54786 - 6.1 SI54702

7.2 SI54787


2014-09-18

7.2 SI53306 - 7.1 SI53305 - 6.1 SI53304

  • Command Print Report using BRM (PRTRPTBRM) has been enhanced as follows:

- support multiple values on the From system (FROMSYS) parameter

- support added for the TSM (USEADSM) parameter

- support added for the Use save files (USESAVF) parameter

7.2 SI53306

  • Backups with *SIZE specified Sort by (SORT) have been enhanced to improve performance.

  • BRMS commands have been enhanced to increase limits on the number of choices that can be displayed for parameters.

  • Backup object lists have been enhanced to allow entries to omit objects.

  • Backup object lists have been enhanced to allow entries for *ALLUSR libraries.

  • Control group entries *ALLCHGRCV and *ALLDTCRCV have been enhanced to allow journals to be excluded from the backup.

  • Recovery report QP1ARCY has been enhanced to use the Configure Device ASP (CFGDEVASP) command to configure IASPs.


2014-05-10

7.2 SI52668 - 7.1 SI52670 - 6.1 SI52666

  • Improved performance for the Add List Entry (Q1AADDLSTE) API when it is used to append entries to a BRMS link list

  • STRBKUBRM will automatically re-mount file systems after a backup is run for a control group during Backup of integrated file system objects



7.2 SI52668

  • Improved performance for installation of the BRMS license program product (LPP 5770BR1)

  • Recovery report QP1ARCY will now list libraries from independent auxiliary storage pools (IASP) that have not been saved using BRMS

 

2014-03-06

7.1 SI51667 - 6.1 SI51666

  • None


2013-12-14

7.1 SI51029 - 6.1 SI51027 - V5R4M0 SI51021

  • Improved performance for remote operations

7.1 SI51029 - 6.1 SI51027

7.1 SI51029

  • Support scheduling new backup control groups, new move policies and save of all save files in GUI


2013-10-10

7.1 SI50292 - 6.1 SI50291 - V5R4M0 SI50290

  • Answered Inquiry messages will now be left in BRMS job logs - FITS MR0612135552

7.1 SI50292 - 6.1 SI50291


2013-06-15

7.1 SI49719 - 6.1 SI49721 - V5R4M0 SI49713

  • DUPMEDBRM VOL(*SCHHST) handles more volume sequences

7.1 SI49719 - 6.1 SI49721

  • Media will be retried after an inquiry message for media that was previously unavailable

  • PRTRPTBRM FROMSYS(*LCL) will now show retention information

  • Support fully qualified domain names (FQDN) using relational database (RDB) entries

  • Support relational database (RDB) entries for all BRMS communications

  • Volumes that encounter mount problems will now have additional diagnostic information

7.1 SI49719

  • Support relational database (RDB) entries for all BRMS Enterprise communications


2013-03-15

7.1 SI48969 - 6.1 SI48967 - V5R4M0 SI48966

7.1 SI48969 - 6.1 SI48967


2012-12-15

7.1 SI47935 - 6.1 SI47934 - V5R4M0 SI47933

7.1 SI47935 - 6.1 SI47934


2012-10-03

7.1 SI47039 - 6.1 SI47038


2012-09-05

7.1 SI47039 - 6.1 SI47038

  • Allow SAVSYSBRM saves to save files when *SYSDTA is omitted.

  • Allow a 'Shared media' value of *YES for optical media classes.

  • Support *ULTRIUM6 tape format.


2012-06-05

7.1 SI46340 - 6.1 SI46339 - V5R4M0 SI46335

7.1 SI46340 - 6.1 SI46339


2012-03-06

7.1 SI45327 - 6.1 SI45326 - V5R4M0 SI45325

  • None


2011-11-08

7.1 SI44710 - 6.1 SI44709 - V5R4M0 SI44708

7.1 SI44710 - 6.1 SI44709


2011-09-15

7.1 SI43868 - 6.1 SI43869 - V5R4M0 SI43862

7.1 SI43868 - 6.1 SI43869


2011-06-15

7.1 SI42925 - 6.1 SI42924 - V5R4M0 SI42923


2011-03-15

7.1 SI42066 - 6.1 SI42065 - V5R4M0 SI42064


7.1 SI42066 - 6.1 SI42065


2010-12-15

7.1 SI41206 - 6.1 SI41205 - V5R4M0 SI41204


7.1 SI41206 - 6.1 SI41205


2010-09-15

7.1 SI40005 - 6.1 SI40006 - V5R4M0 SI40001


2010-06-15

7.1 SI38740 - 6.1 SI38739 - V5R4M0 SI38733


2010-03-15

6.1 SI37276 - V5R4M0 SI37269

Notes

  1. All BRMS activity must be stopped while BRMS PTFs are being applied. In 7.1, when a CUM package is loaded, it will cause BRMS PTFs to be applied. After BRMS PTFs have been applied, users must sign off and on again before using BRMS.

  2. BRMS PTFs should not be loaded on a system when it is in FlashCopy mode. The FlashCopy status needs to be *END. To verify the Flash copy status, run the following command:
    CALL PGM(QBRM/Q1AOLD) PARM('FLSSYSSTS ' '*DISPLAY')

  3. Systems in a BRMS network can be at different IBM i releases. However, the systems in a BRMS network should all be at currently supported releases. It is also important to keep all the systems in the network at the same BRMS PTF level. BRMS PTFs (service packs) for all supported releases are released at the same time on a quarterly basis.

  4. Due to the official end of support for IBM i release level V7R1M0 on 2018/04/30, the final BRMS PTF for V7R1M0 was released in June 2018.

  5. Due to the official end of support for IBM i release level V6R1M0 on 2015/09/30, the final BRMS PTF for V6R1M0 was released in December 2015.

  6. Due to the official end of support for IBM i release level V5R4M0 on 2013/09/30, the final BRMS PTF for V5R4M0 was released in December 2013.

  7. Starting with the March 2014 BRMS PTFs, only systems at release IBM i 6.1 or later will be supported in a BRMS network. All systems at release levels earlier than 6.1 must be removed from a BRMS network that has systems with the March 2014 BRMS PTF applied. - - Service extensions for V5R4 are no longer available
    If you have purchased the Service Extension for i5/OS V5R4, V5R4 systems will still be supported in BRMS networks with systems at release IBM i 6.1 and later.
    For the official end of release dates for IBM i releases, see Upgrade planning - Operating System Release information.

  8. Starting with the December 2015 BRMS PTFs, only systems at release IBM i 7.1 or later will be supported in a BRMS network. All systems at release levels earlier than 7.1 must be removed from a BRMS network that has systems with the December 2015 BRMS PTF applied. - - Service extensions for 6.1 are no longer available
    If you have purchased the Service Extension for i5/OS 6.1, 6.1 systems will still be supported in BRMS networks with systems at release IBM i 7.1 and later.
    For the official end of release dates for IBM i releases, see Upgrade planning - Operating System Release information.

  9. Starting with the June 2018 BRMS PTFs, only systems at release IBM i 7.2 or later will be supported in a BRMS network. All systems at release levels earlier than 7.2 must be removed from a BRMS network that has systems with the June 2018 BRMS PTF applied.
    If you have purchased the Service Extension for i5/OS 7.1, 7.1 systems will still be supported in BRMS networks with systems at release IBM i 7.2 and later.
    For the official end of release dates for IBM i releases, see Upgrade planning - Operating System Release information.