MAINTAINING THE DOMINO AND DB2 ENVIRONMENT


Manually restoring a DB2 enabled Notes database
Use this procedure to manually restore a DB2 enabled IBM® Lotus® Notes® database from an IBM® DB2 Universal Database™ Enterprise Server Edition database or tablespace backup. One database-managed space (DMS) tablespace may be the container for more than one DB2 enabled Notes database; therefore, online tablespace restore, that is, replacing the live DB2 tablespace, is not recommended. You can accomplish an online restore for most restore scenarios by using the following method to restore a DB2 tablespace to an alternate DB2 database within the same DB2 Instance.

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


Procedure

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:

2. From the DB2 CLP, initiate a redirected restore by entering this command:
3. Define storage for the DMS tablespace containers being restored, by entering this command:
4. After all required tablespaces have had their containers redirected, continue the restore by entering this command:
5. Verify the log directory for restoreDB by entering this command:
6. Copy all transaction log extents (files) from the liveDB's log directory to the NEWLOGPATH specified in the initial RESTORE command. For example, copy all of the S*.LOG files to restoreDB’s log directory (C:\newdb\logs).
7. If your system is configured to use retain style logging, retrieve from the archive all of the transaction log extents required to complete a point-in-time recovery, or a recovery to "end of logs," to the directory specified by NEWLOGPATH in the initial RESTORE command.
8. For point-in-time recovery, the last log file is truncated to the specified point-in-time for the recovery. To avoid having to copy the transaction log files to NEWLOGPATH for multiple point-in-time recovery scenarios, perform the recovery to the latest or most recent point-in-time first, then perform the recovery for the second most recent point-in-time, and so forth.

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:


The DB2 database restoreDB is ready to be used by a spare Domino server or a third-party DB2 enabled Notes database data retrieval tool.

Sample output


Related topics