Netbackup Veritas Error Codes
The installation will complete successfully under a non-administrator account but the NetBackup Client service is not added to Windows NT and the NetBackup server cannot access the client. Kies je taal. Recommended Action: 1. Status Code – 84 Reason: Reduce the backup failure due to I/O error. have a peek here
On Sun Solaris, verify that all operating system patches are installed (see the Operating Notes section of the NetBackup Release Notes - UNIX). 4. It is possible that updates have been made to the original version after this document was translated and published. Fill in your details below or click an icon to log in: Email (required) (Address never made public) Name (required) Website You are commenting using your WordPress.com account. (LogOut/Change) You are Certain operations are not allowed during an online catalog backup. (These include catalog archiving, catalog compression, and expiration of the last copy of an image.) Status Code 126 ==================== NB database internet
Netbackup Error Codes Pdf
To display this dialog box, start the Backup, Archive, and Restore interface on the server and click Configure on the Actions menu (also see "Using the Configure - NetBackup Window" on Status code 2 Reason: None of the file backed up Action taken: no files in target path 2. For example, if a slave server does not have a server list entry for the master, it does not accept connections from the master. If one is not available, NetBackup re-queues the job with a status of 134 and retries it later.
- To display this dialog box, start the Backup, Archive, and Restore interface and click Configure on the Actions menu (also see "Using the Configure - NetBackup Window" on page 57).
- Please visit the Veritas support web site, and refer to Technote number 262225 for further information. 10:09:56.571  <16> bpbkar Exit: ERR - bpbkar FATAL exit status = 142: file does
- On PC clients, increase the debug or log level as explained in the activity log topics in Chapter 3, "Using the Logs and Reports." 2. 2.
- Recommended Action: First, verify that the server did not crash.
- Add more swap space or physical memory.
- Status Code: 61 Top Message: wbak was killed Explanation: The wbak process on the Apollo was killed.
- It can be resumed from the last checkpoint by the administrator.
- Status Code 215 ==================== failed reading global config database information During the periodic checking of the NetBackup configuration, nbproxy was unable to read the global configuration parameters.
It should not occur for standard file system backups.Open a NetBackup support case (recommended in Symantec document 276903.pdf) if you encounter this error for the following: a UNIX or Windows file Log in om dit toe te voegen aan de afspeellijst 'Later bekijken' Toevoegen aan Afspeellijsten laden... If rbak does not exit with a status message, NetBackup cannot determine whether the restore worked or not. Important Error Codes In Veritas Netbackup This error occurs when there is insufficient system memory available.
Correct problems and retry the backup. 2. Status Code 236 ==================== the specified client does not exist in an active policy within the configuration database A client name was not specified or the specified client does not exist. SearchDisasterRecovery Plan your ransomware recovery strategy with cloud DR Ensure protection against ransomware with snapshots and the cloud. https://www.veritas.com/support/en_US/article.000100616 Correct problems that you find and retry the restore.
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, Veritas Netbackup Error Codes Pdf The values on the Network tab are written to the services file when the NetBackup Client service starts. Create a bpbkar activity log directory. Also, verify that the server or Windows NT administration client has a server list entry on the master server.
Veritas Netbackup Error Codes List
Check the permissions on the command to be executed. 3. check this link right here now Ensure that the NetBackup Client Service Port Number and NetBackup Request Service Port Number on the Network tab in the NetBackup Configuration dialog box match the settings in the services file. Netbackup Error Codes Pdf 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. Netbackup Error Codes And Resolution Status Code 160 ==================== authentication failed NetBackup encounters a problem when two systems attempt to authenticate one another.
Get Symantec's explanation of how to fix this issue. navigate here This problem can occur during a backup or restore in either a single or a multiple server configuration. But do you remember the whole Netbackup status code and how to troubleshoot? c. Netbackup 7.7 Status Codes
Check the NetBackup All Log Entries report for clues on where and why the failure occurred. 2. This error can also occur if the volume is a cleaning tape but was not specified as a cleaning tape. Recommended Action: Check the NetBackup Problems report for clues on why the failure occurred. http://windowsazure4j.org/error-codes/netbackup-error-codes.html Recommended Action: 1.
Some possible solutions are: o Adjust the backup schedules. Netbackup Important Error Codes If the above processes are running, examine the All Log Entries report for the time of the failure to determine where the failure occurred. 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
This error can also occur if the volume happens to be a cleaning tape but was not specified as a cleaning tape.
This error occurs when the Vault job is unable to get the local host name. Then, create an activity log directory for bpdbm, retry the operation, and check the resulting activity log. Status Code 276 ==================== invalid session id This error should not occur. Netbackup Status Code 58 For a regular backup, the volume is automatically set to the SUSPENDED state and not used for further backups.
On Windows NT, verify that the recommended service packs are installed. Status Code 146 ==================== cannot get a bound socket The service or daemon did not bind to its socket. On Windows NT, verify that the recommended service packs are installed. this contact form Status Code 140 ==================== user id was not superuser A user or process that did not have root privileges (on UNIX) or administrator privileges (on Windows) started the process.
Status Code 198 ==================== no active policies contain schedules of the requested type for this client A user backup or archive was requested, and this client is not in a policy 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. Verify that the tape is not a cleaning tape that is configured as a regular volume. 4. Status Code 114 ==================== unimplemented error code This error should not occur.
Recommended Action: Check the NetBackup Problems report for clues on where and why the problem occurred. Verify that the bpcd and bprd port numbers in the %SystemRoot%\system32\drivers\etc\services file on the server matches the setting on the client. Status Code 282 ==================== cannot connect to nbvault server The vault job cannot connect to the NetBackup Vault Manager service (nbvault on UNIX, nbvault.exe on Windows). Sorry, we couldn't post your feedback right now, please try again later.
Either no Vault jobs were run for this profile or the corresponding sidxxx session id directory (or directories) were removed from the following directory: UNIX: /usr/openv/netbackup/vault/sessions/vault_name Windows: install_path\NetBackup\vault\sessions\vault_name Status Code 270 Meer weergeven Laden... Status Code 94 ==================== cannot position to correct image The tape manager (bptm) searched for a backup image to restore but did not find the correct backup ID at the expected Status Code: 24 Top Message: socket write failed Explanation: A write operation to a socket failed.
If so, kill it and try again. Keep in mind that if the VM is running a 32-bit operating system it will never be able to use more than 4 GB of RAM. On UNIX systems, this error may be due to a lack of system resources for System V inter-process communication. c.
Check the script for problems. VxSS authentication is used with the NetBackup Access Control feature (NBAC). Or one or more of the images to be synthesized was encrypted. If the error logs show that it is associated with a subsequent error, it usually indicates a communication problem.
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.