BRMS Backup

Business Unit or Product Name
iSeries - Backups Using BRMS
RISHI RAJ SINGH K.R.

risingh7@in.ibm.com
1 Presentation Title | Presentation Subtitle | Confidential © 2007 IBM Corporation

Purpose
 Why Backups ?
 How to plan your backup ?
 BRMS Application
 Functionality of Media Library
 Domino Online Backup

Objective
 After the session you would be able to

 Resolve problems with backups
 Understand how BRMS functions and its parts.
 Able to schedule backups on AS400 machine

Backup
 Backup -> making copies of data so as to restore the original after a data
loss event.
 Importance
– Restore a computer to an operational state following a disaster
(called disaster recovery).
– to restore small numbers of files after they have been accidentally
deleted or corrupted

Backup Types
 Full
 Incremental
 Differential or Cumulative

Incremental Vs Cumulative
Sun Mon Tue Wed Thu
Object A A+a A+a+b A+a+b+c A+a+b+c+d
Full A A+a A+a+b A+a+b+c A+a+b+c+d
Incr a b c d
Cum a a+b a+b+c a+b+c+d
Tape AS01 AS02 AS03 AS04 AS05
AS01 AS01,AS02 AS01,AS02,AS03 AS01, AS02 , AS03, AS04 AS01, AS02, AS03, AS04,
AS05
Incremental
Cumulative AS01 AS01,AS02 AS01,AS03 AS01,AS04 AS01,AS05

Implementing Backups Strategies
 Backup to Tapes – Objects are saved on the tapes and then tapes are moved
to a different location for storage.
 Backup on another Server – Any change on the primary server is copied on

the backup / Mirror server with the help of a Replicator e.g. Mimix.

BRMS
GO BRMS

BRMS

BRMS Standard Product
The standard product provides capability to implement

– Fully automated backup,
– Recovery
– Media management strategy for your iSeries system

BRMS Advanced Functions Feature
 The BRMS Advanced Functions feature provides hierarchical storage

management (HSM) capability which includes
– Archive,
– Dynamic retrieval,
– Automatic auxiliary storage pool (ASP) migration

Backup
 Assists in establishing a disciplined approach to design and manage backup

operations.
 Helps to define, process, monitor and report backup activities.
 Used to back up all of the data on iSeries system including objects in

libraries, folders, directories, spooled files, security information, system
configurations, and the operating system itself.
– This can be achieved thorough various control groups

Recovery:
 Provides for the orderly retrieval of lost or damaged data
 Recovery reports helps to recover the system sequentially .Reports contains

restore instructions as well as tapes details
With BRMS, you can restore your entire system, or selected items such as
control groups, libraries, objects, folders, auxiliary storage pools (ASPs),
spooled files, or Integrated File System links.

Media Management
 Tracks all the tapes and save files. Media is tracked through all cycles from
creation to expiration.
 Tracking process includes active use, storage location, and return to scratch
pool availability.
 Tracks media until you remove it from the media inventory or until it is
otherwise disabled due to usage threshold or poor quality rating.
 Records and updates changes to the media inventory.

BRMS Policies
 Policies define how BRMS operations are generally to be done

 This is similar to the ways in which system values control how your iSeries
operates.
 They establish actions and assumptions that are used during processing.

BRMS Policies
 They also provide a single point of control for administering broad changes in
operating principles.
 Each policy provides a template for managing backup and media
management strategies at high levels.

Type of Policies
 The standard BRMS package provides the following policies

– The System Policy :-
– Similar to a set of system values.
– In Absence of any policies system policy parameters determine the policy defaults for BRMS
operations

Types of Policies
– The Backup Policy :-

– Specifies how to perform backups.
– Define weekly backup activities
– Types of incremental backup,
– Level at which media information is saved.
– One backup policy governs all backup operations. You can define or change these operations at
the control group level.

Type of Policies
– The Recovery Policy
–Defines how recovery operations are generally to be

performed.
–One recovery policy governs all recovery operations.

Types of policies
– The Media Policy

– Govern the handling of media by media type.
– Determine retention periods
– Instruct BRMS where to find the appropriate tapes to perform
your backup.
– Determine if backup operations will create and use save files.
– Unlike system, backup, and recovery policies, multiple media
policies can exist

