...
CALL QBRM/Q1AOLD PARM('HSTUPDSYNC' '*ADD' ‘SYSTEM’ ‘NETWORK 'SYSTEM' 'NETWORK ID' 'IASPNAME' '*CHGSYSNAM')
...
CALL QBRM/Q1AOLD PARM('HSTUPDSYNC' '*ADD' ‘SYSTEM'SYSTEM' ' ‘NETWORK NETWORK ID' 'IASPNAME ' '*NORMAL')
...
CALL QBRM/Q1AOLD PARM('HSTUPDSYNC' '*REMOVE' ‘SYSTEM'SYSTEM' ' ‘NETWORK NETWORK ID' 'IASPNAME ' )
To remove all systems:
...
CALL QBRM/Q1AOLD PARM('HSTUPDSYNC' '*DISPLAY')
Specific System Synchronization support for *SYSBAS
With the increased use of High Availability (HA) strategies and replication software being utilized in IBM i system environments, the BRMS recovery report needs be able to combine two systems backups into a single recovery report. The goal of this combined recovery report is to prevent replicated data from being saved multiple times, yet still being available for recovery from any system. To achieve this, the Specific System Synchronization support for IASP is being enhanced to additionally include support for *SYSBAS available in versions 7.3 and later with the following PTFs:
7.5 SI78291
7.4 SI78290
7.3 SI78289
To activate this behavior, run the following command on the target HA system:
CALL QBRM/Q1AOLD ('HSTUPDSYNC' '*ADD' 'Source_HA_System_Name' 'Source_HA_Network_ID' '*SYSBAS' '*CHGSYSNAM')
IMPORTANT: All entries need to be in upper-case characters
Once activated, history for non-system related backups on the Target HA System will be synced to the new owning system (the Source HA System) with the system name changed to make it appear that the backup was run on the new owning system.
The following backup history will NOT be synced:
*SAVSYS
*SAVCFG
*SAVSECDTA
System libraries (Library names that start with 'Q')
Libraries that start with # that are system libraries:
#CGULIB, #COBLIB, #DFULIB, #DSULIB, #RPGLIB, #SDALIB, #SEULIB
Recovery reports run on the Source HA system will now combine all backups run on the Source HA System and all non-system backups from the Target HA System.
To disable this behavior, run one of the following commands on the target HA system.
To stop all syncing of history to the Source HA System:
CALL QBRM/Q1AOLD ('HSTUPDSYNC' '*REMOVE' 'Source_HA_System_Name' 'Source_HA_Network_ID' '*SYSBAS')
To continue syncing history, but without changing the owning system of the history:
CALL QBRM/Q1AOLD ('HSTUPDSYNC' '*ADD' 'Source_HA_System_Name' 'Source_HA_Network_ID' '*SYSBAS' '*NORMAL')
NOTES:
- Only libraries and IFS data backed up from an IASP can have it's ownership changed prior to the June 2022 PTFs mentioned above. Items saved from *SYSBAS are not supported until the June 2022 PTFs are applied.
- Data backed up to save files or TSM will not be synchronized.
- Object level detail is not synchronized and will only be available on the system that did the backup.
- The following commands will not list any data
- WRKOBJBRM
- WRKMEDIBRM Option 9
- WRKLNKBRM DIR(/MYDIR1)
- Use the FROMSYS() parameter on the above commands to view/restore individual objects or use WRKMEDBRM VOL(xxxxxx)
- The following commands will not list any data
- Works with reports created via Start Recovery using BRM (STRRCYBRM) and Start Maintenance for BRM (STRMNTBRM)
- Volume ownership will remain with the system that did the original backup
- If using this option, STRRCYBRM ASPDEV(XXXXXXXX *ALL) - where XXXXXXX is the flash copy system - will no longer work. *LCL needs to be specified for this parameter.
- If planning on duplicating the volumes with DUPMEDBRM ,
- The volume(s) need to be duplicated on the system that did the backup or,
- Duplicate history ownership will be lost if remote duplicates are done.
- When using STRRCYBRM OPTION(*ASPDEV) ASPDEV((XXXXXXX IASPNAME)), the libraries have to exist in the IASP of the system where the command is being run.
- Saves to BRMS save files are not synchronized between systems
- If the target LPAR is at a higher release than the source LPAR, *ALLUSR cannot be used. Individual or generic library names would have to be used.
- If LIB(*NONSYS), LIB(*ALLUSR), or LIB(*IBM) is specified, only the current release can be the target release.