Tips and Techniques for Shrinking Backup/Recovery Windows on IBM i

Transcription

1 Tips and Techniques for Shrinking Backup/Recovery Windows on IBM i Common Conference 2017 Debbie Saugen Director, Business Continuity Services debbiesaugen@helpsystems.com HelpSystems LLC. All rights reserved. All trademarks and registered trademarks are the property of their respective owners.

2 Shrinking the Backup/Recovery Windows The Big Question: "How Fast Can I Backup and Recover?"

3 Shrinking the Backup/Recovery Windows The Answer: "It Depends!" Factors Influencing Backup/Recovery Performance Hardware Tape Devices Tape Device Attachment Card Number of DASD Units Data Spread Across Workload Type Large Files User Mix Source Files IFS (Domino) Data Compression, Data Compaction and Optimum Block Size (USEOPTBLK) Use System Defaults Best Performance Main Storage Memory and Pool Sizes Save of Access Paths Improves Recovery Performance

4 Overview of Factors Influencing Save Performance Target device technology + Connection technology + Bus and HSL speed + Disk configuration + CPU and memory + Data Type (size and quantity) = GB per hour saved or restored

5 The Backup/Recovery Challenge Minimize backup window (daily, weekly, etc.) Minimum complexity Maximum coverage Transaction recovery Minimum recovery time Minimum complexity

6 Shrinking Your Backup/Recovery Windows Latest Tape Technology Saving to Save Files Saving to Virtual Tape SAVSYSINF and RSTSYSINF Concurrent/Parallel Save/Restore Alternatives for Minimal Downtime Saves Save-while-active External Disk FlashCopy High Availability Software Online Lotus Servers Backup Omit Non Critical Data Archive Historical Data Reorganize Files Recovery Enhancements Logical/Physical File Recovery (6.1) Fast Restore of Single Object (7.1) Recovery for Journals (7.1 TR7) Configuring IASPs (7.2) Recover Authorization Lists in QSYS (7.3)

7 Latest Tape Technology

8 Current IBM Tape Product Line for IBM i LTO Family Enterprise Family TS3100 TS3200 TS3310 TS1140/TS1150 TS2360 TS2900 TS2260 Low cost High capacity Fast streaming operations High performance High capacity Industrial strength Fast streaming and start/stop operations

9 LTO 7 Tape Highlights Seventh Generation LTO Tape Drive 6 TB capacity (up to 15 TB at 2.5:1 compression) 300 MB/sec native data transfer rate (750 MB/sec with compression) Full height and half height form factors Full height: Fibre Channel at 8 Gbit/sec Half height: SAS at 6 Gbit/sec and Fibre Channel at 8 Gbit/sec Capability to Read/Write Ultrium 6 and read Ultrium 5 cartridges Features Encryption, WORM Media partitioning Supported in IBM tape automation systems 3-year warranty standard in most countries

10 LTO 7 Tape Drives - IBM i Requirements IBM LTO 7 on IBM i Supported on 7.1 and 7.2 only Note: With current IOA limitations, users will see very little, if any performance improvement compared to LTO 6 drives. Capacity will however be improved. OS PTFs required MF60438 BRMS MF SI SI57831

11 GB/HR GB/HR LTO6 Half High Performance on IBM i GB Source File Save Operations Save Operations Fiber attached , Fibre , Attached LTO4, LTO5, and 3592E07 TS1140, LTO6 1 Directory Many Objects Many Directories Many Objects 12 GB User Mix Domino (offline) 64 GB Large File 320 GB Large File Restore Operations Operations Fiber Fibre attached Attached , , LTO4, LTO5, and 3592E07 TS1140, LTO6 1 GB Source File 1 Directory Many Objects Many Directories Many Objects 12 GB User Mix Domino (offline) 64 GB Large File 320 GB Large File LTO B 4Gb LTO5 IOA TS D 8Gb IOA LTO LTO B 4Gb IOA 3580 LTO D 8Gb IOA 3592 TS1140 E07 577D 8Gb IOA LTO6 577D 8Gb IOA 3592 E07 577D 8Gb IOA D 8Gb IOA LTO6 Save Usermix 86 MB/sec Large File 500 MB/sec LTO6 Restore Usermix 80 MB/sec Large File 500 MB/sec Notice that LTO6 is almost as fast as TS1140 POWER7 and 8 Gbit fibre is needed to reach the largefile speeds

