0 the requested operation was successfully completed There were no problems detected with the requested operation. 1 the requested operation was partially successful A problem that may require corrective action was detected during the requested operation. 2 none of the requested files were backed up A backup or archive could not back up any of the files in the file list. 3 valid archive image produced, but no files deleted due to non-fatal problems The backup portion of the archive command reported problems so the files were not deleted. 4 archive file removal failed The backup portion of the archive completed was successful but the delete failed. 5 the restore failed to recover the requested files There were errors that caused the restore to fail. 6 the backup failed to back up the requested files Errors caused the user backup to fail. 7 the archive failed to back up the requested files Errors caused the user archive to fail. 8 unable to determine the status of rbak On DomainOS clients, rbak is used to do restores. If rbak does not exit with a status message, NetBackup cannot determine whether the restore worked or not. 9 an extension package is needed but was not installed A NetBackup extension product is required in order to perform the requested operation. 10 allocation failed Allocation of system memory failed because there is insufficient system memory available. This could be caused by the system being overloaded with too many processes and not enough physical or virtual memory. 11 system call failed A system call failed. This status code is used for a generic system call failure that does not have its own status code. 12 file open failed An open of a file failed. 13 file read failed A read of a file or socket failed. Possible causes include: * I/O error reading from the file system. * Read of an incomplete or corrupt file. * Socket read failing. A socket read failure can be caused by a network problem or a problem with the process that is writing to the socket. 14 file write failed A write to a file or socket failed. Possible causes include: * I/O error writing to the file system. * Write to a socket failed. This can be caused by a network problem or a problem with the process reading from the socket. * Writing to a full disk partition. * The bpfsmap temporary directory (usually /tmp) became full (on Auspex FastBackup jobs). 15 file close failed A close of a file or socket failed. 16 unimplemented feature The specified operation is unimplemented. This error should not occur through normal use of NetBackup. 17 Error: Can't find Troubleshooting Guide, or status code not available. 18 pipe close failed Close of a pipe failed, when one process tries to start a child process. 19 getservbyname failed A call to getservbyname() failed. The getservbyname() function uses the name of the service to find a service entry in the services file (or NIS services map on UNIX if it is configured). 20 invalid command parameter One or more command parameters were not valid. This error can occur when a master and its media servers or a master server and a client have different levels of NetBackup installed. For example, if a NetBackup master server has NetBackup 3.2 and the media server has NetBackup 3.0.This error can also occur if the wrong parameters are used when executing a command line. 21 socket open failed A socket open failed. 22 socket close failed A socket could not be closed. 23 socket read failed A read operation from a socket failed. 24 socket write failed A write operation to a socket failed. 25 cannot connect on socket A process timed out while connecting to another process for a particular operation. This problem can occur 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 NT/2000, these daemons are the NetBackup Request Manager and NetBackup Database Manager services). It can also occur if the network or server is heavily loaded and has slow response time. 26 client/server handshaking failed A process on the server encountered an error when communicating with the client. This error indicates that the client and server were able to initiate communications, but encountered difficulties in completing them. This problem can occur during a backup or a restore. 27 child process killed by signal A child of the process reporting this error was killed. This can occur because the backup job was terminated or the child process was terminated by another error. This problem can also occur if a NetBackup process was terminated through Task Manager or another utility. 28 failed trying to fork a process A fork of a child process failed (on UNIX) or a CreateProcess failed (on Windows NT/2000). This may be due to: * An overloaded system * Insufficient swap space or physical memory * Too many processes running on the system 29 failed trying to exec a command A command could not be executed. This can occur because the permissions of the command do not allow it to be executed, or there is lack of system resources such as memory and swap space. 30 could not get passwd information Could not get the passwd entry for a user. 31 could not set user id for process Could not set the user ID of a process to that of the requesting user. NetBackup executes client processes as the requesting user. 32 could not set group id for process Could not set the group ID of a process to the requesting user group. NetBackup executes client processes with the group ID of the requesting user. 33 failed while trying to send mail An E-mail notification of backup, archive, or restore results has failed. The E-mail could not be sent to the administrator's address as specified by the E-mail global attribute, or in the case of a UNIX client, an E-mail address specified with USEMAIL in the client's bp.conf file. 34 failed waiting for child process The bpsched process encountered a failure while waiting for a child process to complete. 35 cannot make required directory Could not create a required directory. 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 no space available on the device containing the directory 36 failed trying to allocate memory Allocation of system memory failed. This error occurs when there is insufficient system memory available. This could be caused by the system being overloaded with too many processes and there is not enough physical and virtual memory. 37 operation requested by an invalid server A request was made to the NetBackup request daemon (bprd) or NetBackup database manager daemon (bpdbm) by an invalid media server or Windows NT/2000 administration client. On Windows NT/2000, these daemons are the NetBackup Request Manager and NetBackup Database Manager services. 38 could not get group information Could not get the group entry describing a UNIX user group. 39 client name mismatch The name that the client used in a request to the NetBackup server did not match the client name configured in the class on the server. 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 media server during a backup. 41 network connection timed out The server did not receive any information from the client for too long a period of time. 42 network read failed An attempt to read data from a socket failed. 43 unexpected message received The client and server handshaking was not correct. 44 network write failed An attempt to write data to a socket failed. 45 request attempted on a non reserved port An attempt was made to access a client from a nonreserved port. 46 server not allowed access The server is trying to access the client but the server is not listed on the client as a valid server. 47 host is unreachable An attempt to connect to another machine failed. 48 client hostname could not be found The system function gethostbyname() failed to find the client's host name. 49 client did not start The client failed to start up correctly. 50 client process aborted The client backup aborted. One instance when this code appears is if a NetBackup master or media server is shut down or rebooted when a backup or restore is in process. 51 timed out waiting for database information The catalog process did not respond within five minutes. 52 timed out waiting for media manager to mount volume The requested volume was not mounted before the timeout expired. This error can also occur if the volume happens to be a cleaning tape but was not specified as a cleaning tape.Another possible cause: if the last available drive has a mount request for a non-backup (such as a restore), then a backup requiring the same drive is initiated before the mount completes. This is due to the drive not being reported as busy until the mount completes. 53 backup restore manager failed to read the file list The backup and restore manager (bpbrm) could not read the list of files to back up or restore. 54 timed out connecting to client The server could not complete the connection to the client. The accept system call timed out after 60 seconds. 55 permission denied by client during rcmd The UNIX client does not have the server's name in its /.rhosts file. 56 client's network is unreachable The server got ENETUNREACH when trying to connect to the client. 57 client connection refused The client refused a connection on the port number for bpcd. This can occur because there is no process listening on the bpcd port or there are more connections to the bpcd port than the network subsystem can handle with the listen() call. 58 can't connect to client The server was unable to connect to the client. 59 access to the client was not allowed The master or media server is trying to access the client, but the server is not recognized by the client as a valid server. 60 client cannot read the mount table The backup process on the client could not read the list of mounted file systems. 61 wbak was killed The wbak process on the Apollo was killed. 62 wbak exited abnormally The wbak process on the Apollo exited abnormally. 63 process was killed by a signal A kill signal was sent to the client process. 64 timed out waiting for the client backup to start The client did not send a ready message to the server within the allotted time. 65 client timed out waiting for the continue message from the media manager. The tape manager, bptm reported that the media did not load and position within the allotted time. 66 client backup failed to receive the CONTINUE BACKUP message The client bpbkar process did not receive the message from the server that indicates that the server is ready to continue. 67 client backup failed to read the file list The client could not read the list of files to back up. 68 client timed out waiting for the file list The client did not receive the list of files to back up within the allotted time. This list comes from the server. 69 invalid file list specification The file list received from the server had invalid entries. 70 an entry in the file list expanded to too many characters The wildcards used in one of the file list entries caused too many files to be specified. 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 when there is only one file in the file list and the file cannot be backed up due to an I/O error. 72 the client type is incorrect in the configuration database The class type attribute in the class configuration indicates that the client is one type, but the installed software is for another type. 73 bpstart_notify failed The bpstart_notify script returned a nonzero exit code. 74 client timed out waiting for bpstart_notify to complete The bpstart_notify script on the client took too long. 75 client timed out waiting for bpend_notify to complete The bpend_notify script on the client took too long. 76 Error: Can't find Troubleshooting Guide, or status code not available. 77 execution of the specified system command returned a nonzero status An immediate command returned a nonzero status. 78 afs/dfs command failed Indicates an AFS vos command failure. 79 Error: Can't find Troubleshooting Guide, or status code not available. 80 Media Manager device daemon (ltid) is not active If the server is UNIX, the Media Manager device daemon, ltid, is not running. If the server is Windows NT/2000, the NetBackup Device Manager service is not running. 81 Media Manager volume daemon (vmd) is not active The tape manager (bptm) could not communicate with the NetBackup Volume Manager service (Windows NT/2000) or the Media Manager volume daemon (UNIX). This communication is required for most operations. 82 media manager killed by signal The tape manager (bptm) or disk manager (bpdm) was terminated by another process or a user. 83 media open error The tape manager (bptm) or disk manager (bpdm) could not open the device or file that the backup or restore must use. 84 media write error The system's device driver returned an I/O error while NetBackup was writing to removable media or a disk file. 85 media read error The system device driver returned an I/O error while NetBackup was reading from tape, optical disk, or a disk file. 86 media position error The system's device driver returned an I/O error while NetBackup was positioning media (tape or optical disk). 87 media close error The system's device driver returned an I/O error while NetBackup was closing a tape or optical disk. 88 Auspex SP/Backup failure NetBackup detected a problem when backing up an Auspex FastBackup client. 89 Error: Can't find Troubleshooting Guide, or status code not available. 90 media manager received no data for backup image The tape manager (bptm) or disk manager (bpdm) received no data when performing a backup or archive. This can occur for incremental backups where no data was backed up because no files have changed. 91 fatal NB media database error The tape manager (bptm) received an error while reading or updating its media catalog. 92 media manager detected image that was not in tar format When performing a restore, the tape manager (bptm) or disk manager (bpdm) could not find a tar header at the offset it expected. 93 media manager found wrong tape in drive When loading a volume for a backup or restore, the tape manager (bptm) found a volume loaded that did not have the expected tape header. This can indicate that volumes in a robot are not in the slots indicated in the Media Manager volume configuration. 94 cannot position to correct image When searching for a backup image to restore, the tape manager (bptm) did not find the correct backup ID at the expected position on the volume. This can indicate a drive hardware problem. 95 requested media id not found in NB media database and/or MM volume database An operation was requested on a media ID for which NetBackup does not have a record. An example of this is using bpmedia to suspend or freeze a media ID that does not exist. 96 unable to allocate new media for backup, storage unit has none available The tape manager (bptm) could not allocate a new volume for backups. This indicates that the storage unit has no more volumes available in the volume pool for this backup. 97 requested media id is in use, cannot process request An operation was requested on a media ID that is in use. An example of this is attempting to suspend or freeze a volume while it is being used for a backup or restore. 98 error requesting media (tpreq) The tape manager and optical manager (bptm) received an error when requesting a media mount from the NetBackup Device Manager service on Windows NT/2000 or the Media Manager device daemon (ltid) on UNIX. 99 NDMP backup failure None of the paths in your NDMP class file list was backed up successfully. 100 system error occurred while processing user command A system call failed in bparchive, bpbackup, bplist, or bprestore. 101 failed opening mail pipe The process that attempts to send mail could not open the pipe to the server. 102 failed closing mail pipe The process that sends mail could not close the pipe to the server. 103 Error: Can't find Troubleshooting Guide, or status code not available. 104 Error: Can't find Troubleshooting Guide, or status code not available. 105 file pathname exceeds the maximum length allowed The path name built by using the current working directory exceeds the maximum path length allowed by the system. 106 invalid file pathname found, cannot process request One of the file paths to be backed up or archived is not valid. 107 Error: Can't find Troubleshooting Guide, or status code not available. 108 Error: Can't find Troubleshooting Guide, or status code not available. 109 Error: Can't find Troubleshooting Guide, or status code not available. 110 Cannot find the NetBackup configuration information On Windows NT/2000, NetBackup could not read the registry entries that were created during installation. On UNIX, the /usr/openv/netbackup/bp.conf file does not exist. 111 No entry was found in the server list On UNIX, the SERVER = server_name line is missing in the bp.conf file. On Windows NT/2000, the server list contains no entries. 112 no files specified in the file list A restore was requested with no files in the file list. 113 Error: Can't find Troubleshooting Guide, or status code not available. 114 Error: Can't find Troubleshooting Guide, or status code not available. 115 Error: Can't find Troubleshooting Guide, or status code not available. 116 Error: Can't find Troubleshooting Guide, or status code not available. 117 Error: Can't find Troubleshooting Guide, or status code not available. 118 Error: Can't find Troubleshooting Guide, or status code not available. 119 Error: Can't find Troubleshooting Guide, or status code not available. 120 cannot find configuration database record for requested NB database backup The program that backs up the NetBackup internal catalogs could not find the attributes that indicate which media IDs to use or paths to back up. This error should not occur under normal circumstances. 121 no media is defined for the requested NB database backup NetBackup attempted to back up its internal catalogs and there were no media IDs defined in the catalog backup configuration. 122 specified device path does not exist The NetBackup internal catalogs were backed up by using the bpbackupdb command line and specifying a raw device file that does not exist. 123 specified disk path is not a directory NetBackup attempted to back up its internal catalogs and the backup attributes were set to dump to a disk. However, the disk file path already exists and is not a directory. 124 NB database backup failed, a path was not found or is inaccessible One or more of the paths specified in the catalog backup configuration could not be backed up. 125 another NB database backup is already in progress Only one NetBackup catalog backup may be active at any given time. 126 NB database backup header is too large, too many paths specified Too many paths were specified in the NetBackup catalog backup configuration to fit in a fixed-size media header. This error should not occur under normal circumstances. 127 specified media or path does not have a valid NB database backup header The bprecover command was issued and the media ID specified does not have valid catalog backup data. 128 Error: Can't find Troubleshooting Guide, or status code not available. 129 Error: Can't find Troubleshooting Guide, or status code not available. 130 system error occurred An error occurred that prevents the product from operating in a consistent fashion. This error is usually related to a system call. 131 client is not validated to use the server The client name, as determined from the connection to the server, did not match any client name in the NetBackup configuration and there was no altnames configuration for this client on the master server. A client and server that have multiple network connections can encounter this problem if the name by which the client is configured is not the one by which its routing tables direct connections to the server. 132 Error: Can't find Troubleshooting Guide, or status code not available. 133 invalid request One of two explanations exist. * A request was made that is unrecognized. This usually results from different versions of NetBackup software being used together. * If a client receives this error in response to a list or restore request, it means that the DISALLOW_CLIENT_LIST_RESTORE or DISALLOW_CLIENT_RESTORE option exists in the bp.conf file on a UNIX NetBackup server or registry on a Windows NT/2000 NetBackup server. These options deny list and restore requests from all NetBackup clients. 134 Error: Can't find Troubleshooting Guide, or status code not available. 135 client is not validated to perform the requested operation This is usually caused by a request to restore files to a client other than the one that made the request and the request did not come from the root user (administrator on Windows NT/2000) on a NetBackup server. 136 Error: Can't find Troubleshooting Guide, or status code not available. 137 Error: Can't find Troubleshooting Guide, or status code not available. 138 Error: Can't find Troubleshooting Guide, or status code not available. 139 Error: Can't find Troubleshooting Guide, or status code not available. 140 user id was not superuser The process was started by a user or process that did not have root privileges (on UNIX) or administrator privileges (on Windows NT/2000). 141 file path specified is not absolute The file specification must be an absolute path. 142 file does not exist This code is reserved for future use. 143 invalid command protocol An ill-formed request was made to the NetBackup request daemon (UNIX) or Request Manager service (Windows NT/2000). This can be due to mismatched versions of the product, corrupted network communication, or to a non-NetBackup process sending data across the port for the daemon or service. 144 invalid command usage This status code is due to a NetBackup process being started with improper options or an incompatibility in the product. 145 daemon is already running There is another copy of the process executing. 146 cannot get a bound socket The daemon (service on Windows NT/2000) could not bind to its socket. A system call failed when the daemon (UNIX) or service (Windows NT/2000) attempted to bind to its configured port number. This is usually caused by another process having acquired the port before the daemon or service started. 147 required or specified copy was not found The requested copy number of a backup or archive image cannot be found. 148 daemon fork failed A NetBackup service could not create a child process due to an error received from the system. This is probably an intermittent error based on the availability of resources on the system. 149 Error: Can't find Troubleshooting Guide, or status code not available. 150 termination requested by administrator The process is terminating (or has terminated) as a direct result of a request from an authorized user or process. 151 Backup Exec operation failed The Global Data Manager console has reported that a Backup Exec job (backup, archive, or restore) did not complete normally. 152 required value not set An incomplete request was made to the bpdbm process (NetBackup Database Manager service on Windows NT/2000). This usually occurs because different versions of software are being used together. 153 server is not the master server This status code is reserved for future use. 154 storage unit characteristics mismatched to request A backup was attempted and the storage unit selected for use had characteristics that were not compatible with the backup type. 155 Error: Can't find Troubleshooting Guide, or status code not available. 156 Error: Can't find Troubleshooting Guide, or status code not available. 157 Error: Can't find Troubleshooting Guide, or status code not available. 158 failed accessing daemon lock file The process could not lock its lock file because an error was received from a system call. This lock file synchronizes process activities (for example, preventing more than one daemon from executing at a time). 159 licensed use has been exceeded A configuration limit has been exceeded. An example is number of drives allowed per server. 160 authentication failed A problem was encountered when two systems were attempting to authenticate one another. 161 Evaluation software has expired. See www.veritas.com for ordering information. The time allowed for the NetBackup evaluation software has ended. 162 Error: Can't find Troubleshooting Guide, or status code not available. 163 Error: Can't find Troubleshooting Guide, or status code not available. 164 unable to mount media because it is in a DOWN drive or misplaced A restore was attempted and the volume required for the restore was in a DOWN drive in a robot. Or, the slot that should contain the volume is empty. 165 NB image database contains no image fragments for requested backup id/copy number A restore was attempted and NetBackup has no record of fragments associated with the backup ID that has the files. 166 backups are not allowed to span media An end of media (EOM) was encountered while the backup image was being written. The backup was terminated because the NetBackup DISALLOW_BACKUPS_SPANNING_MEDIA option was present in bp.conf on UNIX or the registry on Windows NT/2000. The backup will be retried automatically with a different volume if this is allowed by the backup tries attribute in the NetBackup global attribute configuration. 167 cannot find requested volume pool in Media Manager volume database A backup to a nonrobotic drive was attempted and the tape manager (bptm) could not find or add the specified volume pool. 168 cannot overwrite media, data on it is protected A catalog backup was attempted to a volume that could not be overwritten because it contains data that NetBackup, by default, does not overwrite (tar, cpio, ANSI, and so on). 169 media id is either expired or will exceed maximum mounts A backup or catalog backup was attempted and the volume selected for use has reached its maximum number of mounts as specified in the Media Manager volume configuration. For a regular backup, the volume is automatically set to the SUSPENDED state and not used for further backups. For a NetBackup catalog backup, the operation terminates abnormally. 170 Error: Can't find Troubleshooting Guide, or status code not available. 171 media id must be 6 or less characters An operation, such as using bpmedia to suspend or freeze a media ID, was attempted and the media ID specified was longer than six alpha-numeric characters. 172 cannot read media header, may not be NetBackup media or is corrupted When loading a volume for a backup or restore, the tape manager (bptm), did not find the expected tape header. This can mean that a volume in a robotic device is not in the slot number shown in the Media Manager volume configuration or that a read error (I/O error) occurred. 173 cannot read backup header, media may be corrupted When searching for a backup image to restore, the tape manager (bptm) could not find the correct backup ID at the position on the media where NetBackup expected it to be. This can indicate a drive hardware problem. 174 media manager system error occurred An abnormal condition occurred causing a tape manager (bptm) or disk manager (bpdm) failure. This should not occur under normal circumstances. Note: If this occurs on a Sequent platform and you are attempting to back up more than four gigabytes of data, save all your logs and call VERITAS technical support. For other platforms perform the recommended actions described below. 175 not all requested files were restored When restoring files from an image, the bptm or bpdm process detected a fatal error condition and terminated the restore before it completed. This should not occur under normal circumstances. 176 cannot perform specified media import operation The tape manager (bptm) detected an error condition when attempting to import a specific backup image. Possible reasons for this are: * Media ID is already active in the NetBackup media catalog on this server * Media ID is not in the Media Manager volume configuration * Fatal tape manager (bptm) error occurred * Total image was not obtained from Phase 1 of import 177 could not deassign media due to Media Manager error The tape manager (bptm) could not successfully deassign a media ID. 178 media id is not in NetBackup volume pool NetBackup attempted a backup of its catalogs and the media ID specified for the catalog backup was not in the NetBackup volume pool. Volumes for catalog backups must be in the NetBackup volume pool. 179 density is incorrect for the media id An operation such as "list contents" was attempted on an invalid media ID, such as a cleaning tape. Another possibility is that a media ID in the NetBackup catalog backup configuration does not match the media type entered in the Media Manager volume configuration. 180 tar was successful tar returned a successful exit status. 181 tar received an invalid argument One of the parameters passed to tar was not valid. 182 tar received an invalid file name tar cannot write to the file that is specified with the -f parameter. 183 tar received an invalid archive The data passed to tar was corrupt. 184 tar had an unexpected error A system error occurred in tar. 185 tar did not find all the files to be restored There were files in the tar file list that were not in the image. 186 tar received no data The media manager did not send data to tar. 187 Error: Can't find Troubleshooting Guide, or status code not available. 188 Error: Can't find Troubleshooting Guide, or status code not available. 189 the server is not allowed to write to the client's filesystems The client is not allowing writes from the server. 190 found no images or media matching the selection criteria A verify, duplicate, or import was attempted and no images matching the search criteria were found in the NetBackup catalog. 191 no images were successfully processed A verify, duplicate, or import was attempted and failed for all selected images. 192 Error: Can't find Troubleshooting Guide, or status code not available. 193 Error: Can't find Troubleshooting Guide, or status code not available. 194 the maximum number of jobs per client is set to 0 The NetBackup Maximum jobs per client global attribute is currently set to 0. Setting the value to 0 disables backups and archives. 195 client backup was not attempted A backup job was in the NetBackup scheduler's worklist but was not attempted. 196 client backup was not attempted because backup window closed A backup or archive operation that was queued by the backup scheduler was not attempted because the backup window was no longer open. 197 the specified schedule does not exist in the specified class A user backup or archive request has specified the exact class and schedule to use when performing a backup. The class exists but does not contain the schedule. * On Microsoft Windows and NetWare nontarget clients, you can specify a class or schedule on the Backups tab in the NetBackup Configuration dialog box. To display this dialog box, start the Backup, Archive, and Restore interface on the client and click Configure on the Actions menu. * On UNIX and Macintosh clients, you can specify a class or schedule by using the bp.conf options, BPBACKUP_CLASS or BPBACKUP_SCHED. * On NetWare target clients, you can specify a class or schedule in the bp.ini file. 198 no active classes contain schedules of the requested type for this client A user backup or archive has been requested, and this client is not in a class that has a user backup or archive schedule. 199 operation not allowed during this time period A user backup or archive has been requested and this client is not in a class that has a user backup or archive schedule with an open backup window. This error implies that there is an appropriate class and schedule combination for this client. 200 scheduler found no backups due to run When checking the class and schedule configuration, the NetBackup scheduler process (bpsched) did not find any clients to back up. This could be due to: * No backup time windows are open (applies only to full and incremental schedules). * Classes are set to inactive. * The clients were recently backed up and are not due for another backup (based on Frequency setting for the schedules). * Classes do not have any clients. 201 handshaking failed with server backup restore manager A process on the master server encountered an error when communicating with the media host (can be either the master or a media server). This error means that the master and media server processes were able to initiate communication, but encountered difficulties in completing them. This problem can occur during a backup, restore, or media list in a single or multiple server configuration. 202 timed out connecting to server backup restore manager A process on the master server timed out while trying to initiate communications with the media host (can be either the master or a media server). This problem can occur during a backup or restore in either a single or multiple server configuration. 203 server backup restore manager's network is unreachable A process on the master server could not connect to a particular host on the network when trying to initiate communication with the media host for a particular operation. This problem can occur during a backup or restore in either a single or multiple server configuration. 204 connection refused by server backup restore manager The media host refused a connection on the port number for bpcd. This error can be encountered during a backup or restore. 205 cannot connect to server backup restore manager A process on the master server could not connect to a process on a host on the network while trying to initiate communication with the server that has the storage unit for a particular operation. This problem can occur during a backup or restore in either a single or multiple server configuration. This can also occur when the scheduler process (bpsched) is building its list of available storage units to use during backups. 206 access to server backup restore manager denied The master server is trying to start a process on another server (or itself) and the master server does not appear in the Netbackup server list on that server. On a UNIX server, the master is the first SERVER entry in the bp.conf file. On a Windows NT/2000 server, the master is designated on the Servers tab in the Master Server Properties dialog. To access this dialog, see "Using the Configure - NetBackup Window" in the Troubleshooting Guide. 207 error obtaining date of last backup for client An error occurred when the backup scheduler (bpsched) tried to obtain the date of the last backup for a particular client, class, and schedule combination. 208 failed reading user directed file list An error occurred when the backup scheduler (bpsched) attempted to read the list of files requested for a user backup or archive. This error indicates either a client-server communication problem, or a system problem on the master server where the NetBackup scheduler process (bpsched) is running. 209 error creating or getting message queue An error occurred when the backup scheduler (bpsched) attempted to create an internal message queue construct for interprocess communication. This error indicates a problem on the master server and is most likely due to a lack of system resources for System V interprocess communication. 210 error receiving information on message queue An error occurred when one of the backup scheduler (bpsched) processes attempted to receive a message from another bpsched process on an internal message queue construct. This error indicates a problem on the master server and is likely due to problems with or a lack of system resources for System V interprocess communication. 211 scheduler child killed by signal A backup scheduler (bpsched) child process, which interacts with the backup restore manager (bpbrm) on the media host, was terminated. This can occur because of system administrator action. 212 error sending information on message queue The backup scheduler (bpsched) encountered an error when attempting to attach to an already existing internal message queue construct for interprocess communication. This error indicates a problem on the master server and is likely due to a lack of system resources for System V interprocess communication. 213 no storage units available for use The NetBackup scheduler process (bpsched) did not find any of its storage units available for use. Either all storage units are unavailable or all storage units are configured for "on demand only" and the class and schedule does not require a specific storage unit. 214 regular bpsched is already running The NetBackup scheduler (bpsched) performs periodic checking of the class and schedule configuration to determine if there are new backups due. Error 214 indicates that when a new instance of NetBackup starts, it finds that a scheduler process is already checking the class and schedule configuration. 215 failed reading global config database information During the periodic checking of the NetBackup configuration, the NetBackup scheduler process (bpsched) was unable to read the global configuration parameters. 216 failed reading retention database information During its periodic checking of the NetBackup configuration, the NetBackup scheduler process (bpsched) could not read the list of retention levels and values. 217 failed reading storage unit database information During its periodic checking of the NetBackup configuration, the NetBackup scheduler process (bpsched) could not read the storage unit configuration. 218 failed reading class database information During the periodic checking of the NetBackup configuration, the NetBackup scheduler process (bpsched) could not read the class (backup policy) configuration. 219 the required storage unit is unavailable The class or schedule for the backup requires a specific storage unit, which is currently unavailable. This error also occurs for other attempts to use the storage unit within the current backup session. 220 database system error The bpdbm process (NetBackup Database Manager service on Windows NT/2000) could not create a directory path for its configuration catalogs due to the failure of a system call. This is usually due to a permission problem or an "out of space" condition. 221 continue This status code is used in coordinating communication between various NetBackup processes and normally does not occur. If the logs show that it is associated with a subsequent error, it usually indicates a communication problem. In this case, concentrate your troubleshooting efforts on the subsequent error. 222 done This status code is used in coordinating communication between various NetBackup processes and is normally not seen. If the error logs show that it is associated with a subsequent error, it usually indicates a communication problem. In this case, concentrate your troubleshooting efforts on the subsequent error. 223 an invalid entry was encountered A request to the bpdbm process (NetBackup Database Manager service on Windows NT/2000) had invalid or conflicting information. This is usually a result of using software from different versions together, but can also be caused by incorrect parameters on a command. 224 there was a conflicting specification A request to the bpdbm process (NetBackup Database Manager service on Windows NT/2000) had conflicting information. This is usually a result of using software from different version levels together. 225 text exceeded allowed length A request containing text that exceeds a buffer size was made to the bpdbm process (NetBackup Database Manager service on Windows NT/2000). This is usually a result of using software from different version levels together. 226 the entity already exists The configuration already has an entity with the same name or definition. For example, you see this status if you try to add a new class when an existing class has the same name or definition (attributes, clients, and so on). 227 no entity was found The item requested was not in the catalog. For example, the entity could be a file or class information. 228 unable to process request An inconsistency exists in the catalog or a request was made that would be improper to satisfy. 229 events out of sequence - image inconsistency A request was made which, if satisfied, would cause the image catalog to become inconsistent. 230 the specified class does not exist in the configuration database The specified class name does not exist. 231 schedule windows overlap The start and duration times specified for one day of the schedule overlap with another day of the schedule. 232 a protocol error has occurred This is an intermediate status code that usually precedes another status code. It indicates that either the bpdbm process (NetBackup Database Manager service on Windows NT/2000) or the process communicating with it has received unexpected information. 233 premature eof encountered This is an intermediate status code that usually precedes another status code and is associated with a problem in network communication. 234 communication interrupted This is an intermediate status code that usually precedes another status code and is associated with a problem in network communication. A process, either server or client, received an interrupt signal. 235 inadequate buffer space This code usually indicates a mismatch between server and client software versions. 236 the specified client does not exist in an active class within the configuration database A client name was not specified or the specified client does not exist. 237 the specified schedule does not exist in an active class in the configuration database The specified schedule does not exist in the NetBackup configuration. 238 the database contains conflicting or erroneous entries The catalog has an inconsistent or corrupted entry. 239 the specified client does not exist in the specified class The specified client is not a member of the specified class. 240 no schedules of the correct type exist in this class The appropriate schedule was not found in the specified class. For example, a user backup specified a class name but no user backup schedule exists in that class. 241 the specified schedule is the wrong type for this request The schedule that was specified for an immediate manual backup is not for a full nor an incremental backup. It must be one of these. 242 operation would cause an illegal duplication Processing the request would cause a duplicate catalog entry. This is usually due to a mistake in specifying media IDs for NetBackup catalog backups. 243 the client is not in the configuration The specified client name was not in the catalog. 244 main bpsched is already running A bpsched process tried to become the main backup scheduler but another process is currently in this mode. 245 the specified class is not of the correct client type A user backup specified a class that is not the type required for the client. 246 no active classes in the configuration database are of the correct client type A user backup request was not satisfied because no active classes were the type required for the client. 247 the specified class is not active Backups for the specified class are disabled because the class is inactive. 248 there are no active classes in the configuration database No active class was found that would satisfy the request. 249 the file list is incomplete The server timed out while waiting for the client to finish sending the file list, or a sequencing problem occurred. 250 the image was not created with TIR information This is an internal error and should not be seen by customers. 251 the TIR information is zero length For a true-image backup, the client sent no file information to the master server. NetBackup discovered this condition when it attempted to write the TIR information to media.