omnihealthcheck
checks the status of Data Protector services, the consistency of the Data Protector
internal database (IDB), and if at least one backup of the IDB exists
nl
(this command is available on the Data Protector Cell Manager)
omnihealthcheck
SYNOPSIS
omnihealthcheck -version | -help
omnihealthcheck [-config ConfigFile]
DESCRIPTION
The omnihealthcheck command reads the specified configuration file where each
line of the file is treated as a separate command and is executed. The commands
must be listed with full pathnames except if they are Data Protector commands located
on the Cell Manager in the directory Data_Protector_home\bin (Windows
systems) or the directory /opt/omni/bin or /opt/omni/sbin (UNIX systems).
With the Windows Cell Manager, the configuration file must be in the Unicode
format. If the configuration file is not specified, the default file on the Cell Manager
is used:
Data_Protector_program_data\Config\Server\HealthCheckConfig
(Windows Server 2008),
Data_Protector_home\Config\Server\HealthCheckConfig (other
Windows systems), or /etc/opt/omni/server/HealthCheckConfig (UNIX
systems).
If the default file is used, omnihealthcheck checks if Data Protector services (RDS,
CRS, MMD, UIProxy, KMS, omnitrig, and omniinet) are active, if the Data
Protector MMDB is consistent, and if at least one backup of the Data Protector internal
database (IDB) exists.
Exit codes of individual commands are inspected at the end.
There are 3 different exit codes for the omnihealthcheck command:
0: All listed commands and their exit codes have been executed.
1: At least one of the commands in the configuration file could not be executed or
has completed with an exit code other than 0.
2: The configuration file could not be read.
Command line interface reference 343
To Next Page
Loading...
Need help?
General