Forum Discussion

Kev_Lamb's avatar
Kev_Lamb
Level 6
11 years ago

Windows Server 2012 & 7.5.0.6

Hi,

I have installed the Win2012 7.5.0.6 client onto a Win Server 2012 client but am having difficulties connecting from the Master Server to the client.

The install completed wihout error and I can run the Backup/Restore client from the Server; however, when I try to connect to the client from the Master GUI I get Connection Requested By Invalid Server, the Master was correctly placed in the relevant box on install and I have double checked the client GUI and this is correct.

If I run the usual connection tests from the master server I get the following:

bpclntcmd -hn lonbfbvmconn2

host lonbfbvmconn2: LONBFBVMCONN2.corp.ad.timeinc.com at 10.132.113.127

aliases:     LONBFBVMCONN2.corp.ad.timeinc.com     lonbfbvmconn2     10.132.113.127

 

telnet lonbfbvmconn2 bpcd

Trying 10.132.113.127...

Connected to lonbfbvmconn2.corp.ad.timeinc.com (10.132.113.127).

Escape character is '^]'.

 

bptestbpcd -host lonbfbvmconn2   

<16>bptestbpcd main: Function ConnectToBPCD(lonbfbvmconn2) failed: 46

server not allowed access

bfbackup.ipcmedia.com:/root> bptestbpcd -client lonbfbvmconn2

<16>bptestbpcd main: Function ConnectToBPCD(lonbfbvmconn2) failed: 46

server not allowed access

So as you can see I can quiet clearly access the bpcd port via Telnet and the bpclntcmd returns the correct client details but the bptstbpcd fails.There is no firewall active on the client and the client and master can do a reverse lookup on each other and can ping also.

Anyione got any ideas as I am at a loss

 

Kev

 

 

Backup and Recovery
Configuring
Error messages
NetBackup
Not Applicable
Troubleshooting
Upgrade
  • CRZ's avatar
    CRZ
    11 years ago

    Ignore me at your peril!  wink

    You haven't addressed the problem I found yesterday.  I'm STILL seeing that extra space I shouldn't see in your bpcd log for the reverse DNS of your master server's hostname.

    To make it easier to spot, I've replaced the space with percent signs in this excerpt from your most recently posted bpcd log:

    12:07:39.250 [2680.1320] <2> setup_debug_log: switched debug log file for bpcd
