Enhanced Omits From Backups

Backup omit order of processes

Users can designate libraries and objects to omit from backups in various ways. The Work with Policies using BRM (WRKPCYBRM) command WRKPCYBRM TYPE(*BKU) menu option 2 can be used to create a global list of omits that apply to all backups. Using the GUI, users can add object omits for a specific control group entry to omit specific libraries or objects. With the Work with Lists using BRM (WRKLBRM) command, users can exclude libraries, objects, and folders from backup lists.
 
BRMS used a hierarchy of precedence for processing backup omits. Omissions created with the GUI would be given precedence over other omits created with *BKUPCY commands. WRKLBRM *BKU lists using the *EXC parameter functioned with the GUI created omit. This behavior, in effect gave any GUI or WRKLBRM *BKU list created omit authority to disqualify all other *BKUPCY omits.

This hierarchy is now more precise, considering each entry in a control group or list to determine if the a GUI created omit overrides a *BKUPCY omit. Omits for *SAVSYS, *SAVCFG, *SAVSECDTA, and *ALLDLO control group entries with the GUI omits will disqualify any *BKUPCY omits for the corresponding control group entry. For *ALLUSR, *ASPnn, *IBM, and generic library entries, BRMS will combine GUI and *BKUPCY omits.

Consult the two examples in this section for more information about this enhancement:



Example: omitting objects from an *ALLUSR save

This example compares and contrasts the differences between how BRMS for the IBM i system processed omits created by various methods prior to the July 2019 BRMS PTFs with how BRMS can process omits in an enhanced method beginning with the July 2019 BRMS PTFs: 7.2f SI70366, 7.3f SI70367, and 7.4 SI70368. The default omit processing behaviors still function as normal but users now have the option to use an additional feature to combine omits that were created by separate, different methods. 

About this task

In this example scenario, the tasks of omitting objects from the *ALLUSR backup control group entry are performed on IBM i Series systems using both additions to the *BKUPCY and the BRMS GUI to demonstrate how the various omits are processed. A simplified example of an *ALLUSR that resolves to 5 libraries is used:

  • LIB1

  • LIB2

  • LIB3

  • LIB4

  • LIB5

Some of these libraries will be omitted with the Work with Items to Omit from Backup display and others will be omitted in the BRMS GUI.The example scenario assumes that the user:

  • has an *ALLUSR control group entry.

  • omitted LIB2 and LIB3 from any *ALLUSR saves from option 2, Work with Items to Omit from Backup in the Backup Policy (WRKPCYBRM *BKU) menu or Work with Backup Control Groups in BRMS (WRKCTLGBRM) screen using option F10.

  • used the BRMS GUI to add an omit of all the physical file objects from LIB1 for the *ALLUSR control group entry.

The user proceeds to run a backup for this *ALLUSR control group.



Note - If using the Interface to Control Which Control Groups Will Not Use the Select User Space Code option , omits in object lists will be ignored. If the user space is set up to not use the *SELECT option (ie it has a value in it), the excludes in object lists should not be used, ie omits will be ignored. If they are, users may see BRM14A1 listed in the job log

                        CALL PGM(QBRM/Q1AOLD) PARM('Q1ANSELECT' '*DISPLAY  ')   



Procedure

Default procedure (without using the enhancement)

First, a backup is run with the default processes in place.

  1. When STRBKUBRM CTLGRP(ALLUSR) OMITS(*PROCESS) is run from the command line:

    • the libraries LIB1, LIB2, LIB3, LIB4, and LIB5 backup.

    • all physical file objects are omitted from the backup of LIB1.

    The backup control group contains both GUI and BKUPCY created omits, only the GUI omits are processed.

  2. When STRBKUBRM CTLGRP(ALLUSR) OMITS(*IGNORE) is run from the command line:

    • LIB1, LIB2, LIB3, LIB4, and LIB5 all backup fully.

    • all physical file objects are in LIB1 are included in the backup.

    The *IGNORE parameter overrides all omits in this control group.

Enhanced procedure (using the enhancement)

