On a UNIX NetBackup server, add the VERBOSE option to the bp.conf file. This lock file synchronizes process activities (for example, it prevents more than one daemon from running at a time). Recommended Action: First, verify that the server did not crash. Status Code 145 ==================== daemon is already running Another copy of the process is running. Check This Out
Status Code 116 ==================== VxSS authentication failed On either end of a socket connection, the parties did not mutually authenticate each other. Recommended Action: 1. On a UNIX or Windows NT clients, check for the following problems with the bpbkar client process. Possible causes are: · A process does not have permission to create the directory · The path to the directory is not valid · An IO error occurs · There was
Recommended Action: 1. This error can be encountered during a backup or restore. Status Code 6 ==================== the backup failed to back up the requested files Errors caused the user backup to fail.
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. 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 Recommended Action: Change the wildcards in the file list to specify fewer files. Netbackup 7.7 Status Codes If nbjm received a negative error number, status 114 is issued.
Because system requirements vary, we can make no absolute recommendations, other than to use values great enough to provide resources to all applications. Veritas Netbackup Error Codes List Do a better job of ... Status Code 93 ==================== media manager found wrong tape in drive When you load a volume for a backup or restore, the tape manager (bptm) found a volume that loaded without o On NetWare target and OS/2 clients add a SERVER entry in the bp.ini file.
CALL US: 1 (866) 837-4827 Solutions Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government Products Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z Services Education Services Business Critical Important Error Codes In Veritas Netbackup If necessary, update the server list. The accept system or winsock call timed out after 60 seconds. Status Code 87 ==================== media close error The system's device driver returned an I/O error while NetBackup closed a tape or optical disk.
You could also try -- regardless of whether the system is physical or virtual -- a simple reboot. Status Code 146 ==================== cannot get a bound socket The service or daemon did not bind to its socket. Netbackup Error Codes And Solutions Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Netbackup Error Codes And Resolution This error indicates a problem on the master server.
The default for the CLIENT_READ_TIMEOUT and CLIENT_CONNECT_TIMEOUT is 300 seconds if unspecified. http://cpresourcesllc.com/error-code/status-error-code-1-winscp.php The only way to correct this particular condition is to figure out what the error means. 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). Recommended Action: Try to ping the client from the server. Symantec Netbackup Status Codes
You should begin the troubleshooting process by checking the logs for any further explanation of why the restore failed. TechStorey 2,089 views 7:25 NETBACKUP 7.7.3 - Duration: 17:01. Status Code 155 ==================== disk is full The write to the catalog file failed because the disk that contains the catalog database is full. this contact form The symptoms of the problem vary.
If the client software is earlier than 3.0, verify that the client is in a Standard type class. Netbackup Error Code 1 Status Code 210 ==================== error receiving information on message queue When a NetBackup process attempts to receive a message from a NetBackup daemon using bprd on an internal message queue construct, 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
Retry the operation and check the resulting activity logs. Status Code 162 ==================== incorrect server platform for license The platform identifier in the license key does not match the platform type on which the key was installed. Status Code 9 ==================== an extension package is needed, but was not installed A NetBackup extension product is required to perform the requested operation. Netbackup Status Code 6 o Verify that the Windows NT TCP/IP service specifies the domain server that resolves names for the subnet that contains the NetBackup servers.
Status Code 261 ==================== vault internal error 261 This error code should not occur. To verify which files were backed up, use the NetBackup client-user interface in restore mode and browse the files in the archive. Verify that there is space in the file system that contains the NetBackup databases. 3. navigate here On UNIX, verify that the /etc/services file (and NIS services if NIS is used) has entries for the NetBackup services: bpcd, bpdbm, and bprd.
You may be able to free up some memory by terminating such processes.