12:07:39.250 [2680.1320] <2> bpcd main: VERBOSE = 0
12:07:39.250 [2680.1320] <2> logparams: C:\Program Files\Veritas\NetBackup\bin\bpcd.exe -standalone
12:07:39.250 [2680.1320] <2> process_requests: offset to GMT 0
12:07:39.266 [2680.1320] <2> logconnections: BPCD ACCEPT FROM 10.132.112.22.55614 TO 10.132.113.127.1556 fd = 292
12:07:39.266 [2680.1320] <2> process_requests: setup_sockopts complete
12:07:39.266 [2680.1320] <2> bpcd peer_hostname: Connection from host bfbackup.ipcmedia.com% (10.132.112.22) port 55614
12:07:39.266 [2680.1320] <2> bpcd valid_server: comparing bfbackup.ipcmedia.com and bfbackup.ipcmedia.com%
12:07:39.266 [2680.1320] <8> vnet_cached_getaddrinfo_and_update: [vnet_addrinfo.c:1585] in failed file cache ERR=11001 NAME=bfbackup.ipcmedia.com% SVC=NULL
12:07:39.266 [2680.1320] <8> vnet_cached_getaddrinfo: [vnet_addrinfo.c:1275] vnet_cached_getaddrinfo_and_update() failed 6 0x6
12:07:39.266 [2680.1320] <8> vnet_same_host_and_update: [vnet_addrinfo.c:2848] vnet_cached_getaddrinfo() failed STAT=6 RV=11001 NAME2=bfbackup.ipcmedia.com%
12:07:39.266 [2680.1320] <2> bpcd valid_server: comparing lonbfbnbumedia1.corp.ad.timeinc.com and bfbackup.ipcmedia.com%
12:07:39.266 [2680.1320] <8> vnet_cached_getaddrinfo_and_update: [vnet_addrinfo.c:1532] in failed cache ERR=11001 NAME=bfbackup.ipcmedia.com% SVC=NULL
12:07:39.266 [2680.1320] <8> vnet_cached_getaddrinfo: [vnet_addrinfo.c:1275] vnet_cached_getaddrinfo_and_update() failed 6 0x6
12:07:39.266 [2680.1320] <8> vnet_same_host_and_update: [vnet_addrinfo.c:2848] vnet_cached_getaddrinfo() failed STAT=6 RV=11001 NAME2=bfbackup.ipcmedia.com%
12:07:39.266 [2680.1320] <2> bpcd valid_server: comparing lonbfbreddev.ipcmedia.com and bfbackup.ipcmedia.com%
12:07:39.266 [2680.1320] <8> vnet_cached_getaddrinfo_and_update: [vnet_addrinfo.c:1532] in failed cache ERR=11001 NAME=bfbackup.ipcmedia.com% SVC=NULL
12:07:39.266 [2680.1320] <8> vnet_cached_getaddrinfo: [vnet_addrinfo.c:1275] vnet_cached_getaddrinfo_and_update() failed 6 0x6
12:07:39.266 [2680.1320] <8> vnet_same_host_and_update: [vnet_addrinfo.c:2848] vnet_cached_getaddrinfo() failed STAT=6 RV=11001 NAME2=bfbackup.ipcmedia.com%
12:07:39.266 [2680.1320] <4> bpcd valid_server: bfbackup.ipcmedia.com% is not a master server
12:07:39.266 [2680.1320] <16> bpcd valid_server: bfbackup.ipcmedia.com% is not a media server either
12:07:39.266 [2680.1320] <8> vnet_cached_getaddrinfo_and_update: [vnet_addrinfo.c:1532] in failed cache ERR=11001 NAME=bfbackup.ipcmedia.com% SVC=NULL
12:07:39.266 [2680.1320] <8> vnet_cached_getaddrinfo: [vnet_addrinfo.c:1275] vnet_cached_getaddrinfo_and_update() failed 6 0x6
12:07:39.266 [2680.1320] <8> vnet_is_local_host: [vnet_addrinfo.c:327] vnet_cached_getaddrinfo() failed STAT=6 RV=11001 NAME=bfbackup.ipcmedia.com%
12:07:39.266 [2680.1320] <2> process_requests: output socket port number = 1

    You can also see from this bpcd log that OTHER hosts do not have the extra space after the hostname - for example...

    12:06:45.848 [2216.2056] <2> bpcd peer_hostname: Connection from host LONBFBVMCONN2.CORP.AD.TIMEINC.com (10.132.113.127) port 53900

    ...so it's something unique to JUST your master.

    Can you explain why your client's reverse DNS for 10.132.112.22 is appending some invisible space to the FQDN of your master when the reverse DNS for 10.132.113.127 doesn't append that space to *its* FQDN?

    The problem with invisible space is...you might not see it when you're doing test DNS lookups, because it's invisible.  :)

  • Kev_Lamb's avatar
    Kev_Lamb
    11 years ago

    Embarrased or what, we have located the original issue with the hosts file, this was saved as a .txt file so the server was ignoring this, once this was corrected we could then connect.

    Still unsure as to why it is seeing the extra space in DNS though, the QIP entry has been checked and looks good so unless this is in the DNS cache somewhere we are unsure but as I said all our other servers use the same DNS entries without error.

    I will continue to look into this.

    Thanks for all you help 

28 Replies

