BMC Coordinated Recovery for IMS, DB2 &VSAMRick WeaverDB2 Software Consultant
Today we will discuss….      The need for Coordinated Recovery      What can cause an outage?      BMC Building blocks – s...
Complexity Creep      Relationships within and between unlike DBMSes      Relationships outside the organization          ...
SWPOC Impact      To get a System Wide Point of Consistency, services must be stopped                                     ...
No SWPOC Impact      If your availability requirement is such that you cannot obtain a SWPOC, you have no      consistent ...
What can cause an application outage?    Some events are planned:               Other events are unplanned     - Database ...
The BMC Building Blocks  -       Recovery Management for DB2                  Define Application Recovery Groups, generat...
DB2 Recovery Management Overview               ISPF                       application with DB2 repository tables         ...
IMS Recovery Management Overview               ISPF                       application with repository datasets           ...
VSAM Recovery Management Overview               ISPF                       application with VSAM repository tables       ...
Backing into the Backup Strategy      Determine your local Recovery Time Objective        -    Generally 1-2 hours        ...
Hybrid Copy – No Outage, high speed, low CPU                                             Many Small      A Few Large      ...
BMC COPY PLUS for DB2 Cabinet Copyvs. DB2 9 Copy        -    Copying ERP application with 7,797 tablespaces to tape (IBM 3...
Recovery Interface Process Flow                 Build                     Specify                     Specify         Vali...
Find DB2 Recovery Points                                           Recovery Point found  A  B  C  D  E  F  G  H          U...
Force DB2 Recovery point                                           PIT selected    A    B    C    D    E    F    G    H   ...
Find IMS Recovery Points                                           Recovery Point found  A  B  C  D  E  F  G  H          U...
Force IMS Recovery point                                           PIT selected    A    B    C    D    E    F    G    H   ...
Force VSAM Recovery point                                           PIT selected    A    B    C    D    E    F    G    H  ...
Point in Time Recovery – Physical Backout      The fastest way to get the database to the point prior to the application e...
DB2 Local PIT Recovery considerations•     DB2 recovery groups can range from one object to entire subsystem•     Local Re...
When to Declare DisasterSite-wide calamity - declare                      Data CenterLose Network connectivity – maybe dec...
Coordinated Disaster Recovery - Opportunities      IMS, DB2, & CICS/VSAM allow for ‘online’ copies      IMS, DB2, and CICS...
Recovery Management for DB2Programs and Utilities        -    ARMBTSI                   Insert timestamp into RM reposito...
Backup and Recovery for IMSPrograms and Utilities        -    DRAMS               Capture AMS (Delete/Define) information...
Coordinated Disaster Point –Timestamp based (NO LOCAL SITE OUTAGE)        -    IMS                   Log Switch performed...
IMS Recovery point                                           PiT selected    A    B    C    D    E    F    G    H     Use ...
VSAM Recovery point                                           PiT selected        A        B        C        D        E   ...
DB2 Conditional Restart point                                           UOW 1                                             ...
Coordinated DR Support   Local Site Processes (IMS event driven)Backup IMS & DB2Cat&Dir, libraries,RMGR Repositories      ...
DR Site Recovery procedures  -      IMS                Prepare RECONs                Recover Application databases to DR...
DR RECON Cleanup UtilityCloses open PRILOGsDeletes PRIOLDsCloses open SECLOGsDeletes SECOLDsDeletes SUBSYS records        ...
Coordinated DR Support           Remote Site Processes                                                                    ...
BMC SoftwareCoordinated Recovery      Building on years of expertise in IMS, DB2 & VSAM      Providing tools to solve the ...
BMC Recovery Management for z/OS                                                       DB2                        IMS     ...
Questions?© Copyright 03/10/2012 BMC Software, Inc                36
Upcoming SlideShare
Loading in …5
×

Dfw 10 03-2012-coordinated recovery

558 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
558
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Dfw 10 03-2012-coordinated recovery

  1. 1. BMC Coordinated Recovery for IMS, DB2 &VSAMRick WeaverDB2 Software Consultant
  2. 2. Today we will discuss…. The need for Coordinated Recovery What can cause an outage? BMC Building blocks – solutions for local and disaster recovery Backup strategies and solutions PIT recovery options Local DB2 PIT recovery considerations Disaster declaration? BMC Coordinated Disaster Recovery support© Copyright 03/10/2012 BMC Software, Inc 2
  3. 3. Complexity Creep Relationships within and between unlike DBMSes Relationships outside the organization External Supplier Production DB2 Supplier Customer Supplier Customer Catalog Catalog Marketing Purchasing Marketing Purchasing Inventory Sales Inventory Sales Data Warehouse Production IMS Supplier Customer Part Order Type title here Catalog Marketing Purchasing Stock Purchase Order Detail Shipment Type title here Type title here Inventory Line Item Detail Sales© Copyright 03/10/2012 BMC Software, Inc 3
  4. 4. SWPOC Impact To get a System Wide Point of Consistency, services must be stopped External Supplier Production DB2 Supplier Customer Supplier Customer Catalog Catalog Marketing Purchasing Marketing Purchasing Inventory Sales Inventory Sales Data Warehouse Production IMS Supplier Customer Part Order Type title here Catalog Marketing Purchasing Stock Purchase Order Detail Shipment Type title here Type title here Inventory Line Item Detail Sales© Copyright 03/10/2012 BMC Software, Inc 4
  5. 5. No SWPOC Impact If your availability requirement is such that you cannot obtain a SWPOC, you have no consistent recovery point Production DB2 Supplier Customer Supplier Customer Catalog Catalog Marketing Purchasing Marketing Purchasing Inventory Sales Inventory Sales Data Warehouse Production IMS Supplier Customer Part Order Type title here Catalog Marketing Purchasing Stock Purchase Order Detail Shipment Type title here Type title here Inventory Line Item Detail Sales© Copyright 03/10/2012 BMC Software, Inc 5
  6. 6. What can cause an application outage? Some events are planned: Other events are unplanned - Database maintenance - Site disasters (floods, power outages, - Data migration storms, fire, etc.) - Schema change implementation - Hardware failures (disk, CPU, network, - Hardware upgrades etc.) - Software upgrades - Operating system failures - Disaster recovery preparation - DBMS failures - Operation errors - Batch cycle errors - Improper data feeds - User errors - Deliberate data corruption - Application software errors© Copyright 03/10/2012 BMC Software, Inc 6
  7. 7. The BMC Building Blocks - Recovery Management for DB2  Define Application Recovery Groups, generate recovery jobs  Automate Conditional Restart process for local and remote subsystem recovery  Find Quiet Points  Recover to ANY Point in Time  Copy data with no outage - Backup and Recovery for IMS  Define Application Recovery groups, generate recovery jobs  Extract log switch information from RECONs  Find Quiet Points  Recover to ANY Point in Time  Copy databases with no outage - RECOVERY UTILITY for VSAM  Define Application Recovery groups, generate recovery jobs  Recover to ANY Point in Time  Copy data with no outage© Copyright 03/10/2012 BMC Software, Inc 7
  8. 8. DB2 Recovery Management Overview  ISPF application with DB2 repository tables  Access DB2 Recovery Resources and …  Group objects for recovery  Validate recoverability of objects ICF DB2  Specify/Generate recovery jobs Recovery Resources C o TABLE pi SPACE e SYSLGRNG s Recovery Manager Active Archive Repository Log Logs Recovery BSDS SYSCOPY Jobs© Copyright 03/10/2012 BMC Software, Inc 8
  9. 9. IMS Recovery Management Overview  ISPF application with repository datasets  Access IMS Recovery Resources and …  Group objects for recovery  Validate recoverability of objects ICF IMS  Specify/Generate recovery jobs Recovery  GUI Recovery Advisor for automation Resources C o DATA pi BASE e s Recovery Manager SLDS OLDS Repository Recovery RECON Jobs© Copyright 03/10/2012 BMC Software, Inc 9
  10. 10. VSAM Recovery Management Overview  ISPF application with VSAM repository tables  Registration and management of backups …  Group objects for back-up & recovery  Validate recoverability of objects ICF VSAM  Specify/Generate recovery jobs Recovery Resources C o VSAM pi Files e s RUV Repository Archive Logs CICS/TS Logs Recovery RUV Subsystem Jobs© Copyright 03/10/2012 BMC Software, Inc 10
  11. 11. Backing into the Backup Strategy Determine your local Recovery Time Objective - Generally 1-2 hours - Driven by cost of downtime – imagine your worst case scenario! - Total Site Disaster is a special case – plan for it but not only for it Examine your application environment - Size and number of objects in mission critical applications - Number of transactions per day on active objects Your backup strategy needs to support your RTO - May need more frequent backups to support SLA - You need low/no outage inexpensive backups© Copyright 03/10/2012 BMC Software, Inc 11
  12. 12. Hybrid Copy – No Outage, high speed, low CPU Many Small A Few Large IMS/DB2/VSAM IMS/DB2/VSAM Databases Databases Disk BMC Instant Image Copies COPY Snapshots IMS/DB2 BMC LOGS RECOVER Recovered Databases© Copyright 03/10/2012 BMC Software, Inc 12
  13. 13. BMC COPY PLUS for DB2 Cabinet Copyvs. DB2 9 Copy - Copying ERP application with 7,797 tablespaces to tape (IBM 3592) - 1,692,369 pages, or appx. 6.5 Gb. - The more objects copied, the bigger the benefit (think SAP with 30,000+ objects!) Business Value – much lower elapsed time and CPU usage for required backup processing© Copyright 03/10/2012 BMC Software, Inc 13
  14. 14. Recovery Interface Process Flow Build Specify Specify Validate Object Recovery N Recovery Recovery PIT? List Type Options Status Y Choose Generated Y Alternate Recovery GEN PIT Jobstream JCL? N Saved Y Recovery Save? Group© Copyright 03/10/2012 BMC Software, Inc 14
  15. 15. Find DB2 Recovery Points Recovery Point found A B C D E F G H Use the Log Master for DB2 “Quiet Point Report” feature to determine when there are “quiet points” of no transaction activity (from DB2 logs) Activity before the recovery point is recovered© Copyright 03/10/2012 BMC Software, Inc 15
  16. 16. Force DB2 Recovery point PIT selected A B C D E F G H Use the Recovery Management for DB2 “Recover to Timestamp” function to recover to ANY Point in Time (PiT) Transactions that finished before the PiT are applied Transactions that finished after the PiT are not applied© Copyright 03/10/2012 BMC Software, Inc 16
  17. 17. Find IMS Recovery Points Recovery Point found A B C D E F G H Use the Recovery Manager for IMS “Find Recovery Points” feature to determine when there are … • standard DBRC recovery points (from RECONs) • “quiet points” of no transaction activity (from IMS logs) Activity before the recovery point is recovered© Copyright 03/10/2012 BMC Software, Inc 17
  18. 18. Force IMS Recovery point PIT selected A B C D E F G H Use the RECOVERY PLUS for IMS “Recover to Timestamp” Utility syntax to recover to ANY Point in Time (PiT) Transactions that finished before the PiT are applied Transactions that finished after the PiT are not applied© Copyright 03/10/2012 BMC Software, Inc 18
  19. 19. Force VSAM Recovery point PIT selected A B C D E F G H Use the Recovery Utility for VSAM “Recover to Timestamp” syntax to recover to ANY Point in Time (PiT). Transactions that finished before the PiT are applied Transactions that finished after the PiT are not applied© Copyright 03/10/2012 BMC Software, Inc 19
  20. 20. Point in Time Recovery – Physical Backout The fastest way to get the database to the point prior to the application error is to remove one hour of records Very powerful for local PIT recovery where Storage is not the issue 1 Hr of Bad 23 Hours of Good Transactions Transactions Backout 1 Hr of Log Image Copy Recovery Recovery Point started© Copyright 03/10/2012 BMC Software, Inc 20
  21. 21. DB2 Local PIT Recovery considerations• DB2 recovery groups can range from one object to entire subsystem• Local Recovery of a DB2 subsystem to a prior point in time may require a catalog recovery and conditional restart • If DDL has executed since the desired recovery point, recover/restart catalog, then recover application data • If no DDL has executed, bypass catalog recover/restart and just recover application data• Local Subsystem Recovery may be required for ERP type subsystem recovery, or for wide impact outage not worthy of DR declaration (e.g. storage controller failure)• Recovery Management for DB2 automates the analysis and if required creation of the local subsystem conditional restart© Copyright 03/10/2012 BMC Software, Inc 21
  22. 22. When to Declare DisasterSite-wide calamity - declare Data CenterLose Network connectivity – maybe declare - Estimate repair time - > nn hours, declare (BCP Group) L L L L L LLose 1 LPAR – no declare P P P P P PLose entire CPU – maybe declare A A A A A A - Estimate repair time - > nn hours, declare (BCP group) R R R R R RLose one volume – no declareLose one disk controller – no declareLose all disk controllers – maybe declare - Estimate repair time - > nn hours, declare (BCP group)Lose one application, one database - no declare - Most likely event © Copyright 03/10/2012 BMC Software, Inc 22
  23. 23. Coordinated Disaster Recovery - Opportunities IMS, DB2, & CICS/VSAM allow for ‘online’ copies IMS, DB2, and CICS allow for log switch with no outage IMS and DB2 have repositories of B&R information  IMS RECONs  DB2 Catalog and Directory DB2 allows for a subsystem-wide restart to any RBA/LRSN  Inflight transactions are automatically backed-out at restart© Copyright 03/10/2012 BMC Software, Inc 23
  24. 24. Recovery Management for DB2Programs and Utilities - ARMBTSI  Insert timestamp into RM repository - ARMBCRC  Translate timestamp into equivalent RBA/LRSN - ARMBLOG  Issues ARCHIVE LOG command and waits for completion. - ARMBARC  Copy ARCHIVE LOG (copies 3 & 4 for offsite) - ARMBSRR  Generate DB2 Subsystem Restart jobs (200+ job steps) - ARMBGEN  Generate Application Recover jobs based on Application Groups - ARMPGPV  Performs Application Recovery Group Validation  Ensures new objects are added, dropped objects are deleted - ARMPGPS  Creates a set of balanced groups for the entire subsystem  Ensures new objects are added, dropped objects are deleted  Local Subsystem Recovery Conditional Restart Analysis and Avoidance© Copyright 03/10/2012 BMC Software, Inc 24
  25. 25. Backup and Recovery for IMSPrograms and Utilities - DRAMS  Capture AMS (Delete/Define) information for DR - DRRCN  RECON Cleanup utility – prep for DR  Can be run in ‘CHECK’ mode to obtain information  CRPREXX can fetch log switch PIT and feed DB2 process - IRMBATCH  Generate RECOVERY PLUS jobs to specified timestamp© Copyright 03/10/2012 BMC Software, Inc 25
  26. 26. Coordinated Disaster Point –Timestamp based (NO LOCAL SITE OUTAGE) - IMS  Log Switch performed  Timestamp available to recover applications  Timestamp fed to DB2 process via CRPREXX - VSAM  Switch Journals or Archive Log Streams  Use IMS Timestamp as recovery point - DB2  IMS Timestamp stored in RMGR for DB2 repository  Issue ARCHIVE LOG command  ARMBCRC converts IMS timestamp into RBA/LRSN – RBA/LRSN is then used to prepare and recover DB2 subsystem - This example is based on an IMS log switch being the ‘driver’ of the process. - It could have just as easily have been a DB2 log switch, or an arbitrary point in time.© Copyright 03/10/2012 BMC Software, Inc 26
  27. 27. IMS Recovery point PiT selected A B C D E F G H Use the RECOVERY PLUS for IMS “Recover to Timestamp” Utility syntax to recover to ANY Point in Time (PiT) Transactions that finished before the PiT are applied Transactions that finished after the PiT are not applied© Copyright 03/10/2012 BMC Software, Inc 27
  28. 28. VSAM Recovery point PiT selected A B C D E F G H Use the Recovery Utility for VSAM “Recover to Timestamp” syntax to recover to ANY Point in Time (PiT) Transactions that finished before the PiT are applied Transactions that finished after the PiT are not applied© Copyright 03/10/2012 BMC Software, Inc 28
  29. 29. DB2 Conditional Restart point UOW 1 UOW 2 UOW 3 UOW 4 Undo Records Log point of CRC (from ARMBCRC)© Copyright 03/10/2012 BMC Software, Inc 29
  30. 30. Coordinated DR Support Local Site Processes (IMS event driven)Backup IMS & DB2Cat&Dir, libraries,RMGR Repositories IMS Log Switch, Accum VSAM Backup Archives, Backup RECONs RUV Repository DRAMS ARMBSRR (Capture IMS ARMBCRC (Derive DB2 RBA/LRSN (Gen DB2 System AMS Info) Recovery jobs) TMS from CR DR Timestamp) Pull Truck DRRCN – (IMS) ARMBLOG ICF Dump v (DB2 Log ARMBGEN CRPREXX Switches) (Gen DB2 App v Recovery jobs) ARMBTSI (DB2) ARMBARC (Obtain/Register (copy DB2 CR DR Timestamp) Archive log)IMS, DB2, VSAMApplicationCopies © Copyright 03/10/2012 BMC Software, Inc 30
  31. 31. DR Site Recovery procedures - IMS  Prepare RECONs  Recover Application databases to DR Timestamp  Brings Application to point of consistency at that point  Backs out any in-flight transactions - DB2  Execute Subsystem Recovery JCL to DR Timestamp  DB2 Restart will backout any transactions in-flight  Recover Applications to Current (DR Timestamp) - VSAM  Generate and run RUV recoveries to DR timestamp  RUV will backout any inflight activity© Copyright 03/10/2012 BMC Software, Inc 31
  32. 32. DR RECON Cleanup UtilityCloses open PRILOGsDeletes PRIOLDsCloses open SECLOGsDeletes SECOLDsDeletes SUBSYS records RECON Data SetPerforms other cleanup... Updates/deletes ALLOCs Updates/deletes LOGALLs Closes open PRISLDs Closes open SECSLDs Marks CA runs “invalid” Marks DBs as “recov needed” Subsys Subsys Provides detailed reports Provides Suggested PIT Provides Suggested CA time © Copyright 03/10/2012 BMC Software, Inc 32
  33. 33. Coordinated DR Support Remote Site Processes Release IRM & VRS generated IMS & VSAM Update IRM & VRS application recoveries With CR DR PiT TS & to CR DR PiT TS generate recoveries DRRCN IMS & VSAM ICF & TMS Applications Update RECONs restores, many IPLs & create copies COLD available at CR DR START PiT Timestamp IMS Truck START Restore system libs, DB2 DB2 Applications IMS RECONs, & IMS RMGR available at CR DR repository Release ARMBSRR PiT Timestamp generated DB2 CRCR & system recoveries Release ARMBGEN generated DB2 application recoveries© Copyright 03/10/2012 BMC Software, Inc 33
  34. 34. BMC SoftwareCoordinated Recovery Building on years of expertise in IMS, DB2 & VSAM Providing tools to solve the HARD problems Leveraging knowledge and innovation© Copyright 03/10/2012 BMC Software, Inc 34
  35. 35. BMC Recovery Management for z/OS DB2 IMS VSAM Solutions Solutions SolutionsRecovery Management •Application Recovery •DB2 Subsystem Recovery Recovery Recovery Management Management •Coordinated Recovery for DB2 for IMS •Disaster RecoveryHigh Speed Recovery Coordinated Recovery for DB2/IMS/VSAM •Fast, Smart, Efficient High Speed High Speed Backup and RECOVERY Recovery Recovery •Any Point-In-Time Recovery Recovery Management Recovery Solution UTILITY •Reduced Downtime for DB2 For DB2 for IMS for IMS for VSAMHigh Speed Copy Snapshot Upgrade Feature for DB2/IMS/VSAM •Fast, Smart, Efficient High Speed High Speed •Non-Disruptive Features Copy Copy •Exploit Intelligent Storage for DB2 for IMS © Copyright 03/10/2012 BMC Software, Inc 35
  36. 36. Questions?© Copyright 03/10/2012 BMC Software, Inc 36

×