How To
Summary
This document explains how to correctly use the BRMS created cloud control groups QCLDBSYS0x, QCLDBIPL0x, QCLDBGRP0x, and QCLDBUSR0x, and make copies of these control groups if customization is needed.
Steps
As documented on the BRMS wiki https://helpsystemswiki.atlassian.net/wiki/spaces/IWT/pages/165642265/System+Backup+and+Recovery+from+the+Cloud), the QCLDBxxxyy control groups should not be updated or changed.
What if you want to update/change what is saved, retention periods of data saved, etc.
What if you want to update/change what is saved, retention periods of data saved, etc.
The recommended option is to copy the BRMS created cloud control group(s) to user cloud control group(s) using the name format of QCLDUxxxyy. For example, if you want to copy QCLDBIPL01, name the copy QCLDUIPL01. The naming convention is very important, particularly with QCLDBIPLxx and QCLDBGRPxx as the IPL and GRP are key in forcing those groups to virtual optical instead of virtual tape.
If you are trying to create a daily backup of some user libraries to virtual tape you should copy QCLDBSYS01 or QCLDBUSR01. In this example, you have a little more flexibility as the names just need to start with the QCLDU prefix. For example, you could copy QCLDBSYS01 and call it QCLDUDAILY.
Once the new user created control group(s) are created, users can change what is going to be backed up, add *EXITs, retain object level detail, use Save-while-active, save private authorities etc.
In the new user control group(s), all attributes can be updated except:
- The Backup Devices
- The media polices used must match an existing ICC configuration resource name.
Note - using a User created media policy that does not match an ICC resource will cause the BRMS created control group (QCLDBxxxyy) to be deleted when BRMS maintenance or INZBRM OPTION(*DATA) is run. - Options 9 and 10 on a control group can be updated as needed, however, it is recommended user created cloud control groups are used if any changes are needed.
If you need to use different media retention periods there are two options:
- Create a new ICC resource with the same attributes as the original one and then update the new media policy that will be created with the new retention policy. One media policy/ICC resource can be used for FULL backups and the other for Incremental backups or different retention periods
- Change the existing media policy to the retention period required.
If the media policy of one of these BRMS created control groups does not match one of the existing ICC resources, it may be deleted when BRMS maintenance or INZBRM OPTION(*DATA) is run.
If the media policy of any user created cloud control group does not match one of the existing ICC resources, backups may not run as expected.
To recreate or refresh the BRMS created control groups, follow instructions in this document:
https://helpsystemswiki.atlassian.net/wiki/spaces/IWT/pages/965869581/Refresh+BRMS+Turnkey+Cloud+Control+Groups
https://helpsystemswiki.atlassian.net/wiki/spaces/IWT/pages/965869581/Refresh+BRMS+Turnkey+Cloud+Control+Groups
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB68","label":"Power HW"},"Business Unit":{"code":"BU070","label":"IBM Infrastructure"},"Product":{"code":"SWG60","label":"IBM i"},"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"7.3.0"}]
Was this topic helpful?
Document Information
Modified date:
15 November 2024
UID
ibm17176228