Type of Policies
– The Move Policy
– determines the movement of media from creation through

expiration, and through various on and off site storage locations.
– Multiple move policies can also exist

BRMS Control Groups
 Consist of groups of libraries, objects, folders, spooled files, and

other types of data that share common characteristics or that can be
grouped together for backup purposes.
 Policies determine how data is processed, control groups determine,

by their content, which data to process.
 Specify kinds of backup to perform, such as full, incremental, or

cumulative-incremental.

BRMS Control Groups
 Specify which days the data will be processed, and the order in which
the processing occurs.
 Control groups usually refer to, and work with, related policies.
 You can set control group attributes to override policy decisions.
 Though you cannot create control groups specifically for a recovery

job, BRMS does efficiently recover data by control groups.

How Policies and Control Groups Work

Together
 The media, move, backup, and recovery policies are sometimes called
function policies because they pertain to specific, core BRMS functional
activities.
 The system policy is called a global policy because BRMS applies many of
its values to the core functional activities.


Policies
 The system policy is global and encompasses the function policies

and the control groups.
 The information contained in system policy parameters overrides

information that is contained in function policy parameters.
 By the same token, function policy information, unless otherwise

altered, overrides control group information.

Policies
 Since save and restore needs vary depending on customer needs, policies
and control groups that share the same parameters and values can override
one another.
 In this way, a function policy value can override a shared system policy value,
and a control group value can override a shared function or system policy
value.

System Policy

Backup Policy

Backup Policy

Control Group

Control Group

Tip
 If you have modified the default values, you can reset these back to the
default values by running the INZBRM OPTION(*DATA) command.

How the standard function work together

The building blocks of BRMS/400
 What: This information is held in the backup control group. The timing
of the backup is determined by how often you schedule the backup of
each backup control group.
 How: Next task is to choose the media which is determined by media

class, which in turn comes from the media policy.
 The media policy also specifies if the data should be staged through
a save file before being committed to the media. The media policy is
specified in the attributes of the backup control group.

The building blocks of BRMS/400
 Where: The journey that media is defined in a move policy. The

move policy is specified in the media policy.
 How long: Nightly backups may need to be retained for one week,
where monthly backups may need to be retained for one or more
years.
 The retention information is specified in the media policy.

Storage locations
• Storage locations define any place where media is stored.

• Two storage locations are provided as defaults with BRMS/400:
– *HOME: The default on-site storage location

– VAULT: The default off-site storage location

Storage Location
 Storage Location in the media policy instructs where to look for a tape to
perform backup.
 Normally this is the scratch pool or the automated tape library, but it can also
be another location.
 The default for the storage location parameter in the media policy is *ANY.

Storage Location
 One should review this parameter, especially if one permit media to expire in
a location other than the “home” location so that BRMS/400 does not request
the mount of a tape that is not even on-site.
 For media libraries, one must be careful in specifying the storage location to
ensure it only indicates tapes that are “inside” of the library.

Storage Location
 Work with Storage Locations (WRKLOCBRM) command display the

storage locations that are defined for BRMS/400.
 The WRKLOCBRM command can also be used to add, change, or

remove storage locations.
 We can work with media or containers that are in the storage

locations by selecting additional parameters when using the change
option for a specific storage location.



A Media Policy

Media Policy
 There are two important field parameters which needs to be set correctly:
– Allow volumes to expire: Should be set to *NO for your off-site location. One could select *YES
for a storage location that is physically located near the system such as the computer room or a
tape library.

Media Policy
 Media slotting:
– *YES if media is to be filed and tracked by individual slot numbers at storage locations
– Media slotting is optional and can be used for some storage locations and not for others,
– *HOME is set to a media slotting value of * NO. VAULT is set to a media slotting value of
*YES.

Media Policy
– Media can be assigned a slot number when it is added to the BRMS/400 media inventory using
the Add Media to BRM (ADDMEDB RM) command.
– Slot numbers can be changed using the Change Media in BRM (CHGMEDBRM) command.

Media devices
 Work with Devices using BRM (WRKDEVBRM) command shows all of the
devices and their associated type and model that are defined to BRMS/400.
 This command allows to add, change, or remove a device from a list of

devices
 For adding a device, it must already be defined to the system through the
device description (CRTDEV*) function.

WRKDEVBRM

Option 2- Change

