Veritas NBU控制台无法查看Media pool

发布于 2022-08-04 20:28:10 字数 488 浏览 6 评论 2

现象:
其他工作可以正常进行备份,但是打开各个菜单时响应特别慢,查看Media pool时报无法连接Media server错,代码195,无法看到任何一盒磁带。
用service netbackup stop/start 重启netbackup服务,问题依旧。
再次停止netbackup服务,用ps auxf查看,发现有一个进行没有终止:/usr/openv/netbackup/bin/nbsl

解决:
在Symentec建议下用 /usr/openv/netbackup/bin/bp.kill_all 去杀进程失败,于是用kill -9 PID 将其杀掉。再次用
service netbackup start 启动服务,一切正常,可以浏览Media pool。

原因:
/usr/openv/netbackup/bin/nbsl 是netbackup的一个进程间通信服务进程,该进程僵死后导致进程间通信不畅,故出现响应慢、无法连接等问题

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

那支青花 2022-08-18 07:16:59

路过   学习了

似最初 2022-08-16 13:25:27

STATUS CODE 195: Viewing media or volume pools in the NetBackup Administration Console results in status code 195: unable to connect to the Netbackup service layer service.
--------------------------------------------------------------------------------
Exact Error Message
Unable to connect to the NetBackup service layer service (NetBackup Service Layer Daemon) on host <master>, it failed to respond - Server connection failed. Verify services or daemons are up and running (195).

Details:
Overview:
The above problem can occur when going to view media or volume pools if nbsl terminates during normal operation of NetBackup.  In one case it was seen during a period of heavy backup activity at the same time that NetBackup Operations Manager (NOM) was performing data collection.

Troubleshooting/Log Files:
The last messages seen in the nbsl log when the service stopped:

11/6/2007 21:28:56.288 [Debug] NB 51216 nbsl 132 PID:4384 TID:4880 File ID:132 [No context] 1 [ServiceManagerCollector:oCollect()]  PC Flag is 1(ServiceManagerCollector.cpp:312)
11/6/2007 21:28:56.288 [Debug] NB 51216 nbsl 132 PID:4384 TID:4880 File ID:132 [No context] 1 [ServiceManagerCollector:oCollect()] Collecting data for Media Server = <media server> (ServiceManagerCollector.cpp:286)

During this time there is a heavy demand on master server resources, particularly with socket availability.  Check for a large number of TIME_WAIT processes by running netstat -a on the master server.    This number can be considered large generally if it is over 100.  

Resolution:
If the above symptoms occur and a large number of TIME_WAIT processes on the master server are found, consider reducing the TcpTimedWaitDelay value.  This can be an indication that ports are not being released quickly enough to allow another connection on that port. The registry setting TcpTimedWaitDelay can be added to reduce the time a port will stay in this state.

1. Go to Start | Run, type regedit, and click OK
2. Navigate to HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesTcpipParameters
3. Highlight the Parameters key, right-click and select New | DWORD Value
4. Type the name TcpTimedWaitDelay
5. Double-click TcpTimedWaitDelay and enter a decimal value of 30

By default, this value is 240 seconds (4 minutes). It is recommended that this be changed to a value between 30-60 (seconds) in decimal, to decrease the wait time before a port becomes available.

Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文