12 LTO6 Performance on IBM i LTO4 LTO5 TS1140 LTO6 Speeds shown are in GB/hr 9117-MMA 16 Way With 200 DASD 9179-MHC With 720 DASD On 574E IOAs EXP 12 3Gb SAS Drawers 9179-MHC With 720 DASD on 574E IOAs EXP 12 3Gb SAS Drawers 9179-MHD With 288 DASD on 57B5 IOAs Gb SAS Drawers B 4Gb IOA D 8Gb IOA 3592 E07 577D 8Gb IOA D 8Gb IOA SAVE 1 GB Source File Directory Many Objects Many Directories Many Objects GB User Mix Domino (offline) GB Large File GB Large File RESTORE 1 GB Source File Directory Many Objects Many Directories Many Objects GB User Mix Domino (offline) GB Large File GB Large File POWER7 and 8 Gbit fibre is needed to reach the largefile speeds shown

13 TS1140 Enterprise Tape Drive (3592-E07) Native Data Rate 250 MB/sec; 650 MB/sec with max compaction Dual 8 GB fibre ports Fits in TS3500 or standalone NOT supported in TS3400 or 3494 Upgrades TS1130 (3592-E06) can be upgraded to TS1140 TS1130 (3592-EU6) CANNOT be upgraded to TS1140 On IBM i Must attach to an IOPless fibre card Hence POWER6 and at a minimum

14 TS1140 Media Overview Introducing three new enhanced Barium Ferrite (BaFe) particle media types JC media: 4.0 TB IBM Enterprise Advanced Data Tape NEW Extended JY media: 4.0 TB IBM Enterprise Advanced WORM Tape NEW Ext WORM JK media: 500 GB IBM Enterprise Economy Data Tape NEW SHORT This media is planned to be re-usable on future generation drives. This media CANNOT be used in previous generation drives Firmware patches will be available for TS1120 / TS1130 so they will give an error message if you accidentally load one of the new tapes Previous generation media (JB/JX) *can* be used in TS1140 At the previous generation of format Or it can be reformatted to the new media density Original Generation Media (JA/JW, JJ/JR) cannot be used in TS1140

15 TS1150 Tape Drive Overview 5th generation of 3592 enterprise tape drive Barium Ferrite media types with up to 10 TB native capacity Re-Writable and Write Once Read Many (WORM) cartridge at 10 TB Economy cartridge available at 2 TB 360 MBps native drive data rate Dual 8Gb fiber channel interfaces with 700 MB/s max compressed data rate Supports data partitioning, data encryption and key management Differentiated media Media types usable at higher capacity on future drive generations Media re-use of existing JC/JY/JK media types with automatic upformat support Two models 3592-E08 for TS3500 and racks 3592-EH8 HD2 compatible format for TS4500 MES upgrade for TS1140 available (model conversion) 3592-E08

16 TS1150 Tape Drive Overview Attaches to Open systems only IBM Power Systems, System i, System p, System x Selected HP and Oracle servers Servers running selected versions of Microsoft Windows and Linux Supported in IBM TS3500 and TS4500 tape libraries IBM racks Supports IBM Linear Tape File System

17 TS1150 Tape Drives IBM i Requirements Attaches to IBM i IOPless only V6R1M1 (IBM i 6.1.1) and above Supported in IBM TS3500 and TS4500 tape libraries PTFS Required V6R1M1 - MF58975 If using BRMS, SI53304 or superseding PTF IBM i MF59046 If using BRMS, SI53305 or superseding PTF IBM i MF59015 If using BRMS, SI53306 or superseding PTF

18 TS1150 Tape Drive Summary Designed to protect existing investment in IBM tape Full (read/write) backward compatibility with the previous generation Supported in TS3500 and TS4500 libraries Designed to provide seamless integration and support Attachment to IBM systems and other open systems platforms Attachment to native Fabric and FC-AL SANs Designed to meet highest workload demands with the lowest TCO Big data and analytics Social Mobile Cloud

19 3592 JD/JZ/JL Media Three cartridge models: JD: 10 TB IBM Enterprise Advanced Data Tape JZ: 10 TB IBM Enterprise Advanced WORM Tape JL: 2 TB IBM Enterprise Economy Data Tape Designed to be reusable at higher capacities in future drive generations Not usable in earlier drive generations Cartridge options available: initialized and labeled labeled not initialized or labeled Read / write up to 360 MB/s, native, sustained, and up to 700 MB/s (at 3:1 compression)

