V System i © 2007 IBM Corporation BRMS Overview – What Does It Do and How Do I Implement It? Debbie Saugen Senior Recovery Architect/Consultant.

System i © 2007 IBM Corporation About the Speaker Debbie Saugen is the Technical Owner of System 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 Conferences, User Group conferences and writing for various magazines, books and websites. You can reach Debbie at dsaugen@us.ibm.com.

System i © 2007 IBM Corporation 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? V5R4 Enhancements Agenda

System i © 2007 IBM Corporation 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? Next, we will provide some guidance for you as you plan your BRMS implementation, 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? L Notes Agenda

Are You Ready for Recovery?

System i © 2007 IBM Corporation 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 AS/400 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.

System i © 2007 IBM Corporation Backup Recovery and Media Services (BRMS)  i5/OS’s Strategic Backup Management Product (5722-BR1)  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

System i © 2007 IBM Corporation 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. 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 Notes - What will BRMS do for my Business?

ƒ 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 IBM Cartridge System Tape Enhanced Capacity Hierarchical Storage Management Option #2: HSM Network BRMS Media Database BRMS Media Database BRMS Media Database iSeriesA iSeriesB iSeriesC Option #1: Network Tape Library Support 3494 3590/2 LTO 3570/3575 ƒ 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? Media Management 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 Vol123 Paylib2 Vol 456 Paylib3 Vol 789 ƒ List of Tapes required ƒ List of Steps to Recover ƒ On-Line Progress Report ƒ Location-specific Recovery Steps Lib3 Lib4 Non-Critical Application Critical Application Lib1 Lib2 Backup Planning ƒ 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 *BASE BRMS GUI BRMS BRMS is included with Enterprise Edition for i550 and above

System i © 2007 IBM Corporation 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 - Media Management

System i © 2007 IBM Corporation 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.

System i © 2007 IBM Corporation 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

System i © 2007 IBM Corporation 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). Notes - HSM

Tape Library Support BRMS will.... Select Scratch Tapes Mount/Demount from drives Eject Tapes from Library after the save

System i © 2007 IBM Corporation Tape Library Support BRMS provides support for automated tape libraries such as:  9427 (8mm cartridges)  3490e model F (3490 cartridges)  3570 (3570 Magstar cartridges)  3575 (3570 Magstar cartridges)  3581 (LTO 7 cartridge)  3582 (LTO 2 device library)  3583 (LTO 6 device library)  3584 (LTO and 3592 cartridges)  3590 (3590 Magstar cartridges)  3494 (3490, 3590 and 3592 cartridges)

System i © 2007 IBM Corporation 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. Notes - Tape Library Support

System i © 2007 IBM Corporation Work with MediaRCHAS400 Position to............... ________Starting characters Type options, press Enter. 1=Add2=Change4=Remove5=Display6=Work with media set 7=Expire8=Move10=Reinitialize13=Display Contents15=Display Duplicates... VolumeCreationExpirationMoveMediaDup OptSerial ExpiredDateDateLocationDateClass Sts ___________ ___R000021/13/99*PERMCOMPRM*NONEFMT7GB ___R00067*YES1/23/992/20/99COMPRM*NONEFMT7GB ___Q00001*YES1/15/992/12/99TAPMLB012/12/99FMT3590 ___Q00002*YES1/29/992/29/99TAPMLB012/29/99FMT3590 ___Q00003+2/12/993/12/99OFFSITE2/12/99FMT3590 * ___Q00004+2/12/993/12/99OFFSITE2/12/99FMT3590 * ___Q00005+3/07/994/07/99COMPRM3/01/99FMT3590 1 ___________________________________________________________________More... F3=ExitF5=RefreshF11=Volume statisticsF12=CancelF23=More options Media Management

System i © 2007 IBM Corporation 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. Notes - Media Management

Media Management Media Report by Expiration Date "Scratch Listing" Total active......... : 20 Total expired........ : 7 Total volumes........ : 27 Media Expiration Report Volume Serial Expired Media Class Creation Date Expiration Date Storage Location System ID HIJ616 J001 J002 J003 M00901 M00902 M00903 Yes Yes Yes Yes Yes Yes Yes FMT3590 QIC120 QIC120 QIC120 FMT7GB FMT7GB FMT7GB 1/12/99 1/17/99 1/20/99 1/27/99 8/12/98 1/11/99 1/12/99 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

System i © 2007 IBM Corporation 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. Notes - Media Management

System i © 2007 IBM Corporation Media Movement Report All Volumes From Location.. : CMPROOMTo Location.. : OFFSITE Volume Creation Expiry Move Move Serial Date Date Policy Date SAM4203/1/993/28/99 OFFSITE 3/1/99 SAM4213/1/99 3/28/99OFFSITE 3/1/99 SAM4223/1/99 3/28/99 OFFSITE 3/1/99 SAM4233/1/99 3/28/99 OFFSITE 3/1/99 Total Volumes.......: 4 Media Management

System i © 2007 IBM Corporation 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/400 installed can then fax the list to the offsite storage vendor each day, thus giving him a picking list for the returned tapes. Notes - Media Management

System i © 2007 IBM Corporation Media Threshold Information Media class.......... : FMT2GB Volume CreationExpiry Read WriteException SerialDateDateLocationUses Errors ErrorsDetail ABC0012/1/992/28/99COMPRM246132*2 ABC0323/1/993/29/99OFFSITE113794*3 ABC1381/6/992/03/99COMPRM235958*2 *4 ABC1513/2/993/30/99OFFSITE252221*2 *2 = Media has exceeded use count *3 = Read error threshold has been exceeded *4 = Write error threshold has been exceeded. Media Management

