Status 59 Issue
Updated: 21 May 2010 | 6 comments
Hello all,
So I'm having issues with status 59:
access to the client was not allowed
Relevant info:
Client
Windows 2003 server, standard sp1
Located within a DMZ
Netbackup 6.5.3
Master/Media Server:
Windows 2003 Enterprise SP2
Located on prod network in different subnet
Netbackup 6.5.3
What we've tried
- Telnet to/from client and to/from master/media server on ports 13724, 13721, 13720 both work.
- ping to client from master works on both ip and hostname.
- Ping to server vrom client fails on the hostname but goes through via ip
- waiting for results of bpclntcmd from client machine.
Other notesS
Since the client is in a dmz we are not allowed to modify the host file entries. I suspect there could be a reverselookup issue of some kind. But I'm not sure.
Thoughts, ideas and suggestions are appreciated and rewarded.
discussion Filed Under:
Comments
ANd I did do some research...
I viewed these technotes exftpp.symantec.com/pub/support/products/NetBackup_Enterprise_Server/277539.pdf
"I’m an early bird and a night owl. So I’m wise and I have worms."
- Michael Scott
does your client know about all your media servers
Alex,
Open the console, Host properties > clients > open the client properties . Check the 'Servers' section in the left hand pane.
Add all your media servers in that list.
-Rajeev
"Unix IS user friendly... It's just selective about who its friends are"
Yes...The above may fix your issues
Even i used to have same issues earlier..
After updating the servers list.. it got fixed.
--Thanks,
Jaya Syam
The Client is not able to
The Client is not able to match the connecting media server with an entry in the servers list in the bp.conf/registry. There are two possible causes:
1. The media/masterserver is not in the clients serverlist
2. The name of the media/masterserver cannot be (reverse) looked up
Since you cannot ping the name of the server from the client, i suspect the issue is the name resolution on your client. If there is no DNS in your DMZ, you have to get your NetBackup Servers into the hosts-file of all clients.
You can find further information in the bpcd logfile (C:\Program Files\Veritas\NetBackup\logs\bpcd).
Two things from your original
Two things from your original post:
1. Ping to server from client fails on the hostname but goes through via ip
2. we are not allowed to modify the host file entries.
Quite correct - the problem is with reverse lookup - the client needs to resolve the incoming request to a host name in order to validate the backup request against the list of SERVER names in it's configuration.
Try to add the server's IP address to the client's SERVER list.
Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows.
Handy NBU links
Master/Media Server(s) need to be in clients server list
Add server entries on Windows clients by doing the following:
1. Open the Backup, Archive, and Restore interface.
2. Select File > “Specify NetBackup Machines and Policy Type”.
3. Select the “Servers” tab.
4. Verify that the Master/Media Server(s) are added to this server list, and that the Master
Server is set as “current”.
5. Click OK after adding any needed servers and exit Backup, Archive and Restore.
Note: If server entries are modified on a NetBackup Master Server, it is necessary to stop and
restart NetBackup services/processes. Services/processes do not need to be restarted on a
Media Server or Client after updating the server list.
i faced same problem many time all i have to do was above, this should resolve the issue,
if ur still facing problem let us know.
Regards,
Venkat
Thanks & Regards,
Venki
Dont forget to Vote for + if you think suggestion is good, and mark as solution if it has resolved your problem.
Would you like to reply?
Login or Register to post your comment.