Reinstall the client if these executables are not the same size as on other Windows NT clients or are not at the same release level or do not have the same Status Code: 41 Top Message: network connection timed out Explanation: The server did not receive any information from the client for too long a period of time. On a UNIX client, use the ps command to check for a client process that is using too much CPU time. 4. Then retry the operation and check the resulting activity logs. 2. weblink
Check the Problems report for clues. This error should not occur through normal use of NetBackup. Then, retry the operation and check the resulting activity log. This situation arises when the following occurs: * The most recent backup image for the client is a synthetic full or cumulative backup * The TIR information from one or more
This problem can occur during a backup or a restore. If the server is a valid slave server, verify that the storage unit for the slave server is defined. 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. Important Error Codes In Veritas Netbackup Status Code 67 ==================== client backup failed to read the file list The client did not read the list of files to back up.
Status Code 190 ==================== found no images or media matching the selection criteria A verify, duplicate, or import was attempted and no images that matched the search criteria were found in Veritas Netbackup Error Codes List If necessary add it as follows: o On Windows NT, 98, and 95 clients, add the server on the Servers tab in the NetBackup Configuration dialog box. If you still have problems, talk to your network administrator. https://www.veritas.com/support/en_US/article.DOC6471 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
Status Code: 39 Top Message: client name mismatch Explanation: The name that the client used in a request to the NetBackup server did not match the client name configured in the Netbackup Error Code 1 This error is usually a result of the use of software from different versions. See the NetBackup guide that came with the database extension for information on the scripts and troubleshooting logs. Status Code 170 ==================== third party copy backup failure Usually indicates a problem with the 3pc.
Recommended Action: First, verify that the server did not crash. Discover More The progress log also usually names the script. Netbackup Error Codes Pdf If there are media servers involved, create a bpbrm debug log directory on them. 4 Retry the operation and check the resulting debug logs. Netbackup Error Codes And Resolution For detailed troubleshooting information, create an activity log for the process that you suspect of returning this status code.
This error is usually a result of the use of software from different version levels. http://nodatasource.com/error-code/msi-error-codes.html Status Code: 9 Message: an extension package is needed but was not installed Explanation: A NetBackup extension product is required in order to perform the requested operation. To increase the logging level, set the loglevel parameter in the mac.conf file to a higher value. 1. Correct problems and retry the archive. Netbackup 7.7 Status Codes
Status Code: 19 Top Message: getservbyname failed Explanation: A call to getservbyname() failed. Status Code 51 ==================== timed out waiting for database information The catalog process did not respond within five minutes. Increase the logging level for the diagnostic and debug logs for nbpem, nbjm, and nbrb. http://nodatasource.com/error-code/veritas-netbackup-error-codes-list.html Verify that there is space in the file system that contains the NetBackup databases. 3.
Only one session is allowed for a vault at any given time. Netbackup Important Error Codes To increase the amount of information that appears in the logs, see the logging topics in Chapter 3, "Using the Logs and Reports." 2. Status Code 231 ==================== schedule windows overlap The specified start and the duration times for one day of the schedule overlap with another day of the schedule.
Status Code 14 ==================== file write failed A write to a file or socket failed. 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. Recommended Action: Verify that the files exist and you have read access to them. · On UNIX clients, check to see if the files or directories would be excluded because of Netbackup Status Code 58 This error is usually caused when another process acquired the port before the daemon or service started.
This error is probably an intermittent error that is based on the availability of resources on the system. This has been seen to occur during backups when directories have thousands of unmodified files; it has also been seen when backing up file systems or directories that reside on optical For a Macintosh or NetWare target client, verify that the server is not trying to connect when a backup or restore is already in progress on the client. this content Recommended Action: 1.
Status Code 76 ==================== client timed out reading file A fifo was specified in the file list and no data was produced on the fifo within the allotted time. Status Code: 45 Top Message: request attempted on a non reserved port Explanation: An attempt was made to access a client from a nonreserved port. If there are slave servers involved, create a bpbrm activity log directory on them. 4. On Windows, these daemons are the NetBackup Request Manager and NetBackup Database Manager services.
Until more file system space is available, images of similar size or larger may fail with this error when written to this disk storage unit.In a scheduled backup job that writes That storage unit may have more unused capacity now than it did when the job failed. Status Code 124 ==================== NB database backup failed, a path was not found or is inaccessible One or more of the specified paths in the catalog backup configuration were not backed Errors associated with NetBackup status codes can often be traced to permissions issues, resource allocation issues, or other simple configuration or logistical issues.
The SYSTEM account cannot access network drives. On Windows NT, these daemons are the NetBackup Request Manager and NetBackup Database Manager services. If you change the server list on a UNIX master server, you must stop and then restart the NetBackup Request daemon (bprd) and NetBackup Database Manager daemon (bpdbm) for the changes If this is not possible, check for loose connections or other network problems. 2.
Status Code â€“ 84 Reason: Reduce the backup failure due to I/O error. This error can be due to the following: mismatched versions of the product, corrupted network communication, or to a non-NetBackup process sending data across the port for the daemon or service. It is also a good idea to check the resource you are backing up to ensure the NetBackup client has permission to write data to the location where the data is Status Code 263 ==================== session id assignment failed The unique identifier to be assigned to the Vault session is corrupt.
On UNIX, check the system log. Check for a semaphore problem. Recommended Action: Check the NetBackup All Log Entries report for clues on where and why the failure occurred. Verify that the server list specifies the correct master server.
On Windows NT clients, verify that the NetBackup Client service is running. 3. Enable detailed activity logging on the client: o Create bpcd and bpbkar (UNIX or Windows NT only) activity log directories.