20 3592 Cartridge Media *Native performance = up-formatted reuse TAPE CARTRIDGES With the TS1150 drive With the TS1140 drive With the TS1130 drive With the TS1120 drive Generation / Model Four JD/JZ (WORM) Four JL (short JD) Three JC /JY (WORM) Three JK (short JC) Two JB / JX (WORM) Tape Format Capacity Performance* Capacity Performance* Capacity Performance* Capacity Performance* TS TB Up to 360 MBps TS TB Up to 360 MBps TS TB Up to 300 MBps 4 TB Up to 250 MBps TS GB Up to 300 MBps 500 GB Up to 250 MBps TS1140 Not supported Not supported 1.6TB Up to 200 MBps 1TB Up to160 MBps TS1130 Not supported Not supported 1TB Up to160 MBps 1TB Up to160 MBps TS1120 Not supported Not supported 700GB Up to 104 MBps (read-only) 700GB Up to 150 MBps 700GB 104MBps One JJ (short) / One JR (short WORM) TS1130 Not supported Not supported 128 GB TS1120 Not supported Not supported 100 GB Up to 143MBps (read-only) Up to 104MBps (read-only) 128GB Up to 143 MBps 100GB Up to 143 MBps 100GB 104MBps 3592J1A Not supported Not supported 60GB Up to 50MBps (read-only) 60GB Up to 71 MBps 60GB 50MBps TS1130 Not supported Not supported 640 GB Up to 143 MBps (read-only) 640GB Up to 143 MBps One JA / JW (WORM) TS1120 Not supported Not supported 500 GB Up to 104MBps (read-only) 500GB Up to 143 MBps 500GB 104MBps 3592J1A Not supported Not supported 300GB Up to 50 MBps (read-only) 300GB Up to 71 MBps 300GB 50MBps

21 3592 JC Media With TS1150, TS1140 media can have standard use Read/write JC/JY at 4 TB or JK at 500 GB in Gen 4 format Three cartridge models can be up-formatted with better performance JC: from 4 TB to 7 TB JY: from 4 TB to 7 TB JK: from 500 GB to 900 GB Data rate increases to 300 MBps Earlier generation media is not supported

22 Performance Impact of Tape Device and Media Errors Tape Device or Media Errors During Save/Restore Extra Error Recovery High Performance Tape Devices Very Costly to Performance Poor Save/Restore Performance Analyze Error Logs and Media Statistics Rule Out Poorly Performing Tape Device or Media

23 Saving to Savefiles Savefile Benchmark Performed in the Most Favorable Environment to Achieve Maximum Save Rates 24-way GB Main Store 1080 DASD Units **Performance Rates Achieved will Depend Upon Available Resources V5R1 Save Performance 135 GB/hr for User Mix Data 170 GB/hr for Large Files V5R2 and Higher Save Performance 200 GB/hr for User Mix Data 480 GB/hr for Large Files 2757 IOA DASD 250 GB/hr for User Mix Data 1000 GB/hr for Large Files

24 Virtual Tape Support for i5/os (V5R4) CRTIMGCLG (2) Up to 256 virtual tape volumes ADDIMGCLGE (3) LODIMGCLG (4) CRTDEVTAP Virtual Tape Device Save (1) Restore Disk Any ASP or iasp Duplicate to media, switch or FTP to another system

25 Virtual Tape Support for i5/os 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

26 Virtual Tape Support for i5/os Considerations Additional DASD Requirements No Install from SAVSYS Virtual Volume D-IPL Only from Media May Not Be Faster Data Compaction Not Supported Data Compression Support DTACPR(*YES) Parameter on Save Commands (Default is *NO) SNA Low Data Compression Significant Performance Impact Tape Technology System Configuration and Environment

27 Virtual Tape Support for i5/os Implementation of Virtual Tape Included in Base i5 Operating System Configures on 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 & 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

28 What Does the TS7650 ProtecTIER Do? IP Replication Minimized bandwidth since data is de-dup d before sending Ohio TS7650 IBM i Optional duplication to physical tape (at local or remote site) TS3500/ TS4500 New York IBM i Virtual Tapes TS7650 C B A Disk What is DeDuplication? A A B A C B C B A C B A Local Saves to Virtual Tape with De-dup A A B A C B A A B A C B

