Backup/Recovery on IBM i Including Virtual Tape and …schd.ws/hosted_files/commons17/86/Common 2017... · SNA Low Data Compression ... IBM Rochester Lab Services Available to help

All trademarks and registered trademarks are the property of their respective owners.© HelpSystems LLC. All rights reserved.

Common Conference 2017

What’s New with Backup/Recovery on IBM i – Including Virtual Tape and Encryption

Debbie Saugen

Director, Business Continuity Services

[email protected]

What’s New with Backup Recovery on IBM i

• Virtual Tape

• Tape Encryption

• Recovery for Logical/Physical Files

• Save and Restore Enhancements

– Faster IFS Saves

– 7.1

– 7.2

– 7.3

• Backup, Recovery and Media Services (BRMS) Enhancements

– BRMS Enterprise Function

– 7.1

– 7.2

– 7.3

Agenda for Backup/Recovery Enhancements

UP NEXT...

Virtual Tape and Tape Encryption Support


• Key Advantages

– Supported on all Save/Restore Commands and APIs (except SAVSTG)

– Can Be Faster than Saving Directly to Tape

Similar Performance as Save Files

Best Performance in Separate ASP

– Eliminates Save File Limitations

One Library Per Save File

SAVSYS Not Supported on Save File

Parallel Saves Not Supported on Save File

1 TB Size Limitation on Save File

– Eliminates Media Error Limitations

Saves Ending Due to Tape Device or Media Errors

Save-while-active Checkpoint Restriction (Once Checkpoint Reached Saves Can’t be Restarted)

– Duplicate Saves to Media (DUPTAP or DUPMEDBRM)

When Tape Devices Available

At Your Convenience

– Onsite and Offsite Storage

Keep Virtual Volumes on Systems as Needed

Keep Duplicated Volumes Offsite

Virtual Tape Support (Introduced in V5R4)


• Considerations

– Additional DASD Requirements

– No Install from SAVSYS Virtual Volume

D-IPL Only from Media

– May Not Be Faster

Tape Technology

System Configuration and Environment

– Data Compaction Not Supported

– Data Compression Support

DTACPR(*YES) Parameter on Save Commands (Default is *NO)

SNA Low Data Compression

Significant Performance Impact

Virtual Tape Support


• Implementation of Virtual Tape

– Included in Base i5 Operating System

– Configures as RACL (Random Access Cartridge Loader) Tape Device

I/O to Disk instead of Tape Media

Behaves as Tape Library Mounting Specified Volumes

Up to 35 Virtual Tape Devices

Virtual Tape Volumes Support Multiple Optimum Block Sizes (Compatibility with Tape Devices)

– Existing Image Catalog Commands used for Virtual Optical

– Tape Volume Management Interface with iSeries Navigator

– User Interface is Green Screen or iSeries Navigator

– Complete End User Interface and Tape Management with BRMS

• Virtual Volumes Stored as IFS Stream Files

– FTP to Other Servers or Partitions Considerations

Bandwidth

Management of Transmitted Files

– Disaster Recovery

Virtual Tape Support


Overview and Implementation

1098

7

6

5

4

3

2

1

Up to 256 virtual tape volumes

LODIMGCLG

Virtual Tape

Device

SaveCRTDEVTAP

Disk

CRTIMGCLG

(1)

(2)

(4)

ADDIMGCLGE(3)

Any ASP or iASP

Restore

Duplicate to media, switch or

FTP to another system


• Considerations

– Must Create Virtual Tape Devices Outside of BRMS

CRTDEVTAP Command

– Must Create Image Catalog and Virtual Volumes Outside of BRMS

CRTIMGCLG

ADDIMGCLGE

iSeries Navigator

– BRMS Virtual Tape Acts Just Like Physical Tape Device

BRMS Automatically Performs Virtual Tape Mounts

– Disaster Recovery

Duplicate to Physical Media (DUPMEDBRM)

(Physical Tapes Become Original Save Volume and Virtual Tapes Become Duplicated Save Volume)

Virtual Tape Volumes Stored as IFS Objects

Image Catalogs in READY Status (Not Saved During Normal Save so no Virtual Volumes in Image Catalog After Disaster Recovery)

– Virtual Media Volumes Not Shared in BRMS Network

Local System Only

Independent IASPs Allowing Sharing by Switching IASP

BRMS and Virtual Tape


ProtecTIER on IBM i – Where does it fit?

IBM i TS7650

Our Niche – TS7650 IP Replication

IBM iTS7650

For customers who are moving their tapes offsite via truck

today and would like a safer, more automated solution

Note: If the customer already has an HA/DR solution that replicates his data to his

remote site, then that will likely provide a more economical solution for remote tape:

• IBM i Software-based Replication (eg ROBOT HA, MIMIX, iTera, etc)

• External Disk Copy Services

• IBM i Geographic Mirroring (formerly Cross Site Mirorring or XSM)

For customers where a tape

cartridge is much bigger

than needed

. . .VIOS /

NPIV

ProtecTIER

Our Niche – Tiny LPARs

Our Niche – Tired of

Handling Tapes?


OhioIBM iTS7650

Local Saves to

Virtual Tape with

De-dup

IBM i TS7650

New York

IP Replication

Minimized bandwidth

since data is de-dup’d

before sending

TS3500

Optional

duplication

to physical

tape

(at local or

remote

site)

Disk

Virtual

Tapes C

A

B

C

A

AB

B

A

What is

DeDuplication

?

C

A

B

C

A

AB

B

A C

A

B

C

A B

B

A

A

What does the TS7650 ProtecTIER do?


IBM i

Host

“Server”

LPAR

Minimum

IBM i 7.1

TR2

IBM i

Guest

“Client”

LPAR

Minimum

IBM i 6.1.1

When IBM i is hosted by IBM i …..

• Previously, tape drive had to be “moved”

among the LPARs via LPAR sharing

• With releases shown above, guest partitions

can all “see” the tape drive and share it

similar to SAN-attached libraries

Small sequential-mode drives only

(see detailed list of drives

on next page)

If you need library function, then

you need VIOS / NPIV instead

IBM i

Guest

“Client”

LPAR

Minimum

IBM i 6.1.1

IBM i

Guest

“Client”

LPAR

Minimum

IBM i 6.1.1

. .

.

IBM i hosting IBM i – Client Virtualized Tape Device


IBM i Tape Encryption on IBM Tape Drives

SKLM Server

IBM i

LTO4/5/6/7 or TS1120 /30/ 40/50

Drives

in a Tape Library

Components

▪ Encryption Capable Tape Drive – fibre

TS1120/TS1130/TS1140/TS1150 or fibre/SAS LTO4/5/6/7