System i © 2007 IBM Corporation 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. Notes - Media Management

System i © 2007 IBM Corporation 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... Full Incr Weekly Control Media Media Activity Opt Group Policy Policy SMTWTFS Text *BKUGRP *BKUPCY *BKUPCY *BKUPCY Entry created by BRM *SYSGRP SAVSYS SAVSYS *BKUPCY Entry created by BRM *SYSTEM *BKUPCY *BKUPCY *BKUPCY Entry created by BRM 2 TESTSAVE WEEKEND DAILY F i i i i i F Demo CTLG Backup Planning

System i © 2007 IBM Corporation 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 Notes - Backup Planning

System i © 2007 IBM Corporation Edit Backup Control Group Entries Group.......... : TESTSAVE Default activity.... F i i i i i F Text............ Demo Backup Control Group Weekly Retain Save Backup Activity Object While Seq ItemsSMTWTFS Detail Active 10*EXIT*DFTACT 20*SAVSECDTA*DFTACT*NO 30 LIB**DFTACT *ERR *NO 40 PAYLIBFFFFFFF *NO *LIB 50 CUSTLIB*DFTACT *MBR *SYNCLIB 60 EMPLIB*DFTACT *MBR *SYNCLIB Backup Planning

System i © 2007 IBM Corporation 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-level- detail (*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. Notes - Backup Planning

System i © 2007 IBM Corporation 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

System i © 2007 IBM Corporation 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)

System i © 2007 IBM Corporation 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.

System i © 2007 IBM Corporation 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.

System i © 2007 IBM Corporation Change Backup Control Group Attributes Group................ : TESTSAVE Media policy for full backups..... WEEKENDF4 Prompt Media policy for incremental backups........ DAILYF4 Prompt Backup devices............. MLB3570F4 Prompt Parallel Drive Resources: Minimum Resources.........*NONE Maximum Resources........ Sign off interactive users....... *BKUPCY Sign off limit............. *BKUPCY Incremental type............ *BKUPCY Text.................. Demo Backup Backup Planning

System i © 2007 IBM Corporation 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. Notes - Backup Planning

System i © 2007 IBM Corporation Start Backup using BRM (STRBKUBRM) Type choices, press Enter. Control group......... Testsave *BKUGRP, *SYSGRP, *SYSTEM... Schedule time......... *IMMED hhmm, *IMMED Submit to batch........ *YES *CONSOLE, *YES, *NO Starting sequence: Number............ *FIRST 1-9999, *FIRST Library........... *FIRST Name, *FIRST Append to media........ *CTLGRPATR *CTLGRPATR, *BKUPCY, *YES... Job description........ *USRPRF Name, *USRPRF Library........... Name, *LIBL, *CURLIB Job queue........... *JOBD Name, *JOBD Library........... Name, *LIBL, *CURLIB Activity............ *CTLGRPATR *CTLGRPATR, *FULL, *INCR Retention: Retention type........ *CTLGRPATR *CTLGRPATR, *PERM, *DAYS Retain media......... 35 1-9999 NEW AT V5R1 Running the Backup

System i © 2007 IBM Corporation Start Backup using BRM (STRBKUBRM) Type choices, press Enter. Control group......... TESTSAVE*BKUGRP, *SYSGRP Schedule time........... *IMMEDhhmm, *IMMED Submit to batch.......... *YES*CONSOLE, *YES, *NO Starting sequence: Number.............. *FIRST1-9999, *FIRST Library............. *FIRSTName, *FIRST Append to Media...... *NO*YES, *CTLGRPATR,... Running the Backup

System i © 2007 IBM Corporation 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). Notes - Running the Backup

System i © 2007 IBM Corporation 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. Running the Backup

System i © 2007 IBM Corporation 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. Notes - Running the Backup

System i © 2007 IBM Corporation Work with Media Information ITCBRMS1 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 Volume File Expiration Opt Item Date Time Type Serial Sequence Date QUSRRDARS 5/01/02 16:41:57 *FULL 103673 66 6/05/02 QUSRSYS 5/01/02 16:41:57 *FULL 103673 67 6/05/02 TEAM01AU 5/01/02 16:41:57 *FULL 103673 68 6/05/02 TEAM1USR 5/01/02 16:41:57 *FULL 103673 69 6/05/02 7 TEAM3USR 5/01/02 16:41:57 *FULL 103673 70 6/05/02 TONIB 5/01/02 16:41:57 *FULL 103673 71 6/05/02 T04USR2 5/01/02 16:41:57 *FULL 103673 72 6/05/02 USRPROD01 5/01/02 16:41:57 *FULL 103673 73 6/05/02 USRPROD01A 5/01/02 16:41:57 *FULL 103673 74 6/05/02 USRPROD02 5/01/02 16:41:57 *FULL 103673 75 6/05/02 More... Online Object Selection Screen from WRKMEDIBRM

System i © 2007 IBM Corporation 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 more- critical 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. Notes - Media Information Report

System i © 2007 IBM Corporation Work with Media Information RCHAS400 2=Change 4=Remove5=Display 6=Work with media 7=Restore 9=Work with saved objects SavedSaveVolumeFileExp OptItemDateTimeTypeSerialSeqDate 7 LIB12/01/9922:13*FULLVOLA13/15/99 7 LIB9992/15/9908:00*FULLVOL313/30/99 7 LIBXYZ2/15/9908:23*FULLVOL323/30/99 QUSRSYS1/30/9915:40*FULLWW04 14/11/99 QUSRBRM1/30/9915:48*QBRMWW04 24/11/99 F3=Exit F5=Refresh F12=Cancel Recovery

