Spreadsheet: 198187d1354697313-how-to-do-a-search-in-a-few-colums-sumproduct_solution
Sheet: error_code

1 | The requested operation was partially successful | A problem was detected that may require corrective action during the requested operation. | Do manual backup
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. | Do manual backup
6 | The backup failed to back up the requested files | Errors caused the user backup to fail. | Do manual backup
13 | File read failed | A read of a file or socket failed. | Do manual backup
23 | Socket read failed | A read operation from a socket failed. | Do manual backup
24 | Socket write failed | A write operation to a socket failed. | Do manual backup
25 | Cannot connect on socket | A process that timed out while it connects to another process for a particular operation. 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. (On Windows, these daemons are the NetBackup Request Manager and NetBackup database manager services.) | Do manual backup
28 | Failed trying to fork a process | A fork of a child process failed (on UNIX and Linux) or a CreateProcess failed (on Windows). | Do manual backup
40 | Network connection broken | The connection between the client and the server was broken.  This status code can also appear if the connection is broken between the master and the media server during a backup. | Do manual backup
48 | Client hostname could not be found | The system function gethostbyname() failed to find the client’s host name. | Do manual backup
50 | Client process aborted | The client backup terminated abnormally.  For example, this error occurs if a NetBackup master or media server is shut down or rebooted when a backup or restore is in progress. | Do manual backup
58 | Can't connect to client | The server was unable to connect to the client. | Do manual backup
59 | Access to the client was not allowed | The master or the media server tries to access the client, but the client does not recognize the server as a valid server | Do manual backup
71 | None of the files in the file list exist | The files in the file list did not match any of the files on the client.  This error can occur with only one file in the file list and the file cannot be backed  up due to an I/O error. | Do manual backup
89 | Problems encountered during setup of shared memory | The NetBackup processes use shared memory for some operations.  This status is returned when an error is encountered in the initialization of the shared memory by the operating system’s APIs. | Do manual backup
96 | Unable to allocate new media for backup, storage unit has none available | The NetBackup resource broker (nbrb) did not allocate a new volume for backups. This error indicates that the storage unit has no more volumes available in the volume pool for this backup. Note that NetBackup does not change storage units during the backup. | Waiting for new [NAME] - or - added tapes
129 | Disk storage unit is full | As NetBackup writes to the file system for the disk storage unit, runs out of space. 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. | Do manual backup
150 | Termination requested by administrator | The process terminates (or has terminated) as a direct result of a request from an authorized user or process. | Do manual backup
155 | Disk is full | The write to the catalog file failed because the disk that contains the catalog database is full. | Do manual backup
 | Snapshot error encountered | A snapshot-backup related error regarding Windows Open File Backup or Snapshot Client. | Do manual backup
191 | No images were successfully processed | Averify, duplicate, duplication to remote master, automatic import, or import was tried and failed for all selected images. | Do manual backup
196 | Client backup was not attempted because backup window closed | [NAME] or an archive operation that the backup scheduler queued was not tried because the backup window was no longer open. | Do manual backup
229 | Events out of sequence - image inconsistency | A request was made that would cause the image catalog to become inconsistent if satisfied | Do manual backup
233 | Premature eof encountered | This status code is an intermediate one that usually precedes another status code and is associated with a problem in network communication. | Do manual backup
811 | Failed to communicate with resource requester | Job manager (nbjm) tries to notify a process (usually bptm) of the status of a resource it requested. That notification fails because of a communication problem.C30