156 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
8.1 BRMS operations
This section elaborates on most of the common BRMS issues. In the BRMS base product,
objects may already be created to make it possible to take a full backup. The predefined
setups are probably not what you want to run in production, but they give you a good starting
point with a minimum amount of additional tailoring. We recommend that you begin using one
of these predefined setups to quickly have a good level of protection. Then you can be sure
that every object is backed up at least once.
To assist in your backup and recovery processes, BRMS keeps track of which objects you
have not included in your backup strategy. Those left out are found in the BRMS log. In
addition, there is a separate exception report.
Typically you see such BRM1570 messages as:
Library AH is not included in save strategy.
Library ALEKN is not included in save strategy.
Library ANZFLTS is not included in save strategy.
Library APILIB is not included in save strategy.
Library AS0301LIB is not included in save strategy.
BRMS uses policies that define a set of standards. In many levels of definition within BRMS,
you find the same parameter. If specified, BRMS selects the parameter value specified at the
lowest level. If nothing is specified at a lower level, BRMS tries to find a value for that
parameter at the next level until it reaches the top level for that parameter. A parameter’s top
level can be in any of the policies that are defined. An example is the weekly activity. Its
ending point is the backup policy. Nothing is found about weekly activities in the highest level,
which is the system policy.
Figure 8-2 shows how this works. It also shows a run-time priority order that is embedded.
The selection order is:
1. Item overrides
2. Control groups
3. Backup, Archive, Recovery, Retrieve, Migration policies
4. System policy