System i © 2007 IBM Corporation 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. Notes - Recovery

System i © 2007 IBM Corporation Display Recovery ItemsRCHAS400 Remaining items.... : 3 Remaining objects... : 126 Remaining size..... : 349 M96.8% Saved SaveVol File ExpirationObjects ItemDateTime TypeSerialSeq DateSaved LIB12/01/9922:13:26 *FULLVOLA1 3/15/9938 LIB9992/15/9908:00:01 *FULLVOL31 3/15/9929 LIBXYZ2/15/9908:23:00 *FULLVOL32 3/30/9959 Press ATTN to cancel recovery. Recovery

System i © 2007 IBM Corporation 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. Notes - Recovery

System i © 2007 IBM Corporation Total volumes needed for Recovery............: 6 Recovery Volume Summary Report * This report lists all the tapes you would need for a specific recovery Recovery Volume Serial ExpiredMedia Class Creation Date Expiry Date Location Date Storage Location System ID ABC071 ABC951 HIJ787 MNO843 NOP042 VOL006 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 3/02/99 3/04/99 2/28/99 3/05/99 *pending *pending MLB3494 MLB3494 BLDGXYZ BLDGXYZ OFFSITE OFFSITE PID400V PID400V PID400V

System i © 2007 IBM Corporation 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. Notes - Recovery

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. __ 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....... c

System i © 2007 IBM Corporation 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

System i © 2007 IBM Corporation 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 - continued

System i © 2007 IBM Corporation 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. Notes - Recovery

System i © 2007 IBM Corporation BRMS iSeries Navigator Interface  V5R1 Initial Implementation - Operations Navigator Plug-In –Created Separately –Looks and Behaves like Operations 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

System i © 2007 IBM Corporation Setting Up BRMS iSeries Navigator  Instructions to Install BRMS iSeries Navigator Plug-In in the iSeries Information Center BRMS Articles at: http://publib.boulder.ibm.com/pubs.html/as400/infocenter.htm http://publib.boulder.ibm.com/pubs.html/as400/infocenter.htm  Once BRMS iSeries Navigator Plug-In Installed, Current Backup Option in iSeries Navigator Replaced

System i © 2007 IBM Corporation V5R4 BRMS Enhancements  BRMS iSeries Navigator GUI Client –Archive: Policy, Lists, and Reports –Email Policy –Containers Support –User Filter of Logged Messages –User MLB (Media Library) support –ASP (Auxiliary Storage Pool) Classes  Backup Enhancements –Control Group ERP (Error Recovery Process) –New Missed Library/Object Control Group –Library Lists in Object Lists –*CUML - Force Full Reference Data Control –SAVSYSINF Support –Save/Restore of Spooled Files –*LINK – User Defined Omit QLNKOMT –STRBKUBRM –FLASHCOPY Support –Parallel Save/Restore Enhancements Including Support for IFS

System i © 2007 IBM Corporation V5R4 BRMS Enhancements  Recovery and Retrieval Enhancements –Restore/Retrieve from Any Volume –STRRCYBRM – Multiple Enhancements –RSTOBJBRM / RSTLIBBRM – Multiple Enhancements –Auto Create of Parent Directories  Devices/Media Management Enhancements –Virtual Tape Support –New 3592 WORM (Write Once Read Many) Device Support (Media Class Support) –Add Cartridge Type to Displays (WRKMLMBRM, ADDMLMBRM, GUI Client) –TSM (Tivoli Storage Manager) –DR450/550 Support (Data Retention) –New TSM Performance Report –DUPMEDBRM Multiple Enhancements

System i © 2007 IBM Corporation V5R4 BRMS Enhancements  Network Enhancements –Support Available/Unavailable Status (GUI) –Support User Control of Sending Messages –Restricted State Network Interface (GUI)  Archive –Support Save Media Information on STRARCBRM  Miscellaneous Enhancements –WRKOBJBRM - ASP Parameter

System i © 2007 IBM Corporation Notes: T The system that you select as the primary server will distribute these messages. If the primary server cannot complete the distribution, it sends the message to the secondary server for distribution. For example, you could select a local primary server and a remote secondary server. When the local system is in restricted state, BRMS sends the email through the remote secondary system. If a secondary server is not specified and the primary server is in restricted state, the message will be queued and distributed as soon as the BRMS network is restarted.

System i © 2007 IBM Corporation Notes: T When in restricted state, it may be necessary for BRMS to communicate with other systems in the network to get a volume for a save. Use this option to specify which network interfaces should be started when the current system is in restricted state. Only one network interface of each type can be started. Note: The target systems cannot be in a restricted state.

System i © 2007 IBM Corporation Notes: T Select error message IDs added to the BRMS log that you want also want distributed. An error message cannot be distributed if it is never logged by BRMS. Use the Browse button to view a list of unique messages that currently exist in the BRMS log. Use the Add and Remove buttons to update this list. Note: Messages should comply with message syntax rules. The first three characters of the message identifier must consist of an alphabetic character followed by two alphanumeric (alphabetic or decimal) characters. The last four characters of the message identifier must consist of the decimal numbers 0 through 9 or alphabetic characters A through F. All alphabetic characters in the message identifier must be uppercase.

System i © 2007 IBM Corporation Notes: T The feature to configure a user-defined Media Library Device through the GUI interface is new at V5R4. This is the same as using the green screen command WRKDEVBRM - Option 1, ADD

System i © 2007 IBM Corporation Notes: T Making changes to this will be reflected in the QLNKOMT link list (WRKLBRM in Green Screen). This link list allows users to omit files from the *LINK save item rather than creating a new link list. Only files or directories you want to omit should be included in this list.

