Restoring and recovering a DB2 database - with a catalog name that has been specified
A catalog name can be specified for a database backup and an archive log backup. If a user specified a catalog name during a backup, there are certain setup actions you must follow during restore operations. Follow the following options for use in a Windows and UNIX environment.
If you use a non-root service user account, specific access must be allowed for that user when you add files to the /usr/openv/netbackup/db/altnames directory. The service user account must have full access to these files through the ownership or group and the permissions. For example, if the service user is svcname and its group is srvgrp, the file can have permissions of 400. If the file owner is for a different user and group, the file permissions must allow access to the service user. For example, 777. Equivalent permission settings must be used in a Windows environment.
Windows:
If the catalog name is equal to the name of the client performing the restore, no special setup is needed.
If the primary and the client are the same server and if the catalog name does not equal the name of the client performing the restore, update the
db2.confas follows:DATABASE and ARCHIVE stanzas:
CLIENT <catalog name>
ARCHIVE stanza only:
FORCE_BACKUP_CLIENT <name of the host performing the restore>
The newer releases of the DB2 database want to perform a backup of the archive logs after a restore.
If the client is a different server than where the backup has occurred and if the catalog name does not equal the name of the client performing the restore:
db2.confDATABASE and ARCHIVE stanzas:
CLIENT <catalog name>
ARCHIVE stanza only:
FORCE_BACKUP_CLIENT <name of the host performing the restore>
The newer releases of the DB2 database want to perform a backup of the archive logs after a restore.
The
altnamesdirectory must be set up:install_path\netbackup\db\altnames
UNIX:
If the catalog name is equal to the name of the client performing the restore, no special setup is needed.
If the catalog name does not equal the client name performing the restore, update the
db2.confas follows:db2.confDATABASE and ARCHIVE stanzas:
CLIENT <catalog name>
ARCHIVE stanza only:
FORCE_BACKUP_CLIENT <name of the host performing the restore> The newer releases of DB2 want to perform a backup of the archive logs after a restore
The
altnamesdirectory must be set up:/usr/openv/netbackup/db/altnames
More Information