Netbackup Error Status 54
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, Client backups fail with a status 54 if the bp.conf file is empty or is missing a SERVER entry Article:000029308 Publish: Article URL:http://www.veritas.com/docs/000029308 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 Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem STATUS CODE: 54, Client backups fail with a status 54 if the bp.conf file is empty or is missing a SERVER entry Error Message Timed out connecting to client(54) Solution Overview:The bpcd daemon will fail to start if the /usr/openv/netbackup/bp.conf file on the client is missing a SERVER entry or is zero bytes in size. The bpcd daemon will still be registered with the inetd daemon and a telnet to the port will be successful. However, the bpcd daemon will not start properly and no messages will be generated in the /usr/openv/netbackup/logs/bpcd/log.
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 outside a firewall and backups fail https://www.veritas.com/support/en_US/article.TECH38741 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 to Subscribe Please sign in to set up your https://www.veritas.com/support/en_US/article.000087014 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/port) is normally permitted. Resolution: There are two possible solutions to this issue: Solution 1. Enable the Use Random Port
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 https://www.veritas.com/support/en_US/article.TECH38541 Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 https://support.symantec.com/en_US/article.TECH20449.html 한국어 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 netbackup error 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 netbackup error status 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 computers. This setting applies when connecting to NetBackup on a computer configured to accept only reserved ports. If the check box for non-reserved ports is selected here, then clients will need to be configured to accept incoming connections on non-reserved ports.Client Log Fil
PKI Service Identity Access Manager Shop Online Cyber Security Services Managed Security Services DeepSight Intelligence Incident Response Security Simulation Website Security SSL Certificates Complete Website Security Code Signing Certificates Norton Shopping Guarantee Buy SSL Products A-Z Services Services Home Business Critical Services Consulting Services Customer Success Services Cyber Security Services Education Services Solutions Solutions Home Topics Encryption Everywhere Internet of Things Next Generation Endpoint Office 365 Industries Automotive Cyber Insurance Education Financial Services Global Service Providers Industrial Control Systems Healthcare Retail Government Federal Government State & Local Support Center Technical Support Symantec Connect Buying Programs Upgrades Maintenance & Renewals Training Security Center Security Center Home Blogs ISTR Threats Virus Definitions and Security Updates Removal Tools Partner Find a Partner Become a Partner Login Required Login into Partner Portal Partner Licensing Partner Renewals Partner Training Margin Builder Opportunity Registration Financial Benefits English 中文(简体) 中文(繁體) Česká English Français Deutsch Magyar Italiano 日本語 한국어 Polski Português Pусский Español Site: Symantec Enterprise Small Business Norton United States Search Support Home Support Home MySymantec Licensing Products A-Z Login Profile Subscriptions Logout Login Forgot Password? Don't have a SymAccount? Create a SymAccount now!' STATUS CODE 54: Oracle restores may fail with a NetBackup Status Code 54 (timed out connecting to client) if RMAN simultaneously requests un-multiplexed restores to different RMAN channels of a backup set that are on the same media. TECH20449 October 24th, 2013 http://www.symantec.com/docs/TECH20449 Support / STATUS C