Backup, Recovery, & Media Services (BRMS) V6R1 Enhancements

Backup, Recovery, & Media Services (BRMS) V6R1 Enhancements
Mervyn Venter

Course Description This course is designed to give you an overview of the enhancements to BRMS, Backup, Recovery, Media Services (5761BR1) licensed program for V6R1 i5/OS. The updates include virtually all native Save/Restore enhancements, with BRMS-unique enhancements also. The presentation will cover, Client Highlights, Backup and Restore enhancements as well as Media Management, Device, Network, and Installation improvements.

Audience The intended audience for this class are i5/OS Support Personnel with experience in supporting various save/restore, tape and BRMS functions.

Topics – changes/enhancements to:
Client Backup Recovery Media management Device Network Install

Client Enhancements

BRMS Client Enhancements
Web browser support via IBM Systems Director Navigator for i5/OS System i Navigator vs. IBM Systems Director Navigator for i5/OS Key GUI features (Some available in earlier releases) Externalize media polices DVD/Optical Libraries

System i Navigator vs. Systems Director Navigator
Almost functionally and visually identical IBM Systems Director Navigator for i5/OS is missing the scheduling function For backup, maintenance, printing reports, reclaim, etc. Included in future release

Web Browser support Browser support via IBM Systems Director Navigator for i5/OS. Access via browser address line: This capability is installed with the BRMS product. It is activated by a stop/start of the HTTP Admin Server. Screens very similar to System i Navigator. See following slides for sample comparisons.

System i Navigator

Example - Backup Control Groups
IBM Systems Director Navigator for i5/OS

Example - Backup Control Groups
System i Navigator

Example - Volumes IBM Systems Director Navigator for i5/OS

Example - Volumes System i Navigator

BRMS GUI – Key features Not necessarily new, but good to know…..

BRMS GUI Overview BRMS GUI is a System i5 Navigator Plug-in or Web Interface Easy to learn Contains most BRMS green screen functions GUI created/edited BRMS policies and objects are compatible with green screen Green screen created control groups, devices, volumes, media classes/pools can be edited via GUI or green screen Enhanced help text searching (via Eclipse Help) Searches all i5/OS help (not just BRMS)

BRMS GUI Overview For a smooth transition to the BRMS GUI, read the BRMS GUI FAQ on the BRMS web page www-03.ibm.com/servers/eserver/iseries/service/brms/pluginfaq.html Review this documentation for BRMS GUI Plug-in information (including install/remove) and gathering GUI Debug information

BRMS GUI Overview – GUI Plug-in View
Expanded Help options BRMS Plug-in folders 

GUI – Quickly Find What You Want to Restore
Query history by Date ranges Disk pools/Asps Save item type (library, directory, folder). Generics (mylib*, myIfsPath*) Specific item (myMail.nsf) … Selecting different saved item type changes the options below type. Above shows type of “Library, objects, or members” Once OK is clicked a list of all history items is shown that meet the criteria. User can select one or more items, right-click and select restore.

GUI – Easily Manage Your BRMS Network & Distribute Status

GUI – Easily Manage Your BRMS Network - Manage Systems
- You get to this screen by clicking the Manage Systems button shown on the previous slide.

GUI – Easily Distribute/E-mail BRMS Log Entries
Specify Message IDs to distribute  - See previous slide that shows network distribution/ setup.

GUI – Backup Control Group Properties – Special Lists
Select item and then click the “Edit” button. Special lists for some special values (e.g., on-line lotus, all ifs, etc.) allow user to add/omit items to/from the backup item

GUI – Backup Control Group Properties – Details…
1 2

GUI – Easily Create Custom Backup Control Group
– Select type of data

Create the Control Group with the Backup Control Group Wizard. Mention that New Archive Control Group Wizard is very similar. It is easy to create a custom backup Control Group and select the desired items to backup. These screen shots are for custom user data selection. Advanced backup options (save while active, asps, etc…) can be changed via Backup/Archive Control Group Properties after the Control Group is created.

– Select Item Type to add (or browse, shown here), select specific items and/or define lists

GUI – Easily Run or Schedule Control Groups
Select the Control Group, right-click and then select “Run Now” or “Schedule…” Via System i Navigator only….Scheduling functions not available in IBM Systems Director Navigator for i5/OS.

GUI Enhancements at V6R1

Externalize Media Policy
BRMS media policies are now externalized when using GUI rather than creating the Zxxxxxxxxxxx ones.

Externalize Media Policy – Davedom Example

DVD/Optical Library Support
BRMS now supports writing to physical and virtual optical devices.

Backup Enhancements

Backup Enhancements Software Data Encryption
Multiple Job Common Synchronization Point (Save While Active) IFS and QSYS Support Backup “Auditing/Performance” Report and Outfile Flashcopy® support Support of which type of Parallel to use on control group entry Journal Receiver Support SAVOBJBRM and Object List support of Generic Libraries ….enhancements continued next page NOTE: GUI Client supports these items also

Backup Enhancements-continued
*SYSDTA omit capability on the SAVSYSBRM command Add the reference date/time parameters on SAVOBJBRM Device, Media class, and move policy override for STRBKUBRM command Missing Objects support for IFS control group IFS backups will put more messages into the BRMS log Private authority support NOTE: GUI Client supports these items also

Software Data Encryption via BRMS

Software Data Encryption
Use the Cryptographic Services Key Management in GUI to create key store file Q1AKEYFILE in QUSRBRM with a unique file label BRMS provides you with the ability to encrypt your data to any tape device (including Virtual Tape. Encryption to an Optical device or TSM is not supported). This encryption solution is hardware independent, meaning no need for any encryption device. To use the encryption function, you need to have the BRMS Advanced feature (5761-BR1 Option 2) and Encrypted Backup Enablement (5761-SS1 Option 44) installed on the operating system. (Keyed, chargeable, products) Encryption setup is a billable service. BRMS will not manage the keys used for encryption. The user is still responsible for key management. BRMS simply provides the interface for the user to ask for encryption, specify the keys they want to use for the encryption, and what items they want encrypted. The key information is also saved by BRMS, so for restoring, BRMS knows what key information is needed to decrypt on the restore. For more information about key management, refer to Cryptographic services key management. To locate the topic in i5/OS Information Center, expand i5/OS information->Security->Cryptography. Save file encryption and optical media encryption are not supported. If you are using encrypted independent auxiliary storage pools (ASPs) and want to have the data remain encrypted when you save them to tapes, you need to use the software encryption function provided in the backup and archive control groups to encrypt the data; otherwise, the data will be decrypted when you save them to tapes.

Software Data Encryption-GUI
``

Create keystore file-GUI
The only valid keystore file is Q1AKEYFILE and it must exist in library QUSRBRM. (The user must create this file.) This ensures that when saving media information via your control group or the SAVMEDIBRM command, the key file is also saved. The Q1AKEYFILE keystore file must exist in library QUSRBRM prior to any save or restore operation that requires encryption or decryption. Key values in the keystore file are encrypted under a master key. When moving the Q1AKEYFILE keystore file to another system, you must ensure that the master key is set correctly. (Please see the section in this presentation on Recovery Enhancements for further information on moving a keystore file to another system for a remote restore.) To create this keystore file, refer to ‘Creating a new keystore file’. To locate the topic in i5/OS Information Center, expand i5/OS information->Security->Cryptography. The Keystore library parameter specifies the name of the library containing the keystore file. The only valid library for this parameter is QUSRBRM, any other library entered will cause an error. The Key record label parameter specifies a unique identifier of a key record in a keystore file. While BRMS supports only one keystore file, the user can create multiple labels within that keystore file. If the keys are lost, the data cannot be restored.

Create keystore file-CRTCKMKSF command
Type choices, press Enter. Keystore file Q1AKEYFILE Name Library QUSRBRM Name, *CURLIB Master key Authority *LIBCRTAUT Name, *LIBCRTAUT, *CHANGE... Text 'description' *BLANK Bottom F3=Exit F4=Prompt F5=Refresh F12=Cancel F13=How to use this display F24=More keys

Change or create media policy
Change Media Policy Media policy : ENCRYPT Type choices, press Enter. Encrypt Data *YES *NO, *YES Key store file Q1AKEYFILE Name Key store library QUSRBRM Name Key record label ENCRYPTION Bottom F3=Exit F5=Refresh F12=Cancel The keystore file is specified on the Media Policy. (Create or Change)

Work with Media Policies - GUI
The keystore file is specified on the Media Policy. (Create or Change)

Specify in control group
Edit Backup Control Group Entries CLIO Group : LIB001 Default activity *BKUPCY Text LIBRARY backup Type information, press Enter. Backup List Parallel Private Seq Items Type Type Authorities Encrypt 10 SHANES *DEFAULT *NO *MEDPCY 20 AJANISCH *DEFAULT *NO *NO Bottom F3=Exit F5=Refresh F11=Display main F12=Cancel Now that the media policy that supports encryption has been created, you can specify it on any of the BRMS save commands. This will then encrypt the items being saved. The SAVSAVFBRM and DUPMEDBRM also support this type of media policy. You will have the ability to encrypt save file data onto media, just by specifying a media policy that supports encryption. If you would rather not encrypt your data during your backup, but would like to encrypt the data when you duplicate it to another media, simply specify a media policy that supports encryption. In addition to all the ways you may encrypt data, further controls have also been provided in the backup and archive control groups that allow you to enable and disable encryption for each save item.

