1 / 31

DB2 Recovery Management Strategy

DB2 Recovery Management Strategy. David R. Schwartz. Presentation Agenda. Introduction Background – DB2 z/OS recovery Current IBM products for recovery RE z/OS product roadmap Product architecture A sample of using the product. Background – DB2 Recovery.

koren
Download Presentation

DB2 Recovery Management Strategy

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. DB2 Recovery Management Strategy David R. Schwartz IBM CONFIDENTIAL

  2. Presentation Agenda • Introduction • Background – DB2 z/OS recovery • Current IBM products for recovery • RE z/OS product roadmap • Product architecture • A sample of using the product. IBM CONFIDENTIAL

  3. Background – DB2 Recovery • DB2 recovery is perhaps the most complex activity that DBAs participate in • There are many different potential scenarios • Recoveries are rare and most people don’t practice them enough, so their skills are often not sharp when they are needed • There is a need for an Expert type product to assist DBAs in recovery tasks • Types of recovery situations • Hardware failures • Application failures • Accidentally dropped objects • Disaster recovery IBM CONFIDENTIAL

  4. Types of Recovery DBMS System-level Subcritical HW Failure Application Local Local Remote Local √ Point in Time (PIT) √ √ √ Current • Application Recovery • Caused by application logic error • Always recover to point in time (PIT) • DBMS System-level Recovery • Caused by application logic, middleware/operating system, or hardware error • Includes DBMS Catalog/DBRC, Logs (active and archive), and User Data • Recovery from sub-critical hardware failures • Always recover to current Disaster Recovery IBM CONFIDENTIAL

  5. Recovery Components: Disaster Recovery Recovery Point Objectives (Amount of lost data) Tier 7 - System Automatic Site Switch (e.g., GDPS) Tier 6 - Disk and/or Tape Data Mirroring Websphere Information Itegrator Replication Tier 5 - Software Data Replication Cost (TCO: Servers, Network, Storage) Tracker Site (zDB2); RSR (IMS); HADR (LUW) Tier 4 - Log Replication Initial DR support Tier 3 - Electronic Transport Tier 2 - Physical Transport and Hot Site Tier 1 - Physical Transport 15 Min. 1-4 Hr.. 4 -8 Hr.. 12-16 Hr.. 24 Hr.. Days 8-12 Hr.. Recovery Time Objective (How quickly is application recovered) Tiers developed by SHARE Technical Steering Committee circa late 1980s Ref: http://www.eservercomputing.com/mainframe/articles/index.asp?id=781 IBM CONFIDENTIAL

  6. Current IBM products for DB2 recovery • DB2 COPY Utility • Make backups of application and catalog objects • DB2 RECOVER Utility • Primary recovery tool for application and catalog objects • Log Analysis Tool • Selective backout and recovery • Object Restore • Dropped object recovery (and more) • Change Accum Tool • Speed recovery by producing log subset files or using log records to update image copies • Automation Tool • Disaster recovery support • V8 – SYSTEM BACKUP and RESTORE Utilities • Backup and restore complete application subsystems IBM CONFIDENTIAL

  7. DB2 Automation Tool - Preparing for disaster recovery • Create disaster recovery profiles • Primary profile • Forces checkpoint • Forces log archive • Secondary profile • Archive log only process • Run periodically throughout the day • Build DR profiles in batch • Find image copies, archive logs, etc. • Run the DR jobs on a regular schedule • Ensure the necessary data sets are sent off-site IBM CONFIDENTIAL

  8. DB2 Automation Tool - Recovery at the remote site • Run the ssid#JCL job • Cleanup MVS catalog • Restores DB2 catalog and BSDS files • Recatalogs image copy data sets • Rebuilds BSDS and restores to VSAM format • Creates conditional restart record • Uncatalogs tape archive logs, copies them to DASD and recatalogs the DASD versions IBM CONFIDENTIAL

  9. DB2 Log Analysis Tool Selectively back out errant application updates Provides summary reports and multiple filtering options "Auto-Continue" mode Generation for static SQL for undo and/or redo records Filter criteria expanded to include OBID, PSID and DBID IBM CONFIDENTIAL

  10. IBM CONFIDENTIAL

  11. DB2 Change Accumulation Tool • A powerful DBA tool for restoring database objects in the most precise and least disruptive manner possible • Facilitates point in time recovery • Create image copies without impacting production systems • Creation of filtered log subsets (minilogs) for faster recovery • Direct Tablespace write of minilog (no image copy generated) • Management of minilogs • Multiple Image Copy Generation IBM CONFIDENTIAL

  12. DB2 Recovery Expert for z/OS V1.1 • GA target – 1H 2006 • We assist with many types of recoveries • In V3.1 we don’t do backup management • The strategy is to have customers use Automation Tool to perform the backups • Will build JCL to invoke: • DB2 RECOVER Utility • SYSTEM RESTORE Utility • DB2 LOAD Utility • Includes functionality from: • Log Analysis Tool • Object Restore • Automation Tool (object profiles) • In the future will include functionality from: • Change Accum • Automation Tool (disaster recovery) IBM CONFIDENTIAL

  13. V1.1 – 1H 2006 Application recovery Drop recovery Single or multiple objects Dependency analysis Quiet point analysis SYSTEM RESTORE And more! Futures Disaster recovery Most critical new feature Hardware assisted recovery Change Accum functionality Integration with RE MP Recovery Expert Release Roadmap IBM CONFIDENTIAL

  14. Product Architecture IBM CONFIDENTIAL

  15. Product Architecture • 3 tier architecture • UI – Java (no ISPF interface) • Server – C/C++ • Agent – C/C++ and assembler • No Java on the mainframe • No USS installation • No files in HFS • Agent and Server do require USS authorization • Server and Agent run as started tasks or batch jobs • Communication via TCP Sockets • One UI can log onto any number of Servers across an Enterprise (one at a time) • Servers can talk to any number of agents across an Enterprise • Servers can talk to agents on different LPARs or systems • Schema Level Repository (SLR) • Enhanced version of Object Restore’s Version Repository • Stored in DB2 tables • Updated via batch job (like Object Restore today) • Future – provide capability for ongoing update from log IBM CONFIDENTIAL

  16. Product Architecture – Other Products • Recovery Expert contains the necessary code from the following products (there are NO pre-reqs on these products) • Object Restore • Log Analysis Tool • Recovery Expert interoperates with Automation Tool if the customer has that product • There is no hard pre-req on Automation Tool • However, if the customer already has object profiles set up in Automation Tool, those can be used in Recovery Expert • Futures • Include Disaster Recovery from Automation Tool • This functionality will be enhanced in RE • Include functionality from Change Accum Tool IBM CONFIDENTIAL

  17. Update Schema Level Repository • This program goes through the DB2 catalog and builds the base for the Schema Level Repository • The Schema Level Repository is where we store information about existing DB2 objects so that we can, for example, recover objects when they are dropped (and disappear from the DB2 catalog) • The SLR update job needs to be scheduled on a regular basis by the customer to insure that the SLR is up to date • A future enhancement will be to allow the user to indicate that they would like us to continuously update the SLR from the log IBM CONFIDENTIAL

  18. Recover Points • There are 3 choices when specifying a recovery point • Recover to current • Recover to a timestamp • Can be selected from • Object version • Recovery history events • Quiet points • Recover to an RBA/LRSN • Can be selected from • Recovery history events • Quiet points IBM CONFIDENTIAL

  19. Working with Groups of Objects • In RE, there are 4 ways to specify a group of objects to be recovered • Explicit selection (one by one) • By pattern • Via RI relationships (Grouper and catalog RI) • Grouper groups can be selected in the object tree • If Automation Tool is available, via Automation Tool object profiles • Automation Tool profiles can be selected in the object tree IBM CONFIDENTIAL

  20. After logging on, the user selects a DB2 subsystem IBM CONFIDENTIAL

  21. Selection of recovery object(s) IBM CONFIDENTIAL

  22. In this example, we’re choosing to recover to current IBM CONFIDENTIAL

  23. The product returns several options with estimated costs IBM CONFIDENTIAL

  24. The status of your recovery is reported IBM CONFIDENTIAL

  25. Finally, the results are displayed. VIEW will show details IBM CONFIDENTIAL

  26. Now, let’s use log analysis to determine “quiet times” IBM CONFIDENTIAL

  27. The welcome screen appears IBM CONFIDENTIAL

  28. After selecting a DB2, we’ve selected a time range IBM CONFIDENTIAL

  29. Now, we’ll define some filtering (by object here) IBM CONFIDENTIAL

  30. As this is a batch process, the JCL is displayed IBM CONFIDENTIAL

  31. Similar to the recover scenerio, job results are shown IBM CONFIDENTIAL

More Related