Are you running the command local on the Cell Manager or from a remote system?

Check if the name in

/etc/opt/omni/cell/cell_server (if Unix) or
HKLM\SOFTWARE\Hewlett-Packard\OpenView\OmniBackII\Site - CellServer (if Windows) is
correct.

Cannot access the Cell Manager system (inet is not responding).

The Cell Manager host file is not reachable or is not up and running or has no
OmniBack II software installed and configured on it.

A telnet to port 5555 of the cell manager host returns:

connection refused

Solution

There was no "omni" entry in /etc/inetd.conf.

Add the following line to inetd.conf:

omni stream tcp nowait root /opt/omni/lbin/inet inet \

-log /var/opt/omni/log/inet.log

Run "inetd -c" to reread the configuration file.

Technical Document OV-EN010292

I have experience with this problem because I faced with it when I am a beginner
with DP :)
The exactly reason is : you are missing in /etc/inetd.conf file configuration!
Just check for this line has been added to this file:

omni stream tcp nowait root /opt/omni/lbin/inet inet -log

/var/opt/omni/log/inet.log

This clears still running sessions:

omnidbutil -clear

Show database is running?

omnisv -status

Is your tmp directory /var/opt/omni/tmp missing?

Run the omnisv -stop command on the Cell Manager to stop the
Data Protector services/processes:
/opt/omni/sbin/omnisv -stop
On the Cell Manager, manually create the temporary directory:
/var/opt/omni/tmp

Run the omnisv -start command to start the services/processes.

/opt/omni/sbin/omnisv -start

==========================================
S1: /opt/omni/sbin>omnidb -session
Connect to CRS failed.
To start the OmniBack II daemons on the Cell Manager host use the command omnisv
-start
on HP/UX Cell Manager or omnisv.exe -start on Windows NT Cell Manager.
S1: /opt/omni/sbin> ./omnisv -status

S1: /opt/omni/sbin>./omnisv -status

ProcName Status [PID]
===============================
rds : Active [7944]
crs : Active [7945]
mmd : Active [7946]
omnitrig: Active
Sending of traps disabled.
===============================
Status: All OmniBack II relevant processes/services are up and running.
S1: /opt/omni/sbin>omnidb -session
Connect to CRS failed.
To start the OmniBack II daemons on the Cell Manager host use the command omnisv
-start
on HP/UX Cell Manager or omnisv.exe -start on Windows NT Cell Manager.

S1: /opt/omni/sbin>./omnidbcheck
Check Level Mode Status
==================================================
Core -core OK

omnisv -stop
Check running processes with ps -ef | grep omni
Kill all omni processes still running
omnisv -start

omnisv -status

Is the cellmanager patched-up?

omnisv -stop
/opt/omni/lbin/crs -clshm
/opt/omni/lbin/crs -shutdown
omnisv -start
This clears shared memory.

omnisv -status