System i © 2007 IBM Corporation Backup Item Exit Program New Control Support after each Entry (Check Message, Stop, Retry, Continue) Exit program  Change Backup Control Group Attributes Group................ : *BKUGRP Type information, press Enter. IPL after backup............ *BKUPCY *YES, *NO, *BKUPCY How to end............. *BKUPCY *CNTRLD, *IMMED, *BKUPCY Delay time, if *CNTRLD....... *BKUPCY Seconds, *NOLIMIT Restart after power down...... *BKUPCY *YES, *NO, *BKUPCY IPL source............. *BKUPCY *PANEL, A, B, *BKUPCY IPL restart type.......... *IPLA *FULL, *IPLA, *SYS... Save active wait time: Object locks............ 120 0-99999, *NOMAX Pending record changes....... 120 0-99999, *NOCMTBDY, *NOMAX Other pending changes........ 120 0-99999, *NOMAX Backup item exit program........ *BKUPCY Name, *NONE, *BKUPCY Exit program library........ Name Exit program format......... BKUI0100 Missed object policy.......... *BKUPCY Name, *NONE, *BKUPCY Clear missed objects......... *NO *NO, *YES

System i © 2007 IBM Corporation Notes: T Specifies the name of an exit program called following processing of one or more backup items in backup control groups. See ‘Backup Control Group Backup Item Exit Program’ in the Backup, Recovery and Media Services book, SC41-5345, for additional details about required parameters for the exit program. User could Check Message, Stop, Retry, Continue. Allows you to specify an exit program to run after an item has been saved or after a save has been attempted. You can use the exit program as part of your error recovery procedures to determine why the save of an item failed. Note: Backup control group processing will continue if the exit program does not exist, but exception BRM10A1 will be returned to the caller of the Start Backup using BRM (STRBKUBRM) command. Restriction: You must have *USE authority to the exit program. Possible values are: *BKUPCY-The value for backup item exit program from the Backup Policy is used for this backup control group. *NONE - Specifies no program is called during backup item processing. program-name - Specifies the name of the program called during backup item processing.

System i © 2007 IBM Corporation Missed Object Policy New Missed Object Policy BRMS Builds a Control Group with a List of Missed Objects. Control Group can be Run or Viewed. Can Use With Multiple Control Groups using Same Missed Object Control Group.  Change Backup Control Group Attributes Group................ : *BKUGRP Type information, press Enter. IPL after backup............ *BKUPCY *YES, *NO, *BKUPCY How to end............. *BKUPCY *CNTRLD, *IMMED, *BKUPCY Delay time, if *CNTRLD....... *BKUPCY Seconds, *NOLIMIT Restart after power down...... *BKUPCY *YES, *NO, *BKUPCY IPL source............. *BKUPCY *PANEL, A, B, *BKUPCY IPL restart type.......... *IPLA *FULL, *IPLA, *SYS... Save active wait time: Object locks............ 120 0-99999, *NOMAX Pending record changes....... 120 0-99999, *NOCMTBDY, *NOMAX Other pending changes........ 120 0-99999, *NOMAX Backup item exit program........ *BKUPCY Name, *NONE, *BKUPCY Exit program library........ Name Exit program format......... BKUI0100 Missed object policy.......... *BKUPCY Name, *NONE, *BKUPCY Clear missed objects......... *NO *NO, *YES

System i © 2007 IBM Corporation Notes: T Allows BRMS to build a control group with a list of missed objects. This control group can then be run later ….or reviewed. Can be used with multiple control groups using same missed objects control group. Specifies the name of backup control group and lists used to track missed objects during backup control group processing. If the backup control group or lists do not exist, these will be created using the same attributes as the current backup control group. Possible values: *BKUPCY The value for missed object policy from the Backup Policy is used for this backup control group. *NONE Specifies no tracking of missed objects occurs during backup control group processing. policy-name Specifies the name of the backup control group and lists to use for tracking missed objects during backup control group processing. Clear Missed Objects Specifies whether the missed object policy is cleared of previous missed objects when backup control group processing begins. The value of this prompt is ignored if the value for missed object policy is *NONE. Possible values are: *NO - Specifies the missed object policy is not cleared of previous missed objects before backup control group processing begins. *YES - Specifies the missed object policy is cleared of previous missed objects before backup control group processing begins. If using this with multiple control groups, the first control group should be *YES and the following control group will need to be *NO.

System i © 2007 IBM Corporation Force Full Backup Force Full Backup Days – Use to Ensure Full Backup Done After So Many Days Change Backup Policy MYSYS Type choices, press Enter. Media policy for full backups..... *SYSPCY Name, F4 for list Media policy for incremental backups......... *SYSPCY Name, F4 for list Backup devices............. *SYSPCY Name, F4 for list Default weekly activity........ FFFFFFF SMTWTFS(F/I) Incremental type............ *CUML *CUML, *INCR Force full backup days......... *NOMAX 0-365, *NOMAX Sign off interactive users....... *SYSPCY *YES, *NO, *SYSPCY Sign off limit............. *SYSPCY 0-999 minutes, *SYSPCY Save journaled objects when saving changed objects........ *NO *YES, *NO

