Veritas: Connection Requested by Invalid server

Veritas: Connection Requested by Invalid server

April 17, 2017

So here is the scenario:

I recently built a SQL 2016 Failover Cluster with multiple NICs and one NIC dedicated for Backup. I went through Symantec Netbackup documentation available here which indicated that I had to create a virtual name referencing my Backup LANs IP Address to get the backup configuration to work. (this is a paraphrase). I did all that, update the host files on the client, master and media servers but kept getting this error in the log files in the path C:\Program Files\Veritas\NetBackup\logs\bpcd


bpcd valid_server: mastersvr-01 is not a master server
bpcd valid_server: mastersvr-01 is not a media server either

.

.

.

process_requests: Server access denied


 

Checking a few solutions on vox.veritas.com indicated that the master server name as resolved by the client was not matching the name configured in Windows Registry. It turns out the order I had entered the master and media server names in the host file actually mattered. I switch from A to B to get it to work:

 

A.

xxx.xxx.xxx.xxx      mastersvr-01     mastersvr-01.domain.group

yyy.yyy.yyy.yyy      mediasvr-01       mediasvr-01.domain.group

B.

xxx.xxx.xxx.xxx      mastersvr-01.domain.group   mastersvr-01

yyy.yyy.yyy.yyy      mediasvr-01.domain.group     mediasvr-01

 

Important to note is the fact that this is the default order in the Netbackup Appliance in version 7.7:

IP Address , FQDN, Short Host Name.

Igiri Books © Copyright 2016. All Rights Reserved. Site Credits: AppWorld