Problem after restart OS

NBU Version 8.1.1. Windows server 2019. NBU worked normally. Today I restart server and get problem.

After restart Windows Server 2019 I have problem with NBU 8.1.1.

  • I start GUI but when I try open policies I get error -  Can not connect on socket (25). Can not connect to Remote Service:[DARSManagement- my server_name]"

I decided that some services of NBU doesnot start. And really. NetBackup Device Manager , BMR Master Service,  NetBackup Event Manager  - don't started.

I started them manually. Then  policies was opened but Activity Monitor say cannot connect  on socket.  Another try I get message 

vrts.vss.sdk.at.exception unexpected vxat error .

 

Then I run

bpdown /f /v      
net stop VRTSpbx  

and

net start VRTSpbx
bpup /f /v

Then my GUI became work normally and Activity monitor too.

What has happened ? Why services of VERITAS NBU does not start automatically and started after   bpdown / bpup ? 

What to do ? How to diagnose problem?

 

2 Replies
Highlighted

Re: Problem after restart OS

Hello,

pay attention to versions - Windows 2019 support for Master/Media Servers is starting with the latest NetBackup version - 8.2.

https://www.veritas.com/bin/support/docRepoServlet?bookId=NB_80_OSSCL&requestType=pdf

But generally, refer to Event Viewer which NetBackup Service failed to start first, and then debug its logs in %netbackup%\logs.

Regards

Michal

 

Highlighted

Re: Problem after restart OS

nbars log shows connectivity problems:

07/02/2020 09:21:36.264 [Debug] NB 51216 libraries 137 PID:6576 TID:6580 File ID:362 [No context] 1 [vnet_configured_stacks] [vnet_addrinfo.c:8903] WARN: Neither IPv4 nor IPv6 configured for remote 0 0x0
07/02/2020 09:21:36.264 [Debug] NB 51216 libraries 137 PID:6576 TID:6580 File ID:362 [No context] 1 [NBIORInterceptor::establish_components] DNSQuery Lookup failed for host tmn-smicro-nbu.utair.dom error:9852(NBIORInterceptor.cpp:93)