Specify in control group - GUI

WRKMEDIBRM Encryption History
Work with Media Information RCHASYUM 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 Encrypted Key Store Key Store Key Record Opt Item File Library Label TESTERDATA *NO TESTERJRN$ *NO KLD *YES Q1AKEYFILE QUSRBRM KLDLABEL TSTR2LIB *NO QDOC *NO *LINK *NO More... F3=Exit F5=Refresh F11=Volume identifier F12=Cancel F23=More options

Save History – Encryption Status - GUI

Recovery with Data Encryption
Restore Command Defaults Type information, press Enter. Restore to library *SAVLIB Name, *SAVLIB Auxiliary storage pool *SAVASP Name, *SAVASP, 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 Key store file *SAV Name, *SAV, *NONE Key store library *SAV Name, *SAV, *NONE More... F12=Cancel During a recovery, the user can select which keystore file to use. For a local restore, it is recommended the keystore file used for the save be selected. (*SAV, which will use what BRMS has stored with the save record in the QA1AHS file). For a remote recovery, a different keystore file/library may be selected. The section on Recovery Enhancements provides further information regarding BRMS recoveries with software data encryption.

Recovery - GUI Select Restore

Restore Wizard

Encryption caveats Encryption not allowed for:
*IBM, *SAVSYS, *SAVSECDTA, *SAVCFG Library names beginning with ‘Q’ – user or system Performance impact – see following slide Not supported on optical, virtual optical, save files, or TSM Error on Recovery Report - be aware Discussed in future section Most important: User MUST understand Cryptographic Services key management If not, risks losing data Encrypted data cannot be restored to a prior release Attention: It is extremely important that you understand Cryptographic services key management. Master keys, which are used to encrypt the key that BRMS uses, can have an effect on being able to recover your data. Refer to Cryptographic services key management to clearly understand the importance of these master keys as well as the required steps to ensure your data is truly encrypted and recoverable. To locate the topic in i5/OS Information Center, expand i5/OS information->Security->Cryptography. Encrypted data cannot be restored to a prior release.

BRMS-based encryption
Task Performance CPU Utilization Source file saves minimal impact approx double Usermix Saves approx 30% degradation approx double Largefile Saves approx 50% degradation approx 3-5* increase Source file restores minimal impact approx 40% increase Usermix restores approx 25% degradation approx 40% increase Largefile restores approx 4% degradation approx 5-7* increase This function is targeted at customers with a small amount of data to encrypt, or customers with a large backup window, since there is a performance impact. Customers who need encryption but require the fastest backup speeds should plan to use the encryption-capable tape hardware such as TS1120 and LTO4 instead since it has very minimal performance degradation. The User Mix data is contained in a single library and made up of a combination of source files, database files, programs, command objects, data areas, menus, query definitions, etc. Large File - The Large Database File workload is a single database file. Note: Performance tests were run on an i570 and an i570 MMA 4-way system with EXP24 disk and LTO3 tape

Multiple Job Common Synchronization Point

i5/OS support to save while active and synchronize library and Integrated File System (IFS) objects Single checkpoint to ensure library and IFS data saved in consistent state Using the MONSWABRM command and the Sync ID field in the Backup Control Group, you can utilize the multiple save synchronization feature. This feature allows you to synchronize libraries and/or integrated file system together to achieve one common checkpoint. The following slides provide an example on how you might use this function.

Edit Backup Control Group Entries CLIO Group : MSTRSWA Default activity *BKUPCY Text Master SWA control group Type information, press Enter. Backup Seq Items Exit command 10 *EXIT 20 *EXIT MONSWABRM LIB(ASN) CMD(STRSBSBRM) SYNCID(MULTSWAID) NUMSYNC(2) 30 *EXIT SBMJOB CMD(STRBKUBRM CTLGRP(SWA01)) 40 *EXIT SBMJOB CMD(STRBKUBRM CTLGRP(SWA02)) 50 *EXIT Bottom F3=Exit F5=Refresh F10=Change item F11=Advanced backup controls F12=Cancel In the example, the Master Backup Control Group starts the MONSWABRM command with the appropriately set parameters and then submits off two backup control groups. Note: the Save-while-Active jobs (SWA01 and SWA02 in this example) MUST be submitted.

Edit Backup Control Group Entries CLIO Group : CTLG01 Default activity *BKUPCY Text st SWA control group Type information, press Enter. Weekly Retain Save SWA Backup List ASP Activity Object While Message Sync Seq Items Type Device SMTWTFS Detail Active Queue ID 10 *EXIT *DFTACT 20 ASN *SYSBAS *DFTACT *ERR *SYNCLIB SWA MULTSWAID 30 DLACE *SYSBAS *DFTACT *ERR *SYNCLIB *LIB MULTSWAID 40 MPTESTCASE *SYSBAS *DFTACT *ERR *SYNCLIB *LIB MULTSWAID 50 *EXIT *DFTACT Bottom F3=Exit F5=Refresh F10=Change item F11=Display exits F12=Cancel F14=Display client omit status F24=More keys First control group…

Edit Backup Control Group Entries CLIO Group : CTLG02 Default activity *BKUPCY Text nd SWA control group Type information, press Enter. Weekly Retain Save SWA Backup List ASP Activity Object While Message Sync Seq Items Type Device SMTWTFS Detail Active Queue ID 10 *EXIT *DFTACT 20 IFSLIST *LNK *SYSBAS *DFTACT *NO *SYNC SWA MULTSWAID 30 *EXIT *DFTACT Bottom F3=Exit F5=Refresh F10=Change item F11=Display exits F12=Cancel F14=Display client omit status F24=More keys Second Control Group. Both control groups CTLG01 and CTLG02 have backup entries that are syncing to the Sync ID of MULTSWAID. CTLG01 will run a save of libraries ASN, DLACE and MPTESTCASE with one command and CTLG02 will run a save of integrated file system paths with one command. Since these two saves now meet the number of save operations specified on the Number of save operations parameter for the MONSWABRM command (specified in the control group MSTRSWA); a common checkpoint for both libraries and integrated file system objects will now be made. A checkpoint message will then be sent to the message queue SWA. Once the message is sent to the queue, BRMS will then run the command STRSBSBRM, which was specified on the Command parameter for MONSWABRM. Note: It is very important to get the number of save operations correct. If you specified three save operations, and only two were submitted, then the sync will wait for the third save to begin. If the third save never starts, then the sync attempt will fail after the specified value on the Start save wait time parameter for MONSWABRM command has been met.

GUI-Master Control Group

Secondary control group - Libraries - GUI

Secondary control group - IFS - GUI

Backup “Auditing/Performance” Report and Outfile

Backup “Auditing/Performance” Report and Outfile
Print Report using BRM (PRTRPTBRM) Type choices, press Enter. Report type *BKUSTAT *BKUSTAT Time period for report: Start time and date: Beginning time *AVAIL Time, *AVAIL Beginning date *BEGIN Date, *CURRENT, *BEGIN End time and date: Ending time *AVAIL Time, *AVAIL Ending date *END Date, *CURRENT, *END Auxiliary storage pool *ALL Name, 1-255, *ALL, *SYSTEM Library *ALL Name, *ALL, *ALLUSR Output *PRINT *PRINT, *OUTFILE Bottom F3=Exit F4=Prompt F5=Refresh F12=Cancel F13=How to use this display F24=More keys Command to generate the report is new, PRTRPTBRM. It may also be accessed via the BRMS menu system: GO BRMS #12 (Reports) #54 (Print Backup Statistics) This report provides summarized information about all objects that have been saved by BRMS within a specified period.

Report option – LIB(xxxxxx)
Display Spooled File File : QP1ABS Page/Line 55/36 Control P Columns Find * Start date and time : *BEGIN *AVAIL Ending date and time : *END *AVAIL Auxiliary storage pool : *ALL Library : QUSRBRM From System : X1521P3 Number of Number of Save Control Start Start End End Objects Objects Size Save Media Save Group Date Time Date Time Duration Saved Not saved (MB) GB/HR Class Volume Status LINKS /03/08 12:19:19 3/03/08 12:19:29 0:01: ULTRIUM AGK JOURNAL 1/01/40 0:00:00 1/01/40 0:00:00 0:00: FMT3592A2 *SAVF LINKS /03/08 10:14:37 3/03/08 10:14:46 0:01: ULTRIUM AGK LINKS /03/08 6:09:15 3/03/08 6:09:24 0:01: ULTRIUM AGK LINKS /03/08 6:32:46 3/03/08 6:32:55 0:01: ULTRIUM AGK More... F3=Exit F12=Cancel F19=Left F20=Right F24=More keys The user has the report option shown here, or may direct output to a file.

