BRMS Overview – What Does It Do and
How Do You Implement It?
Agenda Key: 36RH
Session Number: 580793
Follow us @IBMpowersystems
Learn more at www.ibm.com/power
© 2013 IBM Corporation
© 2013 IBM Corporation
About the Speaker
Debbie Saugen is the Technical Owner of IBM i Backup and Recovery in the
Rochester, MN Development Lab. She is also a Senior Business Recovery
Architect/Consultant with IBM Business Continuity and Resiliency Services.
Debbie ensures the Backup and Recovery Solution meets the customer's
requirements in capability and usability. She does actual Backup/Recovery
testing using the new functions, products and publications.
As a recognized expert on Backup and Recovery worldwide, Debbie enjoys
sharing her knowledge by speaking at Common, Technical Conferences,
Business Continuity and Resiliency Services Conferences, User Group
conferences and writing for various magazines, books and websites.
You can reach Debbie at [email protected].
Agenda
What is BRMS and What does it do?
Are you ready for recovery?
What will BRMS do for my Business?
Installing BRMS and Implementing BRMS
Main BRMS functions
How do I Install BRMS?
What are the various BRMS Entities?
What order should I create the BRMS Entities?
What BRMS reports should I review each day?
What Resources are Available to help me?
6.1 Enhancements
7.1 Enhancements
Faster IFS Saves (New PTFs)
7.1 BRMS Enterprise Function (New PTFS)
More Post 7.1 BRMS Enhancements (Latest BRMS PTFs)
Notes Agenda
Suppose your management has just heard about BRMS, and knows it will somehow help
your firm to manage your backups. They have asked you to learn more about the product
and provide a draft implementation plan for their review. If so, then this presentation is for
you! We will cover the following topics:
What is BRMS and What does it do?
First, we will set the stage, and remind you of the pressures and challenges you face when a
system recovery is required. Then we will step through the various functions of BRMS.
How do I get started using BRMS?
we will provide some guidance for you as you plan your BRMS implementation,
LNext,
including the following topics:
• What are the SW installation steps?
• What are the various BRMS entities that I need to set up?
• What order should I set up all the BRMS entities?
• What BRMS reports should I print and check each day?
• What resources are available to help me?
Are You Ready for Recovery?
NOTES: ARE YOU READY FOR RECOVERY?
Imagine yourself just waking up one morning and getting ready to walk the dog. Your telephone rings,
and your IBM i operator is on the line to tell you that you had a disk problem overnight, and the system
needs to be reloaded. What are the questions that you need to be able to answer?
•
When was our last backup? Did it run successfully?
•
What tapes do we need to get?
•
Where are they? How do we recall them?
•
What do we do with them once we get them?
•
Who should I call?
•
.......
Now imagine a worse scenario still .... suppose there was a natural disaster overnight. Suppose you and
your DP staff all need to be with your families, and are not available to manage your computer
operations? What additional questions do you need to ask?
•
Do we have a DRP Plan in place?
•
Who outside our firm can manage the process of getting us back into business?
•
.....
BRMS will ensure you can always answer these questions with confidence.
What will BRMS do for my Business?
IBM
Enhanced Capacity
Cartridge
System
TapeTape
Cartridge
System
IBM
IBM
IBM
IBM
IBM
Enhanced Capacity
Cartridge
System
TapeTape
Cartridge
System
Enhanced Capacity
Cartridge
System
Tape Tape
Cartridge
System
Enhanced Capacity
Cartridge System Tape
Cartridge System Tape
Enhanced Capacity
Cartridge
System
TapeTape
Cartridge
System
Enhanced Capacity
Cartridge
System
Tape Tape
Cartridge
System
IBM
IBM
Enhanced Capacity
Cartridge
System
TapeTape
Cartridge
System
Enhanced Capacity
Cartridge
System
TapeTape
Cartridge
System
IBM
Enhanced Capacity
Cartridge
System
Tape Tape
Cartridge
System
Backup Recovery and Media Services (BRMS)
• IBM i’s Strategic Backup and Tape Management Product (5722-BR1, 5761BR1)
• Manages Your Media
• Automates Your Backups
• Simplifies Your Recoveries
• Provides Detailed Reporting
– Detailed Reports on What Was Saved, Not Saved
– Detailed Instructions on Recovery Process
• Tape Library Support
• Virtual Tape Support (New for V5R4)
• Software Tape Encryption (New for 6.1)
Notes - What will BRMS do for my Business?
BRMS is IBM i's Strategic Backup Management Product. It helps you to manage your save/restore operations and makes
you confident that you could restore your system if necessary. The BRMS functions fall into 5 key areas, as follow:
Manage your Media:
tracks the contents of your tapes as they are written
prevents overwriting active tapes
provides move reports showing which tapes should move to different locations each day
provides lists of tapes that should be in each location at any given time, etc
Automate your Backups:
sets up your backups in a standardized format that others can understand easily
supports save-while-active, object-level saves, spooled file saves that maintain print attributes, saves to TSM, etc
provides detailed reporting on activity and errors etc
Simplify your Recoveries:
shows you all the saves of a certain set of objects so you can choose which generation you want to restore
provides interactive restores of those objects, complete with operator mount messages as appropriate
simplifies full-system recoveries by providing reports showing ASP configuration, tapes required for recovery, and
detailed steps for recovery. Automates those steps once the BRMS product is back on the system.
provides an on-line progress report during a recovery
Hierarchical Storage Management (HSM):
migrates objects among disk ASPs based on age, size, and usage criteria
archives objects to tape based on age and usage criteria
dynamically recalls *file objects, folders, and stream files when accessed by a user or application, and performs
interactive recalls of other object types
Tape library Support:
interfaces with automated tape libraries to select and mount/demount/eject volumes
*BASE Function
Backup Planning
Critical
Application
Non-Critical
Application
Lib1
Lib2
Lib3
Lib4
What Objects should be backed up?
ƒWhat media? Tape, savefile, or TSM?
ƒFull, Incremental, or Cumulative
Backups?
ƒSave-while-active, Parallel saves
ƒSpoolfile and Object Level saves
ƒDuplicate Backup Tapes
ƒDid last night's backup run OK?
ƒVirtual Tape Support
Option #1: Network
Media Management
Network
What is on Tape XYZ?
ƒWhat tapes should be in location DEF?
ƒWhat tapes are old or have a lot of errors?
ƒWhat tapes should move offsite today?
ƒWhat tape has the latest copy of Object ABC?
ƒ
BRMS
Media
Database
iSeriesA
BRMS
Media
Database
ƒ
BRMS
Media
Database
iSeriesB
iSeriesC
Recovery
Recovery Volume Summary Report
Vol123 Offsite
3/01/99
Vol456 Comproom 3/01/99
Vol789 MLD01
3/01/99
Recovery Analysis Report
Step 5: Recover your BRMS
database by mounting VOL123 and
typing RSTLIB QUSRBRM.
Step 6: Recover your user profiles by
mounting VOL456 and typing
STRRCYBRM *SYSTEM
*RESTORE.
Step 7: Recover your special OS/400
libraries by mounting VOL789 and
typing STR ...
Libs Completed: 6
Libs to go: 114
% Complete: 3%
Paylib1
Paylib2
Paylib3
Vol123
Vol 456
Vol 789
Option #2: Advanced
List of Tapes required
ƒ List of Steps to Recover
ƒ On-Line Progress Report
ƒ Location-specific Recovery Steps
New in
6.1
ƒ
Tape Library Support
3494
LTO
Hierarchical Storage
Management
3590/2 3570/3575
Migrate libraries, root folders, and
spoolfiles among disk ASPs based on
age, size, and last use criteria
ƒArchive objects to tape based on age,
size, frequency of use, and ASP
storage criteria
ƒDynamically recall database files,
DLO's and streamfiles when needed
ƒ
BRMS GUI
- Software Data
Encryption
- Media Library Mgmt
- User Defined System
Name
- Tape Library Status
Tool
Notes - Media Management
BRMS has a database that keeps track of all the tapes in its inventory. This database allows BRMS to
help you manage your media as follows:
Media Selection and Protection:
When you request a save, BRMS selects an available tape. If you are using a media library, BRMS will
mount the tape automatically. If you are using a standalone drive, BRMS will issue a mount message to
your operator showing 10 possible volumes for mount. The operator can mount one of these volumes, or
any other valid tape. If the operator accidentally mounts an invalid tape, such as a tape with active data,
BRMS will refuse to continue until a suitable tape is provided.
Media Tracking
While BRMS is writing the save, it records all the saved items in the BRMS database. By default, BRMS
tracks items at the library level, but you can request object-level-detail and/or member-level-detail on
certain saves if desired.
Move Management
When each tape is written, a move policy is associated with the tape, to provide a "travel Itinerary" for the
tape to move among locations such as offsite storage. When required, typically each morning, BRMS
provides a "Move Report" telling which tapes should move locations that day. The BRMS database logs
the current location of each tape at all times.
Reporting
Standard reports and other queries can be run against the BRMS database to provide such info as
follows:
Scratch listing to ensure enough tapes are available for the next evening's backups
List of all tapes at a given location, which can be used to check that the tapes are where they should be
Error Threshold listing showing tapes that should be taken out of circulation due to age or errors
Notes – Backup Planning
Backup Control Groups
When you set up BRMS for backup, you create "Control Groups" that describe your backup fully and typically replace your
backup CL programs. They include a list of the items to backup, save-while-active controls if desired, a list of subsystems to
end/restart, a list of JOBQs to hold/rls, the parameters for the underlying save command (eg access paths, compression, etc),
and optionally, any number of CL commands interspersed throughout the backup using the BRMS *EXIT function.
Since BRMS backups are in a standard format, any BRMS-trained person can quickly understand your backup strategy,
which is helpful as your staff turns over, and more importantly, in an emergency situation where your own staff may not be
available to tend to your system.
Small and medium-sized shops typically only need a handful of control groups, eg one for their weekend full saves, and one
for their daily pre-application backup. Larger shops may choose a more granular approach. For example, they may use a
separate control group to backup each application, thus allowing them to recover their most critical application first in a
disaster scenario.
Special Features
BRMS allows spooled files to be backed up in such a way that their attributes such as overlays, graphics, images, special
fonts, etc will be retained. The user merely makes a list of spooled files to be backed up, based on their OUTQ, job name, file
name, user name, and/or user data parameters. Contrast this with the OS400 method of backing up spooled files whereby
they must be copied to database files prior to saving, and the attributes are NOT retained.
Beginning at V4R4, BRMS is able to run parallel saves whereby a single job can use multiple tape drives simultaneously to
backup a library or group of objects from within a library. This function will be helpful for customers who have very large
objects that can now be split across multiple tapes simultaneously. This function is only available in OS/400 via an API
interface. It was enhanced in V5R1 to allow library spreading of multiple libraries across multiple tape drives under one
backup job.
Reporting
BRMS provides detailed reporting while backups are running. This includes the BRMS log that gathers all the save/restore
messages in one place, and the Media Information Report that summarizes all libraries saved.
Notes – Recovery
Using the information logged in the BRMS database, BRMS is able to simplify recoveries as follows:
Recovering Objects Interactively
Suppose a user calls to say he believes he corrupted his data libraries over the weekend. You can use
BRMS to list all the available saves of those libraries, and find out which copy he wants to restore. BRMS will
then mount the required tape, and restore the objects, all the while displaying an online progress screen
indicating the next 10 libraries to be restored, along with the number of objects remaining and their size.
Performing a Full Restore
Each morning when the saves are completed, BRMS generates a series of recovery reports, that provide
custom-tailored instructions for recovering the entire system. Duplicate copies should be kept in a safe place
both onsite and offsite. The reports are as follow:
The ASP Configuration Report shows the ASP sizes and %full so new disk can be configured at a hot site
if required
The Recovery Volume Summary Report shows all the tape volumes that are required for a full system
recovery, and where to find them
The Recovery Analysis Report provides customized, step-by-step instructions, including volume serials
and object names, to recover your system
The Recovery Activities Report documents any special in-house procedures that may be required as part
of the recovery process
Notes - HSM
The BRMS Backup and Recovery functions help you to ensure you can recover your system in case of a problem. By
comparison, HSM helps you to ensure you are using your storage space in an economical fashion by letting you move
less-frequently used objects to less-costly media. This is done using "migration" to move objects among disk ASPs, and
"archive/auto-recall" to move objects between disk and tape. Migration is available from V4R3 onwards, whereas
archive/auto-recall is available on all supported releases, with auto-recall of streamfiles and folders being added at V4R3.
Selection criteria for HSM is as follows:
Migration of Libraries and Folders
Full libraries and root level folders can be selected for migration based on the following criteria: size, creation date, age,
last-used-date, last-changed-date, last-migration-date, days-since last use/change/migration. Selection can demand that
ALL objects in the library or folder meet the criteria, or that a certain percentage of the objects meet the criteria. Note
that at the present time, the entire library or folder must migrate between ASPs when selected for migration: it is not
possible to have some of the objects in one ASP, and the rest of the objects in another ASP.
Migration of Spooled files
Spooled files are migrated from an output Q in one ASP to an output Q in another ASP. Selection criteria include: output
Q name, job name, file name, user name, user data, creation date, last used date, and min-max size range.
Archive/Auto-recall
Objects can be selected for archive based on the following criteria: days since last use (all releases), minimum
object size (V4R3), minimum ASP % full (V4R3), average number of days used per month (V4R4).
Spooled files have additional selection criteria of job name, file name, user name, and user data. Any
archived object can be restored to the system using the BRMS interactive menus. Certain objects
can be auto-recalled to the system when accessed by a user or application. These object types are
as follow: *FILE objects (all supported releases), folders (V4R3) and bytestream files (V4R3).
Tape Library Support
BRMS will ....
Select Scratch Tapes
Mount/Demount from drives
Eject Tapes from Library after the save
Notes - Tape Library Support
Companies who have tape libraries need software to manage the library by doing the
following:
selecting appropriate media for the save
submitting mount and demount commands to load the tapes in and out of the drives
submitting insert and eject commands to move the tapes in and out of the library
enclosure for offsite rotation
BRMS provides this support.
Media Management
Work with Media
Position to . . . . . . . . . . . . . . . ________
Type options, press Enter.
1=Add 2=Change
7=Expire 8=Move
Opt
___
___
___
___
___
___
___
___
Volume
Serial
________
R00002
R00067
Q00001
Q00002
Q00003+
Q00004+
Q00005+
4=Remove
5=Display
10=Reinitialize
Expired
*YES
*YES
*YES
Starting characters
6=Work with media set
13=Display Contents 15=Display Duplicates ...
Creation
Date
Expiration
Date
Location
Move Media
Date
Class
1/13/99
1/23/99
1/15/99
1/29/99
2/12/99
2/12/99
3/07/99
*PERM
2/20/99
2/12/99
2/29/99
3/12/99
3/12/99
4/07/99
COMPRM
COMPRM
TAPMLB01
TAPMLB01
OFFSITE
OFFSITE
COMPRM
*NONE
*NONE
2/12/99
2/29/99
2/12/99
2/12/99
3/01/99
___________________________________________________________________
F3=Exit
F5=Refresh
F11=Volume statistics
F12=Cancel
FMT7GB
FMT7GB
FMT3590
FMT3590
FMT3590
FMT3590
FMT3590
More. . .
F23=More options
Dup
Sts
*
*
1
Notes - Media Management
The BRMS tape database can be viewed using the menus or the WRKMEDBRM command.
The entire database can be viewed, or the command can be prompted to subset the tapes
displayed. The resulting screen has 3-4 views depending on the version. The first view is
shown on the attached chart. Subsequent views show information such as error threshold
information, parallel save information (V4R4) and the text associated with the tape, such as
"Weekend Full Save", or "Daily Pre-Application Backup".
The tape contents can be viewed by drilling down on each tape with option 13=contents. If
object-level-detail or member-level-detail was recorded, additional levels of drill-down are
also possible.
Volumes that are members of a tape set are marked with a '+' sign just to the right of the
volume serial. Drill down with 6="Work with Media Set" to see the other tapes in the set.
Volumes that have been marked for duplication have a '1' in the right-hand column under
"Dup Sts". After they are duplicated, they are marked with a '*' in this column. Drill down
with 15="Display Duplicates" to see the twin tape.
Media Report
by Expiration Date
"Scratch Listing"
Media Management
Media Expiration Report
Volume
Serial
HIJ616
J001
J002
J003
M00901
M00902
M00903
Expired
Media
Class
Yes
Yes
Yes
Yes
Yes
Yes
Yes
FMT3590
QIC120
QIC120
QIC120
FMT7GB
FMT7GB
FMT7GB
Total active . . . . . . . . . : 20
Total expired . . . . . . . . : 7
Total volumes . . . . . . . . : 27
Creation
Date
1/12/99
1/17/99
1/20/99
1/27/99
8/12/98
1/11/99
1/12/99
Expiration
Date
Storage
Location
System
ID
2/17/99
2/17/99
2/20/99
2/27/99
9/15/98
2/11/99
2/12/99
MLB3494
CMPROOM
CMPROOM
CMPROOM
CMPROOM
CMPROOM
CMPROOM
ABC400V
PID400J
PID400J
PID400J
ABC400V
ABC400V
ABC400V
Notes - Media Management
The Media Report by Expiration Date provides a scratch tape
listing. For standalone drive environments, it can be used as a
picking list to choose tapes for the next night's backups. In an
automated tape library environment, it can be used to confirm there
are sufficient scratch tapes available in the library. In a complex
environment with many systems and media classes, customers
may choose to customize the parameters on this report to group
the tapes by type so a detailed check of available tapes is possible.
Media Management
Media Movement Report All Volumes
From Location . . : CMPROOM
To Location . . : OFFSITE
Volume
Serial
Creation
Date
Expiry
Date
SAM420
SAM421
SAM422
SAM423
3/1/99
3/1/99
3/1/99
3/1/99
3/28/99
3/28/99
3/28/99
3/28/99
Total Volumes .......: 4
Move
Policy
OFFSITE
OFFSITE
OFFSITE
OFFSITE
Move
Date
3/1/99
3/1/99
3/1/99
3/1/99
Notes - Media Management
The Media Movement Report shows all the tapes that are to move
between locations each day. A standard consolidated report is
generated by the MOVMEDBRM command or the STRMNTBRM
MOVE(*YES) command. However, many customers prefer the report
shown, which is generated with the PRTMOVBRM command, because
it generates a separate page for each pair of locations.
By setting various date parameters, you can create a move list for a
future date. Systems with FAX installed can then fax the list to the
offsite storage vendor each day, thus giving him a picking list for the
returned tapes.
Media Management
Media Threshold Information
Media class . . . . . . . . . . : FMT2GB
Volume
Serial
ABC001
ABC032
ABC138
ABC151
Creation
Date
2/1/99
3/1/99
1/6/99
3/2/99
Expiry
Date
Location
Read
Uses Errors
2/28/99
3/29/99
2/03/99
3/30/99
COMPRM
OFFSITE
COMPRM
OFFSITE
2461
1137
2359
2522
*2 = Media has exceeded use count
*3 = Read error threshold has been exceeded
*4 = Write error threshold has been exceeded.
3
9
5
2
Write
Errors
2
4
8
1
Exception
Detail
*2
*3
*2 *4
*2
Notes - Media Management
The Media Threshold Report shows tapes that should be
investigated, and possibly removed from the BRMS inventory
because they have exceeded the thresholds set for their media class,
eg QIC120, FMT3590, etc. For example, tapes should be retired
when they have been used more than a certain number of times, or
are receiving too many read or write errors.
Backup Planning
Work with Backup Control Group
Type options, press Enter
1=Create 2=Edit entries 3=Copy
4=Delete 5=Display
6=Add to schedule 8=Change attributes 9=Subsystems to process ...
Opt
Control
Group
Full
Media
Policy
Incr
Media
Policy
Weekly
Activity
SMTWTFS
2
*BKUGRP
*SYSGRP
*SYSTEM
TESTSAVE
*BKUPCY *BKUPCY *BKUPCY Entry created by BRM
SAVSYS SAVSYS *BKUPCY Entry created by BRM
*BKUPCY *BKUPCY *BKUPCY Entry created by BRM
WEEKEND DAILY
F i i i i i F Demo CTLG
Text
Notes - Backup Planning
BRMS Backup Control Groups describe the backup to be performed. BRMS is shipped with 3
default control groups as follow:
*BKUGRP which does the majority of your full save, excluding *SAVSYS, *IBM, and
spooled files.
*SYSGRP which does your *SAVSYS and *IBM
*SYSTEM full system backup, equivalent to Go Save 21
You can use these groups directly, or copy them into other groups to modify, or create your
own.
To describe a control group fully, you need to complete 4 types of screens as follow:
#2 = Edit Entries (i.e. describe the libraries/objects/etc to be backed up)
#8 = Attributes (i.e. specify the other BRMS entities related to the save, and set the
various parameters for your saves)
#9 = Subsystems to end/restart
#10 = JOBQs to hold/release
Backup Planning
Edit Backup Control Group Entries
Group . . . . . . . . . . : TESTSAVE
Default activity . . . . F i i i i i F
Text . . . . . . . . . . . . Demo Backup Control Group
Seq
10
20
30
40
50
60
Backup
Items
*EXIT
*SAVSECDTA
LIB*
PAYLIB
CUSTLIB
EMPLIB
Weekly
Activity
SMTWTFS
*DFTACT
*DFTACT
*DFTACT
FFFFFFF
*DFTACT
*DFTACT
Retain Save
Object While
Detail Active
*NO
*ERR
*NO
*MBR
*MBR
*NO
*LIB
*SYNCLIB
*SYNCLIB
Notes - Backup Planning
On the "Edit Entries" screen of the control group, you can list the items you want to
backup. Libraries, generic libraries, and special values such as *ALLUSR, *ALLDLO
etc can be listed directly on the lines provided. To backup other items, such as
objects, spooled files, folders, and IFS objects, you can create a BRMS list and put the
list name onto the blank lines in the control group. If you need to issue CL commands
or call programs during the backup, they may be included using *EXIT line items.
Beside each line item, indicate what kind of backup you would like on each day of the
week. Using the default system values, "F" will indicate a full save, "I" will indicate an
incremental save (eg SAVCHGOBJ), and a blank will indicate that the item should not
be backed up that day.
For each line item, you can specify whether you want BRMS to log library-level detail
only (*LIB - default at V4R2 and below), or object-level-detail (*OBJ), member-leveldetail (*MBR), or library level detail with object level detail ONLY if an object isn't saved
successfully (*ERR - default at V4R3 and above). You can also indicate what level of
save-while-active synchronization is required.
Parallel Saves and Restores
• Parallel Saves (V4R4 and higher)
– Save Large Library, Large Object or List of Large Objects to Multiple
Tape Devices in Parallel
• "Spreads Data across Tapes"
– Improves Save Performance for Very Large Objects
• Not Designed for Small Objects
– End User Interface with BRMS
– Same Number of Tape Devices on Save "Recommended" for Restore
Parallel Saves and Restores
• Expanded Parallel Support (V5R1 and higher)
– Special Values *ALLPROD, *ALLTEST, *ALLUSR, *IBM, *ASP01 *ASPxx and Generics Supported
– Objects "Spread" at Full Library Level
– Restore of Parallel Saves with Special Values in Serial Restore Mode
(One Tape Device)
• Media Library with Multiple Devices Provides Tape Mounting
Automation
– List of Libraries - BRMS Determines Best "Spreading" (Object or Full
Library Level)
Notes – Parallel Support
Parallel backup is the ability to backup individual objects or a library to different tape devices at the same
time, writing pieces of the library or object to multiple tape volumes. The goal is to utilize the full throughput
potential of the tape device; a single library that is backed up in parallel will have as its goal that all volumes
being used finish at the same time, as opposed to having the data split among the tape volumes equally.
Save/Restore will be implementing changes to allow large objects and libraries to be save to multiple devices,
parallel, at the same time. This is to minimize the backup window. This parallel concept will reduce the
amount of time it takes to save the objects.
Thee following commands have been enhanced to control parallel saves.
• Save Library using BRM (SAVLIBBRM)
• Save Object using BRM (SAVOBJBRM)
• Save Object List using BRM (SAVOBJLBRM)
• Restore Library using BRM (RSTLIBBRM)
• Restore Object using BRM (RSTOBJBRM)
• Work Control Groups using BRM (WRKCTLGBRM)
Today, when multiple devices are specified on an OS or BRMS command (i.e. DEV(TAP01 TAP02 TAP03)),
it means sequentially. It means use TAP01 and at end of volume, use TAP02, then TAP03, and then back
to TAP01, as it cycles around. Parallelism on the other hand needs to allow DEV(TAP01 TAP02 TAP03) to
save at the same time to all three devices, keeping in mind that each device may span volumes creating a
set of volume sets that are linked together.
Media library devices also offer an interesting concept to parallel saves. If a user has a 3494 with 4 tape
resources, it should be able to attempt to use 4 resources, but potentially use as many as are available when
the save is ready to start.
Notes – Save Types
To clarify the differences between the types of backup, the definitions are below:
SERIAL BACKUP (always)
The concept of using one tape device at a time to backup objects or libraries. The output volume may span to
more than one volume creating a volume set.
CONCURRENT BACKUP (V4R1)
The ability to backup different objects from the same library (or different libraries) using separate jobs
(commands) to different save/restore devices at the same time. The goal is to allow the user access to save
multiple large objects in the same library at the same time.
PARALLEL BACKUP (V4R4)
The ability to backup individual objects or a library to different tape devices at the same time, writing pieces of
the library or object to multiple tape volumes. The goal is to utilize the full throughput potential of the tape
device; a single library that is backed up in parallel will have as its goal that all volumes being used finish at
the same time, as opposed to having the data split among the tape volumes equally.
PARALLEL BACKUP (V5R1)
Library Spreading based on *ALLUSR, *ALLPROD, *ALLTEST, etc. where all libraries are divided among
available drives selected for the parallel save. If you list the individual library, it will do object spreading like
V4R4 and V4R5.
Backup Planning
Change Backup Control Group Attributes
Group . . . . . . . . . . . . . . . . :
Media policy for full backups . . . . .
Media policy for
incremental backups . . . . . . . .
Backup devices . . . . . . . . . . . . .
Parallel Drive Resources:
Minimum Resources . . . . . . . . .
Maximum Resources . . . . . . . .
Sign off interactive users . . . . . . .
Sign off limit . . . . . . . . . . . . .
Incremental type . . . . . . . . . . . .
Text . . . . . . . . . . . . . . . . . .
TESTSAVE
WEEKEND
F4 Prompt
DAILY
MLB3570
F4 Prompt
F4 Prompt
*NONE
*BKUPCY
*BKUPCY
*BKUPCY
Demo Backup
Notes - Backup Planning
On the Control Group Attributes screen, specify the various BRMS
entities that will be used for this save (eg media policy, tape device)
and set the various save parameters such as saving access paths,
saving the contents of savefiles, object pre-check, etc.
Note that from V4R4 onwards, new parameters are available to allow
parallel saves whereby a single save is sent to multiple tape drives
simultaneously.
Running the Backup
Start Backup using BRM (STRBKUBRM)
Type choices, press Enter.
Control group . .
Schedule time . .
Submit to batch .
Starting sequence:
Number . . . . .
Library . . . .
Append to media .
Job description .
Library . . . .
Job queue . . . .
Library . . . .
Activity . . . . .
Retention:
Retention type .
Retain media . .
. . . . . . .
. . . . . . .
. . . . . . .
Testsave
*IMMED
*YES
*BKUGRP, *SYSGRP, *SYSTEM...
hhmm, *IMMED
*CONSOLE, *YES, *NO
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
*FIRST
*FIRST
*CTLGRPATR
*USRPRF
*CTLGRPATR
1-9999, *FIRST
Name, *FIRST
*CTLGRPATR, *BKUPCY, *YES...
Name, *USRPRF
Name, *LIBL, *CURLIB
Name, *JOBD
Name, *LIBL, *CURLIB
*CTLGRPATR, *FULL, *INCR
. . . . . . .
. . . . . . .
*CTLGRPATR
35
*CTLGRPATR, *PERM, *DAYS
1-9999
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
*JOBD
NEW AT V5R1
Running the Backup
Start Backup using BRM (STRBKUBRM)
Type choices, press Enter.
Control group . . . . . . . . . TESTSAVE
Schedule time . . . . . . . . . . . *IMMED
Submit to batch . . . . . . . . . . *YES
Starting sequence:
Number . . . . . . . . . . . . . . *FIRST
Library . . . . . . . . . . . . .
*FIRST
Append to Media . . . . . .
*NO
*BKUGRP, *SYSGRP
hhmm, *IMMED
*CONSOLE, *YES, *NO
1-9999, *FIRST
Name, *FIRST
*YES, *CTLGRPATR, ...
Notes - Running the Backup
To run a BRMS Backup Control Group, use the STRBKUBRM
command. Notice that you have the option to restart a failed control
group, and to override the append parameter. Prior to V5R3, if the
backup includes a *SAVSYS, it needs to be submitted interactively
from the console, or the BRMS console-monitoring parameters need
to be set (i.e. do not choose "submit-to-batch" for a *SAVSYS).
Running the Backup
BRMS Log
Begin processing for control group DENNISTEST type *BKU.
Interactive users are allowed to stay active.
Starting save of library EXAMPLE to save file.
*FILE DSPPTF2 in EXAMPLE not saved.
11 objects were saved; 2 objects were not saved.
Starting save of library JEFFM to save file.
7 objects saved from library JEFFM.
Starting save of library JOHND to save file.
134 objects saved from library JOHND.
Starting save of BRM media information at level *LIB to device *SAVF.
11 objects saved from library QUSRBRM.
Save of BRM media information at level *LIB complete.
Control group DENNISTEST type *BKU completed with errors.
Notes - Running the Backup
When BRMS is running backups, it logs all messages in a central
location called the BRMS Log. This log can be searched and
subsetted by message id or message severity or type of operation
(eg backup, recovery, archive, retrieve, maintenance, etc), and
printed if desired. The BRMS Log makes it much easier to check the
status of the overnight backup streams, compared with locating and
checking the joblogs for all backup jobs if you did not have BRMS.
However the actual backup job joblog can still be used if desired.
Online Object Selection Screen from WRKMEDIBRM
Work with Media Information
ITCBRMS1
Position to Date . . . . .
Type options, press Enter.
2=Change
4=Remove
5=Display
9=Work with saved objects
Saved
Opt Item
QUSRRDARS
QUSRSYS
TEAM01AU
TEAM1USR
7 TEAM3USR
TONIB
T04USR2
USRPROD01
USRPROD01A
USRPROD02
Date
5/01/02
5/01/02
5/01/02
5/01/02
5/01/02
5/01/02
5/01/02
5/01/02
5/01/02
5/01/02
Time
16:41:57
16:41:57
16:41:57
16:41:57
16:41:57
16:41:57
16:41:57
16:41:57
16:41:57
16:41:57
6=Work with media
Save
Type
*FULL
*FULL
*FULL
*FULL
*FULL
*FULL
*FULL
*FULL
*FULL
*FULL
Volume
Serial
103673
103673
103673
103673
103673
103673
103673
103673
103673
103673
7=Restore
File
Sequence
66
67
68
69
70
71
72
73
74
75
Expiration
Date
6/05/02
6/05/02
6/05/02
6/05/02
6/05/02
6/05/02
6/05/02
6/05/02
6/05/02
6/05/02
More...
Notes - Media Information Report
The Media Information Report shows all the items backed up since
midnight the day before yesterday. BRMS users can scan the "not
saved" column and investigate any objects that were missed ... they
may decide that *MSGQs don't need to be re-saved, whereas morecritical objects such as QUSRSYS objects may need to be saved
immediately to ensure recovery will be possible. Also you can do a
restore directly from the display.
Recovery
Work with Media Information
2=Change 4=Remove 5=Display 6=Work with media
Item
Saved
Date
Save
Time
LIB1
LIB999
LIBXYZ
QUSRSYS
QUSRBRM
2/01/99
2/15/99
2/15/99
1/30/99
1/30/99
22:13
08:00
08:23
15:40
15:48
Opt
7
7
7
F3=Exit
F5=Refresh F12=Cancel
RCHAS400
7=Restore 9=Work with saved objects
Type
Volume
Serial
File
Seq
Exp
Date
*FULL
*FULL
*FULL
*FULL
*QBRM
VOLA
VOL3
VOL3
WW04
WW04
1
1
2
1
2
3/15/99
3/30/99
3/30/99
4/11/99
4/11/99
Notes - Recovery
To recover objects, simply locate them in the BRMS database using
the various BRMS commands and menus, then choose option #7 to
restore. If you are in a standalone environment, BRMS will issue
mount messages to your operator. If you have an automated tape
library and the tape is inside, BRMS will automatically mount it and
restore the data.
If you kept object-level-detail and you want to restore individual
objects from within a library, you can drill down and select those
objects for restore. Otherwise, BRMS will present a RSTOBJ screen
where you can key the names of the specific objects you need.
Recovery
Display Recovery Items
Remaining items . . . . :
Remaining objects. . . :
Remaining size . . . . . :
Item
Saved Save
Date
Time
LIB1
LIB999
LIBXYZ
2/01/99 22:13:26
2/15/99 08:00:01
2/15/99 08:23:00
Press ATTN to cancel recovery.
RCHAS400
3
126
349 M 96.8%
Type
Vol
Serial
File
Seq
Expiration
Date
Objects
Saved
*FULL
*FULL
*FULL
VOLA
VOL3
VOL3
1
1
2
3/15/99
3/15/99
3/30/99
38
29
59
Notes - Recovery
While BRMS does the restore, you will see an on-line-progress report
with details about the number of items restored to date, and the
number of objects still to go. This screen is very helpful during a large
recovery to estimate how much longer the restore will take, particularly
when compared to the input-inhibited sign seen during an OS/400
RSTLIB command.
Recovery
Recovery Volume Summary Report
Volume
Serial
ABC071
ABC951
HIJ787
MNO843
NOP042
VOL006
Expired
Media
Class
Creation
Date
Expiry
Date
FMT3590
FMT3590
FMT3590
FMT3590
FMT3590
FMT3590
2/16/99
2/18/99
2/28/99
3/05/99
3/06/99
3/07/99
3/16/99
*ver 002
3/28/99
4/05/99
4/06/99
*ver 002
Location
Date
3/02/99
3/04/99
2/28/99
3/05/99
*pending
*pending
Storage
Location
MLB3494
MLB3494
BLDGXYZ
BLDGXYZ
OFFSITE
OFFSITE
System
ID
PID400V
PID400V
PID400V
PID400V
PID400V
PID400V
Total volumes needed for Recovery ............: 6
*
This report lists all the tapes you would need for a specific recovery
Notes - Recovery
The Recovery Volume Summary Report shows all the tapes that would be needed in
order to do a full system restore. A typical report would include the most recent
*SAVSYS, the full save from the previous weekend, the incremental saves from each
weeknight prior to the failure, any adhoc saves performed, and the most recent copy of
the BRMS database.
Two copies of this report should be stored, one locally, and one offsite, so a copy will
always be available should a restore be necessary. Shops that have a network of
systems in different buildings, will sometimes send the recovery reports to a system in
another building, so they will be available even after a site loss.
Recovering Your System
STEP: Recover Licensed Internal Code
Start time ______
Stop time ______
Use media as shown below and the procedure for "Recovering the
Licensed Internal Code" in the "Backup and Recovery" book.
__ Use "Option 2" if you are recovering to a different system or if
you are recovering to a system with user ASP(s) or if you are
recovering to the same system with a different release.
c
__ Use "Option 3" if you are recovering to the same release and same
system or you are recovering a logical partition to another logical
partition.
Saved
Save
Save
Sequence Control
Volume
Item
Type ASP Date
Time
Objects Omit Number
Group
Identifier
---------- ----- --- -------- ------- ------- ----- --------- ---------- ---------5722BR1 V5R1M0 010523
Recovering Your Entire System
ITCBRMS2
*SAVSYS
*FULL 01 3/25/02 11:00:49
0
1 *SYSTEM
AA111
STEP: Recover operating system
Start time ______
Stop time ______
Use the media shown below and the procedure for "Restoring the Operating
System using the Complete Restore Method", as detailed in the "Backup
and Recovery" book.
Saved
Save
Save
Sequence Control
Volume
Item
Type ASP Date
Time
Objects Omit Number
Group
Identifier
---------- ----- --- -------- ------- ------- ----- --------- ---------- ---------*SAVSYS
*FULL 01 3/25/02 11:00:49
0
1 *SYSTEM
AA111
STEP: Recover the BRMS/400 product and associated libraries
Start time _____
Stop time ____
The BRMS/400 product and associated libraries must be recovered
before you can use the product to perform other recovery operations.
To prevent messages that are not related to the recovery from
interrupting the recovery process, run the following command:
CHGMSGQ MSGQ(QSYSOPR) DLVRY(*NOTIFY) SEV(99)
Use the following command to see which tape devices are configured:
WRKCFGSTS CFGTYPE(*DEV) CFGD(*TAP)
ETC.......
Notes
The Recovery Analysis Report shows the steps to follow and the tape volumes to use, in order to do a full system recovery. Notice
that the early steps say which tapes to use, then refer to the checklists in the Backup and Recovery Guide, since BRMS is not yet
loaded onto the system to guide the recovery. Part way through the recovery, once BRMS is loaded, the report will instruct you to
use BRMS commands to automate the rest of the process.
At V5R1, several enhancements were made to the report. They are:
Attention Boxes
QUSRBRM
Not saved last
User Profiles
TSM Server
SAVSYS
Configuration Data
IBM Products
Document Library
Start/Stop time areas for user
New steps
All commands to issue stand alone now
Special recovery steps
Helpful for starting some LPPs with special needs
Notes - continued
At V5R2, more enhancements have been made. They are:
New steps
Setting up standalone or media library devices for recovery
Initialize BRMS functional authority information
Update system name in BRMS media information
Configure ASP devices
Verify ASP device names
Recovering Linux servers in a logical partition
At V5R3, more enhancements have been made. They are:
Step numbers included
Total number of objects not saved
Objects not saved column per item
New steps
Recovering AIX servers in a logical partition
Notes - Recovery
The Recovery Analysis Report shows the steps to follow and the tape
volumes to use, in order to do a full system recovery. Notice that the
early steps say which tapes to use, then refer to the checklists in the
Backup and Recovery Guide, since BRMS is not yet loaded onto the
system to guide the recovery. Part way through the recovery, once
BRMS is loaded, the report will instruct you to use BRMS commands to
automate the rest of the process.
BRMS Navigator Interface
• V5R1 Initial Implementation - Navigator Plug-In
– Created Separately
– Looks and Behaves like Navigator GUI
• Simplifies Setup and Management of Backup/Recovery Strategy
• Easy to Use Wizards
–
–
–
–
–
Create a Backup Policy
Add Tape Media to BRMS
Prepare Tapes for Use
Add Items to Backup Policy
Restore Backed Up Items
BRMS Enhancements for 6.1
•
•
•
•
•
•
•
•
•
•
•
•
•
•
BRMS Client Navigator Enhancements
– Web Browser Support via Systems Director Navigator
– Media Policies Externalized
– DVD/Optical Support
BRMS Software Encryption
Multiple Save Synchronization for Save While Active
Missed Object Control Group Support for IFS
Save/Restore Private Authorities with Objects
Parallel Save Type Selection
Save Generic Libraries
Omit *SYSDTA on SAVSYSBRM
Reference Date/Time on SAVOBJBRM
Save Journal Receivers Support
New Overrides on STRBKUBRM
Auditing and Performance Backup Report
Better IFS Messaging in BRMS Log
Flashcopy Support
BRMS Enhancements for 6.1
•
Media Management Enhancements
– Media Balancing
– Automatic Duplication
– Move Media Retention Capability
– Movement/Container Auto Open/Close
• Networking – Stop SNA Attempt if No TCP
• New BRMS Advanced Features (Option 2)
• Recovery Enhancements
– Restore Private Authorities Saved with Objects
– STRRCYBRM
• Priority Recovery Sequencing
• Location Omit
• Report Enhancements for Optical and Encryption
– Recovery for Logical/Physical Files
Web Browser Support (New for 6.1)
• Web Browser Support via Systems Director Navigator for i5/OS
• Almost Functionally and Visually Identical to System i Navigator
• System Director Navigator Missing:
– Scheduling Function
– For Backup, Maintenance, Printing Reports, etc.
– Included in Future Release
Externalize Media Policy (New for 6.1)
• Previously no Media Policy Selection with BRMS Client
• Resulted in Green Screen Media Policy Renamed to Zxxxxxxxxxxx
• No More Renames in 6.1!
DVD/Optical Support (New for 6.1)
• New Device Support
• DVD, Optical Libraries and Virtual Optical Devices
Software Encryption (New for 6.1)
• Encryption for Any Tape Device, Tape Library or
Virtual Tape
– AES Encryption
– Data Encrypted – Not Tape Labels
– Capability to Encrypt Each File Via Different Key
• Requires i5/OS option 44 (Encrypted Backup
Enablement)
– Requires Tape Management Application to
Enable Encryption
– Recommend BRMS
• BRMS Advanced Feature Required
– Not Compatible with Hardware Encrypting Tape
Devices
Software Encryption Considerations (New for 6.1)
Tape Backup Performance - Saves
G B /H R
9406-MMA-4w ay Encrypted ASP SAVLIBBRM NO Softw are Encryption
9406-MMA-4w ay Encrypted ASP SAVLIBBRM With Softw are Encryption
9406-MMA-4w ay NON Encrypted ASP SAVLIBBRM NO Softw are Encryption
9406-MMA-4w ay NON Encrypted ASP SAVLIBBRM With Softw are Encryption
9406-570-4w ay NON Encrypted ASP SAVLIBBRM NO Softw are Encryption
9406-570-4w ay NON Encrypted ASP SAVLIBBRM With Softw are Encryption
700
600
500
400
300
200
100
0
1 GB Source File
12 GB User Mix
64 GB Large File
320 GB Large File
Software Encryption Considerations (New for 6.1)
• Capacity
– Loss of Compaction May Result in More Tape Cartridges
• CANNOT Encrypt
– Operating system (*SAVSYS, *SAVSYSINF, *SAVSECDTA,
*SAVCFG)
– QBRM, QUSRBRM, QSYS2, QGPL and QUSRSYS
– BRMS Will Not Encrypt “Q” Libraries
• Standard Labeled Tapes Only
• Cannot Use with Tape Write Error Recovery Enabled
• If Key Store File Lost – Data is Unrecoverable
Multiple Save Synchronization (New for 6.1)
• Save While Active Saves
– Synchronize Libraries and/or IFS for Common Checkpoint
– Ensure Libraries and IFS Data Save in Consistent State
• MONSWABRM Command
• Sync ID Field in Backup Control Group
Multiple Save Synchronization (New for 6.1)
Edit Backup Control Group Entries
Group . . . . . . . . . . : MSTRSWA
Default activity . . . *BKUPCY
Text . . . . . . . . . . . Master SWA control group
Type information, press Enter.
Backup
Seq Items
10 *EXIT
20 *EXIT
30 *EXIT
40 *EXIT
50 *EXIT
Exit command
MONSWABRM LIB(ASN) CMD(STRSBSBRM) SYNCID(MULTSWAID)
NUMSYNC(2)
SBMJOB CMD(STRBKUBRM CTLGRP(SWA01))
SBMJOB CMD(STRBKUBRM CTLGRP(SWA02))
Multiple Save Synchronization (New for 6.1)
Edit Backup Control Group Entries
Group . . . . . . . . . . : CTLG01
Default activity . . . *BKUPCY
Text . . . . . . . . . . . 1st SWA control group
Type information, press Enter.
Backup List ASP
Seq Items
Type Device
10 *EXIT
20 LIB1
30 LIB2
40 LIB3
50 *EXIT
*SYSBAS
*SYSBAS
*SYSBAS
Weekly
Retain Save SWA
Activity
Object While Message
SMTWTFS Detail Active Queue
*DFTACT
*DFTACT
*DFTACT
*DFTACT
*DFTACT
*ERR *SYNCLIB
*ERR *SYNCLIB
*ERR *SYNCLIB
SWA
*LIB
*LIB
Sync
ID
MULTSWAID
MULTSWAID
MULTSWAID
Multiple Save Synchronization (New for 6.1)
Edit Backup Control Group Entries
Group . . . . . . . . . . : CTLG02
Default activity . . . . . *BKUPCY
Text . . . . . . . . . . . 2nd SWA control group
Type information, press Enter.
Backup
Seq Items
10 *EXIT
20 IFSLIST
30 *EXIT
List ASP
Type Device
Weekly
Retain Save SWA
Activity
Object While Message
SMTWTFS Detail Active Queue
*DFTACT
*LNK *SYSBAS *DFTACT *NO
*DFTACT
*SYNC
SWA
Sync
ID
MULTSWAID
Missed Object Control Group - IFS Support (New for 6.1)
Edit Backup Control Group Entries
Group . . . . . . . . . . : MISSINGCG
Default activity . . . *BKUPCY
Text . . . . . . . . . . . *NONE
Type information, press Enter.
Backup
Seq Items
List ASP
Type Device
Weekly
Retain Save SWA
Activity
Object While Message
SMTWTFS Detail Active Queue
10 *EXIT
*DFTACT
20 Z016416002 *LNK *ALLAVL FFFFFFF *YES
30 *EXIT
*DFTACT
*NO
Sync
ID
Save Private Authorities with Objects (New for 6.1)
Edit Backup Control Group Entries
Group . . . . . . . . . . : LIB001
Default activity . . . *BKUPCY
Text . . . . . . . . . . . Library Backup
Type information, press Enter.
Backup
Seq Items
10 *EXIT
20 LIB1
30 LIB2
40 LIB3
50 *EXIT
List Parallel
Type Type
*OBJ *DEFAULT
*DEFAULT
*DEFAULT
Private
Authorities Encrypt
*NO
*YES
*NO
*NO
*NO
*NO
Save Private Authorities SAVOBJBRM (New for 6.1)
Save Object using BRM (SAVOBJBRM)
Type choices, press Enter.
Save active wait time:
SAVACTWAIT
Object locks . . . . . . . . . . . . . .
Pending record changes . . . .
Other pending changes . . . . .
Save active message queue . . SAVACTMSGQ
Library . . . . . . . . . . . . . . . . . .
Control group . . . . . . . . . . . . . . CTLGRP
End of media option . . . . . . . . ENDOPT
Use optimum block size . . . . . . USEOPTBLK
Sequence number . . . . . . . . . . SEQNBR
Target release . . . . . . . . . . . . . TGTRLS
Clear . . . . . . . . . . . . . . . . . . . . CLEAR
Object pre-check . . . . . . . . . . . PRECHK
Save access paths . . . . . . . . . ACCPTH
Private authorities . . . . . . . . . . PVTAUT
Data compression . . . . . . . . . . DTACPR
120
*LOCKWAIT
*LOCKWAIT
*NONE
*LIBL
*NONE
*REWIND
*BKUPCY
*END
*CURRENT
*NONE
*NO
*SYSVAL
*NO
*DEV
Parallel Save Type Selection (New for 6.1)
• Select Type of Parallel Save
• Specific Entry in Control Group
• Values for Parallel Type
– *PARALLEL
• Uses Multiple Devices Creating Multiple Media Files
• BRMS Creates Media Definition Used in Recovery with BRMS Save
History
– *SERIAL
• Uses Multiple Devices with One Media File per Backup
• Media Definition not Required for Recovery
– *NONE
• No Parallel Save
– *DEFAULT
• BRMS Decides Best Parallel Type
• If Backup Item Does Not Support Parallel, Serial Save Performed
Parallel Save Selection on Control Group (New for 6.1)
Create Backup Control Group Entries
Group . . . . . . . . . . : PARALLEL
Default activity . . . *BKUPCY
Text . . . . . . . . . . . Parallel save options
Type information, press Enter.
Backup List Parallel
Seq Items Type Type
•
Private
Authorities Encrypt
10 LIB1
*PARALLEL *NO
*NO
20 LIB2
*SERIAL
*NO
*NO
30 LIB3
*DEFAULT
*NO
*NO
Save Generic Libraries (New for 6.1)
Add Object List
Use . . . . . . . . . : *BKU
List name . . . . . GENERICLIB
Text . . . . . . . . . Generic list of Libraries
Type choices, press Enter.
Seq
10
Library
PAYROLL*
Object
Type
Member
*ALL
*ALL
*ALL
Omit *SYSDTA on SAVSYSBRM (New for 6.1)
• New *SYSDTA Value on Omit Parameter of SAVSYSBRM Command
• Omits Licensed Internal Code and i5/OS
• Enables SAVSECDTA and SAVCFG in BRMS
– *CFG and *SECDTA Values Also Available on Omit
• Not Available in Navigator
Omit *SYSDTA SAVSYSBRM (New for 6.1)
Save System using BRM (SAVSYSBRM)
Type choices, press Enter.
Device . . . . . . . . . . . . . . . . . . DEV
Media policy . . . . . . . . . . . . . MEDPCY
Data compression . . . . . . . . . DTACPR
Data compaction . . . . . . . . . COMPACT
Control group . . . . . . . . . . . . CTLGRP
End of media option . . . . . . . ENDOPT
Use optimum block size . . . . USEOPTBLK
Omit . . . . . . . . . . . . . . . . . . . OMIT
Clear . . . . . . . . . . . . . . . . . . CLEAR
Start controlling subsystem . STRCTLSBS
Expiration date . . . . . . . . . . EXPDATE
Move policy . . . . . . . . . . . . MOVPCY
Media class . . . . . . . . . . . . MEDCLS
Location . . . . . . . . . . . . . . . LOC
*DEV
*DEV
*NONE
*REWIND
*BKUPCY
*SYSDTA
*NONE
*YES
*MEDPCY
*MEDPCY
*MEDPCY
*MEDPCY
REFDATE/REFTIME on SAVOBJBRM (New for 6.1)
Save Object using BRM (SAVOBJBRM)
Type choices, press Enter.
Data compaction . . . . . . . . . . COMPACT
Save contents of save files . . SAVFDTA
Spooled file data . . . . . . . . . . SPLFDTA
Type of save . . . . . . . . . . . . . . SAVTYPE
Reference date . . . . . . . . . . . . REFDATE
Reference time . . . . . . . . . . . . REFTIME
Journaled objects . . . . . . . . . OBJJRN
Objects to omit:
OMITOBJ
Object . . . . . . . . . . . . . . . . .
Library . . . . . . . . . . . . . . .
Object type . . . . . . . . . . . .
Auxiliary storage pool . . . . . . . ASPDEV
Expiration date . . . . . . . . . . . EXPDATE
Move policy . . . . . . . . . . . . . . MOVPCY
Media class . . . . . . . . . . . . . . MEDCLS
*DEV
*YES
*NONE
> *FULL
*REF
*REF
*NO
*NONE
*ALL
*ALL
*SYSBAS
*MEDPCY
*MEDPCY
*MEDPCY
Save Journal Receivers Support (New for 6.1)
• New Special Values
• *ALLCHGRCV
– Save Journal Receivers in User Libraries
– Never Been Saved (or)
– Changed Since Last Saved
• *ALLDTCRCV
– Save Detached Journal Receivers in User Libraries
– Never Been Saved (or)
– Changed Since Last Saved
Save Journal Receivers Support (New for 6.1)
Create Backup Control Group Entries
Group . . . . . . . . . . : JRNRCV
Default activity . . . *BKUPCY
Text . . . . . . . . . . . *NONE
Type information, press Enter.
Backup
Seq Items
List ASP
Type Device
10 *ALLDTCRCV
20 *ALLCHGRCV
*SYSBAS
*SYSBAS
Weekly
Activity
SMTWTFS
*DFTACT
*DFTACT
Retain Save SWA
Object While Message
Detail Active Queue
*YES *NO
*YES *NO
Sync
ID
New Overrides on STRBKUBRM (New for 6.1)
Start Backup using BRM (STRBKUBRM)
Type choices, press Enter.
Device . . . . . . . . . . . . . . . . *CTLGRPATR
+ for more values
Parallel device resources:
Minimum resources . . . . . . *CTLGRPATR
Maximum resources . . . . . *MIN
Media class . . . . . . . . . . . . . *CTLGRPATR
Move policy . . . . . . . . . . . . . *CTLGRPATR
Omits . . . . . . . . . . . . . . . . . . *PROCESS
Name, *CTLGRPATR, *MEDCLS
1-32, *CTLGRPATR, *NONE...
1-32, *MIN, *AVAIL
*CTLGRPATR, *SYSPCY,MLR3,
*CTLGRPATR, *NONE,
*PROCESS, *IGNORE
Better IFS Messages - BRMS Log (New for 6.1)
Display BRM Log Information
Current date/time . . . . . : 12/28/07 11:29:24
Position to date . . . . . . : 12/28/07
Date sent Time sent Message
12/28/07 11:15:28 Interactive users are allowed to stay active.
12/28/07 11:15:28 Change to media controls successful.
12/28/07 11:15:28 Change to media controls successful.
12/28/07 11:15:28 Starting save of list *LINK to devices TAPVRT01.
12/28/07 11:28:58 Object in use. Object is /derby.log.
12/28/07 11:28:58 Cannot open object /derby.log.
12/28/07 11:28:58 Object in use. Object is /QIBM/ProdData/OS400/Eclipse/co
12/28/07 11:28:58 Cannot open object /QIBM/ProdData/OS400/Eclipse/configura
12/28/07 11:28:58 Object in use. Object is /QIBM/ProdData/OS400/Eclipse/co
12/28/07 11:28:58 Cannot open object /QIBM/ProdData/OS400/Eclipse/configura
12/28/07 11:28:58 Object in use. Object is /QIBM/ProdData/OS400/Eclipse/co
12/28/07 11:28:58 Cannot open object /QIBM/ProdData/OS400/Eclipse/configura
Auditing/Performance Backup Report (New for 6.1)
• View or Print
– Backup Statistics
– Monitor Backup Activities
• PRTRPTBRM *BKUSTAT Command
FlashCopy Support
FlashCopy Support (New for 6.1)
• Better BRMS Integration
– System Policy
– INZBRM Command
• BRMS Network Feature (Option 1) Required
• Backup of Clone System
– Enable BRMS FlashCopy Function on Production System
– BRMS History Appears as if Backup Performed on Production System
• BRMS FlashCopy Mode
– BRMS Synchronization Job Will Not Run on Production System
– Do Not Perform BRMS Activity on Production until FlashCopy Post
Steps Complete
Flashcopy Support (New for 6.1)
Change System Policy
Type choices, press Enter.
End subsystems wait time . . . . . . . . 1200
End servers wait time . . . . . . . . . . . 0
Controlling subsystem:
Allow backups in batch . . . . . . . . . *NO
Restricted state time limit . . . . . . .*NOMAX
*NOMAX
Trace . . . . . . . . . . . . . . . . . . . . . . . *NO
Allow alternate input media. . . . . . . *YES
Volume prefix . . . . . . . . . . . . . . . . .
Enable FlashCopy . . . . . . . . . . . . . .*NO
BRMS submitted jobs:
Job description. . . . . . . . . . . . . . . .
Library. . . . . . . . . . . . . . . . . . . . . .
Job queue. . . . . . . . . . . . . . . . . . . .
Library. . . . . . . . . . . . . . . . . . . . . .
1-99999 seconds,*IMMED
0-9999 seconds
*NO, *YES
5-9999 minutes,
*NO, *YES
*NO, *YES
Prefix
*NO, *YES
Name, *USRPRF
Name, *LIBL, *CURLIB
Name, *JOBD
Name, *LIBL, *CURLIB
Flashcopy Support (New for 6.1)
Initialize BRMS (INZBRM)
Type choices, press Enter.
Option . . . . . . . . . . . . . > *FLASHCOPY
*DATA, *CHGSYSNAM,
State . . . . . . . . . . . . . *STRPRC
*ENDBKU, *ENDPRC,
Media Management Enhancements
Media Balancing (New for 6.1)
• New STRBALBRM Command
• Balance Scratch Volumes
– Owned by Each System
– BRMS Network
• Restricted State Saves
– Less Likely to Run Out of Media
– No Need to Ask Other Systems for More Media
• Run STRBALBRM with No BRMS Activity
Media Balancing (New for 6.1)
1.
2.
List Systems in Order of Highest to Lowest Priority
Set Priority
STRBALBRM ACTION(*SET) MEDCLS(media-class) LOC(location)
SYSNAME(system-name) MEDPTY(number) MEDREQ(number)
3.
Print and Review Media Balance Report
STRBALBRM ACTION(*REPORT) MEDCLS(media-class) LOC(location)
4.
If Necessary, Balance Media
5.
Review Media Balance Report
Media Balancing Report (New for 6.1)
File . . . . . : QP1AMBL
Page/L
Control . . . . .
Column
Find . . ..+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....8....+....9....+....0....+....1.
5761BR1 V6R1M0 080215
Criteria
Media Balancing Report
6/29/07 13:56:1 Selection
Media Class . . . . . . . . . . : FMT3590H
Location . . . . . . . . . . . . : TAPMLB01
System . . . . . . . . . . . . . : *NETGRP
Number of
System
Network
Media
Media
Class
Location
Media
Priority
Media
Name
ID
PROD01
APPN
FMT3590H TAPMLB01
1
5
3
Communicating
PROD02
APPN
FMT3590H TAPMLB01
2
4
5
Communicating
DEV
APPN
FMT3590H TAPMLB01
3
2
3
Communicating
*****ENDOFLISTING*****
Required
Number of
Available
Status
After Media Balancing Report (New for 6.1)
File . . . . . : QP1AMBL
Page/L
Control . . . . .
Column
Find . . ..+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....8....+....9....+....0....+....1.
5761BR1 V6R1M0 080215
Criteria
Media Balancing Report
6/29/07 13:59:1 Selection
Media Class . . . . . . . . . . : FMT3590H
Location . . . . . . . . . . . . : TAPMLB01
System . . . . . . . . . . . . . : *NETGRP
Number of Number of
System
Name
Network
Media
Media
ID
Class
Location
Priority
Media
Media
Required
Available
Status
PROD01
APPN
FMT3590H TAPMLB01
1
5
5
Communicating
PROD02
APPN
FMT3590H TAPMLB01
2
4
4
Communicating
DEV
APPN
FMT3590H TAPMLB01
3
2
2
Communicating
*****ENDOFLISTING*****
Automatic Duplication (New for 6.1)
• Automatic Duplication Option on Media Policy
• Ensures Virtual Media is Duplicated to Physical Media
• Control Group Backup
– Duplication Occurs after Each Save is Complete
– Multiple Duplications with Asynchronous Jobs
– Jobs Run on Queue Specified on System Policy
• Duplication Jobs
– If Insufficient Devices Waits for Devices to Become Available
– If System in Restricted State, Jobs Wait in Job Queue until System
Active
• Backup Completes
– Control Returned to User
– Duplications Continue in Background
Automatic Duplication (New for 6.1)
Change Media Policy
Media policy . . . . . . . . . . . . . . : JAPMED
Type choices, press Enter.
Automatic duplication:
From devices . . . . . . . . . . . . *NONE
From device end option . . . . *REWIND
To devices . . . . . . . . . . . . . . *SAME
To device end option . . . . . . *REWIND
To media policy . . . . . . . . . *SAME
Save media information . . . . *SAME
Name, *NONE, *SAME, *MEDCLS..
*REWIND, *LEAVE, *UNLOAD
Name, *SAME, *MEDCLS, F4
*REWIND, *LEAVE, *UNLOAD
*SAME, *SYSPCY, F4
*SAME, *BKUPCY, *LIB, *OBJ
*NONE
Move Media Retention Capability (New for 6.1)
• Media is Brought Onsite for Restores
• Need to Keep Media Onsite for Period of Time
• Move Media Option
– Exempt Media from Move Policy
– Specified Amount of Time
Move Media Retention Capability (New for 6.1)
Move Media
Type storage location or container to receive volumes.
Storage location . . *SAME
*SAME, F4 for list
Container . . . . . . . *SAME
*SAME, F4 for list
Exempt from movement 35
*SAME, 0 - 9999
…................................................……………….......................
Volume :
Exempt from movement - Help
:
Opt Serial :
:
8 GEN001 :
Specify the number of days that this media will be
:
:
retained at the current location exempt from move
:
:
policy processing. Number of days can range from 0 to :
:
9999. 0 indicates that the media is not exempt from
:
:
movement.
:
Movement/Container Auto Open/Close (New for 6.1)
Change Move Policy
Move policy . . . . . . . . . : OFFSITE
Home location . . . . . . . . . *SYSPCY
Name, *SYSPCY, *ORIGIN, F4 list
Use container . . . . . . . . . *YES
*YES, *NO
Verify moves . . . . . . . . . . *YES
*YES, *NO
Calendar for working days . . . *ALLDAYS Name, *ALLDAYS, F4 for list
Calendar for move days . . . . . *ALLDAYS Name, *ALLDAYS, F4 for list
Text . . . . . . . . . . . . . . Entry created by BRM configuration
Type choices, press Enter.
Seq
10
20
•
Location
OLDVAULT
VAULT
Duration
20
*EXP
Container Action
*CLOSE
*OPEN
Stop SNA Attempt If No TCP (New for 6.1)
Change Network Group
Network group . . . . . . . . :
FlashCopy state. . . . . . . :
Receive media info . . . . :
Communication method :
Notify period . . . . . . . . . :
*MEDINV
*ENDPRC
*NONE
*AVAIL
30
Position to . . . . :
*NONE, *LIB
*AVAIL, *IP, *SNA, *NONE
30-99999 seconds
Type options, press Enter.
1=Add 4=Remove 8=Set time
Remote Local Remote Receive
System
Opt Location Name Network ID Media Info Status
X1521P3
APPN
*LIB
Online
Network
Status
Active
Advanced Feature – Tape Library Status (New for 6.1)
• Report Displays Users of Tape Library Resources in BRMS Network
• Tape Library Resource Status for Specific System
QSYS/CALL QBRM/Q1AOLD PARM(’DEVUSESTS ’ ’SYSTEM1
SYSTEM2’)
• Tape Library Resource Status for All Systems in BRMS Network
QSYS/CALL QBRM/Q1AOLD PARM(’DEVUSESTS ’ ’*NETGRP’)
• Output File QTEMP/DEVICELOG and Report QP1ADEVUSE Generated
• PTFs for Previous Releases
– SI24433 (V5R4)
– SI24427 (V5R3)
Recovery Enhancements
Restore Private Authorities (New for 6.1)
Restore Command Defaults
Type information, press Enter.
Restore private authorities . . . .
*NO, *YES
STRRCYBRM Priority Sequencing (New for 6.1)
Add Object List
Use . . . . . . . . . : *BKU
List name . . . . . RCYLIST
Text . . . . . . . . . Recovery Order Library List
Type choices, press Enter.
Seq
10
20
30
Library
MYPAYROLL
FRIENDSPAY
BOSSPAY
Object
*ALL
*ALL
*ALL
Type
Member
*FILE
*FILE
*FILE
*ALL
*ALL
*ALL
STRRCYBRM Priority Sequencing (New for 6.1)
Start Recovery using BRM (STRRCYBRM)
Type choices, press Enter.
Libraries to omit . . . . . . . . . . . . OMITLIB
Additional Parameters
Volume locations to include . . . .LOC
+ for more values
Volume locations to omit . . . . . . OMITLOC
+ for more values
From system . . . . . . . . . . . . . . .FROMSYS
Print system information . . . . . . PRTSYSINF
Use duplicate media . . . . . . . . USEDUPMED
User recovery information . . . .USRRCYINF
Recovery order list . . . . . . . . . RCYORDLST
*DELETE
*ALL
*NONE
*LCL
*NO
*NO
*NONE
RCYLIST
STRRCYBRM Location Omit (New for 6.1)
Start Recovery using BRM (STRRCYBRM)
Type choices, press Enter.
Libraries to omit . . . . . . . . . . . . OMITLIB
*DELETE
Additional Parameters
Volume locations to include . . . .LOC
Volume locations to omit . . . . . . OMITLOC
From system . . . . . . . . . . . . . . FROMSYS
Print system information . . . . . . PRTSYSINF
Use duplicate media . . . . . . . . USEDUPMED
User recovery information . . . . USRRCYINF
Recovery order list . . . . . . . . . RCYORDLST
*ALL
VAULT
*LCL
*NO
*NO
*NONE
XXXXXXX
Recovery for Logical/Physical Files (New for 6.1)
Additional Message Information
Message ID . . . . . . : CPC371C
Message type . . . . : Completion
Date sent . . . . . . : 01/06/08
Severity . . . . . . . : 00
Time sent . . . . . . : 12:43:14
Message . . . . : 12 objects completed for DFRID Q1ARSTID
Cause . . . . . : The restore has been completed for all 12 objects that
were deferred with Defer ID (DFRID) Q1ARSTID.
BRMS Enhancements for 7.1
• Domino 8.5 DAOS
• IBM Systems Director
• IBM Systems Director Navigator for i
– Level 2 Console (L2C)
– Scheduling via Systems Director
– Viewing Scheduled BRMS Jobs
– Filtering BRMS Messages in BRMS Log
– Marking Volumes for Duplication
– Multiple E-mail Addresses Support
• QIBMLINK Link List
• QALLUSRLNK Link List
• Support for more than 999,999 Objects
• STRRCYBRM Enhancements
– Additional Overrides
– Recovery Report Enhancements
BRMS Enhancements for 7.1
• BRMS Restores with Outfile Option
• BRMS ASP Control Support on RSTLIBBRM/RSTOBJBRM
• BRMS Distributed Backup Support
– 5250 Emulation Screens
– IASP History Setup via Systems Director Navigator for i
• BRMS Maintenance Enhancements
• Movement Report Improvements
•
•
•
•
•
Clearing Volumes in *ERR Status
Protecting Volumes Marked for Duplication
Improved Recovery Times
New Restore Special Value
Non-BRMS Saves on a BRMS System
BRMS and Domino 8.5 DAOS (New for 7.1)
• Before Domino 8.5.0 and DAOS
– Document Attachment and Object Service (DAOS)
– Document Attachments Part of .nsf File
• With Domino 8.5.0 and DAOS
– Document Attachments Pulled out of .nsf File as .nlo Objects
• With Domino 8.5.1 and PTFs SI34916 (V5R4M0) or SI34918 (6.1) or Later
– BRMS Auto-detects NLO Objects for Domino Online Backups (NO BRMS
Changes Needed)
– Full Save Includes all NLO Objects
– Incremental Save Includes New and Changed NLO Objects
– In BRMS Base Code for 7.1
• Be Careful with Externalized Attachment Size
– Otherwise Many .nlo Objects
– Lot of Extra IFS Objects = Slower Backups
DAOS Objects Saved at End of SAVDOMBRM (New for 7.1)
Work with Media Information
BRMSSYS
Position to Date . . . . .
Type options, press Enter.
2=Change 4=Remove 5=Display 6=Work with media 7=Restore
9=Work with saved objects ...
Saved
Save Save Save Parallel Volume File
Expire
Opt Item
Date Time Type Devices Serial Sequence Date
DOMINO04 3/01/10 3:23:30 *LTSONL 2 PT1015
1 3/21/10
DOMINO04 3/01/10 3:24:27 *LTSONL 2 PT1015
3 3/21/10
DOMINO04 3/01/10 3:24:59 *LTSONL 2 PT1015
5 3/21/10
DOMINO04 3/01/10 3:26:33 *FULL
2 PT1015
6 3/21/10
DAOS Objects Saved at End of SAVDOMBRM (New for 7.1)
Work with Media Information
BRMSSYS
Position to Date . . . . .
Type options, press Enter.
2=Change 4=Remove 5=Display 6=Work with media 7=Restore
9=Work with saved objects ...
Saved
Save
Save Item
Opt Item
Date
Time Type
----- Objects ----- Control
Obj
Saved Not Saved Group
Dtl
DOMINO04
3/01/10 3:23:30 *LNK
50
0 QLTSDOM04 *YES
DOMINO04
3/01/10 3:24:27 *LNK
50
0 QLTSDOM04 *YES
DOMINO04
DOMINO04
3/01/10 3:24:59 *LNK
3/01/10 3:26:33 *LNK
10
1345
0 QLTSDOM04 *YES
0 QLTSDOM02 *YES
IBM Navigator for i (GUI) vs. Systems Director Navigator
for i (WEB) (New for 7.1)
• Almost Functionally and Visually Identical
• IBM Systems Director Navigator for i Includes Scheduling Function with
7.1
– For Backup, Maintenance, Printing Reports, Reclaim, etc.
IBM Systems Director Navigator for i 6.1
Scheduling BRMS - Systems Director Navigator for i
(New for 7.1)
• Schedule BRMS Jobs via WEB Interface
• Can Schedule:
– Backup Control Groups
– Archive Control Groups
– BRMS Maintenance
– BRMS Movement
Viewing BRMS Scheduled Jobs (New for 7.1)
• Only Active or Completed Jobs Could be Viewed or Monitored at 6.1
• Scheduled Jobs via IBM Navigator for i (GUI) Also Listed
• BRMS Green Screen Lists IBM Systems Director for i (WEB) and IBM
Navigator for i (GUI) Jobs
Filtering Control Group Messages in BRMS Log
(New for 7.1)
• New Option in IBM Navigator for i and IBM Systems Director Navigator
for i
• Searches Messages for Specific Control Group
Marking Volumes for Duplication via GUI/WEB
(New for 7.1)
• With 7.1 can Mark/Unmark Volumes for Duplication
– IBM Navigator for i (GUI)
– IBM Systems Director Navigator for i (WEB)
• Same Functionality as WRKMEDBRM Option 18 and 19
Multiple E-mail Address Support (New for 7.1)
• With 7.1 Specify Multiple E-mail Addresses to Send BRMS Alerts
• Setup Under Global Policies>Network
– IBM Navigator for i (GUI)
– IBM Systems Director Navigator for i (WEB)
• Not Available in 5250 Emulation
• Separate E-mail Addresses with Comma and No Space
• Requires SMTP Server to be Running
IBM IFS Link List Added to *SYSGRP (New for 7.1)
• QIBMLINK Link List for IBM Directories Added to *SYSGRP Control
Group
– Only Added on New BRMS Installations – NOT Added during
System Release Upgrade
– Recommend to Add Manually to *SYSGRP for Current Installations
IBM IFS Link List Added to *SYSGRP (New for 7.1)
Display Backup Control Group Entries
BRMSSYS
Group . . . . . . . . . . : *SYSGRP
Default activity . . . . : *BKUPCY
Text . . . . . . . . . . : Backs up all system data
Weekly
Backup List
ASP
Activity
Seq Items
Type Device SMTWTFS
10 *EXIT
*******
20 *SAVSYS
*DFTACT
30 *IBM
*DFTACT
40 QIBMLINK *LNK *ALLAVL*DFTACT
50 *EXIT
*******
Retain
Object
Detail
Save
While
Active
*NO
*NO
*NO
*NO
SWA
Message Sync
Queue
ID
User IFS Link List (New for 7.1)
• New QALLUSRLNK Link List
– Save User IFS Directories and Files
– Use in Conjunction with QIBMLINK Link List
– Omits the Following:
• '/QSYS.LIB'
• '/QDLS'
• ‘/TMP/BRMS'
• '/QIBM/ProdData‘
• '/QOpenSys/QIBM/ProdData'
QALLUSRLNK Link List (New for 7.1)
Work with Lists
Position to . . . . . .
Starting characters
Type options, press Enter.
1=Add 2=Change 3=Copy 4=Remove 5=Display 6=Print
Opt List Name Use Type Text
QALLSPLF
*BKU *SPL All printed output
QALLUSRLNK *BKU *LNK All user directories
QIBMLINK
*BKU *LNK All IBM directories
QLNKOMT
*BKU *LNK Associated user omit list for *LINK.
BRMSSYS
Support More than 999,999 Objects (New for 7.1)
• BRMS now Shows More than 999,999 Objects Saved:
– WRKMEDIBRM Display
– BRMS Recovery Report (QP1ARCY)
Correct Number of Objects Saved Listed
(New for 7.1)
Work with Media Information
BRMSSYS
Position to Date . . . . .
Type options, press Enter.
2=Change 4=Remove 5=Display 6=Work with media 7=Restore
9=Work with saved objects ...
Saved
Save
Save Item
----- Objects -----
Date Time Type
2/26/10 8:11:38 *LIB
LIBB
2/26/10 8:13:26 *LIB
1
0
MJTEST *YES
*LINK
2/26/10 8:14:57 *LNK
1090926
0
MJTEST *NO
0
MJTEST *YES
16
Group
*NONE
Obj
Opt Item
LIBA
QUSRBRM 2/26/10 8:15:04 *OBJ
Saved Not Saved
1
0
Control
Dtl
*NO
Correct Number of Objects on Recovery Report
(New for 7.1)
__ STEP 017 : Recover Directories and Files
Start date/time __________________ Stop date/time __________________ Duration ___________
You should restore the current version of your objects in directories.
If you are performing a complete system restore, run the following
command to continue.
STRRCYBRM OPTION(*RESUME)
Otherwise, run the following command.
STRRCYBRM OPTION(*LNKLIST) ACTION(*RESTORE)
Type the command choice and press "Enter".
Select the saved item(s) listed below from the "Select Recovery Items"
display and press "Enter" to recover these saved items. Recovery of
these saved items will require the volumes listed on the report or
duplicate volumes.
--- Objects --Saved
Save ----- ASP ------ Save Save
Not Sequence Control
Item
Type Name
Number Date
Time Saved Saved Number Group
---------- ------- ---------- ----- -------- -------- -------- ------ --------- ---------- --------__ *LINK
*FULL *SYSBAS 00001 11/02/09 14:32:43 1090926 0
0
*SYSTEM
STRRCYBRM - Overrides for Special Values
(New for 7.1)
• Override Selective Parts of Recovery
– *ALLSYS
– *SAVSYS
– *SECDTA
– *SAVCFG
• Ignored if Override Recovery Element (OVERRIDE) Set to *NO
• Affects both *REPORT and *RESTORE
• Override Warning Posted in BRMS Recovery Report
STRRCYBRM – Overrides for Special Values
(New for 7.1)
Start Recovery using BRM (STRRCYBRM)
Type choices, press Enter.
Volume locations to include . . LOC
+ for more values
*ALL
Volume locations to omit . . . . OMITLOC
+ for more values
Override recovery element . . . OVERRIDE
Recovery element override:
*NONE
*YES
RCYELEM
Recovery element . . . . . . .
*SAVSYS
Time period for recovery:
Start time and date:
Beginning time . . . . . . . .
Beginning date . . . . . . . .
End time and date:
Ending time . . . . . . . . .
Ending date . . . . . . . . .
+ for more values
*AVAIL
*BEGIN
*AVAIL
*END
Attention in BRMS Recovery Report for Overrides
(New for 7.1)
Display Spooled File
File . . . . . : QP1ARCY
Page/Line 7/48
Control . . . . .
Columns 1 - 130
Find . . . . . .
*...+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....8....+....9....+....0....+....1....+....2....+....3
****************************************************************************************************
__ STEP 009 : Recover User Profiles
Start date/time __________________ Stop date/time __________________ Duration _________________
----- Attention --------------------------------------------------There is an override for recovery element *SECDTA.
--------------------------------------------------------------------You should restore a current version of your user profiles.
To do so, type the following command and press "Enter".
----- Attention --------------------------------------------------Press F9 on the Select Recovery Items display to go to the Restore
Command Defaults display.
__ Ensure the tape device name or media library device name is
correct for the Device prompt.
__ Ensure *SAVLIB is specified for the Restore to library prompt.
__ Ensure *SAVASP is specified for the Auxiliary storage pool prompt.
If you are recovering to a different system or a different logical
partition, you must specify the following:
BRMS Recovery Report (QP1ARCY) Enhancements
(New for 7.1)
• Verify System Information Step: Added UPDSYSINF Command
– Save of QUSRSYS Includes RTVSYSINF
– Updates System Information if Recovery from Distribution Media
– Updates System Information from More Current QUSRSYS Save than
SAVSYS Save
– Resets System Values Changed for System Recovery
• Recover User Profiles Step: Use New *COMPATIBLE Value
STRRCYBRM - Verify System Information Step
(New for 7.1)
File . . . . . : QP1ARCY
Page/Line 22/42
Control . . . . .
Columns 1 - 130
Find . . . . . . Verify
********************************************************************************************
__ STEP 020 : Verify System Information
Start date/time __________________ Stop date/time _________________ Duration
_________________
You should verify your system information.
If you use either of the following commands after the save, additional
reports are created which can be used to verify the system information.
STRRCYBRM PRTSYSINF(*YES)
STRMNTBRM PRTSYSINF(*YES)
If you recovered using distribution media or if your save of QUSRSYS is
more current than your system save, then it is recommended that you
update your system information by running the following command:
UPDSYSINF LIB(QUSRSYS)
For more information about recreating your system information, refer
to the "Recovering your system" topic.
*******************************************************************************************
STRRCYBRM Recover User Profiles (New for 7.1)
File . . . . . : QP1ARCY
Page/Line 8/38
Control . . . . .
Columns 1 - 130
Find . . . . . .
********************************************************************************************
__ STEP 009 : Recover User Profiles
Start date/time __________________ Stop date/time __________________ Duration
_________________
You should restore a current version of your user profiles.
To do so, type the following command and press "Enter".
STRRCYBRM OPTION(*SYSBAS) ACTION(*RESTORE)
----- Attention --------------------------------------------------Press F9 on the Select Recovery Items display to go to the Restore
Command Defaults display.
__ Ensure the tape device name or media library device name is
correct for the Device prompt.
__ Ensure *SAVLIB is specified for the Restore to library prompt.
__ Ensure *SAVASP is specified for the Auxiliary storage pool prompt.
If you are recovering to a different system or a different logical
partition, you must specify the following:
__ *ALL for the Data base member option prompt.
__ *COMPATIBLE for the Allow object differences prompt.
__ *NONE for the System resource management prompt.
Press "Enter" to return to the Select Recovery Items display.
BRMS Restores with OUTFILE Option (New for 7.1)
• New OUTFILE Option for BRMS Restores
• Lists What Restored and What Not Restored
• Specify OUTFILE Option
– Recovery Policy – WRKPCYBRM TYPE(*RCY)
– BRMS Restore Commands
• RSTLIBBRM
• RSTOBJBRM
• RSTBRM
– Recovery Defaults for
• WRKMEDIBRM
• STRRCYRM ACTION(*RESTORE)
OUTFILE Option on BRMS Recovery Policy
(New for 7.1)
Change Recovery Policy
BRMSSYS
Type choices, press Enter.
Key store file . . . . . . . . . . *SAV
Name, *SAV, *NONE
Key store library . . . . . . . *SAV
Name, *SAV, *NONE
Restore private authorities. . . . *NO *NO, *YES
Output options for recoveries:
Output. . . . . . . . . . . . . . *NONE
*NONE, *OUTFILE
File to receive output. . . . . .
Name
Library. . . . . . . . . . . . . *LIBL
Name, *LIBL, *CURLIB
Output member options:
Member to receive output . . . . *FIRST
Name, *FIRST
Replace or add records . . . . . *REPLACE
*REPLACE, *ADD
Output options for directory object recoveries:
Output. . . . . . . . . . . . . . *NONE
OUTFILE Option on RSTLIBBRM Command
(New For 7.1)
Restore Library using BRM (RSTLIBBRM)
Type choices, press Enter.
Restore incremental . . . . . . *YES
*YES, *NO
Allow object differences . . . . *NONE *NONE, *ALL, *COMPATIBLE...
+ for more values
Private authorities . . . . . . *NO
*NO, *YES
Restore to library . . . . . . . *SAVLIB
Name, *SAVLIB
Auxiliary storage pool . . . . . *SAVASP Name, 1-32, *SAVASP, *SYSTEM
From system . . . . . . . . . . *LCL
Additional Parameters
Output . . . . . . . . . . . . . *NONE
File to receive output . . . . .
Library . . . . . . . . . . . *LIBL
Output member options:
*NONE, *OUTFILE
Name
Name, *LIBL, *CURLIB
Member to receive output . . . *FIRST
Name, *FIRST
Replace or add records . . . . *REPLACE *REPLACE, *ADD
OUTFILE Option on RSTBRM Command
(New For 7.1)
Restore Object using BRM (RSTBRM)
Type choices, press Enter.
Save level time reference:
Save date . . . . . . . . . .
Date
Save time . . . . . . . . . . *LATEST
Time, *LATEST
End of media option . . . . . . *REWIND
*REWIND, *LEAVE, *UNLOAD
Option . . . . . . . . . . . . . *ALL
*ALL, *NEW, *OLD
Allow object differences . . . . *NONE
*NONE, *ALL, *AUTL, *OWNER...
Private authorities . . . . . . *NO
*NO, *YES
Object ID . . . . . . . . . . . *SAVED
*SAVED, *SYS
Create parent directories . . . *NO
*NO, *YES
Parent directory owner . . . . . *PARENT Name, *PARENT
From system . . . . . . . . . . *LCL
Output . . . . . . . . . . . . . *NONE
OUTFILE Option on WRKMEDIBRM – STRRCYBRM
(New for 7.1)
Restore Command Defaults
Type information, press Enter.
Restore private authorities . . . . *NO
*NO, *YES
Output options for recoveries:
Output . . . . . . . . . . . . . . *NONE
*NONE, *OUTFILE
File to receive output . . . . . .
Name
Library . . . . . . . . . . . . . *LIBL
Name, *LIBL, *CURLIB
Output member options:
Member to receive output. . . . . *FIRST
Name, *FIRST
Replace or add records. . . . . . *REPLACE *REPLACE, *ADD
Output options for directory object recoveries:
Output . . . . . . . . . . . . . . *NONE
ASP Control on RSTLIBBRM/RSTOBJBRM
(New for 7.1)
• Specify Saved ASP on following BRMS Commands
– RSTLIBBRM
– RSTOBJBRM
• Allows More Control to Select Restores by ASP
ASP Parameter on RSTLIBBRM Command
(New for 7.1)
Restore Library using BRM (RSTLIBBRM)
Type choices, press Enter.
Library . . . . . . . . . . . .
Name, *MEDINF
+ for more values
Device . . . . . . . . . . . . .
Name, *MEDCLS
+ for more values
Parallel device resources:
Minimum resources . . . . . . *SAV
1-32, *SAV, *NONE, *AVAIL
Maximum resources . . . . . . *MIN
1-32, *MIN, *AVAIL
Save level . . . . . . . . . . . *CURRENT
1-99, *CURRENT, *SAVDATE
Saved auxiliary storage pool . . *ANY
Name, 2-32, *ANY, *SYSTEM
End of media option . . . . . . *REWIND
*REWIND, *LEAVE, *UNLOAD
Option . . . . . . . . . . . . . *ALL
*ALL, *NEW, *OLD, *FREE
Database member option . . . . . *MATCH MATCH, *ALL, *NEW, *OLD
Spooled file data . . . . . . . *NEW
*NEW, *NONE
Restore incremental . . . . . . *YES
*YES, *NO
Allow object differences . . . . *NONE
*NONE, *ALL, *COMPATIBLE...
+ for more values
BRMS Distributed Backup Support (New for 7.1)
• New BRMS Network Options Allowing Distribution of Backup History
• Used for:
– Which Systems Receive Saved History
• Requires Remote System with *LIB for Networking
– iASP Support and Synchronization Control
• Decide to Make Synchronized System the Owner
• Update Reference Date for Incremental Backups
Change Network Group (6.1)
Change Network Group
BRMSSYS APPN
Network group . . . . : *MEDINV
Position to . . . . :
FlashCopy state . . . : *ENDPRC
Receive media info . : *LIB
*NONE, *LIB
Communication method : *IP
*AVAIL, *IP, *SNA, *NONE
Notify period . . . . : 30
30-99999 seconds
Type options, press Enter.
1=Add 4=Remove 8=Set time
Remote Local
Remote
Receive System
Network
Opt Location Name Network ID Media Info
Status
Status
BRMSSYSB
BRMSSYSC
APPN
APPN
*LIB
*LIB
Online
Online
Active
Active
Enhancements to Change Network Group
(New for 7.1)
Change Network Group
APPN
Network group . . . . : *MEDINV
Position to . . . . :
FlashCopy state . . . : *ENDPRC
Communication method : *AVAIL
*AVAIL, *IP, *SNA, *NONE
Notify period . . . . : 30
30-99999 seconds
Type options, press Enter.
1=Add 4=Remove 8=Set time
Remote Local Remote
System
Opt Location Name Network ID Status
BRMSSYSB
BRMSSYSC
APPN
APPN
Online
Online
Network
Status
Active
Active
BRMSSYS
Enhancements to Change Network Group (cont)
Change Network Group
APPN
Network group . . . . : *MEDINV
Position to . . . . :
FlashCopy state . . . : *ENDPRC
Communication method : *AVAIL
*AVAIL, *IP, *SNA, *NONE
Notify period . . . . : 30
30-99999 seconds
Type options, press Enter.
1=Add 4=Remove 8=Set time
-----BRMS Media Information----Remote Local Remote
Local -------Remote------Opt Location Name Network ID Receives Receives Overrides
BRMSSYSB
BRMSSYSB
APPN
APPN
*LIB
*NONE
*NONE
*NONE
*NO
*NO
BRMSSYS
iASP Distributed History (New for 7.1)
• Used for iASP Flash Copy
• Allows iASP to be Flashed Copied, Connected to Another System in
BRMS Network and Saved
• Once Save Complete, History Sent to Defined System
• Ownership of History can be Changed to Source System allowing
Cumulative Saves on the Source System
BRMS Maintenance Enhancements (New for 7.1)
• BRMS Maintenance (STRMNTBRM) Enhancements Include:
– More Concurrent Maintenance Allowed
– Warning when Volumes in Use and Cannot be Moved
– Volume Move Report (QPIAVMS) Warning
– Automatic hold BRMS Jobs Wanting to use Files Maintenance is Using
• Messages
– BRM6714 - Current job being held by maintenance job
– BRM6715 – BRM restricted procedure started
– BRM6716 – BRM restricted procedure ended
Media Movement Planning Report (New for 7.1)
• PRTMOVBRM TYPE(*NEXT) Shows Future Movement of Media
• Select Future Date on Second Value on Select dates (SLTDATE)
Parameter
Move Media Report - QP1APVMS (New for 7.1)
File . . . . . : QP1APVMS
Page/Line 8/11
Control . . . . .
Columns 1 - 130
Find . . . . . .
*...+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....8....+....9....+....0....+....1....+....2....+....3
Next Scheduled Volume Movement
From location . . . : VAULT
To location . . . . : TS7650
Volume
To Creation Expire Move
Move
Container
From
Volume
Serial
Slot Date
Date
Policy
Date Container Slot Slot System
Identifier
BRM001
2 3/04/10 3/30/10 DAILY
3/30/10 *NONE
2 BRMSSYS BRM001
BRM003
3 3/04/10 3/30/10 DAILY
3/30/10 *NONE
3 BRMSSYS BRM003
Total volumes . . . . . :
2
***** END OF LISTING *****
Clearing Volumes in *ERR Status (New for 7.1)
• Clear Volumes in *ERR Status Without Removing from BRMS
• Available in WEB, GUI and 5250 Emulation
• New Option 9 on WRKMEDBRM
• Changes *ERR Volume to *INZ Status
• Once *INZ Status, Volume can be Re-initialized
– WRKMEDBRM - Option 10
– WRKMLMBRM - Option 5
– INZMEDBRM
WRKMEDBRM – Volume in *ERR Status (New for 7.1)
Work With Media
System:
BRMSSYS
Position to . . . . .
Starting characters
Type options, press Enter.
1=Add 2=Change 4=Remove 5=Display 6=Work with serial set 7=Expire
8=Move 9=Remove volume error status
Volume
Opt Serial
Creation Expiration
Status Date
Date
10=Reinitialize ...
Move
Location Date
Media
Class
Dup
Sts
BRM001
*EXP 03/04/10 *NONE
*HOME
*NONE
ULTRIUM2
9 BRM002
BRM003
*ERR 03/04/10 *NONE
*EXP 03/04/10 *NONE
*HOME
*HOME
*NONE ULTRIUM2
*NONE ULTRIUM2
BRM004
*EXP 03/04/10 *NONE
*HOME
*NONE
ULTRIUM2
Volume Changed to *INZ Status (New for 7.1)
Work With Media
BRMSSYS
Position to . . . . .
System:
Starting characters
Type options, press Enter.
1=Add 2=Change 4=Remove 5=Display 6=Work with serial set 7=Expire
8=Move 9=Remove volume error status 10=Reinitialize ...
Volume
Opt Serial
Creation Expiration
Status Date
Date
Move
Media
Location Date
Dup
Class
Sts
BRM001
BRM002
*EXP 03/04/10 *NONE
*INZ 03/04/10 *NONE
*HOME
*HOME
*NONE
*NONE
ULTRIUM2
ULTRIUM2
BRM003
BRM004
*EXP 03/04/10 *NONE
*EXP 03/04/10 *NONE
*HOME
*HOME
*NONE
*NONE
ULTRIUM2
ULTRIUM2
Protection of Media Marked for Duplication
(New for 7.1)
• Media Marked for Duplication Will Not Expire
• Warning Message in Media Expiration Report (QP1AEP)
– Pending volume duplication, cannot expire
• Protects Physical and Virtual media
• WRKMEDBRM - Option 7
– Posts BRM0010 Message
BRMS Recovery Time Enhancement (New for 7.1)
• BRMS Supports New POSITION Parameter on RSTLIB, RSTOBJ and
RST Commands
• Done Automatically by BRMS
• Requires Object Level Detail be Saved
– *YES, *OBJ or *MBR on Save Item
• Very Significant Performance Improvements
– For Example: Restoring Last Object from 1.1 million IFS File Save
went from 22 minutes to less than 3 minutes
• Not Supported on WRKMEDIBRM Option 7,7 (Libraries)
• Not Supported on WRKMEDIBRM 9,9,7,7 (IFS)
BRMS Supports *COMPATIBLE for ALWOBJDIF
(New for 7.1)
• *COMPATIBLE Special Value Supported on ALWOBJDIF Parameter
• Behaves like ALWOBJDIF(*ALL) in Combination with
ALWOBJDIF(*FILE) for Database Files
• FINALLY a Single Value that Does What You Usually Need
Running Non-BRMS Saves (New for 7.1)
• Running Non-BRMS Saves with Non-BRMS Volumes
• System Installed with BRMS
• Job will NOT End if BRMS Volume Loaded
• BRMS will Post BRM1730 Message Giving Option to Load Non-BRMS
Volume
IFS Save Performance Enhancement (New ASYNCBRING)
–
–
–
–
AYSNCBRING Parameter Added to Parameter Overrides
PTFs for 6.1 and 7.1
Very good Performance Improvement for Most Customers
For details see BRMS website:
• https://www.ibm.com/developerworks/mydeveloperworks/wikis/home?lang=en#/wiki/IBM%20Backup
%2C%20Recovery%20and%20Media%20Services%20%28BRMS%29%20for%20i/page/Overriding
%20the%20ASYNCBRING%20parameter%20on%20IFS%20saves%20to%20improve%20performa
nce
New BRMS Enterprise Function
Central
“Enterprise System”
The central “Enterprise System” (HUB)
pulls important information from systems
(NODES) defined in its “Enterprise”
network. From this information, specific
notifications, verifications and various
other functions can be made and help an
administrator manage the health of their
BRMS backups/recoveries from one
central server. Very beneficial for those
customer environments where there are
networks of systems.
Multiple BRMS networks
Central
“Enterprise System”
OR
One BIG BRMS network
Central
“Enterprise System”
Collects
BRMS Network
1
BRMS
Media
Databas
e
iSeries
B
BRMS
Media
Databas
e
Collects
iSeries
A
BRMS
Media
Databas
e
Collects
iSeries
C
BRMS Network 2
BRMS
Media
Database
iSeries
A
BRMS
Media
Database
BRMS
Media
Database
iSeries
B
iSeries
C
BRMS Network 3
BRMS
Media
Database
iSeries
A
iSeries
B
BRMS
Media
Databas
e
BRMS
Media
Databas
e
iSeries
C
Collects
BIG! BRMS Network
BRMS Enterprise Function
No Green Screen – IBM Navigator for i (Web) or
IBM System Navigator (GUI) 7.1 and Higher
Central
“Enterprise System”
- BRMS Hub and Node Systems Require
BRMS Licenses
- Hub System Require BRMS Network Feature
and BRMS Advanced Feature Licenses
- Required PTFs for Systems in BRMS
Enterprise Network
- i 7.1 - SI47935 Note: For this release,
language specific PTFs applied for each
secondary language on the system
- V6R1 - SI47934
- V5R4 - SI47933
BRMS Enterprise Terminology
•
•
•
•
HUB (aka…Centralized Enterprise System)
– The Enterprise Hub is a central site that monitors BRMS backups for other BRMS systems called Enterprise Nodes. The
Nodes being monitored by the Hub are called an Enterprise Network.
– The Enterprise Network may include BRMS stand-alone and BRMS Networked systems. Communication is configured
through each of the Nodes in the Enterprise Network and is completely independent of traditional BRMS Network
configuration.
Nodes
– Enterprise Nodes are BRMS systems that are being monitored by an Enterprise Hub. Enterprise Node properties are
defined by and maintained on the Hub. No Enterprise configuration is currently required on the Nodes!
• Node Policy
– Each Node has an associated Node Policy. The Node Policy defines properties that can be shared between multiple
Nodes. Each Node can reference the Node Policy for any of its properties.
• Node Group
– Node Groups allow an administrator to assign a name to a group of Nodes. The Node Groups can be based on
attributes the Nodes have in common, for example - owner, location, time zone, etc.
Contact
– Contacts are users associated with the Hub and Nodes. The Contacts are used for a variety of notifications including
reports or errors encountered while generating reports.
Report Definition
– Report Definitions define how and when a report will be generated for a Node. The Report Definition can be run manually or
it can be scheduled to run at defined intervals.
– The output created by running a Report Definition will be stored in a user designated output queue on the Hub. The output
can also be stored in a user designated output queue on the Node and/or emailed to the Contacts for the Node.
• Report Policy
– Each Report Definition has an associated Report Policy. The Report Policy defines properties that can be shared
between multiple Report Definitions. Each Report Definition can reference the Report Policy for any of its properties.
• Report
– When a Report Definition is run for a Node, a Report is generated. Each Report will identify when the Report
Definition was run, what Report Output was produced and where the Report Output was stored.
• Report Output
– Report Output is produced when a Report is run for a Report Definition. The Report Output can be found through the
Report that identifies when the Report Definition was run. Report Output may include multiple files.
How do I access the BRMS Enterprise function?
How do I add a Node to the BRMS Enterprise Network?
When selected, Enterprise Services will display the Hub Center panel. The Hub Center
displays the Nodes that are in the Enterprise Network. Initially the Enterprise Network will
not contain any Nodes. Use the Add button to add Nodes.
How do I quickly add all systems in a BRMS network?
Once a Node exists in the Enterprise Network, the systems that are currently in that Nodes
current BRMS Network can be quickly added to the Enterprise Network by selecting the
Add all systems in the BRMS network option on the pop-up menu for the Node.
What’s a Node look like?
What’s a Node look like? (Continued )
Note: Report definitions, Backup status, and BRMS log will be shown later
What’s a Node Group?
Used to group similar nodes to have similar behavior.
What’s a Node Policy?
Each Node has an associated Node Policy. The Node Policy defines properties that
can be shared between multiple Nodes. Each Node can reference the Node Policy
for any of its properties.
What’s a Node Policy? (Continued)
What’s a Report Definition?
Report Definitions define how and when a report will be generated for a Node. The Report
Definition can be run manually or it can be scheduled to run at defined intervals.
What’s a Report Policy?
Each Report Definition has an associated Report Policy. The Report Policy defines
properties that can be shared between multiple Report Definitions. Each Report Definition
can reference the Report Policy for any of its properties.
What’s a Contact?
Contacts are users associated with the Hub and Nodes. The Contacts are used for a
variety of notifications including reports or errors encountered while generating reports.
What is the Hub Center?
This is the main enterprise panel and can be used as the BRMS Dashboard to find out
information about all the nodes.
What is the Backup Status?
Control groups are now monitored and results are stored in a new file.
What is the Backup Status? (Continued)
Results include if successful or not, amount of data, objects not saved, etc..
What is the BRMS log?
BRMS logs can be viewed from the central system for any node!
What is the BRMS Log? (Continued)
Results include joblog messages,etc. Filtering can also be used on messages,etc.
What about the Reports?
Reports that are generated by BRMS using the STRRCYBRM and STRMNTBRM
commands can be managed by Enterprise via Report Definitions.
They can be scheduled to run and/or can be run directly when needed (as shown below)
How do I view the Reports?
Reports that were generated by Report Definitions can be viewed from the HUB Center as
shown below.
How do I view the Reports? (Continued)
Reports that generated by the Report Definitions can be viewed from the HUB Center as
shown below.
How do I use the Reports?
Reports that generated by the Report Definitions create Report Output…so you can view
the output in detail. They can be viewed/printed in pdf format.
How do I use the Report Outputs?
They can be viewed/printed in pdf format.
Output!
Allow Movement of Volumes Marked for Duplication
PTF Support for Releases V5R4, 6.1 and post 7.1 – See this Wiki URL for more details:
https://www.ibm.com/developerworks/mydeveloperworks/wikis/home?lang=en#/wiki/IBM%20Bac
kup%2C%20Recovery%20and%20Media%20Services%20(BRMS)%20for%20i/page/Allow%
20volumes%20that%20are%20marked%20for%20duplication%20to%20be%20moved
Here is the support integrated into the post IBM i 7.1 release:
BRMS Auto-Restart Option On Saves For Media Errors
– Post 7.1 with Latest BRMS PTF
– Will not be PTF’d to Previous Releases
Use All Tapes Evenly in BRMS
– Switched to Pick Oldest Create Date and then Volume Uses
– PTFs
• IBM i 7.1 - SI43868
• IBM i 6.1 - SI43869
• V5R4 - SI43862
BRMS and RDX Removable Media Devices Support
• RDX Cartridges for Low End Performance (Faster than DAT Tape)
• Capacity 160 GB – 1 TB per Removable Cartridge
• Native Attach with 7.1 TR5 (USB or SATA)
• 6.1.1 PTFs for SATA only
• SATA Dock in either 5.25” internal (SATA or USB) or external USB
• Cartridges Have 30+ years of Reliability and Rugged
• Never Have to Clean the Drive!
BRMS Support via Optical Support
• 32 byte Volume Ids
• Volume selection done upfront
BRMS and RDX Removable Media Devices (cont)
Installing BRMS
• Install BRMS 57xx-BR1 *BASE
57xx-BR1 Option 1 Network Feature
57xx-BR1 Option 2 Advanced Functions Feature
• ADDLICKEY 57xx-BR1
• Apply latest CUM and Save/Restore Group PTF
• Apply BRMS PTFs & Network Ensure no other tape management
software exists
• Install Media Storage Extensions 57xx-SS1 Option#18
• PTFs on all iSeries in BRMS network
• Installation provides three (3) libraries:
– QBRM
BRMS Program Objects
– QUSRBRM
BRMS User setup and BRMS DB
– QMSE
MSE Program Objects
Notes: Installing BRMS
To install BRMS, do the following:
Ensure no other tape management system is installed on your system, since i5/OS can only communicate with one tape
management system at a time. If you will be migrating from another tape management system, careful planning will be
required in advance to avoid problems
Install the Media and Storage Extensions (MSE) feature of OS/400 that should have been shipped on your BRMS tape,
using the standard RSTLICPGM interface. MSE provides the tape exit programs that advise BRMS of all tape activity on
your system so your tapes can be logged and protected. Note that MSE should be installed prior to BRMS so the exit
points can be registered.
Install BRMS using the standard RSTLICPGM interface
Load the latest CUM tape, and then the save-restore group PTF to ensure you are up-to-date on your PTFs for tape,
save/restore, and BRMS. To have IBM ship you the latest save-restore group PTF, do a SNDPTFORD for the following
PTF:
V4R5: SF99077
V5R1: SF99078
V5R2: SF99085
V5R3: SF99185
V5R4: SF99186
V6R1: SF99187
If you are in a BRMS network, you should install the CUM and group PTF on ALL systems in the network. For example
sometimes new versions of BRMS incorporate new fields in the BRMS database to allow new function. Prior to adding a
new system to the network, all systems must have the appropriate PTFs to convert the database records as they are
passed between systems at higher and lower release levels
Following the installation, you will notice 3 new libraries on your system as follow:
QBRM has the BRMS programs
QUSRBRM has your BRMS setup and inventory databases
QMSE has the Media and Storage Extensions programs.
BRMS Entities
Defaults
System Policy
Backup/Recovery/Archive Policy
Retention
Quarterly
Lib1
Lib2
Savefiles
Media Policies
Daily
Lib3
Lib4
Control Groups
15
Move Policies
Storage Locations
Media Classes
Tape Devices
Notes - BRMS Entities
In order to setup a BRMS backup, you will need to consider each of the following objects. Default
objects are created by BRMS, or you can create similar objects of your own:
A Backup Control Group is the list of items that should be backed up, along with various
parameters for the underlying save command.
A Media Policy indicates where the scratch tapes are located, whether savefiles should be
used, and how long the saves should be kept
A Move Policy describes the rotation cycle for the tapes
A Storage Location describes a place where you keep tapes, such as COMPROOM,
MLB3494, OFFSITE, LEFT_DRAWER, etc
A Media Class describes the type of tape that should be used, eg 1/2" reel, QIC, 8mm, 3490,
3570, 3590, etc
A Tape Drive is a BRMS description for a device on the system. It includes additional
information such as where the drive is located, and what valid tape densities it can read/write.
You can start at the Control Group, and drill down to select/create the other objects as required, or
you can start at the bottom of the chart, and work your way upwards as you create the various
objects. When using GUI, the backup control group and media policy are combined and called a
Backup Policy and the media class becomes a media pool.
You may find all these objects confusing at first, but as you grow more familiar with BRMS, you will
find that they provide a very flexible save environment.
BRMS Implementation Summary
•
•
•
•
Identify/Review/Design Recovery/Backup Strategy
Add and Update Storage Locations
Review/Update Media Classes
Review/Update Media Device Entries and/or Media Library
Entries
• Add and Modify Move and Media Policies
• Review/Update System, Backup and Recovery Policies
•
•
•
•
•
•
Create Backup Control Groups
Enroll Tapes, Specifying Media Class and Storage Location
Perform Initial Full Save of System (Recovery Starting Point)
Establish BRMS Maintenance and Media Movement Procedures
Review Reports & Address Any Problems
Plan a Recovery Test
Notes - BRMS Implementation Summary
Review your Recovery Strategy: Before setting up BRMS, it is VERY important to ensure you have a sound backup/recovery strategy that is
meeting the needs of your business
Add and Update Storage Locations: This simply entails keying names and addresses. These will be used later in the Tape Drive
Description setup (WRKLOCBRM)
Review and Update Media Classes: BRMS will setup the default media classes based on the drives attached to your system at the time
you loaded BRMS. You can add text, and make any other adjustments that you require. (WRKCLSBRM *MED)
Review Tape/Library Devices: BRMS will setup devices based on the drives attached to your system at the time you loaded BRMS.
Check/adjust the following parameters to suit your environment: Storage Location, Media Classes allowed, Shared Device, Optimum
Block, Next Volume Mount Message (WRKDEVBRM)
Review System, Backup, Recovery Policies: These provide default values for your BRMS system. (WRKPCYBRM *SYS etc)
Add and Modify Move and Media Policies: Be sure to make the move policies first since the media policies point back to them. Also be
sure to set the "Location" parameters correctly in each ... The Media Policy Storage Location tells BRMS where to take the input tape
from. The Move Policy Home Location tells BRMS where to leave the tape after it is finished all its moves. (WRKPCYBRM *MOV or
*MED)
Create Backup Control Groups: Define the items you want to backup, and link the save to the other BRMS entities by making a control
group, You can also specify "subsystems to end/restart" and "JOBQs to hold/release" as part of the backup. (WRKCTLGBRM *BKU)
Enroll Tapes: Add your tapes into the BRMS Database using ADDMEDBRM for standalone tape drives, and ADDMLMBRM for tape
libraries. Be sure to specify the media class and storage location according to those requested in your media policy and control group.
Perform Initial Full Save of System: Run a complete backup of the system, so BRMS will be aware of at least 1 copy of each object.
(STRBKUBRM) Option 21 save that runs the *System control group can be used
Establish BRMS Maintenance and Media Movement Procedures: Arrange to run BRMS maintenance and media movement each evening
to expire tapes, cleanup the database, adjust volume locations, print recovery reports, etc. (STRMNTBRM)
Review Reports and Address any problems: Arrange for an operator or analyst to check the BRMS reports each morning as described
later in this document
Plan a Recovery Test: Ensure that you practice your full system recovery at least once a year to ensure your recovery strategy is
complete and your staff is familiar with the most efficient procedures.
Notes - Monitoring BRMS
The attached checklist shows the BRMS reports that should be reviewed each day to
ensure the saves ran correctly, and the appropriate tapes and documentation are stored
in a safe place in case a recovery is necessary.
Monitoring BRMS
• Find the Recovering Your Entire System Report, Recovery Volume Summary Report, ASP
Information Report, and Recovery Activities Report (if it exists). Make sure you keep these
reports safe since they tell you how to reconfigure your disks and recover your system to
today's backup. Consider one copy on-site and one copy off-site.
BRMS network: find the Centralized Media Audit Report that compares the BRMS database
across systems and correct any errors.
Check the Volume Movement Report for error messages in the right-hand column and
resolve. Gather the volumes that need to move off-site and watch for the volumes returning.
Check the Media Report by Expiration Date to ensure you have enough scratch tapes of
each class for tonight's backups.
Review the Media Information Report to ensure zeroes in the "not-saved" column and
investigate any problems (it is VERY important to resolve any problems).
Review the Media Movement Report--Next Scheduled Volume Movement and contact your
off-site storage company to arrange to have the tapes returned on the dates indicated.
Review the BRMS Services Log (DSPLOGBRM) for error messages.
Check whether a Media Threshold Information Report was printed. If there are any
exceptions, replace those tapes.
BRMS New Web page/Wiki!
Summary
Where are my
tapes?
Priority
Applications
up first
Avoid human
error: writing
over critical
data
Backup
Recovery &
Media Services
Confidence in backup
Recovery
steps outlined
11121
10
2
3
9
4
8
76 5
How much longer
for the restore?
Ability to save spooled
files
Notes - Summary
BRMS is IBM's Strategic Backup Management Product. It helps you to manage your save/restore operations and makes you confident
that you could restore your system if necessary by doing the following:
Manage your Media:
tracks the contents of your tapes as they are written
prevents overwriting active tapes
provides move reports showing which tapes should move to different locations each day
provides lists of tapes that should be in each location at any given time
Automate your Backups:
sets up your backups in a standardized format that others can understand easily
supports save-while-active, object-level saves, spooled file saves that maintain print attributes, saves to TSM, etc
provides detailed reporting on activity and errors etc
Simplify your Recoveries:
shows you all the saves of a certain set of objects so you can choose which generation you want to restore
provides interactive restores of those objects, complete with operator mount messages as appropriate
simplifies full-system recoveries by providing reports showing ASP configuration, tapes required for recovery, and detailed steps for
recovery. Automates those steps once the BRMS product is back on the system.
provides an on-line progress report during a recovery
Hierarchical Storage Management (HSM):
migrates objects among disk ASPs based on age, size, and usage criteria
archives objects to tape based on age, size, usage, frequency-of-use (V4R4) criteria
dynamically recalls *file, DLO and IFS objects when accessed by a user or application, and performs interactive recalls of other
object types
Tape library Support:
interfaces with automated tape libraries to select and mount/demount/eject volumes
Reference Material
Reference Material
• IBM i Information Center
– http://publib.boulder.ibm.com/iseries/
• BRMS Customer site
– http://www-03.ibm.com/systems/i/support/brms/
– Will redirect to new wiki website:
•
https://www.ibm.com/developerworks/ibmi/brms
(short url)
• BRMS GUI documentation
– https://www.ibm.com/developerworks/mydeveloperworks/wikis/home?lang=en#/wiki/IBM
%20Backup%2C%20Recovery%20and%20Media%20Services%20%28BRMS%29%20f
or%20i/page/GUI
Reference Material
Backup and Recovery; SC41-5304-09 (6.1)
Backup and Recovery; SC41-5304-10 (7.1)
Backup, Recovery and Media Services; SC41-5345-06 (6.1)
Backup, Recovery and Media Services; SC41-5345-07 (7.1)
Virtual Tape Redbook; SQ24-7164
http://www.redbooks.ibm.com/abstracts/sg247164.html
Backup, Recovery and Media Service for OS/400: A Practical Approach Redbook; SG24-4840
http://www.redbooks.ibm.com/abstracts/sg244840.html
Performance Management on System i
http://www-03.ibm.com/servers/eserver/iseries/perfmgmt/resource.html
Trademarks and Disclaimers
Adobe, Acrobat, PostScript and all Adobe-based trademarks are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, other
countries, or both.
Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered
trademarks of Intel Corporation or its subsidiaries in the United States and other countries.
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.
IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce.
ITIL is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is registered in the U.S. Patent and Trademark
Office.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Cell Broadband Engine and Cell/B.E. are trademarks of Sony Computer Entertainment, Inc., in the United States, other countries, or both and are used under license
therefrom.
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
Other company, product, or service names may be trademarks or service marks of others.
Information is provided "AS IS" without warranty of any kind.
The customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual
environmental costs and performance characteristics may vary by customer.
Information concerning non-IBM products was obtained from a supplier of these products, published announcement material, or other publicly available sources and
does not constitute an endorsement of such products by IBM. Sources for non-IBM list prices and performance numbers are taken from publicly available information,
including vendor announcements and vendor worldwide homepages. IBM has not tested these products and cannot confirm the accuracy of performance, capability, or
any other claims related to non-IBM products. Questions on the capability of non-IBM products should be addressed to the supplier of those products.
All statements regarding IBM future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only.
Some information addresses anticipated future capabilities. Such information is not intended as a definitive statement of a commitment to specific levels of performance,
function or delivery schedules with respect to any future products. Such commitments are only made in IBM product announcements. The information is presented here
to communicate IBM's current investment and development activities as a good faith effort to help with our customers' future planning.
Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any
user will experience will vary depending upon considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage
configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve throughput or performance improvements
equivalent to the ratios stated here.
Prices are suggested U.S. list prices and are subject to change without notice. Contact your IBM representative or Business Partner for the most current pricing in your
geography.