Filter
Top Products
15. Establish and test DB2 Backup/Recovery Procedures. These procedures
should include a combination of DB2 and non-DB2 utilities in order to handle various
recovery scenarios. In addition, DB2 V8 provides two new utilities for providing DB2
controlled system wide backup and a point in time recovery. These are the BACKUP
SYSTEM and RESTORE SYSTEM (See OSS note 83000).
In addition, with DB2 V8 and DB2 9 you can leverage the RESTORE SYSTEM utility for
point-in-time recovery processes. It is not necessary to use the BACKUP SYSTEM
utility in obtaining the
system level copy in order to leverage the benefits of a total
system level recovery using the RESTORE SYSTEM utility. The system level copy can
be obtained using the volume level copy technology of your DASD, along with a SET
LOG SUSPEND. With the RESTORE SYSTEM utility the complexity of point-in-time
recovery is greatly reduced, providing a process that can be accomplished in a couple
of hours.
Recommended initial backup procedure:
Weekly ------> 1. Full DB2 Image Copy Of All R/3 Tablespaces
(SHRLEVEL=CHANGE or REFERENCE)
(2 copies - one for offsite)
(Perform a dynamic build of COPY utility JCL and
Control statements)
Daily ---------> 2. Full Image Copy of DB2 Catalog/Directory
(SHRLEVEL=REFERENCE)
(2 copies - one for offsite)
3. Issue DB2 command ARCHIVE LOG MODE(QUIESCE)
to establish point of consistency RBA
Daily ------> 1. FlashCopies of DB2 Volumes using DB2
SUSPEND LOG command or DB2 V8 BACKUP
SYSTEM
Note: DB2 SUSPEND LOG command performs the following actions:
- suspends log writes
- flushes log records to DASD
- records high log RBA in BSDS
- queues updates
- creates a point of consistency identified by a LOG RBA
- bufferpools are not flushed (it is not a checkpoint)
- allows a normal DB2 restart to obtain a consistent database (transactions in flight are
rolled back)
Copyright 2006
IBM Solutions Technical Sales (STS) 12/18/2007Page 21 of 51
12/18/2007
Planning and Preparation Guide for SAP NetWeaver Version 6.40: z/OS Implementation