Bpcd Error
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 Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research
Netbackup Error 58 Can't Connect To Client
Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano netbackup error 25 cannot connect on socket 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet STATUS CODE 25: Troubleshooting procedures for client Status 25 errors. netbackup error code 59 Article:000009351 Publish: Article URL:http://www.veritas.com/docs/000009351 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
Bptestbpcd
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 The master server is getting a status code 25 (cannot connect on socket) error when attempting to bring up the client host properties using the GUI or remote admin console. Cause A status 25 error
Error Code 25 In Netbackup
results from either a TCP SYN request sent to a client from the NetBackup server that was not acknowledged or the server was not resolvable so a TCP SYN request was not 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 failing to resolve the client by hostname, or the client can not resolve the NetBackup server by its IP address. For NetBackup clients running 6.x release, although the vnetd daemon is used for incoming connections, it is still required that bpcd perform the hostname compare to authenticate the NetBackup server. Solution Troubleshooting: Step 1: When troubleshooting status 25 errors on a NetBackup client, verify that the client was working prior to the issue. If it had been working try to determine what changes may have been made to the client server's OS or the network links. Step 2: In 6.x and above 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 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 bptestbpcd exit status 25 Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet General Error: Status code 23, socket read failed, during client vnetd port number backups or restores, or when loading client properties. Article:000090314 Publish: Article URL:http://www.veritas.com/docs/000090314 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome https://www.veritas.com/support/en_US/article.TECH141839 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 General Error: Status code 23, socket read failed, during client backups or restores, or when loading client properties. Error Message Status code 23, socket read failed Cause The keyfile.dat https://www.veritas.com/support/en_US/article.TECH57100 file in the 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 https://www.veritas.com/support/en_US/article.TECH68832 Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal https://www.veritas.com/support/en_US/article.000010655 Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet STATUS CODE 58: Can't connect to client. Troubleshooting procedures for Status 58 errors. Article:000037729 Publish: Article URL:http://www.veritas.com/docs/000037729 Support / Article Sign In Remember me Forgot Password? Don't netbackup error 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 58: Can't connect to client. Troubleshooting procedures for netbackup error 58 Status 58 errors. Error Message Status Code: 58 Solution Overview: A status 58 error can occur during connections to legacy processes; bpcd, bprd, bpdbm, bpjobd, vmd, etc. typically from master or media server to client, but alsofrom master server to media server, orfrom media servers to master, orfrom client to master servers, orin very rare cases from client to media server. The cause is that either a TCP SYN request did not reach the destination host, orthe expected processes were not listening on the destination host, orthe TCP SYN+ACK returned by the destination host did not reach the source host, orthe destination host could not validate that the inbound connection was from a valid NetBackup (NB) host, orthat PBX or vnetd on the destination host could not transfer the connection the desired daemon, orin rare instances that the destination host could not create a connection to the source host - for the same reasons as noted above. The majority of these situations are due to the TCP port(s) not being open through the firewall, daemon processes not runnin 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 59: access to the client was not allowed backing up a media server to its own disk storage unit. Article:000010655 Publish: Article URL:http://www.veritas.com/docs/000010655 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 59: access to the client was not allowed backing up a media server to its own disk storage unit. Error Message Job Details: 12/16/2010 1:44:12 PM - requesting resource DiskStuFor-media-server12/16/2010 1:44:13 PM - granted resource DiskStuFor-media-server12/16/2010 1:44:17 PM - end writing12/16/2010 1:45:45 PM - Error bpbrm(pid=2728) bpcd on media-server exited with status 59: access to the client was not allowedaccess to the client was not allowed(59) *************Media Server log snippets: bpcd 13:45:44.734 [1936.1360] <2> bpcd main: no authentication required13:45:44.750 [1936.1360] <2> bpcd peer_hostname: Connection from host media-server.enterprise.veritas.com (10.82.108.161) port 262313:45:44.750 [1936.1360] <2> bpcd valid_server: comparing master-server and media-server.enterprise.veritas.com13:45:44.750 [1936.1360] <2> hosts_equal: gethostbyname failed for media-server.enterprise.veritas.com: The requested name is valid, but no data of the r (0)13:45:44.750 [1936.1360] <2> bpcd valid_server: comparing media-server and media-Bptestnetconn