DB2 backups

You can make a backup of an entire database or certain table spaces. Doing so creates a copy of the database or table space on separate media, such as tape or another server. Backups can be made while the database is active or inactive, depending on the type of recovery logs you use.

NoteNote:

When making a backup of a geodatabase in DB2 for z/OS, you must back up all databases in the database subsystem that compose the geodatabase. At a minimum, this will be two databases: the one that stores the ArcSDE geodatabase repository and one that stores user-defined data.

The following information is a summary of DB2 backup types. For complete information, read the backup and recovery documentation available for DB2. The documentation is as follows:

Data Recovery and High Availability Guide and Reference

DB2 LUW V 9.5 Information Center

DB2 z/OS Information Center

The BACKUP DATABASE command is used to create a backup image. It only affects the database partition on which it is executed. To execute BACKUP DATABASE, you must have either SYSADM, SYSCTR, or SYSMAINT authorization in the database.

When you use the BACKUP DATABASE command, you can specify to which directory the backup image is saved. This is the target location. Possible target locations include directories, devices, or other servers. If you do not specify a target location in the command, the backup image is saved in the directory from which the command is issued.

The database for which the backup operation is to be performed can be local or on a remote server. The backup image is saved on the database's server unless you are using a third-party storage management application.

When the BACKUP DATABASE command begins executing, a connection to the database is made that is specifically for the backup operation. If you are already connected to the database, that connection is dropped before the backup operation connection is created. Once the backup is completed, the backup operation connection is disconnected.

If the backup operation is successful, you receive a message to that effect that includes a time stamp for the backup image. This time stamp uniquely identifies each backup image.

To back up your ArcSDE DB2 database, you must copy the following files to an offline location:

The database recovery log files are important for bringing the data files from an earlier state to a later state. Between any two points in time, if you want to use the recommended Roll-forward recovery option, the recovery logs must be found in an unbroken sequence for database recovery to succeed.

ESRI recommends that you maintain at least two copies of all archive recovery logs for as far back in time as may be reasonably necessary for database recovery. The two copies should be stored on physically distinct media-separate disk drives, for example, or a disk drive and a tape drive. You could use log mirroring to maintain separate copies of the recovery logs.

If you intend to purge the archive recovery log files from their location on disk, be sure that you have a second backup copy of each archive recovery log file before purging.

This strategy of multiple backups of the archive recovery log files helps guard against multiple media failure, which is not as rare as it might seem. Some tape drives, for example, fail to detect bit errors until you attempt to restore a file, when it may be too late.

You only need to make a single copy of each data file with each backup as long as you carefully maintain multiple copies of archive recovery logs.

You can use the Configure Automatic Maintenance wizard in the DB2 Control Center to set the type of maintenance performed, such as backups, and when to run them. Using the wizard, specify your maintenance goals and at what times maintenance can occur. DB2 uses this information to determine if and when maintenance activities are required and runs them during the next time period in which maintenance is allowed.

In addition to setting the type of maintenance and times, you can set up notification e-mail to send error or trouble messages to recipients you specify.

NoteNote:

You can perform manual backup operations even when your database is configured to use automatic maintenance.

You can also use the Backup wizard in the DB2 Control Center to create backups of database objects, partitions, or the entire database.

Related Topics


11/18/2013