Report option – LIB(*ALLUSR)
Display Spooled File File : QP1ABS Page/Line 3/54 Control Columns Find * From System : RCHASYUM Number of Number of Save Control Start Start End End Objects Objects Size Save Media Save Group Date Time Date Time Duration Saved Not saved (MB) GB/HR Class Volume Status 5761BR1 V6R1M Backup Statistic Report /20/08 12:47: Page ALLUSR /09/08 12:32:23 3/09/08 12:32:26 0:01: ULTRIUM *SYSTEM 3/11/08 7:03:42 3/11/08 7:03:42 0:00: FMT3590H SAM444 Selection Criteria Start date and time : *BEGIN *AVAIL Ending date and time : *END *AVAIL Auxiliary storage pool : *ALL Library : #BLDSHIP ALLUSR /09/08 12:32:27 3/09/08 12:32:29 0:01: ULTRIUM *SYSTEM 3/11/08 7:03:43 3/11/08 7:03:44 0:01: FMT3590H SAM444 More... F3=Exit F12=Cancel F19=Left F20=Right F24=More keys

FlashCopy Support

Flashcopy Support (production backup)
V6R1M0 Change System Policy CLIO Type choices, press Enter. End subsystems wait time seconds,*IMMED End servers wait time seconds Controlling subsystem: Allow backups in batch *NO *NO, *YES Restricted state time limit *NOMAX minutes, *NOMAX Trace *NO *NO, *YES Allow alternate input media *YES *NO, *YES Volume prefix Prefix Enable FlashCopy *NO *NO, *YES BRMS submitted jobs: Job description Name, *USRPRF Library Name, *LIBL, *CURLIB Job queue Name, *JOBD Bottom F3=Exit F4=Prompt F5=Refresh F12=Cancel ESS FlashCopy creates a clone of the source system onto a second set of disk drives which are then attached and used by another system or LPAR partition. BRMS provides a mechanism to perform a backup on the second system such that it appears to have been done on the original system. In order to use BRMS to perform a backup of the production system on the clone system, the FlashCopy® function must be enabled on the production system. The BRMS implementation of the ESS FlashCopy provides a way to perform a backup on the clone system. The BRMS history information will appear as if the backup had been performed on the production system. Note: The BRMS Network feature (Option 1) is required to use this value. FlashCopy is not new to BRMS at V6R1. Capability existed at V5R3 and above. What is new is the implementation of manual, ‘old world’ commands into the System Policy and other BRMS functions.

Flashcopy Support (production backup)
Initialize BRMS (INZBRM) Type choices, press Enter. Option > *FLASHCOPY *DATA, *CHGSYSNAM, *DEVICE,... State *STRPRC *ENDBKU, *ENDPRC, *STRBKU... Bottom F3=Exit F4=Prompt F5=Refresh F12=Cancel F13=How to use this display F24=More keys Note: When the system is in FlashCopy mode, a BRMS synchronization job will not run on the production system. BRMS activity should not be performed on the production system until all steps in post FlashCopy steps are completed. Any update to the BRMS database on the production system via any BRMS activity such as save, restore, BRMS maintenance will be lost. When the system is in FlashCopy state, all BRMS incoming communication from the BRMS networked system will be blocked. BRMS backup information about the current system might be outdated when backup is being performed on the clone system. Chapter 14, ‘Networking with BRMS’ of the V6R1 BRMS manual contains more detail on when to issue the necessary commands.

Owning system-Global Policy Properties
After a FlashCopy switchover to a different system, the user should update the ‘BRMS system name’ field in the Global (System) Policy. The BRMS system name will be used as the owning system name for all future BRMS save operations. Changing the system name does not change existing BRMS save history.

Parallel Selection

Support parallel save type selection for Control Group entry
Create Backup Control Group Entries CLIO Group : PARALLEL Default activity *BKUPCY Text Parallel save options Type information, press Enter. Backup List Parallel Private Seq Items Type Type Authorities Encrypt 10 SHANES *PARALLEL *NO *NO 20 BLIB* *PARALLEL *NO *NO 30 ASN *DEFAULT *NO *NO Bottom F3=Exit F5=Refresh F11=Display main F12=Cancel It is now possible to select the type of parallel save to perform by specific entry in a control group. The possible values for Parallel Type are: *PARALLEL A parallel save format backup is being requested. This will use multiple drives and will create multiple media files that must be used together on the restore. BRMS will create the media definition on the recovery, but will require history information from the save to accomplish this. *SERIAL A serial save format backup is being requested. This will use multiple drives and create a media file per backup item. On restoring the data, a media definition is not required. *NONE A parallel backup is not being requested. *DEFAULT BRMS will decide the best Parallel Type to use on the backup item. If the backup item doesn't support parallel, then a non parallel backup will be requested.

Parallel - Edit Control Group
“Allow save item to be spread across devices” (*PARALLEL on green screen ) A parallel save format backup is being requested. This will use multiple drives and will create multiple media files that must be used together on the restore. BRMS will create the media definition on the recovery, but will require history information from the save to accomplish this. “Do not allow save item to be spread across devices” (*SERIAL) A serial save format backup is being requested. This will use multiple drives and create a media file per backup item. On restoring the data, a media definition is not required. “Not Parallel” (*NONE) A parallel backup is not being requested. “Let BRMS decide” (*DEFAULT) BRMS will decide the best Parallel Type to use on the backup item. If the backup item doesn't support parallel, then a non parallel backup will be requested.

Journal Receiver Support

Create Backup Control Group Entries CLIO Group : JRNRCV Default activity *BKUPCY Text *NONE Type information, press Enter. Weekly Retain Save SWA Backup List ASP Activity Object While Message Sync Seq Items Type Device SMTWTFS Detail Active Queue ID 10 *ALLDTCRCV *SYSBAS *DFTACT *YES *NO 20 *ALLCHGRCV *SYSBAS *DFTACT *YES *NO Bottom F3=Exit F5=Refresh F10=Change item F11=Display exits F12=Cancel F14=Display client omit status F24=More keys *ALLCHGRCV - Save all journal receivers in user libraries that do not start with the letter "Q" that have never been saved or that have changed since they were last saved. *ALLDTCRCV - Save all detached journal receivers in user libraries that do not start with the letter "Q" that have never been saved or that have changed since they were last saved. An enhancement is planned to allow users to create a list of libraries to save the journal receivers in them.

When adding items to save in the control group, the ‘Add Backup Items’ Wizard will now give the option to save previously unsaved journal receivers.

Generic Library Support

SAVOBJBRM and Object List Support of Generic Libraries
Add Object List CLIO Use : *BKU List name GENERICLIB Text Generic list of Libraries Type choices, press Enter. Seq Library Object Type Member 10 PAYROLL* DEDUCT *ALL *ALL Bottom F3=Exit F4=Prompt F5=Refresh F12=Cancel Feature also supported on the SAVOBJBRM command. Supported in backup and archive object lists.

Save list of generic libraries - GUI

*SYSDTA omit on SAVSYSBRM
Save System using BRM (SAVSYSBRM) Type choices, press Enter. Device DEV + for more values Media policy MEDPCY Data compression DTACPR *DEV Data compaction COMPACT *DEV Control group CTLGRP *NONE End of media option ENDOPT *REWIND Use optimum block size USEOPTBLK *BKUPCY Omit OMIT *SYSDTA Clear CLEAR *NONE Start controlling subsystem . . STRCTLSBS *YES Expiration date EXPDATE *MEDPCY Move policy MOVPCY *MEDPCY Media class MEDCLS *MEDPCY Location LOC *MEDPCY More... F3=Exit F4=Prompt F5=Refresh F12=Cancel F13=How to use this display F24=More keys *SYSDTA The Licensed Internal Code and the QSYS library are to be omitted for this system save operation. This feature is not available via either GUI interface. This capability was added to enable a functional SAVSECDTA and SAVCFG via BRMS.

SAVOBJBRM – REFDATE/REFTIME
Save Object using BRM (SAVOBJBRM) Type choices, press Enter. Data compaction COMPACT *DEV Save contents of save files . . SAVFDTA *YES Spooled file data SPLFDTA *NONE Type of save SAVTYPE > *FULL Reference date REFDATE *REF Reference time REFTIME *REF Journaled objects OBJJRN *NO Objects to omit: OMITOBJ Object *NONE Library *ALL Object type *ALL + for more values Auxiliary storage pool ASPDEV *SYSBAS Expiration date EXPDATE *MEDPCY Move policy MOVPCY *MEDPCY Media class MEDCLS *MEDPCY More... F3=Exit F4=Prompt F5=Refresh F12=Cancel F13=How to use this display F24=More keys Added the reference date/time parameters on SAVOBJBRM