Next, the backup employing the new functionality is enabled with one of the following commands:

  • CALL QBRM/Q1AOLD PARM('SETUPFUN' '*SET' 'Q1ACGOMITS' '*SYS') which enables the new functionality for all BRMS backups.

  • CALL QBRM/Q1AOLD PARM('SETUPFUN' '*SET' 'Q1ACGOMITS' '*JOB') which enables the new functionality for the current signed on job only.

  1. When STRBKUBRM CTLGRP(ALLUSR) OMITS(*PROCESS) is run at the command line.

    • LIB1, LIB4, and LIB5 all backup.

    • all physical file objects are omitted from the backup of LIB1.

    Both the BKUPCY omits created with the command line, and the omit added using the GUI are processed.

  2. When STRBKUBRM CTLGRP(ALLUSR) OMITS(*IGNORE) is run at the command line.

    • LIB1, LIB2, LIB3, LIB4, and LIB5 all backup fully.

    • all physical file objects are in LIB1 are included in the backup.

    The *IGNORE parameter continues to override all omits created for this control group.

Example: omitting entries in an *OBJ list in a control group

This example compares and contrasts the differences between how BRMS for the IBM i system processed omits created by various methods prior to the July 2019 BRMS PTFs with how BRMS can process omits in an enhanced method beginning with the July 2019 BRMS PTFs: 7.2f SI70366, 7.3f SI70367, and 7.4 SI70368. The default omit processing behavior remains the same. The existing *OBJ list function already combines *OBJ list excludes with BKUPCY omits..

About this task

In this example scenario, the tasks of omitting entries from an *OBJ list control group entry are performed on IBM i Series systems using both additions to the *BKUPCY and an object list to demonstrate how the various omits are processed. A simplified example of an *OBJ list control group *ALLUSR entry that resolves to 5 libraries is used:

  • LIB1

  • LIB2

  • LIB3

  • LIB4

  • LIB5

Some of these libraries will be omitted with the Work with Items to Omit from Backup display and others will be omitted in an object list.The example scenario assumes that the user:

  • control group entry ALLUSRLST *OBJ list containing an *ALLUSR entry and an entry to exclude of all the physical file objects from LIB1 in the *OBJ list.

  • omitted LIB2 and LIB3 from any *ALLUSR saves from option 2, Work with Items to Omit from Backup in the Backup Policy (WRKPCYBRM *BKU) menu or Work with Backup Control Groups in BRMS (WRKCTLGBRM) screen using option F10.

The user proceeds to run a backup for this ALLUSRLST control group.

Procedure

The default procedure (without using the enhancement) and the enhanced procedure (using the enhancement) runs the backup with one of the following commands:

  • CALL QBRM/Q1AOLD PARM('SETUPFUN' '*SET' 'Q1ACGOMITS' '*SYS') enables the new functionality for all BRMS backups.

  • CALL QBRM/Q1AOLD PARM('SETUPFUN' '*SET' 'Q1ACGOMITS' '*JOB') enables the new functionality only for the current job.

1. When STRBKUBRM CTLGRP(ALLUSR) OMITS(*PROCESS) is run at the command line:

  • The libraries LIB1, LIB4, and LIB5 are backed up.

  • All physical file objects are omitted from the backup of LIB1.

Both the BKUPCY omits and the excludes from the *OBJ list are processed.

2. When STRBKUBRM CTLGRP(ALLUSR) OMITS(*IGNORE) is run at the command line:

  • All libraries, LIB1, LIB2, LIB3, LIB4, and LIB5 are backed up completely.

  • All physical file objects are omitted from the backup of LIB1.

The OMITS(*IGNORE) parameter does not apply to an *OBJ list, the omits are always applied.



Summary:


Parm 1: Char 10 - 'SETUPFUN '
Parm 2: Char 8 - Action - *SET, *DISPLAY, *REMOVE
Parm 3: Char 10 - Function name
Parm 4: Char 4 - Scope of data function valid values:

*JOB - job level - create data area in QTEMP
*SYS - system level - create data area in QUSRBRM



To Enable

CALL QBRM/Q1AOLD PARM('SETUPFUN  ' '*SET    ' 'Q1ACGOMITS' '*JOB')    - set up to for current job only

CALL QBRM/Q1AOLD PARM('SETUPFUN  ' '*SET    ' 'Q1ACGOMITS' '*SYS')    - set up to affect all jobs



To Remove:

CALL QBRM/Q1AOLD PARM('SETUPFUN  ' '*REMOVE ' 'Q1ACGOMITS' '*JOB')  - remove for current job only

CALL QBRM/Q1AOLD PARM('SETUPFUN  ' '*REMOVE ' 'Q1ACGOMITS' '*SYS')  - remove for all jobs



To check what is setup:

CALL QBRM/Q1AOLD PARM('SETUPFUN' '*DISPLAY' 'Q1ACGOMITS' )