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