New overrides on STRBKUBRM
Start Backup using BRM (STRBKUBRM) Type choices, press Enter. Device *CTLGRPATR Name, *CTLGRPATR, *MEDCLS + for more values Parallel device resources: Minimum resources *CTLGRPATR , *CTLGRPATR, *NONE... Maximum resources *MIN , *MIN, *AVAIL Media class *CTLGRPATR *CTLGRPATR, *SYSPCY, MLR3, ... Move policy *CTLGRPATR *CTLGRPATR, *NONE, OFFSITE Omits *PROCESS *PROCESS, *IGNORE Bottom F3=Exit F4=Prompt F5=Refresh F12=Cancel F13=How to use this display F24=More keys Messages pending on other displays. STRBKUBRM now allows for overrides on the DEV, MEDCLS, PRLRSC and MOVPCY paramters.

Run Backup Control Group overrides - GUI
User can override Move policy Media pool (media class in green screen) Parallel device resources

Missing Objects support for IFS control group
Edit Backup Control Group Entries Y0446P4 Group : MISSINGCG Default activity *BKUPCY Text *NONE Type information, press Enter. Weekly Retain Save SWA Backup List ASP Activity Object While Message Sync Seq Items Type Device SMTWTFS Detail Active Queue ID 10 *EXIT *DFTACT 20 Z *LNK *ALLAVL FFFFFFF *YES *NO 30 *EXIT *DFTACT Bottom F3=Exit F5=Refresh F10=Change item F11=Display exits F12=Cancel F14=Display client omit status F24=More keys The implementation of missing directory objects is similar to what was done for missing objects at V5R4.

Missing Objects support for IFS control group
Display Link List (DSPLNKLBRM) Type choices, press Enter. List > Z Character value Objects: Name > '''/fist/glink.o''' Include or omit > *INCLUDE *INCLUDE, *OMIT Name > '''/fist/glink64.o''' Directory subtree *ALL *ALL, *DIR, *NONE, *OBJ Text > 'Entry created by BRM configuration' Bottom F3=Exit F4=Prompt F5=Refresh F12=Cancel F13=How to use this display F24=More keys This is the list created for the customer

Private Authorities Support
Edit Backup Control Group Entries CLIO Group : LIB001 Default activity *BKUPCY Text LIBRARY backup Type information, press Enter. Backup List Parallel Private Seq Items Type Type Authorities Encrypt 10 *EXIT 20 LIB *OBJ *DEFAULT *NO *NO 30 SHANES *DEFAULT *YES *NO 40 AJANISCH *DEFAULT *NO *NO 50 *EXIT Bottom F3=Exit F5=Refresh F11=Display main F12=Cancel Note: Also supported on IFS lists and SAVxxx/RSTxxxBRM commands i5/OS support to allow private authorities to be saved/restored along with the objects Private authorities must be SAVED in order to be RESTORED. NOT intended for full system backup/recovery Existing full system backup / recovery process unchanged Slower if saving/restoring authorities Intended more for migrating a set of objects Authority required *SAVSYS or *ALLOBJ to save *ALLOBJ to restore

Private Authorities Support - SAVOBJBRM
Save Object using BRM (SAVOBJBRM) Type choices, press Enter. Save active wait time: SAVACTWAIT Object locks Pending record changes *LOCKWAIT Other pending changes *LOCKWAIT Save active message queue SAVACTMSGQ *NONE Library *LIBL Control group CTLGRP *NONE End of media option ENDOPT *REWIND Use optimum block size USEOPTBLK *BKUPCY Sequence number SEQNBR *END Target release TGTRLS *CURRENT Clear CLEAR *NONE Object pre-check PRECHK *NO Save access paths ACCPTH *SYSVAL Private authorities PVTAUT *NO Data compression DTACPR *DEV More... F3=Exit F4=Prompt F5=Refresh F12=Cancel F13=How to use this display F24=More keys Messages pending on other displays.

Private authorities – Control Group Properties

Better IFS messages in the BRMS Log
Display BRM Log Information CLIO 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 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 More... Press Enter to continue. F3=Exit F4=Message details F5=Refresh F11=Alternate view F12=Cancel F17=Top F18=Bottom These improvements to the BRMS log have been PTFed back to V5R3 and V5R4. (APAR SE28271)

Better IFS messages in the BRMS Log

Recovery Enhancements

Recovery Enhancements Highlights
Logical/Physical file restore order independence Private authority support Priority sequencing of saved items for STRRCYBRM STRRCYBRM Report Enhancements Optical Encryption Location omit Use of Date/Time on RSTxxxBRM commands Remote Recovery with Encryption

Logical/Physical file restore order independence
Additional Message Information Message ID : CPC371C Severity : 00 Message type : Completion Date sent : 01/06/ 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. Bottom Press Enter to continue. F3=Exit F6=Print F9=Display message details F12=Cancel F21=Select assistance level For logical and physical files, BRMS uses a BRMS defined ID of Q1ARSTID that is used for the parameter Defer ID (DFRID) on RSTLIB and RSTOBJ commands. This will automatically handle the dependencies on a specific restore order for these files.

Private Authority Support
Restore Command Defaults Type information, press Enter. Restore private authorities *NO, *YES Bottom F12=Cancel BRMS supports the saving/restoring of private authorities with the objects.

Restore Wizard – Private Authorities - GUI
This option is only visible if private authorities were SAVED with the object!

Priority sequencing during STRRCYBRM
Add Object List CLIO Use : *BKU List name RCYLIST Text Recovery Order Library List Type choices, press Enter. Seq Library Object Type Member 10 PAYROLL *ALL *FILE *ALL 20 PAYROLL *ALL *FILE *ALL 30 SHANES *ALL *FILE *ALL Bottom F3=Exit F4=Prompt F5=Refresh F12=Cancel There are times where the sequence of when you restore a specific library becomes important. Many times it is because of dependencies that objects have across libraries. To assist in these situations, BRMS has provided a way to prioritize these libraries as well as list them ahead in the recovery report, before all the other user libraries. To be able to use this useful function you will need to generate a list of these libraries (recovery order list) in the order that you wish them to be. Once that list has been made, use this list on the Start Recovery using BRMS (STRRCYBRM) command.

Use of Priority Sequencing of Saved Items in STRRCYBRM
Start Recovery using BRM (STRRCYBRM) Type choices, press Enter. Libraries to omit OMITLIB *DELETE + for more values Additional Parameters Volume locations to include . . LOC *ALL Volume locations to omit OMITLOC *NONE From system FROMSYS *LCL Print system information PRTSYSINF *NO Use duplicate media USEDUPMED *NO User recovery information USRRCYINF *NONE Recovery order list RCYORDLST RCYLIST Bottom F3=Exit F4=Prompt F5=Refresh F12=Cancel F13=How to use this display F24=More keys User creates a backup list (Use=*BKU) Specifies an object list that you want to use to determine the order of recovery. *NONE Indicates that you are not using an object list to determine the order of recovery. name Specify the name of the object list that contains libraries that will determine the recovery order. These libraries will be listed prior to any other user libraries that will be recovered.

Location omit for STRRCYBRM
Start Recovery using BRM (STRRCYBRM) Type choices, press Enter. Libraries to omit OMITLIB *DELETE + for more values Additional Parameters Volume locations to include . . LOC *ALL Volume locations to omit OMITLOC VAULT From system FROMSYS *LCL Print system information PRTSYSINF *NO Use duplicate media USEDUPMED *NO User recovery information USRRCYINF *NONE Recovery order list RCYORDLST XXXXXXX Bottom F3=Exit F4=Prompt F5=Refresh F12=Cancel F13=How to use this display F24=More keys Now have the ability to omit specific locations from a recovery.

STRRCYBRM Enhancements - Optical
* 5761BR1 V6R1M Recovery Volume Summary Report Y0446P /12/08 Volume Media Creation Expiration Location Storage Volume C Serial Status Class Date Date Date Location Slot Container S FIST01 *ACT VRTUDF /13/ /02/ *NONE *HOME *NONE FIST02 *ACT VRTUDF /13/ /02/ *NONE *HOME *NONE OPT004 *ACT FMTMLBUDF 10/22/ /29/ *NONE OPTMLB *NONE OPT005 *ACT FMTMLBUDF 10/22/ /31/ *NONE OPTMLB *NONE OPT006 *ACT FMTMLBUDF 10/27/ /31/ *NONE OPTMLB *NONE Total volumes needed for recovery : **************************************************************************************************** Volume Identifier Information Volume Volume Media Creation Expiration Storage Serial Identifier Status Class Date Date Location OPT004 FISTLER *ACT FMTMLBUDF 10/22/ /29/ OPTMLB01 OPT005 FISTLER *ACT FMTMLBUDF 10/22/ /31/ OPTMLB01 OPT006 STEVE5A *ACT FMTMLBUDF 10/27/ /31/ OPTMLB01 For Optical, the Recovery Volume Summary Report shows the true 32 character serial number of the optical media. The six character Volume Serial is the BRMS serial number only

