Netbackup Error 54 Windows
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 Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet STATUS CODE: 54 "Timed out connecting to client" occurs when backing up a Novell NetWare client. Article:000029216 Publish: Article URL:http://www.veritas.com/docs/000029216 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 Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem STATUS CODE: 54 "Timed out connecting to client" occurs when backing up a Novell NetWare client. Error Message timed out connecting to client (54) Solution Overview: A Status 54 "Timed out connecting to client" error occurs when backing up a NetWare client. This can be because the master or media server is configured to use non-reserved ports, but the NetWare client is not.Troubleshooting:Within the Veritas NetBackup (tm) Administration Console, pull up the Host Properties for the master or media servers that access the client: 1. Launch the NetBackup Administration Console, connecting to the master server 2. Expand Host Properties in the left pane 3. Select Media Server in the left pane 4. In the right pane, double click the media server in question that backs up the NetWare client in question 5. Under the Port Ranges section, identify if non-reserved ports are being used (Figure 1) Figure 1: Non-reserved ports are being used to connect to clients The Client Reserved Port Window property specifies the range of reserved ports that are used for connecting to NetBackup on other compu
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 Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet STATUS CODE 54: Veritas NetBackup for SQL Server client is located https://www.veritas.com/support/en_US/article.TECH38541 outside a firewall and backups fail intermittently with NetBackup Status Code 54 (timed out connecting to client). Article:000087014 Publish: Article URL:http://www.veritas.com/docs/000087014 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 https://www.veritas.com/support/en_US/article.000087014 to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem STATUS CODE 54: Veritas NetBackup for SQL Server client is located outside a firewall and backups fail intermittently with NetBackup Status Code 54 (timed out connecting to client). Error Message timed out connecting to client Solution Overview: Veritas NetBackup for SQL Server client is located outside a firewall and backups fail intermittently with NetBackup Status Code 54 (timed out connecting to client). Windows-NT file system backups consistently complete with success (Exit Status 0). SQL Server backups, however, sometimes fail with exit status 54.Troubleshooting: Enable the dbclient log file on the SQL server. Log Files: The dbclient log file shows:connectSock: ERR - connect() to server failed, Only one usage of each socket address (protocol/network address/po
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 https://www.veritas.com/support/en_US/article.000032603 Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Status Code 54: Timed out connecting to client. Article:000032603 Publish: Article URL:http://www.veritas.com/docs/000032603 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 netbackup error Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem Status Code 54: Timed out connecting to client. Error Message Status code 54: Timed out connecting to client. Solution Overview:Status Code 54: Timed out connecting to client.Troubleshooting:After bpcd is started by netbackup error 54 the inbound connection from the bpbrm, it needs to complete a second socket connection to bpbrm before starting bpbkar, tar, or other client processes. Prior to attempting to complete the second connection, bpcd has to obtain a source port from the operating system from which to originate the connection. If ports are not available, the bpcd log will show a message similar to this. 15:20:30 [19683] <2> bpcd main: offset to GMT 25200 15:20:30 [19683] <2> bpcd main: setup_sockopts complete 15:20:30 [19683] <2> bpcd main: output socket port number = 1020 15:20:30 [19683] <2> bpcd peer_hostname: Connection from host nitro (192.168.101.212) port 1022 15:20:30 [19683] <2> bpcd main: Peer hostname is nitro 15:20:30 [19683] <16> bpcd main: Couldn't reserve output port. Errno = 11: Resource temporarily unavailable Reservation, bind, or resource busy/unavailable log entries like that above indicate that bpcd could not successfully bind a source port to use for the second connection. Consequently bpbrm will timeout in 60 seconds and return a status 54 for the job.Connection failure messages (unlike the one above) may be caused by name reso