Vault duplication failing after we move the robot controller to other media server: EXIT STATUS 303
Hi All,
I just moved our NetBackup controller from mserver11 to mserver12. The robot can inventory fine, all other operations are running fine so far, except the Vault duplication. It gave me: "EXIT STATUS 303: error encountered executing Media Manager command"
I checked in the log on /usr/openv/netbackup/logs/vault I found out, it still wants to connect to the old media server (mserver11) instead the new robot controller media server (mserver12).
...
00:59:32.680 [3890] <16> vltrun@BldRobotInventory()^39: command /usr/openv/volmgr/bin/vmcheckxxx -rt tld -rn 0 -rh mserver11 -h nbubck
k -list 2>&- returned [42] <F0><D0>,u<FC>^?
00:59:32.680 [3890] <16> vltrun@BldRobotInventory()^39: FAILed MM_EC=42 MM_MSG=cannot connect to robotic software daemon
00:59:32.680 [3890] <16> vltrun@BldRobotInventory()^39: FAILed NB_EC=303 NB_MSG=error encountered executing Media Manager command
00:59 ...
Which configuration I need to change to so the Vault know th new media server with robot contoller?
Thank you,
Iwan Tamimi
You need to check the Vault config as well.
Vault Robot also has a 'Robot Control Host' field that you need to update.