STRRCYBRM Enhancements - Encryption
Display Spooled File File : QP1ARCY Page/Line 13/10 Control Columns Find Encrypted Saved Save ASP Save Save Not Sequence Control Volume Item Type Name Number Date Time Saved Saved Number Group Identifier Encrypted *LINK *FULL *SYSBAS /28/07 11:15:29 128, IFS GEN *YES ************************************************************************************************** STEP 018 : Recover Spooled Files for all ASPs Start date/time __________________ Stop date/time __________________ Duration _________________ If spooled files were saved, restore your saved spooled files. Attention If your backup strategy was to save spooled file data with saved output queues and you specified *NEW for Restore spooled file data recovery default, then you should not need to restore individual spooled files since the spooled files were restored with the output queues. To do so, type the following command and press "Enter". WRKSPLFBRM Use F16 to select all recovery items and press "Enter". Otherwise, select the saved items you need to recover and press "Enter". More... F3=Exit F12=Cancel F19=Left F20=Right F24=More keys

Encrypted Save Key Information
Display Spooled File File : QP1A2RCY Page/Line 1/2 Control Columns Find * 5761BR1 V6R1M Recovery Volume Summary Report CLIO /14/08 10:45: Page Volume Media Creation Expiration Location Storage Volume Container System Serial Status Class Date Date Date Location Slot Container Slot ID GEN001 *ACT VIRTUAL /28/ /01/ *NONE *HOME *NONE CLIO VOL001 *ACT VIRTUAL /28/ /01/ *NONE *HOME *NONE CLIO VOL002 *ACT VIRTUAL /28/ /01/ *NONE *HOME *NONE CLIO Total volumes needed for recovery : **************************************************************************************************** Encrypted Save Key Information Keystore Keystore Key File File Record Volume Library Name Label ************************************************************* DEF QUSRBRM Q1AKEYFILE ENCRYPTKEY1 DEF QUSRBRM Q1AKEYFILE ENCRYPTKEY2 DEF QUSRBRM Q1AKEYFILE ENCRYPTKEY3 * * * * * E N D O F L I S T I N G * * * * * Bottom F3=Exit F12=Cancel F19=Left F20=Right F24=More keys This is found at the end or the Recovery Report.

Correction: Use ADDMSTPART not LODMSTKEYP
Display Spooled File File : QP1ARCY Page/Line 10/46 Control Columns Find LODMSTKEYP * You must set your Save/Restore Master Key Value to recover your encrypted data. To do so, you must run the LODMSTKEYP command for every pass phrase used. Once the master keys are loaded, you must run the SETMSTKEY command. To load your master key: LODMSTKEYP MSTKEY(*SAVRST) PASSPHRASE('phrase-used') PASSLEN(*CALC) To set your master key: SETMSTKEY MSTKEY(*SAVRST) Use F16 to select all recovery items and press "Enter". After all saved items are recovered, continue with the step following 5761BR1 V6R1M Recovering the Entire System "Recover Directories and Files". ****************************************************************************** __ STEP 014 : Recover IBM Product Libraries More... F3=Exit F12=Cancel F19=Left F20=Right F24=More keys String found in position 52. Due to a late change, the documented LODMSTKEYP command noted on the Recovery Report has been changed to ADDMSTPART. Please be aware of the change. It is documented in an Knowledge Base (KB) Document Proper implementation: ADDMSTPART MSTKEY(*SAVRST) PASSPHRASE('phrase-used') PASSLEN(*CALC)

Remote Recoveries-Moving a keystore file for REMOTE RESTORE
1. Set up a temporary master key on both systems by loading and setting an unused master key with identical passphrases. System A: ADDMSTPART MSTKEY(3) PASSPHRASE('mytransferkey') SETMSTKEY MSTKEY(3) System B - same as above! Make sure the key being used is open to use. CHKMSTKVV MSTKEY(3) VERSION(*CURRENT) should get Version 1 of master key 3 If using BRMS for remote restore, you need to bring a translated file over from the remote file to be able to restore encrypted data. These instructions are not for a Disaster Recovery situation. This information will eventually be included in a Knowledge Base document. Here is how to set that up: Set up a temporary master key on both systems by loading and setting an unused master key with identical passphrases. Example: System A ADDMSTPART MSTKEY(3) PASSPHRASE('mytransferkey') SETMSTKEY MSTKEY(3) System B same as above! Make sure the key being used is open to use. CHKMSTKVV MSTKEY(3) VERSION(*CURRENT) should get Version 1 of master key 3 is not set.

Remote Recoveries-Moving a keystore file for REMOTE RECOVERIES
2. On the source system, create a duplicate of the keystore file (for example, using the CRTDUPOBJ CL command). System A: CRTDUPOBJ OBJ(Q1AKEYFILE) FROMLIB(QUSRBRM) OBJTYPE(*FILE QUSRBRM) TOLIB(QUSRBRM) NEWOBJ(BRMTRANSF) ASPDEV(*) TOASPDEV(*ASPDEV) DATA(*YES) CST(*YES) TRG(*YES) FILEID(*NO) 2. On the source system, create a duplicate of the keystore file (for example, using the CRTDUPOBJ CL command). Example: System A: CRTDUPOBJ OBJ(Q1AKEYFILE) FROMLIB(QUSRBRM) OBJTYPE(*FILE QUSRBRM) TOLIB(QUSRBRM) NEWOBJ(BRMTRANSF) ASPDEV(*) TOASPDEV(*ASPDEV) DATA(*YES) CST(*YES) TRG(*YES) FILEID(*NO)

3. Translate the duplicated keystore file to the temporary master key. System A : TRNCKMKSF KEYSTORE(QUSRBRM/BRMTRANSF) MSTKEY(3) 4. Move the keystore file to the target system. System A: PUTOBJ OBJ(BRMTRANSF) LIB(QUSRBRM) OBJTYPE(*FILE) RMTLOCS(System B) RMTUSER(KLD) RMTPWD(yourpw) MODE(*INT) 3. Translate the duplicated keystore file to the temporary master key. Example: System A TRNCKMKSF KEYSTORE(QUSRBRM/BRMTRANSF) MSTKEY(3) 4. Move the keystore file to the target system. Example: System A PUTOBJ OBJ(BRMTRANSF) LIB(QUSRBRM) OBJTYPE(*FILE) RMTLOCS(System B) RMTUSER(KLD) RMTPWD(yourpw) MODE(*INT)

5. Delete the translated keystore file from the source system. (You still have the original keystore file.) System A: DLTOBJ QUSRBRM/BRMTRANSF 6. On the target system, translate the keystore file to another master key. Use the master key that is used for QUSRBRM/Q1AKEYFILE. System B TRNCKMKSF KEYSTORE(QUSRBRM/BRMTRANSF) MSTKEY(1) 5. Delete the translated keystore file from the source system. (You still have the original keystore file.) Example: System A DLTOBJ QUSRBRM/BRMTRANSF 6. On the target system, translate the keystore file to another master key. Use the master key that is used for QUSRBRM/Q1AKEYFILE. Example: System B TRNCKMKSF KEYSTORE(QUSRBRM/BRMTRANSF) MSTKEY(1) 7. Clear the temporary master key on both systems. Example: System A and B CLRMSTKEY MSTKEY(3) VERSION(*CURRENT) 8. When restoring a saved item via STRRCYBRM/WRKMEDIBRM/WRKOBJBRM/WRKLNKBRM FROMSYS, change the command defaults (F9) for the Key store file and Key store library to QUSRBRM/BRMTRANSF

7. Clear the temporary master key on both systems. System A and B CLRMSTKEY MSTKEY(3) VERSION(*CURRENT) 8. When restoring a saved item via STRRCYBRM/WRKMEDIBRM/WRKOBJBRM/WRKLNKBRM FROMSYS, change the command defaults (F9) for the Key store file and Key store library to QUSRBRM/BRMTRANSF 7. Clear the temporary master key on both systems. Example: System A and B CLRMSTKEY MSTKEY(3) VERSION(*CURRENT) 8. When restoring a saved item via STRRCYBRM/WRKMEDIBRM/WRKOBJBRM/WRKLNKBRM FROMSYS, change the command defaults (F9) for the Key store file and Key store library to QUSRBRM/BRMTRANSF

Use of Date/Time on RSTxxxBRM commands
Restore Object using BRM (RSTOBJBRM) Type choices, press Enter. Object OBJ + for more values Library SAVLIB Device DEV Parallel device resources: PRLRSC Minimum resources *SAV Maximum resources *MIN Object type OBJTYPE *ALL Save level SAVLVL *CURRENT Save level time reference: SAVDATE Save date Save time *LATEST End of media option ENDOPT *REWIND Option OPTION *ALL More... F3=Exit F4=Prompt F5=Refresh F12=Cancel F13=How to use this display F24=More keys (Note: some had Date…Time added on all)

Media Management Enhancements

Media Management Highlights
Expired column changed to Status on WRKMEDBRM (*INZ (new), *ERR, *ACT, *EXP) New command to balance media in a network (STRBALBRM) Automated Duplication New DUPMEDBRM message to indicate what the output volumes were Move Media retention capability Movement/Container enhancements Virtual Tape to TSM Server (Future enhancement)