29 TS7650 ProtecTIER on IBM i Where does it fit? IBM i TS7650 IP Replication For customers who are moving their tapes offsite via truck today and would like a safer, more automated solution TS7650 TS7650 IBM i De-Duplication For customers who want to store a lot of data online such that de-dup reduces their costs C B A C B A A A B A C B A A B A C B Need to Review the Cost Benefit Analysis to make sure it s a fit 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, icluster, MIMIX, itera, QuickEDD, etc) External Disk Copy Services IBM i Geographic Mirroring (formerly Cross Site Mirorring or XSM) /

30 Protectier Virtual Tape on IBM i Important Points Overall Speed and Single Stream Speed Virtual Tape Devices shine when they can run a large number of medium-speed backup streams. IBM i customers sometimes need a small number of very fast streams. Be sure to understand the single stream performance provided to make sure your Virtual Tape Device will meet your needs IBM i Single Stream performance depends on the VTL disk type/amount MB/sec per stream MB/sec per stream MB/sec per stream ProtecTIER Backup Scheduling LPAR 11 pm 11:30 pm Mid-nite 12:30 am 1 am IBM i 01 IBM i 02 IBM i 03 IBM i 04 Total MB/Sec Draw a Backup Gantt Chart to check the MB/sec and # streams at your peak MB/sec per stream ProtecTIER Gateway full box save capacity is 2500 MB/sec with 2 DD5 nodes Current Technology Physical Drives run at MB/sec per stream (user mix / largefile) Non-Infinite Resources Although virtual tape is flexible, remember the resources aren t infinite

31 GB per hour Low End Tape Performance Benchmarks See Chapter 15 of the Performance Capabilities Reference manual for benchmark details. This publication can be found at the following url: Legend Source File IFS 1:m User Mix Large File IFS m:m Domino Offline Linux NWS Offline 250 QIC Family VXA Family LTO HH GB/hr 150 4mm DAT 72 Performance Large file 22 GB/hr GB/hr 34 GB/hr 41 GB/hr 82 GB/hr 0 QIC 30 (SLR 60) QIC 50 (SLR 100) VXA 2 VXA 320 HH LTO-2

32 GB per hour High End Tape Performance Benchmarks See Chapter 15 of the Performance Capabilities Reference manual for benchmark details. This publication can be found at the following url: Legend Source File IFS 1:m User Mix IFS m:m Large File Domino Offline LTO Family 359x Family Notice Updated LTO4 benchmarks on EXP24 & IOPless: Usermix 65 MB/sec (234 GB/hr) Large file MB/sec (890 GB/hr) TS1130 is the same as TS GB/hr Disk Linux NWS Offline 1700 GB/hr Notice User mix speed is not increasing 890 GB/hr LTO4 LVD SCSI tops out at 140 MB/sec (500 GB/hr) (ie LTO3 speeds) 890 GB/hr GB/hr GB/hr 142 GB/hr 365 GB/hr Note: the 1st Savefile & Virtual Tape Benchmarks used 924 arms in the Virtual Tape ASP. Smaller environments should review the arm-based Benchmarks on next page LTO2 - fibre LTO3 - fibre (5704) LTO4 - fibre (IOPless) 3590H fibre 3592J fibre TS1120 on 4Gbit fibre Savefile on fc 2757 Integrated Virtual Tape

33 Influence of Workload Type Source User Mix Large File IFS Domino (offline) Linux (offline) Domino Online Saves... Plan on: LT02: 100 GB/hr TS1120: 183 GB/hr SLOW! SLOW! Source files User Mix (12 GB) Large File (8 GB) 1 Dir / Many Obj Domino Offline User Mix (3 GB) Large File (4 GB) Large File (16 GB) Many Dir / Many Obj Linux NWS

34 GB/HR GB/HR V5R4 Integrated Virtual Tape Benchmarks (varying disk arms) i570 8-way SYSBAS Production Data 312 * 70 GB EXP24 arms User ASP Virtual Tapes ASP size ranges from * 70 GB EXP24 arms Separate benchmarks indicate that 12 arms in the production ASP are plenty to send the data to tape / virtual tape, so SYSBAS has plenty of arms User Mix Virtual Tape Scaling (SAVE) Write to Virtual Tape RAID5 SAVE RAID6 SAVE MIRRORING SAVE Large File Virtual Tape Scaling (SAVE) Write to Virtual tape RAID5 SAVE RAID6 SAVE MIRRORING SAVE Also see the corresponding restore benchmarks: IBM i Performance Capabilities Reference Manual (PCRM), section

