HP B6960-90078 manual

		Managing the Data Protector Internal Database
		Recovering the IDB
	•	Verify that Data Protector is installed on the Cell Manager and the
		system where a device is attached (preferably, the device used for the
		IDB backup).
	•	If the IDB is installed on MC/ServiceGuard, run the cmhaltpkg
		<pkg_name> command on the active node before performing the
		guided autorecovery, to stop the Data Protector package. When the
		guided autorecovery has finished, run the cmrunpkg <pkg_name>
		command on the active node to start the Data Protector package,
		where <pkg_name> is the name of the Data Protector cluster
		package.
	•	If the IDB is installed on Microsoft Cluster Server, take the
		OBVS_VELOCIS cluster group offline using the Cluster Administrator
		utility on the active node before performing the guided autorecovery.
		When the guided autorecovery has finished, bring the OBVS_VELOCIS
		and OBVS_MCRS cluster groups online using the Cluster
		Administrator utility.
Recovery	1.	Run the following command to create a text file with the restore job
Procedure		options:
		omnidbrestore -logview -autorecover -skiprestore -save
		C:\TEMP\restjob.txt
IMPORTANT	The specified -logviewcommand lists first transaction logs, next to the
	session IDs. Remember the first transaction log for the session you want
	to restore, because you will need it in order to update the IDB after the
	restore. For example, from the output 2001/02/09-2 AAAAAAH, you
	would remember the first transaction log AAAAAAH in order to restore the
	2001/02/09-2 session.

The created restjob.txt file has the information on original devices and on slots in which media were originally located (at IDB backup time).

For example, if the IDB backup was done on a DDS drive with the SCSI address scsi0:0:0:0, a file like this is created:

-name LDEV -policy 1 -type 1

Chapter 9 425