▪ A Tape Library – TS2900/3100/3200/3310, TS3400,

TS3500,TS4500 and 3494

▪ Multiple Key Managers (SKLMs)

▪ Suitable Drive / Library / SKLM at DR Site to restore

How does it Work?

▪ IBM i sends the

backup to the tape

library

▪ If the drive / library

has encryption

turned on, then the

library gets the keys

from the SKLM

▪ The drive/library

write the save

▪ BRMS is

recommended to

keep encrypted /

non-encrypted

tapes separate

SKLM Server

http://www-03.ibm.com/systems/i/hardware/520express/index.html


Security Key Lifecycle Manager (SKLM)

What is SKLM?

•Follow-on to Encryption Key Manager (EKM)

•Stores / Serves keys for Encryption:

•Tape: TS1120, TS1130, TS1140,TS1150,

LTO4, LTO5, LTO6, LTO7

•Disk: DS8000

•MUCH more user-friendly than EKM

IBM i customers usually run their SKLM on Windows

because:

• They typically have good skill on Windows

• It avoids the temptation to run SKLM on a system with a

production application and accidentally encrypt the keys

(this would make it impossible to recover due to the

chicken / egg problem

• Easy to load up a spare SKLM and store it offsite

• Easy to acquire hardware to re-build the SKLM after a big

disaster

• Faster to restore / rebuild the key store on Windows vs a

larger platform

Although we can’t RUN SKLM on IBM i, we can use SKLM

on another platform to encrypt our IBM i saves

What Platforms does it run on?

•Windows Server 2003 & 2008

•AIX 5.3, AIX 6.1 or later

•Red Hat Enterprise Linux 4 & 5

•SuSE Linux Enterprise Server 9 &10

•Solaris 9&10 SPARC

•z/OS Version 1.9, 1.10, 1.11

For SKLM Pubs and More Info:

http://publib.boulder.ibm.com/infocenter/

tivihelp/v2r1/index.jsp?topic=/com.ibm.S

KLM.doc/welcome.htm

Never delete

your old keys


• Things to Remember

• Hardware Required

LTO4/LTO5/LTO6/LTO7 or TS1120/TS1130/TS1140/TS1150 tape drives

Fibre or SAS (not SCSI)

Drives must reside in a tape library

(although it’s OK to run in sequential mode)

For LTO4/LTO5/LTO6/LTO7, library must have the transparent LTO encryption feature

LTO4/LTO5/LTO6/LTO7 media for LTO4/LTO5/LTO6/LTO7, or any TS1120/TS1130/TS1140/TS1150 formatted media

Comparable gear at your recovery site

• Software Required

Security Key Lifecycle Manager Software + hardware to run it on

• Key Manager Reminders

Don’t encrypt your Key Manager

Have multiple Key Managers at your home site and DR site

Save your Key Manager and send a copy offsite anytime your keys change

• Other Reminders

Choose TS3500/TS4500/3494 over other libraries since they can turn encryption on/off based on volser

Include ALMS on a TS3500/TS4500 order so encrypted/non-encrypted drives can share a library partition

IBM Rochester Lab Services Available to help with install/setup (contact Carol Ward or Mike Gordon)

Tape Drive Based Encryption Reminders

UP NEXT...

Recovery for Logical/Physical Files


• Allow Logical/Physical Files in Different Libraries to Restore in Any Order

• New DFRID parameter on RSTLIB and RSTOBJ

– RSTLIB LIB(*ALLUSR/*IBM/*NONSYS) DFRID(*DFT)

Automatically Handles Order Dependencies Without User Action

Restore Option 21, 22, and 23 Handles Automatically

– DFRID(name) Associates Multiple Restore Commands

• New Commands

– RSTDFROBJ DFRID(name)

Restore Deferred Objects Associated with RSTxxx DFRID(name)

– RMVDFRID DFRID(name)

Remove Deferred Objects - Decide They Can’t be Restored

• Example:

– RSTLIB LIB1 DEV(TAP01) DFRID(MYDFRID)

LIB1 contains logical files built over physicals in LIB2

– RSTLIB LIB2 DEV(TAP02) DFRID(MYDFRID)

– RSTDFROBJ DFRID(MYDFRID)

• Also Handles Materialized Query Table (MQT)

• Backup Recovery and Media Service (BRMS) Handles Automatically

Recovery for Logical/Physical Files (Starting with 6.1)

UP NEXT...

Save and Restore Enhancements for 7.1


• Saves now Track Position of Each Object (Physical Location on Tape)

– New Save OUTFILE or OUTPUT Field for Each Object

– User must Retain Positioning Information to use for Restore

• New Restore POSITION Parameter for:

– RSTLIB, RSTOBJ and RST Commands

– QsrRestore and QSRRSTO APIs

– POSITION(*START) is Default (Existing Behavior)

– POSITION(hexadecimal value) to Pass Position for Single Object Restore

– Requires SEQNBR also Specified

• Supported for Parallel Restores

– QsrCreateMediaDefinition api to Specify Positioning for each Media File

• Very Significant Performance Improvements

– Example: Restoring Last Object from 1.1 million IFS Object Save went from 22 minutes to less than 3 minutes

• Backup Recovery Media Service (BRMS) Automatically Uses New Support

Fast Restore of Single Object (7.1)


• ALWOBJDIF Parameter New *COMPATIBLE Value

– Behaves like ALWOBJDIF(*ALL) in Combination with ALWOBJDIF(*FILE) for Database Files

– FINALLY a Single Value that Does What You Usually Need

• Supported on RSTLIB and RSTOBJ Commands

• Supported on QSRRSTO API

• RESTORE Menu Options 21, 22, and 23 Changed to ALWOBJDIF(*COMPATIBLE) When Specifying to Restore to Different System

ALWOBJDIF(*COMPATIBLE) Restore (7.1)


• SAVLIB/SAVCHGOBJ of QUSRSYS Library Automatically Performs Retrieve System Information (RTVSYSINF) Command

– RTVSYSINF Saves System Information such as:

System Values

Edit Descriptions

Service Attributes

Message Reply List Entries

• RTVSYSINF Information Included with SAVSYS Command

– Not Needed if System Recovered with SAVSYS Media

– Run Update System Information (UPDSYSINF) LIB(QUSRSYS) if no SAVSYS Media and System Recovered from PID/Install Media

– Run UPDSYSINF to reset System Values changed for System Recovery

• Included with Latest Backup/Recovery Group PTF for 6.1

– SF99187

RTVSYSINF with QUSRSYS Save (7.1)

UP NEXT...



• ASYNCBRING Parameter Added to Save Object (SAV) Command Command

– Brings Objects into Memory Asynchronously

– May Improve IFS Save Performance

• PTFs for 6.1 and 7.1

• Very Good Performance Improvement for Most Customers

• For Details see BRMS Website: https://www.ibm.com/developerworks/mydeveloperworks/wikis/home?lang=en#/wiki/IBM%20Backup%2C%20Recovery%20and%20Media%20Services%20%28BRMS%29%20for%20i/page/Overriding%20the%20ASYNCBRING%20parameter%20on%20IFS%20saves%20to%20improve%20performance

IFS Save Performance Enhancement (ASYNCBRING)


• SELECT Parameter Added to Save Commands and APIs

• Save Multiple Objects with Save Object (SAVOBJ) Command

• Select Objects with Save Library (SAVLIB) Command

• Select Objects, Object Types, Object Attributes and File Members to Include or Omit

• Allows Refining Selections with other Parameters

Save Object Selection Enhancements


• Restoring Multiple Libraries

• *ANY Specified

First Version of Saved Libraries Restored Starting With Specified Sequence Number (SEQNBR)

For Optical Media all Saved Libraries Restored found in Directory on Optical File (OPTFILE)

• *SELECT Specified

Libraries Specified are Restored

Restore Library Selection Enhancements


• Save Spooled Files with Save Changed Objects (SAVCHGOBJ) Command

• Expire Spooled Files as you Save with Save Object List (QSRSAVO) API

Saving Spooled Files Enhancements


• SAVLIB/SAVCHGOBJ of QUSRSYS Library Automatically Performs Retrieve System Information (RTVTCPINF) Command

– RTVTCPINF Retrieves and Saves Current TCP/IP Configuration

• If System Recovered using Distribution Media

– Restore User Data

– Run UPDTCPINF LIB(QUSRSYS)

Automatic Save of TCP/IP Configuration Information


• Save/Restore Menu Options 21, 22 and 23

• New End TCP/IP Wait Time Prompt

– Specify Time to Allow TCP/IP Processing to End before Ending All Subsystems

• New Print Joblog Prompt

– Print Joblog When Save/Restore Menu Option Completes

New Save/Restore Menu Enhancements


• Save Storage (SAVSTG) Command No Longer Available

• Restore Storage Function No Longer Available

Save Storage Command


• Configure IASPs During System Recovery

• New Configure Device ASP (CFGDEVASP) Command

– IBM i Navigator No Longer Required during System Recovery

– Skip the IPL Required to Start IBM i Navigator

• PTF SI44141 Required

Configure IASP Enhancement (7.1 Technology Refresh 3)


• Allow Journals/Journaled Objects to Restore in Any Order

• New DFRID parameter on RSTLIB and RSTOBJ

– RSTLIB LIB(*ALLUSR/*IBM/*NONSYS) DFRID(*DFT)

– Restore Option 21, 22, and 23 Handles Automatically

• Once Journal Restored

– Object with Deferred Journal Start will Establish and Resume Journaling

• Backup Recovery and Media Service (BRMS) Handles Automatically

Recovery for Journals (7.1 Technology Refresh 7)

UP NEXT...



New Save Menu Enhancements (7.3)

New Start Date

Schedule Up to Seven Days in Advance


New Save Menu Enhancements (7.3)

Will Attempt to Remount File Systems after Save


– Authorization Lists in QSYS

Used to Secure System Commands

– SAVSYS and SAVSECDTA

Now Preserves Authorization List Links for QSYS Objects

– RSTUSRPRF and RSTAUT

Normal Recovery Process

Automatically Recovers Authorization List Links in QSYS

7.3 Recover Authorization Lists in QSYS

UP NEXT...

BRMS


• IBM i’s Strategic Backup Management Product

• 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 (Introduced in V5R4)

• Software Tape Encryption (Introduced in 6.1)

Backup Recovery and Media Services (BRMS)


Tape Library Support

3494 3590/2LTO 3570/357

5

ƒ 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

RecoveryRecovery 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 Function

ƒ 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

Hierarchical Storage

Management

Option #2: Advanced

Option #1: Network

Network

BRMS

Media

Database

BRMS

Media

Database

BRMS

Media

Database

iSeriesA

iSeriesB iSeriesC

BRMS GUI

- Software Data

Encryption

- Media LibraryMgmt

- User Defined System

Name

- Tape Library Status

Tool

6.1

UP NEXT...

BRMS Encryption


• Encryption for Any Tape Device, Tape Library or Virtual Tape

– AES Encryption

– Data Encrypted – Not Tape Labels

– Capability to Encrypt Each File Via Different Key

• Requires i5/OS option 44 (Encrypted Backup Enablement)

– Requires Tape Management Application to Enable Encryption

– Recommend BRMS

BRMS Advanced Feature Required

– Not Compatible with Hardware Encrypting Tape Devices

Software Encryption (6.1)


• Performance

– Encrypted Data Does Not Compact Well - Native Device Save Rate will Limit Maximum Performance

6387 (SLR100) 5MB/sec (18 GB/hour)

3590 Model H11 14MB/sec (50 GB/hour)

3580 Model 002 35MB/sec (126 GB/hour)

3592 Model 01A 40MB/sec (144 GB/hour)


3592 Model E05 100MB/sec (360 GB/hour)

– Supports Much Faster Save Rates - Hardware Encryption


– Supports Much Faster Save Rates - Hardware Encryption

Virtual Tape - Performance Limited by Disk Config and Processor Speed

– System Processor Speed Impacts Performance

P5 processors -> Expect 76MB/sec (275 GB/hour) or less

P6 processors -> Expect 130MB/sec (468 GB/hour) or less

Software Encryption Considerations (6.1)



Tape Backup Performance - Saves

0

100

200

300

400

500

600

700

1 GB Source File 12 GB User Mix 64 GB Large File 320 GB Large File

GB

/HR

9406-MMA-4w ay Encrypted ASP SAVLIBBRM NO Softw are Encryption

9406-MMA-4w ay Encrypted ASP SAVLIBBRM With Softw are Encryption9406-MMA-4w ay NON Encrypted ASP SAVLIBBRM NO Softw are Encryption

9406-MMA-4w ay NON Encrypted ASP SAVLIBBRM With Softw are Encryption9406-570-4w ay NON Encrypted ASP SAVLIBBRM NO Softw are Encryption

9406-570-4w ay NON Encrypted ASP SAVLIBBRM With Softw are Encryption


• Capacity

– Loss of Compaction May Result in More Tape Cartridges

• CANNOT Encrypt

– Operating system (*SAVSYS, *SAVSYSINF, *SAVSECDTA, *SAVCFG)

– QBRM, QUSRBRM, QSYS2, QGPL and QUSRSYS

– BRMS Will Not Encrypt “Q” Libraries

• Standard Labeled Tapes Only

• Cannot Use with Tape Write Error Recovery Enabled

• If Key Store File Lost – Data is Unrecoverable


UP NEXT...

BRMS Enhancements for 7.1


• Domino 8.5 DAOS

• IBM Systems Director

• IBM Systems Director Navigator for i

– Level 2 Console (L2C)

– Scheduling via Systems Director

– Viewing Scheduled BRMS Jobs

– Filtering BRMS Messages in BRMS Log

– Marking Volumes for Duplication

– Multiple E-mail Addresses Support

• QIBMLINK Link List

• QALLUSRLNK Link List

• Support for more than 999,999 Objects

• STRRCYBRM Enhancements

– Additional Overrides

– Recovery Report Enhancements



• BRMS Restores with Outfile Option

• BRMS ASP Control Support on RSTLIBBRM/RSTOBJBRM

• BRMS Distributed Backup Support

– 5250 Emulation Screens

– IASP History Setup via Systems Director Navigator for i

• BRMS Maintenance Enhancements

• Movement Report Improvements

• Clearing Volumes in *ERR Status

• Protecting Volumes Marked for Duplication

• Improved Recovery Times

• New Restore Special Value

• Non-BRMS Saves on a BRMS System



• Before Domino 8.5.0 and DAOS

– Document Attachment and Object Service (DAOS)

– Document Attachments Part of .nsf File

• With Domino 8.5.0 and DAOS

– Document Attachments Pulled out of .nsf File as .nlo Objects

• With Domino 8.5.1 and PTFs SI34916 (V5R4M0) or SI34918 (6.1) or Later

– BRMS Auto-detects NLO Objects for Domino Online Backups (NO BRMS Changes Needed)

– Full Save Includes all NLO Objects

– Incremental Save Includes New and Changed NLO Objects

– In BRMS Base Code for 7.1

• Be Careful with Externalized Attachment Size

– Otherwise Many .nlo Objects

– Lot of Extra IFS Objects = Slower Backups

BRMS and Domino 8.5 DAOS (7.1)


Work with Media Information BRMSSYS

Position to Date . . . . .

Type options, press Enter.

2=Change 4=Remove 5=Display 6=Work with media 7=Restore

9=Work with saved objects ...

Saved Save Save Save Parallel Volume File Expire

Opt Item Date Time Type Devices Serial Sequence Date

DOMINO04 3/01/10 3:23:30 *LTSONL 2 PT1015 1 3/21/10

DOMINO04 3/01/10 3:24:27 *LTSONL 2 PT1015 3 3/21/10

DOMINO04 3/01/10 3:24:59 *LTSONL 2 PT1015 5 3/21/10

DOMINO04 3/01/10 3:26:33 *FULL 2 PT1015 6 3/21/10

Bottom

F3=Exit F5=Refresh F11=Object detail F12=Cancel

F23=More options

DAOS Objects Saved at End of SAVDOMBRM (7.1)







Saved Save Save Item ----- Objects ----- Control Obj

Opt Item Date Time Type Saved Not Saved Group Dtl

DOMINO04 3/01/10 3:23:30 *LNK 50 0 QLTSDOM04 *YES




DAOS Objects Saved at End of SAVDOMBRM (7.1)


• Almost Functionally and Visually Identical

• IBM Systems Director Navigator for i Includes Scheduling Function with 7.1

– For Backup, Maintenance, Printing Reports, Reclaim, etc.

IBM Navigator for i (GUI) vs. Systems Director Navigator for i (WEB) 7.1


• Schedule BRMS Jobs via WEB Interface

• Can Schedule:

– Backup Control Groups

– Archive Control Groups

– BRMS Maintenance

– BRMS Movement

Scheduling BRMS - Systems Director Navigator for i (7.1)


• Only Active or Completed Jobs Could be Viewed or Monitored at 6.1

• Scheduled Jobs via IBM Navigator for i (GUI) Also Listed

• BRMS Green Screen Lists IBM Systems Director for i (WEB) and IBM Navigator for i (GUI) Jobs

Viewing BRMS Scheduled Jobs (7.1)


• New Option in IBM Navigator for i and IBM Systems Director Navigator for i

• Searches Messages for Specific Control Group

Filtering Control Group Messages in BRMS Log (7.1)


• With 7.1 can Mark/Unmark Volumes for Duplication

– IBM Navigator for i (GUI)

– IBM Systems Director Navigator for i (WEB)

• Same Functionality as WRKMEDBRM Option 18 and 19

Marking Volumes for Duplication via GUI/WEB (7.1)


• With 7.1 Specify Multiple E-mail Addresses to Send BRMS Alerts

• Setup Under Global Policies>Network

– IBM Navigator for i (GUI)

– IBM Systems Director Navigator for i (WEB)

• Not Available in 5250 Emulation

• Separate E-mail Addresses with Comma and No Space

• Requires SMTP Server to be Running

Multiple E-mail Address Support (7.1)


• QIBMLINK Link List for IBM Directories Added to *SYSGRP Control Group

– Only Added on New BRMS Installations – NOT Added during System Release Upgrade

– Recommend to Add Manually to *SYSGRP for Current Installations

IBM IFS Link List Added to *SYSGRP (7.1)


Display Backup Control Group Entries BRMSSYS

Group . . . . . . . . . . : *SYSGRP

Default activity . . . . : *BKUPCY

Text . . . . . . . . . . : Backs up all system data

Weekly Retain Save SWA

Backup List ASP Activity Object While Message Sync

Seq Items Type Device SMTWTFS Detail Active Queue ID

10 *EXIT *******

20 *SAVSYS *DFTACT

30 *IBM *DFTACT *NO *NO

40 QIBMLINK *LNK *ALLAVL*DFTACT *NO *NO

50 *EXIT *******

Bottom

Press Enter to continue.

F3=Exit F11=Display exits F12=Cancel F14=Display client omit status

IBM IFS Link List Added to *SYSGRP (7.1)


• New QALLUSRLNK Link List

– Save User IFS Directories and Files

– Use in Conjunction with QIBMLINK Link List

– Omits the Following:

'/QSYS.LIB'

'/QDLS'

‘/TMP/BRMS'

'/QIBM/ProdData‘

'/QOpenSys/QIBM/ProdData'

User IFS Link List (7.1)


Work with Lists BRMSSYS

Position to . . . . . . Starting characters


1=Add 2=Change 3=Copy 4=Remove 5=Display 6=Print

Opt List Name Use Type Text

QALLSPLF *BKU *SPL All printed output

QALLUSRLNK *BKU *LNK All user directories

QIBMLINK *BKU *LNK All IBM directories

QLNKOMT *BKU *LNK Associated user omit list for *LINK

QALLUSRLNK Link List (7.1)


• BRMS now Shows More than 999,999 Objects Saved:

– WRKMEDIBRM Display

– BRMS Recovery Report (QP1ARCY)

Support More than 999,999 Objects (7.1)







Saved Save Save Item ----- Objects ----- Control Object

Item Date Time Type Saved Not Saved Group Detail

LIBA 2/26/10 8:11:38 *LIB 1 0 *NONE *NO

LIBB 2/26/10 8:13:26 *LIB 1 0 MJTEST *YES

*LINK 2/26/10 8:14:57 *LNK 1090926 0 MJTEST *NO

QUSRBRM 2/26/10 8:15:04 *OBJ 16 0 MJTEST *YES

Correct Number of Objects Saved Listed (7.1)


__ STEP 017 : Recover Directories and Files

Start date/time __________________ Stop date/time __________________ Duration _________________

You should restore the current version of your objects in directories.

If you are performing a complete system restore, run the following

command to continue.

STRRCYBRM OPTION(*RESUME)

Otherwise, run the following command.

STRRCYBRM OPTION(*LNKLIST) ACTION(*RESTORE)

Type the command choice and press "Enter".

Select the saved item(s) listed below from the "Select Recovery Items"

display and press "Enter" to recover these saved items. Recovery of

these saved items will require the volumes listed on the report or

duplicate volumes.

--- Objects ---

Saved Save ----- ASP ------ Save Save Not Sequence Control

Item Type Name Number Date Time Saved Saved Number Group

---------- ------- ---------- ----- -------- -------- -------- ------ --------- ---------- ---------

__ *LINK *FULL *SYSBAS 00001 11/02/09 14:32:43 1090926 0 0 *SYSTEM

Correct Number of Objects on Recovery Report (7.1)


• Override Selective Parts of Recovery

– *ALLSYS

– *SAVSYS

– *SECDTA

– *SAVCFG

• Ignored if Override Recovery Element (OVERRIDE) Set to *NO

• Affects both *REPORT and *RESTORE

• Override Warning Posted in BRMS Recovery Report

STRRCYBRM - Overrides for Special Values (7.1)


Start Recovery using BRM (STRRCYBRM)

Type choices, press Enter.

Volume locations to include . . LOC *ALL

+ for more values

Volume locations to omit . . . . OMITLOC *NONE

+ for more values

Override recovery element . . . OVERRIDE *YES

Recovery element override: RCYELEM

Recovery element . . . . . . . *SAVSYS

Time period for recovery:

Start time and date:

Beginning time . . . . . . . . *AVAIL

Beginning date . . . . . . . . *BEGIN

End time and date:

Ending time . . . . . . . . . *AVAIL

Ending date . . . . . . . . . *END

+ for more values

STRRCYBRM - Overrides for Special Values (7.1)


Display Spooled File

File . . . . . : QP1ARCY Page/Line 7/48

Control . . . . . Columns 1 - 130

Find . . . . . .

*...+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....8....+....9....+....0....+....1....+....2....+....3

****************************************************************************************************

__ STEP 009 : Recover User Profiles

Start date/time __________________ Stop date/time __________________ Duration _________________

----- Attention ---------------------------------------------------

There is an override for recovery element *SECDTA.

---------------------------------------------------------------------

You should restore a current version of your user profiles.

To do so, type the following command and press "Enter".

----- Attention ---------------------------------------------------

Press F9 on the Select Recovery Items display to go to the Restore

Command Defaults display.

__ Ensure the tape device name or media library device name is

correct for the Device prompt.

__ Ensure *SAVLIB is specified for the Restore to library prompt.

__ Ensure *SAVASP is specified for the Auxiliary storage pool prompt.

If you are recovering to a different system or a different logical

partition, you must specify the following:

Attention in BRMS Recovery Report for Overrides (7.1)


• New OUTFILE Option for BRMS Restores

• Lists What Restored and What Not Restored

• Specify OUTFILE Option

– Recovery Policy – WRKPCYBRM TYPE(*RCY)

– BRMS Restore Commands

RSTLIBBRM

RSTOBJBRM

RSTBRM

– Recovery Defaults for

WRKMEDIBRM

STRRCYBRM ACTION(*RESTORE)

BRMS Restores with OUTFILE Option (7.1)


Change Recovery Policy BRMSSYS


Key store file . . . . . . . . . . *SAV Name, *SAV, *NONE

Key store library . . . . . . . *SAV Name, *SAV, *NONE

Restore private authorities. . . . *NO *NO, *YES

Output options for recoveries:

Output. . . . . . . . . . . . . . *NONE *NONE, *OUTFILE

File to receive output. . . . . . Name

Library. . . . . . . . . . . . . *LIBL Name, *LIBL, *CURLIB

Output member options:

Member to receive output . . . . *FIRST Name, *FIRST

Replace or add records . . . . . *REPLACE *REPLACE, *ADD

Output options for directory object recoveries:

Output. . . . . . . . . . . . . . *NONE

OUTFILE Option on BRMS Recovery Policy (7.1)


Restore Library using BRM (RSTLIBBRM)


Restore incremental . . . . . . *YES *YES, *NO

Allow object differences . . . . *NONE *NONE, *ALL, *COMPATIBLE...

+ for more values

Private authorities . . . . . . *NO *NO, *YES

Restore to library . . . . . . . *SAVLIB Name, *SAVLIB

Auxiliary storage pool . . . . . *SAVASP Name, 1-32, *SAVASP, *SYSTEM

From system . . . . . . . . . . *LCL

Additional Parameters

Output . . . . . . . . . . . . . *NONE *NONE, *OUTFILE

File to receive output . . . . . Name

Library . . . . . . . . . . . *LIBL Name, *LIBL, *CURLIB


Member to receive output . . . *FIRST Name, *FIRST

Replace or add records . . . . *REPLACE *REPLACE, *ADD

OUTFILE Option on RSTLIBBRM Command (7.1)


Restore Object using BRM (RSTBRM)


Save level time reference:

Save date . . . . . . . . . . Date

Save time . . . . . . . . . . *LATEST Time, *LATEST

End of media option . . . . . . *REWIND *REWIND, *LEAVE, *UNLOAD

Option . . . . . . . . . . . . . *ALL *ALL, *NEW, *OLD

Allow object differences . . . . *NONE *NONE, *ALL, *AUTL, *OWNER...

Private authorities . . . . . . *NO *NO, *YES

Object ID . . . . . . . . . . . *SAVED *SAVED, *SYS

Create parent directories . . . *NO *NO, *YES

Parent directory owner . . . . . *PARENT Name, *PARENT

From system . . . . . . . . . . *LCL

Output . . . . . . . . . . . . . *NONE

OUTFILE Option on RSTBRM Command (7.1)


Restore Command Defaults

Type information, press Enter.

Restore private authorities . . . . *NO *NO, *YES

Output options for recoveries:

Output . . . . . . . . . . . . . . *NONE *NONE, *OUTFILE

File to receive output . . . . . . Name

Library . . . . . . . . . . . . . *LIBL Name, *LIBL, *CURLIB


Member to receive output. . . . . *FIRST Name, *FIRST

Replace or add records. . . . . . *REPLACE *REPLACE, *ADD

Output options for directory object recoveries:

Output . . . . . . . . . . . . . . *NONE

OUTFILE Option on WRKMEDIBRM - STRRCYBRM (7.1)


• Specify Saved ASP on following BRMS Commands

– RSTLIBBRM

– RSTOBJBRM

• Allows More Control to Select Restores by ASP

ASP Control on RSTLIBBRM/RSTOBJBRM (7.1)


Restore Library using BRM (RSTLIBBRM)


Library . . . . . . . . . . . . Name, *MEDINF

+ for more values

Device . . . . . . . . . . . . . Name, *MEDCLS

+ for more values

Parallel device resources:

Minimum resources . . . . . . *SAV 1-32, *SAV, *NONE, *AVAIL

Maximum resources . . . . . . *MIN 1-32, *MIN, *AVAIL

Save level . . . . . . . . . . . *CURRENT 1-99, *CURRENT, *SAVDATE

Saved auxiliary storage pool . . *ANY Name, 2-32, *ANY, *SYSTEM

End of media option . . . . . . *REWIND *REWIND, *LEAVE, *UNLOAD

Option . . . . . . . . . . . . . *ALL *ALL, *NEW, *OLD, *FREE

Database member option . . . . . *MATCH MATCH, *ALL, *NEW, *OLD

Spooled file data . . . . . . . *NEW *NEW, *NONE

Restore incremental . . . . . . *YES *YES, *NO

Allow object differences . . . . *NONE *NONE, *ALL, *COMPATIBLE...

+ for more values

ASP Parameter on RSTLIBBRM Command (7.1)


• New BRMS Network Options Allowing Distribution of Backup History

• Used for:

– Which Systems Receive Saved History

Requires Remote System with *LIB for Networking

– iASP Support and Synchronization Control

Decide to Make Synchronized System the Owner

Update Reference Date for Incremental Backups

BRMS Distributed Backup Support (7.1)


Change Network Group BRMSSYS APPN

Network group . . . . : *MEDINV Position to . . . . :

FlashCopy state . . . : *ENDPRC

Receive media info . : *LIB *NONE, *LIB

Communication method : *IP *AVAIL, *IP, *SNA, *NONE

Notify period . . . . : 30 30-99999 seconds


1=Add 4=Remove 8=Set time

Remote Local Remote Receive System Network

Opt Location Name Network ID Media Info Status Status

BRMSSYSB APPN *LIB Online Active

BRMSSYSC APPN *LIB Online Active

Change Network Group (6.1)





Communication method : *AVAIL *AVAIL, *IP, *SNA, *NONE




Remote Local Remote System Network

Opt Location Name Network ID Status Status

BRMSSYSB APPN Online Active

BRMSSYSC APPN Online Active

Enhancements to Change Network Group (7.1)





Communication method : *AVAIL *AVAIL, *IP, *SNA, *NONE




-----BRMS Media Information-----

Remote Local Remote Local -------Remote-------

Opt Location Name Network ID Receives Receives Overrides

BRMSSYSB APPN *LIB *NONE *NO

BRMSSYSC APPN *NONE *NONE *NO

Enhancements to Change Network Group (cont)


• Used for iASP Flash Copy

• Allows iASP to be Flashed Copied, Connected to Another System in BRMS Network and Saved

• Once Save Complete, History Sent to Defined System

• Ownership of History can be Changed to Source System allowing Cumulative Saves on the Source System

iASP Distributed History (7.1)


• BRMS Maintenance (STRMNTBRM) Enhancements Include:

– More Concurrent Maintenance Allowed

– Warning when Volumes in Use and Cannot be Moved

– Volume Move Report (QPIAVMS) Warning

– Automatic hold BRMS Jobs Wanting to use Files Maintenance is Using

• Messages

– BRM6714 - Current job being held by maintenance job

– BRM6715 – BRM restricted procedure started

– BRM6716 – BRM restricted procedure ended

BRMS Maintenance Enhancements (7.1)


• PRTMOVBRM TYPE(*NEXT) Shows Future Movement of Media

• Select Future Date on Second Value on Select dates (SLTDATE) Parameter

Media Movement Planning Report (7.1)


File . . . . . : QP1APVMS Page/Line 8/11

Control . . . . . Columns 1 - 130

Find . . . . . .

*...+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....8....+....9....+....0....+....1....+....2....+....3

Next Scheduled Volume Movement

From location . . . : VAULT To location . . . . : TS7650

Volume To Creation Expire Move Move Container From Volume

Serial Slot Date Date Policy Date Container Slot Slot System Identifier

BRM001 2 3/04/10 3/30/10 DAILY 3/30/10 *NONE 2 BRMSSYS BRM001

BRM003 3 3/04/10 3/30/10 DAILY 3/30/10 *NONE 3 BRMSSYS BRM003

Total volumes . . . . . : 2

* * * * * E N D O F L I S T I N G * * * * *

Move Media Report - QP1APVMS (7.1)


• Clear Volumes in *ERR Status Without Removing from BRMS

• Available in WEB, GUI and 5250 Emulation

• New Option 9 on WRKMEDBRM

• Changes *ERR Volume to *INZ Status

• Once *INZ Status, Volume can be Re-initialized

– WRKMEDBRM - Option 10

– WRKMLMBRM - Option 5

– INZMEDBRM

Clearing Volumes in *ERR Status (7.1)


Work With Media System: BRMSSYS

Position to . . . . . Starting characters


1=Add 2=Change 4=Remove 5=Display 6=Work with serial set 7=Expire

8=Move 9=Remove volume error status 10=Reinitialize ...

Volume Creation Expiration Move Media

Opt Serial Status Date Date Location Date Class

BRM001 *EXP 03/04/16 *NONE *HOME *NONE ULTRIUM6

9 BRM002 *ERR 03/04/16 *NONE *HOME *NONE ULTRIUM6



WRKMEDBRM – Volume in *ERR Status (7.1)


Work With Media System: BRMSSYS

Position to . . . . . Starting characters


1=Add 2=Change 4=Remove 5=Display 6=Work with serial set 7=Expire

8=Move 9=Remove volume error status 10=Reinitialize ...

Volume Creation Expiration Move Media

Opt Serial Status Date Date Location Date Class


BRM002 *INZ 03/04/16 *NONE *HOME *NONE ULTRIUM6



Volume Changed to *INZ Status (7.1)


• Media Marked for Duplication Will Not Expire

• Warning Message in Media Expiration Report (QP1AEP)

– Pending volume duplication, cannot expire

• Protects Physical and Virtual media

• WRKMEDBRM - Option 7

– Posts BRM0010 Message

Protection of Media Marked for Duplication (7.1)


• BRMS Supports New POSITION Parameter on RSTLIB, RSTOBJ and RST Commands

• Done Automatically by BRMS

• Requires Object Level Detail be Saved

– *YES, *OBJ or *MBR on Save Item

• Very Significant Performance Improvements

– For Example: Restoring Last Object from 1.1 million IFS File Save went from 22 minutes to less than 3 minutes

• Not Supported on WRKMEDIBRM Option 7,7 (Libraries)

• Not Supported on WRKMEDIBRM 9,9,7,7 (IFS)

BRMS Recovery Time Enhancement (7.1)


• *COMPATIBLE Special Value Supported on ALWOBJDIF Parameter

• Behaves like ALWOBJDIF(*ALL) in Combination with ALWOBJDIF(*FILE) for Database Files

• FINALLY a Single Value that Does What You Usually Need

BRMS Supports *COMPATIBLE for ALWOBJDIF (7.1)


• Running Non-BRMS Saves with Non-BRMS Volumes

• System Installed with BRMS

• Job will NOT End if BRMS Volume Loaded

• BRMS will Post BRM1730 Message Giving Option to Load Non-BRMS Volume

Running Non-BRMS Saves (7.1)


BRMS Support via Optical Support

• 32 byte Volume Ids

• Volume selection done upfront

RDX Cartridges for Low End Performance (Faster than DAT Tape)

• Capacity 160 GB – 1 TB per Removable Cartridge

• Native Attach with 7.1 TR5 (USB or SATA)

• 6.1.1 PTFs for SATA only

• SATA Dock in either 5.25” internal (SATA or USB) or external USB

• Cartridges Have 30+ years of Reliability and Rugged

• Never Have to Clean the Drive!

BRMS and RDX Removable Media Devices Support


The central “Enterprise System” (HUB) pulls important information from systems (NODES) defined in its “Enterprise” network. From this information, specific notifications, verifications and various other functions can be made and help an administrator manage the health of their BRMS backups/recoveries from one central server. Very beneficial for those customer environments where there are networks of systems.

Central

“Enterprise System”

New BRMS Enterprise Function


OR

BIG! BRMS Network

Collects

One BIG BRMS network

Central


Multiple BRMS networks

Central


BRMS Network 1BRMS

Media

Database

BRMS

Media

Database

BRMS

Media

Database

iSeries

A

iSeries

B iSeries

C

BRMS Network 2BRMS

Media

Database

BRMS

Media

Database

BRMS

Media

Database

iSeriesA

iSeriesB iSeriesC

BRMS Network 3BRMS

Media

Database

BRMS

Media

Database

BRMS

Media

Database

iSeries

A

iSeries

B iSeries

C

Collects

Collects

Collects


No Green Screen – IBM Navigator for i (Web) or IBM System Navigator (GUI) 7.1 and Higher

Central


- BRMS Hub and Node Systems Require BRMS Licenses

- Hub System Require BRMS Network Feature and BRMS Advanced Feature Licenses

- Required PTFs for Systems in BRMS Enterprise Network

- i 7.1 - SI47935 Note: For this release, language specific PTFs applied for each secondary language on the system

- V6R1 - SI47934

- V5R4 - SI47933

BRMS Enterprise Function


–

How do I access the BRMS Enterprise function?


When selected, Enterprise Services will display the Hub Center panel. The Hub Center displays the Nodes that are in the Enterprise Network. Initially the Enterprise Network will not contain any Nodes. Use the Add button to add Nodes.

–

How do I add a Node to the BRMS Enterprise Network?


Once a Node exists in the Enterprise Network, the systems that are currently in that Nodes current BRMS Network can be quickly added to the Enterprise Network by selecting the Add all systems in the BRMS network option on the pop-up menu for

the Node.

How do I quickly add all systems in a BRMS network?


What’s a Node look like?


What’s a Node look like? (Continued )

Note: Report definitions, Backup status, and BRMS log will be shown later


What’s a Node Group?

Used to group similar nodes to have similar behavior.


What’s a Node Policy?

Each Node has an associated Node Policy. The Node Policy defines properties that can be shared between multiple Nodes. Each Node can reference the Node Policy for any of its properties.


What’s a Node Policy? (Continued)


What’s a Report Definition?

Report Definitions define how and when a report will be generated for a Node. The Report Definition can be run manually or it can be scheduled to run at defined intervals.


What’s a Report Policy?

Each Report Definition has an associated Report Policy. The Report Policy defines properties that can be shared between multiple Report Definitions. Each Report Definition can reference the Report Policy for any of its properties.


What’s a Contact?

Contacts are users associated with the Hub and Nodes. The Contacts are used for a variety of notifications including reports or errors encountered while generating reports.


What is the Hub Center?

This is the main enterprise panel and can be used as the BRMS Dashboard to find out information about all the nodes.


What is the Backup Status?

Control groups are now monitored and results are stored in a new file.


What is the Backup Status? (Continued)

Results include if successful or not, amount of data, objects not saved, etc..


What is the BRMS log?

BRMS logs can be viewed from the central system for any node!


What is the BRMS Log? (Continued)

Results include joblog messages, etc. Filtering can also be used on messages, etc.


What about the Reports?

Reports that are generated by BRMS using the STRRCYBRM and STRMNTBRM commands can be managed by Enterprise via Report Definitions.

They can be scheduled to run and/or can be run directly when needed (as shown below)


How do I view the Reports?

Reports that were generated by Report Definitions can be viewed from the HUB Center as shown below.


How do I view the Reports? (Continued)

Reports that generated by the Report Definitions can be viewed from the HUB Center as shown below.


How do I use the Reports?

Reports that generated by the Report Definitions create Report Output…so you can view the output in detail. They can be viewed/printed in pdf format.


How do I use the Report Outputs?

They can be viewed/printedin pdf format.


Output!

UP NEXT...



• BRMS Enterprise Enhancements

• ASYNCBRING Parameter – Faster IFS Saves

• Setting Spooled File Expiration Date Enhanced Option

• Object Omits Support

• Save by Library Size – SORT Parameter

• Incremental Save of Spooled Files

• Online Domino Backups – New Weekly Activity Types

• ABNENDDLY on ENDSBS to Force Restricted State

• Automatically IPL System on Restricted State Failure

• STRBKUBRM Auto Restart for Abnormal End

• Saving to *SAVF in IASP

• Use All Tapes Evenly in BRMS

• Recovery Report Showing Deleted Libraries – SHWDLTLIB Parameter



– List of the nodes and how many failed backups each have had.

Failed Backup Support!


– To list all the failed backups so can do “debug” on

Failed Backups Include (Selection) Support!


– From list of each failed one

Can display BRMS log or Backup History or Failed History

Failed Backups – Lists the backups that failed


PRTRPTBRM support on reports


Auto Refresh on the Hub’s node status (dashboard) - Via new Q1ABRMENT enterprise subsystem


ASYNCBRING parameter to improve IFS backup performance (Backup Policy)


ASYNCBRING parameter to improve IFS backup performance (Control Group Attribute)


ASYNCBRING parameter to improve IFS backup performance (Navigator for i)


Enhanced spool file expiration date during backup(Spool file list expiration view (WRKLBRM))*CRTDAT better than *SAVDAT as date will not change


Enhanced spool file expiration date during backup(Manage lists Navigator for i)


BRMS object list (Object Omit and Attribute support)(Can now exclude objects even based on attribute)


BRMS object list (Object Omit and Attribute support)(Navigator for i)


Control group can sort by library size


Control group can sort by library size (Navigator for i)


Incremental Support for Spoolfile Lists


• More info: http://www-03.ibm.com/systems/i/support/brms/domdaos.html

• Can now separate out the domino databases (nsf files) from the directory attach object services(DAOS) objects (nlo files)

• Can now control incremental and full on each type of Domino

– Mixed mode

• New activity type

– N for full of nsf files and incremental of nlo files (default)

– D for incremental of nsf files and full of nlo files (default)

– I and F remain the same…both nsf files and nlo files get either full or incremental

Domino DAOS new separation support


Domino DAOS new separation support (con’t)


Domino DAOS new separation support (con’t)(Navigator for i)


• Here is a backup with the incrementals separated (along with a full)

Domino DAOS new separation support (con’t)


Help for getting to restricted stateNew field in System Policy


Help for getting to restricted stateNew field in System Policy


Help if can’t get to restricted stateAwareness Chart – IPL on CPF1099


Auto-restart on abnormal ends of STRBKUBRM


Support for saving to *SAVF in IASP ( 33-99 only)(Must use I-ASP name)


• Switched to Pick Oldest Create Date and then Volume Uses

• PTFs

– IBM i 7.1 - SI43868

– IBM i 6.1 - SI43869

– V5R4 - SI43862

Use All Tapes Evenly in BRMS


Can turn off deleted libraries on recovery report(SHWDTLLIB)

UP NEXT...



• BRMS Web Client

– Better Filtering and Usability (Dojo)

– Main Panel – Multitask Navigational Tree

– Improved Backup List Editing (Sorting)

– Improved Include Panel Selection (on OK)

• BRMS Server

– PRTRPTBRM FROMSYS Support

– INZBRM Network Checker Options

• Modernization of Storage Tiering using BRMS Migration

– IFS Lists Supported

– SSD to HDD Support

– IASP Support

• CHGMEDBRM Movement Support of One Volume

• SAVBRM Pattern Parameter Support



Example of System Policy with DOJO


Example of Multi-task Navigation in 7.3

This will allow quicker launches into the BRMS client area that you wish to go.


Example of Improved Backup List Editing


PRTRPTBRM FROMSYS - Help Text


INZBRM *VFYSYS, *VFYNET, *VFYENT - Help Text


Modernization of Storage Tiering via BRMS Migration

(Note: PTF’d Back to 7.2 in December 2015 PTF)


High Level View Previous Migration Support

ASP01 USER ASP

Library Support

LIB A LIB A

If LIB A isn’t used enough based on customer choices, LIB A can get moved down to USER ASP or vice versa if use increases.


ASP01 User ASP I-ASP

SSD

HDD

SSD

HDD

SSD

HDD

Can move PF/LF files withinan ASPBetween SSD(Fast) and HDD(Slow)

NEW I-ASP SUPPORT

IFS now supported!

Library Support!

High Level View


Migration Support for I-ASP

• I-ASP can be marked migration eligible and support *LIB, *LNK, and *OBJ control group entries.

• Available in 7.2 using command:QSYS/CALL QBRM/Q1AOLD PARM('SETMGRELIG' 'asp-name'

'asp-class' 'Y')


• Migration (*MGR) list support for link lists (*LNK)

Migration Support for IFS


Support for IFS - Restrictions

• Only first level directory path names allowed. Example: ‘/dirName’• Only one directory entry allowed in an *LNK list.• IBM product directories (directories starting with /Q) not

supported• Non IBM product directories not supported:

//tmp/dev

• Directory tree contents must all be in the same file system.


Support for IFS- Report Output

• Displays *LNK list control group entry statistics as the Migration *LNK list name


Support for Object List Migration

• Migration (*MGR) list support for object lists (*OBJ)


Support for Object List Migration - Restrictions

• Moves objects within same ASP or IASP (SSD)• Specific library names (special values and generics not

supported)• Only supports DB files (Object type *FILE and Object Attribute

PF or LF) • Specific member names (no generics)


Support for Object List Migration – Report Output

Report Output• Displays *OBJ list control group entry statistics on first line• Breaks out individual objects from the migration object list


Example of all 3 in Migration Control Group


Putting It All Together

Could migrate a library then move a file from HDD to SSD in that library!


MGRBRM support for I-ASP, *LNK and *OBJ

Option to force migration when needed

This would force PF and LF files to SSD in object list FREDDY


MGRBRM for *LNK

Force the directory in link list FREDDY to IASP00


CHGMEDBRM – Move – Location/Container


SAVBRM Support of Name Pattern


BRMS has a Web page/Wiki!

#COMMONS17www.common.org

Don’t Forget Your Session Surveys

• Sign in to the Online Session Guide (www.common.org/sessions)

• Go to your personal schedule

• Click on the session that you attended

• Click on the Feedback Survey button located above the abstract

Completing session surveys helps us plan future programming and provides feedback used in speaker awards. Thank you for your participation.

http://www.common.org/sessions

Documents

Backup/Recovery on IBM i Including Virtual Tape and …schd.ws/hosted_files/commons17/86/Common 2017... · SNA Low Data Compression ... IBM Rochester Lab Services Available to help