Home > Error Code > Symantec Netbackup Error Codes

Symantec Netbackup Error Codes


Check the Problems report for information about the error. 2. Recommended Action: 1. Both logs are created automatically. Status Code 265 ==================== session id file is empty or corrupt The session ID that is stored in the following file is corrupt. navigate here

Err no= 242: No route to host 01/31/96 14:05:48 ruble crabtree.null.com successfully wrote backup id crabtree.null.com_0823125016, copy 1, fragment 1, 440864 Kbytes at 628.538 Kbytes/sec 01/31/96 14:05:51 netbackup crabtree.null.com CLIENT crabtree.null.com If the error occurs during a backup, pay attention to what is being backed up. Status Code 268 ==================== the vault session directory is either missing or inaccessible This error occurs when a Vault job cannot access the following: UNIX: /usr/openv/netbackup/vault/sessions Windows: install_path\NetBackup\vault\sessions This directory is Rating is available when the video has been rented.

Netbackup Error Codes And Resolution

Perform "Resolving Network Communication Problems" on page 21. 3. Use your system's ps command and monitor CPU utilization to help decide which of the above conditions exist. right?.

If a process was unable to report the extended error status as the final job status, the job exits with status 252. On UNIX clients, check for core files in the / directory. 4. This problem can occur during a backup or restore in either a single or a multiple server configuration. Netbackup Important Error Codes You could also try -- regardless of whether the system is physical or virtual -- a simple reboot.

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 Veritas Netbackup Error Codes List Status Code 79 ==================== unsupported image format for the requested database query Possible causes are that the images to be synthesized were generated as follows: using an ASCII catalog, for a This status code is used for a generic system call failure that does not have its own status code. The log messages were similar to the following: 01/31/96 14:05:23 ruble crabtree.null.com from client crabtree.null.com: ERR - Cannot write to STDOUT.

Status Code 16 ==================== unimplemented feature The specified operation is not implemented. Netbackup Error Code 1 Recommended Action: 1. Status Code 84 ==================== media write error The system's device driver returned an I/O error while NetBackup wrote to removable media or a disk file. Status Code 54 ==================== timed out connecting to client The server did not complete the connection to the client.

Veritas Netbackup Error Codes List

However, the synthetic backup job fails with this error if the TIR restore fails due to bad, missing, or vaulted media or a bad drive. If the server is a valid slave server, verify that the storage unit for the slave server is defined. Netbackup Error Codes And Resolution Status Code 139 ==================== Status code not available. Netbackup 7.7 Status Codes Status Code 149 ==================== master server request failed None Status Code 150 ==================== termination requested by administrator The process terminates (or has terminated) as a direct result of a request from

If you cannot determine the cause from the Problems report, create activity log directories for the processes that could have returned this status code. http://allconverter.net/error-code/symantec-netbackup-error-code-130.html b. Check the NetBackup Problems report for clues on why the failure occurred. 2. 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. Important Error Codes In Veritas Netbackup

Status Code 2 ==================== none of the requested files were backed up A backup or archive did not back up any of the files in the file list.This status code applies Related This entry was posted in Netbackup and tagged Netbackup Status Code, Veritas Netbackup, Veritas Netbackup Error Codes, Veritas Netbackup Troubleshooting Guide. Please try the request again. his comment is here For detailed troubleshooting information, create an activity log for the process that you suspect of returning this status code.

This failure may be due to the following: * An overloaded system * Insufficient swap space or physical memory * Too many processes are running on the system Status Code 29 Veritas Netbackup Error Codes Pdf Status Code: 54 Top Message: timed out connecting to client Explanation: The server could not complet e the connection to the client. Increase the debug or log level as explained in the activity log topics in Chapter 3, "Using the Logs and Reports." c.

Status Code: 26 Top Message: client/server handshaking failed Explanation: A process on the server encountered an error when communicating with the client.

Storage pros confident their business disaster recovery plan will work SearchStorage Hot data storage technology trends for 2017 Learn what's hot and what's not-quite-so-hot on our list of data storage technology Status Code 91 ==================== fatal NB media database error The tape manager (bptm) received an error while it read or updated its media catalog. Status Code 154 ==================== storage unit characteristics mismatched to request A backup was attempted and the storage unit selected for use had the characteristics that were not compatible with the backup Netbackup Status Code 156 Focus attention on a cognitive data management system Jon Toigo advises paying less attention to storage component stories and more to system-focused narratives such as a cognitive ...

For detailed troubleshooting information, create an activity log directory for the process that you suspect of returning this status code. On UNIX systems, this error may be due to a lack of system resources for System V inter-process communication. Please try again later. http://allconverter.net/error-code/symantec-netbackup-error-code-84.html Status Code 15 ==================== file close failed A close of a file or socket failed.

Possible causes include: * An I/O error occurred during a write to the file system. * Write to a socket failed. Sign in to make your opinion count. Recommended Action: Try the backup again. Status Code 214 ==================== Status code not available.

For example, if you see a message similar to the following in the Problems report or bpdbm activity log: 06/27/95 01:04:00 romb romb db_FLISTsend failed: system call failed (11) 06/27/95 01:04:01 NetBackup executes client processes as the requesting user. You also agree that your personal information may be transferred and processed in the United States, and that you have read and agree to the Terms of Use and the Privacy Status Code 256 ==================== logic error encountered An internal Vault error occurred.

This email address is already registered. This problem can occur during a backup or restore in either a single or a multiple server configuration. Sign in to report inappropriate content. Set up activity logging: o On UNIX and Windows NT clients, create an activity log directory for bpbkar.

Create an activity log directory for the process that reported the problem and the operation. This could be caused by the system being overloaded with too many processes and not enough physical or virtual memory. Verify that the client name is correct in: o The NetBackup class configuration on the master server. But the internet of things will soon make eMMC ...

This can occur because the backup job was terminated or the child process was terminated by another error. Recommended Action: Perform "Resolving Network Communication Problems" on page 21. This problem can occur in the following situation: when a process tries to connect to the NetBackup request daemon (bprd) or database manager daemon (bpdbm) and the daemon is not running. Correct problems that you find and retry the restore.

Check the All Log Entries and Problems reports to determine which system call failed and other information about the error. 2. To back up network drives or UNC paths, change the NetBackup Client service startup to log in as a user that has permission to access network drives. Possible reasons for this error are as follows: * Media ID is already active in the NetBackup media catalog on this server * Media ID is not in the volume configuration Status Code 82 ==================== media manager killed by signal Another process or a user terminated the tape manager (bptm) or disk manager (bpdm).