Media classes
 Media classes define the types of physical media that are used for
backup, archive, or recovery operations
 Within each type of physical media, there may be a further distinction

by format or capacity.
 BRMS/400 creates classes for all media types supported by the

drive. The Work with Media Classes (WRKCLSBRM) command can
be used to add, change, or remove media classes

WRKCLSBRM

Media classes
 An additional media class called SAVSYS is automatically created by

BRMS/400 for the alternate IPL tape device.
 The media class for SAVSYS should not be shared .This is because
–You would not like to share your media with another system.
–During SAVSYS system is in restricted state so no

communication lines will be active. Hence no check can be
made if the shared volume is also in use on another system.

Move policy
 BRMS volume movement is normally controlled using a move policy

WRKPCYBRM TYPE(*MOV).
 A default move policy of OFFSITE is created when BRMS/400 is installed.

A simple move policy

Move policy
 The move policy is associated with an expired volume when it is

saved
 Once the volume has followed all the sequences in the move policy
and reached the home location, the move policy is removed from the
volume.
 In addition, the volume will not have a move policy associated with
it. This normally occurs when the volume expires.

Move policy
 When a volume is used and a move policy is associated with the

volume, the volume will be at the location of the standalone tape
drive or that of the Tape Media Library.
 Once the move policy is associated with the volume and media
movement is run (via maintenance ( STRMNTBRM MOVMED(*YES)
) or via media movement (MOVMEDBRM) commands), the logical
location of the volume will change.

Move policy
 If move verification is *YES in the move policy, the change in logical

location occurs after VFYMOVBRM is run
 The volume then follows the sequences in the move policy.
 Once it reaches the last sequence and it is complete, it moves to the

home location specified in the move policy. (The default is
*SYSPCY which refers to the home location specified in the system
policy - WRKPCYBRM TYPE(*SYS) , Option 1 )

Example
 Volumes are in a tape library, TAPMLB01, and will move to an on-site vault for 3 days and then
move off-site until they expire. Once they return, they will be placed back in the tape library.
Move policy . . . . . . . . . . : MYMOVEPCY

Home location . . . . . . . . . : TAPMLB01
Use container . . . . . . . . . : *NO
Verify moves . . . . . . . . . : *NO
Calendar for working days . . . : *ALLDAYS
Calendar for move days . . . . : *ALLDAYS
Text . . . . . . . . . . . . . : Entry created by BRM configuration
Seq Location Duration
10 VAULT 3
20 OFFSITE *EXP
 Once the volume is moved to TAPMLB01, the move policy for that volume is changed to *NONE

Tips
If you are planning to use APPEND(*YES) as part of your backup policy, you
must make sure that the move policy keeps the tape on-site for enough
days.

Media policy

Media policy
 Media Policy = { Retention Period, Media Class, Move Policy }
 Media policies are designed / created keeping in mind the retention period
and the media class that has to be used. So we can say Media Policy as a
function consisting both of them as an element

Default Media Policies
 With the installation of BRMS/400, there are three default media policies:
– FULL (35 days retention) with a move policy of OFFSITE
– INCR (incremental, 14 days retention) with a move policy of *NONE
– ARCHIVAL (1725 days retention) with a move policy of *NONE

Change Media Policy

BRMS/400 policies
 The seven types of policies are:

– System policy
– Media policy
– Move policy
– Backup policy
– Archive policy
– Retrieve policy
– Recovery policy

System and backup policies
 The system policy is the same as a set of system values

 Unless other controls are in effect, the system policy determines the default
for all users

System Policy
 Provides defaults for

– Default media policy, tape device, location of media
– Whether to sign off interactive users before a backup or archive function is started, or specify a
list of users and devices that continue to remain active.
– License information and default values for displaying BRMS/400 log.

System Policy
– List of subsystems to check before performing an IPL. If any of the subsystems in the list are
active when an IPL is scheduled, BRMS/400 does not perform an IPL.
– Presentation controls such as characters used for full backup, incremental backups, and
defining the first day of the week

System Policy

Backup Policy
 As with the system policy, you can also change the backup policy to tailor
some of the parameters based on your backup strategy.

Backup Policy

Backup Policy

Backup Policy - Parameters
 The Default weekly activity : Defines type of backup to be run on days of

