vmoprcmd -d yields "database server is down", similar responses for
anything else that would want to hit EMM. Google pointed up
http://seer.entsupport.symantec.com/docs/287092.htm, but I'm not having
exactly that same problem, because NB_dbsrv actualy is NOT running, and
today's vault-managed hot catalog backup failed when it tried to connect
too.

Is it theoretically safe just to start NB_dbsrv back up again, like I
would have before with bprd and bpsched? Looking at a system that still
has a running instance, it looks like there're supposed to be a whole
mess of command line arguments...

--
gabriel rosenkoetter
Radian Group Inc, Unix/Linux/VMware Sysadmin / Backup & Recovery
gabriel.rosenkoetter AT radian DOT biz, 215 231 1556 



_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu