Netbackup Error Status 58
Contents |
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing
Netbackup Error 59
Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom netbackup error code 58 in windows client Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 bptestbpcd: exit status = 25 Português Español USA Site: Veritas Veritas PartnerNet STATUS CODE 58: "Can't connect to client". Backups fail with status code 58 after enabling Veritas Security Services
Netbackup Cannot Connect On Socket
(VxSS) and NetBackup Access Control (NBAC). Article:000027851 Publish: Article URL:http://www.veritas.com/docs/000027851 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In
Netbackup Port Numbers
Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem STATUS CODE 58: "Can't connect to client". Backups fail with status code 58 after enabling Veritas Security Services (VxSS) and NetBackup Access Control (NBAC). Error Message can't connect to client Solution Overview: A Status 58 will occur when the server cannot connect to the client. This can occur for standard backups when there are problems with hostname resolution or network routing. This can also occur during catalog backups when the master server cannot make a network connection to a media server in order to read the catalog data. This can also happen when NetBackup Access Control (NBAC) is configured incorrectly.Troubleshooting:Verify the forward and reverse hostname lookups are working for the client. Also verify the network path is valid for the host. From the media server run the command:# telnet
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom status: failed, (42) connect_refused Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français
Connect Failed Status (18) Connect_failed
Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet GENERAL ERROR: Status 58 can't connect to netbackup status code 25 a Windows client Article:000005913 Publish: Article URL:http://www.veritas.com/docs/000005913 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your https://www.veritas.com/support/en_US/article.000027851 Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem GENERAL ERROR: Status 58 can't connect to a Windows client Error Message GENERAL ERROR: Status 58 can't connect to client Solution ISSUE: GENERAL ERROR: Status 58 can't connect https://www.veritas.com/support/en_US/article.000005913 to client ENVIRONMENT/CONDITIONS: This issue has been known to occur on Windows Client when the machine has run out of non-interactive desktop heap or has a memory issue of some kind. Typically the client may work for several days then start getting status 58 errors. EVIDENCE: bpcd log from the client: 01:09:59.389 [6560.6920] <4> bpcd valid_server: hostname comparison succeeded 01:09:59.577 [6560.6920] <2> bpcd main: output socket port number = 1 01:10:02.374 [6560.6920] <2> get_long: (2) premature end of file (byte 1) 01:10:02.374 [6560.6920] <2> get_vnetd_forward_socket: get_string ipc_string failed: 5 01:10:02.374 [6560.6920] <16> bpcd main: get_vnetd_forward_socket failed: 23 SOLUTION/WORKAROUND: Rebooting the client will resolve the issue for a short time, however the issue could be the result of the client running out of Non-interactive Desktop Heap Memory. The issue is better seen if you connect to the problem host via RDP using the -console switch to see the problem program's/systems's pop up errors. Suggestion is to increase the desktop heap setting on the client server- HKEY_LOCAL_MACINE\SYSTEM\CurrentControlSet\Control\Session Manager\SubSystems\ Type REG_EXPAND_SZ: Value: Windows Original windows key: %SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows SharedSection=1024,3072,512 Windows=On SubSystemType=Windows ServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3 ServerDll=winsrv:ConServe
58: can't connect to client Details: Overview: A status 58 error results from either a TCP SYN request sent to a client from the NetBackup (NBU) server that was not acknowledged http://thebackupsblog.blogspot.com/2009/08/troubleshooting-status-code-58.html or the server was not resolvable so a TCP SYN request was not http://unix.ittoolbox.com/groups/technical-functional/solaris-l/netbackup-error-58-cant-connect-to-client-5560887 sent. The majority of the causes of this issue are due to the client not listening on the BPCD or VNETD ports, the master server unable to resolve the client by hostname, or the client can not resolve the NBU server by its IP address. NBU clients running 6.x release, though it netbackup error uses the vnetd daemon for incoming connections, it still requires bpcd to perform the hostname compare to authenticate the NBU server.Troubleshooting:Below are steps you can use to help isolate the issue.When troubleshooting status 58 errors on a NetBackup client, the first thing to test is to whether or not you can access the client from the client Host Properties from the master server. If that netbackup error status works the same ports are involved when backing up the client as to when you access the client host properties. Connecting to the client host properties from the master server would prove the master server can access the client without any problems. So if using a storage unit on the master server you should be able to backup the client without getting the status 58 error. In 6.x environments you can use the command- bptestbpcd to verify you can connect to both the vnetd and bpcd ports on the client server.e.g.bptestbpcd -verbose -debug -client See the tech note 277901 for additional details on use of that command. http://entsupport.symantec.com/docs/277901 If still getting status 58 errors after ensuring the master server can connect to the client, focus on the media server used during the backup. The problem is more than likely with the client hostname lookup or gethostbyname call made to DNS or local host file on the media server.If the master server can not connect to the client when trying to access the client host properties, or the point of failure appears to be with the media server, below are steps you can tak
Technology and Trends Enterprise Architecture and EAI ERP Hardware IT Management and Strategy Java Knowledge Management Linux Networking Oracle PeopleSoft Project and Portfolio Management SAP SCM Security Siebel Storage UNIX Visual Basic Web Design and Development Windows < Back CHOOSE A DISCUSSION GROUP Research Directory TOPICS Database Hardware Networking SAP Security Web Design MEMBERS Paul_Pedant DACREE MarkDeVries MacProTX VoIP_News Inside-ERP I_am_the_dragon Inside-CRM maxwellarnold Michael Meyers-Jouan TerryCurran Chris_Day Andrew.S.Baker Ramnath.Awate JoeTorre Locutus Craig Borysowich Dennis Stevenson mircea_luca Richard DukeGanote iudithm Clinton Jones bracke Nikki Klein AbhaiTripathi Iqbalyk jakarman Adrian_Grigoriu knowscognosdoi COMPANIES GeoTrust Juniper Networks Silver Peak Sophos View All Topics View All Members View All Companies Toolbox for IT Topics UNIX Groups Ask a New Question Solaris The Solaris group is a forum where peers share technical expertise, solve problems, and discuss issues related to the Solaris operating system, including OS-related malfunctions, security issues, and network performance. Home | Invite Peers | More UNIX Groups Your account is ready. You're now being signed in. Solve problems - It's Free Create your account in seconds E-mail address is taken If this is your account,sign in here Email address Username Between 5 and 30 characters. No spaces please The Profile Name is already in use Password Notify me of new activity in this group: Real Time Daily Never Keep me informed of the latest: White Papers Newsletter Jobs By clicking "Join Now", you agree to Toolbox for Technology terms of use, and have read and understand our privacy policy. Netbackup - Error '(58) Can't Connect to Client" olakunleoj asked Aug 7, 2014 | Replies (3) I was using netbackup for my backup, the netbackup was on Solaris 10 and I have several Windows 8 server as a client recently one of my client severs displays error "(58) can't connect to client " 08/06/2014 09:02:23 - Info nbjm (pid=7874) s