week.
– “F” – Full Backup ( SAVLIB )
– “I” – Incremental Backup ( SAVCHGOBJ)
– “Blank” – No Backup for that day .

 Incremental Type – Specifies the type of backup
– “*CUML” -- save all of the changes to the objects since the last full backup (SAVCHGOBJ with
default values)
– “*INCR”-- save the changes to the objects since the last incremental backup (SAVCHGOBJ
command with the reference date (REFDATE) and reference time (REFTIME) values)

 Save access paths : save access paths associated with your physical and
logical files
 Recommended : *YES
 Drawback : System save may take longer time there by decreasing system
availability .
 But it will be very difficult to restore the system if you do not save Access
Paths.

 Append to media- specifies whether to add data files on existing media with
active files or to begin a new volume
 “*YES” - files are written to the volume immediately following the last active
file

Backup Policy
 Libraries to omit from backups

Backup control groups

 A backup control group can be considered to be an interpretive CL

program for performing backup.
 Advantage over a CL program is that it is easy to create, easy to

change, easy to execute, and provides full error checking while
maintaining the flexibility and function that a CL program offers, all
without requiring CL programming skills.
 A save strategy for a system consists of multiple backup control

groups which define what is backed up and when.

 Used to back up
– a single library,
– a group of related libraries,
– a set of objects or
– folders defined by a Backup List, and
– certain predefined components of the system such as configuration or security data.

 It can also include special operations to tell the operator to load a new tape
or execute an exit program.
 This program can send a message to operations or users, start a

subsystem, or do anything you choose.

Backup Activity
 Backup Activity is defined as a part of BRMS control group.
 It identifies which days of the week the backup list performs a backup and
whether the backup is a full (save entire object) or incremental (save
changed object) save.

Default backup control groups
 1. *BKUGRP - control group controls backing up user data

 2. *SYSGRP - control group controls backing up IBM data

*BKUGRP

*SYSGRP

backup control groups
 Default control groups do not provide facility to hold a job and release certain
job queues or subsystems, or save spooled files.
 Either change the default control groups or create a new to tailor how to
manage system during a BRMS/400 save

Job queue processing from control group
 Specify the job queues that you may want to hold during the control group
processing
 WRKCTLGBRM -> Option 10

Subsystem processing from control groups
 One can also include a list of subsystems that you may want to shut down
and restart (if required) after the backup control group has completed
 WRKCTLGBRM - > Option 9


Backup Items
 Special operations
 *EXIT - perform user command processing
 *LOAD - begin new tape
 Special values
 *ALLDLO - save the document library, all ASPs
 *ALLUSR - save all user libraries
 *ALLPROD - save all *PROD type libraries
 *ALLTEST - save all *TEST type libraries

Backup Items
 *IBM - save all IBM libraries

 *LINK - save all objects not in /QSYS.LIB and /QDLS
directories
 *QHST - save history information
 *SAVCFG - save configurations
 *SAVSECDTA - save security data
 *SAVSYS - save the operating system

List Type
 List is nothing but group of similar objects .

 It can be of following types.
 Folder - *FLR
Object - *OBJ
Spooled file - *SPL
File system - *LNK
 To create a list we use command WRKLBRM

WRKLBRM

Retain Object Details
 Whether to keep the object level details is defined by this parameter.
 The options are

– *ERR - Objects that were not saved due to an error condition are identified.
– *NO Do not keep object detail for an entry in the backup items list. You can retrieve at the library
level from the backup history.

 *YES Save object details for an entry in the backup items list. This allows
object retrieval from the backup history. Member level details are kept for
physical files in addition to object detail.
 *OBJ Object detail is kept in the BRMS backup history. No member level
detail is kept.

 *MBR Object detail is kept in the BRMS backup history.

– Note: Member level information is included in the object detail for physical files.
– Note: This choice is the same as *YES.

Adding Media into BRMS
 ADDMEDBRM ( Tape Drive )

 ADDMLMBRM ( Media Library )
 Media can be enrolled into the BRMS/400 media inventory at any time. The
only requirement is that the media must be known to BRMS/400 prior to any
save or restore operation

ADDMEDBRM

ADDMEDBRM

ADDMLMBRM

Appending to media rule
 Field Append(*YES)
 Ensure volume availability onsite.
 Selection for media is done for all devices
