Filter
Top Products
Troubleshooting
Troubleshooting Data Protector Services and Daemons
Chapter 12572
There are several possible reasons why the Data Protector daemon has
failed to start:
Raima Velocis server daemon could not be started
/opt/omni/sbin/omnisv -start
Could not start Raima Velocis server daemon.
Action See /var/opt/omni/db40/datafiles/catalog/RDS.log for details.
Check that you have all IDB files in the /var/opt/omni/db40 directory.
Compare the list of files in the
/opt/omni/newconfig/var/opt/omni/db40 to the list of files in the
/var/opt/omni/db40 directory. Ensure that these directories are
mounted.
Raima Velocis server daemon is apparently not running
If any of the Data Protector commands terminate with following
message:
[12:1166] Velocis daemon error - the daemon is probably not
running
Action Check if the database server is really not running using following
command: /opt/omni/sbin/omnisv -status
• If the database server is not running, start it by running:
/opt/omni/sbin/omnisv -start
• If the database server is running, then it is likely either that the
/var/opt/omni/db40 directory does not exist or some of the files
are missing. This can happen if someone has accidently removed the
directory or some of the IDB files. Recover the IDB. Refer to
“Recovering the IDB” on page 417.
Data Protector Cell Manager daemon could not be started
/opt/omni/sbin/omnisv -start
Could not start the Cell Manager daemon.
Action See /var/opt/omni/tmp/omni_start.log for details.
Ensure that the following configuration files exist: