Backup3G/DA-DB2 5.1 Release Notes

From Documentation

Overview and Features

This is the second release of the DB2 backup module. This module has also been certified for use with DB2 7.1, 7.2 and DB2 8.1.

The distribution is generic and will run on all UNIX platforms supported by Backup3G 5.1 or newer.

Features in DA-DB2

• full DB2 online database backup and all active logs created during the backup
• full DB2 online tablespace backup, tablespace by tablespace and all active logs created during the backup
• online tablespace backup has option to select tablespaces (-t <tablespaces> in backup item options) or exclude tablespaces (-x <tablespaces> in backup item options)
• full DB2 offline database backup
• full DB2 offline tablespace backup, tablespace by tablespace
• by default an offline backup will leave the database in the same state it was prior to the backup. This can be overridden with -U in backup item options to ensure the database is unquiesced or -D in backup item options to leave the database quiesced
• both online and offline backup have options to include extra files and directories in the backup (-s <pattern> in backup item options)
• backing up parameter directory in online and offline backups (-p <pattern> in backup item options)
• backup of DB2 archived logs
• archived logs backup has option to remove old logs (-k <number to keep> in backup item options) - active logs will not be removed
• verbose mode (-v in backup item options) displays list of files in the backup log that represent the tablespaces, active and archived logs to be backed up.

Environment

Software Prerequisites

Before you can install DA-DB2 5.1, COSmanager 4.2.5 (or newer) and Backup3G 5.1 (or newer) must already be installed on the same host.

Disk Space Required

DA-DB2 5.1 is installed under the Backup3G home directory. It requires less than 200 Kbytes disk space.

Supported DB2 Versions

DA-DB2 5.1 supports DB2 7.1, 7.2, 8.1 and 9.1.

Notes

Simultaneous Backups

You cannot run two or more backup jobs of the same database at the same time. The exception is an Online Tablespace backup. To decrease the backup window, multiple backup jobs of the same database may be run at the same time. Each job specifies which tablespaces are included or excluded—example: -t <tablespaces> or -x <tablespaces>

To avoid backing up the active logs in each job that is being run at the same time, specify that active logs are to be ignored in all but one of the jobs—example: -A

Backing Up from Instances of DB2

To perform any DB2 backup of an instance on a host, specify the name of the associated DB2 user for that instance in the Options field when you add or change a Backup Item—example: -u <username>

Instance details are configured by COSbackup configuration > Initial configuration > Configure Data Avalability for DB2

Backing Up Archived Logs

If archived logs are copied elsewhere by a “User Exit”script, specify the archived logs directory in the Options field when you add or change a Backup Item—example: -a <archived logs dir>

Protect File Patterns

The DB2 offline and Oracle online backup methods can accept a file pattern comprising a list of files to be backed up along with the DB2 object. The file pattern is specified in the Options field when you add or change a Backup Item.

This pattern is globbed before being passed to the method. Protect file patterns with quotes (example: -s “*/*savefile”) to make sure they are passed correctly to the backup method.

Database has Status “Backup Pending”

A db2 database backup needs to be performed either from the command line or from db2cc or from COSbackup before the database will return to a Consistent state.

Recovering DB2 Databases

The suggested process is as follows:

1. Deactivate the datebase being restored

su - <db2 user> db2 deactivate database <db>

If you get messages about being unable to deactivate, then there are client connections that need to be killed, then deactivate again

2. Perform the restore, whether it be from an offline, online or archived logs backup via COSbackup > Recover

3. Roll the database forward

db2 rollforward database <db> to end of logs and complete

Should show that the roll forward is successful and what the first active log is

4. Activate the database

db2 activate database <db>

5. Check the database is consistent

db2 connect to <db> db2 get database config

Check the output (near the beginning) such that:

Backup pending = NO

Database is consistent = YES

Rollforward pending = NO

Restore pending = NO

5. Log out

db2 connect reset exit

Warnings

Archive Log Backups with no Archive Logs

When performing an archived log backup, and no archived logs are found, the backup job will succeed even though no files are backup up.

Hardware and OS Dependencies

None known.