Expired Column Changed to Status on WRKMEDBRM
Work With Media System: CLIO 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 10=Reinitialize ... Volume Creation Expiration Move Media Dup Opt Serial Status Date Date Location Date Class Sts GEN *ACT 12/28/07 02/01/08 *HOME *NONE VIRTUAL VOL *ACT 12/28/07 02/01/08 *HOME *NONE VIRTUAL VOL *ERR 12/28/07 02/01/08 *HOME *NONE VIRTUAL VOL *INZ 12/28/07 12/29/07 *HOME *NONE VIRTUAL VOL *EXP 12/28/07 *NONE *HOME *NONE VIRTUAL Bottom Parameters or command: ===> F3=Exit F4=Prompt F5=Refresh F11=Volume system F12=Cancel F17=Top F18=Bottom F23=More options (C) COPYRIGHT IBM CORP. 1998, ALL RIGHTS RESERVED. The possible values are: *ACT (New at V6R1) The volume is active. *ERR The volume was flagged in error and can only be reset by removing the volume, then adding the volume back into the inventory. *EXP The volume is expired. *INZ (New at V6R1) The volume requires initialization before it can be used. To initialize a volume, use Option 10=Reinitialize. *UNR This is an unregistered pre-V4R4M0 volume. Run maintenance to clear this status.

Media Balancing

Media balancing (STRBALBRM)
System Priority Required Available Prod01 1 5 3 Prod02 2 4 Dev Media Class Media Location Media Balancing (Customer decides) This function gives you the ability to balance a number of scratch volumes owned by each system in the BRMS network. With the scratch volumes balanced, a restricted state save will be less likely to run out of scratch media, and the system will not need to remotely ask other systems for more media. It is recommended that you run this when there is no other BRMS activity going on. Allocate media depends on availability. If not able to allocate required media, message will be issued Priority Number Required

Media balancing (STRBALBRM) - how
List your systems in order of highest priority to lowest priority. Set priority STRBALBRM ACTION(*SET) MEDCLS(media-class) LOC(location) SYSNAME(system-name) MEDPTY(number) MEDREQ(number) Print and Review Media Balance Report STRBALBRM ACTION(*REPORT) MEDCLS(media-class) LOC(location) If necessary, Balance Media Review Media Balance Report To balance your scratch media follow these steps: List your systems in order of highest priority to lowest priority. Once you have established your hierarchy of systems, you must issue the following command to set the above priority: STRBALBRM ACTION(*SET) MEDCLS(media-class) LOC(location) SYSNAME(system-name) MEDPTY(number) MEDREQ(number) STRBALBRM ACTION(*SET) MEDCLS(FMT3590H) LOC(TAPMLB01) SYSNAME(PROD01) MEDPTY(1) MEDREQ(5) STRBALBRM ACTION(*SET) MEDCLS(FMT3590H) LOC(TAPMLB01) SYSNAME(PROD02) MEDPTY(2) MEDREQ(4) STRBALBRM ACTION(*SET) MEDCLS(FMT3590H) LOC(TAPMLB01) SYSNAME(DEV) MEDPTY(3) MEDREQ(2) Produce and evaluate the Media Balance report to ensure that your systems are setup correctly. To do so run the following command: STRBALBRM ACTION(*REPORT) MEDCLS(media-class) LOC(location) Using the same example sample from above, we would issue STRBALBRM ACTION(*REPORT) MEDCLS(FMT3590H)LOC(TAPMLB01). From the report, if the actual amount of media is not greater to or equal to the required amount, then you will need balance your media. To balance your media, you need to run the following command: STRBALBRM ACTION(*BALANCE) MEDCLS(media-class) LOC(location) Such as, STRBALBRM ACTION(*BALANCE) MEDCLS(FMT3590H) LOC(TAPMLB01) Repeat step 3.

Media Balancing Report-Initial
File : QP1AMBL Page/L Control Column Find 5761BR1 V6R1M Media Balancing Report /29/07 13:56:1 Selection Criteria Media Class : FMT3590H Location : TAPMLB01 System : *NETGRP Number of Number of System Network Media Media Media Media Name ID Class Location Priority Required Available Status PROD APPN FMT3590H TAPMLB Communicating PROD APPN FMT3590H TAPMLB Communicating DEV APPN FMT3590H TAPMLB Communicating * * * * * E N D O F L I S T I N G * * * * *

Media Balancing Report-After balancing
File : QP1AMBL Page/L Control Column Find 5761BR1 V6R1M Media Balancing Report /29/07 13:59:1 Selection Criteria Media Class : FMT3590H Location : TAPMLB01 System : *NETGRP Number of Number of System Network Media Media Media Media Name ID Class Location Priority Required Available Status PROD APPN FMT3590H TAPMLB Communicating PROD APPN FMT3590H TAPMLB Communicating DEV APPN FMT3590H TAPMLB Communicating * * * * * E N D O F L I S T I N G * * * * *

Media Balancing - GUI From the ‘Volumes’ folder, select ‘Manage Volume Balancing…’

Media Balancing - GUI From here the user can select the Volume Balance functions.

Automatic Duplication

Automatic Duplication in Media Policy
Change Media Policy Media policy : JAPMED Type choices, press Enter. Automatic duplication: From devices *NONE Name, *NONE, *SAME, *MEDCLS.. From device end option *REWIND *REWIND, *LEAVE, *UNLOAD To devices *SAME Name, *SAME, *MEDCLS, F4 To device end option *REWIND *REWIND, *LEAVE, *UNLOAD To media policy *SAME *SAME, *SYSPCY, F4 Save media information *SAME *SAME, *BKUPCY, *LIB, *OBJ *NONE More F3=Exit F4=Prompt F5=Refresh F12=Cancel Automatic duplication can be used to duplicate data after it has been saved. In a control group backup, this will happen at each save done within the control group, so multiple duplications will occur in asynchronous jobs. The joblog from the backup will contain messages indicating which jobs are performing the duplications. The backup will finish and return control to the user before the duplications have completed. Each duplication job will issue completion and error messages to the BRMS log. Use DSPLOGBRM to view these messages. This new feature is most ideal for ensuring your virtual media are being duplicated off to physical media.

Where do Automatic Duplication Jobs Run?
V6R1M Change System Policy Z1014P28 Type choices, press Enter. End subsystems wait time seconds,*IMMED End servers wait time seconds Controlling subsystem: Allow backups in batch *YES *NO, *YES Restricted state time limit minutes, *NOMAX Trace *YES *NO, *YES Allow alternate input media *YES *NO, *YES Volume prefix Prefix Enable FlashCopy *NO *NO, *YES BRMS submitted jobs: Job description *USRPRF Name, *USRPRF Library *LIBL Name, *LIBL, *CURLIB Job queue *JOBD Name, *JOBD Bottom F3=Exit F4=Prompt F5=Refresh F12=Cancel The duplications will be submitted to the BRMS submitted job's description and queue specified in the BRMS System Policy. If a parallel save is performed, multiple duplication jobs will be started. There will be one duplication per media set created. If there are insufficient devices available, the duplications will pause and wait for the devices to become available. This can also be controlled by configuring the maximum number of jobs running in the job queue. If the system is in restricted state, the jobs will wait in the job queue. Once the system is active again, the duplication jobs will start.

Additional Message Information
DUPMEDBRM Message Additional Message Information Message ID : BRM Severity : 10 Message type : Information Date sent : 01/06/ Time sent : 12:43:14 Message : Data has been moved from the source to destination media. Cause : Data has been moved from the source input media VRT001 to output media VOL037. Bottom Press Enter to continue. F3=Exit F6=Print F9=Display message details F12=Cancel F21=Select assistance level

Move Media Retention Capability
Type storage location or container to receive volumes. Storage location *SAME *SAME, F4 for list Container *SAME *SAME, F4 for list Exempt from movement *SAME, Volume : Exempt from movement - Help : Opt Serial : : 8 GEN : 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 : : indicates that the media is not exempt from : : movement : : : : Bottom : : F2=Extended help F10=Move to top F11=Search Index : : F12=Cancel F20=Enlarge F24=More keys : F12=Cancel : : Already at to : : Occasionally there are times where you might require a volume to be brought back on site for restore purposes or for many other reasons. However, once that volume is brought back on site, and movement has been ran, the volume moves back to the location directed by the move policy associated with it. This feature allows you to exempt the volume from the move policy for a specified amount of time. To access the above screen…. WRKMEDBRM Opt, 8 on an active volume

Media Movement Exemption
Display Media Attributes Volume serial : VOL001 Media type : *VT Image catalog : CLG02 Media class : VIRTUAL Expiration date : 02/01/08 Previous location : *NONE Previous slot number : 0 Current location : *HOME Last moved date : *NONE Scheduled location : *NONE Scheduled move date : *NONE Exempt from move until date : 04/13/08 Container ID : *NONE Move policy : *NONE Creation date : 12/28/07 Secure volume : *NO Beginning volume : VOL001 More... Press Enter to continue. F12=Cancel Another method of determining if a volume is exempt from movement for a certain timeframe is to do WRKMEDBRM, then option 5 (Display) on the volume in question.

