ArcGIS Server Banner

Recovery models for DB2

Recovery models for DB2

Release 9.3 E-mail This TopicPrintable VersionGive Us feedback
Note:This topic was updated for 9.3.1.

The types of recovery you can use with geodatabases in DB2 are version recovery, which uses circular logging; roll-forward recovery, which uses archive logging; or high-availability disaster recovery (HADR).

NOTE: Be sure to recover all databases that make up the ArcSDE geodatabase when restoring an ArcSDE for DB2 for z/OS geodatabase.

To restore your geodatabase, you can use the RECOVER DATABASE command or the Restore Data wizard from the DB2 Control Center. The geodatabase can be restored to an existing database or to a new database. The following are notes on recovering to a new database:

When you perform a full database recovery of a recoverable database, there can be no other connections to the database other than the connection that is made when the database is recovered. When a full database backup is restored, DB2 checks to be sure that all the tablespaces referenced in the backup image are present in the database to which the data is being restored. (This could be an existing database or a new, empty database.) If it finds that a tablespace is missing or inaccessible, the recovery operation will fail.

To avoid this, you can perform a redirected restore operation. This allows you to specify new tablespaces to which you can restore table spaces from the backup image that were missing from the target database. For details on how to perform a redirected restore, consult your DB2 documentation.

If you are only restoring individual tablespaces of a recoverable database, the database can remain online as long as users aren't connected to the tablespaces you are trying to restore.

Tip

See Also

  • DB2 backups
  • About database backup and recovery