– Media Library – automatic
– Stand Alone – BRM1472 messages is issued specifying the suitable
volume
 Selects an active volume that matches the requesting media policies, and the
volume must pass the following checks:
– Same expiration date
– Owned by the requesting system
– Same move policy
– Same secure attributes

Appending to media rule
 Fails to find media of same EXP date then finds an earlier expired volume
starting with the earliest .All other test must match
 Else selects any expired volume from the same system
 If fails at previous point then contacts another server ( only if media library is
present ) through DDM

Media security
 BRMS /400 enrolled media can not be initialized by INZTAP

command ( native OS/400 )
 Special Authority required : *SECOFR,*SAVSYS,*SERVICE ,

*ALLOBJ
 No Authority .Error message thrown asking user to use INZMEDBRM

command which checks the data on the tape

GO SAVE and BRMS
Select one of the following: Command Command
Save Data SAVOBJ SAVOBJBRM

1. Files SAVLIB SAVLIBBRM
2. Libraries SAVDLO SAVDLOBRM
SAVOBJ *PGM SAVOBJBRM *PGM
3. Documents and folders SAVOBJ *ALL SAVOBJBRM *ALL
4. Programs SAVCHGOBJ SAVACT parameter *YES
5. Other objects SAVLICPGM *SAVSYS
6. Changed objects only SAVSECDTA *SAVSECDTA
SAVSTG
7. Licensed programs SAVCFG *SAVCFG
8. Security data SAV SAVBRM
9. Storage
10. Configuration
11. Objects in directories

GO SAVE and BRMS
Save System and User Data Command BRMS Command
20. Define save system and user Policies.

data defaults
SAVSYS,SAVLIB, SAVDLO,SAV *SYSGRP,*BKUGRP
21. Entire system SAVSYS,SAVLIB *IBM,SAV *SYSGRP
SAVSECDTA,SAVCFG, SAVLIB *BKUGRP

22. System data only *ALLUSR,SAVDLO,SAV
23. All user data SAVDLO *ALL *ALLDLO

SAVDLO *CHG SAVDLOBRM with SAVACT
*YES
Save Document Library Objects SAVDLO SAVFLRLBRM, SAVDLOBRM
SAVDLOBRM
SAVBRM
30. All documents, folders, and mail SAVDLO *MAIL
SAVCAL
31. New and changed documents,
new folders, all mail
32. Documents and folders
33. Mail only

34. Calendars

GO SAVE and BRMS
Save Libraries
SAVLIB LIB(*NONSYS) *IBM, *ALLUSR
40. All libraries other
than SAVLIB *IBM *IBM
system library
SAVLIB *ALLUSR *ALLUSR
41. All IBM libraries SAVCHGOBJ *ALLUSR *ALLUSR SAVACT *YES
other
than system library
42. All user libraries
43. All changed
objects
in user libraries

BRMS Log - DSPLOGBRM

BRMS/400 reports and maintenance
 Maintenance should be run regularly after daily save
 It produces reports for recovery analysis ,backup activity and expired media
 The Start Maintenance for BRM (STRMNTBRM) command performs various

BRMS maintenance and clean-up functions.

STRMNTBRM
The STRMNTBRM command processes several other commands that can be run separately. These
include:
o RMVMEDIBRM - Remove media information from BRM
o MOVMEDBRM - Move media using BRM
o STREXPBRM - Expire media from BRM
o RMVLOGEBRM - Remove BRM log entries
o WRKMEDIBRM - Work with media information
o STRRCYBRM - Recovery analysis

STRMNTBRM
Note: The STRMNTBRM command should be run as an independent job. No

other BRMS functions should be active when the STRMNTBRM command
is processing.

Reports produced by STRMAINTBRM
o QP1AVER - Version Control

o QP1AEP - Media Expiration
o QP1AMM - Media Report by Expiration Date
o QP1AHS - Media Information
o QP1ALE - Save Strategy Exceptions
o QP1ARCY - Recovering Your Entire System
o QP1AASP - Display ASP Information
o QP1ARW - Recovery Activities
o QP1A2SL - Location Analysis
o QP1ASYN - Centralized Media Audit
o QP1A2RCY - Recovery Volume Summary

STRMNTBRM

STRMNTBRM

VFYMOVBRM
 Used to verify the media movement .
 Tapes should be verified after they have been actually moved to the other