35 GB/HR GB/HR V5R4 Physical Tape Benchmarks (varying disk arms) i570 8-way SYSBAS Production Data 312 * 70 GB EXP24 arms User ASP Virtual Tapes ASP size ranges from * 70 GB EXP24 arms LTO3 User Mix Saves Large File Save RAID5 SAVE RAID6 SAVE MIRRORING SAVE RAID5 SAVE RAID6 SAVE MIRRORING SAVE From: IBM i Performance Capabilities Reference Manual (PCRM), section

36 Estimating Performance of a New Tape Drive To Estimate the Performance of a new drive: Tape Drive User Mix Large File LTO2 43 MB/sec 100 MB/sec LTO3 60 MB/sec 140 MB/sec LTO4 65 MB/sec 247 MB/sec How do you figure out how fast your current drive is running? Measure a full system backup where you know your total amount of data * or * Use the i 6.1 BRMS Backup Statistics Report 3592J 51 MB/sec 104 MB/sec TS MB/sec 250 MB/sec Backup Statistics Report Figure out how fast the current drive is running Eg LTO2 at 40 MB/sec Match it to the benchmarks for the current drive Eg User Mix Read off the performance for the new drive for that benchmark Eg LTO4 65 MB/sec Ctlg Start/End Duration Total GB MB/ sec CtlgA 3am 2: CtlgB 6am 1:

37 Hardware Choices for Tape Performance This chart dates back to POWER5 days. On newer boxes our main problem is older / slower tape adapters and SAN switches CPU Power Tape Adapters HSL User Mix: 1.3 CPUs per tape drive Large File: 0.5 CPUs per tape drive 5704/5761: 2/4 Gbit fibre LVD SCSI Memory Adapter Placement User Mix: 1 GB per save Large File: ½ GB per save HSL 64 bit slots High Speed Buses Disk HSL Placement User Mix: 50 arms, 15K RPM Large File: 40 arms, 15K RPM Spread across HSLs Add more HSLs if needed On EXP24 disk or newer, 6-12 disk arms are enough to run an LTO3 drive at rated speed

38 Faster SAVSYS, Concurrent & Parallel Save/Restore

39 Faster SAVSYS Backup Omit Parameter on SAVSYS Omits SAVCFG and/or SAVSECDTA OMIT(*CFG) OMIT(*SECDTA) OMIT(*CFG *SECDTA) Must Run SAVCFG/SAVSECDTA Regularly System not Required to be in Restricted State

40 SAVSYSINF and RSTSYSINF Commands (V5R4) Save System Information (SAVSYSINF) Command Performs a Partial Save of Data Saved by Save System (SAVSYS) Command Cumulative Save Since Last SAVSYS Restricted State Not Required SAVSYS Requires Restricted State Saves System Reply List Entries Certain System Values Some System Values are Not Saved Not Required for System Recovery Service Attributes Network Attributes PTFs for 5722SS1 and Applied (TEMP or PERM) Since Last SAVSYS All Group PTFs All PTF Cover Letters and Loaded PTFs Copied into *SERVICE

41 SAVSYSINF and RSTSYSINF Considerations Base SAVSYS Required SAVSYSINF Not Replacement for SAVSYS *ALLOBJ or *SAVSYS Special Authority Required Can t be Used For Restoring to Another Existing System System Upgrades or Migrations Intended for Customers Who Can t Bring System to Restricted State for SAVSYS Can t Take Down Time for SAVSYS PTF Save Files Must Remain on System Until Next SAVSYS Do Not Run Delete Program Temporary FIX (DLTPTF) Command Unless Right Before SAVSYS Right After SAVSYS Installing PTFs Default is NOT to Restore Save Files Change System Default CPYPTF(*YES) on CHGSRVA Command or Use CPYPTF(*YES) in INSPTF Command Consistently Increases System Recovery Time and Complexity SAVSYS and SAVSYSINF Needs to be Recovered RSTSYSINF Additional Step per Backup and Recovery Checklists

