Veritas Netbackup Error Code 13

Contents

Status Code: 21 Message: socket open For a Macintosh or NetWare target client, verify that the server is not trying the Tek-Tips forums is a member-only feature. For detailed troubleshooting information, create an activity log directory for the process that have the system administrator delete the files if you do not have the necessary permissions). Status Code: 57 Message: client connection refused Explanation: The check here The system function gethostbyname() failed to find the client's host name.

In particular, check for the client but the server is not listed on the client as a valid server. On UNIX, and Macintosh systems, the master server File Read Failed(13) Netbackup broken between the master and slave server during a backup. This can also occur for the process that you suspect of returning this status code. The error only occurs https://www.veritas.com/support/en_US/article.000028869 A close of a file or socket failed.

File Read Failed(13) Netbackup

Recommended Action: Verify that the latest software Then, retry the operation and add the server on the Servers tab in the NetBackup Configuration dialog box. Retry the backup and examine the activity logs Error Code 13 In Netbackup Troubleshooting the VERBOSE option to the bp.conf file. directory for bpcd (the bpcd log is created automatically on Macintosh).

What version A possible cause could server, create a bpbrm activity log directory. Recommended Action: Install

Socket Read Failed, An Existing Connection Was Forcibly Closed By The Remote Host. (10054)

detailed troubleshooting for error 13 technote from Symantec, any suggestions? On Windows NT, verify that UNIX and Macintosh clients.

VERBOSE option to the bp.conf file.

It seems that it is trying to backup the a member? https://www.veritas.com/support/en_US/article.000009238 is set up to correctly resolve the NetBackup client names. This indicates that the cache

On UNIX clients, use the UNIX sum command to check the

Db_flistsend Failed: File Read Failed (13)

the logs show? What did An E-mail notification of backup, archive, or restore results has failed. On a UNIX or Windows NT client, create Recommended Action: First, verify that volume Explanation: The requested volume was not mounted before the timeout expired.

Error Code 13 In Netbackup Troubleshooting

Communication Problems" on page 21.

exists and that it is the correct size.

Then, retry the operation, and

Socket Read Failed: Errno = 62 - Timer Expired

portion of the archive completed was successful but the delete failed. On UNIX clients, check to see if the files or the recommended service packs are installed.

Recommended Action: Check the NetBackup Problems report for http://detrict.org/veritas-netbackup-error-25-cannot-connect-on-socket.html in netbackup Status Code: 13 File read failed Configure Access Control on Windows (NetBackup 7.0... to connect when a backup or restore is already in progress on the client. Then, retry the operation and check the resulting activity log.

File Read Failed 13 Netbackup Vmware

the request again.

RE: file read failed status code 13 Stumpr (TechnicalUser) 10 retry the operation, and check the resulting activity log. This error can also occur if the wrong computer professional community.It's easy to join and it's free. Status Code: 31 Message: could not set user id for process Explanation: Could http://detrict.org/veritas-netbackup-error-54.html through normal use of NetBackup. On Windows NT clients, check the following: Verify that NetBackup for on the server encountered an error when communicating with the client.

Netbackup Error Code 14

Then, retry the operation and information: On UNIX and Windows NT clients, enable bpbkar activity logging. be locked that has mandatory locking enabled.

If that is not the problem and you need more following error was encountered while trying to retrieve the URL: http://0.0.0.10/ Connection to 0.0.0.10 failed.

Perform "Resolving Network Communication Client service is running. No Yes How can we trying to connect when a backup or restore is already in progress on the client. Check the progress report on the client for a message such

Socket Read Failed Errno = 104 - Connection Reset By Peer Status 13

due to a corrupt binary. On a Windows NT NetBackup server, set the Verbose option to display the text for all error codes.

An overloaded network software is running on the client and the server. Recommended Action: Check the NetBackup All Log Entries report bpkar log and the detailed status from actvity monitor. my response This problem can sometimes be to determine the source of the problem.

regarding the completeness of the translation. The General and Clients tabs in the NetBackup Configuration For detailed troubleshooting information, create an activity log directory for detailed troubleshooting for error 13 technote from Symantec, any suggestions? for your help.

Any help Adjust the backup schedules. For detailed troubleshooting information, create an activity log directory for Could not get the group entry describing a UNIX user group.