location .
 Verification can be done by system with no intervention required by operator

– Change Move Policy parameter “ Verify Move “ to *NO reflect this.

MOVMEDBRM
 BRMS determines the location of media according to the move policy and
checks the location where it actually is.
 If the two are different, it issues a move request to move the media to the
correct location.

MOVMEDBRM
 MOVMEDBRM invokes the RMVTAPCTG command to eject the cartridges

from “Media Library “
 If we want VFYMOVBRM to issue the RMVTAPCTG command we have to
change the Q1APRM Data-area

BRMS/400 console monitor
 Allows full save to run unattended

 Allows to run the backup in batch mode as well.
 For backup to run through console .We must ensure that it is active on
Console System.

BRMS Console Monitor
 To start it login on Console using an id which is exempted from signoff during

SYSSAV.
 GO BRMS
 Option 2 Backup
 Option 4 Start Console Monitor
 This will put system in BRMS Console Mode.

STRBKUBRM

Syntax for STRBKUBRM
STRBKUBRM CTLGRP(SYSSAV50) SBMJOB(*CONSOLE)
STRBKUBRM CTLGRP (SYSSAV56) SBMJOB (*CONSOLE) STRSEQ

(100 NAVDFSUP)

Online domino Backup
 BRMS will automatically generate the control groups and media policies you
need to perform Lotus Server online backups
 BRMS also dynamically creates backup link lists so that those same Lotus
Server databases can be excluded from other backups.

Default Policy and Group
 QLTSSVR - Control group - Backs up all Lotus Servers on the system

 QLTSDOMnn - Control group - Backs up all databases for Lotus Domino
Server nn, where nn is 01-99
 QLTSSVR - Media policy - Media policy specifying the media class and
expiration to be used for Lotus Server backups

Default Lists
 Special Value : *LNKOMTONL

or QLTSEXCL
 User modifiable list : QLNKOMTONL
 Description : This link list excludes all Lotus Server databases from the
backup since they have already been saved by the online Lotus Server
backup.

Default Lists
 Special Value : *LNKOMTLTS

or QIFSXCLLTS
 List : QLNKOMTLTS
 Description : This link list excludes all Lotus Server data directories from the
backup.

Default Lists
 Special Value : *LTSOMTONL

or QLTSXCLONL
 List : QLTSOMTONL
 Description : This link list includes all Lotus Server data directories and
excludes the online backup Lotus Server databases.

Default Lists
 Special Value : *LINK

 List : QLNKOMT
 Description : In V5R3 with SI13463 applied, you can specify any directories
or links to be excluded from a *LINK backup by adding them to the
QLNKOMT user-modifiable list.

Entry Name or Special Values.
 If you enter either the special value or link list name in an entry of your
control group, BRMS will dynamically generate a list of objects to include or
exclude from your save

How it works.
 A full online backup of Lotus servers consists of two files:

– The database files
– Changes files which contain the updates to the databases while they were being backed up.
 An incremental online backup is a save of the transaction logs for the server.

How it works.
 In order to allow the collection of two backups into one entity, BRMS
and the Lotus Servers use a concept in BRMS called a package
(identified by the PKGID parameter on the SAVBRM command).
 Lotus Servers will backup the databases while they are active, and
upon completion will back up a secondary file and associate it with
the first by using the package concept in BRMS.

How it works.
 The secondary file contains all of the changes that occurred during the
backup, such as transaction logs or journal-type information.
 The control groups supplied by BRMS with a SAVDOMBRM *EXIT contain

empty pre and post *EXITs. These *EXITs are required for online Lotus
Server backups to occur correctly

How it works.
 If the first entry in a control group is an *EXIT, it is processed before

any subsystem or job queue processing is done during STRBKUBRM
pre-processing.
 If the last entry in a control group is an *EXIT, it is processed after any

subsystem or job queue processing is done during STRBKUBRM
post-processing.

Example
 QLTSSVR control group:
10 *EXIT
20 *EXIT SAVDOMBRM SERVER(DOM1) CTLGRP(QLTSSVR)
30 *EXIT

FEW important Commands
 CHKEXPBRM
 WRKCFGSTS *DEV DSP*
 WRKPCYBRM *MED *BKU *SYS
 WRKMLBBRM
 WRKMLMBRM
 WRKMLBSTS
 DSPTAPSTS

