Running Non-Restricted and Restricted State Functions in BRMS

When using BRMS control groups (WRKCTLGBRM), it is possible to add user commands using the *EXIT option for the backup item. These commands can run many different backup items or end/start applications.

First and Last *EXIT
If used, these are processed outside of the control group. The first *EXIT is the pre-control group exit that runs before any of the control group attributes are run (signing off users, ending subsystems, holding job queues, and so on). The last *EXIT is the post-control group and is run after all entries in the control group have been run.…

Cleaning up BRMS Data Files

BRMS is not a set it and forget it backup and recovery application.  Since BRMS uses database files to store information, some of these files can get large and have many records inserted and/or deleted every day.  There are ways that you can clean up BRMS data files on a regular and as-needed basis.

Regular BRMS data files cleanup strategy:

BRMS recommends that the Start Maintenance for BRM (STRMNTBRM) command with *YES specified for the reorganize BRMS database (RGZBRMDB) parameter, is run at least once a month to clean up the files.  Because it can take a long time to reorganize the BRMS database, it may be desirable to reorganize the BRMS database in batch using the STRMNTBRM command, and performing this when no other BRMS activity is being performed.  The more often you run it, the less time it takes to run.  I would recommend running daily, as part of your BRMS strategy to include:…

Webinar: Basics of IBM i Backup and Recovery

Understand the different ways to save your system, using BRMS or traditional native commands. Learn about what you need to restore your system, and the steps involved to perform the restore. Tips will be given along the way on best practices.

This webinar will cover:

  • Understanding basic backup and recovery
  • If you are saving the right information to recover your system
  • What you need to know to recover your system

[Watch Now ]



Excluding Items from the IFS backup in BRMS

I have been asked by customers using BRMS, if there is an easy way to exclude objects in the IFS, that are unable to be saved, when using *LINK, to prevent getting the softer error: “Save of list *LINK completed with errors” (BRM10A1 is issued)”.

There are several methods:

  • Create and use a BRMS backup list in your backup control group, type *LNK, specifying the IFS directories or files you want to include and omit, and use that as a backup item *LNK in your BRMS backup control group for saving IFS information.
  • When using *LINK, list type *LNK, as a backup item in your backup control group, for saving the IFS, use the BRMS backup list, type *LNK, QLNKOMT, to specify any directories or links to be excluded from a *LNK backup, by adding them to the OQLNKOMT user-modifiable list.  This is the method I will discuss in further detail in this article.

BRMS *SAVSYS BYPASSED for a Control Group

Have you ever seen or gotten a BRM1744 during a BRMS full system save or SAVSYSBRM?  Here is what you need to do to resolve this, and I am only going to address V5R3M0 and above. When a SAVSYS is performed through BRMS using a backup control group or the SAVSYSBRM command, BRMS will automatically attempt to end the system to a restricted condition by issuing the following command: