Yup, you'll probably have to cleanup your global database from your master
server.
You can use "vmglob -b -listalll | grep <media_server_name>" to find all the
glob db entries for this media server. Then use "vmglob -delete -drive <>"
or "-delete -robot" as necessary to delete the entries. They should add
back to the DB using tpconfig when you're successful.
robot 0 ADIC202100120 snoopy
drive LTO2-01 1110052176 snoopy
So, for example, the output above:
vmglob -delete -drive -serial 1110052176 -name LTO2-01 -devhost snoopy
vmglob -delete -robot -serial ADIC202100120 -robnum 0 -devhost snoopy
...then use tpconfig on your media server to add them back.
HTH -M
-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu]On Behalf Of Lewick,
Taylor
Sent: Monday, June 13, 2005 8:43 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Media Server Issues
Recently (while I was out of office) someone upgraded the OS of one of
our SAN media servers, (it only backs itself up). So naturally when I
returned, found some issues such as netbackup was no longer on there.
I reinstalled, but I am unable to add drives or robot, I am getting all
sorts of problems about can't update the global device database.
Anyone have any ideas..? Do I have to delete these definitions out of
the
Global device database on the master server? If so, how can I do that?
This is NetBackup 4.5 FP 8 on HP-UX 11.11.
Thanks,
Taylor
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|