Verify that both the client and the server are operational. 2. Enable detailed activity logging: o Create a bpbkar activity log directory (UNIX or Windows NT only). On Sun Solaris, verify that all operating system patches are installed (see the Operating Notes section of the NetBackup Release Notes - UNIX). 3. The connection was terminated because VxSS authentication cannot be completed. have a peek here
Recommended Action: Check the NetBackup All Log Entries report for clues on where and why the failure occurred. This status code can also appear if the connection is broken between the master and slave server during a backup. Then, retry the operation and check the resulting activity log. Close Yeah, keep it Undo Close This video is unavailable.
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 Status Code 152 ==================== required value not set An incomplete request was made to the bpdbm process (on UNIX), or the NetBackup Database Manager service (on Windows). Also, see "Verifying Host Names and Services Entries" on page 31. 4.
Create a bpcd activity log directory on the client. Status Code 100 ==================== system error occurred while processing user command A system call failure in bparchive, bpbackup, bplist, or bprestore. Status Code 164 ==================== unable to mount media because it is in a DOWN, or otherwise not available A restore was attempted and the volume required for the restore was in Netbackup 7.7 Status Codes If the client software is earlier than 3.0, verify that the client is in a Standard type class.
Status Code: 36 Top Message: failed trying to allocate memory Explanation: Allocation of system memory failed. Netbackup Error Codes Pdf Status Code 238 ==================== the database contains conflicting or erroneous entries The catalog has an inconsistent or a corrupted entry. Status Code 225 ==================== text exceeded allowed length Text in a request exceeds a buffer size. weblink NetBackup runs client processes as the requesting user.
Status Code 70 ==================== an entry in the filelist expanded to too many characters The wildcards, which were used in one of the file list entries, specified too many files. Important Error Codes In Veritas Netbackup Statistics Search for: Recent Posts My new Blog Network Installation Manager(NIM) NTP Client configuration inAIX Enabling Telnet in Solaris10 Subsystem Resource Controller(SRC) Archives November 2012 Categories AIX AIX LESSONS GENERAL LINUX o Check the bpbkar and tar messages in the bpcd log file. Status Code 22 ==================== socket close failed A socket was not closed.
SearchStorage Tintri OS storage upgrade focuses on cloud, containers for DevOps Tintri storage moves 'in lockstep' with VMware for cloud, container and DevOps support with a vRealize Orchestrator plug-in and ... http://searchdatabackup.techtarget.com/tip/Five-Symantec-NetBackup-error-messages-and-how-to-resolve-them Status Code: 48 Top Message: client hostname could not be found Explanation: The system function gethostbyname() failed to find the client's host name. Netbackup Error Codes And Solutions It indicates the following: either the bpdbm process (on UNIX) or the NetBackup Database Manager service (on Windows) or the process that communicates with it has received unexpected information. Veritas Netbackup Error Codes List Status Code 24 ==================== socket write failed A write operation to a socket failed.
No Yes Did this article save you the trouble of contacting technical support? navigate here Recommended Action: 1. Read Symantec's advice on how to solve this status code. On a Windows NT NetBackup server, set the Verbose option on the General tab in the Master Server Properties dialog box (see "Using the Configure - NetBackup Window" on page 57). Netbackup Error Codes And Resolution
Status Code 108 ==================== Status code not available. Recommended Action: Verify that you have permission to delete the files and that the read-only flag is not set for the files. In some cases, 1,023-character file paths are allowed, but try to keep the path under 1,000 characters if possible. http://nbxcorp.com/error-code/wii-error-codes-101.html Corrupt binaries are one possible cause for this error.
A client and server with multiple network connections can encounter this problem in the following situation: the name by which the client is configured is not the one by which its Veritas Netbackup Error Codes Pdf Status Code 217 ==================== failed reading storage unit database information During its periodic checking of the NetBackup configuration, nbpem did not read the storage unit configuration. o On UNIX, and Macintosh clients, add a SERVER entry in the bp.conf file.
For Windows NT NetBackup servers: a. On Sun Solaris, verify that all operating system patches are installed (see the Operating Notes section of the NetBackup Release Notes - UNIX). 5. Status Code 281 ==================== vault core error An internal Vault error occurred. Netbackup Error Code 1 o Increase the amount of debug information included in the logs as explained in the activity log topics in Chapter 3, "Using the Logs and Reports." 3.
Status Code 211 ==================== Status code not available. It can also occur if a large number of concurrent data streams are active at the same time. Verify that the client name is correct in: o The NetBackup class configuration on the master server. http://nbxcorp.com/error-code/wep-error-codes.html Look in the activity log files to find more information on the problem.
There are a couple of things you can do in this situation. For detailed troubleshooting information, create an activity log directory for the process that you suspect of returning this status code. Status Code 186 ==================== tar received no data NetBackup did not send data to tar. Status Code 199 ==================== operation not allowed during this time period A user backup or archive was requested and this client is not in a policy that has the following: a
That storage unit may have more unused capacity now than it did when the job failed. This error indicates a problem on the master server. If the bpbrm log has entries similar to the following: bpbrm hookup_timeout: timed out waiting during the client hookup bpbrm Exit: client backup EXIT STATUS 41: network connection timed out then Watch QueueQueueWatch QueueQueue Remove allDisconnect Loading...
o The bp.ini file on OS/2 and NetWare target clients. 2. On UNIX systems, this error may be due to a lack of system resources for System V inter-process communication. 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 On Windows NT, verify that the recommended service packs are installed.
Status Code: 61 Top Message: wbak was killed Explanation: The wbak process on the Apollo was killed. Status Code: 15 Top Message: file close failed Explanation: A close of a file or socket failed. If the above actions do not reveal the problem, create an activity log directory for the process that returned this status code, retry the operation, and check the resulting activity log. On a UNIX client, add the VERBOSE option to the /usr/openv/netbackup/bp.conf file.
When the robot is controlled by an Automated Cartridge System, verify that the ACSLS system is up. 5.
© Copyright 2017 nbxcorp.com. All rights reserved.