® IBM Software Group © 2006 IBM Corporation IBM CONFIDENTIAL DB2 Recovery Management Strategy...

31
® IBM Software Group © 2006 IBM Corporation IBM CONFIDENTIAL DB2 Recovery Management Strategy David R. Schwartz

Transcript of ® IBM Software Group © 2006 IBM Corporation IBM CONFIDENTIAL DB2 Recovery Management Strategy...

Page 1: ® IBM Software Group © 2006 IBM Corporation IBM CONFIDENTIAL DB2 Recovery Management Strategy David R. Schwartz.

®

IBM Software Group

© 2006 IBM CorporationIBM CONFIDENTIAL

DB2 Recovery Management Strategy

David R. Schwartz

Page 2: ® IBM Software Group © 2006 IBM Corporation IBM CONFIDENTIAL DB2 Recovery Management Strategy David R. Schwartz.

IBM Software Group

2

IBM CONFIDENTIAL

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.

Page 3: ® IBM Software Group © 2006 IBM Corporation IBM CONFIDENTIAL DB2 Recovery Management Strategy David R. Schwartz.

IBM Software Group

3

IBM CONFIDENTIAL

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

Page 4: ® IBM Software Group © 2006 IBM Corporation IBM CONFIDENTIAL DB2 Recovery Management Strategy David R. Schwartz.

IBM Software Group

4

IBM CONFIDENTIAL

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

Types of Recovery

DBMS System-levelSubcritical HW Failure

Disaster Recovery

√√

√√ Point in Time (PIT)

LocalRemoteLocalLocal

Application

Current

Page 5: ® IBM Software Group © 2006 IBM Corporation IBM CONFIDENTIAL DB2 Recovery Management Strategy David R. Schwartz.

IBM Software Group

5

IBM CONFIDENTIAL

15 Min. 1-4 Hr.. 4 -8 Hr.. 8-12 Hr.. 12-16 Hr.. 24 Hr.. Days

Recovery Point Objectives (Amount of lost data)

Cost (TCO: Servers, Network, Storage)

Recovery Time Objective (How quickly is application recovered)

Tier 7 - System Automatic Site Switch (e.g., GDPS)

Tier 6 - Disk and/or Tape Data Mirroring

Tier 5 - Software Data Replication

Tier 4 - Log Replication

Tier 3 - Electronic Transport

Tier 2 - Physical Transport and Hot Site

Tier 1 - Physical Transport

Tiers developed by SHARE Technical Steering Committee circa late 1980sRef: http://www.eservercomputing.com/mainframe/articles/index.asp?id=781

Recovery Components: Disaster Recovery

Websphere Information Itegrator Replication

Tracker Site (zDB2); RSR (IMS); HADR (LUW)

Initial DR support

Page 6: ® IBM Software Group © 2006 IBM Corporation IBM CONFIDENTIAL DB2 Recovery Management Strategy David R. Schwartz.

IBM Software Group

6

IBM CONFIDENTIAL

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

Page 7: ® IBM Software Group © 2006 IBM Corporation IBM CONFIDENTIAL DB2 Recovery Management Strategy David R. Schwartz.

IBM Software Group

7

IBM CONFIDENTIAL

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

Page 8: ® IBM Software Group © 2006 IBM Corporation IBM CONFIDENTIAL DB2 Recovery Management Strategy David R. Schwartz.

IBM Software Group

8

IBM CONFIDENTIAL

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

Page 9: ® IBM Software Group © 2006 IBM Corporation IBM CONFIDENTIAL DB2 Recovery Management Strategy David R. Schwartz.

IBM Software Group

9

IBM CONFIDENTIAL

DB2 Log Analysis Tool

DB2 Log Analysis Tool

Summary Report

Log Extract

DB2 Log Analysis Tool

Detail Report

DetailReport Data DB2

UNDO SQL

REDO SQL

General Report

DB2 Logs General Panel

Filter Criteria

Detail Panel Filter Criteria

USERID, TABLE, URID etc.

Data values

Selectively back out errant application updatesProvides summary reports and multiple filtering options"Auto-Continue" modeGeneration for static SQL for undo and/or redo recordsFilter criteria expanded to include OBID, PSID and DBID

Page 10: ® IBM Software Group © 2006 IBM Corporation IBM CONFIDENTIAL DB2 Recovery Management Strategy David R. Schwartz.

IBM Software Group

10

IBM CONFIDENTIAL

Page 11: ® IBM Software Group © 2006 IBM Corporation IBM CONFIDENTIAL DB2 Recovery Management Strategy David R. Schwartz.

IBM Software Group

11

IBM CONFIDENTIAL

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 recoveryCreate image copies without impacting production systemsCreation of filtered log subsets (minilogs) for faster recoveryDirect Tablespace write of minilog (no image copy generated)Management of minilogsMultiple Image Copy Generation

Page 12: ® IBM Software Group © 2006 IBM Corporation IBM CONFIDENTIAL DB2 Recovery Management Strategy David R. Schwartz.

