Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager on the IBM eServer iSeries Server

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.

8.1.1 Policies

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

Chapter 8. Backup Recovery and Media Services up and running 157

Figure 8-2 Control group priority order

At execution time, many of the following specifications can be overridden:

򐂰 System policy

– Should we sign off interactive users

– Who is allowed to stay active

– Ending subsystems

– Presentation controls such as which is the first day of the week, etc.

– During what time of day an IPL is allowed

– When a backup day logically starts

– Default media class

– Default media policy

– Default backup device

– Network definitions

򐂰 Backup policy

– Media policy

– Backup devices

– Default activity

• Full backup

• Incremental backup

• No activity at all

System Policy (one per operating system)

Recommended media class

Recommended media policy and device(s)

User notification and sign-off controls

IPL controls, presentation controls

Systems that share the media inventory

Start of day time

Media Monitor on/off

License information

Backup, Archive, Recovery, Retrieve, Migration

Policies (one of each, override system policy)

Preferred media policy and device(s)

Weekly activity, user sign-off controls

Operation specific controls

Control Groups

(as many as needed, override policies)

User sign-off controls

Media policy and device(s)

Weekly activity

Operation specific controls

Item controls (override group controls)

Weekly activity

Operation specific controls

Note: As for all the other policies, some specifications are only found here. Others are

defaults if not specified elsewhere.