Movement/Container Enhancements – Auto Open/Close
Change Move Policy CLIO 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 Location Duration Container Action 10 OLDVAULT *CLOSE 20 VAULT *EXP *OPEN Bottom F3=Exit F4=Prompt F5=Refresh F12=Cancel You can *OPEN or *CLOSE your containers through movement by setting the Container Action column for each location. Note: Container Action field is editable only if ‘Use Container’ is *YES.

Future enhancement – no time estimate yet!
Create Media Policy Type choices, press Enter. Encrypt Data *NO *NO, *YES TSM management class STANDARD TSM transfer size TSM transfer ASP *SYSTEM Name, *SYSTEM, 1-32 TSM security: TSM node APPN.CLIO TSM password *NONE Bottom F3=Exit F5=Refresh F12=Cancel New Fields show, but are disabled A future enhancement will allow for using virtual tapes to backup to a TSM server. Please be aware that the MRI changes have been made, and the user may see these two new parameters, which are disabled. NOTE: There is no time estimate on the delivery of this function.

Device Highlights Network Highlights Install Highlight
DVD/Optical library support Performance improvements for TSM backups. (PTF’ing back – no slide) Tape Library 35xx enhancement (old library manager on 3494) New media library status tool Network Highlights Support to stop SNA attempt if TCP/IP fails Enable IPv6 support (no slide) VIPA (Virtual IP Address) restricted state support Install Highlight BRMS print files will keep attributes from previous release on upgrade

DVD/Optical Support

DVD/Optical Device Support - WRKDEVBRM
Work with Devices Y0446P4 Position to Starting characters Type options, press Enter. 1=Add 2=Change 4=Remove 5=Display 8=Work with status Opt Device Category Type/Model Text FISTOPT *VRTOPT 632B/ Entry created by BRM configuration LANTAP *TAP / Entry created by BRM configuration OPTMLB01 *OPTMLB 399F/ Entry created by BRM configuration OPTVRT01 *VRTOPT 632B/ Entry created by BRM configuration OPT *OPT / Entry created by BRM configuration TAP *TAP / Entry created by BRM configuration VIRTUALOPT *VRTOPT 632B/ Entry created by BRM configuration Bottom F3=Exit F5=Refresh F12=Cancel

DVD/Optical Device Support - WRKMLBBRM
Work with Media Libraries Y0446P4 Position to Starting characters Type options, press Enter. 2=Change 3=Hold 5=Display 6=Release 8=Work with MLB media 9=Display MLB media 10=Display MLB status 11=Add MLB media Opt Library Status Location Text OPTMLB01 Released OPTMLB01 Entry created by BRM configuration Bottom F3=Exit F5=Refresh F9=System command F12=Cancel

DVD/Optical Device Support - WRKMEDBRM
Work With Media System: Y0446P4 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 10=Reinitialize ... Volume Volume Optical Opt Serial Identifier Media Type KMA LPP LN LN4121 LN LN5795 OPT FISTOPT01 OPT FISTOPT *DVD-RAM OPT FISTOPT03 OPT FISTLER01 More... Parameters or command: ===> F3=Exit F4=Prompt F5=Refresh F11=Volume information F12=Cancel F17=Top F18=Bottom F23=More options

DVD/Optical Device Support - ADDMEDBRM
Add Media to BRM (ADDMEDBRM) Type choices, press Enter. Volume identifier > OPT Media class > FISTOPTUDF BOPTHPOFS, BOPTUDF, DAVE, F... Number to add Initialize media *NO *NO, *YES Expiration date *NONE Date, *PERM, *NONE Creation date *CURRENT Date, *CURRENT System *LCL Text *NONE Image catalog *NONE Name, *NONE Bottom F3=Exit F4=Prompt F5=Refresh F10=Additional parameters F12=Cancel F13=How to use this display F24=More keys Add Media to BRM (ADDMEDBRM) command - The Volume identifier (VOL) parameter was changed from a 6 character parameter to a 32 character parameter. This is to support the new Optical media that can have up to 32 character volume identifiers. If the volume identifier exceeds 6 characters, BRMS will use a Volume Prefix found in the System Policy to generate a unique 6 character volume serial that will map to the 32 character volume identifier. Please see following screens for an example of adding an optical volume to the BRMS media inventory.

Volume prefix must be specified
Additional Message Information Message ID : BRM Severity : 30 Message type : Escape Date sent : 03/07/ Time sent : 10:58:16 Message : Volume OPT not added. Cause : A volume identifier greater than six characters was entered and the Volume prefix in the System Policy was not set or a unique six character name could not be determined using the current Volume prefix. Recovery : Update the Volume prefix in the System Policy to a different prefix. Bottom Press Enter to continue. F3=Exit F6=Print F9=Display message details F10=Display messages in job log F12=Cancel F21=Select assistance level

V6R1M0 Change System Policy CTFIB8
Type choices, press Enter. End subsystems wait time seconds,*IMMED End servers wait time seconds Controlling subsystem: Allow backups in batch *NO *NO, *YES Restricted state time limit *NOMAX minutes, *NOMAX Trace *NO *NO, *YES Allow alternate input media *YES *NO, *YES Volume prefix OP Prefix Enable FlashCopy *NO *NO, *YES BRMS submitted jobs: Job description Name, *USRPRF Library Name, *LIBL, *CURLIB Job queue Name, *JOBD Bottom F3=Exit F4=Prompt F5=Refresh F12=Cancel Device OPT01 is not allowed. Specifies the volume prefix to use when media is added to BRMS that has a volume identifier greater than six characters. BRMS will use this prefix to generate a six character unique volume identifier. For instance, specifying an "V", added volume names would be increased by 1, such as V00001, V00002, V00003 and so on to generate a unique six character name.

ADDMEDBRM now successful….
Additional Message Information Message ID : BRM Severity : 00 Message type : Completion Date sent : 03/07/ Time sent : 11:10:50 Message : Volume OP0001 with volume identifier OPT and media class FISTOPTUDF added to the media inventory. Bottom Press Enter to continue. F3=Exit F6=Print F9=Display message details F10=Display messages in job log F12=Cancel F21=Select assistance level

WRKMEDBRM WRKMEDBRM shows the volume mapping. Work With Media
System: CTFIB8 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 10=Reinitialize ... Volume Volume Optical Opt Serial Identifier Media Type OP OPT Bottom Parameters or command: ===> F3=Exit F4=Prompt F5=Refresh F11=Volume information F12=Cancel F17=Top F18=Bottom F23=More options WRKMEDBRM shows the volume mapping.

DVD/Optical media in Optical Tape Library-WRKMLMBRM
Work with Media Library Media Y0446P4 Media library : OPTMLB01 Position to Type options, press Enter. 1=Add MLB media =Work with media 5=Initialize Volume Optical Opt Volume Identifier Serial Volume Type Media Type ABSW1A *NONE *PRIMARY *WORM ASCIIVOL *NONE *PRIMARY *ERASE DUPOPT-4XCCW-TO-4XCCW *NONE *PRIMARY *WORM DUPOPT-4XWORM-TO-4XCCW *NONE *PRIMARY *WORM FISTLER OPT004 *PRIMARY *ERASE FISTLER OPT005 *PRIMARY *ERASE FULL *NONE *PRIMARY *WORM FULL *NONE *PRIMARY *WORM More... F3=Exit F5=Refresh F9=System command F11=BRMS information F12=Cancel F13=Repeat

Advanced Features 5761BR1 option 2

Volume Status - WRKTAPCTG
Work with Tape Cartridges RCHASYUM 03/20/08 12:59:56 Library Device: NET3592 Type options, press Enter. 1=Add 2=Change 4=Remove 5=Display 6=Print ... Cartridge Volume Media Opt ID ID Type Status HPK *UNKNOWN JA Available HPK *UNKNOWN JA Ejected HPK *UNKNOWN JA Error HPK *UNKNOWN JA Available HPK *UNKNOWN JA Available HPK *UNKNOWN JA Ejected JRX JRX JR Available More... Parameters or command ===> F3=Exit F4=Prompt F5=Refresh F9=Retrieve F11=Show category F12=Cancel F17=Top F18=Bottom F23=More options (C) COPYRIGHT IBM CORP. 1980, 2007.

Volume Status - WRKMLMBRM
Work with Media Library Media RCHASYUM Media library : NET3592 Position to Starting characters Type options, press Enter. 1=Add MLB media =Work with media 5=Initialize 6=Change category 7=Eject 8=Mount 9=Demount Media BRM Information-- Opt Volume Type Category Status Media Class Status HPK600 JA *SHARE400 Available FMT3592A1 *EXP HPK601 JA *EJECT Ejected FMT3592A1 *EXP HPK602 JA *SHARE400 Error FMT3592A1 *ERR HPK604 JA *SHARE400 Available FMT3592A1 *EXP HPK620 JA *SHARE400 Available FMT3592A1 *EXP HPK623 JA *EJECT Ejected *NONE JRX012 JR *SHARE400 Available *NONE JRX013 JR *SHARE400 Available *NONE More... F3=Exit F5=Refresh F9=System command F12=Cancel F13=Repeat

