GENERAL ERROR: Network Protocol Error 39
| Article:TECH52616 | | | Created: 2007-01-11 | | | Updated: 2008-01-11 | | | Article URL http://www.symantec.com/docs/TECH52616 |
Problem
GENERAL ERROR: Network Protocol Error 39
Solution
Overview:
Network
Protocol Error 39 - any NBU task that requires any master\media server
communication can result in this error.
Troubleshooting:
One possible
root cause of this error is the existence of unresolvable server names in the
<install_path>\VERITAS\NetBackup\Remote_Versions
directory. Any master to media server communication will spawn a named
server entry in this directory. Decommissioned media server names may
still exist in this directory.
This directory
is designed for version checking between media servers.
Example:
Log
Files:
Various
NetBackup log files may capture the Network Protocol Error 39,
including:
<install_path>\Veritas\NetBackup\logs\nbpushdata
<install_path>\Veritas\NetBackup\logs\nbconsole
log
Resolution:
Deleting the
entire contents of the
<install_path>\VERITAS\NetBackup\Remote_Versions directory (without
deleting the directory itself) on the master server and all media servers is the
resolution to this issue. Veritas NetBackup (tm) will repopulate this folder
with the correct entries anytime a connection is made between the master and a
media server.
Because the
master server will try to verify the host names of all entries contained in this
file, the Network Protocol Error 39 can post for Remote_Version entries
that the master cannot resolve.
In NetBackup
6.0 the master server uses this directory to verify the version of the media
server. A connection is made to the media server either using
vnetd or
vmd depending on the NetBackup version
found.
|
|
Legacy ID
289917
Article URL http://www.symantec.com/docs/TECH52616
Terms of use for this information are found in Legal Notices
Thank you.