Thanks for your Attention
Questions ?

Thank You
RISHI RAJ SINGH K.R.

risingh7@in.ibm.com

BRMS Backup

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

BRMS Backup

Transféré par

Droits d'auteur :

Formats disponibles

Business Unit or Product Name

iSeries - Backups Using BRMS

RISHI RAJ SINGH K.R.

1 Presentation Title | Presentation Subtitle | Confidential © 2007 IBM Corporation

2 Presentation Title | Presentation Subtitle | Confidential © 2007 IBM Corporation

 After the session you would be able to

3 Presentation Title | Presentation Subtitle | Confidential © 2007 IBM Corporation

4 Presentation Title | Presentation Subtitle | Confidential © 2007 IBM Corporation

5 Presentation Title | Presentation Subtitle | Confidential © 2007 IBM Corporation

Sun Mon Tue Wed Thu

Object A A+a A+a+b A+a+b+c A+a+b+c+d

Full A A+a A+a+b A+a+b+c A+a+b+c+d

Cum a a+b a+b+c a+b+c+d

Tape AS01 AS02 AS03 AS04 AS05

Cumulative AS01 AS01,AS02 AS01,AS03 AS01,AS04 AS01,AS05

6 Presentation Title | Presentation Subtitle | Confidential © 2007 IBM Corporation

Implementing Backups Strategies

 Backup on another Server – Any change on the primary server is copied on

7 Presentation Title | Presentation Subtitle | Confidential © 2007 IBM Corporation

8 Presentation Title | Presentation Subtitle | Confidential © 2007 IBM Corporation

9 Presentation Title | Presentation Subtitle | Confidential © 2007 IBM Corporation

BRMS Standard Product

The standard product provides capability to implement

10 Presentation Title | Presentation Subtitle | Confidential © 2007 IBM Corporation

BRMS Advanced Functions Feature

 The BRMS Advanced Functions feature provides hierarchical storage

11 Presentation Title | Presentation Subtitle | Confidential © 2007 IBM Corporation

 Assists in establishing a disciplined approach to design and manage backup

 Helps to define, process, monitor and report backup activities.

 Used to back up all of the data on iSeries system including objects in

12 Presentation Title | Presentation Subtitle | Confidential © 2007 IBM Corporation

 Provides for the orderly retrieval of lost or damaged data

 Recovery reports helps to recover the system sequentially .Reports contains

13 Presentation Title | Presentation Subtitle | Confidential © 2007 IBM Corporation

 Records and updates changes to the media inventory.

14 Presentation Title | Presentation Subtitle | Confidential © 2007 IBM Corporation

 Policies define how BRMS operations are generally to be done

15 Presentation Title | Presentation Subtitle | Confidential © 2007 IBM Corporation

16 Presentation Title | Presentation Subtitle | Confidential © 2007 IBM Corporation

 The standard BRMS package provides the following policies

17 Presentation Title | Presentation Subtitle | Confidential © 2007 IBM Corporation

– The Backup Policy :-

18 Presentation Title | Presentation Subtitle | Confidential © 2007 IBM Corporation

– The Recovery Policy

–Defines how recovery operations are generally to be

19 Presentation Title | Presentation Subtitle | Confidential © 2007 IBM Corporation

– The Media Policy

20 Presentation Title | Presentation Subtitle | Confidential © 2007 IBM Corporation

– The Move Policy

– determines the movement of media from creation through

21 Presentation Title | Presentation Subtitle | Confidential © 2007 IBM Corporation

BRMS Control Groups

 Consist of groups of libraries, objects, folders, spooled files, and

 Policies determine how data is processed, control groups determine,

 Specify kinds of backup to perform, such as full, incremental, or

22 Presentation Title | Presentation Subtitle | Confidential © 2007 IBM Corporation

BRMS Control Groups

 You can set control group attributes to override policy decisions.

 Though you cannot create control groups specifically for a recovery

23 Presentation Title | Presentation Subtitle | Confidential © 2007 IBM Corporation

How Policies and Control Groups Work

24 Presentation Title | Presentation Subtitle | Confidential © 2007 IBM Corporation

25 Presentation Title | Presentation Subtitle | Confidential © 2007 IBM Corporation

 The system policy is global and encompasses the function policies