IBM Software Group

12

IBM CONFIDENTIAL

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)

Page 13: ® IBM Software Group © 2006 IBM Corporation IBM CONFIDENTIAL DB2 Recovery Management Strategy David R. Schwartz.

IBM Software Group

13

IBM CONFIDENTIAL

Recovery Expert Release Roadmap

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

Page 14: ® IBM Software Group © 2006 IBM Corporation IBM CONFIDENTIAL DB2 Recovery Management Strategy David R. Schwartz.

IBM Software Group

14

IBM CONFIDENTIAL

Product Architecture z/OS System

RE Server

WindowsGUI

RE Agent 2RE Agent 1

DB2A DB2B

Page 15: ® IBM Software Group © 2006 IBM Corporation IBM CONFIDENTIAL DB2 Recovery Management Strategy David R. Schwartz.

IBM Software Group

15

IBM CONFIDENTIAL

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

Page 16: ® IBM Software Group © 2006 IBM Corporation IBM CONFIDENTIAL DB2 Recovery Management Strategy David R. Schwartz.

IBM Software Group

16

IBM CONFIDENTIAL

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

Page 17: ® IBM Software Group © 2006 IBM Corporation IBM CONFIDENTIAL DB2 Recovery Management Strategy David R. Schwartz.

IBM Software Group

17

IBM CONFIDENTIAL

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

Page 18: ® IBM Software Group © 2006 IBM Corporation IBM CONFIDENTIAL DB2 Recovery Management Strategy David R. Schwartz.

IBM Software Group

18

IBM CONFIDENTIAL

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

Page 19: ® IBM Software Group © 2006 IBM Corporation IBM CONFIDENTIAL DB2 Recovery Management Strategy David R. Schwartz.

IBM Software Group

19

IBM CONFIDENTIAL

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

Page 20: ® IBM Software Group © 2006 IBM Corporation IBM CONFIDENTIAL DB2 Recovery Management Strategy David R. Schwartz.

IBM Software Group

20

IBM CONFIDENTIAL

After logging on, the user selects a DB2 subsystem

Page 21: ® IBM Software Group © 2006 IBM Corporation IBM CONFIDENTIAL DB2 Recovery Management Strategy David R. Schwartz.

IBM Software Group

21

IBM CONFIDENTIAL

Selection of recovery object(s)

Page 22: ® IBM Software Group © 2006 IBM Corporation IBM CONFIDENTIAL DB2 Recovery Management Strategy David R. Schwartz.

IBM Software Group

22

IBM CONFIDENTIAL

In this example, we’re choosing to recover to current

Page 23: ® IBM Software Group © 2006 IBM Corporation IBM CONFIDENTIAL DB2 Recovery Management Strategy David R. Schwartz.

IBM Software Group

23

IBM CONFIDENTIAL

The product returns several options with estimated costs

Page 24: ® IBM Software Group © 2006 IBM Corporation IBM CONFIDENTIAL DB2 Recovery Management Strategy David R. Schwartz.

IBM Software Group

24

IBM CONFIDENTIAL

The status of your recovery is reported

Page 25: ® IBM Software Group © 2006 IBM Corporation IBM CONFIDENTIAL DB2 Recovery Management Strategy David R. Schwartz.

IBM Software Group

25

IBM CONFIDENTIAL

Finally, the results are displayed. VIEW will show details

Page 26: ® IBM Software Group © 2006 IBM Corporation IBM CONFIDENTIAL DB2 Recovery Management Strategy David R. Schwartz.

IBM Software Group

26

IBM CONFIDENTIAL

Now, let’s use log analysis to determine “quiet times”

Page 27: ® IBM Software Group © 2006 IBM Corporation IBM CONFIDENTIAL DB2 Recovery Management Strategy David R. Schwartz.

IBM Software Group

27

IBM CONFIDENTIAL

The welcome screen appears

Page 28: ® IBM Software Group © 2006 IBM Corporation IBM CONFIDENTIAL DB2 Recovery Management Strategy David R. Schwartz.

IBM Software Group

28

IBM CONFIDENTIAL

After selecting a DB2, we’ve selected a time range

Page 29: ® IBM Software Group © 2006 IBM Corporation IBM CONFIDENTIAL DB2 Recovery Management Strategy David R. Schwartz.

IBM Software Group

29

IBM CONFIDENTIAL

Now, we’ll define some filtering (by object here)

Page 30: ® IBM Software Group © 2006 IBM Corporation IBM CONFIDENTIAL DB2 Recovery Management Strategy David R. Schwartz.

IBM Software Group

30

IBM CONFIDENTIAL

As this is a batch process, the JCL is displayed

Page 31: ® IBM Software Group © 2006 IBM Corporation IBM CONFIDENTIAL DB2 Recovery Management Strategy David R. Schwartz.

IBM Software Group

31

IBM CONFIDENTIAL

Similar to the recover scenerio, job results are shown