Filter
Top Products
Managing the Data Protector Internal Database
Configuring the IDB
Chapter 9 395
• On UNIX: /opt/omni/sbin/omnisv -start
If the IDB is installed on MC/ServiceGuard, run the cmrunpkg
<pkg_name> command on the active node to start the Data Protector
package.
Creating an Additional Copy of the IDB Recovery File
Creating an additional copy of the IDB recovery file prevents you from
losing important data for IDB recovery.
Use the following steps to make another copy of the IDB recovery file:
1. Stop all backups and other Data Protector activities and run the
omnisv -stop command to stop the Data Protector services.
• On Windows: <Data_Protector_home>\bin\omnisv -stop
• On UNIX: /opt/omni/sbin/omnisv -stop
If the IDB is installed on MC/ServiceGuard, run the cmhaltpkg
<pkg_name> command on the active node to stop 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.
2. Edit the global options file by setting the value for the
RecoveryIndexDir variable: specify an additional location where
Data Protector makes a copy of the IDB recovery file, obrindex.dat.
It is recommended to specify a different physical disk.
3. Run the omnisv -start command (on UNIX, located in the
/opt/omni/sbin directory) to start the Data Protector services.
• On Windows: <Data_Protector_home>\bin\omnisv -start
• On UNIX: /opt/omni/sbin/omnisv -start
If the IDB is installed on MC/ServiceGuard, run the cmrunpkg
<pkg_name> command on the active node to start the Data Protector
package.
If the IDB is installed on Microsoft Cluster Server, bring the
OBVS_VELOCIS and OBVS_MCRS cluster groups online using the
Cluster Administrator utility.