omnisv
starts, stops, or displays the status of Data Protector daemons (HP-UX, Solaris, or
Linux systems) or services (Windows systems)
nl
(this command is available on the Data Protector Cell Manager)
omnisv
SYNOPSIS
omnisv -version | -help
omnisv {-start | -stop | -status | -start_mon}
DESCRIPTION
The omnisv command enables you to start or stop Data Protector services and
display their status.
Omnisv can start or stop the RDS, CRS, UIProxy, KMS and MMD services on the
Cell Manager. Note that the MMD service can only be started or stopped locally on
the Cell Manager with the MMDB.
On the HP-UX or Solaris Cell Manager the omnisv command also adds the
omnitrig process to the cron table and schedules it (the omnitrig command on
the Windows Cell Manager is started by the CRS service). You can modify the
scheduler granularity by changing the SchedulerGranularity global variable.
By default, the granularity is 15 minutes, but it can be modified to 1 minute.
On the Windows Cell Manager omnisv also starts the Inet service (the Data
Protector Inet program (/opt/omni/lbin/inet) is on the HP-UX or Solaris Cell
Manager started by the system inet daemon when an application tries to connect to
the Data Protector port, which is by default port number 5555. Normally, these
daemons are started automatically during the system's startup).
Stopping of RDS service is logged down in the RDS.log located on the Cell Manager
in the directory Data_Protector_program_data\db40\datafiles\catalog
(Windows Server 2008), Data_Protector_home\db40\datafiles\catalog
(other Windows systems), or /var/opt/omni/server/log (UNIX systems) with
the ***SERVER SHUTDOWN INITIATED*** message. Each time the RDS service
is started a new RDS.log is created and the previous RDS.log is renamed to
RDS.bak.
Command line interface reference 389
To Next Page
Loading...
Need help?
General