RE: [Veritas-bu] Windows backup failing to Unix Server - Succeeds to Windows server
Title: Message In the netbackup client on the windows system, there are settings to configure the client name and server that it should talk to, same as the settings in the bp.conf on a *nix box. when you start the client GUI on the machine, click file, then "specify Netbackup machines and policy type" or something to that effect. then there should be client name and server name tabs in there. (sorry if that's vague, but I don't deal with windows client side stuff very often) Also, you say it works with windows but not unix master.it's possible that even if everything else is ok (server names, etc) that it still won't work. Actually, I have a feeling this stuff is ok, that you have the correct server name. because you mention this: "bpcd valid_server: comparing cthroat.water.com and atubks01.dsw.net. atubks01.dsw.net is the name of the Unix server. cthroat.water.com was our old server and that address has been aliased to point to the new server." it could be that the windows client is resolving the windows server using WINS. When it goes to talk to the unix master, it looks to DNS.then the problem comes inyou mention a new name with an alias to an old when you do a backup, the client basically does this.. sees an incoming connection from 10.10.10.10 perform a reverse look up on the address. reverse lookup returns cthroat.water.com Checks the server configured in the registry (bp.conf equivalent) and finds atubks01.dsw.net These don't match, so your backup fails with a status 59. You need to remove cthroat.water.com from your DNS table, add an entry for atubks01.dsw.net and if you still have old systems around that point to the old name, create an alias for cthroat.water.comto point to the new server. Netbackup uses forward AND reverse DNS lookups to verify connections.an alias only works for forward lookups. Might want to check that out. Paul -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff LightnerSent: December 30, 2005 4:10 PMTo: veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] Windows backup failing to Unix Server - Succeeds to Windows server An odd one here. Our Windows Admin has attempted to setup a Windows machine to be backed up by our Unix Master. When he does he gets a Status 59 which means the server isnt recognized by the client. When he uses his Windows Master to do this it goes just fine. Per the troubleshooting we turned on logging on the client. In the bprd log we see lines like: bpcd valid_server: comparing cthroat.water.com and atubks01.dsw.net. atubks01.dsw.net is the name of the Unix server. cthroat.water.com was our old server and that address has been aliased to point to the new server. After the initial statements we see bcd valid_server hostname comparison succeeded so that seems good. Later in the log though I see it comparing the Windows Master to my main Production DB server which is confusing because: 1) Weve told it to use the Unix Master which doesnt know about the Windows Master. 2) It says the Production DB server is not a server (presumably meaning master) which is true but also says not a media server which is NOT true. If this were Unix Id think he had odd entries in bp.conf that needed to be changed. However I dont know Windows and didnt see anything called bp.conf when doing an explore of the Netbackup directory there. Any ideas on what I could check? The troubleshooting guide makes it clear this is an issue with the client recognizing the server not vice-versa so I need some idea what to check on the Windows side. Jeffrey C. Lightner Unix Systems Administrator DS Waters of North America 678-486-3516
RE: [Veritas-bu] Windows backup failing to Unix Server - Succeeds to Windows server
Title: Windows backup failing to Unix Server - Succeeds to Windows server Check to see if you can ping the Unix master and then run bpclntcmd. Your network settings will have to be correct to back up to the Unix master (dns, netmask...). WINS resolution will get you to the Windows master. Bobby Williams 2205 Peterson Drive Chattanooga, Tennessee 37421 423-296-8200 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff LightnerSent: Friday, December 30, 2005 4:10 PMTo: veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] Windows backup failing to Unix Server - Succeeds to Windows server An odd one here. Our Windows Admin has attempted to setup a Windows machine to be backed up by our Unix Master. When he does he gets a Status 59 which means the server isnt recognized by the client. When he uses his Windows Master to do this it goes just fine. Per the troubleshooting we turned on logging on the client. In the bprd log we see lines like: bpcd valid_server: comparing cthroat.water.com and atubks01.dsw.net. atubks01.dsw.net is the name of the Unix server. cthroat.water.com was our old server and that address has been aliased to point to the new server. After the initial statements we see bcd valid_server hostname comparison succeeded so that seems good. Later in the log though I see it comparing the Windows Master to my main Production DB server which is confusing because: 1) Weve told it to use the Unix Master which doesnt know about the Windows Master. 2) It says the Production DB server is not a server (presumably meaning master) which is true but also says not a media server which is NOT true. If this were Unix Id think he had odd entries in bp.conf that needed to be changed. However I dont know Windows and didnt see anything called bp.conf when doing an explore of the Netbackup directory there. Any ideas on what I could check? The troubleshooting guide makes it clear this is an issue with the client recognizing the server not vice-versa so I need some idea what to check on the Windows side. Jeffrey C. Lightner Unix Systems Administrator DS Waters of North America 678-486-3516
RE: [Veritas-bu] Windows backup failing to Unix Server - Succeeds to Windows server
Title: Message Under Windows the bp.conf entries are all stored in the registry instead. Just go into the host properties of the client through the JAVA GUI and it'll look much the same as a UNIX client. Go and configure yourSERVER and MEDIA_SERVER entriesas normal. If you get another "access denied" message when trying to pull up the client's host properties, you'll need to have your SA go in through his Windows Master and add the UNIX Master to the SERVERs list on the client. Otherwise, it sounds like you just need to add your media server as a SERVER or MEDIA_SERVER. - John Nardello -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff LightnerSent: Friday, December 30, 2005 1:10 PMTo: veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] Windows backup failing to Unix Server - Succeeds to Windows server An odd one here. Our Windows Admin has attempted to setup a Windows machine to be backed up by our Unix Master. When he does he gets a Status 59 which means the server isnt recognized by the client. When he uses his Windows Master to do this it goes just fine. Per the troubleshooting we turned on logging on the client. In the bprd log we see lines like: bpcd valid_server: comparing cthroat.water.com and atubks01.dsw.net. atubks01.dsw.net is the name of the Unix server. cthroat.water.com was our old server and that address has been aliased to point to the new server. After the initial statements we see bcd valid_server hostname comparison succeeded so that seems good. Later in the log though I see it comparing the Windows Master to my main Production DB server which is confusing because: 1) Weve told it to use the Unix Master which doesnt know about the Windows Master. 2) It says the Production DB server is not a server (presumably meaning master) which is true but also says not a media server which is NOT true. If this were Unix Id think he had odd entries in bp.conf that needed to be changed. However I dont know Windows and didnt see anything called bp.conf when doing an explore of the Netbackup directory there. Any ideas on what I could check? The troubleshooting guide makes it clear this is an issue with the client recognizing the server not vice-versa so I need some idea what to check on the Windows side. Jeffrey C. Lightner Unix Systems Administrator DS Waters of North America 678-486-3516
RE: [Veritas-bu] Windows backup failing to Unix Server - Succeeds to Windows server
Title: Windows backup failing to Unix Server - Succeeds to Windows server All serversshould be defined in bp.conf on the Unix Master server, no matter what OS. So you should have an entry for your DB server in bp.conf such as: SERVER =DB server hostname. Rusty From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff LightnerSent: Friday, December 30, 2005 3:10 PMTo: veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] Windows backup failing to Unix Server - Succeeds to Windows server An odd one here. Our Windows Admin has attempted to setup a Windows machine to be backed up by our Unix Master. When he does he gets a Status 59 which means the server isnt recognized by the client. When he uses his Windows Master to do this it goes just fine. Per the troubleshooting we turned on logging on the client. In the bprd log we see lines like: bpcd valid_server: comparing cthroat.water.com and atubks01.dsw.net. atubks01.dsw.net is the name of the Unix server. cthroat.water.com was our old server and that address has been aliased to point to the new server. After the initial statements we see bcd valid_server hostname comparison succeeded so that seems good. Later in the log though I see it comparing the Windows Master to my main Production DB server which is confusing because: 1) Weve told it to use the Unix Master which doesnt know about the Windows Master. 2) It says the Production DB server is not a server (presumably meaning master) which is true but also says not a media server which is NOT true. If this were Unix Id think he had odd entries in bp.conf that needed to be changed. However I dont know Windows and didnt see anything called bp.conf when doing an explore of the Netbackup directory there. Any ideas on what I could check? The troubleshooting guide makes it clear this is an issue with the client recognizing the server not vice-versa so I need some idea what to check on the Windows side. Jeffrey C. Lightner Unix Systems Administrator DS Waters of North America 678-486-3516