Sort By
  • Mark_Solutions's avatar
    Mark_Solutions
    Level 6
    11 years ago

    Setup a bpcd log on the client to see why it actually denies access

    It may just be a FQDN thing and you will then need to either add a hosts file entry to the client and / or Master / Media Servers or add the FQDN to the clients server list

    Create the bpcd directory - try and connect to it again and post the resulting log file

  • Kev_Lamb's avatar
    Kev_Lamb
    Level 6
    11 years ago

    Just done that, looking through the log (attached) it is stating that my master server is not a master or a media.....

     

     

  • Kev_Lamb's avatar
    Kev_Lamb
    Level 6
    11 years ago

    Just had a look at the Reg Key in HKEY_LOCAL_MACHINE\Softeare\veritas\netbackup\currentversion\config and the Server key includes the following:

    bfbackup.ipcmedia.com
    bfbackup
    10.132.112.22

    So it is listed in the software as a server in all the FQDN ways

     

     

  • chack22's avatar
    chack22
    Level 4
    11 years ago

    What does bptestbpcd show? I don't recall the options off the top of my head, but it checks connections to clients. What about bpclntcmd -hn (option) and bpclntcmd -ip (IP)? This checks lookups (forward and reverse) from the NBU side.

  • Kev_Lamb's avatar
    Kev_Lamb
    Level 6
    11 years ago
    Chack22 if you take a look at the initial post the bpclntcmd returns ok but the bptesbpcd fails with server not allowed access, the telnet to the bpcd port works fine, all entries on the client are correct and I have even put the master in the host file and can do forward & reverse DNS from client to master and master to client.
  • CRZ's avatar
    CRZ
    Level 6
    11 years ago

    I may be nuts, but something stood out from your log...

    17:22:30.901 [2060.2032] <2> bpcd peer_hostname: Connection from host bfbackup.ipcmedia.com  (10.132.112.22) port 51386
...
17:22:31.151 [1108.536] <4> bpcd valid_server: bfbackup.ipcmedia.com  is not a master server
17:22:31.151 [1108.536] <16> bpcd valid_server: bfbackup.ipcmedia.com  is not a media server either

    It sure looks like there's an invisible space appended to the reverse DNS of your master (I'm seeing two spaces instead of the one which I would expect) which is causing NetBackup to fail to match the name "bfbackup.ipcmedia.com " to "bfbackup.ipcmedia.com" because, to NetBackup, the strings ARE technically different...

    Can you recheck the host file on the client and see if there's something you can edit?  (I'm assuming this isn't a problem for other clients so it's something local to this particular one, but you probably know your DNS better than I do)

  • Kev_Lamb's avatar
    Kev_Lamb
    Level 6
    11 years ago

    Hi,

    I have checked and rewritten the hosts file on the Win2012 server and this still fails, I even removed the hosts file and checked I could still do a reverse nslookup to the Master from the client and thsi was Ok.

    Still getting the same entries in the bpcd log about the master and media server.

     

    Kev

  • Mark_Solutions's avatar
    Mark_Solutions
    Level 6
    11 years ago

    As your entries look OK try this:

    1. See what the Browser registry key is set to - this should match the Client_Name key

    2. Run this twice on the client:

    \program files\veritas\netbackup\bin\blclntcmd -clear_host_cache

    3. Check what the Port_BPCD key value is - it should be 13782

    4. Re-start the client service on the client

    5. Try to connect again

    Also on the client run bpclntcmd -sv to see what it brings back

  • Kev_Lamb's avatar
    Kev_Lamb
    Level 6
    11 years ago

    Hi Mark

    The Reg keys look correct (see attached doc) I have ran the clear_cache option twice and restarted the client services, also the output of the bpclntcmd -sv returns 7.5

    I am at a loss as to why it cannot relate to the Master Server

     

    Kev

  • Mark_Solutions's avatar
    Mark_Solutions
    Level 6
    11 years ago

    There doesn't look to be enough components in the registry there

    Could you try re-installing (run a repair) on the client - make sure AV is turned off and that you do everything using the Run As Administrator