Updating Cartridge Status-TS35xx Tape Libraries

Highlight device, R-click and select Manage Tape Library Media Library Connections

BRMS will update the cartridge status for TS35XX tape libraries across systems in the network. Can affect performance…. Not yet available. Current estimate: May 15, 2008 BRMS PTF

Tape Library Status Tool – Who’s using my tape resource?
Display Spooled File File : QP1ADEVUSE Page/Line 1/27 Control Columns Find * FILE LIBRARY MEMBER FORMAT DEVICELOG QTEMP DEVICELOG DEVICELOG DATE /04/08 TIME :50:59 01/04/08 14:50: PAGE 1 DEVSTSDATE DEVSTSTIME STATUS SYSTEM : X1521P3 :NET3590: TAP06 STATUS :-*ALLOCATED * * * E N D O F R E P O R T * * * Bottom F3=Exit F12=Cancel F19=Left F20=Right F24=More keys This tool will produce a report that displays the users of the resources in a tape library for all systems in a BRMS network that share that library. The tool is also available on earlier release with the following PTFS: SI24433 for V5R4 and SI24427 for V5R3. To find the tape library resource status for a specific system, issue the following command: QSYS/CALL QBRM/Q1AOLD PARM(’DEVUSESTS ’ ’SYSTEM1 SYSTEM2’) Note: The second parameter can specify multiple systems, restricted only by the parameter length of 200 characters. To find the tape library resource status for all systems in the BRMS network, issue the following command: QSYS/CALL QBRM/Q1AOLD PARM(’DEVUSESTS ’ ’*NETGRP’) Both of the commands will generate an output file, QTEMP/DEVICELOG, and a printer report, QP1ADEVUSE. Note: In order to get status from a particular system, that system must have the appropriate PTF applied and must be in the BRMS network. Documentation on this tool can be found at this link:

Support to Stop SNA Attempt If No TCP/IP or Vice Versa
Change Network Group Y0446P4 APPN Network group : *MEDINV Position to : FlashCopy state : *ENDPRC Receive media info . : *NONE *NONE, *LIB Communication method : *AVAIL *AVAIL, *IP, *SNA, *NONE Notify period : 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 X1521P APPN *LIB Online Active Bottom F3=Exit F5=Refresh F12=Cancel Specifies whether BRMS is enabled for all available types of communication, just TCP/IP or just SNA for its network operations. The possible values are: *AVAIL BRMS will attempt to use TCP/IP first, but if that is unsuccessful, BRMS will then attempt to use SNA for its network operations. *IP BRMS is enabled to use TCP/IP for its network operations. *SNA BRMS is enabled to use SNA for its network operations. *NONE BRMS is not enabled to use TCP/IP or SNA for its network operations. At prior releases, the user would need to specify individual commands, now available here.

Support Virtual IP Addressing In Restricted State- New to GUI for V6R1
When you are running SAVSYS backup procedures, the operating system must be in restricted state. In a shared media inventory, if the current system does not have any volumes available, then BRMS needs to communicate with the remote systems for volume selection. In order to do this while in restricted state, BRMS will need to start the TCP/IP or VIPA interfaces that will be used to communicate with the remote systems. You will need to specify those interfaces to BRMS. On V5R2M0, V5R3M0 and V5R4M0 systems use the following command to specify the TCP/IP or VIPA interfaces that BRMS is to use during restricted state. QSYS/CALL QBRM/Q1AOLD PARM('TCPIPIFC' '*ADD' 'interface') QSYS/CALL QBRM/Q1AOLD PARM('TCPIPIFC' '*REMOVE' 'interface') Where: The interface is the internet address of the system from which you issued this command and which you are using to communicate with the remote systems. Specify the interface in the form of nnn.nnn.nnn.nnn Example: QSYS/CALL QBRM/Q1AOLD PARM('TCPIPIFC' '*ADD' ' ') Note: BRMS will not start any TCP/IP interfaces if the system is not completely in restricted state. Therefore any user-defined exit that is used to bring system to restricted state must make sure that system is completely in restricted state before starting the backup process. Note: You can specify multiple interfaces by issuing the QSYS/CALL QBRM/Q1AOLD PARM('TCPIPIFC' '*ADD' 'interface') command multiple times. Once this command is run, it need not be run again unless you want to disable or re-enable restricted state TCP/IP.

Support Virtual IP Addressing In Restricted State
…. Continued…. See additional notes Example: QSYS/CALL QBRM/Q1AOLD PARM('TCPIPIFC' '*ADD' ' ') Note: BRMS will not start any TCP/IP interfaces if the system is not completely in restricted state. Therefore any user-defined exit that is used to bring system to restricted state must make sure that system is completely in restricted state before starting the backup process. Note: You can specify multiple interfaces by issuing the QSYS/CALL QBRM/Q1AOLD PARM('TCPIPIFC' '*ADD' 'interface') command multiple times. Once this command is run, it need not be run again unless you want to disable or re-enable restricted state TCP/IP. Restrictions: The following restrictions apply when the operating system is running in restricted state: The interface must use a line description of type *ELAN, *TRLAN or *DDI. (To view the line type for your interface, at a command line interface enter CFGTCP and select option 1 - Work with TCP/IP interfaces.) The line description may not be attached to an NWID or NWSD. (To verify the interface is not attached to a NWID or NWSD, from a command line interface enter DSPLIND lindesc (where lindesc is the name of your line description). Verify that the Resource name is not *NWID or *NWSD.) BRMS can only start one interface per line description type. BRMS needs to be at V5R2 or higher in order to use this function. The system has to be in restricted state for this to work. If any subsystems are started after going into a restricted state , this will function will not work.

Printer Files-Upgrading
BRMS will no longer delete Printer file attributes when upgrading. BRMS will no longer delete Printer file attributes when upgrading. Prior to V6R1M0, when installing 5722-BR1, the printer files that existed on the system were deleted and replaced by the new shipped printer files. Now when upgrading, BRMS will save off the printer file attributes, install the new files, and apply the saved attributes to the new printer files. Therefore preserving any changes made to the attributes prior to upgrading.

Blade Information

Blade information Solution Partial backup Full-system backup
i5/OS save to virtual optical in VIOS; VIOS command to tape Yes i5/OS save to virtual optical in VIOS; VIOS TSM client save over network i5/OS save to virtual optical IMGCLG, FTP images to VIOS or another i5/OS i5/OS save to virtual optical in VIOS; FlashCopy VIOS virtual media LUNs and attach to 2nd VIOS Not practical i5/OS save to virtual tape IMGCLG; FTP IMGCLG files to another i5/OS partition No FlashCopy (full copy) VIOS LUNs assigned to i5/OS; bring up separate i5/OS partition from copy Replicate VIOS LUNs assigned to i5/OS; bring up separate i5/OS partition from copy

i5/OS Save/Restore via VIOS File-backed Optical Images
Use GO SAVE or BRMS in i5/OS Save is to writeable optical device in i5/OS Optical volume is backed by file in VIOS Two options to copy image files to tape: Option VIOS command to SAS tape Option 2 – Web Client Streaming Use IVM GUI to stream optical media files between VIOS and web client, then move images files to media attached to web client. IVM/VIOS i5/OS i5/OS Virtual Adapter Virtual Adapter Virtual Adapter Virtual Adapter Virtual Adapter Hypervisor IVE Hardware Adapter Adapter VIOS Storage Filed-backed Optical Filed-backed Optical Filed-backed Optical Tape Web Client

New BRMS APIs q1aCrtCg Create Control Group
q1aCrtCgBO Create Control Group Based On q1aDltCg Delete Control Group q1aAddCgE Add Control Group Entry q1aRmvCgE Remove Control Group Entry q1aAddCgEO Add Control Group Entry Object Omit q1aRmvCgEO Remove Control Group Entry Object Omit q1aCrtLst Create List q1aDltLst Delete List q1aAddLstE Add List Entry q1aRmvLstE Remove List Entry For more information, please see the V6R1 BRMS manual

References System i Information Center
System i Backup, Recovery, and Media Services for i5/OS (V6R1) SC BRMS Customer site BRMS GUI documentation www-03.ibm.com/servers/eserver/iseries/service/brms/pluginfaq.html

Trademarks and Disclaimers
8 IBM Corporation All rights reserved. References in this document to IBM products or services do not imply that IBM intends to make them available in every country. Trademarks of International Business Machines Corporation in the United States, other countries, or both can be found on the World Wide Web at 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.

Backup, Recovery, & Media Services (BRMS) V6R1 Enhancements

Similar presentations

Presentation on theme: "Backup, Recovery, & Media Services (BRMS) V6R1 Enhancements"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

Backup, Recovery, & Media Services (BRMS) V6R1 Enhancements

Similar presentations

Presentation on theme: "Backup, Recovery, & Media Services (BRMS) V6R1 Enhancements"— Presentation transcript:

Similar presentations

About project

Feedback