omnisv

starts, stops or displays the status of Application Recovery Manager daemons (HP-UX Cell Manager) or services (Windows Cell Manager). It can only be run on the Cell Manager.

omnisv

SYNOPSIS

omnisv -help

omnisv -version

omnisv {-start -stop -status -start_mon}

DESCRIPTION

The omnisv command enables you to start or stop Application Recovery Manager services and display their status.

Omnisv can start or stop the RDS, CRS, 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 IDB.

On the HP-UX 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 starts the OmniInet service (the Application Recovery Manager Inet program (/opt/omni/lbin/inet) is on the HP-UX Cell Manager started by the system inet daemon when an application tries to connect to the Application Recovery Manager 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 in

AppRM_home\db40\datafiles\catalog on the Windows Cell Manager or /var/opt/omni/server/log on the UNIX Cell Manager) 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.

OPTIONS

-version

Command line interface reference

139

Page 139
Image 139
HP Application Recovery Manager Cell Manager Windows Media Kit manual Omnisv, Version