During this procedure, you will be issuing a command where you specify a name for the restored database. The abbreviation restoreDB is used to represent that database.

This procedure can be used with a tablespace or database level backup image.

Prerequisites

• The backup image, either a full database or a tablespace level backup, must contain the tablespaces SYSCATSPACE, DOMINO, and any tablespace you want to restore.
• The database restoreDB cannot already exist.
• There cannot be any files in NEWLOGPATH.

All tablestores that are restored with this procedure are placed in the database, restoreDB.

1. From the DB2 Command Line Processor (CLP), type this command:

DB2 DROP DB restoreDB
• Where restoreDB represents the name that you are assigning to the restored database.

DB2 RESTORE DB liveDB REBUILD WITH TABLESPACE (SYSCATSPACE, DOMINO, GRPx, GRPy, and so forth) TAKEN AT date-time INTO restoreDB NEWLOGPATH c:\newdb\logs REDIRECT WITHOUT PROMPTING
• Where you specify the date and time in this format: yyyymmddhhmmss
• Where liveDB is the DB2 database currently being used by IBM® Lotus® Domino™. It is the database from which the DB2 backup was taken, that is, the database from which you want to restore.
• Where newdb is the temporary database you are going to create during the restore process.
Note Restoring the SYSCATSPACE and DOMINO tablespace is required for this mechanism to work. The directory specified by NEWLOGPATH must not contain any transaction log files. All tablespaces that are restored with this procedure are placed in restoreDB as a result of the steps that follow. The DB2 redirected restore is the foundation of the restore and recovery process.

DB2 SET TABLESPACE CONTAINERS FOR tsid  IGNORE ROLLFORWARD CONTAINER OPERATIONS USING (FILE path size)

DB2 automatically reassigns a new storage PATH for system-managed space (SMS) tablespaces, for example, SYSCATSPACE or DOMINO. This did not automatically occur in some early versions of UDB 8.1.

Note The IGNORE ROLLFORWARD CONTAINER OPERATIONS option is important. In the event the transaction logs contain operations on the original tablespace containers, any attempt to replay the container operations, which in and of themselves are rare, will run into problems since that container will already be in use by another database.

Containers that are relative to the database directory do not need to be redirected since they are created under the new database’s database directory. For example, SYSCATSPACE and DOMINO tablespaces for a DB2 database being used by Domino should be defined as SMS tablespaces with storage relative to the new database's directory.

DB2 RESTORE DB liveDB CONTINUE

db2 get db cfg for newdb

Note To see a sample output generated by the command in Step 5, see "Sample output" at the end of this procedure.

Note At the end of this restore process, restoreDB has the same database configuration as liveDB, which means they will have the same log directory. No two databases can share the same log directory; therefore, you must specify the location of the transaction log extents. The log directory should be automatically reassigned and should be different from the log directory used by liveDB. To eliminate the possibility of a conflict, the NEWLOGPATH parameter is used to assign restoreDB an existing and empty directory.

Note If your DB2 system is configured to use RETAIN-style logging, be sure that you have manually recovered any transaction log files from any transaction log archive (backup) for any transaction log extent that was created after the DB2 backup you are restoring from. This is required in order to complete a point-in-time recovery, including any recovery to the "end of logs" (current time). These files must be restored to the directory referenced by NEWLOGPATH in the RESTORE command.

9. Complete the recovery. You can choose to perform a recovery to a specific point in time or a recovery to the end of logs. The target of the ROLLFORWARD command is now the new DB2 database, not the source DB2 database as in the examples above. Enter this command to complete the recovery:

DB2 ROLLFORWARD DB restoreDB TO END OF LOGS AND COMPLETE

Sample output

A sample output generated in Step 5 is shown here.

Changed path to log files  (NEWLOGPATH) =

Path to log files                        = :\newdb\logs\

 (for our example)

Overflow log path   (OVERFLOWLOGPATH)    =

Mirror log path          (MIRRORLOGPATH) =

First active log file                    = S0000002.LOG

Administering the Domino and DB2 environment

Glossary