Check withinn Data Protector cell manager to see if the Internal Database services are running
UNIX
/opt/omni/sbin/omnisv -status
Windows
cd \Program Files\Omniback\bin
omnisv status
If something shows as not running, stop and restart Data Protector
omnisv stop
omnisv start
DNS issue
- The DNS settings may be faulty and Cell Manager’s or Backup Navigator’s domain name cannot be resolved
- Ping Backup Navigator from Cell Manager, ping Cell Manager from Backup Navigator and check if each machine pings itself with fqdn.
Check if agent can collect the data from Cell Manager
- Execute a command which should return a list of devices:
/opt/agent/util_cmd –query FUN_LISTDEVICES -1 –server cellmanager.hostname
- If a return value is different than 0 (*RETVAL*) and you can see no data, there is an error with agent – Cell Manager communication
Backup Navigator is a pretty new product, so I was not able to find much on this error. You will need to open a case with the response center to get the lab involved. We would want you to collect the following
Installation Log /var/log/HPBackup_navigator_install.log This may be a copy of what you have already sent
Application Logs /opt/apache-tomcat/logs/cataline.out
/opt/dpa-ext/logs
Data Collection logs
agent_core.log
agent_util_cmd.log
THere was no directory path supplied for these last two, you may need to do a 'find' for the filenames
I don't know if the following would work for you, because I don't know if you are getting this far
Logs can be collected trough GUI or directly from file system. Steps to collect log files trough GUI:
- Navigate to administration -> logging
- Set appropriate log level and save
- Reproduce the issue
- Click on Download log button
- Send .zip file with collected log files