Netbackup Windows GUI Console reports Error connecting to media manager on drbkpsfms protocol error 39

Platform : - Storage – Backup – VERITAS Netbackup 7.1

Error: -

Error connecting to media manager on drbkpsfms protocol error 39_Netbackup_Window

Troubleshooting Summary :-

1.  While open the netbackup GUI console on window machine below error is reported

Error connecting to media manager on drbkpsfms protocol error 39_Netbackup_Window

2.Posts enabling the NBU Console logs below messages are observed.

NBU CONSOLE LOGS

16:24:59.235 [1020.2304] <2> getrequestack: server response to request:  REQUEST ACKNOWLEDGED 650

16:24:59.235 [1020.2304] <2> getrequeststatus: server response:  EXIT_STATUS 0

16:24:59.235 [1020.2304] <4> vmdb_start_oprd: vmdb_start_oprd request status:  successful (0)

16:25:19.765 [1020.2304] <2> get_long: (1) cannot read (byte 1) from network: Connection timed out.

16:25:19.765 [1020.2304] <16> read_string: unable to get record string from socket: Error number:  (10060), stat=-3

16:25:19.765 [1020.2304] <16> startOprd: oprd is not ready:  network protocol error (39)

16:31:47.041 [3452.3448] <2> vnet_pcache_init_table: ../../libvlibs/vnet_private.c.232: 0: starting cache size: 200 0x000000c8

16:31:47.056 [3452.3448] <2> vnet_cached_getaddrinfo_and_update: ../../libvlibs/vnet_addrinfo.c.1514: 0: found in file cache name: drbkpsfms

PROBLEM CAUSE

The device configuration seemed to have become corrupted

SOLUTION

n  This was solved by clearing all devices, and reconfiguring.  Make sure that no jobs are running and note of current device configuration has been taken.

n  On the master server

1) nbemmcmd -deletealldevices -allrecords [Warning! this will, as the syntax suggest delete all configured devices]

2) nbrbutil -resetall   [this clears any allocations that are stuck in the system for the now nonexistent devices]

3) reboot netbackup 

Done the reconfiguration of Device with netbackup