Managing the Data Protector Internal Database

Recovering the IDB

 

The catalogs created by subsequent backups are good enough.

 

There is no IDB backup available.

Recovery

Proceed as follows:

Procedure

1.Run the command:

omnidbutil -writedb -no_detail -cdb <Directory> -mmdb <Directory>

to write the IDB without detail catalogs to ASCII files.

2.Run the command:

omnidbutil -readdb -cdb <Directory> -mmdb <Directory>

to read the IDB from the ASCII files.

The operation lasts approximately 5-20 minutes.

After the detail catalogs are removed, all DC binary files can be deleted, although the DC directories are still registered. Subsequent backups will store the file versions in the DC binary files.

Recovering the IDB Using IDB Recovery File and

Changed Device

Use this procedure to recover the IDB if the IDB recovery file

(obrindex.dat) is available but the original device used for the IDB backup is different from the one to be used for recovery, or the medium is located in a different slot.

Prerequisites Ensure the following before performing the database recovery:

Mount a disk of the same size as before the disaster on the same directories as at the IDB backup time (on Windows systems, the same drive letters must be assigned). If this cannot be ensured, follow the procedure for recovering the IDB to a different disk/volume layout. You can use the -previewoption of the omnidbrestore command to see where the files will be restored.

If possible, move the media.log file from the previous installation to a safe place. It will provide you with the information about the media used since the last IDB backup. This is very helpful for updating the IDB if transaction logs are not available.

424

Chapter 9

Page 454
Image 454
HP B6960-90078 manual Recovering the IDB Using IDB Recovery File Changed Device, 424