Your Cell Manager has a small set of processes that constitute the core of Data Protector. You can start, stop, or check on these processes quite simply from the command line using "omnisv". Just be sure you have no running sessions when stopping services, and that is also easy from the command line using "omnistat". All of these operations are performed on your Cell Manager.
Starting DP Services
C:\> omnisv start HP Data Protector services successfully started.
Checking DP Services
C:\> omnisv status
ProcName Status [PID]
===============================
rds : Active [7676]
crs : Active [8932]
mmd : Active [3764]
kms : Active [7536]
uiproxy : Active [8196]
omniinet: Active [7524]
Sending of traps disabled.
===============================
Status: All Data Protector relevant processes/services up and running.
Checking for Running Sessions
C:\> omnistat No currently running sessions.
Stopping DP Services
C:\> omnisv stop
HP Data Protector services successfully stopped.
C:\> omnisv status
ProcName Status [PID]
===============================
rds : Down
crs : Down
mmd : Down
kms : Down
uiproxy : Down
omniinet: Down
Sending of traps disabled.
===============================
Status: At least one of Data Protector relevant processes/services is not running.
So what are these mysterious services that make up the core of Data Protector?
RDS - Raima Database Service
This is the catalog database engine embedded within Data Protector. It is the interface between session managers (BSM, RSM, CSM, MSM, DBSM) and all of the catalog data within Data Protector's Internal Database (IDB). You can read all about Raima and their Raima Database Manager (RDM) product at their website.
CRS - Cell Request Service
On the Cell Manager, CRS listens for session requests and starts the appropriate session
manager, which in turn starts the required client agents. Scheduled backups will not run, nor will the Cell Manager accept any GUI connections without the Cell Request Service running. CRS along with UIPROXY generally run under a service account rather than using local SYSTEM authority. Ensure that the service account AD user and domain are listed as a Data Protector admin user. Otherwise, you will still have problems.
MMD - Media Management Daemon
It may be somewhat self explanatory, but MMD manages data that resides in the Media Management Database (MMDB) portion of the IDB. Media, media pools, and device configurations are among the data stored in the MMDB.
KMS - Key Management Service
Data Protector 6.1x and later is capable of creating and managing AES-256 encryption keys for LTO4 and LTO5 hardware encryption. The encryption key management service (KMS) was added to support that functionality.
UIPROXY - Java GUI Proxy
To enable a GUI on non-WIndows clients, DP has a Java-based GUI crafted to have the same look and feel as the native Windows GUI. While the presentation layer runs on the client via Java, a single socket connection (5556/TCP) is all that is required back to the Cell Manager where the UIPROXY does all of the GUI's heavy lifting. The Java GUI is also useful on Windows clients when you are separated from your Cell Manager by a firewall. Only one port to open!
OMNIINET - Data Protector Inet Service
The Data Protector Inet process, also known as OMNIINET is actually present on all DP clients. With Windows clients, it is an actual service that runs on its own. With Unix-based clients, the "omni" service is managed by inetd or xinetd. This is the service that listens for incoming connections on 5555/TCP.
Not LIsted: OMNITRIG
Though not a process, OMNITRIG is only relevant to Unix-based Cell Managers. When OMNITRIG is active, an entry is placed in root's crontab that fires the omnitrig process once every 15 minutes (by default). All the process does is parse schedule files to determine what backup(s) should start at each quarter hour. Stop OMNITRIG and all that really happens is removal of the relevant entry in root's crontab. With a Windows-based Cell Manager, the schedule files are parsed in the background by existing DP processes.
That final notation "Sending of traps disabled" simply indicates that an SNMP trap destination has yet to be defined within Data Protector.
So there you have it. These are the process that make your Cell Manager ... well ... a Cell Manager. As a companion to this article, you might find my Alphabet Soup article useful in explaining many of the agent acronyms you see in session messages.