42 SAVSYSINF Backup Strategy After Base SAVSYS, Perform these Commands to Save System Changes SAVLIB LIB(*IBM) SAV OBJ(('/QIBM/ProdData') ('/QOpenSys/QIBM/ProdData')) UPDHST(*YES) SAVSYSINF Commands to Save User Data SAVSECDTA SAVCFG SAVLIB LIB(*ALLUSR) SAVDLO DLO(*ALL) FLR(*ANY) SAV OBJ(('/*') ('/QSYS.LIB *OMIT) ('/QDLS *OMIT) (/ QIBM/ProdData *OMIT) (/ QOpenSys/QIBM/ProdData *OMIT)) UPDHST(*YES)

43 Add Additional Tape Devices for Concurrent Saves/Restores Example 1 Example 2 Job 1 Job 2 Job 1 Job 2 SAVLIB LIB(*allusr) OMITLIB(m* n* o*...z*) DEV(TAP01) SAVLIB LIB(*allusr) OMITLIB(a* b* c*...l*) DEV(TAP02) SAVCHGOBJ (A* B* C*) LIB(MYLIB)) DEV(TAP01) SAVCHGOBJ OBJ(M* N* O*) LIB(MYLIB) DEV(TAP02) 3590 x x 2

44 Concurrent Saves and Restores Multiple Concurrent Saves against Single Library SAVOBJ, SAVCHGOBJ and QSRSAVO API can run Concurrently against Same Library Break Up Large Libraries to Save Concurrently to Multiple Tape Devices SAVCHGOBJ OBJ(A* B* C*...L*) LIB(NAME) SAVCHGOBJ OBJ(M* N* O*...Z*) LIB(NAME)