System i © 2007 IBM Corporation New Save System Information (SAVSYSINF) Uses New SAVSYSINF i5/OS Command - Saves Subset of System Data and Objects Items saved include: System Reply List Service Attributes Environment Variables System Values Network Attributes PTFs Applied Since Last SAVSYS SAVSYSINF is not to be considered a replacement for the SAVSYS command and is not to be used for system upgrades or migrations. Create Backup Control Group Entries MYSYS Group.......... : SAVSISINF Default activity..... *BKUPCY Text........... *NONE Type information, press Enter. Auxiliary Weekly Retain Save SWA Backup List Storage Activity Object While Message Seq Items Type Pool Device SMTWTFS Detail Active Queue _10 *SAVSYSINF *DFTACT ______ ______ _______

System i © 2007 IBM Corporation Backup Object Lists Add Object List MYSYS Use......... : *BKU List name....... LIBLIST_________ Text......... List of libraries____________________ Type choices, press Enter. Seq Library Object Type Member ___ _______ ______ _____ ______ 10 LIB1 *ALL *ALL *ALL 20 LIB2 *ALL *ALL *ALL 30 LIB3 *ALL *ALL *ALL Bottom F3=Exit F4=Prompt F5=Refresh F12=Cancel Since LIB1, LIB2, and LIB3 Use *ALL, will Now be Treated like a Library List and Put on one SAVLIB Applies to the GUI client also 

System i © 2007 IBM Corporation Backup Spooled File Expiration Change Spooled File ListMYSYS Use......... : *BKU List name...... : QALLSPLF Text........ : All printed output Type choices, press Enter. Seq Expiration 0010 *SPLF_______ Bottom F3=Exit F5=Refresh F11=Selection view F12=Cancel New View on Spooled File List PF11 – Expiration. Show here  Need to Run DLTEXPSPFL After Save to Delete Spooled Files from System Values: *SPLF – No Change *EXPIRED – Set to Expired 1-366 - Set Expiration Number of Days from Save (Careful Not to Keep Moving Date Out! )

System i © 2007 IBM Corporation Notes: T Specifies the expiration date for saved spooled files. Run the Delete Expired Spooled files (DLTEXPSPLF) command after the save to delete expired spooled files from the system. Note: This attribute sets the expiration date of the saved spooled files on the system and has no affect on the retention of the saved spooled file information in BRMS history. Restrictions: Additional authorities are required to change the expiration of saved spooled files. The user is authorized to change the expiration of saved spooled files if any of the following conditions are met, otherwise, the expiration will remain unchanged. o The user owns the spooled file. o The user has spool control (*SPLCTL) special authority. o The user has job control (*JOBCTL) special authority, and the output queue on which the spooled file resides is specified as OPRCTL(*YES). o The user owns the output queue on which the spooled file resides, and the output queue is specified as AUTCHK(*OWNER). o The user has read, add, and delete authorities to the output queue on which the spooled file resides, and the output queue is specified as AUTCHK(*DTAAUT).

System i © 2007 IBM Corporation BRMS with FlashCopy  BRMS is Integrated with SAN for FlashCopy Solution  FlashCopy a Production System to “Backup” System in a Few Seconds (After an IPL)  BRMS will Backup Copied System as if it was the Production System Doing Backup  BRMS Networking Enhancement Stops other Systems Trying to Access BRMS Data from Production System until BRMS Media Information is Sent Back to Production System  For more Information see ITSO Redbook: iSeries & Total Storage: A Guide to Implementing External Disk on eServer™. SG24-7120 found at: http://www.redbooks.ibm.com/abstracts/sg247120.html

System i © 2007 IBM Corporation Parallel IFS Save Parallel Support for IFS (*LINK) and Can Now Mix Serial and Parallel Items in Same Control Group Also Applies to GUI Client  Work with Media Information MYSYS 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 ___ *LINK 1/19/06 11:46:04 *FULL 2 000DFC 24 2/23/06 ___ *LINK 1/19/06 11:46:21 *FULL 2 000FC9 24 2/23/06 ___ *LINK 1/19/06 11:50:04 *FULL 2 000DFC 25 2/23/06 ___ ISALIB 1/19/06 11:55:00 *FULL GEN001 37 2/23/06 ___ ITSCID07 1/19/06 11:55:00 *FULL GEN001 38 2/23/06 ___ QGPL 1/19/06 11:55:00 *FULL GEN001 5 2/23/06 ___ QSYS2 1/19/06 11:55:00 *FULL GEN001 4 2/23/06 ___ QUSRSYS 1/19/06 11:55:00 *FULL GEN001 6 2/23/06 ___ QFILE 1/19/06 11:55:21 *FILE GEN001 3 2/23/06 ___ ITSCID08 1/19/06 11:57:25 *FILE GEN001 + 39 2/23/06 Bottom F3=Exit F5=Refresh F11=Object detail F12=Cancel F23=More options

System i © 2007 IBM Corporation Notes: T IFS data can now be saved in parallel format (spread over multiple resources). Not all backup items can be saved using parallel resources. If a backup item does not support parallel save operations, the save will be performed as a serial save. Enhanced at V5R4, backup items capable of parallel saves can be mixed with backup items limited to serial saves within the same control group. See the specific Backup item help to determine whether the item supports the use of parallel resources. Note that there is also now a new field on the WRKMEDIBRM screen to indicate if the save was a parallel save or not.

System i © 2007 IBM Corporation Alternate Input Media Find Alternative Duplicate Volumes if Current Volume is Busy, etc.. Supported by: GUI Client Retrieval RSTxxxBRM V5R4M0 Change System Policy MYSYS Type choices, press Enter. End subsystems wait time........ 01200 1-99999 seconds,*IMMED End servers wait time......... 0 0-9999 seconds Controlling subsystem: Allow backups in batch........ *NO *NO, *YES Restricted state time limit..... *NOMAX 5-9999 minutes, *NOMAX Trace................. *NO *NO, *YES Allow alternate input media....... *YES *NO, *YES Bottom F3=Exit F4=Prompt F5=Refresh F12=Cancel

