| 1 | 0 the requested operation was successfully completed
|
|---|
| 2 | 1 the requested operation was partially successful
|
|---|
| 3 | 2 none of the requested files were backed up
|
|---|
| 4 | 3 valid archive image produced, but no files deleted due to non-fatal problems
|
|---|
| 5 | 4 archive file removal failed
|
|---|
| 6 | 5 the restore failed to recover the requested files
|
|---|
| 7 | 6 the backup failed to back up the requested files
|
|---|
| 8 | 7 the archive failed to back up the requested files
|
|---|
| 9 | 8 unable to determine the status of rbak
|
|---|
| 10 | 9 an extension package is needed, but was not installed
|
|---|
| 11 | 10 allocation failed
|
|---|
| 12 | 11 system call failed
|
|---|
| 13 | 12 file open failed
|
|---|
| 14 | 13 file read failed
|
|---|
| 15 | 14 file write failed
|
|---|
| 16 | 15 file close failed
|
|---|
| 17 | 16 unimplemented feature
|
|---|
| 18 | 17 pipe open failed
|
|---|
| 19 | 18 pipe close failed
|
|---|
| 20 | 19 getservbyname failed
|
|---|
| 21 | 20 invalid command parameter
|
|---|
| 22 | 21 socket open failed
|
|---|
| 23 | 22 socket close failed
|
|---|
| 24 | 23 socket read failed
|
|---|
| 25 | 24 socket write failed
|
|---|
| 26 | 25 cannot connect on socket
|
|---|
| 27 | 26 client/server handshaking failed
|
|---|
| 28 | 27 child process killed by signal
|
|---|
| 29 | 28 failed trying to fork a process
|
|---|
| 30 | 29 failed trying to exec a command
|
|---|
| 31 | 30 could not get passwd information
|
|---|
| 32 | 31 could not set user id for process
|
|---|
| 33 | 32 could not set group id for process
|
|---|
| 34 | 33 failed while trying to send mail
|
|---|
| 35 | 34 failed waiting for child process
|
|---|
| 36 | 35 cannot make required directory
|
|---|
| 37 | 36 failed trying to allocate memory
|
|---|
| 38 | 37 operation requested by an invalid server
|
|---|
| 39 | 38 could not get group information
|
|---|
| 40 | 39 client name mismatch
|
|---|
| 41 | 40 network connection broken
|
|---|
| 42 | 41 network connection timed out
|
|---|
| 43 | 42 network read failed
|
|---|
| 44 | 43 unexpected message received
|
|---|
| 45 | 44 network write failed
|
|---|
| 46 | 45 request attempted on a non reserved port
|
|---|
| 47 | 46 server not allowed access
|
|---|
| 48 | 47 host is unreachable
|
|---|
| 49 | 48 client hostname could not be found
|
|---|
| 50 | 49 client did not start
|
|---|
| 51 | 50 client process aborted
|
|---|
| 52 | 51 timed out waiting for database information
|
|---|
| 53 | 52 timed out waiting for media manager to mount volume
|
|---|
| 54 | 53 backup restore manager failed to read the file list
|
|---|
| 55 | 54 timed out connecting to client
|
|---|
| 56 | 55 permission denied by client during rcmd
|
|---|
| 57 | 56 client's network is unreachable
|
|---|
| 58 | 57 client connection refused
|
|---|
| 59 | 58 can't connect to client
|
|---|
| 60 | 59 access to the client was not allowed
|
|---|
| 61 | 60 client cannot read the mount table
|
|---|
| 62 | 61 wbak was killed
|
|---|
| 63 | 62 wbak exited abnormally
|
|---|
| 64 | 63 process was killed by a signal
|
|---|
| 65 | 64 timed out waiting for the client backup to start
|
|---|
| 66 | 65 client timed out waiting for the continue message from the media manager
|
|---|
| 67 | 66 client backup failed to receive the CONTINUE BACKUP message
|
|---|
| 68 | 67 client backup failed to read the file list
|
|---|
| 69 | 68 client timed out waiting for the file list
|
|---|
| 70 | 69 invalid filelist specification
|
|---|
| 71 | 70 an entry in the filelist expanded to too many characters
|
|---|
| 72 | 71 none of the files in the file list exist
|
|---|
| 73 | 72 the client type is incorrect in the configuration database
|
|---|
| 74 | 73 bpstart_notify failed
|
|---|
| 75 | 74 client timed out waiting for bpstart_notify to complete
|
|---|
| 76 | 75 client timed out waiting for bpend_notify to complete
|
|---|
| 77 | 76 client timed out reading file
|
|---|
| 78 | 77 execution of the specified system command returned a nonzero status
|
|---|
| 79 | 78 afs/dfs command failed
|
|---|
| 80 | 79 unimplemented error code 79
|
|---|
| 81 | 80 Media Manager device daemon (ltid) is not active
|
|---|
| 82 | 81 Media Manager volume daemon (vmd) is not active
|
|---|
| 83 | 82 media manager killed by signal
|
|---|
| 84 | 83 media open error
|
|---|
| 85 | 84 media write error
|
|---|
| 86 | 85 media read error
|
|---|
| 87 | 86 media position error
|
|---|
| 88 | 87 media close error
|
|---|
| 89 | 88 Auspex SP/Backup failure
|
|---|
| 90 | 89 fatal error in Unitree file system
|
|---|
| 91 | 90 media manager received no data for backup image
|
|---|
| 92 | 91 fatal NB media database error
|
|---|
| 93 | 92 media manager detected image that was not in tar format
|
|---|
| 94 | 93 media manager found wrong tape in drive
|
|---|
| 95 | 94 cannot position to correct image
|
|---|
| 96 | 95 requested media id was not found in NB media database and/or MM volume database
|
|---|
| 97 | 96 unable to allocate new media for backup, storage unit has none available
|
|---|
| 98 | 97 requested media id is in use, cannot process request
|
|---|
| 99 | 98 error requesting media (tpreq)
|
|---|
| 100 | 99 NDMP backup failure
|
|---|
| 101 | 100 system error occurred while processing user command
|
|---|
| 102 | 101 failed opening mail pipe
|
|---|
| 103 | 102 failed closing mail pipe
|
|---|
| 104 | 103 error occurred during initialization, check configuration file
|
|---|
| 105 | 104 invalid file pathname
|
|---|
| 106 | 105 file pathname exceeds the maximum length allowed
|
|---|
| 107 | 106 invalid file pathname found, cannot process request
|
|---|
| 108 | 107 too many arguments specified
|
|---|
| 109 | 108 invalid date format specified
|
|---|
| 110 | 109 invalid date specified
|
|---|
| 111 | 110 Cannot find the NetBackup configuration information
|
|---|
| 112 | 111 No entry was found in the server list
|
|---|
| 113 | 112 no files specified in the file list
|
|---|
| 114 | 113 unimplemented error code 113
|
|---|
| 115 | 114 unimplemented error code 114
|
|---|
| 116 | 115 unimplemented error code 115
|
|---|
| 117 | 116 unimplemented error code 116
|
|---|
| 118 | 117 unimplemented error code 117
|
|---|
| 119 | 118 unimplemented error code 118
|
|---|
| 120 | 119 unimplemented error code 119
|
|---|
| 121 | 120 cannot find configuration database record for requested NB database backup
|
|---|
| 122 | 121 no media is defined for the requested NB database backup
|
|---|
| 123 | 122 specified device path does not exist
|
|---|
| 124 | 123 specified disk path is not a directory
|
|---|
| 125 | 124 NB database backup failed, a path was not found or is inaccessable
|
|---|
| 126 | 125 another NB database backup is already in progress
|
|---|
| 127 | 126 NB database backup header is too large, too many paths specified
|
|---|
| 128 | 127 specified media or path does not contain a valid NB database backup header
|
|---|
| 129 | 128 unimplemented error code 128
|
|---|
| 130 | 129 unimplemented error code 129
|
|---|
| 131 | 130 system error occurred
|
|---|
| 132 | 131 client is not validated to use the server
|
|---|
| 133 | 132 user is not validated to use the server from this client
|
|---|
| 134 | 133 invalid request
|
|---|
| 135 | 134 unable to process request because the server resources are busy
|
|---|
| 136 | 135 client is not validated to perform the requested operation
|
|---|
| 137 | 136 unimplemented error code 136
|
|---|
| 138 | 137 unimplemented error code 137
|
|---|
| 139 | 138 unimplemented error code 138
|
|---|
| 140 | 139 unimplemented error code 139
|
|---|
| 141 | 140 user id was not superuser
|
|---|
| 142 | 141 file path specified is not absolute
|
|---|
| 143 | 142 file does not exist
|
|---|
| 144 | 143 invalid command protocol
|
|---|
| 145 | 144 invalid command usage
|
|---|
| 146 | 145 daemon is already running
|
|---|
| 147 | 146 cannot get a bound socket
|
|---|
| 148 | 147 required or specified copy was not found
|
|---|
| 149 | 148 daemon fork failed
|
|---|
| 150 | 149 master server request failed
|
|---|
| 151 | 150 termination requested by administrator
|
|---|
| 152 | 151 Backup Exec operation failed
|
|---|
| 153 | 152 required value not set
|
|---|
| 154 | 153 server is not the master server
|
|---|
| 155 | 154 storage unit characteristics mismatched to request
|
|---|
| 156 | 155 unused b
|
|---|
| 157 | 156 unused f
|
|---|
| 158 | 157 unused d
|
|---|
| 159 | 158 failed accessing daemon lock file
|
|---|
| 160 | 159 licensed use has been exceeded
|
|---|
| 161 | 160 authentication failed
|
|---|
| 162 | 161 Evaluation software has expired. See www.veritas.com for ordering information
|
|---|
| 163 | 162 unimplemented error code 162
|
|---|
| 164 | 163 unimplemented error code 163
|
|---|
| 165 | 164 unable to mount media because its in a DOWN drive or misplaced
|
|---|
| 166 | 165 NB image database contains no image fragments for requested backup id/copy number
|
|---|
| 167 | 166 backups are not allowed to span media
|
|---|
| 168 | 167 cannot find requested volume pool in Media Manager volume database
|
|---|
| 169 | 168 cannot overwrite media, data on it is protected
|
|---|
| 170 | 169 media id is either expired or will exceed maximum mounts
|
|---|
| 171 | 170 unimplemented error code 170
|
|---|
| 172 | 171 media id must be 6 or less characters
|
|---|
| 173 | 172 cannot read media header, may not be NetBackup media or is corrupted
|
|---|
| 174 | 173 cannot read backup header, media may be corrupted
|
|---|
| 175 | 174 media manager - system error occurred
|
|---|
| 176 | 175 not all requested files were restored
|
|---|
| 177 | 176 cannot perform specified media import operation
|
|---|
| 178 | 177 could not deassign media due to Media Manager error
|
|---|
| 179 | 178 media id is not in NetBackup volume pool
|
|---|
| 180 | 179 density is incorrect for the media id
|
|---|
| 181 | 180 tar was successful
|
|---|
| 182 | 181 tar received an invalid argument
|
|---|
| 183 | 182 tar received an invalid file name
|
|---|
| 184 | 183 tar received an invalid archive
|
|---|
| 185 | 184 tar had an unexpected error
|
|---|
| 186 | 185 tar did not find all the files to be restored
|
|---|
| 187 | 186 tar received no data
|
|---|
| 188 | 187 unimplemented error code 187
|
|---|
| 189 | 188 unimplemented error code 188
|
|---|
| 190 | 189 the server is not allowed to write to the client's filesystems
|
|---|
| 191 | 190 found no images or media matching the selection criteria
|
|---|
| 192 | 191 no images were successfully processed
|
|---|
| 193 | 192 unimplemented error code 192
|
|---|
| 194 | 193 unimplemented error code 193
|
|---|
| 195 | 194 the maximum number of jobs per client is set to 0
|
|---|
| 196 | 195 client backup was not attempted
|
|---|
| 197 | 196 client backup was not attempted because backup window closed
|
|---|
| 198 | 197 the specified schedule does not exist in the specified class
|
|---|
| 199 | 198 no active classes contain schedules of the requested type for this client
|
|---|
| 200 | 199 operation not allowed during this time period
|
|---|
| 201 | 200 scheduler found no backups due to run
|
|---|
| 202 | 201 handshaking failed with server backup restore manager
|
|---|
| 203 | 202 timed out connecting to server backup restore manager
|
|---|
| 204 | 203 server backup restore manager's network is unreachable
|
|---|
| 205 | 204 connection refused by server backup restore manager
|
|---|
| 206 | 205 cannot connect to server backup restore manager
|
|---|
| 207 | 206 access to server backup restore manager denied
|
|---|
| 208 | 207 error obtaining date of last backup for client
|
|---|
| 209 | 208 failed reading user directed filelist
|
|---|
| 210 | 209 error creating or getting message queue
|
|---|
| 211 | 210 error receiving information on message queue
|
|---|
| 212 | 211 scheduler child killed by signal
|
|---|
| 213 | 212 error sending information on message queue
|
|---|
| 214 | 213 no storage units available for use
|
|---|
| 215 | 214 regular bpsched is already running
|
|---|
| 216 | 215 failed reading global config database information
|
|---|
| 217 | 216 failed reading retention database information
|
|---|
| 218 | 217 failed reading storage unit database information
|
|---|
| 219 | 218 failed reading class database information
|
|---|
| 220 | 219 the required storage unit is unavailable
|
|---|
| 221 | 220 database system error
|
|---|
| 222 | 221 continue
|
|---|
| 223 | 222 done
|
|---|
| 224 | 223 an invalid entry was encountered
|
|---|
| 225 | 224 there was a conflicting specification
|
|---|
| 226 | 225 text exceeded allowed length
|
|---|
| 227 | 226 the entity already exists
|
|---|
| 228 | 227 no entity was found
|
|---|
| 229 | 228 unable to process request
|
|---|
| 230 | 229 events out of sequence - image inconsistency
|
|---|
| 231 | 230 the specified class does not exist in the configuration database
|
|---|
| 232 | 231 schedule windows overlap
|
|---|
| 233 | 232 a protocol error has occurred
|
|---|
| 234 | 233 premature eof encountered
|
|---|
| 235 | 234 communication interrupted
|
|---|
| 236 | 235 inadequate buffer space
|
|---|
| 237 | 236 the specified client does not exist in an active class within the configuration database
|
|---|
| 238 | 237 the specified schedule does not exist in an active class in the configuration database
|
|---|
| 239 | 238 the database contains conflicting or erroneous entries
|
|---|
| 240 | 239 the specified client does not exist in the specified class
|
|---|
| 241 | 240 no schedules of the correct type exist in this class
|
|---|
| 242 | 241 the specified schedule is the wrong type for this request
|
|---|
| 243 | 242 operation would cause an illegal duplication
|
|---|
| 244 | 243 the client is not in the configuration
|
|---|
| 245 | 244 main bpsched is already running
|
|---|
| 246 | 245 the specified class is not of the correct client type
|
|---|
| 247 | 246 no active classes in the configuration database are of the correct client type
|
|---|
| 248 | 247 the specified class is not active
|
|---|
| 249 | 248 there are no active classes in the configuration database
|
|---|
| 250 | 249 the file list is incomplete
|
|---|
| 251 | 250 the image was not created with TIR information
|
|---|
| 252 | 251 the tir information is zero length
|
|---|
| 253 | 252 unused TIR error 2
|
|---|
| 254 | 253 unused TIR error 1
|
|---|
| 255 | 254 server name not found in the bp.conf file
|
|---|
| 256 | 255 unimplemented error code 255
|
|---|