45 Concurrent Saves and Restores Generic Values on OMITLIB SAVLIB/SAVCHGOBJ Support Generic Values on OMITLIB Parameter Omit Groups of Libraries: OMITLIB(TEMP*) SAVLIB LIB(*ALLUSR) using 2 Tape Devices Concurrently SAVLIB LIB(*ALLUSR) OMITLIB(#LIBRARY A* B*...L*) SAVLIB LIB(*ALLUSR) OMITLIB(M* N*...Z*)

46 Concurrent Saves and Restores with BRMS Run Multiple BRMS Backup Control Groups Concurrently Submit Multiple Save/Restore Jobs to Multiple Tape Devices Reduces Save/Restore Times User Balances the Control Group Data so Jobs end at Same Time

47 Add Additional Tape Devices for Parallel Saves and Restores Job Job V4 BRMS Backup Control Group Large Library V5 BRMS Backup Control Group *ALLUSR 3590 x x 4

48 Parallel Saves and Restores Parallel Saves (V4R4 and higher) Save Large Library, Large Object or List of Large Objects to Multiple Tape Devices in Parallel "Spreads Data across Tapes Improves Save Performance for Very Large Objects Not Designed for Small Objects IFS Parallel Save and Restore Support (V5R4) End User Interface with BRMS Same Number of Tape Devices on Save "Recommended" for Restore

49 Concurrent and Parallel Saves and Restores Shrink Backup/Recovery Windows Concurrent Saves and Restores Parallel Saves and Restores Combination of Concurrent and Parallel

50 Parallel Saves and Restores Expanded Parallel Support (V5R1 and higher) Special Values *ALLPROD, *ALLTEST, *ALLUSR, *IBM, *ASP01 - *ASPxx and Generics Supported Objects "Spread" at Full Library Level Restore of Parallel Saves with Special Values in Serial Restore Mode (One Tape Device) Media Library with Multiple Devices Provides Tape Mounting Automation List of Libraries - BRMS Determines Best "Spreading" (Object or Full Library Level)

51 Alternatives for Minimal Downtime Saves Save While Active External Disk FlashCopy High Availability Software iaspf lash iasp Part of i5/os no additional charge No extra hardware required Short Quiesce required to get checkpoint Requires 2nd system or LPAR with additional disk and software Short Quiesce or power off required to make FlashCopy depending on the solution implemented Requires 2nd system or LPAR with additional disk, plus an HA software application Least disruptive tape backups Fringe Benefit is the HA Capabilities

52 Save-while-active (SWA) Integrated OS/400 Utility for Save Window Reduction No Additional Hardware or Software Required Virtual Point in Time Copy on Individual Objects and Libraries Allows Granular Restores from Tape as Needed #1. Start of save request. #2. Checkpoint complete - object changes now allowed. #3. Unchanged pages and copied pages are saved to tape. #4. Checkpoint image completely saved to media. End of save request. #5. Results! C2 C3 C1 C2 C3 C1 C2 C3 C1 C2 C3 C1 Objects on system after save. Eric Hess/Sue Baker IBM iseries ATS 2001 Objects in memory to be saved - Get a checkpoint (snapshot) of each object. Original pages copied to temp storage before a change. x x x Copied pages in temp storage are released. Original objects as they were at checkpoi nt are written to tape.

53 Online Backup of Notes Servers

54 Online Backup of Notes Servers Save Lotus Notes Servers While Active Starting with V4R4 No Need to Reach Checkpoint - True Online Backup No Ending Server or Replicating to Another Server for Backup BRMS Handles Recovery Process Allows 24X7 Up Time of Lotus Servers

55 Large Number of Private Authorities Increases SAVSECDTA Dramatically Very Problematic with IFS Files Use Authorization Lists Instead

56 Omit Non Critical Data Test Data Temporary Files Performance Data (QMPGDATA)

57 Archive Historical Data BRMS Advanced Feature Archive Objects to Tape Based On Age Frequency of Use Size Dynamically Recall Database Files, DLOs and Stream files

58 Reorganize Database Files REORG Files on Monthly Set STRMNTBRM RGZBRMDB Parameter to *YES Regular Basis Reorganize BRMS Files Available V5R2 or Higher Ensure No BRMS Activity During Reorg

59 IFS Save Performance New 7.2 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: e?lang=en#/wiki/ibm%20backup%2c%20recovery%20and%20med ia%20services%20%28brms%29%20for%20i/page/overriding%20 the%20asyncbring%20parameter%20on%20ifs%20saves%20to %20improve%20performance

60 Saves After An IPL Save Time Increases up to 30 Percent Save-while-active Checkpoint Time May Increase Why Longer? Paging In of Object Headers Additional Processing First Time Objects Touched After IPL Even Longer if Previous IPL Abnormal Recommendation Avoid Saves Immediately After IPL Touch Objects Between IPL and Save DSPOBJD or DSPFD

61 Track Save Option 21 Backup Times (6.1) New Data Area QSRSAV21 in QUSRSYS Tracks Last 5 Full System Option 21 Backups Shows Command Steps Time Completed Device Used Determine Trends in Full System Backup Times Analyze Where Time is Being Spent

62 SAV/RST Messages (6.1) Prior to V6R1 Always Wondering What s Happening? New in Process Status Messages Started processing xxx objects, completed yyy objects

63 Recovery Performance Enhancements

64 Shrinking the Recovery Window Dramatic Recovery Performance Improvements on IBM i Customers with Multiple Tape Devices using Concurrent/Parallel Restores Have Seen: 32 Hour Full System Recovery Reduced to 12 Hours 22 Hour Full System Recovery Reduced to 8 Hours Recovery Tip for Save-while-active Saves Save Full Objects instead of Changed Objects Recovery Time Reduced Restoring Fulls vs. Fulls and Changes

65 Recovery for Logical/Physical Files (6.1) 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 RMVDFRID DFRID(name) RSTDFROBJ DFRID(name) Restore Deferred Objects Associated with RSTxxx 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

66 Fast Restore of Single Object (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

67 Recovery for Journals (7.1 Technology Refresh 7) 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

68 Configure Independent ASP (IASP) Enhancement (7.2) Configure IASPs During System Recovery New Configure Device ASP (CFGEVASP) Command IBM i Navigatoir No Longer Required during System Recovery Skip the IPL required to Start IBM i Navigator

69 7.3 Recover Authorization Lists in QSYS 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

70 Rapid Recovery for IBM i

71 IBM i Replication...a Rapid Recovery feature that enables you to replicate your applications and data Can achieve recovery time objectives of minutes Protects data to last replicated transaction IBM Site Hotsite Customer Customer

72 IBM i Replication Options You can replicate all or part of your system to a target system at either a hotsite or one of your sites. Customer Site Customer Site Hotsite or Customer Site Customer Customer(s) Site(s) Partitioning Hotsite Or you can replicate all or part of your system to a partition on a target system at a hotsite. This solution enables sharing of resources and achieves a new price point for replication.

73 Remember...Test Your Recovery!! Test Your Recovery to Ensure Your Recovery Performance Objectives are Being Met!! IBM i Save/Restore Performance Measurements Located at:

74 Don t Forget Your Session Surveys Sign in to the Online Session Guide ( 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. #COMMONS1 7