System i © 2007 IBM Corporation Use Duplicate Media and User Recovery Steps Support Library Omits  and Using Duplicate Media and Ability to Add own Recovery Steps (Input from a File you Create and Manage) Start Recovery using BRM (STRRCYBRM) Type choices, press Enter. Libraries to omit....... *DELETE Name, generic*, *DELETE... + for more values _________ Additional Parameters Volume location........ *ALL *ALL, *HOME, VAULT + for more values From system.......... *LCL Print system information.... *NO *NO, *YES Use duplicate media...... *NO *NO, *YES User recovery information... *NONE *NONE, *ADD Bottom F3=Exit F4=Prompt F5=Refresh F12=Cancel F13=How to use this display F24=More keys

System i © 2007 IBM Corporation Notes: T New capability to include user specified information in recovery report. File members are created automatically during product initialization. The contents of each user input member will print at the specified section of the recovery report. STRSEU or WRKOBJPDM commands may be use to populate/change the contents of the various members.

System i © 2007 IBM Corporation STRRCYBRM Selection Control and Concurrent Recovery Select Recovery Items MYSYS Select action..... : *ALL Select volume..... : Type options, press Enter. 1=Select 4=Remove 5=Display 7=Specify object Saved Save Save Save Parallel Volume File Expire Opt Item Date Time Type Devices Serial Sequence Date __ LIB01 1/21/06 23:54:02 *FULL 2 000F8C 6 2/20/06 __ LIB02 1/21/06 23:54:24 *FULL VRT004 1 2/20/06 __ LIB01 1/21/06 23:55:08 *FULL 2 000DB4 4 2/20/06 __ ASAPF 1/21/06 23:58:22 *FULL *SAVF 2/20/06 __ INVEN 1/21/06 23:58:53 *FULL *SAVF 2/20/06 __ TSSLIB 1/21/06 23:59:09 *FULL VRT004 2 2/20/06 __ OAKTEST 1/21/06 23:59:31 *FULL VRT004 21 2/20/06 __ TRACKER2 1/22/06 00:02:57 *FULL VRT004 9 2/21/06 F3=Exit F5=Refresh F9=Recovery defaults F11=Object View F12=Cancel F14=Submit to batch F16=Select Selection Control Within a Job using New Action/Volume Parameters Once Selected Another Job Will Not See Recovery Item STRRCYBRM Now Supports Concurrent Recovery With Another Job(s) (Using Same Recovery File!)

System i © 2007 IBM Corporation Notes: T Use to specify the action when using F16 to select saved items for recovery or to clear selected options. *ALL Select all saved items. *CLROPT Clear the Opt field for all entries. *VOLSET Select saved items on the set of volumes containing the volume specified on Select volume. *VOLUME Select saved items on the volume specified on Select volume.

System i © 2007 IBM Corporation Save Level Parameter on Restore New Save Date Parameter – Eliminates Confusion of Restoring by Save Level Restore Library using BRM (RSTLIBBRM) Type choices, press Enter. Library............ > LIB1 Name, *MEDINF + for more values __________ Device............. > TAP01 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........... > *SAVDATE 1-99, *CURRENT, *SAVDATE Save date........... __________ Date End of tape 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 Allow object differences.... *NONE *NONE, *ALL, *AUTL... + for more values Restore to library....... *SAVLIB Name, *SAVLIB More... F9=All parameters F11=Keywords F14=Command string F24=More keys

System i © 2007 IBM Corporation Create Parent Directories on Restore On IFS Restores Can Have the Directory Structure Automatically Created if it Does Not Exist Restore Command Defaults Type information, press Enter. Restore to library........ *SAVLIB Name, *SAVLIB Auxiliary storage pool...... *SAVASP Name, *SAVASP, 1-32... Document name generation..... *SAME *SAME, *NEW System resource management.... *ALL *ALL, *NONE, *HDW, *TRA Apply journaled changes: Restore journal receivers.... *YES *YES, *NO Apply option.......... *NONE *NONE, *APPLY, *REMOVE Ending date.......... *CURRENT Date, *CURRENT Ending time.......... *CURRENT Time, *CURRENT Lotus point-in-time: Ending date........... *CURRENT Date, *CURRENT, *FULL Ending time........... *CURRENT Time, *CURRENT, *FULL Create parent directories..... *NO *NO, *YES Parent directories owner.... *PARENT Name, *PARENT

System i © 2007 IBM Corporation WORM Media BRMS Treats all Media in this Class as WORM when Set to *YES - Can only Write Once – Can Append Until Full Some Tape Devices Ensure the WORM Feature Change Media Class Media class........... : VIRTTAP Type choices, press Enter. Density.............. *VRT256K F4 for list Media capacity.......... *DENSITY *DENSITY, Number nnnnn.nn Unit of measure......... 1=KB, 2=MB, 3=GB Mark for label print....... *NONE *NONE, *MOVE, *WRITE Label size............ 1 1=6 LPI, 2=8 LPI, 3=9 LPI Label output queue........ *SYSPCY Name, *SYSPCY, *PRTF Library............. Name, *LIBL Shared media........... *NO *YES, *NO Write once media......... *NO *YES, *NO Text............... TEST VIRT More... F3=Exit F4=Prompt F12=Cancel

