Home > Error Code > Symantec Netbackup Failure Codes

Symantec Netbackup Failure Codes

Contents

Check the NetBackup Problems report for clues on where and why the failure occurred. Status Code: 25 Top Message: cannot connect on socket Explanation: A process timed out while connecting to another process for a particular operation. Status Code: 1 Top Message: "the requested operation was partially successful" Explanation: A problem that may require corrective action was detected during the requested operation. For detailed troubleshooting information, create activity log directories for the processes that you suspect of returning this status code. this contact form

Create/Manage Case QUESTIONS? The only way to correct this particular condition is to figure out what the error means. For detailed troubleshooting information, create an activity log directory for the process that returned this status code, retry the operation, and check the resulting activity log. Email Address (Optional) Your feedback has been submitted successfully!

Netbackup Error Codes And Resolution

Status Code: 3 Top Message: valid archive image produced, but no files deleted due to non-fatal problems Explanation: The backup portion of the archive command reported problems so the files were Bookmark the permalink. A symptom is an entry similar to the following in a NetBackup log (or report) could not allocate enough shared memory If you see this type of message, refer to the

To display this dialog box, start the Backup, Archive, and Restore interface on the client and click Configure on the Actions menu (also see "Using the Configure - NetBackup Window" on Status Code: 28 Top Message: failed trying to fork a process Explanation: A fork of a child process failed (on UNIX) or a CreateProcess failed (on Windows NT). This problem can occur during a backup or a restore. Netbackup Important Error Codes Check the permissions on the parent directory and verify that NetBackup services are started with a "Logon as" account that has permission to create the directory. 3.

If the preceding steps do not resolve this problem, see "Resolving Network Communication Problems" on page 21. 61 62 63 64 65 66 67 68 69 Top Status Code: 60 Veritas Netbackup Error Codes List If you are backing up a network drive or a UNC (universal naming convention) path, use the Services application in the Windows NT Control Panel to verify that the NetBackup Client Retry the backup and examine the resulting logs to determine the cause of the failure. 1. NetBackup cannot delete files unless you are either the user that owns the files, a superuser on UNIX, or an administrator on Windows NT.

o Check the bpbkar and tar messages in the bpcd log file. Netbackup Error Code 1 Generated Wed, 07 Dec 2016 02:47:57 GMT by s_wx1200 (squid/3.5.20) For detailed troubleshooting information, create an activity log directory for the process that returned this status code, retry the operation, and check the resulting activity log. If virtual memory is the problem, shut down unused applications or increase the amount of virtual memory.

Veritas Netbackup Error Codes List

Recommended Action: If the server is a valid server, add its name to the client's server list: On Windows NT, 98, and 95 clients, add the server on the Servers If rbak does not exit with a status message, NetBackup cannot determine whether the restore worked or not. Netbackup Error Codes And Resolution Working... Netbackup 7.7 Status Codes The progress log also usually names the script.

Status Code: 62 Top Message: wbak exited abnormally Explanation: The wbak process on the Apollo exited abnormally. http://allconverter.net/error-code/symantec-netbackup-error-code-130.html Recommended Action: Verify that you have permission to delete the files and that the read-only flag is not set for the files. If there are slave servers involved, create a bpbrm activity log directory on them. 4. For a FlashBackup client, check the /var/adm/messages log for errors like the following: Mar 24 01:35:58 bison unix: WARNING: sn_alloccache: cache /dev/rdsk/c0t2d0s3 full - all snaps using this cache are now Important Error Codes In Veritas Netbackup

TECHNOLOGIES Storage Backup Storage virtual appliances Virtual machines PRODUCTS Symantec NetBackup + Show More In this Article Share this item with your network: Related Content Error with VERITAS NetBackup for Oracle This error can be caused by the system not having enough semaphores allocated. Status Code: 26 Top Message: client/server handshaking failed Explanation: A process on the server encountered an error when communicating with the client. navigate here On a UNIX NetBackup server, add the VERBOSE option to the bp.conf file.

Rating is available when the video has been rented. Netbackup Status Code 156 Status Code: 37 Top Message: operation requested by an invalid server Explanation: A request was made to the NetBackup request daemon (bprd) or NetBackup database manager daemon (bpdbm) by an invalid On UNIX and Windows NT clients, create a bpbkar activity log directory.

Sign in Share More Report Need to report the video?

On a UNIX client, add the VERBOSE option to the bp.conf file. Recommended Action: 1. Enable detailed activity logging on the client: o Create bpcd and bpbkar (UNIX or Windows NT only) activity log directories. Veritas Netbackup Error Codes Pdf Recommended Action: 1.

On UNIX clients, verify that the /usr/openv/netbackup/bin/bpcd binary exists and that it is the correct size. If the server cannot connect to the client, create bpcd or bpbkar (UNIX and Windows NT only) activity log directories on the client, retry the operation, and check the resulting logs. For this case, try adding or modifying the CLIENT_READ_TIMEOUT and CLIENT_CONNECT_TIMEOUT values in the server's /usr/openv/netbackup/bp.conf file. http://allconverter.net/error-code/symantec-netbackup-error-code-84.html On a UNIX NetBackup server, add the VERBOSE option to the bp.conf file.

Loading... This error can also occur if the wrong parameters are used when executing a command line. The common error that always faced with my customer is ‘status code 196 : client backup was not attempted because backup window closed‘, or the worst is the got ‘status code o If you can view the report and have not found an entry related to this problem, create activity log directories for the related processes that were running when the error

Close Sign In Download Attachments Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Description This guide documents the NetBackup status codes, providing definitions, actions, and Correct problems and retry the archive. In some cases, error messages in the NetBackup log indicate a backup failure due to an error in semaphore operation; another symptom is the inability of the NetBackup Device Manager service On Windows NT, stop and restart the NetBackup Request Manager and NetBackup Database Manager services. 3.

This can occur because the backup job was terminated or the child process was terminated by another error. This error can occur when there is only one file in the file list and the file cannot be backed up due to an I/O error. Download this invaluable guide to discover why you need to know the difference between the two, and for important tips and best practices on building or refining the best data archiving fabrykagwozdzi 21,174 views 4:17 Tech Tuesday: Expediting Veritas NetBackup Troubleshooting: Tips & Practices for Creating Logs - Duration: 48:29.