Solving Operational Business Intelligence with InfoSphere Warehouse Advanced Edition

Chapter 8. Building a corporate backup and recovery strategy 293

8.2.1 Recovery scenarios and objectives

Define the objectives for recovering data for each recovery scenario you have

identified. Recovery time objective (RTO) refers to the service level objective for

the completion of any recovery process; that is, how long it is to take to complete

the restoration of lost data. Recovery point objective (RPO) refers to the service

level objective for how much data loss might be acceptable to the business in

relation to achieving your RTO. Together, these objectives represent how much

time you have to restore data and what amount of data loss can occur when

meeting the time objective.

By documenting your recovery scenarios along with the accepted recovery

objectives, you are clarifying exactly what is to be covered by your backup and

recovery strategy. Table 8-1 shows how a recovery strategy can be documented.

Depending on your strategy, you must choose between the features available:

undo the transaction, reload the data from backup images, or perform a

traditional restore from backup image. DB2 Recovery Expert can help you

identify the recovery paths available.

Table 8-1 Documenting a recovery strategy by scenario

Recovery

scenario

Recovery method Impact RTO/RPO

Data loss

in HOT

partitioned

table

1. Use IBM Recovery Expert for individual

DML error and to help determine root

cause.

2. Reference temporal history where

deployed to assist in “rollback.”

3. Use Optim High Performance Unload

to recover data from table space backup

image. Recover using LOAD or Ingest, as

appropriate.

4. Perform full table or table space restore

from table space backup image. Inform

business of outage.

򐂰 Low: Invalid data for

a period of time.

Online recovery.

򐂰 High: Table space is

offline for period of

recovery.

n minutes

(Use test

environment to

determine

restore speed.)