System i © 2007 IBM Corporation Cartridge Type Display Work with Media Library Media MYSYS Media library...... : TAPMLB01 Position to........ Starting characters Type options, press Enter. 1=Add MLB media 2=Work with media 5=Initialize 6=Change category 7=Eject 8=Mount 9=Demount Media ---BRM Information--- Opt Volume Type Category Media Class Expired Status ___ 000B84 H *SHARE400 *NONE Available ___ 000C3C G *SHARE400 FMT3570E *YES Available ___ 000D63 G *NOSHARE FMT3570E *YES Available ___ 000FC9 G *NOSHARE FMT3570E *YES Available ___ 000FF8 G *NOSHARE FMT3570E *YES Available ___ 0003BC G *INSERT *NONE Inserted ___ 001019 G *INSERT FMT3570E *YES Inserted ___ 0784AE H *SHARE400 FMT3570 *YES Available More... F3=Exit F5=Refresh F9=System command F12=Cancel F13=Repeat Cartridge Type Column Added to WRKMLMBRM and ADDMLMBRM

System i © 2007 IBM Corporation Tivoli Storage Manager Device TSM Support Added: DR450/550 PTFs Back Through V5R1 via Data Area Change Net Device Net device........... : BRMSTSM Type changes, press Enter. Text............... TSM server Location............. TSMSVR Name, F4 for list TSM file space.......... *LCL Buffer size............ 512 *DEVTYPE, 1-512 KB Retention protection....... *NO *NO, *YES Internet address......... BRMSTSMSVR Internet port........... 11850 1-65534

System i © 2007 IBM Corporation Notes: In most cases, BRMS manages the retention and deletion of objects saved to TSM servers. When media retention expires, BRMS deletes the stored data from the TSM server and from the save history located in BRMS. If, however, the TSM administrator has enabled device retention protection in the TSM management class, then the TSM server restricts data from being deleted. If you are saving objects to a TSM server that uses retention protection, for example when using the IBM DR450/550, the media retention that you specify in BRMS must match the retention that is defined in the TSM management class. This is required so these objects can be deleted from BRMS history and the TSM server concurrently at expiration. Version V5R1 or later of the Tivoli Storage Manager Application Programming Interface (TSM APIs), program product 5733-197, is required to use retention protection. Before setting this retention protection for TSM devices on BRMS, verify whether the TSM server uses device retention protection with your TSM administrator.

System i © 2007 IBM Corporation TSM Performance Report Display Spooled File File..... : QP1ATSMRPT Control..... __________ Find...... _____________________________________________________________ *...+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....8....+... ------------------------------------------------------------------------------------- The following summarizes the BRMS save rate - how fast the blocks of save data can be passed to the TSM API. ------------------------------------------------------------------------------------- Entry 1 Job.............. : 054688 Job user............ : ITSCID07 Date.............. : 01/18/06 Time.............. : 06:27:08 Number of blocks........ : 1 Average block size....... : 36880 (bytes) Average block time....... :.091 (seconds) Fastest block time....... :.091 (seconds) Slowest block time....... :.091 (seconds) Save rate........... : 1.458 (billions of bytes each hour) Added TSM Performance Report Go BRMRPT Option 53

System i © 2007 IBM Corporation DUPMEDBRM Smart Append Change Media Policy Media policy.......... : VRTPCY Type choices, press Enter. Required volumes......... *NONE *NONE, 1-9999 Mark volumes for duplication... *NO *NO, *YES Mark history for duplication... *NO *NO, *YES Bottom DUPMEDBRM Smart Append Set in Media Policy to Just Mark History Items for Duplication Saved Item Centric versus Media Centric New *SCHHST on DUPMEDBRM Good When Appending Saves to Media

System i © 2007 IBM Corporation DUPMEDBRM Save Media Information DUPMEDBRM Now has Save Media Information Parameter (Also Added on STRARCBRM) Duplicate Media using BRM (DUPMEDBRM) Type choices, press Enter. From system.......... *LCL Additional Parameters To volume identifier...... *MOUNTED Character value, *MOUNTED + for more values Retain object detail...... *NO *NO, *YES Expiration date........ *MEDPCY Date, *MEDPCY, *PERM Move policy.......... *MEDPCY *MEDPCY, *NONE, AANANCY, DA... Media class.......... *MEDPCY *MEDPCY, *SYSPCY, AASLTST,... Location............ *MEDPCY *MEDPCY, *ANY, *HOME, HERBS... Secure volume......... *MEDPCY *MEDPCY, *NO, *YES Required volumes........ *MEDPCY 1-9999, *MEDPCY, *NONE Mark volumes for duplication.. *MEDPCY *MEDPCY, *NO, *YES Mark history for duplication.. *MEDPCY *MEDPCY, *NO, *YES Save media information..... *NONE *NONE, *BKUPCY, *LIB, *OBJ Bottom

System i © 2007 IBM Corporation BRMS Product STD (Standard)  All of Backup/Recovery and Media Management for a single system  Shared tape devices  Automated tape libraries  Backup to a TSM server  GUI including Functional Usage Model  Unlimited number of media volumes –Tier Priced

