Creating a \hot\" backup server"""

Topic: Code Place

Subtopic: DB2 for LUW

This is a technical document that describes how the production database is backed up, copied and restored to the hot backup server. The reasons for having a hot backup are clear  disaster recovery, reporting, testing, and development for example. There are a few options (log shipping and clustered servers) for what IBM calls High Availability Disaster Recovery. Unfortunately, these options have the limitation that the backup server cannot be used for general use. It is in a standby mode. This document shows a different methodology that provides both database redundancy and a working backup. The high-level process is below. The rest of this document is concerned with the details of these steps. 1. Backup the database on the production server 2. Copy the database backup file and log files to the hot backup server 3. Drop the hot backup database 4. Restore the production database to the hot backup server 5. Apply transaction logs and mark the database active 6. Clean up old database backup files and logs In sum, the backup database is deleted and recreated every day. Because of this, any Views, Stored Procedures, etc. created in the hot backup database will be deleted as well.

Click Here to Download

NOTE: These are only open to members of IDUG. If you are not a member, please CLICK HERE for more information.