Hi All
We’ve upgraded one of our customers on W2003 SP2 about
10 days ago. A couple of days ago the customer realized that jobs are queuing,
not going active. I found reference to fixes for the Resource Broker in 6.5.1A README.
Downloaded and installed the patch yesterday. Started backups at 14:40 –
all went active and started writing. Because backups were running, we did not
realize that nbrb died about an hour later (see extract from System log below).
The customer logged on last night, saw the service down, and restarted it.
Service died again at 01:11 this morning; customer restarted at 08:08.
I have a call open with Symantec, but other than a call ref
#, NO RESPONSE!!!
Has anybody seen/experienced this??? Any ideas/solution?
2008/03/27 08:08:25 Service
Control Manager Information None 7036 N/A MASTER The
NetBackup Resource Broker service entered the running state.
2008/03/27 08:08:25 Service
Control Manager Information None 7035 NT AUTHORITY\SYSTEM MASTER The
NetBackup Resource Broker service was successfully sent a start control.
2008/03/27 01:11:38 Service
Control Manager Error None 7034 N/A MASTER The NetBackup Resource Broker service terminated
unexpectedly. It has done this 2 time(s).
2008/03/26 20:42:01 Service
Control Manager Information None 7036 N/A MASTER The
NetBackup Resource Broker service entered the running state.
2008/03/26 20:42:01 Service
Control Manager Information None 7035 NT AUTHORITY\SYSTEM MASTER The
NetBackup Resource Broker service was successfully sent a start control.
2008/03/26 15:41:37 Service
Control Manager Error None 7034 N/A MASTER The NetBackup Resource Broker service terminated
unexpectedly. It has done this 1 time(s).