System i © 2007 IBM Corporation Notes: BRMS Product BRMS Standard The standard product will be processor based tier pricing. BRMS Standard offers many of the base functions needed by iSeries users to implement a fully automated, single system, backup, recovery and media management strategy using shared tape devices, automated tape libraries, TSM servers, unlimited number of media volumes, and functional authority. The standard product will not support archive, dynamic retrieval, automated migration operations, or shared media. BRMS Network Feature The BRMS Network feature enables a BRMS system to be interconnected via a network to other BRMS networked systems. A networked BRMS system can share the inventory and policies associated with media managed by any BRMS system. BRMS Advanced Functions Feature The BRMS Advanced Functions feature enables BRMS advanced function like archive with dynamic retrieval, and automated ASP object migration. For ease of use, menu and parameter options only show if the feature is installed. When BRMS Standard and the two features are installed, the system License Management function will determine if the user is licensed to use the function, then either execute or terminate the function based on the License Manager response. After installation, the end user will have uninhibited access to the available functions for a grace period of 70 days. A license key must be entered by the end user to enable the function beyond the grace period. The grace period is 70 days. A separate key is required for each of the four controlled functions. The BRMS product key is loaded into License Manager manually by the person installing the product. The key is provided to the user as part of the product license that is shipped with the product order. The key is shipped only if BRMS Standard product was ordered and billed. These keys are not required before or after install in order to use the product. The license keys required to unlock any unordered BRMS product or features will be available over the telephone.

System i © 2007 IBM Corporation Installing BRMS  Install BRMS57xx-BR1 *BASE 57xx-BR1 Option 1 Network Feature 57xx-BR1 Option 2 Advanced Functions Feature  ADDLICKEY57xx-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: –QBRMBRMS Program Objects –QUSRBRMBRMS User setup and BRMS DB –QMSE MSE Program Objects

System i © 2007 IBM Corporation Notes: Installing BRMS To install BRMS, do the following:  Ensure no other tape management system is installed on your system, since OS/400 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  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 Storage Locations Move Policies Control Groups Quarterly Lib1 Lib2 Daily Lib3 Lib4 Defaults System Policy Backup/Recovery/Archive Policy Tape Devices Media Classes Media Policies RetentionSavefiles

System i © 2007 IBM Corporation 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. Notes - BRMS Entities

System i © 2007 IBM Corporation 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

System i © 2007 IBM Corporation 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.

System i © 2007 IBM Corporation 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. Notes - Monitoring BRMS

System i © 2007 IBM Corporation 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. Monitoring BRMS

System i © 2007 IBM Corporation How much longer for the restore? Confidence in backup Avoid human error: writing over critical data Priority Applications up first Where are my tapes? Recovery steps outlined Backup & Recovery Media Services/400 1 12 2 3 4 5 6 7 8 9 10 11 Ability to save spooled files Summary

System i © 2007 IBM Corporation 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 Notes - Summary

System i © 2007 IBM Corporation Backup and Recovery; SC41-5304-08 (V5R4) Backup, Recovery and Media Services; SC41-5345-05 (V5R4) Backup, Recovery and Media Service for OS/400: A Practical Approach Redbook; SG24-4840 http://www.redbooks.ibm.com/abstracts/sg244840.html Virtual Tape Redbook; SQ24-7164 V5R4 iSeries Performance Capabilities Reference; SC41-0607-10 http://www-03.ibm.com/servers/eserver/iseries/perfmgmt/resource.html BRMS Web Page: http://www-03.ibm.com/servers/eserver/iseries/service/brms/ Reference Material

System i © 2007 IBM Corporation Trademarks The following are trademarks of the International Business Machines Corporation in the United States and/or other countries. For a complete list of IBM Trademarks, see www.ibm.com/legal/copytrade.shtml: AS/400, DBE, e-business logo, ESCO, eServer, FICON, IBM, IBM Logo, iSeries, MVS, OS/390, pSeries, RS/6000, S/30, VM/ESA, VSE/ESA, Websphere, xSeries, z/OS, zSeries, z/VM The following are trademarks or registered trademarks of other companies Lotus, Notes, and Domino are trademarks or registered trademarks of Lotus Development Corporation Java and all Java-related trademarks and logos are trademarks of Sun Microsystems, Inc., in the United States and other countries LINUX is a registered trademark of Linux Torvalds UNIX is a registered trademark of The Open Group in the United States and other countries. Microsoft, Windows and Windows NT are registered trademarks of Microsoft Corporation. SET and Secure Electronic Transaction are trademarks owned by SET Secure Electronic Transaction LLC. Intel is a registered trademark of Intel Corporation * All other products may be trademarks or registered trademarks of their respective companies. NOTES: Performance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput 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 improvements equivalent to the performance ratios stated here. IBM hardware products are manufactured from new parts, or new and serviceable used parts. Regardless, our warranty terms apply. All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics will vary depending on individual customer configurations and conditions. This publication was produced in the United States. IBM may not offer the products, services or features discussed in this document in other countries, and the information may be subject to change without notice. Consult your local IBM business contact for information on the product or services available in your area. All statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. Information about non-IBM products is obtained from the manufacturers of those products or their published announcements. IBM has not tested those products and cannot confirm the performance, compatibility, or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. Prices subject to change without notice. Contact your IBM representative or Business Partner for the most current pricing in your geography. References in this document to IBM products or services do not imply that IBM intends to make them available in every country. Any proposed use of claims in this presentation outside of the United States must be reviewed by local IBM country counsel prior to such use. The information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

V System i © 2007 IBM Corporation BRMS Overview – What Does It Do and How Do I Implement It? Debbie Saugen Senior Recovery Architect/Consultant.

Similar presentations

Presentation on theme: "V System i © 2007 IBM Corporation BRMS Overview – What Does It Do and How Do I Implement It? Debbie Saugen Senior Recovery Architect/Consultant."— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

V System i © 2007 IBM Corporation BRMS Overview – What Does It Do and How Do I Implement It? Debbie Saugen Senior Recovery Architect/Consultant.

Similar presentations

Presentation on theme: "V System i © 2007 IBM Corporation BRMS Overview – What Does It Do and How Do I Implement It? Debbie Saugen Senior Recovery Architect/Consultant."— Presentation transcript:

Similar presentations

About project

Feedback