Veritas NetBackup™ Status Codes Reference Guide: UNIX

Veritas NetBackup™ Status
Codes Reference Guide
UNIX, Windows, and Linux
Release 8.1
Veritas NetBackup™ Status Codes Reference Guide
Legal Notice
Copyright © 2017 Veritas Technologies LLC. All rights reserved.
Veritas, the Veritas Logo, and NetBackup are trademarks or registered trademarks of Veritas
Technologies LLC or its affiliates in the U.S. and other countries. Other names may be
trademarks of their respective owners.
This product may contain third party software for which Veritas is required to provide attribution
to the third party (“Third Party Programs”). Some of the Third Party Programs are available
under open source or free software licenses. The License Agreement accompanying the
Software does not alter any rights or obligations you may have under those open source or
free software licenses. Refer to the third party legal notices document accompanying this
Veritas product or available at:
https://www.veritas.com/about/legal/license-agreements
The product described in this document is distributed under licenses restricting its use, copying,
distribution, and decompilation/reverse engineering. No part of this document may be
reproduced in any form by any means without prior written authorization of Veritas Technologies
LLC and its licensors, if any.
THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED
CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED
WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR
NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH
DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. VERITAS TECHNOLOGIES LLC
SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN
CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS
DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS
SUBJECT TO CHANGE WITHOUT NOTICE.
The Licensed Software and Documentation are deemed to be commercial computer software
as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19
"Commercial Computer Software - Restricted Rights" and DFARS 227.7202, et seq.
"Commercial Computer Software and Commercial Computer Software Documentation," as
applicable, and any successor regulations, whether delivered by Veritas as on premises or
hosted services. Any use, modification, reproduction release, performance, display or disclosure
of the Licensed Software and Documentation by the U.S. Government shall be solely in
accordance with the terms of this Agreement.
Veritas Technologies LLC
500 E Middlefield Road
Mountain View, CA 94043
http://www.veritas.com
Technical Support
Technical Support maintains support centers globally. All support services will be delivered
in accordance with your support agreement and the then-current enterprise technical support
policies. For information about our support offerings and how to contact Technical Support,
visit our website:
https://www.veritas.com/support
You can manage your Veritas account information at the following URL:
https://my.veritas.com
If you have questions regarding an existing support agreement, please email the support
agreement administration team for your region as follows:
Worldwide (except Japan)
CustomerCare@veritas.com
Japan
CustomerCare_Japan@veritas.com
Documentation
The latest documentation is available on the Veritas website:
https://sort.veritas.com/documents
Documentation feedback
Your feedback is important to us. Suggest improvements or report errors or omissions to the
documentation. Include the document title, document version, chapter title, and section title
of the text on which you are reporting. Send feedback to:
NB.doc@veritas.com
You can also see documentation information or ask a question on the Veritas community site:
http://www.veritas.com/community/
Veritas Services and Operations Readiness Tools (SORT)
Veritas Services and Operations Readiness Tools (SORT) is a website that provides information
and tools to automate and simplify certain time-consuming administrative tasks. Depending
on the product, SORT helps you prepare for installations and upgrades, identify risks in your
datacenters, and improve operational efficiency. To see what services and tools SORT provides
for your product, see the data sheet:
https://sort.veritas.com/data/support/SORT_Data_Sheet.pdf
Contents
Chapter 1
NetBackup status codes
................................................. 44
NetBackup status codes ................................................................
NetBackup status code: 0 ........................................................
NetBackup status code: 1 ........................................................
NetBackup status code: 2 ........................................................
NetBackup status code: 3 ........................................................
NetBackup status code: 4 ........................................................
NetBackup status code: 5 ........................................................
NetBackup status code: 6 ........................................................
NetBackup status code: 7 ........................................................
NetBackup status code: 8 ........................................................
NetBackup status code: 9 ........................................................
NetBackup status code: 10 .......................................................
NetBackup status code: 11 .......................................................
NetBackup status code: 12 .......................................................
NetBackup status code: 13 .......................................................
NetBackup status code: 14 .......................................................
NetBackup status code: 15 .......................................................
NetBackup status code: 16 .......................................................
NetBackup status code: 17 .......................................................
NetBackup status code: 18 .......................................................
NetBackup status code: 19 .......................................................
NetBackup status code: 20 .......................................................
NetBackup status code: 21 .......................................................
NetBackup status code: 22 .......................................................
NetBackup status code: 23 .......................................................
NetBackup status code: 24 .......................................................
NetBackup status code: 25 .......................................................
NetBackup status code: 26 .......................................................
NetBackup status code: 27 .......................................................
NetBackup status code: 28 .......................................................
NetBackup status code: 29 .......................................................
NetBackup status code: 30 .......................................................
NetBackup status code: 31 .......................................................
NetBackup status code: 32 .......................................................
NetBackup status code: 33 .......................................................
44
44
45
49
50
51
51
52
54
54
54
55
55
57
58
62
63
63
63
63
64
64
67
68
68
69
70
73
73
74
74
75
75
75
75
Contents
NetBackup status code: 34 ....................................................... 76
NetBackup status code: 35 ....................................................... 76
NetBackup status code: 36 ....................................................... 77
NetBackup status code: 37 ....................................................... 77
NetBackup status code: 38 ....................................................... 78
NetBackup status code: 39 ....................................................... 78
NetBackup status code: 40 ....................................................... 78
NetBackup status code: 41 ....................................................... 79
NetBackup status code: 42 ....................................................... 83
NetBackup status code: 43 ....................................................... 83
NetBackup status code: 44 ....................................................... 84
NetBackup status code: 45 ....................................................... 84
NetBackup status code: 46 ....................................................... 85
NetBackup status code: 47 ....................................................... 86
NetBackup status code: 48 ....................................................... 86
NetBackup status code: 49 ....................................................... 87
NetBackup status code: 50 ....................................................... 88
NetBackup status code: 51 ....................................................... 89
NetBackup status code: 52 ....................................................... 89
NetBackup status code: 53 ....................................................... 90
NetBackup status code: 54 ....................................................... 91
NetBackup status code: 55 ....................................................... 91
NetBackup status code: 56 ....................................................... 92
NetBackup status code: 57 ....................................................... 92
NetBackup status code: 58 ....................................................... 93
NetBackup status code: 59 ....................................................... 93
NetBackup status code: 60 ....................................................... 95
NetBackup status code: 61 ....................................................... 96
NetBackup status code: 63 ....................................................... 96
NetBackup status code: 64 ....................................................... 96
NetBackup status code: 65 ....................................................... 97
NetBackup status code: 66 ....................................................... 97
NetBackup status code: 67 ....................................................... 98
NetBackup status code: 68 ....................................................... 99
NetBackup status code: 69 ....................................................... 99
NetBackup status code: 70 ..................................................... 100
NetBackup status code: 71 ..................................................... 100
NetBackup status code: 72 ..................................................... 101
NetBackup status code: 73 ..................................................... 101
NetBackup status code: 74 ..................................................... 101
NetBackup status code: 75 ..................................................... 102
NetBackup status code: 76 ..................................................... 102
NetBackup status code: 77 ..................................................... 102
5
Contents
NetBackup status code: 78 .....................................................
NetBackup status code: 79 .....................................................
NetBackup status code: 80 .....................................................
NetBackup status code: 81 .....................................................
NetBackup status code: 82 .....................................................
NetBackup status code: 83 .....................................................
NetBackup status code: 84 .....................................................
NetBackup status code: 85 .....................................................
NetBackup status code: 86 .....................................................
NetBackup status code: 87 .....................................................
NetBackup status code: 89 .....................................................
NetBackup status code: 90 .....................................................
NetBackup status code: 91 ....................................................
NetBackup status code: 92 ....................................................
NetBackup status code: 93 ....................................................
NetBackup status code: 94 .....................................................
NetBackup status code: 95 ....................................................
NetBackup status code: 96 ....................................................
NetBackup status code: 97 ....................................................
NetBackup status code: 98 .....................................................
NetBackup status code: 99 .....................................................
NetBackup status code: 100 ...................................................
NetBackup status code: 101 ...................................................
NetBackup status code: 102 ...................................................
NetBackup status code: 103 ...................................................
NetBackup status code: 104 ...................................................
NetBackup status code: 105 ...................................................
NetBackup status code: 106 ...................................................
NetBackup status code: 108 ...................................................
NetBackup status code: 109 ...................................................
NetBackup status code: 110 ....................................................
NetBackup status code: 111 ....................................................
NetBackup status code: 112 ....................................................
NetBackup status code: 114 ....................................................
NetBackup status code: 116 ....................................................
NetBackup status code: 117 ....................................................
NetBackup status code: 118 ....................................................
NetBackup status code: 120 ...................................................
NetBackup status code: 121 ...................................................
NetBackup status code: 122 ...................................................
NetBackup status code: 123 ...................................................
NetBackup status code: 124 ...................................................
NetBackup status code: 125 ...................................................
103
104
104
104
105
105
107
108
109
110
110
111
112
113
114
114
115
115
117
118
118
119
119
119
120
120
121
121
121
122
122
123
123
124
124
125
126
128
129
129
129
129
130
6
Contents
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
126
127
128
129
130
131
132
133
134
135
136
140
141
142
143
144
145
146
147
148
149
150
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
130
130
131
131
132
133
133
134
135
135
135
136
136
136
137
138
138
138
139
139
140
140
140
140
141
141
142
155
155
156
156
157
157
157
158
158
158
159
159
159
160
161
161
7
Contents
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
173
174
175
176
177
178
179
180
181
182
183
184
185
186
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
209
210
212
213
215
216
217
218
219
220
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
162
162
164
164
165
166
166
166
166
167
167
168
169
169
170
170
170
172
173
173
174
174
174
175
176
176
177
178
179
180
181
183
183
184
184
185
185
186
186
187
187
188
189
8
Contents
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
NetBackup
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
code:
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
245
246
247
248
249
250
251
252
253
254
256
257
258
259
260
261
262
263
265
266
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
189
190
190
190
191
191
191
192
192
193
193
193
193
194
194
195
195
195
195
196
196
196
197
197
197
197
198
198
198
198
199
199
199
200
200
200
200
201
201
201
201
202
202
9
Contents
NetBackup status code: 267
NetBackup status code: 268
NetBackup status code: 269
NetBackup status code: 270
NetBackup status code: 271
NetBackup status code: 272
NetBackup status code: 273
NetBackup status code: 274
NetBackup status code: 275
NetBackup status code: 276
NetBackup status code: 277
NetBackup status code: 278
NetBackup status code: 279
NetBackup status code: 280
NetBackup status code: 281
NetBackup status code: 282
NetBackup status code: 283
NetBackup status code: 284
NetBackup status code: 285
NetBackup status code: 286
NetBackup status code: 287
NetBackup status code: 288
NetBackup status code: 289
NetBackup status code: 290
NetBackup status code: 291
NetBackup status code: 292
NetBackup status code: 293
NetBackup status code: 294
NetBackup status code: 295
NetBackup status code: 296
NetBackup status code: 297
NetBackup status code: 298
NetBackup status code: 299
NetBackup status code: 300
NetBackup status code: 301
NetBackup status code: 302
NetBackup status code: 303
NetBackup status code: 304
NetBackup status code: 305
NetBackup status code: 306
NetBackup status code: 307
NetBackup status code: 308
NetBackup status code: 309
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
202
203
203
204
204
204
204
205
205
205
205
206
206
206
206
207
207
207
208
208
208
209
209
209
210
211
211
212
213
213
214
214
214
215
215
216
217
217
217
218
218
218
219
10
Contents
NetBackup status code: 310 ...................................................
NetBackup status code: 311 ....................................................
NetBackup status code: 312 ...................................................
NetBackup status code: 313 ...................................................
NetBackup status code: 314 ...................................................
NetBackup status code: 315 ...................................................
NetBackup status code: 316 ...................................................
NetBackup status code: 317 ...................................................
NetBackup status code: 318 ...................................................
NetBackup status code: 319 ...................................................
NetBackup status code: 320 ...................................................
NetBackup status code: 321 ...................................................
NetBackup status code: 322 ...................................................
NetBackup status code: 323 ...................................................
NetBackup status code: 324 ...................................................
NetBackup status code: 325 ...................................................
NetBackup status code: 326 ...................................................
NetBackup status code: 327 ...................................................
NetBackup status code: 328 ...................................................
NetBackup status code: 329 ...................................................
NetBackup status code: 330 ...................................................
NetBackup status code: 331 ...................................................
NetBackup status code: 332 ...................................................
NetBackup status code: 333 ...................................................
NetBackup status code: 334 ...................................................
NetBackup status code: 335 ...................................................
NetBackup status code: 336 ...................................................
NetBackup status code: 337 ...................................................
NetBackup status code: 338 ...................................................
NetBackup status code: 339 ...................................................
NetBackup status code: 340 ...................................................
NetBackup status code: 341 ...................................................
NetBackup status code: 342 ...................................................
NetBackup status code: 343 ...................................................
NetBackup status code: 344 ...................................................
NetBackup status code: 345 ...................................................
NetBackup status code: 346 ...................................................
NetBackup status code: 347 ...................................................
NetBackup status code: 348 ...................................................
NetBackup status code: 349 ...................................................
NetBackup status code: 350 ...................................................
NetBackup status code: 351 ...................................................
NetBackup status code: 400 ...................................................
219
220
220
220
221
221
221
222
222
222
223
223
224
224
224
225
225
225
226
226
226
227
227
228
228
228
228
229
229
229
229
230
230
230
231
231
231
231
232
232
232
232
233
11
Contents
NetBackup status code: 401
NetBackup status code: 402
NetBackup status code: 403
NetBackup status code: 404
NetBackup status code: 405
NetBackup status code: 406
NetBackup status code: 407
NetBackup status code: 408
NetBackup status code: 409
NetBackup status code: 501
NetBackup status code: 502
NetBackup status code: 503
NetBackup status code: 504
NetBackup status code: 505
NetBackup status code: 506
NetBackup status code: 507
NetBackup status code: 508
NetBackup status code: 509
NetBackup status code: 510
NetBackup status code: 511
NetBackup status code: 512
NetBackup status code: 513
NetBackup status code: 514
NetBackup status code: 516
NetBackup status code: 517
NetBackup status code: 518
NetBackup status code: 519
NetBackup status code: 520
NetBackup status code: 521
NetBackup status code: 522
NetBackup status code: 523
NetBackup status code: 525
NetBackup status code: 526
NetBackup status code: 527
NetBackup status code: 537
NetBackup status code: 538
NetBackup status code: 552
NetBackup status code: 600
NetBackup status code: 601
NetBackup status code: 602
NetBackup status code: 603
NetBackup status code: 604
NetBackup status code: 605
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
233
233
234
234
235
235
236
236
236
237
237
237
238
238
239
240
240
241
241
242
242
243
243
244
245
245
246
246
246
246
247
247
248
248
249
249
249
250
250
250
251
251
252
12
Contents
NetBackup status code: 606
NetBackup status code: 607
NetBackup status code: 608
NetBackup status code: 609
NetBackup status code: 610
NetBackup status code: 611
NetBackup status code: 612
NetBackup status code: 613
NetBackup status code: 614
NetBackup status code: 615
NetBackup status code: 616
NetBackup status code: 617
NetBackup status code: 618
NetBackup status code: 619
NetBackup status code: 620
NetBackup status code: 621
NetBackup status code: 622
NetBackup status code: 623
NetBackup status code: 624
NetBackup status code: 625
NetBackup status code: 626
NetBackup status code: 627
NetBackup status code: 628
NetBackup status code: 629
NetBackup status code: 630
NetBackup status code: 631
NetBackup status code: 632
NetBackup status code: 633
NetBackup status code: 634
NetBackup status code: 635
NetBackup status code: 636
NetBackup status code: 637
NetBackup status code: 638
NetBackup status code: 639
NetBackup status code: 640
NetBackup status code: 641
NetBackup status code: 642
NetBackup status code: 643
NetBackup status code: 644
NetBackup status code: 645
NetBackup status code: 646
NetBackup status code: 647
NetBackup status code: 648
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
252
252
253
253
254
254
254
255
255
256
256
256
257
257
257
258
258
258
259
259
259
260
260
260
261
261
262
262
262
263
263
264
264
264
265
266
266
266
266
267
268
268
269
13
Contents
NetBackup status code: 649
NetBackup status code: 650
NetBackup status code: 651
NetBackup status code: 652
NetBackup status code: 653
NetBackup status code: 654
NetBackup status code: 655
NetBackup status code: 656
NetBackup status code: 657
NetBackup status code: 658
NetBackup status code: 659
NetBackup status code: 660
NetBackup status code: 661
NetBackup status code: 662
NetBackup status code: 663
NetBackup status code: 664
NetBackup status code: 665
NetBackup status code: 667
NetBackup status code: 668
NetBackup status code: 669
NetBackup status code: 670
NetBackup status code: 671
NetBackup status code: 800
NetBackup status code: 801
NetBackup status code: 802
NetBackup status code: 803
NetBackup status code: 805
NetBackup status code: 806
NetBackup status code: 807
NetBackup status code: 811
NetBackup status code: 812
NetBackup status code: 813
NetBackup status code: 818
NetBackup status code: 819
NetBackup status code: 823
NetBackup status code: 830
NetBackup status code: 831
NetBackup status code: 832
NetBackup status code: 833
NetBackup status code: 900
NetBackup status code: 901
NetBackup status code: 902
NetBackup status code: 903
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
...................................................
269
269
270
270
271
271
271
272
272
272
273
273
274
274
274
275
275
275
276
276
276
277
277
277
278
279
280
280
281
281
281
282
282
282
282
283
284
284
284
285
285
286
286
14
Contents
NetBackup status code: 904 ...................................................
NetBackup status code: 905 ...................................................
NetBackup status code: 906 ...................................................
NetBackup status code: 907 ...................................................
NetBackup status code: 908 ...................................................
NetBackup status code: 912 ...................................................
NetBackup status code: 914 ...................................................
NetBackup status code: 915 ...................................................
NetBackup status code: 916 ...................................................
NetBackup status code: 917 ...................................................
NetBackup status code: 918 ...................................................
NetBackup status code: 1000 ..................................................
NetBackup status code: 1001 ..................................................
NetBackup status code: 1002 ..................................................
NetBackup status code: 1057 ..................................................
NetBackup status code: 1058 ..................................................
NetBackup status code: 1401 ..................................................
NetBackup status code: 1402 ..................................................
NetBackup status code: 1403 ..................................................
NetBackup status code: 1405 ..................................................
NetBackup status code: 1407 ..................................................
NetBackup status code: 1408 ..................................................
NetBackup status code: 1409 ..................................................
NetBackup status code: 1410 ..................................................
NetBackup status code: 1411 ..................................................
NetBackup status code: 1412 ..................................................
NetBackup status code: 1413 ..................................................
NetBackup status code: 1414 ..................................................
NetBackup status code: 1415 ..................................................
NetBackup status code: 1416 ..................................................
NetBackup status code: 1417 ..................................................
NetBackup status code: 1418 ..................................................
NetBackup status code: 1419 ..................................................
NetBackup status code: 1420 ..................................................
NetBackup status code: 1421 ..................................................
NetBackup status code: 1422 ..................................................
NetBackup status code: 1423 ..................................................
NetBackup status code: 1425 ..................................................
NetBackup status code: 1426 ..................................................
NetBackup status code: 1500 ..................................................
NetBackup status code: 1501 ..................................................
NetBackup status code: 1502 ..................................................
NetBackup status code: 1503 ..................................................
286
287
287
287
288
288
289
289
289
290
290
290
291
291
291
292
292
292
293
293
293
293
293
294
294
294
294
295
295
295
295
296
296
296
296
296
297
297
297
297
298
298
299
15
Contents
NetBackup status code: 1504 ..................................................
NetBackup status code: 1505 ..................................................
NetBackup status code: 1506 ..................................................
NetBackup status code: 1507 ..................................................
NetBackup status code: 1508 ..................................................
NetBackup status code: 1509 ..................................................
NetBackup status code: 1510 ..................................................
NetBackup status code: 1511 ..................................................
NetBackup status code: 1512 ..................................................
NetBackup status code: 1513 ..................................................
NetBackup status code: 1514 ..................................................
NetBackup status code: 1515 ..................................................
NetBackup status code: 1516 ..................................................
NetBackup status code: 1517 ..................................................
NetBackup status code: 1518 ..................................................
NetBackup status code: 1519 ..................................................
NetBackup status code: 1521 ..................................................
NetBackup status code: 1522 ..................................................
NetBackup status code: 1523 ..................................................
NetBackup status code: 1524 ..................................................
NetBackup status code: 1525 ..................................................
NetBackup status code: 1526 ..................................................
NetBackup status code: 1527 ..................................................
NetBackup status code: 1528 ..................................................
NetBackup status code: 1529 ..................................................
NetBackup status code: 1530 .................................................
NetBackup status code: 1531 ..................................................
NetBackup status code: 1532 ..................................................
NetBackup status code: 1533 ..................................................
NetBackup status code: 1534 ..................................................
NetBackup status code: 1535 ..................................................
NetBackup status code: 1536 ..................................................
NetBackup status code: 1537 ..................................................
NetBackup status code: 1538 ..................................................
NetBackup status code: 1539 ..................................................
NetBackup status code: 1540 ..................................................
NetBackup status code: 1541 ..................................................
NetBackup status code: 1542 ..................................................
NetBackup status code: 1543 ..................................................
NetBackup status code: 1545 ..................................................
NetBackup status code: 1546 ..................................................
NetBackup status code: 1547 ..................................................
NetBackup status code: 1548 ..................................................
299
300
300
300
301
301
301
302
302
302
303
303
303
304
304
304
305
305
305
305
306
306
306
307
307
308
309
309
310
310
310
311
311
312
312
313
313
313
314
314
314
314
315
16
Contents
NetBackup status code: 1549 ..................................................
NetBackup status code: 1552 ..................................................
NetBackup status code: 1553 ..................................................
NetBackup status code: 1554 ..................................................
NetBackup status code: 1556 ..................................................
NetBackup status code: 1557 ..................................................
NetBackup status code: 1558 ..................................................
NetBackup status code: 1559 ..................................................
NetBackup status code: 1560 ..................................................
NetBackup status code: 1561 ..................................................
NetBackup status code: 1562 ..................................................
NetBackup status code: 1563 ..................................................
NetBackup status code: 1564 ..................................................
NetBackup status code: 1565 ..................................................
NetBackup status code: 1566 ..................................................
NetBackup status code: 1567 ..................................................
NetBackup status code: 1568 ..................................................
NetBackup status code: 1569 ..................................................
NetBackup status code: 1570 ..................................................
NetBackup status code: 1571 ..................................................
NetBackup status code: 1572 ..................................................
NetBackup status code: 1573 ..................................................
NetBackup status code: 1574 ..................................................
NetBackup status code: 1575 ..................................................
NetBackup status code: 1576 ..................................................
NetBackup status code: 1577 ..................................................
NetBackup status code: 1578 ..................................................
NetBackup status code: 1579 ..................................................
NetBackup status code: 1580 ..................................................
NetBackup status code: 1581 ..................................................
NetBackup status code: 1582 ..................................................
NetBackup status code: 1583 ..................................................
NetBackup status code: 1584 ..................................................
NetBackup status code: 1585 ..................................................
NetBackup status code: 1586 ..................................................
NetBackup status code: 1587 ..................................................
NetBackup status code: 1588 ..................................................
NetBackup status code: 1589 ..................................................
NetBackup status code: 1590 ..................................................
NetBackup status code: 1591 ..................................................
NetBackup status code: 1592 ..................................................
NetBackup status code: 1593 ..................................................
NetBackup status code: 1594 ..................................................
315
316
316
317
317
317
318
318
318
319
319
319
320
320
320
320
321
321
321
322
322
322
323
323
323
324
324
324
324
325
325
325
326
326
326
327
327
327
327
328
328
328
329
17
Contents
NetBackup status code: 1596 ..................................................
NetBackup status code: 1597 ..................................................
NetBackup status code: 1598 ..................................................
NetBackup status code: 1599 ..................................................
NetBackup status code: 1600 ..................................................
NetBackup status code: 1601 ..................................................
NetBackup status code: 1602 ..................................................
NetBackup status code: 1603 ..................................................
NetBackup status code: 1604 ..................................................
NetBackup status code: 1800 ..................................................
NetBackup status code: 1915 ..................................................
NetBackup status code: 1916 ..................................................
NetBackup status code: 1917 ..................................................
NetBackup status code: 1918 ..................................................
NetBackup status code: 1919 ..................................................
NetBackup status code: 1920 ..................................................
NetBackup status code: 1921 ..................................................
NetBackup status code: 1922 ..................................................
NetBackup status code: 1924 ..................................................
NetBackup status code: 1925 ..................................................
NetBackup status code: 1926 ..................................................
NetBackup status code: 1927 ..................................................
NetBackup status code: 1928 ..................................................
NetBackup status code: 2000 ..................................................
NetBackup status code: 2001 ..................................................
NetBackup status code: 2002 ..................................................
NetBackup status code: 2003 ..................................................
NetBackup status code: 2004 ..................................................
NetBackup status code: 2005 ..................................................
NetBackup status code: 2006 ..................................................
NetBackup status code: 2007 ..................................................
NetBackup status code: 2008 ..................................................
NetBackup status code: 2009 ..................................................
NetBackup status code: 2010 ..................................................
NetBackup status code: 2011 ..................................................
NetBackup status code: 2012 ..................................................
NetBackup status code: 2013 ..................................................
NetBackup status code: 2014 ..................................................
NetBackup status code: 2015 ..................................................
NetBackup status code: 2016 ..................................................
NetBackup status code: 2017 ..................................................
NetBackup status code: 2018 ..................................................
NetBackup status code: 2019 ..................................................
329
329
329
330
330
330
331
331
331
332
332
332
333
333
333
334
334
334
335
335
335
336
336
336
337
338
338
339
339
339
340
340
340
341
341
341
342
342
343
343
343
344
344
18
Contents
NetBackup status code: 2020 ..................................................
NetBackup status code: 2021 ..................................................
NetBackup status code: 2022 ..................................................
NetBackup status code: 2023 ..................................................
NetBackup status code: 2024 ..................................................
NetBackup status code: 2025 ..................................................
NetBackup status code: 2026 ..................................................
NetBackup status code: 2027 ..................................................
NetBackup status code: 2028 ..................................................
NetBackup status code: 2029 ..................................................
NetBackup status code: 2030 ..................................................
NetBackup status code: 2031 ..................................................
NetBackup status code: 2032 ..................................................
NetBackup status code: 2033 ..................................................
NetBackup status code: 2034 ..................................................
NetBackup status code: 2035 ..................................................
NetBackup status code: 2036 ..................................................
NetBackup status code: 2037 ..................................................
NetBackup status code: 2038 ..................................................
NetBackup status code: 2039 ..................................................
NetBackup status code: 2040 ..................................................
NetBackup status code: 2041 ..................................................
NetBackup status code: 2042 ..................................................
NetBackup status code: 2043 ..................................................
NetBackup status code: 2044 ..................................................
NetBackup status code: 2045 ..................................................
NetBackup status code: 2046 ..................................................
NetBackup status code: 2047 ..................................................
NetBackup status code: 2048 ..................................................
NetBackup status code: 2049 ..................................................
NetBackup status code: 2050 ..................................................
NetBackup status code: 2051 ..................................................
NetBackup status code: 2052 ..................................................
NetBackup status code: 2053 ..................................................
NetBackup status code: 2054 ..................................................
NetBackup status code: 2055 ..................................................
NetBackup status code: 2056 ..................................................
NetBackup status code: 2057 ..................................................
NetBackup status code: 2058 ..................................................
NetBackup status code: 2059 ..................................................
NetBackup status code: 2060 ..................................................
NetBackup status code: 2061 ..................................................
NetBackup status code: 2062 ..................................................
344
344
345
345
345
346
346
347
347
347
348
348
349
349
349
350
350
350
351
351
351
352
352
352
352
353
353
353
353
354
354
354
355
355
355
355
356
356
356
356
357
357
357
19
Contents
NetBackup status code: 2063 ..................................................
NetBackup status code: 2064 ..................................................
NetBackup status code: 2065 ..................................................
NetBackup status code: 2066 ..................................................
NetBackup status code: 2067 ..................................................
NetBackup status code: 2068 ..................................................
NetBackup status code: 2069 ..................................................
NetBackup status code: 2070 ..................................................
NetBackup status code: 2071 ..................................................
NetBackup status code: 2072 ..................................................
NetBackup status code: 2073 ..................................................
NetBackup status code: 2074 ..................................................
NetBackup status code: 2075 ..................................................
NetBackup status code: 2076 ..................................................
NetBackup status code: 2078 ..................................................
NetBackup status code: 2079 ..................................................
NetBackup status code: 2080 ..................................................
NetBackup status code: 2081 ..................................................
NetBackup status code: 2082 ..................................................
NetBackup status code: 2083 ..................................................
NetBackup status code: 2084 ..................................................
NetBackup status code: 2085 ..................................................
NetBackup status code: 2086 ..................................................
NetBackup status code: 2087 ..................................................
NetBackup status code: 2088 ..................................................
NetBackup status code: 2089 ..................................................
NetBackup status code: 2090 ..................................................
NetBackup status code: 2091 ..................................................
NetBackup status code: 2092 ..................................................
NetBackup status code: 2093 ..................................................
NetBackup status code: 2094 ..................................................
NetBackup status code: 2095 ..................................................
NetBackup status code: 2096 ..................................................
NetBackup status code: 2097 ..................................................
NetBackup status code: 2098 ..................................................
NetBackup status code: 2099 ..................................................
NetBackup status code: 2100 ..................................................
NetBackup status code: 2101 ..................................................
NetBackup status code: 2102 ..................................................
NetBackup status code: 2103 ..................................................
NetBackup status code: 2104 ..................................................
NetBackup status code: 2105 ..................................................
NetBackup status code: 2106 ..................................................
357
358
358
358
359
359
359
360
360
360
361
361
361
362
362
363
363
363
364
364
364
365
365
365
365
366
366
367
368
368
369
369
369
370
370
370
371
371
371
372
372
372
372
20
Contents
NetBackup status code: 2107 ..................................................
NetBackup status code: 2108 ..................................................
NetBackup status code: 2109 ..................................................
NetBackup status code: 2110 ..................................................
NetBackup status code: 2111 ..................................................
NetBackup status code: 2112 .................................................
NetBackup status code: 2113 ..................................................
NetBackup status code: 2504 ..................................................
NetBackup status code: 2517 ..................................................
NetBackup status code: 2521 ..................................................
NetBackup status code: 2522 ..................................................
NetBackup status code: 2523 ..................................................
NetBackup status code: 2524 ..................................................
NetBackup status code: 2525 ..................................................
NetBackup status code: 2800 ..................................................
NetBackup status code: 2801 ..................................................
NetBackup status code: 2802 ..................................................
NetBackup status code: 2803 ..................................................
NetBackup status code: 2804 ..................................................
NetBackup status code: 2805 ..................................................
NetBackup status code: 2806 ..................................................
NetBackup status code: 2807 ..................................................
NetBackup status code: 2808 ..................................................
NetBackup status code: 2809 ..................................................
NetBackup status code: 2810 ..................................................
NetBackup status code: 2811 ..................................................
NetBackup status code: 2812 ..................................................
NetBackup status code: 2813 ..................................................
NetBackup status code: 2814 ..................................................
NetBackup status code: 2815 ..................................................
NetBackup status code: 2816 ..................................................
NetBackup status code: 2817 ..................................................
NetBackup status code: 2818 ..................................................
NetBackup status code: 2819 ..................................................
NetBackup status code: 2820 ..................................................
NetBackup status code: 2821 ..................................................
NetBackup status code: 2826 ..................................................
NetBackup status code: 2827 ..................................................
NetBackup status code: 2828 ..................................................
NetBackup status code: 2829 ..................................................
NetBackup status code: 2830 ..................................................
NetBackup status code: 2831 ..................................................
NetBackup status code: 2832 ..................................................
373
374
374
374
375
375
375
376
376
376
377
377
377
378
378
379
380
380
382
383
384
384
385
385
386
387
388
389
389
390
390
391
391
392
392
394
394
395
395
395
396
396
396
21
Contents
NetBackup status code: 2833 ..................................................
NetBackup status code: 2834 ..................................................
NetBackup status code: 2835 ..................................................
NetBackup status code: 2836 ..................................................
NetBackup status code: 2837 ..................................................
NetBackup status code: 2838 ..................................................
NetBackup status code: 2839 ..................................................
NetBackup status code: 2840 ..................................................
NetBackup status code: 2841 ..................................................
NetBackup status code: 2842 ..................................................
NetBackup status code: 2843 ..................................................
NetBackup status code: 2844 ..................................................
NetBackup status code: 2845 ..................................................
NetBackup status code: 2846 ..................................................
NetBackup status code: 2847 ..................................................
NetBackup status code: 2848 ..................................................
NetBackup status code: 2849 ..................................................
NetBackup status code: 2850 ..................................................
NetBackup status code: 2864 ..................................................
NetBackup status code: 2865 ..................................................
NetBackup status code: 2866 ..................................................
NetBackup status code: 4200 ..................................................
NetBackup status code: 4201 ..................................................
NetBackup status code: 4202 ..................................................
NetBackup status code: 4203 ..................................................
NetBackup status code: 4204 ..................................................
NetBackup status code: 4205 ..................................................
NetBackup status code: 4206 ..................................................
NetBackup status code: 4207 ..................................................
NetBackup status code: 4208 ..................................................
NetBackup status code: 4209 ..................................................
NetBackup status code: 4210 ..................................................
NetBackup status code: 4211 ..................................................
NetBackup status code: 4212 ..................................................
NetBackup status code: 4213 ..................................................
NetBackup status code: 4214 ..................................................
NetBackup status code: 4215 ..................................................
NetBackup status code: 4216 ..................................................
NetBackup status code: 4217 ..................................................
NetBackup status code: 4218 ..................................................
NetBackup status code: 4219 ..................................................
NetBackup status code: 4220 ..................................................
NetBackup status code: 4221 ..................................................
397
397
397
398
398
398
399
399
399
400
400
400
401
401
401
401
402
402
403
403
403
404
404
405
405
405
406
406
406
407
407
408
408
408
409
409
410
410
410
410
411
411
412
22
Contents
NetBackup status code: 4222 ..................................................
NetBackup status code: 4223 ..................................................
NetBackup status code: 4224 ..................................................
NetBackup status code: 4225 ..................................................
NetBackup status code: 4226 ..................................................
NetBackup status code: 4227 ..................................................
NetBackup status code: 4228 ..................................................
NetBackup status code: 4229 ..................................................
NetBackup status code: 4230 ..................................................
NetBackup status code: 4231 ..................................................
NetBackup status code: 4232 ..................................................
NetBackup status code: 4233 ..................................................
NetBackup status code: 4234 ..................................................
NetBackup status code: 4235 ..................................................
NetBackup status code: 4236 ..................................................
NetBackup status code: 4237 ..................................................
NetBackup status code: 4238 ..................................................
NetBackup status code: 4239 ..................................................
NetBackup status code: 4240 ..................................................
NetBackup status code: 4243 ..................................................
NetBackup status code: 4245 ..................................................
NetBackup status code: 4246 ..................................................
NetBackup status code: 4247 ..................................................
NetBackup status code: 4248 ..................................................
NetBackup status code: 4249 ..................................................
NetBackup status code: 4250 ..................................................
NetBackup status code: 4251 ..................................................
NetBackup status code: 4252 ..................................................
NetBackup status code: 4253 ..................................................
NetBackup status code: 4254 ..................................................
NetBackup status code: 4255 ..................................................
NetBackup status code: 4256 ..................................................
NetBackup status code: 4257 ..................................................
NetBackup status code: 4258 ..................................................
NetBackup status code: 4259 ..................................................
NetBackup status code: 4260 ..................................................
NetBackup status code: 4261 ..................................................
NetBackup status code: 4262 ..................................................
NetBackup status code: 4263 ..................................................
NetBackup status code: 4264 ..................................................
NetBackup status code: 4265 ..................................................
NetBackup status code: 4266 ..................................................
NetBackup status code: 4267 ..................................................
412
412
412
413
413
413
414
414
414
415
415
415
416
416
416
416
417
417
417
418
418
418
419
419
419
419
420
420
420
420
421
421
422
422
422
422
423
423
423
424
424
424
425
23
Contents
NetBackup status code: 4268 ..................................................
NetBackup status code: 4269 ..................................................
NetBackup status code: 4270 ..................................................
NetBackup status code: 4271 ..................................................
NetBackup status code: 4272 ..................................................
NetBackup status code: 4273 ..................................................
NetBackup status code: 4274 ..................................................
NetBackup status code: 4275 ..................................................
NetBackup status code: 4276 ..................................................
NetBackup status code: 4277 ..................................................
NetBackup status code: 4278 ..................................................
NetBackup status code: 4279 ..................................................
NetBackup status code: 4280 ..................................................
NetBackup status code: 4281 ..................................................
NetBackup status code: 4282 ..................................................
NetBackup status code: 4283 ..................................................
NetBackup status code: 4287 ..................................................
NetBackup status code: 4290 ..................................................
NetBackup status code: 4293 ..................................................
NetBackup status code: 5400 ..................................................
NetBackup status code: 5401 ..................................................
NetBackup status code: 5402 ..................................................
NetBackup status code: 5403 ..................................................
NetBackup status code: 5404 ..................................................
NetBackup status code: 5405 ..................................................
NetBackup status code: 5406 ..................................................
NetBackup status code: 5407 ..................................................
NetBackup status code: 5408 ..................................................
NetBackup status code: 5409 ..................................................
NetBackup status code: 5410 ..................................................
NetBackup status code: 5411 ..................................................
NetBackup status code: 5412 ..................................................
NetBackup status code: 5413 ..................................................
NetBackup status code: 5414 ..................................................
NetBackup status code: 5415 ..................................................
NetBackup status code: 5416 ..................................................
NetBackup status code: 5417 ..................................................
NetBackup status code: 5418 ..................................................
NetBackup status code: 5419 ..................................................
NetBackup status code: 5420 ..................................................
NetBackup status code: 5421 ..................................................
NetBackup status code: 5422 ..................................................
NetBackup status code: 5423 ..................................................
425
425
426
426
426
426
427
427
427
428
428
428
429
429
429
429
430
431
431
431
431
432
432
432
433
433
433
434
434
434
434
435
435
435
436
436
436
436
437
437
437
438
438
24
Contents
NetBackup status code: 5424 ..................................................
NetBackup status code: 5425 ..................................................
NetBackup status code: 5426 ..................................................
NetBackup status code: 5427 ..................................................
NetBackup status code: 5428 ..................................................
NetBackup status code: 5429 ..................................................
NetBackup status code: 5430 ..................................................
NetBackup status code: 5431 ..................................................
NetBackup status code: 5432 ..................................................
NetBackup status code: 5433 ..................................................
NetBackup status code: 5434 ..................................................
NetBackup status code: 5435 ..................................................
NetBackup status code: 5436 ..................................................
NetBackup status code: 5437 ..................................................
NetBackup status code: 5438 ..................................................
NetBackup status code: 5439 ..................................................
NetBackup status code: 5440 ..................................................
NetBackup status code: 5441 ..................................................
NetBackup status code: 5442 ..................................................
NetBackup status code: 5443 ..................................................
NetBackup status code: 5444 ..................................................
NetBackup status code: 5445 ..................................................
NetBackup status code: 5446 ..................................................
NetBackup status code: 5447 ..................................................
NetBackup status code: 5448 ..................................................
NetBackup status code: 5449 ..................................................
NetBackup status code: 5450 ..................................................
NetBackup status code: 5451 ..................................................
NetBackup status code: 5452 ..................................................
NetBackup status code: 5500 ..................................................
NetBackup status code: 5501 ..................................................
NetBackup status code: 5502 ..................................................
NetBackup status code: 5503 ..................................................
NetBackup status code: 5504 ..................................................
NetBackup status code: 5505 ..................................................
NetBackup status code: 5506 ..................................................
NetBackup status code: 5507 ..................................................
NetBackup status code: 5508 ..................................................
NetBackup status code: 5626 ..................................................
NetBackup status code: 5761 ..................................................
NetBackup status code: 5762 ..................................................
NetBackup status code: 5763 ..................................................
NetBackup status code: 5764 ..................................................
438
439
439
440
440
440
441
441
441
442
442
442
443
443
443
444
444
444
445
445
445
445
446
446
446
446
447
447
447
448
448
448
448
449
449
449
450
450
450
451
451
452
452
25
Contents
NetBackup status code: 5765 ..................................................
NetBackup status code: 5766 ..................................................
NetBackup status code: 5767 ..................................................
NetBackup status code: 5768 ..................................................
NetBackup status code: 5769 ..................................................
NetBackup status code: 5770 ..................................................
NetBackup status code: 5771 ..................................................
NetBackup status code: 5772 ..................................................
NetBackup status code: 5773 ..................................................
NetBackup status code: 5774 ..................................................
NetBackup status code: 5775 ..................................................
NetBackup status code: 5776 ..................................................
NetBackup status code: 5777 ..................................................
NetBackup status code: 5778 ..................................................
NetBackup status code: 5779 ..................................................
NetBackup status code: 5780 ..................................................
NetBackup status code: 5781 ..................................................
NetBackup status code: 5782 ..................................................
NetBackup status code: 5783 ..................................................
NetBackup status code: 5784 ..................................................
NetBackup status code: 5786 ..................................................
NetBackup status code: 5787 ..................................................
NetBackup status code: 5788 ..................................................
NetBackup status code: 5789 ..................................................
NetBackup status code: 5790 ..................................................
NetBackup status code: 5794 ..................................................
NetBackup status code: 5796 ..................................................
NetBackup status code: 5798 ..................................................
NetBackup status code: 5799 ..................................................
NetBackup status code: 5800 ..................................................
NetBackup status code: 5801 ..................................................
NetBackup status code: 5803 ..................................................
NetBackup status code: 5804 ..................................................
NetBackup status code: 5805 ..................................................
NetBackup status code: 5806 ..................................................
NetBackup status code: 5807 ..................................................
NetBackup status code: 5808 ..................................................
NetBackup status code: 5809 ..................................................
NetBackup status code: 5811 ..................................................
NetBackup status code: 5812 ..................................................
NetBackup status code: 5813 ..................................................
NetBackup status code: 5814 ..................................................
NetBackup status code: 5815 ..................................................
452
452
453
453
453
453
454
454
454
454
455
455
455
455
456
456
456
456
457
457
457
457
457
458
458
458
458
459
459
459
459
460
460
460
460
461
461
461
461
462
462
462
462
26
Contents
NetBackup status code: 5816 ..................................................
NetBackup status code: 5817 ..................................................
NetBackup status code: 5819 ..................................................
NetBackup status code: 5820 ..................................................
NetBackup status code: 5821 ..................................................
NetBackup status code: 5902 ..................................................
NetBackup status code: 5903 ..................................................
NetBackup status code: 5904 ..................................................
NetBackup status code: 5905 ..................................................
NetBackup status code: 5906 ..................................................
NetBackup status code: 5907 ..................................................
NetBackup status code: 5908 ..................................................
NetBackup status code: 5909 ..................................................
NetBackup status code: 5910 ..................................................
NetBackup status code: 5913 ..................................................
NetBackup status code: 5914 ..................................................
NetBackup status code: 5915 ..................................................
NetBackup status code: 5916 ..................................................
NetBackup status code: 5917 ..................................................
NetBackup status code: 5918 ..................................................
NetBackup status code: 5919 ..................................................
NetBackup status code: 5920 ..................................................
NetBackup status code: 5921 ..................................................
NetBackup status code: 5922 ..................................................
NetBackup status code: 5925 ..................................................
NetBackup status code: 5926 ..................................................
NetBackup status code: 5927 ..................................................
NetBackup status code: 5929 ..................................................
NetBackup status code: 5930 ..................................................
NetBackup status code: 5931 ..................................................
NetBackup status code: 5932 ..................................................
NetBackup status code: 5933 ..................................................
NetBackup status code: 5934 ..................................................
NetBackup status code: 5936 ..................................................
NetBackup status code: 5938 ..................................................
NetBackup status code: 5939 ..................................................
NetBackup status code: 5940 ..................................................
NetBackup status code: 5941 ..................................................
NetBackup status code: 5942 ..................................................
NetBackup status code: 5943 ..................................................
NetBackup status code: 5944 ..................................................
NetBackup status code: 5945 ..................................................
NetBackup status code: 5946 ..................................................
463
463
463
463
463
464
464
464
465
465
465
465
466
466
466
466
467
467
467
468
468
468
468
469
469
469
469
470
470
471
471
471
471
472
472
472
472
473
473
473
474
474
474
27
Contents
NetBackup status code: 5947 ..................................................
NetBackup status code: 5948 ..................................................
NetBackup status code: 5949 ..................................................
NetBackup status code: 5950 ..................................................
NetBackup status code: 5953 ..................................................
NetBackup status code: 5954 ..................................................
NetBackup status code: 5955 ..................................................
NetBackup status code: 5956 ..................................................
NetBackup status code: 5957 ..................................................
NetBackup status code: 5958 ..................................................
NetBackup status code: 5959 ..................................................
NetBackup status code: 5960 ..................................................
NetBackup status code: 5962 ..................................................
NetBackup status code: 5963 ..................................................
NetBackup status code: 5964 ..................................................
NetBackup status code: 5965 ..................................................
NetBackup status code: 5966 ..................................................
NetBackup status code: 5967 ..................................................
NetBackup status code: 5968 ..................................................
NetBackup status code: 5969 ..................................................
NetBackup status code: 5970 ..................................................
NetBackup status code: 5971 ..................................................
NetBackup status code: 5972 ..................................................
NetBackup status code: 5973 ..................................................
NetBackup status code: 5974 ..................................................
NetBackup status code: 5978 ..................................................
NetBackup status code: 5979 ..................................................
NetBackup status code: 5980 ..................................................
NetBackup status code: 5982 ..................................................
NetBackup status code: 5983 ..................................................
NetBackup status code: 5986 ..................................................
NetBackup status code: 5987 ..................................................
NetBackup status code: 5988 ..................................................
NetBackup status code: 5989 ..................................................
NetBackup status code: 6000 ..................................................
NetBackup status code: 6530 ..................................................
NetBackup status code: 6531 ..................................................
NetBackup status code: 6600 ..................................................
NetBackup status code: 6601 ..................................................
NetBackup status code: 6602 ..................................................
NetBackup status code: 6603 ..................................................
NetBackup status code: 6604 ..................................................
NetBackup status code: 6605 ..................................................
474
475
475
475
475
476
476
476
477
477
477
477
478
478
479
479
479
479
480
480
480
481
481
481
482
482
483
483
483
484
485
485
489
489
490
490
490
491
491
492
492
492
492
28
Contents
NetBackup status code: 6606 ..................................................
NetBackup status code: 6607 ..................................................
NetBackup status code: 6608 ..................................................
NetBackup status code: 6609 ..................................................
NetBackup status code: 6610 ..................................................
NetBackup status code: 6612 ..................................................
NetBackup status code: 6614 ..................................................
NetBackup status code: 6616 ..................................................
NetBackup status code: 6617 ..................................................
NetBackup status code: 6618 ..................................................
NetBackup status code: 6619 ..................................................
NetBackup status code: 6620 ..................................................
NetBackup status code: 6621 ..................................................
NetBackup status code: 6622 ..................................................
NetBackup status code: 6623 ..................................................
NetBackup status code: 6625 ..................................................
NetBackup status code: 6626 ..................................................
NetBackup status code: 6628 ..................................................
NetBackup status code: 6629 ..................................................
NetBackup status code: 6630 ..................................................
NetBackup status code: 6631 ..................................................
NetBackup status code: 6633 ..................................................
NetBackup status code: 6634 ..................................................
NetBackup status code: 6635 ..................................................
NetBackup status code: 6640 ..................................................
NetBackup status code: 6641 ..................................................
NetBackup status code: 6642 ..................................................
NetBackup status code: 6643 ..................................................
NetBackup status code: 6644 ..................................................
NetBackup status code: 6646 ..................................................
NetBackup status code: 6647 ..................................................
NetBackup status code: 6649 ..................................................
NetBackup status code: 6650 ..................................................
NetBackup status code: 6652 ..................................................
NetBackup status code: 6653 ..................................................
NetBackup status code: 6654 ..................................................
NetBackup status code: 6655 ..................................................
NetBackup status code: 7600 ..................................................
NetBackup status code: 7601 ..................................................
NetBackup status code: 7603 ..................................................
NetBackup status code: 7604 ..................................................
NetBackup status code: 7607 ..................................................
NetBackup status code: 7609 ..................................................
493
493
493
494
494
494
495
495
495
495
496
496
496
496
497
497
497
498
498
498
499
499
499
499
500
500
500
500
501
501
501
501
502
502
502
503
503
503
503
504
504
504
504
29
Contents
NetBackup status code: 7610 ..................................................
NetBackup status code: 7611 ..................................................
NetBackup status code: 7612 ..................................................
NetBackup status code: 7613 ..................................................
NetBackup status code: 7614 ..................................................
NetBackup status code: 7617 ..................................................
NetBackup status code: 7618 ..................................................
NetBackup status code: 7619 ..................................................
NetBackup status code: 7622 ..................................................
NetBackup status code: 7623 ..................................................
NetBackup status code: 7624 ..................................................
NetBackup status code: 7625 ..................................................
NetBackup status code: 7627 ..................................................
NetBackup status code: 7628 ..................................................
NetBackup status code: 7631 ..................................................
NetBackup status code: 7632 ..................................................
NetBackup status code: 7633 ..................................................
NetBackup status code: 7634 ..................................................
NetBackup status code: 7635 ..................................................
NetBackup status code: 7636 ..................................................
NetBackup status code: 7637 ..................................................
NetBackup status code: 7638 ..................................................
NetBackup status code: 7639 ..................................................
NetBackup status code: 7640 ..................................................
NetBackup status code: 7641 ..................................................
NetBackup status code: 7642 ..................................................
NetBackup status code: 7643 ..................................................
NetBackup status code: 7645 ..................................................
NetBackup status code: 7647 ..................................................
NetBackup status code: 7648 ..................................................
NetBackup status code: 7649 ..................................................
NetBackup status code: 7650 ..................................................
NetBackup status code: 7651 ..................................................
NetBackup status code: 7652 ..................................................
NetBackup status code: 7653 ..................................................
NetBackup status code: 7654 ..................................................
NetBackup status code: 7655 ..................................................
NetBackup status code: 7656 ..................................................
NetBackup status code: 7657 ..................................................
NetBackup status code: 7658 ..................................................
NetBackup status code: 7659 ..................................................
NetBackup status code: 7660 ..................................................
NetBackup status code: 8000 ..................................................
505
505
505
505
505
506
506
506
506
507
507
507
508
508
509
509
509
509
510
510
510
511
511
511
512
512
512
513
513
513
513
514
514
514
515
516
516
517
517
518
518
518
519
30
Contents
NetBackup status code: 8500 ..................................................
NetBackup status code: 8504 ..................................................
NetBackup status code: 8505 ..................................................
NetBackup status code: 8506 ..................................................
NetBackup status code: 8507 ..................................................
NetBackup status code: 8508 ..................................................
NetBackup status code: 8509 ..................................................
NetBackup status code: 8510 ..................................................
NetBackup status code: 8617 ..................................................
NetBackup status code: 8618 ..................................................
NetBackup status code: 8619 ..................................................
NetBackup status code: 8620 ..................................................
NetBackup status code: 8621 ..................................................
NetBackup status code: 8622 ..................................................
NetBackup status code: 8623 ..................................................
NetBackup status code: 8625 ..................................................
NetBackup status code: 8700 ..................................................
NetBackup status code: 8701 ..................................................
NetBackup status code: 8702 ..................................................
NetBackup status code: 8703 ..................................................
NetBackup status code: 8704 ..................................................
NetBackup status code: 8706 ..................................................
NetBackup status code: 8707 ..................................................
NetBackup status code: 8708 ..................................................
NetBackup status code: 8709 ..................................................
NetBackup status code: 8710 ..................................................
NetBackup status code: 8711 ..................................................
NetBackup status code: 8712 ..................................................
NetBackup status code: 8713 ..................................................
NetBackup status code: 8714 ..................................................
NetBackup status code: 8715 ..................................................
NetBackup status code: 8716 ..................................................
NetBackup status code: 8717 ..................................................
NetBackup status code: 8718 ..................................................
NetBackup status code: 8719 ..................................................
NetBackup status code: 8720 ..................................................
NetBackup status code: 8722 .................................................
NetBackup status code: 8723 ..................................................
NetBackup status code: 8724 ..................................................
NetBackup status code: 8800 ..................................................
NetBackup status code: 8900 ..................................................
NetBackup status code: 8901 ..................................................
NetBackup status code: 8902 ..................................................
519
519
519
520
520
520
521
521
521
521
522
522
522
523
523
523
524
524
525
525
525
526
526
526
526
527
527
527
527
528
528
528
528
529
529
529
530
530
530
530
531
531
531
31
Contents
NetBackup status code: 9101 ..................................................
NetBackup status code: 9102 ..................................................
NetBackup status code: 9103 ..................................................
NetBackup status code: 9300 ..................................................
NetBackup status code: 9301 ..................................................
NetBackup status code: 9302 ..................................................
NetBackup status code: 9303 ..................................................
NetBackup status code: 9304 ..................................................
NetBackup status code: 9305 ..................................................
NetBackup status code: 9306 ..................................................
NetBackup status code: 9307 ..................................................
NetBackup status code: 9308 ..................................................
NetBackup status code: 9309 ..................................................
NetBackup KMS status codes .......................................................
NetBackup KMS status code: 1 ...............................................
NetBackup KMS status code: 2 ...............................................
NetBackup KMS status code: 3 ...............................................
NetBackup KMS status code: 4 ...............................................
NetBackup KMS status code: 5 ...............................................
NetBackup KMS status code: 6 ...............................................
NetBackup KMS status code: 7 ...............................................
NetBackup KMS status code: 8 ...............................................
NetBackup KMS status code: 9 ...............................................
NetBackup KMS status code: 10 ..............................................
NetBackup KMS status code: 11 ..............................................
NetBackup KMS status code: 12 ..............................................
NetBackup KMS status code: 13 ..............................................
NetBackup KMS status code: 14 ..............................................
NetBackup KMS status code: 15 ..............................................
NetBackup KMS status code: 16 ..............................................
NetBackup KMS status code: 17 ..............................................
NetBackup KMS status code: 18 ..............................................
NetBackup KMS status code: 19 ..............................................
NetBackup KMS status code: 20 ..............................................
NetBackup KMS status code: 21 ..............................................
NetBackup KMS status code: 22 ..............................................
NetBackup KMS status code: 23 ..............................................
NetBackup KMS status code: 24 ..............................................
NetBackup KMS status code: 25 ..............................................
NetBackup KMS status code: 26 ..............................................
NetBackup KMS status code: 27 ..............................................
NetBackup KMS status code: 28 ..............................................
NetBackup KMS status code: 29 ..............................................
532
532
532
533
533
534
534
535
535
536
536
537
537
538
538
538
539
539
539
539
539
540
540
540
540
540
540
541
541
541
541
541
542
542
542
542
542
542
543
543
543
543
543
32
Contents
NetBackup KMS status code: 30 ..............................................
NetBackup KMS status code: 31 ..............................................
NetBackup KMS status code: 32 ..............................................
NetBackup KMS status code: 33 ..............................................
NetBackup KMS status code: 34 ..............................................
NetBackup KMS status code: 35 ..............................................
NetBackup KMS status code: 36 ..............................................
NetBackup KMS status code: 37 ..............................................
NetBackup KMS status code: 38 ..............................................
NetBackup KMS status code: 39 ..............................................
NetBackup KMS status code: 40 ..............................................
NetBackup KMS status code: 41 ..............................................
NetBackup KMS status code: 42 ..............................................
NetBackup KMS status code: 44 ..............................................
NetBackup KMS status code: 45 ..............................................
NetBackup KMS status code: 46 ..............................................
NetBackup KMS status code: 47 ..............................................
NetBackup KMS status code: 48 ..............................................
NetBackup KMS status code: 49 ..............................................
NetBackup KMS status code: 50 ..............................................
NetBackup KMS status code: 51 ..............................................
NetBackup KMS status code: 52 ..............................................
NetBackup KMS status code: 53 ..............................................
NetBackup KMS status code: 54 ..............................................
NetBackup KMS status code: 55 ..............................................
NetBackup KMS status code: 56 ..............................................
NetBackup KMS status code: 57 ..............................................
NetBackup KMS status code: 58 ..............................................
NetBackup KMS status code: 59 ..............................................
NetBackup KMS status code: 60 ..............................................
NetBackup KMS status code: 61 ..............................................
NetBackup KMS status code: 62 ..............................................
NetBackup KMS status code: 63 ..............................................
NetBackup KMS status code: 1287 ..........................................
Chapter 2
543
544
544
544
544
544
544
545
545
545
545
545
546
546
546
546
546
547
547
547
547
547
548
548
548
548
548
548
549
549
549
550
550
550
Media Manager status codes ....................................... 551
Media Manager status codes ........................................................
Media Manager status code 1 .................................................
Media Manager status code 2 .................................................
Media Manager status code 3 .................................................
Media Manager status code 4 .................................................
Media Manager status code 5 .................................................
551
551
551
552
552
553
33
Contents
Media Manager status code 6 .................................................
Media Manager status code 7 .................................................
Media Manager status code 8 .................................................
Media Manager status code 9 .................................................
Media Manager status code 10 ................................................
Media Manager status code 11 ................................................
Media Manager status code 12 ................................................
Media Manager status code 13 ................................................
Media Manager status code 14 ................................................
Media Manager status code 15 ................................................
Media Manager status code 16 ................................................
Media Manager status code 18 ................................................
Media Manager status code 19 ................................................
Media Manager status code 20 ................................................
Media Manager status code 21 ................................................
Media Manager status code 22 ................................................
Media Manager status code 23 ................................................
Media Manager status code 25 ................................................
Media Manager status code 26 ................................................
Media Manager status code 27 ................................................
Media Manager status code 28 ................................................
Media Manager status code 32 ................................................
Media Manager status code 34 ................................................
Media Manager status code 35 ................................................
Media Manager status code 36 ................................................
Media Manager status code 37 ................................................
Media Manager status code 39 ................................................
Media Manager status code 40 ................................................
Media Manager status code 41 ................................................
Media Manager status code 42 ................................................
Media Manager status code 43 ................................................
Media Manager status code 44 ................................................
Media Manager status code 45 ................................................
Media Manager status code 46 ................................................
Media Manager status code 47 ................................................
Media Manager status code 48 ................................................
Media Manager status code 49 ................................................
Media Manager status code 50 ................................................
Media Manager status code 51 ................................................
Media Manager status code 52 ................................................
Media Manager status code 53 ................................................
Media Manager status code 54 ................................................
Media Manager status code 55 ................................................
553
553
553
554
554
555
555
556
556
556
557
557
558
558
558
559
559
559
559
560
560
561
561
561
562
562
563
563
563
564
564
565
566
566
566
567
567
567
568
568
569
569
569
34
Contents
Media Manager status code 57 ................................................
Media Manager status code 58 ................................................
Media Manager status code 59 ................................................
Media Manager status code 60 ................................................
Media Manager status code 61 ................................................
Media Manager status code 62 ................................................
Media Manager status code 63 ................................................
Media Manager status code 64 ................................................
Media Manager status code 65 ................................................
Media Manager status code 67 ................................................
Media Manager status code 68 ................................................
Media Manager status code 69 ................................................
Media Manager status code 70 ................................................
Media Manager status code 71 ................................................
Media Manager status code 72 ................................................
Media Manager status code 73 ................................................
Media Manager status code 74 ................................................
Media Manager status code 75 ................................................
Media Manager status code 76 ................................................
Media Manager status code 78 ................................................
Media Manager status code 79 ................................................
Media Manager status code 80 ................................................
Media Manager status code 81 ................................................
Media Manager status code 82 ................................................
Media Manager status code 83 ................................................
Media Manager status code 84 ................................................
Media Manager status code 85 ................................................
Media Manager status code 86 ................................................
Media Manager status code 87 ................................................
Media Manager status code 88 ................................................
Media Manager status code 89 ................................................
Media Manager status code 90 ................................................
Media Manager status code 92 ................................................
Media Manager status code 93 ................................................
Media Manager status code 94 ................................................
Media Manager status code 95 ................................................
Media Manager status code 96 ................................................
Media Manager status code 97 ................................................
Media Manager status code 101 ..............................................
Media Manager status code 102 ..............................................
Media Manager status code 104 ..............................................
Media Manager status code 105 ..............................................
Media Manager status code 109 ..............................................
570
570
571
571
572
572
572
572
573
573
574
574
575
576
576
577
577
577
578
578
579
579
579
580
581
581
581
582
582
582
583
583
584
584
584
585
585
586
587
587
588
588
588
35
Contents
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Manager status code 110 ..............................................
Manager status code 111 ..............................................
Manager status code 112 ..............................................
Manager status code 113 ..............................................
Manager status code 114 ..............................................
Manager status code 115 ..............................................
Manager status code 116 ..............................................
Manager status code 117 ..............................................
Manager status code 118 ..............................................
Manager status code 119 ..............................................
Manager status code 121 ..............................................
Manager status code 122 ..............................................
Manager status code 126 ..............................................
Manager status code 127 ..............................................
Manager status code 129 ..............................................
Manager status code 130 ..............................................
Manager status code 131 ..............................................
Manager status code 132 ..............................................
Manager status code 133 ..............................................
Manager status code 134 ..............................................
Manager status code 135 ..............................................
Manager status code 136 ..............................................
Manager status code 137 ..............................................
Manager status code 138 ..............................................
Manager status code 139 ..............................................
Manager status code 140 ..............................................
Manager status code 141 ..............................................
Manager status code 142 ..............................................
Manager status code 143 ..............................................
Manager status code 144 ..............................................
Manager status code 145 ..............................................
Manager status code 146 ..............................................
Manager status code 147 ..............................................
Manager status code 148 ..............................................
Manager status code 149 ..............................................
Manager status code 150 ..............................................
Manager status code 152 ..............................................
Manager status code 153 ..............................................
Manager status code 155 ..............................................
Manager status code 160 ..............................................
Manager status code 162 ..............................................
Manager status code 163 ..............................................
Manager status code 164 ..............................................
589
590
590
590
590
591
591
592
592
592
593
593
593
594
594
595
595
596
596
597
597
597
598
598
598
599
599
599
600
600
600
600
601
601
601
602
602
603
603
603
604
604
604
36
Contents
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Chapter 3
Manager
Manager
Manager
Manager
Manager
Manager
Manager
Manager
Manager
Manager
Manager
Manager
Manager
Manager
Manager
Manager
Manager
Manager
Manager
Manager
Manager
Manager
Manager
Manager
Manager
Manager
Manager
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
165
166
167
168
169
171
172
173
175
176
177
181
182
185
186
187
188
189
190
191
192
193
194
195
196
198
199
..............................................
..............................................
..............................................
..............................................
..............................................
..............................................
..............................................
..............................................
..............................................
..............................................
..............................................
..............................................
..............................................
..............................................
..............................................
..............................................
..............................................
..............................................
..............................................
..............................................
..............................................
..............................................
..............................................
..............................................
..............................................
..............................................
..............................................
605
605
605
606
606
606
606
607
607
607
607
608
609
609
609
610
611
612
612
613
613
613
613
614
614
614
615
Device configuration status codes .............................. 616
Device configuration status codes ..................................................
Device configuration status code 0 ...........................................
Device configuration status code 1 ...........................................
Device configuration status code 2 ...........................................
Device configuration status code 3 ...........................................
Device configuration status code 7 ...........................................
Device configuration status code 8 ...........................................
Device configuration status code 9 ...........................................
Device configuration status code 10 .........................................
Device configuration status code 11 ..........................................
Device configuration status code 13 .........................................
Device configuration status code 14 .........................................
Device configuration status code 15 .........................................
616
616
616
617
617
618
618
618
618
619
619
619
620
37
Contents
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
configuration
configuration
configuration
configuration
configuration
configuration
configuration
configuration
configuration
configuration
configuration
configuration
configuration
configuration
configuration
configuration
configuration
configuration
configuration
configuration
configuration
configuration
configuration
configuration
configuration
configuration
configuration
configuration
configuration
configuration
configuration
configuration
configuration
configuration
configuration
configuration
configuration
configuration
configuration
configuration
configuration
configuration
configuration
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
16
17
18
19
21
22
24
25
27
28
29
30
31
33
34
35
36
37
38
39
40
41
42
44
48
49
51
52
53
55
56
57
58
59
60
61
62
63
64
65
66
67
68
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
620
621
621
621
622
622
622
623
623
623
624
624
624
625
625
625
626
626
626
626
627
627
627
627
628
629
629
629
630
630
630
631
631
631
632
632
632
633
633
633
633
633
634
38
Contents
Device configuration status code 69 .........................................
Device configuration status code 70 .........................................
Device configuration status code 71 .........................................
Device configuration status code 72 .........................................
Device configuration status code 73 .........................................
Device configuration status code 74 .........................................
Device configuration status code 75 .........................................
Device configuration status code 76 .........................................
Device configuration status code 77 .........................................
Device configuration status code 78 .........................................
Device configuration status code 79 .........................................
Device configuration status code 81 .........................................
Device configuration status code 82 .........................................
Device configuration status code 83 .........................................
Device configuration status code 84 .........................................
Device configuration status code 85 .........................................
Device configuration status code 86 .........................................
Device configuration status code 87 .........................................
Device configuration status code 88 .........................................
Device configuration status code 89 .........................................
Device configuration status code 90 .........................................
Device configuration status code 91 .........................................
Device configuration status code 92 .........................................
Device configuration status code 93 .........................................
Device configuration status code 95 .........................................
Device configuration status code 96 .........................................
Device configuration status code 97 .........................................
Device configuration status code 98 .........................................
Device configuration status code 99 .........................................
Device configuration status code 100 ........................................
Device configuration status code 101 ........................................
Chapter 4
Device management status codes
634
634
635
635
635
635
636
636
636
637
637
637
638
638
638
639
639
639
640
640
640
641
641
641
642
642
642
643
643
643
643
............................. 644
Device management status codes ..................................................
Device management status code 1 ...........................................
Device management status code 2 ...........................................
Device management status code 3 ...........................................
Device management status code 4 ...........................................
Device management status code 5 ...........................................
Device management status code 6 ...........................................
Device management status code 7 ...........................................
Device management status code 8 ...........................................
644
644
644
645
645
646
646
646
647
39
Contents
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
management
management
management
management
management
management
management
management
management
management
management
management
management
management
management
management
management
management
management
management
management
management
management
management
management
management
management
management
management
management
management
management
management
management
management
management
management
management
management
management
management
management
management
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
10
12
13
14
15
16
17
19
20
21
22
23
24
25
26
27
28
30
32
33
35
36
37
38
39
40
41
42
44
46
47
48
49
50
52
53
55
56
58
59
60
61
62
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
647
648
648
648
649
649
649
650
650
650
650
651
651
652
652
652
653
653
653
654
654
655
655
655
656
656
656
657
657
657
658
658
659
659
659
660
660
660
660
660
661
661
662
40
Contents
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Device
Chapter 5
management
management
management
management
management
management
management
management
management
management
management
management
management
management
management
management
management
management
management
management
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
status
Robotic status codes
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
code
63
64
65
66
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
662
662
662
663
663
663
664
664
664
664
665
665
665
666
666
666
667
667
667
667
...................................................... 668
Robotic status codes ...................................................................
Robotic status code 200 .........................................................
Robotic status code 201 .........................................................
Robotic status code 202 .........................................................
Robotic status code 203 .........................................................
Robotic status code 204 .........................................................
Robotic status code 205 .........................................................
Robotic status code 206 .........................................................
Robotic status code 207 .........................................................
Robotic status code 208 .........................................................
Robotic status code 209 .........................................................
Robotic status code 210 .........................................................
Robotic status code 211 .........................................................
Robotic status code 212 .........................................................
Robotic status code 213 .........................................................
Robotic status code 214 .........................................................
Robotic status code 215 .........................................................
Robotic status code 216 .........................................................
Robotic status code 217 .........................................................
Robotic status code 218 .........................................................
668
668
668
669
670
670
670
671
671
671
672
672
673
673
674
674
674
675
675
675
41
Contents
Robotic status code 219 .........................................................
Robotic status code 220 .........................................................
Robotic status code 221 .........................................................
Robotic status code 222 .........................................................
Robotic status code 223 .........................................................
Robotic status code 224 .........................................................
Robotic status code 225 .........................................................
Robotic status code 226 .........................................................
Robotic status code 228 .........................................................
Robotic status code 229 .........................................................
Robotic status code 230 .........................................................
Robotic status code 232 .........................................................
Robotic status code 233 .........................................................
Robotic status code 234 .........................................................
Robotic status code 235 .........................................................
Robotic status code 236 .........................................................
Robotic status code 237 .........................................................
Robotic status code 238 .........................................................
Robotic status code 239 .........................................................
Robotic status code 240 .........................................................
Robotic status code 242 .........................................................
Robotic status code 243 .........................................................
Robotic status code 244 .........................................................
Robotic status code 245 .........................................................
Robotic status code 246 .........................................................
Robotic status code 249 .........................................................
Robotic status code 250 .........................................................
Robotic status code 251 .........................................................
Robotic status code 252 .........................................................
Robotic status code 253 .........................................................
Robotic status code 254 .........................................................
Robotic status code 255 .........................................................
Robotic status code 256 .........................................................
Robotic status code 257 .........................................................
Robotic status code 258 .........................................................
Robotic status code 259 .........................................................
Robotic status code 260 .........................................................
Robotic status code 261 .........................................................
Robotic status code 262 .........................................................
676
676
676
677
677
677
678
678
679
679
679
680
680
681
681
681
682
682
682
682
683
683
683
683
684
684
685
685
685
685
685
685
686
686
686
686
687
687
687
42
Contents
Chapter 6
Robotic error codes ......................................................... 689
Robotic error codes .....................................................................
Robot Error status code 1 .......................................................
Robot Error status code 2 .......................................................
Robot Error status code 3 .......................................................
Robot Error status code 4 .......................................................
Robot Error status code 5 .......................................................
Robot Error status code 6 .......................................................
Robot Error status code 7 .......................................................
Robot Error status code 8 .......................................................
Robot Error status code 9 .......................................................
Robot Error status code 10 .....................................................
Robot Error status code 11 .....................................................
Robot Error status code 12 .....................................................
Robot Error status code 13 .....................................................
Robot Error status code 14 .....................................................
Robot Error status code 16 .....................................................
Robot Error status code 17 .....................................................
Chapter 7
Security services status codes
689
689
690
690
690
691
691
691
692
692
692
693
693
693
693
694
694
.................................... 695
Security services status codes .......................................................
Security services status code 93 ..............................................
Security services status code 94 ..............................................
Security services status code 95 ..............................................
Security services status code 96 ..............................................
Security services status code 97 ..............................................
Security services status code 98 ..............................................
Security services status code 99 ..............................................
Security services status code 100 ............................................
Security services status code 101 ............................................
Security services status code 102 ............................................
Security services status code 103 ............................................
Security services status code 104 ............................................
Security services status code 105 ............................................
Security services status code 106 ............................................
Security services status code 107 ............................................
695
695
695
696
696
696
696
697
697
697
697
697
698
698
698
698
43
Chapter
1
NetBackup status codes
This chapter includes the following topics:
■
NetBackup status codes
■
NetBackup KMS status codes
NetBackup status codes
The following is a complete list of the NetBackup status codes that are listed in
numerical order:
Note: The term media server, as distinct from master server or server, does not
apply to the NetBackup server product. When you troubleshoot a Server installation,
ignore any references to media server. (This note does not apply to the NetBackup
Enterprise Server.)
NetBackup status code: 0
Message: the requested operation was successfully completed
Explanation: No problems were detected with the requested operation.
Recommended Action: No action is needed, unless a database was backed up
through a database extension product (for example, NetBackup for Oracle or
NetBackup for SQL Server). In those instances, code 0 means the backup script
(that started the backup) ran without error. However, you must check other status
as explained in the related NetBackup manual to see if the database was
successfully backed up.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status codes
NetBackup status codes
NetBackup status code: 1
Message: The requested operation was partially successful
Explanation: A problem was detected that may require corrective action during
the requested operation.
Recommended Action: Check the All Log Entries report and also the progress
log (if there is one).
The following are some of the problems that can appear under status code 1:
■
A file or a directory path is more than 1023 characters long.
For NetBackup Snapshot Client, the maximum path name length is 1000
characters for snapshot backups, not 1023. When the snapshot is created, a
new mount point is added to the beginning of the file path. If the new mount
point plus the original file path exceeds 1023 characters, the backup fails with
status code 1. The progress log includes the entry
ERR-Skipping long dir path.
■
You cannot open a file.
The file may have been locked for some reason.
■
The following information applies only to UNIX systems:
NetBackup cannot get the link name of a file.
■
The following information applies only to UNIX systems:
NetBackup cannot process a sparse file.
■
A read error that was encountered in a file.
■
File is of an unknown type, or may be hidden.
■
The following information applies only to UNIX systems:
The lstat system call fails on a file that is eligible to be backed up. This error
may be a permission problem.
■
The following information applies only to UNIX systems:
A file cannot be locked that has mandatory locking enabled.
■
A synthetic backup job may terminate with a status code 1 under the following
conditions:
■
No images were found to synthesize (status code = 607).
■
TIR information has been pruned from component images (status code =
136).
■
Image format is unsupported (status code = 79).
45
NetBackup status codes
NetBackup status codes
The synthetic backup job logs the actual status code in the NetBackup error
log. Refer to the documentation for the corresponding NetBackup error code
for the corrective action to take.
■
A BMR job may terminate with status code 1 in the following situation:
You save the BMR configuration and it returns an error even though the child
jobs completed successfully. For information, examine the Detailed Status tab
of the Job Details dialog box, or the nbjm unified log (originator ID 117).
■
A policy that contains multiple backup scripts starts a scheduled backup of a
UNIX database extension client. If it fails with a status code 1, some of the
backup scripts returned a failure status.
■
On clients using Windows Open File Backups (WOFB) to back up open or active
files, the following may occur:
Volume snapshots were not enabled successfully for the backup.
The following logging messages should appear in the bpbkar32 logs if volume
snapshots were not successfully enabled.
If multistreamed backup jobs are enabled, log messages similar to the following
appear that indicate volume snapshots were not enabled for the multistreamed
backup job:
11:05:44.601 AM: [1536.724] <4> tar_backup::V_AddToFI_XBSAObj:
INF - Volume snapshots not enabled for: D:\Directory1
If multistreamed backups were not enabled, log messages similar to the following
appear, which indicate volume snapshots were not enabled for the non-streamed
backup job:
1:59:41.229 PM: [2076.2088] <4>
V_Snapshot::V_Snapshot_CreateSnapshot: INF ===============================
1:59:41.229 PM: [2076.2088] <4>
V_Snapshot::V_Snapshot_CreateSnapshot: INF create snapshots for D:\Directory1
1:59:41.229 PM: [2076.2088] <4>
V_Snapshot::V_Snapshot_CreateSnapshot: INF C:\Program Files\VERITAS\NetBackup\bin\bpfis
"D:\ Directory1"
1:59:41.799 PM: [2076.2088] <4>
V_Snapshot::V_Snapshot_ParseBpfisOutput: INF
creation, FIS_ID: 1058813981
1:59:41.799 PM: [2076.2088] <4>
V_Snapshot::V_Snapshot_ParseBpfisOutput: INF
EXIT STATUS 11: system call failed
Attempting to
CREATE request:
create -fim VSP
- Snapshot
- Snapshot creation
46
NetBackup status codes
NetBackup status codes
1:59:41.799 PM: [2076.2088] <4>
V_Snapshot::V_Snapshot_CreateSnapshot: INF - Snapshot creation
was not successful
1:59:41.799 PM: [2076.2088] <4>
V_Snapshot::V_Snapshot_CreateSnapshot: INF ===============================
In this case, examine the bpfis logs for error messages regarding snapshot
creation failures. More details are available on the bpfis logs.
See the NetBackup Snapshot Client Administrator’s Guide.
In the bpfis logs, the following messages may appear when snapshot creation
fails for Windows Open File Backup:
First message:
04:01:14.168 [376.2364] <32> onlfi_fi_split: VfMS error 11; see
following messages:
04:01:14.168 [376.2364] <32> onlfi_fi_split: Fatal method error
was reported
04:01:14.168 [376.2364] <32> onlfi_fi_split: vfm_freeze_commit:
method: VSP, type: FIM, function: VSP_make
04:01:14.168 [376.2364] <32> onlfi_fi_split: VfMS method error
3; see following message:
04:01:14.168 [376.2364] <32> onlfi_fi_split: snapshot services:
snapshot creation failed: invalid argument(s).
Cause: VSP was not enabled because the VSP snapshot for the backup did
not meet the specified minimum time in the Busy File Wait VSP setting.
Either increase the Busy File Timeout VSP setting (recommended setting: 300
seconds or more) or submit the backup job when the volume has less activity.
Second message:
04:17:55.571 [1636.3224] <2> onlfi_vfms_logf: snapshot services:
(null): There was an unexpected error while preparing the VSP
snapshot transaction. Dumping the parameter array to provide
more information: Error 112 from VSP_Prepare
Cause: VSP was not enabled for the backup because the client for the VSP
Snapshot Cache files does not have enough free disk space.
Free up disk space on the volumes being backed up.
Third message:
If Microsoft Volume Shadow Copy Service (VSS) is used as the Windows Open
File Backup snapshot provider and snapshot creation fails, refer to the following:
Event Viewer’s Application and System Logs for error information.
47
NetBackup status codes
NetBackup status codes
■
A snapshot error may have occurred. Also, you may have some clients that use
the Windows Open File Backup option to back up open or active files. In this
case, a log message in the bpbkar32 debug log appears, which indicates that
a snapshot error occurred.
The following is an example of a snapshot error:
8:51:14.569 AM: [1924.2304] <2> tar_base::V_vTarMsgW: ERR Snapshot Error while reading test.file
See the recommended actions under status code 156.
■
The backup of Microsoft Exchange Server included multiple databases, but not
all of the databases were backed up successfully. Check the job details for
statements about the databases that were not backed up. In a full or a differential
backup, the transaction logs are truncated for any databases that are backed
up successfully. The transaction logs can be restored from the backup image
even if backups of other databases fail. Warning: Any database for which the
backup has failed is unprotected by this backup.
■
A granular-enabled backup of Microsoft Exchange Server successfully backed
up the databases, but the second GRT phase to capture mailbox-level information
failed. Check the job details for the cause of the failure. In a full or differential
backup, the transaction logs are truncated for any databases that are backed
up successfully, regardless of whether the GRT phase succeeds. Any database
that is backed up successfully can be restored from the backup image even if
the GRT phase fails.
■
During VMware backup, the virtual machine cannot be unlocked to allow storage
migration.
The virtual machine can be restored from this backup. However, you may want
to correct this problem before the next backup.
■
During VMware backup, the virtual machine snapshot cannot be deleted or the
virtual machine's disks cannot be consolidated.
The virtual machine can be restored from this backup. However, you may want
to correct this problem before the next backup.
■
During VMware restore, the virtual machine cannot be imported into vCloud. In
the Activity Monitor, the Detailed Status tab of the job details includes messages
from vCloud Director that indicate the reason for the error.
The restored virtual machine is present on the destination vCenter. However,
you must manually import it into vCloud.
A NetApp NDMP accelerator backup may terminate with a status code 1 with the
following clock discrepancy warnings for the volumes:
48
NetBackup status codes
NetBackup status codes
■
Clock discrepancy detected between NDMP filer and NetBackup
Media Server.
■
If this is not expected, please perform a backup with Accelerator
forced rescan enabled.
■
In order to stop seeing these messages, please address
clock discrepancy.
This problem can be caused by one of the following situations:
■
If the NetApp filer and NetBackup NDMP backup host have a time difference
of more than 1 hour, a clock discrepancy warning is displayed for all of the
volumes.
Check the time difference for the affected volumes and update as required, or
use a media server that is in the same time zone as the filer.
Note: An NTP server is the recommended method to ensure the correct time.
■
If any SnapMirror (Data Protection) volume has a lag time of more than 1 hour,
the warnings appear for that volume.
Use the following command to determine if the volume is a Data Protection
volume and if the lag time is greater than 1 hour:
■
For NetApp Clustered Data ONTAP (cDOT):
snapmirror show -fields lag-time
■
For NetApp 7-mode:
snapmirror status
If Data Protection volumes are found on the filer, either:
■
Browse to and select the volumes for backup in the Backup Selections for
the NetBackup policy.
■
Use the VOLUME_EXCLUDE_LIST with the ALL_FILESYSTEMS directive
to exclude the mirror volumes.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2
Message: none of the requested files were backed up
Explanation: A backup or archive did not back up any of the files in the file list.
49
NetBackup status codes
NetBackup status codes
This status code applies primarily to automatic backups using Lotus Notes or SQL
Server database agents, when all the backups that are job-related have failed. Or,
an Enterprise Vault backup has failed. It should not occur for standard file system
backups.
Open a NetBackup support case (as recommended in technical note TECH38838)
if you encounter this error for a UNIX, Linux, or Windows file system backup, or for
database agents other than SQL Server or Lotus Notes.
Recommended Action: Do the following, as appropriate:
■
The following information applies only to Lotus Notes:
This error occurs when archive style logging is not enabled for the Lotus Domino
server on UNIX. It also occurs when another backup of the transaction logs is
in progress.
■
For troubleshooting guidance, such as a list of logs to gather, and for details on
particular issues, refer to technical note TECH38838.
■
See the troubleshooting topic of the appropriate guide for a description of
troubleshooting tools:
■
NetBackup for Microsoft SQL Server Administrator’s Guide
■
NetBackup for Lotus Notes Administrator’s Guide
■
NetBackup for Enterprise Vault Agent Administrator’s Guide
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 3
Message: valid archive image produced, but no files deleted due to non-fatal
problems
Explanation: The backup portion of the archive command reported problems so
the files were not deleted.
Recommended Action: Examine the progress log or status of the archive on the
client to determine if you need to retry the archive after you correct the problem. If
the problem is not serious and the files were backed up, you can manually delete
the files. To verify the files that were backed up, use the NetBackup client-user
interface in restore mode and browse the files in the archive.
A possible cause for files not being deleted is that you do not have the necessary
permissions. NetBackup cannot delete files unless you are the user that owns the
files, a superuser on UNIX, or an administrator on Windows.
50
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4
Message: archive file removal failed
Explanation: The backup portion of the completed archive was successful but the
delete failed.
Recommended Action: Verify that you have permission to delete the files and
that the read-only flag is not set for the files. On UNIX clients, verify that you have
write permission to the directories that contain the files. Since the backup was
successful, you can delete the files that were backed up. (If you do not have the
necessary permissions, have the system administrator delete the files.)
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5
Message: the restore failed to recover the requested files
Explanation: Errors caused the restore to fail.
For a virtual machine restore that uses Instant Recovery, this error can occur for
the following reasons:
■
A name was specified incorrectly for the resource pool or temporary datastore.
■
The virtual machine cannot be mounted or activated in vSphere.
Recommended Action: Perform the following items in the order presented:
■
Ensure that the client’s server list contains entries for the master server and any
media servers that can be used during a backup or restore.
■
Examine the status or the progress log on the client for messages on why the
restore failed. Also, check the All Log Entries report on the server.
■
Check ownership and permission on directories where files are restored.
■
Correct the problems that you find and retry the restore.
For a virtual machine restore that uses Instant Recovery, ensure that the names
for the required parameters are specified correctly. Also, check for known issues
in the vSphere tasks or events. For detailed debugging, consult the bpVMutil logs
on the restore host:
install_path\NetBackup\logs\bpVMutil
51
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 6
Message: the backup failed to back up the requested files
Explanation: Errors caused the user backup to fail.
For VMware backups, this error can occur for the following reasons:
■
VMware item 1: The virtual machine and the backup host virtual machine (for
hotadd backup) may contain too many disks. If the total is too great for the SCSI
controllers on the backup host, a backup with the hotadd transport mode fails.
The following appears in the job status log:
ERR - Error opening the snapshot disks using given transport mode:
Status 23
■
VMware item 2: If the VMware backup host cannot access the datastore over
the selected transport mode, the backup fails. The detailed status log on the
backup host may contain the following:
12/4/2009 1:12:34 PM - Error bpbrm(pid=21376) from client vm4: ERR
- Error opening the snapshot disks using given transport mode:
Status 23
■
VMware item 3: Storage vMotion migrated the virtual machine’s files when
NetBackup performed a backup of the virtual machine directly through the ESX
server.
■
VMware item 4: For hotadd backups: The backup host was unable to resolve
the host name of the ESX server. This error may occur if DNS is not correctly
configured on the virtual machine where the backup host is installed.
■
VMware item 5: For hotadd backups: If the VM to back up and the VM that
contains the backup host do not reside in the same data center, the backup
fails.
■
VMware item 6: A previous hotadd backup of the virtual machine may have
failed, as follows:
■
In hotadd backup, VMware creates a linked clone of the VM's disks and
attaches the cloned disks to the backup host. (The attached disks can be
seen in the vSphere Client.) If a hotadd backup of the VM fails, NetBackup
may be unable to remove the cloned disks from the backup host. In the
backup host, the cloned disks prevent subsequent backups from completing.
■
In a VM backup, VMware creates mount directories in the C:\Windows\Temp
folder on the backup host. After the backup, VMware automatically removes
52
NetBackup status codes
NetBackup status codes
the mount directories. In some cases, such as when the backup uses the
hotadd transport mode, NetBackup may be unable to remove the mount
directories.
■
VMware item 7: Although vSphere 6.0 supports Internet Protocol version 6
(IPv6), it does not support dual-stack configurations with both IPv4 and IPv6.
(In a dual-stack network, network nodes are enabled for both IPv4 and IPv6.)
Note the following:
■
If both IPv4 and IPv6 addresses are enabled, vCenter 6.0 uses IPv4
addresses only.
■
If a vCenter server DNS name resolves to both IPv4 and IPv6 addresses
and the IPv6 address is unreachable, note that the VMware VDDK APIs
attempt to communicate over IPv6 and fail. As a result, a NetBackup backup
job also fails, with status code 6.
Recommended Action: Do the following as appropriate:
■
Verify that you have read access to the files. Check the status or the progress
log on the client for messages about why the backup failed. Correct problems
and retry the backup.
■
The following information applies only to Windows clients:
Verify that the account used to start the NetBackup Client service has read
access to the files.
■
For a UNIX or Linux database extension client (for example, NetBackup for
Oracle), this status code can indicate a problem with the script that controls the
backup.
Check the progress report on the client for a message such as the following:
Script exited with status code = number
The number varies. The progress log usually names the script.
Check the script for problems. Also, check the troubleshooting logs created by
the database extension. See the NetBackup guide that came with the database
extension for information on the scripts and the troubleshooting logs.
■
VMware item 1: Add more SCSI controllers to the backup host virtual machine.
■
VMware item 2: Select a different transport mode and retry the backup.
■
VMware item 3: To avoid conflicts with Storage vMotion in vSphere 5.0 or later,
NetBackup should conduct backups through the vCenter server. For more
information, see the NetBackup for VMware Administrator's Guide.
■
VMware item 4: On the virtual machine, you can enter the IP address of the
ESX server into the hosts file: \Windows\System32\drivers\etc\hosts
53
NetBackup status codes
NetBackup status codes
■
VMware item 5: For a successful hotadd backup, the two virtual machines must
be in the same VMware data center.
■
VMware item 6: Certain mount directories or cloned disks must be manually
removed to allow hotadd backups to succeed, as follows:
■
■
Remove the cloned disks from the VMware backup host and retry the backup.
■
Remove the mount directories from the \Temp folder and retry the backup.
The folder name contains a string such as VMware-System.
VMware item 7: Ensure that the vCenter’s DNS name resolves to either an IPv4
or IPv6 address (not both).
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 7
Message: the archive failed to back up the requested files
Explanation: Errors caused the user archive to fail.
Recommended Action: Verify that you have read access to the files. Check the
progress log or the status on the client for messages on why the archive failed.
Correct problems and retry the archive.
On Windows clients, verify that the account used to start the NetBackup services
has read access to the files.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 8
Message: unable to determine the status of rbak
Explanation: On DomainOS clients, rbak is used to do restores. If rbak does not
exit with a status message, NetBackup cannot determine if the restore works.
Recommended Action: Check for a new core file to see if rbak quit abnormally.
Check the ps output to see if rbak is hung. If so, cancel it and try again. Check the
progress log for any unusual messages from rbak.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 9
Message: a necessary extension package is not installed or not configured properly
54
NetBackup status codes
NetBackup status codes
Explanation: A NetBackup extension product must be installed and configured to
perform the requested operation.
Recommended Action: Verify that the required extension product is installed and
configured.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 10
Message: allocation failed
Explanation: The system memory allocation fails because of insufficient system
memory available. A possible cause is that the system is overloaded with too many
processes and not enough physical or virtual memory.
Recommended Action: Free up memory by terminating any unneeded processes
that consume memory. Add more swap space or physical memory.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 11
Message: system call failed
Explanation: A system call has failed. This status code is used for a generic system
call failure that does not have its own status code.
Recommended Action: Do the following, as appropriate:
■
Check the All Log Entries and Problems reports to determine the system call
that failed and other information about the error.
■
nbjm and nbproxy return status code 11 when an exception is processed, such
as when nbproxy obtains policy or configuration information. Examine the nbjm
unified log (originator ID 117) or the nbproxy legacy log for more detail on the
cause of the error.
■
A frequent cause is that the server’s file system is full. For example, you may
see a message similar to the following in the Problems report or bpdbm debug
log:
06/27/95 01:04:00 romb romb
failed (11)
06/27/95 01:04:01 romb romb
process
db_FLISTsend failed: system call
media manager terminated by parent
55
NetBackup status codes
NetBackup status codes
56
06/27/95 01:05:15 romb romb backup of client romb that exited with
status 11 (system call failed)
On UNIX systems, run a df command on the /usr/openv/netbackup/db
directory.
If the df command does not reveal the problem, check the bpdbm debug logs
or do a grep for the message
system call failed
In relevant files under the directory /usr/openv/netbackup/db/error/
On Windows systems, verify that the disk partition where NetBackup is installed
has enough room.
■
Verify that the system is not running out of virtual memory. If virtual memory is
the problem, turn off unused applications or increase the amount of virtual
memory.
To increase virtual memory on Windows, do the following in the order presented:
■
■
Display the Control Panel.
■
Double-click System.
■
On the Performance tab, set Virtual Memory to a higher value.
The following information applies only to UNIX clients:
Check for a semaphore problem. This error may occur because the system
does not have enough allocated semaphores. It is most commonly seen on
Solaris servers when an RDBMS is also running.
The symptoms of the problem vary. In some cases, error messages in the
NetBackup log indicate a backup failure due to an error in semaphore operation.
Another symptom is the inability of the NetBackup device manager daemon,
ltid, to acquire a needed semaphore.
System requirements vary; thus, no definite recommendations can be made.
One customer running NetBackup and ORACLE on a Solaris server made the
following changes to the /etc/system file and then restarted the system (boot
-r). The changes were adequate.
set
set
set
set
semsys:seminfo_semmni=300
semsys:seminfo_semmns=300
semsys:seminfo_semmsl=300
semsys:seminfo_semmnu=600
Set these attributes to a value great enough to provide resources to all
applications on your system.
NetBackup status codes
NetBackup status codes
■
Examine other debug logs or the progress log or status on the client. Examine
the nbjm unified log (originator ID 117) for more detail on the cause of the error.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 12
Message: file open failed
Explanation: An open of a file failed.
A disk storage unit tries to write to or create a directory on the root device of the
NetBackup server or media server. In this case, the Activity Monitor job details log
contains the message "not permitted to root device." By default, the absolute path
or specified directory for a disk storage unit cannot be on the root file system (or
system disk). You must explicitly enable them to be there when the storage unit is
created.
Recommended Action: Do the following as appropriate:
■
If you want the path for the disk storage unit to reside in the root file system:
Open the Change Storage Unit dialog box in the NetBackup Administration
Console and select the check box: This directory can exist on the root file
system or system disk.
■
If the specified path for the disk storage unit is not in the root file system or
system device, verify that the path is in a mounted file system.
■
If the specified path for the disk storage unit is in the root file system or system
device but does not need to be there, use the Change Storage Unit dialog box
to specify a different (non-root) path in a mounted file system.
■
Check the NetBackup Problems report. Try to determine the file and why the
error occurred. A possible cause is a permission problem with the file. For
detailed troubleshooting information, create a debug log directory for the process
that returned this status code. Then, retry the operation and check the resulting
debug log.
■
For NetBackup Lotus Notes, point-in-time restore jobs may fail with a status 12.
These jobs are initiated from the master server by using either the NetBackup
Administration Console or the Backup, Archive, and Restore interface. Their
failure is reported in the NetBackup tar log file. (For Windows, this file is located
in the install_path\NetBackup\logs\tar folder. For UNIX, it is located in the
/usr/openv/netbackup/logs/tar folder.) If the install path of the NetBackup
master server is different from the install path of the NetBackup client, the
automatic restore of Lotus transaction log extents during recovery of the Lotus
database fail. Note that the Activity Monitor shows a status 0 (successful). The
57
NetBackup status codes
NetBackup status codes
tar log on the client, however, shows success for the restore but a failure (status
12) for the Lotus database recovery.
Perform the restore job from the Backup, Archive, and Restore interface on the
NetBackup client.
■
For NetBackup Snapshot Client, status code 12 may appear in the
/usr/openv/netbackup/logs/bptm or bpdm log with the following:
tpc_read_config failed: cannot open file
/usr/openv/volmgr/database/3pc.conf
This status code may indicate that the policy is configured with either the
NetBackup media server or the Third-party Copy Device as the off-host backup
method, but the 3pc.conf file does not exist or is in the wrong location.
Instructions are available on how to create the 3pc.conf file.
See the NetBackup Snapshot Client Administrator’s Guide.
■
For a FlashBackup policy, if the CACHE= entry follows the source data entry,
the backup fails with status code 12. Messages such as the following appear in
the /usr/openv/netbackup/logs/bpbkar logs on the client:
09:55:33.941 [6092] <16> bpfsmap: ERR - open_snapdisk: NetBackup
snapshot enable failed error 3
09:55:33.942 [6092] <32> bpfsmap: FTL - bpfsmap: can't open
snapshot disk /dev/rdsk/c4t1d0s3 errno 0
09:55:33.950 [6092] <16> bpbkar Exit: ERR - bpbkar FATAL exit
status = 12: file open failed
09:55:33.956 [6092] <4> bpbkar Exit: INF - EXIT STATUS 12: file
open failed
09:55:33.957 [6092] <2> bpbkar Exit: INF - Close of stdout
complete
Change the order of the backup selections list so that the CACHE entry precedes
the source data entry. (The source data entry specifies the raw partition that
contains the file system to be backed up.)
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 13
Message: file read failed
Explanation: A read of a file or socket failed.
The possible causes include the following:
58
NetBackup status codes
NetBackup status codes
■
A network communication problem that occurred on the master server, media
server, or one of the clients.
■
An I/O error that occurred during a read from the file system.
■
Read of an incomplete file or a corrupt file.
■
A socket read failure caused by a network problem or a problem with the process
that writes to the socket.
■
A problem specific to NetBackup Snapshot Client (see recommended actions).
■
The first EV-SQL backup after a NetBackup installation failed.
See the Troubleshooting section of the NetBackup for Enterprise Vault Agent
Administrator’s Guide.
■
On Windows, the file list that NetBackup generates for the snapshot copy
operation does not have enough information to restore from the tar32 copy.
For example, block number information is not correct because the tar32 copy
is not yet created.
■
NetBackup does not support the policy’s Enable file recovery from VM backup
option for dual-boot VMs.
■
Locking timeouts in the VMware VDDK may cause simultaneous hotadd backups
from the same VMware backup host to fail.
In the NetBackup Activity Monitor, the detailed status log may include messages
similar to the following:
59
12/05/2014 06:43:53 - begin writing
12/05/2014 06:48:53 - Error bpbrm (pid=2605) socket read failed:
errno = 62 - Timer expired
12/05/2014 06:48:55 - Error bptm (pid=2654) media manager terminated
by parent process
The /NetBackup/logs/vxms log may include repeated instances of a VDDK
message similar to the following:
12/08/2014 05:11:35 : g_vixInterfaceLogger:libvix.cpp:1844 <DEBUG> :
[VFM_ESINFO] 2014-12-08T05:11:35.146-06:00 [7F1B1163F700 info Libs']
FILE: FileLockWaitForPossession timeout on '/var/log/vmware/hotAddLock.
dat.lck/M34709.lck' due to a local process '15882-26732358(bpbkarv)'
Recommended Action: Do the following, as appropriate:
■
Check the NetBackup Problems report for clues on where and why the problem
occurred.
■
Check that network communication works properly.
NetBackup status codes
NetBackup status codes
See "Resolving network communication problems" in the NetBackup
Troubleshooting Guide.
■
For a FlashBackup client, check the /var/adm/messages log for errors like the
following:
Mar 24 01:35:58 bison unix: WARNING: sn_alloccache: cache
/dev/rdsk/c0t2d0s3 full - all snaps using this cache are now
unusable
This error indicates that the cache partition is not large enough. If possible,
increase the size of the cache partition. Or, if multiple backups use the same
cache, reduce the number of concurrent backups. To reduce the number,
reschedule some of them or reschedule the entire backup to a time when the
file system is less active.
■
For detailed troubleshooting information, create a debug log directory for the
process that returned this status code. Then retry the operation and check the
resulting debug log.
■
Ensure that the latest service packs for all products and components (SQL
Server, Exchange, Notes, etc.) have been installed.
■
Ensure that all the network hardware (NICs, hubs, switches, routers, etc.)
throughout the environment are set to full duplex, not half duplex.
■
Check the following items regarding the NICs in your system:
■
■
Upgrade to the latest NIC drivers throughout the system.
■
Ensure that all NICs are set to full duplex, not half duplex.
See Troubleshooting network interface card performance in the NetBackup
Troubleshooting Guide.
■
Increase the timeout settings on the NIC.
■
If NIC teaming is implemented, deactivate for testing purposes.
■
Replace the NIC itself on the affected client or server.
For NetBackup Snapshot Client, status code 13 may appear in the
/usr/openv/netbackup/logs/bpbkar log.
The log can indicate the following:
■
The files to back up reside on an IDE drive as opposed to SCSI. The off-host
backup method was set to either NetBackup media server or Third-Party
Copy Device. If you use off-host backup, the disk that contains the client
files must be a SCSI or Fibre Channel device.
If the disk is an IDE drive, you may see the following in the /usr/openv/
netbackup/logs/bpfis log:
60
NetBackup status codes
NetBackup status codes
get_disk_info: FTL - /var/tmp/caa026fEU disk_inquiry failed.
Errno = 25: Inappropriate ioctl for device
The following listing may appear in the /usr/openv/netbackup/logs/bpbkar
log:
bpbkar:
bpbkar:
bpbkar:
bpbkar:
bpbkar:
INF
ERR
ERR
ERR
INF
-
Processing /var
get_disk_info() failed, status 13
tpc_get_disk_info() failed: err 13
bpbkar FATAL exit status = 13: file read failed
EXIT STATUS 13: file read failed
■
The files to back up exist on a file system that is not mounted. The file system
that is specified as the snapshot source must be mounted. If the snapshot
source is not mounted but the mount point is present, NetBackup may try to
take a snapshot of the directory preceding the directory that was specified
as the snapshot source.
■
For the NetBackup media server method, you may need to increase the
client read timeout value. In some environments, NetBackup may require
more read time than the default value allows. If the client read timeout is
insufficient, the backup may fail and that causes this error.
To increase the client read timeout for all clients, in the NetBackup
Administration Console, go to Host Properties > Master Servers >
double-click the master server, then go to Properties > Timeouts. Then,
increase the client read timeout.
■
On Windows, refresh the Backup, Archive, and Restore client console and
retry the restore. This action refreshes the file list that is displayed in the client
console and passes the correct information about the selected files.
■
To prevent timeouts in the VMware VDDK that cause simultaneous hotadd
backups from the same VMware backup host to fail, do one of the following:
■
Reduce the number of hotadd backups that run simultaneously.
■
Increase the client-read timeout on the media server as appropriate (15
minutes or more):
In the NetBackup Administration Console, click NetBackup Management
> Host Properties > Double-click on media server > Timeouts > Client
read timeout.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
61
NetBackup status codes
NetBackup status codes
NetBackup status code: 14
Message: file write failed
Explanation: A write to a file or socket failed.
Possible causes include the following:
■
An I/O error that occurred during a write to the file system.
■
Write to a socket failed. The cause of this failure is a network problem or a
problem with the process that reads from the socket.
■
Writing to a full disk partition.
Recommended Action: Do the following, as appropriate:
■
Check the NetBackup Problems report for clues on where and why the problem
occurred.
■
For detailed troubleshooting information, create a debug log directory for the
process that returned this status code. Then retry the operation and check the
resulting debug log.
■
Make sure that the routers, bridges, and other network devices are all at "full"
duplex.
See Troubleshooting network interface card performance in the NetBackup
Troubleshooting Guide.
■
Use a "sniffer" program to determine the number of packets being rejected or
re-requested.
■
On Windows systems, the client bpbkar log may contain a 10054 Connection
Reset Error (usually indicates a hardware error). Somewhere between the
NetBackup client and server, the connection was reset. When NetBackup
receives this error, it cannot continue the backup. This error has been attributed
to the following:
■
■
A hiccup in the network.
■
A bad network interface card on a NetBackup client.
■
A bad network interface card on the NetBackup server.
■
Faulty routers.
■
Any other applications that interfere with NetBackup connections.
The error occurs while you use the NetBackup Java interface: The application
server (bpjava processes) for the NetBackup Java interface probably ran out
of disk space in the file system containing
/usr/openv/netbackup/logs/user_ops. The application server writes temporary
62
NetBackup status codes
NetBackup status codes
files into directories in the /user_ops directory. Try clearing up disk space in
the file system.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 15
Message: file close failed
Explanation: A close of a file or socket failed.
Recommended Action: Check the NetBackup Problems report for clues on where
and why the problem occurred. For detailed troubleshooting information, create a
debug log directory for the process that returned this status code. Then retry the
operation and check the resulting debug log.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 16
Message: unimplemented feature
Explanation: The specified operation is not implemented. This error should not
occur through normal use of NetBackup.
Recommended Action: Save all error information and contact Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 17
Message: pipe open failed
Explanation: Occurs in NetBackup client menu and Vault areas.
Recommended Action: Save all error information and contact Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 18
Message: pipe close failed
Explanation: A pipe close failed when one process tries to start a child process.
63
NetBackup status codes
NetBackup status codes
Recommended Action: Check the NetBackup Problems report for clues on why
the failure occurred. For detailed troubleshooting information, create a debug log
directory for the process that returned this status code. Then retry the operation
and check the resulting debug log.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 19
Message: getservbyname failed
Explanation: 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.)
Recommended Action: Do the following, as appropriate:
■
Check the NetBackup Problems report for clues on why the failure occurred.
■
On a UNIX or Linux system, check that /etc/services and NIS services map
(if applicable) have entries for the NetBackup services: bpcd, bpdbm, and bprd.
■
On a Windows system, verify that the
%SystemRoot%\system32\drivers\etc\services file shows the correct entries
for the NetBackup Internet processes: bpcd, bpdbm, and bprd.
Ensure that the following numbers match the settings in the services file: The
NetBackup Client Service Port number and NetBackup Request Service Port
number on the Network tab in the NetBackup Client Properties dialog box.
To display this dialog box, start the Backup, Archive, and Restore interface and
click NetBackup Client Properties on the File menu. The values on the
Network tab are written to the services file when the NetBackup Client service
starts.
See "Verifying host name and service entries" in the NetBackup Troubleshooting
Guide.
■
Check the level of network activity. An overloaded network can cause this error.
■
If these actions do not reveal the problem, create a debug log directory for the
process that returned this status code. Then retry the operation and check the
resulting debug log.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 20
Message: invalid command parameter
64
NetBackup status codes
NetBackup status codes
65
Explanation: One or more command parameters were not valid. This error can
occur when incompatible levels of NetBackup are installed on a master and its
media servers or clients. For example, a NetBackup master server has NetBackup
8.0 and the media server or the client has NetBackup 7.7.
This error can also occur if the wrong parameters are used when you run a command
line.
Recommended Action: Do the following, as appropriate:
■
Check the NetBackup Problems report for clues.
■
If the error occurs when you run a command on the command line, verify that
the parameters are valid.
■
This status code may occur if nbjm passes parameters but does not have a
required parameter. Check the nbjm unified logs (originator ID 117) for the list
of parameters that were passed.
■
The following information pertains to NetBackup Snapshot Client.
■
If the following appears in the /usr/openv/netbackup/logs/bptm log as
enabled on a third-party copy backup, multiplexing was enabled on a
third-party copy backup:
bptm: cannot perform Third-Party-Copy for multiplexed backups
send_brm_msg: ERROR 20
bptm: EXITING with status 20
The Third-party Copy Device off-host backup method is incompatible with
multiplexing (the writing of two or more concurrent backup jobs to the same
storage device). You must disable multiplexing for any third-party copy
backups. If multiplexing is enabled, the backup fails.
■
The media server may not have the correct 3pc.conf file entry for the client
disk that is needed for the backup.
The following appears in the /usr/openv/netbackup/logs/bpbkar log:
14:45:00.983 [15773] <4> bpmap_mm_get_devid: GET_DEVICE_INDEX 1
EMC:SYMMETRIX:601092014000
14:45:00.986 [15773] <4> bpbkar child_send_keepalives: keepalive
child started, pid = 15822
14:47:02.029 [15773] <4> bpmap_mm_get_devid: keepalive child:
15822 killed
14:47:02.030 [15773] <4> bpmap_mm_get_devid: DEVICE_INDEX -1
14:47:02.031 [15773] <16> bpmap_send_extend: ERR - can't obtain
device id string EMC:SYMMETRIX:601092014000
14:47:33.167 [15773] <16> bpbkar Exit: ERR - bpbkar FATAL exit
NetBackup status codes
NetBackup status codes
66
status = 227: no entity was found
14:47:33.167 [15773] <4> bpbkar Exit: INF - EXIT STATUS 227: no
entity was found
14:47:33.168 [15773] <2> bpbkar Exit: INF - Close of stdout
complete
This shows that a particular device cannot be found in the 3pc.conf file on
the media server (14:47:02.031 [15773] <16> bpmap_send_extend: ERR
- can't obtain device id string EMC:SYMMETRIX:601092014000).
The problem is one of the following:
■
The 3pc.conf file on the media server is outdated. Recreate the 3pc.conf
file.
The media server is not on the same Fibre Channel network as the
third-party copy device and client disk. As a result, the 3pc.conf file does
not have a correct entry for the client disk. Run the bptpcinfo command
with the -x client_name option; this option adds the client disk to the
3pc.conf file. For each disk that is added to the file by means of
bptpcinfo -x client_name, you may need to add the device’s World
Wide Name (WWN=).
See the NetBackup Snapshot Client Configuration online document.
See Snapshot Client Assistance in the NetBackup Snapshot Client
Administrator’s Guide.
■
■
The HP VxFS snapshot mechanism requires a dedicated cache partition for
each snapshot. A check is made in the mount table to make sure that the
cache partition is not already in use. If the cache partition is already in use,
status code 20 occurs.
Check the /usr/openv/netbackup/logs/bpbkar log for a message similar
to the following:
bpfsmap: FTL - bpfsmap: snapshot cache already in use,
/dev/arrayvg/vol4c
bpbkar Exit: ERR - bpbkar FATAL exit status = 20: invalid
command parameter
bpbkar Exit: INF - EXIT STATUS 20: invalid command parameter
If the snapshot cache partition is already in use, do one of the following: Set
up your policy schedules to run at different times or use different cache
partitions for each backup.
If the Allow multiple data streams option is enabled, each stream must
have its own dedicated cache partition.
NetBackup status codes
NetBackup status codes
■
Compare the NetBackup version level on the server to the version level on the
clients by doing the following:
■
On UNIX or Linux NetBackup servers and clients, check the
/usr/openv/netbackup/bin/version file.
■
On Windows NetBackup servers, check the
install_path\Netbackup\version.txt file or the About NetBackup item
on the Help menu.
■
On Microsoft Windows clients, check the About NetBackup item on the
Help menu.
■
If a Java interface displays the error, tell them how to enable the debug print
manager in the Java startup file. Retry and compare the parameters that
were logged on the Java log with the parameters listed in the commands
usage statement.
■
For the Backup Media Server option for VMware backups, the storage unit that
is specified in the policy must be unique to your media servers. If the storage
unit is also available on another media server, the snapshot job cannot succeed.
■
If these actions do not reveal the problem, create a debug log directory for the
process that returned this status code (if the process uses legacy logging). Then
retry the operation and check the resulting log.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 21
Message: socket open failed
Explanation: A socket was not opened.
Recommended Action: Do the following, as appropriate:
■
Check the NetBackup Problems report for clues on where and why the failure
occurred. If you cannot determine the cause from the Problems report, create
debug log directories for the processes that returned this status code. Then,
retry the operation and check the resulting debug logs.
■
The following information applies only to Sun Solaris:
Verify that all operating system patches are installed.
See the Operating Notes section of the NetBackup Release Notes.
■
The following information applies only to Windows systems:
Verify that the recommended service packs are installed.
67
NetBackup status codes
NetBackup status codes
■
The NetBackup media server may not have the Services for Network File System
(NFS) installed. As a result, the media server cannot contact the Portmapper
service. The attempt to manually start the NFS services fails because the
Network File System is not installed.
Install the Services for Network File System on the media server.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 22
Message: socket close failed
Explanation: A socket was not closed.
Recommended Action: Do the following, as appropriate:
■
Check the NetBackup Problems report for clues on where and why the failure
occurred. If you cannot determine the cause from the Problems report, create
debug log directories for the processes that could have returned this status
code. Then, retry the operation and check the resulting debug logs.
■
The following information applies only to Sun Solaris:
Verify that all operating system patches are installed.
See the Operating Notes section of the NetBackup Release Notes.
■
The following information applies only to Windows systems:
Verify that the recommended service packs are installed.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 23
Message: socket read failed
Explanation: A read operation from a socket failed.
Recommended Action: Do the following, as appropriate:
■
Check the NetBackup Problems report for clues on where and why the failure
occurred. If you cannot determine the cause from the Problems report, create
debug log directories for the processes that could have returned this status
code. Then, retry the operation and check the resulting debug logs.
■
Corrupt binaries are one possible cause for this error.
Load a fresh bptm from the install media to try to resolve the problem.
■
The following information applies only to Sun Solaris:
68
NetBackup status codes
NetBackup status codes
Verify that all operating system patches are installed.
See the Operating Notes section of the NetBackup Release Notes.
■
The following information applies only to Windows systems:
Verify that the recommended service packs are installed.
■
The NetBackup media server is an 8.0 or earlier version and you have disabled
insecure communication in NetBackup. If you want to continue with the host
connection, do one of the following:
■
In the NetBackup Administration Console on the master server host,
select Security Management > Global Security > Enable insecure
communication with the NetBackup 8.0 and earlier hosts option.
■
Specify the nbseccmd -setsecurityconfig -insecurecommunication on
command.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 24
Message: socket write failed
Explanation: A write operation to a socket failed.
Recommended Action: Do the following, as appropriate:
■
Check the NetBackup Problems report for clues on where and why the failure
occurred. If you cannot determine the cause from the Problems report, create
debug log directories for the processes that could have returned this status
code. Then retry the operation and check the resulting debug logs.
■
A possible cause is a high network load. For example, this problem occurs with
Cannot write to STDOUT when a Windows system that monitors network load
detects a high load. It then sends an ICMP packet to other systems to inform
them that the route they use is disconnected. The log messages were similar
to the following:
01/31/96 14:05:23 ruble crabtree.null.com from client
crabtree.null.com: ERR - Cannot write to STDOUT. Err no= 242: No
route to host
01/31/96 14:05:48 ruble crabtree.null.com successfully wrote
backup id crabtree.null.com_0823125016, copy 1, fragment 1,
440864 Kbytes at 628.538 Kbytes/sec
01/31/96 14:05:51 netbackup crabtree.null.com CLIENT
crabtree.null.com POLICY Remote3SysFullW SCHED Sirius EXIT
STATUS 24 (socket write failed)
69
NetBackup status codes
NetBackup status codes
■
The following information applies only to Sun Solaris:
Verify that all operating system patches are installed.
See the Operating Notes section of the NetBackup Release Notes.
■
The following information applies only to Windows systems:
Verify that the recommended service packs are installed.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 25
Message: cannot connect on socket
Explanation: 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 the NetBackup Database
Manager services.)
It can also occur in the following situations: the network or server is heavily loaded
and has slow response time or an evaluation license key for NetBackup expired.
However, the most common cause of this error is a host name resolution problem.
The following are other possible causes of this error caused by network connectivity
issues or a required process such as pbx_exchange not running.
■
nbjm is unable to connect to bpcd on the media server
■
nbpem is unable to connect to nbproxy
■
bptm on the media server is unable to connect to nbjm on the master server.
■
You cannot perform an immediate backup operation.
These errors are caused either by network connectivity issues or if a required
process such as pbx_exchange is not running.
Recommended Action: Do the following, as appropriate:
■
Verify that bpcompatd, vnetd, and Private Branch Exchange (PBX) are running.
Information on how to start PBX is available.
See "Resolving PBX problems" in the NetBackup Troubleshooting Guide.
■
If necessary, stop and restart NetBackup.
■
On UNIX systems, enter the following:
/usr/openv/netbackup/bin/bp.kill_all
/usr/openv/netbackup/bin/bp.start_all
70
NetBackup status codes
NetBackup status codes
■
On Windows systems, enter the following:
install_path\NetBackup\bin\bpdown
install_path\NetBackup\bin\bpup
■
The following information applies only to a UNIX or Linux NetBackup master
server:
Verify that the bprd and the bpdbm processes are running. If these processes
are not running, start them. On a Windows master server, verify that the
NetBackup Request Manager and the NetBackup Database Manager services
are running. If these services are not running, start them.
If these processes or services are running, examine the All Log Entries report
for the time of the failure to determine where the failure occurred.
Do one of the following:
■
■
If you cannot view the report or you get a cannot connect on socket error,
verify again that the NetBackup Database Manager service or daemon is
running. Then, create a debug log directory for bpdbm, retry the operation,
and check the resulting debug log.
■
If you view the report and do not find a problem-related entry, create the
debug log directories for the related processes that were running when the
error first appeared. (This process frequently is bpbrm.) Then, retry the
operation and check the resulting debug logs.
Verify that the server list specifies the correct master server.
■
The following information applies only to Windows systems:
The master server is designated in the Server to use for backups and
restores drop-down in the Specify NetBackup Machines and Policy Type
dialog box. To display this dialog box, start the Backup, Archive, and Restore
interface and click Specify NetBackup Machines and Policy Type on the
File menu.
■
The following information applies only to UNIX and Linux systems:
The master server is the first SERVER entry in the bp.conf file.
■
Check the following Veritas Support website to ensure that all recommended
NetBackup patches are installed:
www.veritas.com/support
■
If failure occurs when you run a user-directed backup from a client, make
sure that a user-directed backup schedule exists at the master server.
■
With NetBackup database extensions:
Make sure that the applicable database product has the correct permissions
allowing NetBackup to write to the progress log on the client.
71
NetBackup status codes
NetBackup status codes
■
The following information applies only to UNIX systems:
If bpdbm has quit when the shutdown script runs on a media server, carefully
read the K77netbackup script. It contains details on how to prevent this
problem. The script is in /usr/openv/netbackup/bin/goodies.
If you change the server list on a master server, stop, and restart the following:
The NetBackup Database Manager and request daemons (UNIX) or the
NetBackup Database Manager and NetBackup Request Manager services
(Windows).
■
Check the services file.
■
The following information applies only to UNIX systems:
Verify that the /etc/services file (and NIS services if NIS is used) has
entries for the NetBackup services: bpcd, bpdbm, and bprd.
On Windows, verify that the %SystemRoot%\system32\drivers\etc\services
file has the correct entries for bpcd, bpdbm, and bprd.
Also, verify that the following numbers match the settings in the services file:
The NetBackup Client Service Port and the NetBackup Request Service
Port on the Network tab in the NetBackup Client Properties dialog box. To
display this dialog box, start the Backup, Archive, and Restore interface and
click NetBackup Client Properties on the File menu. The values on the
Network tab are written to the services file when the NetBackup Client service
starts.
See Verifying host names and service entries in NetBackup in the NetBackup
Troubleshooting Guide.
■
On Sun Solaris, verify that all operating system patches are installed
See the Operating Notes section of the NetBackup Release Notes.
■
On Windows, verify that the recommended service packs are installed.
■
When the base NetBackup license key expires, daemons (such as bprd and
bpdbm) terminate on the NetBackup server. If these daemons are not running,
you are likely to encounter status code 25 errors in the Administration console.
Install a valid base NetBackup license key, restart the daemons, and restart the
console.
■
For NetBackup Snapshot Client, the following applies: When many devices are
configured on a media server, it may take a long time for the bptpcinfo
command to generate the file 3pc. When the backup is run for the first time, the
backup may fail with status 25. Make sure that the
/usr/openv/volmgr/database/3pc.conf file exists. If it does, rerun the backup.
If the backup fails again, run the bptpcinfo manually to generate the file 3pc,
then try the backup again.
72
NetBackup status codes
NetBackup status codes
■
In the Auto Image Replication (A.I.R.) scenario, the error can occur if insecure
communication is disabled in NetBackup after the trust relationship between
the 8.1 and 8.0 master servers is established. If you want to continue with the
host connection, do one of the following:
■
In the NetBackup Administration Console on the master server host,
select the Security Management > Global Security > Secure
Communication > Enable insecure communication with NetBackup 8.0
and earlier hosts option.
■
Specify the nbseccmd -setsecurityconfig -insecurecommunication on
command.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 26
Message: client/server handshaking failed
Explanation: A process on the server encountered an error when it communicated
with the client. This error indicates that the client and server were able to initiate
communications, but encountered difficulties and the communications did not
complete. This problem can occur during a backup or a restore.
Recommended Action: Determine which activity encountered the handshake
failure by examining the All Log Entries report for the appropriate time period.
Determine the client and server that had the handshake failure.
For detailed troubleshooting information, create a debug log directory for the process
that returned this status code. Then retry the operation and check the resulting
debug log.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 27
Message: child process killed by signal
Explanation: A child of the process that reported this error was terminated. This
error may occur if the backup job was terminated or another error terminated the
child process. This problem may also occur if a NetBackup process was terminated
through Task Manager or another utility.
Recommended Action: Check the NetBackup All Log Entries report for clues on
where and why the failure occurred. For detailed troubleshooting information, create
73
NetBackup status codes
NetBackup status codes
a debug log directory for the process that you think may have returned this status
code. Then, retry the operation and check the resulting debug log.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 28
Message: failed trying to fork a process
Explanation: A fork of a child process failed (on UNIX) or a CreateProcess failed
(on Windows).
This failure may be due to the following:
■
An overloaded system
■
Insufficient swap space or physical memory
■
Too many processes are running on the system
Recommended Action: Check the NetBackup All Log Entries report for clues on
where and why the failure occurred. For detailed troubleshooting information, create
debug log directories for the processes that think may have returned this status
code. Then, retry the operation and check the resulting debug logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 29
Message: failed trying to exec a command
Explanation: A command was not run. This error can occur because the
permissions of the command do not allow it to be run. Or it occurs due to a lack of
system resources such as memory and swap space.
Recommended Action: Do the following, as appropriate:
■
Check the NetBackup All Log Entries report for clues on where and why the
failure occurred.
■
Check the permissions on the command to be run.
■
For detailed troubleshooting information, create a debug log directory for the
process that returned this status code. Then retry the operation and check the
resulting debug log.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
74
NetBackup status codes
NetBackup status codes
NetBackup status code: 30
Message: cannot get password information
Explanation: Could not get the passwd entry for a user.
Recommended Action: Check the NetBackup All Log Entries report for clues on
where and why the failure occurred. For detailed troubleshooting information, create
a debug log for the process that you think may have returned this status code. Then,
retry the operation and check the resulting debug log.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 31
Message: could not set user ID for process
Explanation: Could not set the user ID of a process to the user ID of the requesting
user. NetBackup runs client processes as the requesting user.
Recommended Action: Check the NetBackup All Log Entries report for clues on
where and why the failure occurred. For detailed troubleshooting information, create
a debug log directory for the process that you think may have returned this status
code. Then, retry the operation and check the resulting debug log.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 32
Message: could not set group ID for process
Explanation: Could not set the group ID of a process to the requesting user group.
NetBackup runs client processes with the group ID of the requesting user.
Recommended Action: Check the NetBackup All Log Entries report for clues on
where and why the failure occurred. For detailed troubleshooting information, create
a debug log directory for the process that you think may have returned this status
code. Then, retry the operation and check the resulting debug log.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 33
Message: failed while trying to send mail
75
NetBackup status codes
NetBackup status codes
Explanation: An email notification about backup, archive, or restore results has
failed. The email was not sent to the administrator’s address as specified by the
email global attribute. On a UNIX or Linux client, the email was not sent to an email
address that is specified with USEMAIL in the client’s bp.conf file.
Recommended Action: Check the NetBackup All Log Entries report for clues on
where and why the failure occurred. For detailed troubleshooting information, create
a debug log directory for the process that you think may have returned this status
code. Then, retry the operation and check the resulting debug log.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 34
Message: failed waiting for child process
Explanation: A NetBackup process encountered a failure while it waited for a child
process to complete.
Recommended Action: Check the NetBackup All Log Entries report for clues on
where and why the failure occurred. For detailed troubleshooting information, create
a debug log for the process that you think may have returned this status code. Then,
retry the operation and check the resulting debug log.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 35
Message: cannot make required directory
Explanation: Could not create a required directory.
Possible causes are the following:
■
A process does not have permission to create the directory
■
The path to the directory is not valid
■
An IO error occurs
■
No space is available on the device that contains the directory
Recommended Action: Do the following, as appropriate:
■
Check the NetBackup All Log Entries report to determine which directory was
not created and why it was not created. In particular, check for a full disk partition.
■
Check the permissions on the parent directory. Verify that NetBackup services
are started with a Logon as account that has permission to create the directory.
76
NetBackup status codes
NetBackup status codes
■
For detailed troubleshooting information, create a debug log directory for the
process that returned this status code. Then retry the operation and check the
resulting debug log.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 36
Message: failed trying to allocate memory
Explanation: Allocation of system memory failed. This error occurs when an
insufficient system memory is available. The system may be overloaded with too
many processes and it does not have enough physical and virtual memory.
Recommended Action: Free up memory by terminating any unneeded processes
that consume a lot of memory. Add more swap space or physical memory.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 37
Message: operation requested by an invalid server
Explanation: An invalid media server or Windows NetBackup Remote
Administration Console made a request to the NetBackup request daemon (bprd)
or NetBackup Database Manager daemon (bpdbm). On Windows, these daemons
are the NetBackup Request Manager and NetBackup Database Manager services.
Recommended Action: Examine the NetBackup All Log Entries report for the
time of this error to determine which system tried to connect to the master server.
If the server is a valid media server, verify that the storage unit for the media server
is defined. Also, verify that the server or Windows NetBackup Remote Administration
Console has a server list entry on the master server.
If necessary, update the server list.
On a UNIX or Linux master server, add a SERVER = media_server_name to the
bp.conf file. media_server_name is the host name of the media server. On a
Windows master server, add the media server to the list on the Servers tab in the
Master Server Properties dialog box.
See "Using the Host Properties window to access configuration settings" in the
NetBackup Troubleshooting Guide.
77
NetBackup status codes
NetBackup status codes
If a server or Windows NetBackup Remote Administration Console has more than
one host name (for example, multiple network interfaces), verify that the master
server has a server list entry for each of them.
If you change the server list on a UNIX or Linux master server, for the changes to
take effect do the following: stop and restart the NetBackup Request daemon (bprd)
and NetBackup Database Manager daemon (bpdbm). If you change the server list
on a Windows master server, stop, and restart the NetBackup Request Manager
and NetBackup Database Manager services.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 38
Message: could not get group information
Explanation: Could not get the group entry that describes a UNIX or Linux user
group.
Recommended Action: Check the NetBackup Problems report for clues on why
the error occurred. For detailed troubleshooting information, create a debug log
directory for the process that returned this status code. Then retry the operation
and check the resulting debug log.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 39
Message: client name mismatch
Explanation: The client used a name in a request to the NetBackup server that
did not match the configured name in the policy on the server.
Recommended Action: Change one of the following so the two match: the
NetBackup client name setting on the client (see the applicable NetBackup users
guide) or the one in the policy configuration on the server.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 40
Message: network connection broken
78
NetBackup status codes
NetBackup status codes
Explanation: 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.
Recommended Action: Do the following, as appropriate:
■
Try pinging the client from the server. If pinging is not possible, check for loose
connections or other network problems.
■
Verify that the server list settings are correct on both the client and the server.
If the backup involves a media server, verify that these entries are correct on
both the master and the media server. For example, if a media server does not
have a server list entry for the master, it does not accept connections from the
master.
■
On Windows, the master server is designated on the Servers tab in the
Master Server Properties dialog box.
See "Using the Host Properties window to access configuration settings" in
the NetBackup Troubleshooting Guide.
■
On UNIX and Linux systems, the master server is the first SERVER entry in
the bp.conf file.
If you change the server list on a UNIX or Linux master server, you must stop
and restart the NetBackup Request daemon (bprd) and NetBackup Database
Manager daemon (bpdbm) in order for the changes to take effect. On Windows,
stop and restart the NetBackup Request Manager and NetBackup Database
Manager services.
■
Status code 40 can also be due to denial of a mount request by the operator.
■
This status code may occur if nbjm was unable to connect to bpbrm or to bpmount.
Examine the nbjm unified log (originator ID 117) or the bpbrm or the bpmount
legacy logs for more detail on the cause of the error.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 41
Message: network connection timed out
Explanation: The possible causes include the following:
■
The server did not receive any information from the client for too long a period
of time.
■
You have attempted to back up too many files using FSCP (File level fast single
copy backup) with fast backup enabled.
79
NetBackup status codes
NetBackup status codes
■
80
NetBackup uses the available bandwidth to it's maximum potential and pushes
the requests accordingly; however, the Amazon S3 compliant cloud cannot
process the high number of requests.
The cloud vendor returns error 503 to slow down the requests and the backup
job fails with the following errors:
In the media server, bptm logs the following:
bptm:4940:<media_server_name>: AmzResiliency:
AmzResiliency::getRetryType cURL error: 0, multi cURL error: 0,
HTTP status: 503, XML response: SlowDown, RetryType: RETRY_EXHAUSTED
In the media server, bpbrm logs the following:
bpbrm Exit: client backup EXIT STATUS 41: network
connection timed out
This issue occurs only if a higher bandwidth is available between NetBackup
and the cloud storage.
Recommended Action: Do the following, as appropriate:
■
If you back up too many files, use Host Properties on the NetBackup server
to change Client read timeout to a much higher value (e.g., 4000). These
settings are on the Universal Settings tab in the Master Server Properties
dialog box. The default for this timeout is 300 seconds.
Also, set the File browse timeouton the Timeouts tab to a value greater than
4000.
Then retry the operation. The names of the files are logged on the debug log
file in the /usr/openv/netbackup/logs/bpbkar directory before bpbkar
processes them. The last file in the log is the file that causes problems.
■
On UNIX, Linux, or Windows clients, check for the following problems with the
bpbkar client process.
On Windows clients: The bpbkar client process is not hung. Due to the files and
directories it scans, it has not replied to the server within the Client read timeout
period. This error occurs during incremental backups when directories have
thousands of unmodified files.
For this case, use Host Properties on the NetBackup server to change Client
read timeout. This setting is on the Universal Settings tab in the Master Server
Properties dialog box. The default for this timeout is 300 seconds.
See "Using the Host Properties window to access configuration settings" in the
NetBackup Troubleshooting Guide.
You can also monitor CPU utilization to determine if this condition exists.
The following information applies only to UNIX or Linux clients:
NetBackup status codes
NetBackup status codes
■
The bpbkar client process is hung on a file that has a mandatory locking set.
For this case, add the following to the client’s bp.conf file:
VERBOSE
And as root on the client run the following:
touch /usr/openv/netbackup/bpbkar_path_tr
/usr/openv/netbackup/logs/bpbkar
Then retry the operation. The names of the files are logged on the debug
log file in the /usr/openv/netbackup/logs/bpbkar directory before bpbkar
processes them. The last file in the log is the file that causes problems.
Note: Also, use these procedures for other unknown bpbkar hangs.
If the problem is due to mandatory file locking, have NetBackup skip the
locked files. Set LOCKED_FILE_ACTION to SKIP in the
/usr/openv/netbackup/bp.conf file on the client.
The bpbkar client process is not hung. Due to the files and directories it
scans, it has not replied to the server within CLIENT_READ_TIMEOUT or
CLIENT_CONNECT_TIMEOUT. This error occurs during backups when
directories have thousands of unmodified files or during restores of the sparse
files that have thousands of holes. For this case, try to add or modify the
CLIENT_READ_TIMEOUT value in the server’s
/usr/openv/netbackup/bp.conf file. The default for
CLIENT_READ_TIMEOUT is 300 seconds if it is not specified.
Use your system’s ps command and monitor CPU utilization to help decide
which of these conditions exist.
When you finish the investigation of the problem, delete the
/usr/openv/netbackup/logs/bpbkar directory, since the log files can become
quite large and are not deleted automatically. Also delete
/usr/openv/netbackup/bpbkar_path_tr so you do not generate larger log
files than needed the next time you create directory
/usr/openv/netbackup/logs/bpbkar.
■
■
On Windows systems, try the following:
■
Disable the following file:
install_path\VERITAS\NetBackup\bin\tracker.exe
■
Repair hard drive fragmentation. Try an application that is called Diskeeper
Lite, which is part of the Windows Resource Kit.
81
NetBackup status codes
NetBackup status codes
■
■
Make sure that enough space is available in \temp.
If the server cannot connect to the client, create bpcd or bpbkar (UNIX, Linux,
and Windows only) debug log directories on the client. Then retry the operation
and check the resulting logs. If these logs do not provide a clue, create a bpbrm
debug log on the server. Then retry the operation and check the resulting debug
log.
If the bpbrm log has entries similar to the following, the problem is in the routing
configuration on the server:
bpbrm hookup_timeout: timed out waiting during the client hookup
bpbrm Exit: client backup EXIT STATUS 41: network connection
timed out
Verify that the client IP address is correct in the name service that is used. On
UNIX clients, if both the NIS and the DNS files are used, verify that they match.
See "Resolving network communication problems" in the NetBackup
Troubleshooting Guide.
■
If you use an AIX token ring adapter and the routed daemon is running, the
timeout occurs because the token ring adapter creates dynamic routes. It then
causes the routed daemon to crash.
■
For a FlashBackup client, this error occurs if the file system being backed up is
very large and has a very large number of files. It can also occur if a large number
of concurrent data streams are active at the same time. To correct it, add
CLIENT_READ_TIMEOUT to the /usr/openv/netbackup/bp.conf file and set
it to increase the timeout interval.
■
Make sure all recommended NetBackup patches are installed. Check the
following Veritas Support website for current patch information:
www.veritas.com/support
■
Add the CLIENT_READ_TIMEOUT values to the master server, media server,
and client when a NetBackup database extension product is installed. The values
should all be the same for each server. The value set is dependent on the size
of the database being backed up. More information on CLIENT_READ_TIMEOUT
is available.
See the NetBackup Administrator’s Guide, Volume II.
■
Make sure that enhanced authentication is configured correctly. For example,
the following may result in status code 41: Host A is configured to use enhanced
authentication with host B, but host B is not configured to use enhanced
authentication with host A. In this case, connections from host B to host A are
likely to fail with status code 41. Connections from host A to B are likely to fail
with authentication errors (status code 160).
82
NetBackup status codes
NetBackup status codes
■
If the Amazon S3 compliant cloud is not able to process the high number of
requests, perform one of the following:
■
Configure the bandwidth throttling to reduce the number of requests. See
"NetBackup cloud storage server connection properties" in the NetBackup
Cloud Administrator's Guide.
■
Reduce the number of read/write buffers. See "NetBackup cloud storage
server bandwidth throttling properties" in the NetBackup Cloud Administrator's
Guide.
■
Ask your cloud vendor to increase the parallel requests limit.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 42
Message: network read failed
Explanation: An attempt to read data from a socket failed.
Recommended Action: Do the following, as appropriate:
■
Verify that both the client and the server are operational.
■
Resolve any network communication problems.
See "Resolving network communication problems" in the NetBackup
Troubleshooting Guide.
■
Check the Problems report for clues.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 43
Message: unexpected message received
Explanation: The client and the server handshake were not correct.
Recommended Action: Do the following, as appropriate:
■
Verify that the correct version of software is running on the client and the server.
■
To enable detailed debug logging, do the following:
■
On the server, create a bpbrm debug log directory.
■
On clients, create a bpcd debug log directory.
■
Increase the amount of debug information to include in the logs.
83
NetBackup status codes
NetBackup status codes
See "About logs" in the NetBackup Logging Reference Guide.
■
Retry the operation and examine the logs.
If you use bpstart_notify scripts on UNIX, Linux, or Windows clients, verify
that messages are not written to stdout or stderr.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 44
Message: network write failed
Explanation: An attempt to write data to a socket failed.
Recommended Action: Do the following, as appropriate:
■
Check the Problems report for information about the error.
■
Verify that the client and servers are operational and connected to the network.
■
Create a debug log directory for the process that reported the problem and the
operation. Examine the resulting debug log file for detailed troubleshooting
information.
See "Resolving network communication problems" in the NetBackup
Troubleshooting Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 45
Message: request attempted on a non-reserved port
Explanation: A try was made to access a client from a non-reserved port.
Recommended Action: Verify that the latest software is installed on the client and
server.
■
On UNIX NetBackup servers and clients, check the
/usr/openv/netbackup/bin/version file.
■
On Windows NetBackup servers, check the
install_path\netbackup\version.txt file or the About NetBackup item on
the Help menu.
■
On Microsoft Windows clients, check the About NetBackup item on the Help
menu.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
84
NetBackup status codes
NetBackup status codes
NetBackup status code: 46
Message: server not allowed access
Explanation: The server tries to access a client, but access is blocked.
Possible causes are as follows:
■
The server is not listed on the client as a valid server.
■
The client was configured to require encrypted backups, but the encryption
attribute for the backup policy on the server was not selected.
■
The evaluation license for the NetBackup Encryption product has expired on
the server, but the NetBackup client was configured to require encrypted
backups. As a result, the server tries to make a non-encrypted backup of the
client. Since the client is configured to require encryption, the backup failed.
Recommended Action: Do the following, as appropriate:
■
If the server is a valid server but is not listed on the client, add its name to the
client’s server list:
■
On Windows clients in the Specify NetBackup Machines and Policy Type
dialog box, do the following: Add the server in the Server to use for backups
and restores drop-down list. To display this dialog box, start the Backup,
Archive, and Restore interface on the client. Then click Specify NetBackup
Machines and Policy Type on the File menu.
■
On UNIX and Linux clients, add a SERVER entry in the bp.conf file.
If you continue to have problems, more information is available:
See "Resolving network communication problems" in the NetBackup
Troubleshooting Guide.
See "Verifying host names and services entries" in the NetBackup
Troubleshooting Guide.
■
To make non-encrypted backups of the client, set CRYPT_OPTION on the client
to allowed or denied.
Refer to the NetBackup Security and Encryption Guide.
■
If the NetBackup encryption evaluation license has expired on the server and
you want to continue encrypting backups of the client, do the following: Purchase
a permanent encryption license key and add it to the server. After you add the
permanent encryption license key, check the attributes of the backup policy to
make sure that encryption is selected.
To check the validity of an evaluation license key, do the following:
On Windows, go to the Help menu on the NetBackup Administration window
on the NetBackup server and select License Keys. If the evaluation key is not
85
NetBackup status codes
NetBackup status codes
listed in the NetBackup License Keys window, the key has expired. Use this
window to add the new permanent encryption key.
On UNIX, use the following command on the server:
/usr/openv/netbackup/bin/admincmd/get_license_key
Select option f to list the active license keys and features. If the evaluation key
is not listed, the key has expired. Use this command to add the new permanent
encryption key.
■
Be sure that all name resolution services (primary, load-balancing, and
secondary) are properly configured for consistent forward and reverse name
resolution of NetBackup hosts.
More information is available in the following technical article:
http://www.veritas.com/docs/TECH204794
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 47
Message: host is unreachable
Explanation: An attempt to connect to another computer failed.
Recommended Action: Do the following, as appropriate:
■
Verify that the name service (or services) used by the client are configured to
resolve the host names of the NetBackup server correctly.
■
Verify that the name service (or services) used by the server are configured to
resolve the host name of the NetBackup client correctly.
■
Try to ping the client from the server and the server from the client.
■
If you continue to have problems, do the following:
See "Resolving network communication problems" in the NetBackup
Troubleshooting Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 48
Message: client host name could not be found
Explanation: The system function gethostbyname() failed to find the client’s host
name.
Recommended Action: Verify that the client name is correct in the following:
86
NetBackup status codes
NetBackup status codes
■
The NetBackup policy configuration on the master server.
■
The General tab in the following dialog boxes: NetBackup Client Properties
and Specify NetBackup Machines and Policy Type (on Microsoft Windows
non-target clients). To display these dialog boxes, start the Backup, Archive,
and Restore interface on the client. For the General tab, click NetBackup Client
Properties on the File menu; click Specify NetBackup Machines and Policy
Type on the File menu.
■
The bp.conf file on UNIX and Linux clients.
■
On clients and servers, verify that the name service is set up to resolve the
NetBackup client names correctly.
On UNIX clients, verify that the client’s host name is in the /etc/hosts file or
the YP hosts file or NIS maps.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 49
Message: client did not start
Explanation: The client failed to start correctly.
Recommended Action: Do the following, as appropriate:
■
Make sure that software is installed on the client and it is the correct version. If
necessary, reinstall the client software.
■
Check for full file systems on the client.
■
Enable detailed debug logging on the client by doing one of the following:
■
Create bpcd and bpbkar (UNIX, Linux, and Windows only) debug log
directories.
■
On a UNIX or Linux client, add the VERBOSE option to the
/usr/openv/netbackup/bp.conf file.
On Windows clients, increase the debug or log level.
See "Changing the logging level on Windows clients" in the NetBackup
Logging Reference Guide.
Retry the operation and examine the resulting logs.
■
■
On UNIX or Linux systems, use the UNIX sum command to check for corrupt
binaries.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
87
NetBackup status codes
NetBackup status codes
NetBackup status code: 50
Message: client process aborted
Explanation: One of the following has occurred:
■
The client backup terminates abnormally. For example, a NetBackup master or
media server is shutdown or restarted when a backup or restore is in progress.
■
An administrator uses an OS-provided command line (for example, the kill
command) to kill an active process. The job status does not reflect the change
until one hour later, when the status changes to DONE and this status code is
generated.
Recommended Action: Do the following, as appropriate:
■
Enable detailed debug logging.
■
Create a bpbkar debug log directory (UNIX, Linux, and Windows clients
only).
■
Create a bpcd debug log directory.
■
On UNIX clients, add the VERBOSE option to the
/usr/openv/netbackup/bp.conf file.
On PC clients, increase the debug or log level.
See "Changing the logging level on Windows clients" in the NetBackup
Logging Reference Guide.
Retry the operation and examine the resulting logs.
■
■
This error may occur if nbjm terminated while a backup job was running. Examine
the unified logging files on the NetBackup server for nbjm (117) for more detail
on the error. All unified logging is written to /usr/openv/logs (UNIX) or
install_path\NetBackup\logs (Windows).
■
On UNIX clients, check for core files in the / directory.
■
On UNIX clients, check the system log (/usr/adm/messages on Solaris) for
system problems.
■
This problem can sometimes be due to a corrupt binary.
On UNIX clients, use the UNIX sum command to check the bpcd, bpbkar, and
tar binaries, which are located in /usr/openv/netbackup/bin on the client.
Reinstall them if they are not the same as in the client directory under
/usr/openv/netbackup/client on the server.
On a Windows client, check the bpinetd.exe, bpcd.exe, bpbkar32.exe, and
tar32.exe files, which are located in the install_path\NetBackup\bin folder
on the client.
88
NetBackup status codes
NetBackup status codes
Reinstall the client if these files are as follows:
■
Not the same size as on other Windows clients
■
Not at the same release level
■
Do not have the same NetBackup patches as other Windows clients
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 51
Message: timed out waiting for database information
Explanation: The catalog process did not respond within five minutes.
Recommended Action: Do the following, as appropriate:
■
Verify that the NetBackup Database Manager service or daemon is running.
■
Verify that the file system that contains the NetBackup catalogs has enough
space.
■
Create bpbrm and bpdbm debug log directories on the server and retry the
operation.
■
Look in the debug log files to find more information on the problem.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 52
Message: timed out waiting for media manager to mount volume
Explanation: The requested volume was not mounted before the timeout expired.
This error can also occur if the volume is a cleaning tape but was not specified as
a cleaning tape.
Another possible cause: the last available drive has a mount request for a
non-backup (such as a restore). Then a backup that requires the same drive is
initiated before the mount completes. This error is due to the drive not being reported
as busy until the mount completes.
Recommended Action: Do the following, as appropriate:
■
Verify that the requested volume is available and an appropriate drive is ready
and in the UP state.
89
NetBackup status codes
NetBackup status codes
■
If this error occurs during a read operation (restore, duplicate, verify), the drives
could be busy. Increase the timeout for the media mount that the NetBackup
global attribute specifies, to allow more time to mount and position the media.
■
Verify that the tape is not a cleaning tape that is configured as a regular volume.
■
When an Automated Cartridge System controls the robot, verify that the ACSLS
system is up.
■
If it is an initial installation, a procedure is available.
See "Troubleshooting configuration problems" in the NetBackup Troubleshooting
Guide.
■
On Windows, check the Event Viewer Application log for the error messages
that indicate why the tape mount did not complete. On UNIX, check the system
log.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 53
Message: backup restore manager failed to read the file list
Explanation: The backup and restore manager (bpbrm) did not read the list of files
to back up or restore.
Recommended Action: Verify that the server software was installed correctly on
all NetBackup servers. If that is not the problem, do the following:
■
Create bpbrm debug log directories on the server.
■
On a UNIX or Linux NetBackup server, add the VERBOSE option to the bp.conf
file. On a Windows NetBackup server, set the Global logging level option on
the Logging tab in the Master Server Properties dialog box.
To display this dialog box, refer to the following topic:
See "Using the Host Properties window to access configuration settings" in the
NetBackup Troubleshooting Guide.
Increase the unified logging levels by using the vxlogcfg command as explained
in the following procedure:
See "About unified logging" in the NetBackup Logging Reference Guide.
■
Retry the operation and check the resulting debug logs for detailed
troubleshooting information.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
90
NetBackup status codes
NetBackup status codes
NetBackup status code: 54
Message: timed out connecting to client
Explanation: The server did not complete the connection to the client. The accept
system or Winsock call timed out after 60 seconds.
Some third-party software packages (for example, a personal firewall product) can
affect the TCP/IP stack in Windows. This action can cause a loss of connection
between the NetBackup server and the bpcd process on the client. NetBackup tries
to set SO_REUSEADDR (allows local address reuse) on the inbound socket
connection so that the port can be handed off from bpinetd.exe (the NetBackup
Client Service) to bpcd.exe. Some products may not allow this functionality due to
the various methods that can be used to violate system security.
Recommended Action: Do the following, as appropriate:
■
Perform the following procedure:
See "Resolving network communication problems" in the NetBackup
Troubleshooting Guide.
■
On UNIX clients, verify that the /usr/openv/netbackup/bin/bpcd binary exists
and that it is the correct size.
■
Check the /etc/inetd.conf file to make sure the bpcd path is correct in the
following entry:
bpcd stream tcp nowait root /usr/openv/netbackup/bin/bpcd bpcd
■
On the systems that include the following, make sure that the client name is in
the master’s /etc/hosts file: NetBackup master, media, and clients (with
NetBackup database extension products installed on one or more clients).
■
Completely uninstall the third-party software package on the client that causes
the failure. Or, contact the software manufacturer to investigate if other
configuration options or workarounds are possible.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 55
Message: permission denied by client during rcmd
Explanation: The UNIX or Linux client does not have the server’s name in its
/.rhosts file.
Recommended Action: Add the server name to the /.rhosts file on the UNIX
or Linux client.
91
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 56
Message: client’s network is unreachable
Explanation: The client cannot reach the host (WSAENETUNREACH on Windows
or ENETUNREACH on UNIX) on a system call.
Recommended Action: Try to ping the client from the server. Check the IP address
for the client. If you still have problems, talk to your network administrator.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 57
Message: client connection refused
Explanation: The client refused a connection on the port number for bpcd.
This error can occur because of the following:
■
No process listening activity occurs on the bpcd port
■
The number of connections to the bpcd port is more than the network subsystem
can handle with the listen() call
Recommended Action: Do the following, as appropriate:
■
For Windows NetBackup servers:
■
Make sure the NetBackup client software is installed.
■
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.
■
Verify that the NetBackup Client Service Port number and NetBackup
Request Service Port number on the Network tab in the NetBackup Client
Properties dialog match the bpcd and bprd settings in the services file. To
display this dialog, start the Backup, Archive, and Restore interface on the
server and click NetBackup Client Properties on the File menu.
The values on the Network tab are written to the services file when the
NetBackup Client service starts.
■
Verify that the NetBackup client service is running.
■
Use the following command to see if the master server returns correct
information for the client:
92
NetBackup status codes
NetBackup status codes
install_path\VERITAS\NetBackup\bin\bpclntcmd -pn
■
■
On UNIX servers, do the following:
■
Make sure the NetBackup client software is installed.
■
Verify that the bpcd port number on the server (either NIS services map or
in /etc/services) matches the number in the client’s services file.
Additional help is available.
See "Resolving network communication problems" in the NetBackup
Troubleshooting Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 58
Message: can’t connect to client
Explanation: The server was unable to connect to the client.
Recommended Action: Resolve network communication problems.
See "Resolving network communication problems" in the NetBackup Troubleshooting
Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 59
Message: access to the client was not allowed
Explanation: The master or the media server tries to access the client, but the
client does not recognize the server as a valid server.
For the Enterprise Vault Agent: The names of all of the media servers among the
Enterprise Vault servers are not specified in the client configuration.
Recommended Action: Do the following, as appropriate:
■
If the server is a valid server, verify that it is in the server list on the client. If
necessary add it as follows:
■
On Windows clients: Add the server on the Server to use for backups and
restores drop-down in the Specify NetBackup Machines and Policy Type
dialog box. To display this dialog box, start the Backup, Archive, and Restore
interface on the client. Then click Specify NetBackup Machines and Policy
Type on the File menu.
93
NetBackup status codes
NetBackup status codes
■
On UNIX clients: Add a SERVER entry in the bp.conf file.
If you change the server list on a UNIX or Linux master server, do the following
for the changes to take effect: Stop and then restart the NetBackup Request
daemon (bprd) and NetBackup Database Manager daemon (bpdbm). On
Windows, stop and restart the NetBackup Request Manager and NetBackup
Database Manager services.
■
■
On Windows clients, enable bpinetd debug logging as follows:
■
Create a bpinetd debug log directory on the client.
■
Increase the debug or log level.
See "Changing the logging level on Windows clients" in the NetBackup
Logging Reference Guide.
■
Retry the backup and examine the resulting logs to determine the cause of
the failure.
On all clients, enable bpcd debug logging as follows:
■
Create a bpcd debug log directory on the client.
■
On a UNIX or Linux client, add the VERBOSE option to the
/usr/openv/netbackup/bp.conf file.
■
On PC clients, increase the debug or log level as explained in the debug log
topics in Chapter 3.
■
Retry the backup and examine the resulting logs to determine the cause of
the failure.
■
Check the bpcd debug log to determine the server’s peer name and what
comparisons are made.
The bpcd process compares NetBackup server list entries to the peer name of
the server that tries the connection. It rejects the connection if the names are
different. If necessary, change the server list entry on the client to match the
peer name.
■
On Windows clients, check the following:
■
Verify that NetBackup for Windows software was installed under a Windows
administrator account.
If NetBackup is under another type of account, reinstall it under an
administrator account. The installation completes successfully under a
non-administrator account except for the following: The NetBackup Client
service is not added to Windows and the NetBackup server cannot access
the client.
■
Verify that the Windows TCP/IP service specifies the domain server that
resolves names for the subnet that contains the NetBackup servers.
94
NetBackup status codes
NetBackup status codes
UNIX, Linux, and Windows clients are frequently not on the same subnet
and use different domain servers. When this condition exists, NetBackup
servers and Windows clients may be able to ping one another, but the server
still cannot access the Windows client.
■
The preceding items may not resolve this problem.
See "Resolving network communication problems" in the NetBackup
Troubleshooting Guide.
■
If NetBackup use multiple network interfaces with media servers, make sure
that the interface names appear in the client’s /usr/openv/netbackup/bp.conf
file.
■
For the Enterprise Vault Agent: See the Troubleshooting section of the
NetBackup for Enterprise Vault Agent Administrator’s Guide.
■
Be sure that all name resolution services (primary, load-balancing, and
secondary) are properly configured for consistent forward and reverse name
resolution of NetBackup hosts.
More information is available in the following technical article:
http://www.veritas.com/docs/TECH204794
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 60
Message: client cannot read the mount table
Explanation: The backup process on the client did not read the list of mounted
file systems.
Recommended Action: Do the following, as appropriate:
■
Run a df to see if the system can read the mount table.
■
On an SCO system, code 60 can occur because the mount-point path name
exceeds 31 characters (the maximum number on an SCO system). The bpbkar
debug log on the client shows a message similar to the following:
bpbkar build_nfs_list: FTL - cannot statfs net Errno: 42406
To eliminate these errors for future backups, create a mount point with a shorter
name and symbolically link the long name to the short name.
■
For detailed troubleshooting information, create a bpbkar debug log directory.
Then retry the operation and check the resulting log.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
95
NetBackup status codes
NetBackup status codes
NetBackup status code: 61
Message: the vnetd proxy encountered an error
Explanation: The command or job was not able to perform secure communication
operations. NetBackup may report additional information in a related code in the
76xx range of codes.
Recommended Action: Examine one of the following for a 76xx code that precedes
the status code 61, and then look up the explanation for that 76xx code:
■
Verbose or debug output from the command.
■
The Detailed Status of the Job Details in the NetBackup Administration
Console.
■
The log file for the command or process that reported the status 61.
Click here to view technical notes and other information in the Veritas knowledge
base about this status code.
NetBackup status code: 63
Message: process was killed by a signal
Explanation: A kill signal was sent to the client process.
Recommended Action: The usual cause for this error is that someone intentionally
terminated a backup.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 64
Message: timed out waiting for the client backup to start
Explanation: The client did not send a ready message to the server within the
allotted time.
Recommended Action: Do the following, as appropriate:
■
On all clients, enable bpcd debug logging as follows:
■
Create a bpcd debug log directory on the client.
■
On a UNIX or Linux client, add the VERBOSE option to the
/usr/openv/netbackup/bp.conf file.
■
On PC clients, increase the debug or log level.
See "Changing the logging level on Windows clients" in the NetBackup
Logging Reference Guide.
96
NetBackup status codes
NetBackup status codes
■
On a UNIX, Linux, or Windows client, create the bpbkar debug log directory on
the client.
■
On Windows clients, verify that the NetBackup Client service is running.
■
On a UNIX or Linux client, use the ps command to check for a client process
that uses too much CPU time.
■
Retry the backup and examine the debug logs for clues on the cause of the
failure.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 65
Message: client timed out waiting for the continue message from the media
manager
Explanation: The tape manager, bptm, reported that the media did not load and
position within the allotted time.
Recommended Action: Verify that the requested volume is available and the
required device is in an UP state.
■
Create a bptm debug log directory on the server.
■
On a UNIX or Linux NetBackup server, add the VERBOSE option to the bp.conf
file. On a Windows NetBackup server, set the Verbose logging level option
on the Logging tab in the Master Server Properties dialog box.
See "Using the Host Properties window to access configuration settings" in the
NetBackup Troubleshooting Guide.
■
Retry the operation and check the bptm debug log file for information on the
drive, robot, and tape that causes the timeout.
■
On a Windows NetBackup server (master or media): check the Event Viewer
Application log for the error messages that indicate why the tape mount did not
complete.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 66
Message: client backup failed to receive the CONTINUE BACKUP message
Explanation: The client bpbkar process did not receive the message from the
server that indicates that the server is ready to continue.
97
NetBackup status codes
NetBackup status codes
Recommended Action: Do the following, as appropriate:
■
Verify that the server did not crash.
■
On UNIX, Linux, and Windows clients, enable bpbkar debug logging.
■
■
Create a bpbkar debug log directory.
■
On a UNIX or Linux client, add the VERBOSE option to the bp.conf file. On a
Windows client, set Verbose on the TroubleShooting tab in the NetBackup
Client Properties dialog box. To display this dialog box, start the Backup,
Archive, and Restore interface on the client. Then select NetBackup Client
Properties from the File menu.
On other PC clients, create a debug log directory for bpcd.
Increase the amount of information that appears in the logs.
See "Changing the logging level on Windows clients" in the NetBackup Logging
Reference Guide.
■
Use the vxlogcfg command as described in the following topic:
See "About unified logging" in the NetBackup Logging Reference Guide.
■
Retry the operation and check the resulting debug logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 67
Message: client backup failed to read the file list
Explanation: The client did not read the list of files to back up.
Recommended Action: Do the following, as appropriate:
■
Verify that the server did not crash.
■
Set up debug logging.
■
On the server, create a bpbrm debug log directory.
■
On UNIX, Linux, and Windows clients, create a bpbkar debug log directory.
■
On other PC clients, create a debug log directory for bpcd.
Increase the amount of information that appears in the logs.
See "Changing the logging level on Windows clients" in the NetBackup Logging
Reference Guide.
■
Retry the operation and check the resulting debug logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
98
NetBackup status codes
NetBackup status codes
NetBackup status code: 68
Message: client timed out waiting for the file list
Explanation: The client did not receive the list of files to back up within the allotted
time. This list comes from the server.
Recommended Action: Do the following, as appropriate:
■
Verify that the server did not crash.
■
Set up debug logging.
■
On the server, create a bpbrm debug log directory.
■
On UNIX, Linux, and Windows clients, create a bpbkar debug log directory.
■
On other PC clients, create a debug log directory for bpcd.
Increase the amount of information that appears in the logs.
See "Changing the logging level on Windows clients" in the NetBackup Logging
Reference Guide.
■
Retry the operation and check the resulting debug logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 69
Message: invalid filelist specification
Explanation: One of the following is true:
■
VMware Intelligent Policy: Multiple backup components with the same VM_name
have conflicting information.
■
The policy file list from the server has invalid entries.
■
For the Enterprise Vault Agent: A policy contains some directives that cannot
be specified together in the same policy.
■
NetBackup Snapshot Client: In an off-host backup (NetBackup Media Server
or Third-Party Copy Device), the file list contains the ALL_LOCAL_DRIVES
entry. NetBackup does not support the ALL_LOCAL_DRIVES entry for off-host
backups.
Recommended Action: Do the following, as appropriate:
■
VMware Intelligent Policy: Check for duplication of the VM_name of the VMs in
the policy.
99
NetBackup status codes
NetBackup status codes
■
Policy file list problem: Check the policy file list. If wildcards are used, verify that
the bracket characters ([ and ]) in the list match. If the file list contains UNC
(Universal Naming Convention) names, ensure that they are properly formatted.
This error can occur if nbjm is running and a SharePoint job rediscovery returns
a 0 or 1 and the policy file list is empty. Examine the nbjm unified log (originator
ID 117) for more detail on the cause of the error.
■
Enterprise Vault Agent: For more information, please see the Troubleshooting
section of the NetBackup for Enterprise Vault Agent Administrator’s Guide
available from the following location:
http://www.veritas.com/docs/DOC5332
■
NetBackup Snapshot Client: Remove the ALL_LOCAL_DRIVES entry from the
file list.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 70
Message: an entry in the filelist expanded to too many characters
Explanation: The wildcards, which were used in one of the file list entries, specified
too many files.
Recommended Action: Change the wildcards in the file list to specify fewer files.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 71
Message: none of the files in the file list exist
Explanation: 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.
Recommended Action: Do the following, as appropriate:
■
Verify that the correct file list is specified for this client.
■
On Windows clients, verify that the account used to start the NetBackup Client
service has read access to the files.
If you back up a network drive or a UNC (Universal Naming Convention) path,
do the following: Use the Services application in the Windows Control Panel to
verify that the NetBackup Client service does not start under the system account.
The System Account cannot access network drives.
100
NetBackup status codes
NetBackup status codes
To back up network drives or UNC paths: Change the NetBackup Client service
startup to log in as a user that has permission to access network drives.
■
Check the All Log Entries report for clues.
■
To set up debug logging, do one of the following:
■
On UNIX, Linux, and Windows clients, create a debug log directory for
bpbkar.
■
On other PC clients, create a debug log directory for bpcd.
■
Increase the amount of information that appears in the logs.
See "Changing the logging level on Windows clients" in the NetBackup Logging
Reference Guide.
■
Retry the operation and check the resulting debug logs.
■
For an NDMP policy type, verify that the credentials of the NDMP hosts have
been added. If not, add them.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 72
Message: the client type is incorrect in the configuration database
Explanation: The policy type attribute in the policy configuration indicates that the
client is one type, but the installed software is for another type.
Recommended Action: Verify that the policy type attribute for the policy is correct.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 73
Message: bpstart_notify failed
Explanation: The bpstart_notify script returned a nonzero exit code.
Recommended Action: Check the bpstart_notify script on the client to see if
it performs as expected.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 74
Message: client timed out waiting for bpstart_notify to complete
101
NetBackup status codes
NetBackup status codes
Explanation: The bpstart_notify script on the client takes too long.
Recommended Action: Try to speed up the bpstart_notify script or set the
BPSTART_TIMEOUT on the server to a value that is larger than the default. Set
BPSTART_TIMEOUT in the bp.conf file on a UNIX or Linux NetBackup server.
On a Windows NetBackup server, use Host Properties to set Backup Start Notify
Timeout.
See "Using the Host Properties window to access configuration settings" in the
NetBackup Troubleshooting Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 75
Message: client timed out waiting for bpend_notify to complete
Explanation: The bpend_notify script on the client takes too long.
Recommended Action: Try to speed up the bpend_notify script or set
BPEND_TIMEOUT on the server to a value that is larger than the default. Set
BPEND_TIMEOUT in the bp.conf file on a UNIX or Linux NetBackup server. On
a Windows NetBackup server, use Host Properties to set Backup End Notify
Timeout.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 76
Message: client timed out reading file
Explanation: A FIFO was specified in the file list and no data was produced on
the FIFO within the allotted time.
Recommended Action: Make sure that the process that is to produce the data
on the named FIFO is started correctly. Add an entry to the
/usr/openv/netbackup/bp.conf file on the server to set CLIENT_READ_TIMEOUT
to a larger value than the default.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 77
Message: execution of the specified system command returned a nonzero status
102
NetBackup status codes
NetBackup status codes
Explanation: An immediate command returned a nonzero status.
Recommended Action: Do the following, as appropriate:
■
Verify that the command is specified correctly.
■
For NetBackup Snapshot Client only, do the following:
The policy file list may contain the files that do not reside within a file system
that was designated as the snapshot source. To apply a snapshot method to
the backup of individual files, the snapshot source must be a file system. (It
cannot be a raw partition or Volume Manager volume.) The files in the policy
file list must reside within that file system.
■
Run the command manually to see if the wanted result is produced.
■
For detailed troubleshooting information, set up debug logging as follows:
■
On UNIX, Linux, and Windows clients, create a debug log directory for
bpbkar.
■
On other PC clients, create a debug log directory for bpcd.
■
Increase the amount of information that appears in the logs.
See "Changing the logging level on Windows clients" in the NetBackup
Logging Reference Guide.
■
Retry the operation and check the resulting debug log.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 78
Message: afs/dfs command failed
Explanation: Indicates an AFS vos command failure.
Recommended Action: Do the following, as appropriate:
■
Check the NetBackup Problems Report for additional information on why the
command failed.
■
The bpbkar debug log shows the command that was run. Create a debug log
directory for bpbkar. Retry the operation and retry the resulting debug log.
■
Try running the vos command manually to duplicate the problem.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
103
NetBackup status codes
NetBackup status codes
NetBackup status code: 79
Message: unsupported image format for the requested database query
Explanation: One or more of the images to be synthesized was encrypted. These
images cannot be synthesized.
Recommended Action: Ensure that none of the images were encrypted.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 80
Message: Media Manager device daemon (ltid) is not active
Explanation: If the server is UNIX or Linux, the NetBackup device manager
daemon, ltid, is not running. If the server is Windows, the NetBackup Device
Manager service is not running.
Recommended Action: Do the following, as appropriate:
■
On Windows, use the Activity Monitor or the Services application in the Windows
Control Panel to see if the NetBackup Device Manager service is running. If it
is not running, start it. To enable verbose logging, place VERBOSE on a line by
itself in the install_path\Volmgr\vm.conf file before you start the service.
■
On UNIX, use vmps to see if ltid is running and if necessary start ltid in
verbose mode with the following command:
/usr/openv/volmgr/bin/ltid -v
Or, add a VERBOSE entry to the /usr/openv/volmgr/vm.conf file. Create the
vm.conf file if necessary.
■
On UNIX, check the system logs to verify that ltid starts.
Note: On UNIX systems, ltid, and on Windows systems, the NetBackup Device
Manager service, is used only if devices are attached to the system.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 81
Message: Media Manager volume daemon (vmd) is not active
104
NetBackup status codes
NetBackup status codes
Explanation: The tape manager (bptm) did not communicate with the NetBackup
Volume Manager (vmd). This communication is required for most operations.
Recommended Action: Do the following, as appropriate:
■
On UNIX, verify that the Media Manager device daemon (ltid) and the
NetBackup Volume Manager (vmd) are running. Start them if necessary.
■
On Windows, verify that both the NetBackup Device Manager service and the
NetBackup Volume Manager service are running. Start them if necessary.
Note: ltid or the NetBackup Device Manager service is used only if devices are
attached to the system.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 82
Message: media manager killed by signal
Explanation: Another process or a user terminated the tape manager (bptm) or
disk manager (bpdm).
Recommended Action: This error should not occur in normal operation. If you
want to terminate an active backup, use the NetBackup Activity Monitor.
When you back up a DomainOS client, this error occurs after the server has not
received anything on the socket for at least 300 seconds. It causes a client read
timeout and breaks the connection. The bpbkar debug log has an entry similar to
the following:
13:22:49 [1347] <16> bpbkar: ERR - Extra output - - ECONNRESET
Connection reset by peer (UNIX/errno status)
To resolve the problem, increase the CLIENT_READ_TIMEOUT value. In this
instance, set the value to 900.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 83
Message: media open error
Explanation: The tape manager (bptm) or disk manager (bpdm) did not open the
device or file that the backup or restore must use.
105
NetBackup status codes
NetBackup status codes
Recommended Action: For additional information, check the following:
■
NetBackup Problems report
■
Event Viewer Application log (Windows)
■
System log (UNIX)
■
Typically, this status code indicates a drive configuration problem that allows
more than one process at a time to open the device. On UNIX, the problem may
be due one or more of the following:
■
Two (or more) devices were configured that are the same physical device
(for different densities perhaps). Verify that none of the /dev files that were
used for these devices have the same major or minor numbers.
■
Links exist in the file system that allows users access to the drives.
■
The configuration for the drives was modified (in the administrator interface
or vm.conf) and the Media Manager device daemon, ltid, was not restarted.
Verify the configuration and then start ltid.
On Windows, the problem may be that the Media and Device Management
device configuration was modified but the NetBackup Device Manager service
was not restarted. Verify the configuration and restart the NetBackup Device
Manager service.
■
On Windows, make sure that the tapes are not write protected.
■
For detailed troubleshooting information:
■
Create a debug log directory for bpdm (if the device is disk) or bptm (if the
device is tape).
■
On UNIX, restartltid in the verbose mode by running the following:
/usr/openv/volmgr/bin/ltid -v
Or, add a VERBOSE entry to the /usr/openv/volmgr/vm.conf file. Create
the vm.conf file if necessary.
■
On Windows, to enable verbose logging, add VERBOSE on a line by itself in
the install_path\Volmgr\vm.conf file. Then, stop and restart the
NetBackup Device Manager service.
■
Retry the operation and check the resulting debug log files.
■
On Windows systems, look at the
install_path\VERITAS\NetBackup\db\media\errors log for a drive that
frequently produces errors.
On UNIX systems, look at the /usr/openv/netbackup/db/media/errors
log (which is also included in the
106
NetBackup status codes
NetBackup status codes
/usr/openv/netbackup/bin/goodies/support/support script output) for
a drive that frequently produces errors.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 84
Message: media write error
Explanation: The system’s device driver returned an I/O error while NetBackup
wrote to removable media or a disk file.
Recommended Action: Do the following, as appropriate:
■
For NetBackup Snapshot Client only:
If the following message appears in the /usr/openv/netbackup/bptm log, and
the values for key, asc, and ascq are all zero (0x0) as shown in this example
message:
tape error occurred on extended copy command, key = 0x0, asc =
0x0, ascq = 0x0
NetBackup Snapshot Client probably does not support your host-bus adapter
and its driver. The host-bus adapters that are supported in the release are listed
in the NetBackup Release Notes.
■
For additional information, check the following:
■
NetBackup Problems report to determine the device or media that caused
the error
■
System and error logs for the system (UNIX)
■
Event Viewer Application and System logs (Windows)
■
If NetBackup writes backups to a disk file, verify the following: The fragment
size that is configured for the disk storage unit is not greater than the maximum
file size that the operating system specifies.
■
On Windows, make sure that the tapes are not write protected.
■
If bpbackupdb was used to back up the NetBackup catalog to a disk path on a
UNIX or Linux system, the image you try to write may be greater than the
maximum file size that is specified by that operating system. Tape files do not
have this limit. You may have to back up the catalog to tape.
■
If the media is tape, check for the following:
■
A defective or a dirty drive. Clean it or have it repaired (refer to the tpclean
command for robotic drives).
107
NetBackup status codes
NetBackup status codes
■
The wrong media type. Verify that the media matches the drive type you
use.
■
Defective media. If it is defective, use the bpmedia command to set the
volume to the FROZEN state so it is not used for future backups.
■
Incorrect drive configuration. Verify the Media and Device Management and
system configuration for the drive.
For example, on UNIX the drive may be configured for fixed mode when it
must be variable mode.
See the NetBackup Device Configuration Guide for more information.
This configuration often results in the media being frozen with the message
too many data blocks written, check tape and drive block size
configuration
See "Frozen media troubleshooting considerations" in the NetBackup
Troubleshooting Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 85
Message: media read error
Explanation: The system device driver returned an I/O error while NetBackup
reads from tape or a disk file.
Recommended Action: For additional information, check the following:
■
NetBackup Problems report to determine the device or media that caused the
error
■
System and error logs for the system (UNIX)
■
Event Viewer Application and System logs (Windows)
■
Check for the following:
■
A defective or a dirty drive. Clean it or have it repaired (see the tpclean
command for cleaning).
■
Incorrect drive configuration. Verify the Media and Device Management and
system configuration for the drive.
For example, on UNIX, the drive may be configured for fixed mode when it
must be variable mode. More information is available.
See the NetBackup Device Configuration Guide.
108
NetBackup status codes
NetBackup status codes
■
Defective media. In this case, you may not be able to recover all the data
on the media. Use the bpmedia command to set the volume to the FROZEN
state so it is not used for future backups.
See "Frozen media troubleshooting considerations" in the NetBackup
Troubleshooting Guide.
■
The wrong media type. Verify that the media matches the drive type you
use.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 86
Message: media position error
Explanation: The system’s device driver returned an I/O error while NetBackup
was positioning the tape media.
Recommended Action: For additional information, check the following:
■
NetBackup Problems report to determine the device or media that caused the
error
■
System and error logs for the system (UNIX)
■
Event Viewer Application and System logs (Windows)
■
Check for the following:
■
A defective or a dirty drive. Clean it or have it repaired (see the tpclean
command for cleaning).
■
Incorrect drive configuration. Verify the Media and Device Management and
system configuration for the drive.
For example, on UNIX, the drive may be configured for fixed mode when it
must be variable mode.
See the NetBackup Device Configuration Guide for more information.
■
Defective media. In this case, some data may be lost. Use the bpmedia
command to set the volume to the FROZEN state so it is not used for future
backups.
See "Frozen media troubleshooting considerations" in the NetBackup
Troubleshooting Guide.
■
The wrong media type. Verify that the media matches the drive type you
use.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
109
NetBackup status codes
NetBackup status codes
NetBackup status code: 87
Message: media close error
Explanation: The system’s device driver returned an I/O error while NetBackup
closed a tape.
Recommended Action: For additional information, check the following:
■
NetBackup Problems report to determine the device or media that caused the
error
■
System and error logs for the system (UNIX)
■
Event Viewer Application and System logs (Windows)
■
Check for the following:
■
A defective or a dirty drive. Clean it or have it repaired (see the tpclean
command for cleaning).
■
Defective media. In this case, some data may be lost. Use the bpmedia
command to set the volume to the FROZEN state so it is not used for future
backups.
See "Frozen media troubleshooting considerations" in the NetBackup
Troubleshooting Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 89
Message: problems encountered during setup of shared memory
Explanation: 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.
Recommended Action: Check for a shared memory problem. This error can occur
if the system cannot allocate enough shared memory. It usually occurs with
multiplexing, which increases the amount of shared memory that is required for the
operation. An entry similar to the following may be seen in a NetBackup log or
report:
system cannot allocate enough shared memory
If you see this type of message, refer to your platform vendor documentation for
instructions on how to increase shared memory on your system.
110
NetBackup status codes
NetBackup status codes
For older levels of Solaris, you may need to change one or more default System V
Shared Memory settings to prevent jobs failing with the memory allocation message,
as follows:
■
For Solaris 9, the default shminfo_shmmax value is 8 megabytes. You can place
the following line in your /etc/system file to increase this setting. A value of 32
megabytes has been used in this example. Your system may require a greater
value under some circumstances such as a high value for the NetBackup
multiplexing parameter. According to Sun Microsystems documentation, setting
this parameter to its maximum possible value has no side effects. (This parameter
is not applicable to Solaris 10).
set shmsys:shminfo_shmmax=33554432
■
For Solaris 9, the default shminfo_shmmni value is 100. You can place the
following line in your /etc/system file to increase this setting. The default value
is usually sufficient for NetBackup. In some circumstances, such as installing a
NetBackup media server on a large database server, this setting may need to
be increased. A value of 220 has been used in this example. (This parameter
is not applicable to Solaris 10).
set shmsys:shminfo_shmmni=220
Note: If you modify any of these values in the /etc/system file, you must restart
the system with boot -r for the new settings to take effect.
Refer to your vendor documentation for detailed instructions on how to modify these
values. Note that these shminfo parameters are not applicable to Solaris 10.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 90
Message: media manager received no data for backup image
Explanation: The tape manager (bptm) or disk manager (bpdm) received no data
when it performed a backup, archive, or duplication. This error can occur for
incremental backups where no data was backed up because no files have changed.
Recommended Action: Do the following, as appropriate:
■
Check the All Log Entries report.
111
NetBackup status codes
NetBackup status codes
■
For detailed debug information, create bpdm or bptm debug log directories on
the server. If the client is Windows, also create a bpbkar debug log directory
on the client. Retry the operation and check the resulting debug logs.
■
For additional information, check the following:
■
NetBackup Problems report to determine the device or media that caused
the error
■
System and error logs for the system (UNIX)
■
Event Viewer Application log (Windows)
■
Verify the Media and Device Management and system configuration for the
drive.
For example, on UNIX, the drive may not be set for variable mode in a case
where NetBackup requires that mode.
Check the NetBackup Device Configuration Guide for drive configuration
information.
■
Verify that the Media and Device Management configuration for the backup
device matches what is specified for the storage unit in the NetBackup policy.
■
Verify that you use the correct media in the drive.
■
For detailed debug information, create a bpdm or bptm debug log directory
(whichever applies) on the server. If the client is Windows, also create a bpbkar
debug log directory on the client. Retry the operation and check the resulting
debug logs.
■
If the error occurred during duplication or a Vault session that uses an Alternate
Read Server to perform duplication, verify that the Alternate Read Server has
access to the source media.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 91
Message: fatal NB media database error
Explanation: The tape manager (bptm) received an error while it read or updated
its media catalog.
Recommended Action: Do the following, as appropriate:
■
Check the All Log Entries report for more information.
112
NetBackup status codes
NetBackup status codes
■
Check the NetBackup Media Lists report to see if the catalog is intact. If the
catalog is not intact, you may want to reload it from the latest NetBackup catalog
backup volume.
■
Verify that the disk partition on which the catalog resides has enough space.
■
If these actions do not explain the problem, check the NetBackup Problems
report.
■
For detailed troubleshooting information, create a bptm debug log directory on
the server and retry the operation. Check the resulting debug log file.
■
Contact customer support and send appropriate problem and debug log sections.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 92
Message: media manager detected image that was not in tar format
Explanation: When you performed a restore, the tape manager (bptm) or disk
manager (bpdm) did not find a tar header at the offset it expected.
Recommended Action: Do the following, as appropriate:
■
Perform a bpverify of the affected image to determine if it is written correctly.
■
Check the NetBackup Problems report for additional information about the error.
■
Verify the Media and Device Management and system configuration for the
drive.
For example, if you do not configure the drive for variable-mode block size writes
on some UNIX systems, the backup images that write to the media produce this
error when you attempt to restore the image.
The following sequence of events occurs:
■
Backup succeeds.
■
Verify succeeds.
■
Restore fails.
The bptm debug log shows an error similar to the following:
00:58:54 [2304] <16> write_data: write of 32768 bytes indicated
only 29696 bytes were written, errno = 0
In this case, configure the drive for variable-mode block sizes and suspend the
media that writes on that device.
See the NetBackup Device Configuration Guide.
113
NetBackup status codes
NetBackup status codes
The images that were written to those media may be restorable (platform
dependent), but single file restores are almost guaranteed to fail. You can expire
these media and regenerate the backups. Or you can attempt to duplicate the
images on these media to another device and then expire the original copy.
■
This error has occurred on re-labeled and value-added 8-mm tape drives where
the drive’s micro code incorrectly processes a forward space record SCSI
command.
■
If the problem is not one of those discussed, create a debug log directory for
either bpdm or bptm and retry the operation. Check the resulting debug log file.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 93
Message: media manager found wrong tape in drive
Explanation: When you load a volume for a backup or restore, the tape manager
(bptm) found a volume that loaded without the expected tape header. This error
may mean that volumes in a robot are not in the slots that are indicated in the Media
and Device Management volume configuration.
Recommended Action: Do the following, as appropriate:
■
If the volume is in a robot and the robot supports barcodes, perform a Compare
Contents with Volume Configuration robot inventory (on Windows) or
Compare robot contents with volume configuration robot inventory (UNIX).
The resulting report shows the media ID that was found and validates its slot
number with what is in the volume configuration. Then, either change the physical
location in the robot or change the volume configuration to show the correct
slot.
■
If the volume was mounted on a nonrobotic drive, verify that the correct volume
was mounted and assigned.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 94
Message: cannot position to correct image
Explanation: The tape manager (bptm) searched for a backup image to restore
but did not find the correct backup ID at the expected position on the volume. This
error can indicate a drive hardware problem.
Recommended Action: Do the following, as appropriate:
114
NetBackup status codes
NetBackup status codes
■
Try the restore on another drive if possible.
■
For additional information, check the following:
■
■
NetBackup Problems report to determine the device or volume that caused
the error
■
System and error logs for the system (UNIX)
■
Event Viewer Application and System logs (Windows)
For detailed troubleshooting information, create a debug log directory for bptm
and retry the operation. Check the resulting debug log files.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 95
Message: Media ID is not assigned to this host in the EMM database
Explanation: An operation was requested on a media ID for which NetBackup
does not have a record assigned to the requesting server. For example, you use
bpmedia to suspend or freeze a media ID that does not exist or is not assigned to
the requesting server.
Recommended Action: Run a NetBackup Media List report to determine the valid
media IDs and their assigned hosts. Then, retry the command with a valid media
ID and assigned host.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 96
Message: unable to allocate new media for backup, storage unit has none available
Explanation: 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 that is specified for this backup. Note that NetBackup
does not change storage units during the backup.
Recommended Action: Check the NetBackup Problems report to determine the
storage unit that is out of media.
■
If the storage unit is a robot with empty slots, add more volumes (remember to
specify the correct volume pool).
■
If there are no empty slots, move some media to nonrobotic and then add
new volumes.
115
NetBackup status codes
NetBackup status codes
■
If you have difficulty keeping track of your available volumes, try the
available_media script:
On UNIX, this script is in:
/usr/openv/netbackup/bin/goodies/available_media
On Windows, the script is in:
install_path\NetBackup\bin\goodies\available_media.cm
d
This script lists all volumes in the volume configuration, and augments that
list with information on the volumes currently assigned to NetBackup.
■
Set up a scratch volume pool as a reserve of unassigned tapes. If NetBackup
needs a new tape and none are available in the current volume pool, it does
the following: Moves a tape from the scratch pool into the volume pool that the
backup uses.
■
If the storage unit and volume pool appear to have media, verify the following:
■
Volume is not FROZEN or SUSPENDED.
Check for this condition by using the NetBackup Media List report. If the
volume is frozen or suspended, use the bpmedia command to unfreeze or
unsuspend it (if that is wanted).
See "Frozen media troubleshooting considerations" in the NetBackup
Troubleshooting Guide.
■
Volume has not expired or exceeded its maximum number of mounts.
■
The EMM database host name for the device is correct.
If you change the EMM database host name, stop and restart the following:
The Media Manager device daemon, ltid, (if the server is UNIX or Linux)
or the NetBackup Device Manager service (if the server is a Windows
system).
■
The correct host is specified for the storage unit in the NetBackup
configuration.
The host connection should be the server (master or media) with drives
connected to it.
■
The Media and Device Management volume configuration has media in the
correct volume pool. Unassigned or active media is available at the required
retention level.
Use the NetBackup Media List report to show the retention levels, volume
pools, and status (active and so on) for all volumes. Use the NetBackup
Media Summary report to check for active volumes at the correct retention
levels.
116
NetBackup status codes
NetBackup status codes
■
The NetBackup bptm process is rejected when it requests media from the vmd
process (UNIX) or the NetBackup Volume Manager service (Windows). The
cause of this problem is that the process or service cannot determine the name
of the host that makes the request.
This error can be due to an incorrect network configuration that involves the
following:
■
Multiple network interfaces
■
/etc/resolv.conf on those UNIX or Linux systems that use it
■
Running DNS with reverse addressing not configured
■
Create bptm and vmd debug log directories and retry the operation.
■
Examine the bptm debug log to verify that bptm connects to the correct system.
If an error is logged, examine the vmd log.
On UNIX, the vmd log is:
/usr/openv/volmgr/debug/daemon/log.xxxxxx
On Windows, the vmd log is:
install_path\Volmgr\debug\daemon\xxxxxx.log
■
If this storage unit is new and this attempt to use it is the first, stop and restart
NetBackup on the master server.
Note: The mds unified logging files (OID 143) usually show the NetBackup
media selection process.
More troubleshooting information in a wizard format is available for this status code.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 97
Message: requested media ID is in use, cannot process request
Explanation: An operation was requested on a media ID that is in use. An example
of this operation is the attempt to suspend or freeze a volume while it is in use for
a backup or restore.
Recommended Action: Retry the command when the volume is not in use. Use
the Device Monitor to determine if the volume is in use.
117
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 98
Message: error requesting media (tpreq)
Explanation: The tape manager (bptm) received an error when it requested a
media mount from the NetBackup Device Manager service (Windows) or the Media
Manager device daemon (ltid) (UNIX).
Recommended Action: Do the following, as appropriate:
■
Check the NetBackup Problems report to determine the reason for the failure.
The most common cause is that the NetBackup Device Manager service (on
Windows) or the Media Manager device daemon (ltid) (on UNIX) is not running.
Start it if necessary.
■
If you duplicate backups or use Vault to duplicate backups, this error could
indicate the following: The Alternate Read Server does not have access to the
tape where the original backup resides.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 99
Message: NDMP backup failure
Explanation: The paths in your NDMP policy file list did not back up successfully.
One of the following occurred:
■
None of the backup paths exist on the NDMP host.
■
An NDMP backup uses a wildcard character that points to a file, not a file path.
Recommended Action: Do the following:
■
Check the NetBackup All Log Entries report for more information.
■
Try the following commands from another master server or media server:
# tpautoconf -verify ndmp_filer
# tpautoconf -probe ndmp_host
On the filer, verify that the NDMP service is running. The verification process
depends on the filer.
For NetApp, run ndmpd status to verify that the NDMP daemon is running. If
not, execute ndmpd on and re-run ndmpd status to verify.
118
NetBackup status codes
NetBackup status codes
■
Change the NDMP wildcard to specify path names only. You cannot use a
wildcard character that also matches a file name. For example, an NDMP backup
selection is /vol/vol_archive_01/autoit*. This specification matches path
name /vol/vol_archive_01/autoit_01/, bit it also matches file
name/vol/vol_archive_01/autoit-v1-setup.exe.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 100
Message: system error occurred while processing user command
Explanation: A system call failure in bparchive, bpbackup, bplist, or bprestore.
Recommended Action: Do the following, as appropriate:
■
Enable debug logging for bparchive, bpbackup, bplist, or bprestore (as
appropriate) by creating debug log directories for them.
On UNIX, if a nonroot user has problems, verify that the directory that was
created has mode 666. Look for and correct any reported errors.
■
Retry the operation and check the resulting logs.
If the logs do not reveal the problem, use the command-line version of the
command and correct any problems that are reported on stderr.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 101
Message: failed opening mail pipe
Explanation: The process that attempts to send mail did not open the pipe to the
server.
Recommended Action: Make sure that mail is configured on the client. For detailed
troubleshooting information, create a bpcd debug log directory and retry the
operation. Check the resulting bpcd debug log.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 102
Message: failed closing mail pipe
Explanation: The process that sends mail cannot close the pipe to the server.
119
NetBackup status codes
NetBackup status codes
Recommended Action: Make sure that mail is configured on the client. For detailed
troubleshooting information, create a bpcd debug log directory and retry the
operation. Check the resulting bpcd debug log.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 103
Message: error occurred during initialization, check configuration file
Explanation: NetBackup Snapshot Client can perform two kinds of off-host backups
by means of a data mover: the NetBackup media server method or the Third-Party
Copy Device method. For either method, an off-host data mover backup requires
a configuration file (the 3pc.conf file) to identify the following devices on the SAN:
■
The client disks to back up
■
The devices on which to store the data
If the media server has access to many disks and storage devices on the SAN, it
may take too long to acquire the device information from the SAN. As a result, if
no 3pc.conf file exists on the media server, the first multistream backup that uses
a data mover method may fail.
Recommended Action: Create the 3pc.conf file manually before running the first
multistream data mover backup. Use the following command to create the 3pc.conf
file:
# bptpcinfo -a
The 3pc.conf file is created at /usr/openv/volmgr/database/3pc.conf.
More information is available on the 3pc.conf file and how to create it.
See Configuring NetBackup for off-host data mover backups in the NetBackup
Snapshot Client Configuration document available at the following location:
https://www.veritas.com/content/support/en_US/article.TECH51377.html
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 104
Message: invalid file pathname
Explanation: None
Recommended Action: None
120
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 105
Message: file pathname exceeds the maximum length allowed
Explanation: The path name (built by using the current working directory) exceeds
the maximum path length that the system allows.
Recommended Action: Shorten the current working directory path length.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 106
Message: invalid file pathname found, cannot process request
Explanation: One of the file paths to be backed up or archived is not valid.
Recommended Action: Do one or more of the following:
■
Verify that the full path names are used and that they do not exceed the
maximum path length for the system. (On UNIX, they start with a slash character
[ / ].)
■
Verify that the files exist and that the permissions allow NetBackup to access
them.
■
Some NDMP servers do not support directory-level expansion. Some NDMP
filer vendors do not have the APIs that Veritas uses to support wildcard
characters lower than the volume level. For example, /fs1/dir* is not a supported
backup selection specification on EMC filers.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 108
Message: Action succeeded but auditing failed
Explanation: The primary action being audited has succeeded but the
corresponding audit record has failed because it was never created.
For example, you use the bppolicynew command to create a policy and it returns
status code 108. The policy is created successfully, but the associated audit record
does not appear in the audit report that the nbauditreport command generates.
This error can be returned only if auditing is enabled using the nbemmcmd command.
121
NetBackup status codes
NetBackup status codes
Recommended Action: Do the following:
■
Ensure that the nbaudit daemon (NetBackup Audit Manager) is running.
■
Examine the logs responsible for the primary action and the nbaudit logs for
more details on the cause of the error. For example, check the bpdbm logs for
policy creation.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 109
Message: invalid date specified
Explanation: This error can occur when you run a command on the command line
that contains a date option. The format of a date option can vary depending on the
locale of the master server.
Recommended Action: Do the following, as appropriate:
■
If the error occurred on a command line, examine the standard error output from
the command for an explanatory message.
■
Refer to the format for the date options in the usage statement for the command.
Look up the locale of the master server. Compare the date format of that locale
with the date format on the usage statement for the command.
■
Check the NetBackup Problems report for clues.
■
If the error appears in a Java interface, enable the debug print manager in the
Java startup file. Retry and compare the parameters that are logged in the Java
log with the parameters listed in the command’s usage statement.
■
If these actions do not reveal the problem, create a debug log directory for the
process that returned this status code. Then retry the operation and check the
resulting debug log.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 110
Message: Cannot find the NetBackup configuration information
Explanation: On Windows, NetBackup did not read the registry entries that were
created during installation. On UNIX, the /usr/openv/netbackup/bp.conf file
does not exist.
122
NetBackup status codes
NetBackup status codes
Recommended Action: On Windows, reinstall NetBackup software on the client.
On UNIX, create a /usr/openv/netbackup/bp.conf file with at least the following
lines:
SERVER = server_name
CLIENT_NAME = client_name
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 111
Message: No entry was found in the server list
Explanation: On UNIX, the SERVER = server_name line is omitted from the bp.conf
file. On Windows, the server list contains no entries.
Recommended Action: Do the following, as appropriate:
■
On a UNIX client, add the following line to the top of the
/usr/openv/netbackup/bp.conf file:
SERVER = server_name
■
On a Microsoft Windows client, add the server name on the Server to use for
backups and restores drop-down in the Specify NetBackup Machines and
Policy Type dialog box. To display this dialog box, start the Backup, Archive,
and Restore interface on the client. Then click Specify NetBackup Machines
and Policy Type on the File menu.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 112
Message: no files specified in the file list
Explanation: A restore was requested with no files in the file list.
Recommended Action: Do the following, as appropriate:
■
Specify at least one file to be restored.
■
This status code may occur if nbjm is running and a stream discovery fails to
find all stream files. Examine the nbjm unified log (originator ID 117) for more
details on the cause of the error.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
123
NetBackup status codes
NetBackup status codes
NetBackup status code: 114
Message: unimplemented error code
Explanation: This error should not occur. If nbjm received a negative error number,
status 114 is issued.
Recommended Action: Examine the nbjm unified log (originator ID 117) for
detailed information on the cause of the error.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 116
Message: VxSS authentication failed
Explanation: On either end of a socket connection, the parties did not mutually
authenticate each other.
Recommended Action: Do the following, as appropriate:
■
Ensure that the Veritas Product Authentication Service is installed and configured.
For complete installation instructions, see the NetBackup Security and Encryption
Guide available from the following location:
http://www.veritas.com/docs/DOC5332
■
Check that both parties have a valid certificate. Examine the expiry date that is
listed from a bpnbat -WhoAmI. For example:
bpnbat -WhoAmI
Name: JDOG
Domain: MYCOMPANY
Issued by: /CN=broker/OU=root@machine1.mycompany.com/O=vx
Expiry Date: Sep 19 12:51:55 2009 GMT
Authentication method: Microsoft Windows
Operation completed successfully.
Shows an expiry date of September 19th, 2009. After 12:51:55 GMT this
credential is no longer valid and a new credential is required.
■
If you run from the NetBackup Administration Console, close and reopen the
console. The console automatically obtains a credential for the currently logged
in identity, if possible. By default, these certificates are valid for 24 hours. The
following is an example of how to extend the credential beyond 24 hours to 30
days (2592000 seconds):
Windows: <install path>\veritas\netbackup\sec\at\bin\vssat
setexpiryintervals -p <plugin_name> -t <user> -e 2592000
124
NetBackup status codes
NetBackup status codes
UNIX: usr/openv/netbackup/sec/at/bin/vssat setexpiryintervals -p
<plugin_name> -t <user> -e 2592000
■
Ensure that the certificates for both sides use the same broker or are children
of the same root broker and that trusts are established between them.
See the NetBackup Security and Encryption Guide for more information on
broker hierarchies and how to establish trust relationships between brokers.
■
Ensure that connectivity between the physical systems in question is possible.
If general sockets cannot connect between the computers (such as ping and
telnet), issues within the network unrelated to NetBackup can cause this
problem.
■
Ensure that the system has sufficient swap space and the following directories
are not full:
■
/home/username
■
/usr/openv/netbackup/logs
■
/tmp
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 117
Message: VxSS access denied
Explanation: The user identity that was used to attempt an operation does not
have the permissions that are needed to perform the action.
Recommended Action: Do the following, as appropriate:
■
If you use the default groups, make certain that the user attempts to perform an
operation appropriate for that group. For example, a member of NBU_Operators
is unable to modify policy information, which is a permission reserved for
administrator roles.
■
Ensure that the system has sufficient swap space and the following directories
are not full:
■
■
/home/username
■
/usr/openv/netbackup/logs
■
/tmp
If you use your own defined groups and permissions, first determine the object
with which the operation is associated. Then, add the permissions relative to
the action. For example, a user is required to up and down drives but currently
125
NetBackup status codes
NetBackup status codes
does not have permission to do so. Verify that the user belongs to the correct
authorization group.
If necessary, verify that the group has Up and Down permissions on the Drive
object within the Group Permission tab. If necessary, increase the verbosity
level of NetBackup to locate what object and what permissions are required for
the failing request. The pertinent lines in the debug logs look similar to the
following:
17:19:27.653 [904.872] <2> GetAzinfo: Peer Cred Info.
Name: JMIZZLE
Domain: MYCOMPANY
Expiry: Sep 24 21:45:32 2003 GMT
Issued by: /CN=broker/OU=root@machine1.mycompany.com/O=vx
AuthType: 1
17:19:37.077 [904.872] <2> VssAzAuthorize: vss_az.cpp.5082:
Function: VssAzAuthorize. Object
NBU_RES_Drives
17:19:37.077 [904.872] <2> VssAzAuthorize: vss_az.cpp.5083:
Function: VssAzAuthorize. Permissions Up
17:19:40.171 [904.872] <2> VssAzAuthorize: vss_az.cpp.5166:
Function: VssAzAuthorize. 20 Permission denied.
In this example, the user JMIZZLE attempts to perform an operation that requires
the Up permission on the Drives object. To diagnose the problem, examine the
group(s) to which the user belongs to ensure that the appropriate group includes
the Up permission. (Up is a member of the Operate permission set for Drives.)
■
If you have performed disaster recovery and are now running catalog recovery
using the Remote Administration Console, you need to restart the master
server services. After the restart, if you do not logout from the Remote
Administration Console and try to access the Security Management tab, you
will receive this error message and must log in again.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 118
Message: VxSS authorization failed
Explanation: NetBackup was unable to complete the authorization check against
the authorization service.
Recommended Action: Do the following, as appropriate:
■
Ensure that the Veritas Product Authorization Service or daemon is running.
126
NetBackup status codes
NetBackup status codes
See the NetBackup Security and Encryption Guide for more information on
authentication and authorization daemons.
■
Ensure that you are in communication with the correct master server. Within
the bp.conf files on the local server, verify that the entry
AUTHORIZATION_SERVICES specifies the proper host name (fully qualified) of the
authorization service. For example, AUTHORIZATION_SERVICE =
machine2.mycompany.com 0 specifies that the server contacts machine2 to
perform authorization checks. Also ensure that this entry matches that of the
master server.
■
Ensure that the system has sufficient swap space and the following directories
are not full:
■
■
/home/userName
■
/usr/openv/netbackup/logs
■
/tmp
Ensure that the server that contacts the master has a valid certificate. The
computer certificate can be examined as follows:
For UNIX:
# bpnbat -WhoAmI -cf
/usr/openv/var/vxss/credentials/machine3.mycompany.com
For Windows:
Bpnbat WhoAmI -cf "c:\Program
Files\VERITAS\NetBackup\var\vxss\credentials\machine3.my
company.com"
Both of which would return:
Name: machine3.mycompany.com
Domain: NBU_Machines@machine2.mycompany.com
Issued by: /CN=broker/OU=root@machine2.mycompany.com/O=vx
Expiry Date: Sep 2 19:25:29 2004 GMT
Authentication method: Veritas Private Security
Operation completed successfully.
If the expiry date was exceeded, use bpnbat -LoginMachine to obtain a new
credential for the computer.
See the NetBackup Commands Reference Guide for more information on bpnbat.
The server that attempts the check is not authorized to examine the authorization
database. Ensure that bpnbaz -ShowAuthorizers re-tuned the computer's
127
NetBackup status codes
NetBackup status codes
identity. Ensure that the computer has a computer credential under the directory
as follows:
Program Files\VERITAS\var\vxss\credentials (Windows)
/usr/openv/var/vxss/credentials (UNIX)
This credential should have the full name of the computer as in the following
example: machine1.company.com.
■
Check that the maximum number of open sockets to the authorization database
was not exhausted. Use netstat to determine the number of sockets that are
opened to port 4032 on the authorization server and that refer to the following
configurations:
Windows:
HKLM\SOFTWARE\VERITAS\Security\Authorization\Communication\ClientMaxConnections
UNIX: /etc/vx/vss/VRTSaz.conf entryClientMaxConnections
If the maximum number of open connections was reached, you may need to
increase the number of maximum open connections. An increase in the number
of open connections increases the memory footprint of the authorization service
or daemon. Note that extreme increases in the maximum number of connections
can cause performance degradation.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 120
Message: cannot find configuration database record for requested NB database
backup
Explanation: The program that backs up the NetBackup internal catalogs did not
find the attributes that indicate which media IDs to use or paths to back up. This
error should not occur under normal circumstances.
Recommended Action: Do the following, as appropriate:
■
Check the NetBackup Problems report for additional information about the error.
■
For detailed troubleshooting information, create admin and bpdbm debug log
directories and retry the operation. Check the resulting debug logs.
■
Contact customer support and send the appropriate problem and debug log
sections that detail the error.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
128
NetBackup status codes
NetBackup status codes
NetBackup status code: 121
Message: no media is defined for the requested NB database backup
Explanation: When NetBackup attempted to back up its internal catalogs, no
media IDs were defined in the catalog backup configuration.
Recommended Action: Add the media IDs to the catalog backup configuration.
Verify that the media IDs are in the NetBackup volume pool.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 122
Message: specified device path does not exist
Explanation: The NetBackup internal catalogs were backed up by using the
bpbackupdb command line and by specifying a device path (on Windows) or a raw
device file (on UNIX) that does not exist.
Recommended Action: Retry the command by using a valid device file name.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 123
Message: specified disk path is not a directory
Explanation: When NetBackup attempted to back up its internal catalogs, the
backup attributes were set to dump to a disk. However, the disk file path already
exists and is not a directory.
Recommended Action: Specify a different disk path for the catalog backup or
delete the file that already exists.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 124
Message: NB database backup failed, a path was not found or is inaccessible
Explanation: One or more of the specified paths in the catalog backup configuration
are not backed up.
Recommended Action: Do the following, as appropriate:
■
Check the NetBackup Problems report for additional information about the error.
129
NetBackup status codes
NetBackup status codes
The following are some possible causes:
■
■
The path does not exist.
■
On a UNIX system, one of the paths contains a symbolic link.
After you determine which path cannot be accessed, correct the path names in
the catalog backup configuration.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 125
Message: a NetBackup catalog backup is in progress
Explanation: Only one NetBackup catalog backup can be active at any given time.
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.)
Recommended Action: Retry the operation after the catalog backup completes.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 126
Message: NB database backup header is too large, too many paths specified
Explanation: 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.
Recommended Action: Delete some of the paths from the catalog backup
configuration.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 127
Message: specified media or path does not contain a valid NB database backup
header
Explanation: The bprecover command was issued and the media ID specified
does not have valid catalog backup data.
Recommended Action: Validate that the correct media ID is used.
130
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 128
Message: NB database recovery failed, a process has encountered an exceptional
condition
Explanation: In the catalogs that were specified for recovery, one or more cannot
be restored. For more detail, refer to the error message that precedes this status
code in the output from the bprecover command.
Recommended Action: Do the following, as appropriate:
■
Fix the problem that was reported in the error message in the bprecover output.
■
Identify which NetBackup services to shut down before a NetBackup database
recovery attempt:
See "About recovering the NetBackup catalog" in the NetBackup Troubleshooting
Guide.
The NetBackup services should be shut down except for the NetBackup Client
Service, which must be running for the database recovery to succeed.
■
Check the NetBackup Problems report for additional information about the error.
The following are some possible causes:
■
A disk may be full.
■
The NetBackup catalog tape may be corrupt.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 129
Message: Disk storage unit is full
Explanation: 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.
In a scheduled backup job that writes to a storage unit group (which contains this
disk storage unit), the following occurs: the NetBackup scheduler requests the
storage unit with the greatest available capacity when the job is retried.
For the retry, when the scheduler requests the storage unit with the greatest available
capacity, note the following:
131
NetBackup status codes
NetBackup status codes
■
A tape storage unit in the storage unit group has preference over any disk storage
units since tape storage units usually have more capacity.
■
If the storage unit with the most unused capacity is busy, NetBackup skips it.
NetBackup then selects an available storage unit with the next largest, unused
capacity.
■
If the storage unit with the greatest unused capacity is the one that lacked
capacity when the job first failed, the scheduler tries it again. That storage unit
may have more unused capacity now than it did when the job failed.
Recommended Action: Do the following, as appropriate:
■
Either free sufficient space or add more space to the file system for this storage
unit.
■
Lower the high capacity mark for this disk storage unit. Configure the policies
to access it through a storage unit group that provides alternative storage to
use when this storage unit fills up. Ideally, if an image exceeds the file system’s
high capacity mark, it also completes successfully. This image leaves the storage
unit in a full state (over the high capacity mark). The storage unit then is not
assigned to other jobs until its capacity falls under its high capacity mark.
■
If the Staging attribute is set on the disk storage unit that did not have enough
capacity, it may be unable to create free space. It cannot create space because
the backups that are staged to the disk are not relocated (eligible to be deleted
from the staging storage unit). Ensure that staging’s relocation (duplication) jobs
successfully copy enough images to provide sufficient free space for new
backups.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 130
Message: system error occurred
Explanation: An error occurred that prevents the product from operating in a
consistent fashion. This error is usually related to a system call.
Recommended Action: Do the following, as appropriate:
■
Check the NetBackup Problems report for additional information about the error.
■
Check the system log for reported problems.
■
For detailed troubleshooting information, create bpdbm, bptm, and bprd debug
log directories on the master server. Increase the unified logging level by using
the vxlogcfg command.
See "About unified logging" in the NetBackup Logging Reference Guide.
132
NetBackup status codes
NetBackup status codes
■
Retry the operation and check the resulting debug logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 131
Message: client is not validated to use the server
Explanation: The client name, as determined from the connection to the server,
did not match any client name in the NetBackup configuration. No altnames
configuration for this client exists on the master server. A client and server with
multiple network connections can encounter this problem in the following situation:
the name by which the client is configured is not the one by which its routing tables
direct connections to the server.
Recommended Action: Do the following, as appropriate:
■
Examine the NetBackup Problems report.
■
Create a debug log directory for bprd and retry the operation. Check the resulting
debug log to determine the connection and the client names.
Depending on the request type (restore, backup, and so on), you may need or
want to do the following:
■
Change the client’s configured name.
■
Modify the routing tables on the client.
■
On the master server, set up an altnames directory and file for this client.
See the NetBackup Administrator’s Guide, Volume I.
Or
■
■
On a UNIX master server, create a soft link in the NetBackup image catalog.
See Verifying host names and services entries in the NetBackup Troubleshooting
Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 132
Message: user is not validated to use the server from this client
Explanation: None
Recommended Action: None
133
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 133
Message: invalid request
Explanation: One of the following has occurred:
■
You make an unrecognizable request. This lack of recognition usually results
from different versions of NetBackup software being used together.
■
A client receives this error in response to a list or restore request. The
DISALLOW_CLIENT_LIST_RESTORE or DISALLOW_CLIENT_RESTORE option exists
in the bp.conf file on a UNIX NetBackup server or in the registry on a Windows
NetBackup server. These options deny list and restore requests from all
NetBackup clients.
Recommended Action: Do the following, as appropriate:
■
■
■
If you suspect that the software versions are the problem, verify that all
NetBackup software is at the same version level.
■
On UNIX NetBackup servers and clients, check the
/usr/openv/netbackup/bin/version file.
■
On Windows NetBackup servers, check the
install_path\netbackup\version.txt file or the About NetBackup item
on the Help menu.
■
On Microsoft Windows clients, check the About NetBackup item on the
Help menu.
If the server denies list and restore requests, do one of the following:
■
Go to the NetBackup Administration Console. In the left pane, expand
NetBackup Management > Host Properties > Master Servers. In the right
pane, double-click the master server you want to modify. In the properties
dialog box, in the left pane, select Client Attributesto access the Allow
client browse and Allow client restore options.
■
Remove the DISALLOW_CLIENT_LIST_RESTORE and
DISALLOW_CLIENT_RESTORE options from the bp.conf file on a UNIX
NetBackup server or from the registry on a Windows NetBackup server.
Then, stop and restart the NetBackup request daemon (UNIX) or NetBackup
Request Manager service (Windows).
For detailed troubleshooting information, create bpdbm, bprd, and admin debug
log directories. Retry the operation and check the resulting debug logs.
134
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 134
Message: unable to process request because the server resources are busy
Explanation: Status code 134 is an informational message that indicates that all
drives in the storage unit are currently in use. If all drives are in use, NetBackup
automatically tries another storage unit. If one is not available, NetBackup re-queues
the job with a status of 134 and retries it later.
Recommended Action: None
The 134 code is an informational message only and is not considered an error. It
can occur for a number of reasons in normal operation. The 134 status code can
occur more frequently in an SSO environment. No action is necessary.
A status 134 is not logged in the error logs. A 134 status causes a new try to appear
in the Activity Monitor. It does not increase the retry count that is associated with
the allowed number of retries.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 135
Message: client is not validated to perform the requested operation
Explanation: An alternate client restore was tried that does not come from the
root user (on UNIX) or the administrator (on Windows).
Recommended Action: Retry the operation as a root user (on UNIX) or as an
administrator (on Windows) on the master server. Also see status code 131.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 136
Message: tir info was pruned from the image file
Explanation: The TIR information was pruned from one or more of the component
(differential or cumulative) backup images being synthesized.
This situation arises when the following occurs:
■
The most recent backup image for the client is a synthetic full or cumulative
backup
135
NetBackup status codes
NetBackup status codes
■
The TIR information from one or more of the component images before the
synthetic full (or cumulative) backup is pruned
The TIR information is automatically restored to the image catalog if you expire the
synthetic backup (full or cumulative) image and try to rerun the synthetic backup
job for the client. However, the synthetic backup job fails with this error if the TIR
restore fails due to bad, missing, or vaulted media or a bad drive.
Recommended Action: Reimport the TIR information into the catalog of each
component image (from which the TIR information was pruned). Then rerun the
synthetic backup job. The TIR information can be imported into the image catalog
by initiating a true image restore of any file from that component image. The restore
process also restores the TIR information in the image catalog.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 140
Message: User ID was not superuser
Explanation: A user or process that did not have root privileges (on UNIX) or
administrator privileges (on Windows) started the process.
Recommended Action: If appropriate, give the user or the process administrator
privileges (on Windows) or root privileges (on UNIX) and retry the operation.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 141
Message: file path specified is not absolute
Explanation: The file specification must be an absolute path.
Recommended Action: Correct the file specification and retry the command.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 142
Message: file does not exist
Explanation: To back up a VxFS file system with Snapshot Client, the VxFS file
system on the client must be patched with correct, dynamically linked libraries. If
the correct VxFS libraries are not installed, the backup fails with status 142.
The following appears in the log:
136
NetBackup status codes
NetBackup status codes
■
For most snapshot backups, the following message appears in the
/usr/openv/netbackup/logs/bpfis log on the client:
09:36:48.299 [527] <32> fs_dev_rt_check: FTL - snapshot method:
nbu_snap abort - required VxFS dynamic linked libraries for
NetBackup are not installed. Please visit the Veritas support
website, and refer to Technote number 262225 for further
information.
■
For the backups that run from a FlashBackup policy, the following appears in
the /usr/openv/netbackup/logs/bpbkar log on the client:
10:09:56.566 [1146] <32> bpfsmap: FTL - bpfsmap: FlashBackup
abort - required VxFS dynamic linked libraries for NetBackup are
not installed. Please visit the Veritas support website, and
refer to Technote number 262225 for further information.
10:09:56.571 [1146] <16> bpbkar Exit: ERR - bpbkar FATAL exit
status = 142: file does not exist
10:09:56.573 [1146] <4> bpbkar Exit: INF - EXIT STATUS 142: file
does not exist
■
The bpexpdate, bpimmedia, bpimport, and bpverify commands return this
status code if you cannot gather disk pool, disk volume, disk pool volume, disk
media IDs, or server type information.
■
The bpbkar returns this status code if a checkpoint clone is missing, or if a
frozen image backup does not return the snapshot information.
Recommended Action: Install the VxFS dynamic libraries on the NetBackup client
as described in tech note TECH28008 and try the backup again.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 143
Message: invalid command protocol
Explanation: A poorly formed request was made to the NetBackup request daemon
(UNIX) or to the Request Manager service (Windows). 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.
Recommended Action: Examine the NetBackup error logs to determine the
system that was the source of the data. On that system, determine the process that
137
NetBackup status codes
NetBackup status codes
initiated the request. If it was a NetBackup process, verify that the process or
command is compatible with the version of software on the server.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 144
Message: invalid command usage
Explanation: This status code is due to a NetBackup process being started with
improper options or an incompatibility in the product.
Recommended Action: Either correct the command or verify that all NetBackup
binaries are at the same version level.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 145
Message: daemon is already running
Explanation: Another copy of the process is running.
Recommended Action: Terminate the current copy of the process and then restart
the process.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 146
Message: cannot get a bound socket
Explanation: The service or daemon did not bind to its socket. A system call fails
when the daemon (UNIX) or service (Windows) attempts to bind to its configured
port number. This error is usually caused when another process acquired the port
before the daemon or service started.
Recommended Action: Do the following, as appropriate:
■
Examine the NetBackup Problems and All Log Entries reports.
■
Create bprd and bpdbm debug log directories and retry the operation. Check
the resulting logs to see the system error message that resulted from the attempt.
If another process has the port, use other system commands to determine the
process. Based on this research, either change the port number in your services
file or map or terminate the process that acquired the port.
138
NetBackup status codes
NetBackup status codes
On UNIX, another possible cause for this error is the use of the kill command
to terminate bprd or bpdbm. To stop bpdbm, use the
/usr/openv/netbackup/bin/bpdbm -terminate command. Use of the kill
command to stop these processes can leave them unable to bind to their
assigned ports the next time they are started.
To identify a bprd or a bpdbm problem, look for lines similar to the following in
the debug log for the respective process:
<16> getsockbound: bind() failed, Address already in use (114)
<32> listen_loop: cannot get bound socket. errno = 114
<4> terminate: termination begun...error code = 146
Similar entries can appear in the reports.
■
If the problem persists longer than 10 minutes, it may be necessary to restart
the server.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 147
Message: required or specified copy was not found
Explanation: The requested copy number of a backup or an archive image cannot
be found.
Recommended Action: Correct the request to specify a copy number that does
exist.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 148
Message: daemon fork failed
Explanation: A NetBackup service did not create a child process due to an error
that was received from the system. This error is probably an intermittent error that
is based on the availability of resources on the system.
Recommended Action: Do the following, as appropriate:
■
Restart the service at a later time and investigate the system problems that limit
the number of processes.
■
On Windows systems, check the Event Viewer Application and System logs.
139
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 149
Message: master server request failed
Explanation: None
Recommended Action: None
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 150
Message: termination requested by administrator
Explanation: Using the GUI, an administrator terminates an active process. The
job status changes to FAILED.
Recommended Action: None
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 152
Message: required value not set
Explanation: An incomplete request was made to the bpdbm process (on UNIX),
or the NetBackup Database Manager service (on Windows). This error usually
occurs because different versions of software are used together.
Recommended Action: Do the following, as appropriate:
■
Verify that all software is at the same version level.
■
For detailed troubleshooting information, create bpdbm and admin debug log
directories and retry the operation. Check the resulting debug logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 153
Message: server is not the master server
Explanation: This status code is reserved for future use.
140
NetBackup status codes
NetBackup status codes
Recommended Action: None
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 154
Message: storage unit characteristics mismatched to request
Explanation: A backup was tried and the storage unit selected for use had the
characteristics that were not compatible with the backup type.
Recommended Action: Verify that the characteristics of the selected storage unit
are appropriate for the attempted backup.
■
For a NetBackup Snapshot Client, the policy storage unit was set to
Any_available and the off-host backup method was set to Third-Party Copy
Device or NetBackup Media Server. Do not choose Any_available. A particular
storage unit (such as nut-4mm-robot-tl4-0) must be specified when
Third-Party Copy Device or NetBackup Media Server is specified as the
off-host backup method.
■
For an NDMP policy type, verify the following:
■
■
You have defined a storage unit of type NDMP.
■
The NDMP host value matches the host name of the client. For example, if
the NDMP policy specifies toaster as the client, the configuration for the
storage unit must specify toaster as the NDMP host.
■
The media server for the storage unit is running the correct version of
NetBackup.
For a policy type other than NDMP, verify that the policy specifies a media
manager or disk type storage unit.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 155
Message: disk is full
Explanation: The write to the catalog file failed because the disk that contains the
catalog database is full, or the track log folder is full.
Recommended Action: Free up space on the disks where NetBackup catalogs
reside or where the track log folder resides and retry the operation.
141
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 156
Message: snapshot error encountered
Explanation: The following are possible causes of this status code:
■
Errors related to VMware
■
An error related to the Enterprise Vault Agent. The following errors can result
in a status code 156:
■
VSS_E_BAD_STATE snapshot error
■
VSS_E_INSUFFICIENT_STORAGE snapshot error
■
A snapshot-backup related error regarding Windows Open File Backup or
Snapshot Client.
■
Multiple volumes are mounted to the same mount point
Recommended Action: Do the following, as appropriate:
■
For NetBackup for VMware:
■
NetBackup cannot obtain the volume ID of a drive
NetBackup may not be able to obtain the volume ID of a drive. In that case,
none of the virtual machine drives are backed up. The backup fails with
NetBackup status code 156.
The drive may be down.
■
A backup of the virtual machine is already active
You cannot run more than one backup per virtual machine at a time. If you
start a second backup of the virtual machine while the first backup is active,
the second job fails with a status 156.
Recommended action: Wait until the first job completes, then run the second
one.
■
Cannot find virtual machine name
NetBackup cannot find the host name or VM display name of a virtual
machine that is listed in the backup policy. The detailed status log may
include the following error message:
Critical bpbrm (pid=<pid number>) from client <client name>:
FTL - snapshot creation failed, status 156.)
If the virtual machines do not have static IP addresses, you can configure
NetBackup to identify virtual machines by their VM display names or UUIDs.
142
NetBackup status codes
NetBackup status codes
Examples of the environments that do not use static IP addresses are
clusters, and the networks that assign IP addresses dynamically.
Note that NetBackup may have been configured to identify virtual machines
by their VM display names. In that case, make sure that the display names
are unique and that they do not contain special characters.
■
The virtual machine is turned off
Through a vCenter server, NetBackup can back up the virtual machines that
are turned off. You must provide credentials for NetBackup to access the
vCenter server.
If NetBackup uses credentials for an ESX server instead of vCenter, it may
not be able to identify a turned off virtual machine. Note the following:
■
■
If the policy uses VM host name or VM DNS name as the Primary VM
identifier, NetBackup may not find the virtual machine. The backup fails.
■
If the policy uses VM display name or VM UUID as the Primary VM
identifier, NetBackup can identify the virtual machine. The backup
succeeds.
The virtual machine has one or more independent disks and is in a suspended
state
If a virtual machine with independent disks is in a suspended state, snapshot
jobs fail. Messages similar to the following appear in the job details log:
01/12/2015 17:11:37 - Critical bpbrm (pid=10144) from client
<client name>: FTL - VMware error received: Cannot take a
memory snapshot, since the virtual machine is configured with
independent disks.
More information is available in the following VMware article:
http://kb.vmware.com/kb/1007532
As a workaround, change the state of the virtual machine to on or off, and
rerun the backup.
Note: Data on independent disks cannot be captured with a snapshot. The
rest of the virtual machine data is backed up.
■
The virtual machine's disk is in raw mode (RDM)
The RDM is ignored (not backed up) and any independent disk is recreated
but empty.
■
The attempt to create a snapshot exceeded the VMware timeout
If the attempt to create a snapshot of the virtual machine exceeds the VMware
timeout of 10 seconds, the snapshot fails with NetBackup status 156. This
143
NetBackup status codes
NetBackup status codes
144
timeout may occur if the virtual machine is configured with a large number
of volumes. Note that the timeout may be encountered even if the Virtual
machine quiesce option was disabled.
Do one of the following:
■
Reduce the number of volumes within the virtual machine.
■
Install a NetBackup client on the virtual machine and select another
backup method for the policy (not the VMware snapshot method).
■
The virtual machine has no vmdk file assigned
Virtual machines without vmdk files can occur in a vCenter Site Recovery
Manager (SRM) environment. If a replicated virtual machine has never been
active, it is in passive mode and may have no vmdk file(s).
You can enable the Ignore diskless VMs option on the VMware Advanced
Attributes tab of the policy. If this option is enabled: NetBackup does not
back up a replicated (passive) virtual machine in an SRM environment if that
virtual machine has no vmdk files.
■
The vmdk file has too many delta files
Whenever a VMware snapshot occurs, a delta.vmdk file is created for each
vmdk. If 32 or more such delta files exist for a single vmdk file, a NetBackup
backup of that VM may fail (status 156). The NetBackup Activity Monitor job
details contain messages similar to the following:
02/06/2015 10:33:17 - Critical bpbrm (pid=15799) from
client fl5vm1_2012: FTL - vSphere_freeze: Unable to proceed with
snapshot creation, too many existing delta files(44).
02/06/2015 10:33:17 - Critical bpbrm (pid=15799) from client
fl5vm1_2012: FTL - VMware_freeze: VIXAPI freeze (VMware snapshot)
failed with 25: SYM_VMC_FAILED_TO_CREATE_SNAPSHOT
02/06/2015 10:33:17 - Critical bpbrm (pid=15799) from client
fl5vm1_2012: FTL - vfm_freeze: method: VMware_v2, type: FIM,
function: VMware_v2_freeze
To back up the VM, do the following:
■
Consolidate the VM's snapshots.
In the VMware interface, right-click on the VM and select Snapshot >
Consolidate. For more information, see your VMware documentation.
■
Verify that each of the VM’s vmdk files now has fewer than 32 delta files.
If the snapshot consolidation was not successful, see the following
VMware article for further assistance:
http://kb.vmware.com/kb/1004545
■
Rerun the NetBackup backup.
NetBackup status codes
NetBackup status codes
■
VMware snapshot quiesce operation failed
If the NetBackup policy is enabled for virtual machine quiesce (the default),
the VMware snapshot operation in vSphere initiates a quiesce of the virtual
machine. If snapshot quiesce fails, the NetBackup job fails with status 156.
■
For the Enterprise Vault Agent:
See the Troubleshooting section of the NetBackup for Enterprise Vault Agent
Administrator’s Guide.
■
For a Windows Open File Backup Snapshot Provider that uses VSS:
See the Troubleshooting section of one of the following guides:
■
NetBackup for VMware Administrator’s Guide
■
NetBackup for Hyper-V Administrator’s Guide
■
NetBackup Snapshot Client Administrator’s Guide
The VSS cache files may be too small for the number of files being backed up
using VSS.
If bpbkar debug logs are turned on, a message similar to the following appears
in the bpbkar debug log for the backup.
8:51:14.569 AM: [1924.2304] <2> tar_base::V_vTarMsgW: ERR failure reading file: D:\ test.file (WIN32 5: Access is denied.
)
8:51:14.569 AM: [1924.2304] <4> tar_base::V_vTarMsgW: INF - tar
message received from dos_backup::tfs_readdata
8:51:14.569 AM: [1924.2304] <2> tar_base::V_vTarMsgW: ERR Snapshot Error while reading test.file
8:51:14.569 AM: [1924.2304] <4> tar_base::V_vTarMsgW: INF - tar
message received from tar_backup::nextfile_state_switch
8:51:14.569 AM: [1924.2304] <2> tar_base::V_vTarMsgW: FTL Backup operation aborted!
8:51:14.569 AM: [1924.2304] <2> tar_base::V_vTarMsgW: INF Client completed sending data for backup
8:51:14.569 AM: [1924.2304] <2> tar_base::V_vTarMsgW: INF - EXIT
STATUS 156: snapshot error encountered
To increase the VSS cache size by using the Shadow Copy configuration in
Windows, do the following in the order listed:
■
In Windows, right-click My Computer and select Manage.
■
In the console tree, right-click Shared Folders, select All Tasks, and select
Configure Shadow Copies.
■
Select the volume where you want to make changes, and then select
Settings.
145
NetBackup status codes
NetBackup status codes
■
■
■
146
In the Settings dialog box, change the Maximum Size setting to either of
the following: No Limit or a size large enough to suit the requirements of
your installation and your usage of VSS.
For backups using Snapshot Client and the NAS_Snapshot method, with
or without SnapVault:
■
If the backup fails with status code 156, consult the bpfis legacy log, in
/usr/openv/netbackup/logs (UNIX) or install_path\NetBackup\logs
(Windows). If the bpfis directory does not already exist, you must create it
and rerun the job.
If necessary, increase the logging level and retry the job.
See "About logs" in the NetBackup Logging Reference Guide.
■
On Windows clients, when restoring files from a backup that is made with
the NAS_Snapshot method, log into the NetBackup Client Service as the
Administrator account, not as the local system account. Otherwise, the
backup fails with status 156.
■
In Windows Services, double-click the NetBackup Client Service.
■
Then check the Log On tab: if the service is not logged on as
Administrator, stop the service.
■
Change the logon to the Administrator account and restart the service.
■
Retry the restore.
For other NetBackup Snapshot Client issues:
■
The file system that is specified as a snapshot source is not mounted. In this
case, you may see the following in the /usr/openv/netbackup/logs/bpfis
log:
17:12:51 bpfis: FTL - snapshot creation failed, status 156
17:12:51 bpfis: INF - EXIT STATUS 156: snapshot error
encountered
And the following in the /usr/openv/netbackup/logs/bpfis log:
17:12:51 onlfi_vfms_logf: INF - cannot snap_on, err: 5
17:12:51 delete_mount_point: INF - Deleted mount point
/tmp/__jody_test:20958
17:12:51 onlfi_freeze: FTL - VfMS error 11; see following
messages:
17:12:51 onlfi_freeze: FTL - Fatal method error
17:12:51 onlfi_freeze: FTL - vfm_freeze: method: nbu_snap, type:
FIM, function: nbu_snap_freeze
NetBackup status codes
NetBackup status codes
147
17:12:51 onlfi_freeze: FTL - VfMS method error 5; see following
message:
17:12:51 onlfi_freeze: FTL - nbu_snap_freeze: Cannot turn on
snapshot; snapshot source=/opt, cache=/dev/rdsk/c1t3d1s0, snap
error=5
17:12:51 onlfi_thaw: WRN - / is not frozen
Make sure that the file system that is specified for the snapshot source has
been mounted.
■
The file system that is specified as the snapshot source does not correspond
to the file system that contains the actual files (as opposed to symbolic links
to the files). The mounted file system for the snapshot source must contain
the actual files, not symbolic links. If items in the file list, such as /oracle,
is a symbolic link to /export/home/oracle, the snapshot source must specify
/export, or /export/home, not /oracle.
■
VxVM is selected as the snapshot method but the snapshot source is not
configured over a Veritas Volume Manager (VxVM) volume. In this case,
you may see the following in the /usr/openv/netbackup/logs/bpfis log:
17:12:51 bpfis: FTL - snapshot creation failed, status 156
17:12:51 bpfis: INF - EXIT STATUS 156: snapshot error
encountered
And something like the following in the /usr/openv/netbackup/logs/bpfis
log:
17:12:51 onlfi_vfms_logf: INF - vxvm_freeze: Snapshot source
/cockpit1 on device /dev/dsk/c1t0d0s6 is not on a VxVM volume
17:12:51 delete_mount_point:
INF - Deleted mount point
/tmp/_cockpit1_coc_group1:3518
17:12:51 onlfi_freeze: FTL - VfMS error 11; see following
messages:
17:12:51 onlfi_freeze: FTL - Fatal method error
17:12:51 onlfi_freeze: FTL - vfm_freeze: method: vxvm, type:
FIM, function: vxvm_freeze
17:12:51 onlfi_freeze: FTL - VfMS method error 9; see following
message:
17:12:51 onlfi_freeze: FTL - vxvm_freeze: Snapshot source
/cockpit1 on device /dev/dsk/c1t0d0s6 is not on a VxVM volume
17:12:51 onlfi_thaw: INF - fim=vxvm
17:12:51 onlfi_thaw: WRN - /cockpit1 is not frozen
Make sure that the snapshot source is configured over a Veritas Volume
Manager (VxVM) volume.
NetBackup status codes
NetBackup status codes
■
148
VxVM was selected as the snapshot method, but a Veritas Volume Manager
snapshot mirror of the snapshot source volume had not been created before
you ran the backup, or another backup is currently running that uses the
snapshot mirror. In either case, you may see the following in the
/usr/openv/netbackup/logs/bpfis log:
17:12:51 onlfi_freeze: FTL
messages:
17:12:51 onlfi_freeze: FTL
17:12:51 onlfi_freeze: FTL
FIM, function: vxvm_freeze
17:12:51 onlfi_freeze: FTL
message:
17:12:51 onlfi_freeze: FTL
available snapshot mirror
- VfMS error 11; see following
- Fatal method error
- vfm_freeze: method: vxvm, type:
- VfMS method error 3; see following
- find_ready_snapshot: Cannot find
See the NetBackup Snapshot Client Administrator’s Guide for information
on how to create a snapshot mirror on the client before you run the backup.
■
VxVM was selected as the snapshot method, and a Veritas Volume Manager
snapshot mirror of the snapshot source volume has been created. However,
two different backup jobs (A and B) try to back up the same volume (for
example, vol01), but job A starts before job B. After an available snapshot
mirror is found, a brief pause occurs before the snapshot is formed. Job B
that runs slightly behind job A may try to create a snapshot of the snapshot
mirror immediately before job A creates the snapshot and gets the lock on
it.
In this case, you may see the following in the
/usr/openv/netbackup/logs/bpfis log:
17:12:51 onlfi_freeze: FTL - VfMS error 11; see following
messages:
17:12:51 onlfi_freeze: FTL - Fatal method error
17:12:51 onlfi_freeze: FTL - vfm_freeze: method: vxvm, type:
FIM, function: vxvm_freeze
17:12:51 onlfi_freeze: FTL - VfMS method error 3; see following
message:
17:12:51 onlfi_freeze: FTL - vxvm_freeze: Command failed with
status=11: /usr/sbin/vxassist -g rootdg snapshot vol01
VfMSCAAu7a4Uw </dev/null>/var/tmp/VfMSAAAs7a4Uw
2>/var/tmp/VfMSBAAt7a4Uw
The job that was unable to get a lock (job B in the preceding example) fails,
and must be run again.
NetBackup status codes
NetBackup status codes
■
149
When you use nbu_snap as a snapshot method, you may have stale
snapshots if status code 156 occurs with the following messages in the
/usr/openv/netbackup/logs/bpfis log. (Stale snapshots are those that
nbu_snap did not automatically delete.)
17:12:51 onlfi_freeze: FTL - VfMS error 11; see following
messages:
17:12:51 onlfi_freeze: FTL - Fatal method error
17:12:51 onlfi_freeze: FTL - vfm_freeze: method: nbu_snap, type:
FIM, function: nbu_snap_freeze
17:12:51 onlfi_freeze: FTL - VfMS method error 5; see following
message:
17:12:51 onlfi_freeze: FTL - nbu_snap_freeze: Cannot turn on
snapshot; snapshot source=/oracle/ufs_r,
cache=/dev/rdsk/c4t1d11s4,snap error=11
■
Look for stale snapshots by running the
/usr/openv/netbackup/bin/driver/snaplist command when there are
no active backups running. If the snaplist command shows cache entries,
there are stale snapshots. Nothing is displayed if there are no stale
snapshots.
Example snaplist output:
id
43
ident
6515
size
8390970
cached
0
minblk
0
0
err time
11/16/00 13:31:36
device = /dev/rdsk/c1t6d0s0
cache = /dev/rdsk/c1t6d0s7
■
Use the snapoff command to remove the stale snapshot, as follows:
/usr/openv/netbackup/bin/driver/snapoff id
Where id is the ID from the snaplist output (such as 43 in the preceding
example).
■
If a backup using the VxFS_Checkpoint snapshot method failed, the
NetBackup bpbkar process should automatically remove the clone.
Sometimes, however, bpbkar is unable to remove the clone. In this case,
you may see messages such as the following in the
/usr/openv/netbackup/logs/bpfis log:
15:21:45.716 [4236] <4> create_mount_point: INF - Created mount
point /tmp/_vtrax_test:4236
NetBackup status codes
NetBackup status codes
150
15:21:45.869 [4236] <2> onlfi_vfms_logf: INF - vxfs clone handle
: 9600344
15:21:45.870 [4236] <2> onlfi_vfms_logf: INF VxFS_Checkpoint_freeze: Cannot create checkpoint; status=17
15:21:45.872 [4236] <4> delete_mount_point: INF - Deleted mount
point /tmp/_vtrax_test:4236
15:21:45.873 [4236] <32> onlfi_freeze: FTL - VfMS error 11; see
following messages:
15:21:45.873 [4236] <32> onlfi_freeze: FTL - Fatal method error
was reported
15:21:45.873 [4236] <32> onlfi_freeze: FTL - vfm_freeze: method:
VxFS_Checkpoint, type: FIM, function: VxFS_Checkpoint_freeze
15:21:45.873 [4236] <32> onlfi_freeze: FTL - VfMS method error
17; see following message:
15:21:45.874 [4236] <32> onlfi_freeze: FTL VxFS_Checkpoint_freeze: Cannot create checkpoint; status=17
Remove the clone as follows.
Note: If the checkpoint is not removed, you cannot use VxFS_Checkpoint
to back up any data in the file system where the checkpoint is mounted.
■
List the name of the checkpoint by entering the following VxFS command:
/usr/lib/fs/vxfs/fsckptadm list /file_system
Where file_system is the name of the file system where the checkpoint is
mounted. A sample output follows. In this example, /vtrax_test is the file
system and fi_ckpt is the name of the checkpoint.
/vtrax_test
fi_ckpt:
ctime = Mon Nov 12 10:08:13 2001
mtime = Mon Nov 12 10:08:13 2001
flags = largefiles
■
Remove the checkpoint by entering the following:
/usr/lib/fs/vxfs/fsckptadm remove checkpoint /file_system
■
If the checkpoint cannot be removed, unmount the checkpoint and retry the
first step in this procedure.
NetBackup status codes
NetBackup status codes
■
151
If a snapshot backup fails using TimeFinder, ShadowImage, or BusinessCopy
method, there may be a VxVM clone left over from a previous backup. You
may see messages similar to the following in the
/usr/openv/netbackup/logs/bpfis log:
19:13:07.686 [14981] <2> onlfi_vfms_logf: INF - do_cmd: Command
failed with status=20: /usr/openv/netbackup/bin/bpdgclone -g
wil_test -n vol01 -f /var/tmp/HDSTFCAAs7aOqD </dev/null
>/var/tmp/VfMSAAAq7aOqD 2>/var/tmp/VfMSBAAr7aOqD
19:13:07.687 [14981] <2> onlfi_vfms_logf: INF - --- Dumping file
/var/tmp/VfMSAAAq7aOqD (stdout):
19:13:07.687 [14981] <2> onlfi_vfms_logf: INF - --- End of file
/var/tmp/VfMSAAAq7aOqD
19:13:07.687 [14981] <2> onlfi_vfms_logf: INF - --- Dumping file
/var/tmp/VfMSBAAr7aOqD (stderr):
19:13:07.687 [14981] <2> onlfi_vfms_logf: INF clone group
and volume already exists
19:13:07.688 [14981] <2> onlfi_vfms_logf: INF - --- End of file
/var/tmp/VfMSBAAr7aOqD
NetBackup automatically creates VxVM clones for TimeFinder, ShadowImage,
or BusinessCopy backups of the data that is configured over volumes. After
the backup has completed, NetBackup removes the VxVM clone. In this
case, a system crash or restart may have prevented the removal. Remove
the clone as follows.
(Do the following on the client or alternate client, depending on the type of
backup.)
■
When no backups are running, use the following VxVM command to list any
clones: vxdg list
The clone name is of the form clone_disk_group_clone.
■
To remove the clone, enter the following:
/usr/openv/netbackup/bin/bpdgclone -g disk_group -n volume -c
For example:
/usr/openv/netbackup/bin/bpdgclone -g wil_test -n vol01 -c
Where wil_test is the name of the disk group and volo1 is the name of
the VxVM volume.
For more information on how to remove a VxVM clone, see the NetBackup
Snapshot Client Administrator’s Guide. For vxdg, see the Veritas Volume
Manager Administrator’s Guide.
NetBackup status codes
NetBackup status codes
■
Before running the backup again, resynchronize the primary disk with the
secondary disk. For assistance, see the NetBackup Snapshot Client
Administrator’s Guide.
■
If a snapshot backup fails using the FlashSnap or VVR snapshot method, a
VxVM snapshot may be left over from a previous backup. You may see
messages similar to the following in the /usr/openv/netbackup/logs/bpfis
log:
152
14:41:15.345 [22493] <32> onlfi_freeze: FTL - VfMS error 11; see
following messages:
14:41:15.345 [22493] <32> onlfi_freeze: FTL - Fatal method error
was reported
14:41:15.345 [22493] <32> onlfi_freeze: FTL - vfm_freeze_commit:
method: FlashSnap, type: FIM, function: FlashSnap_freeze_commit
14:41:15.345 [22493] <32> onlfi_freeze: FTL - VfMS method error
8; see following message:
14:41:15.345 [22493] <32> onlfi_freeze: FTL vxvm__find_ready_snapshot: Cannot find available snapshot mirror
NetBackup automatically creates VxVM snapshots for backups of the data
that is configured over volumes. After the backup completes, NetBackup
removes the VxVM snapshot. In this case, a system crash or restart may
have prevented the removal. Remove the snapshot as follows.
For FlashSnap:
(Do the following on the client or alternate client, depending on the type of
backup.)
■
Find the VxVM disk group:
vxdg list
The format of the disk group name is as follows:
primaryhost_diskgroup_split
If vxdg list does not show the disk group, the group might have been
deported. You can discover all the disk groups including deported ones by
entering:
vxdisk -o alldgs list
The disk groups that are listed in parentheses are not imported on the local
system.
■
Deport the VxVM disk group:
NetBackup status codes
NetBackup status codes
153
vxdg deport primaryhost_diskgroup_split
Enter the following on the primary (original) client:
■
Import and join the VxVM disk group:
vxdg import primaryhost_diskgroup_split
vxrecover -g primaryhost_diskgroup_split -m
vxdg join primaryhost_diskgroup_split diskgroup
■
Start the volume and snap back the snapshot volume:
vxvol -g primaryhost_diskgroup_split start
SNAP_diskgroup_volume
vxassist snapback SNAP_diskgroup_volume
For VVR, on the alternate client:
■
Enter the following to display unsynchronized mirror disks:
vxprint -g diskgroup
■
Enter the following to resynchronize the mirror disks:
vxassist -g diskgroup -v volume snapback
■
When you use a snapshot method such as VxFS_Checkpoint to back up a
Veritas File System (VxFS), the backup fails if the VxFS license has expired.
Messages such as the following appear in the /usr/openv/netbackup/logs/bpfis
log:
11:37:42.279 [24194] <2> onlfi_vfms_logf: INF VxFS_Checkpoint_freeze: Cannot open checkpoint; status=100
11:37:42.283 [24194] <4> delete_mount_point: INF - Deleted mount
point /tmp/_vrts_frzn_img__test1_24194
11:37:42.283 [24194] <32> onlfi_freeze_fim_fs: FTL - VfMS error
11; see following messages:
11:37:42.283 [24194] <32> onlfi_freeze_fim_fs: FTL - Fatal
method error was reported
11:37:42.284 [24194] <32> onlfi_freeze_fim_fs: FTL - vfm_freeze:
method: VxFS_Checkpoint, type: FIM, function:
VxFS_Checkpoint_freeze
11:37:42.284 [24194] <32> onlfi_freeze_fim_fs: FTL - VfMS method
error 100; see following message:
11:37:42.284 [24194] <32> onlfi_freeze_fim_fs: FTL VxFS_Checkpoint_freeze: Cannot open checkpoint; status=100
NetBackup status codes
NetBackup status codes
154
Obtain a new VxFS license and retry the backup.
■
If the backup is enabled for instant recovery with either the VxVM or VVR
snapshot method, your VxVM mirrors may not be properly configured. In this
case, you may see the following in the /usr/openv/netbackup/logs/bppfi
log on the client (when verbose mode is set high).
13:43:39.095 [16375] <2> onlfi_vfms_logf: INF - Executing
command:
13:43:39.095 [16375] <2> onlfi_vfms_logf: INF /usr/sbin/vxprint -g rootdg -q -t -e 'assoc="pfi_concat"'
</dev/null >/var/tmp/VfMSAA Arja4.F 2>/var/tmp/VfMSBAAsja4.F
13:43:39.215 [16375] <2> onlfi_vfms_logf: INF pfi_find_snapdone: 0 SNAPDONE plexes found
13:43:39.215 [16375] <2> onlfi_vfms_logf: INF - Executing
command:
13:43:39.215 [16375] <2> onlfi_vfms_logf: INF /usr/sbin/vxassist -g rootdg snapprint pfi_concat </dev/null
>/var/tmp/VfMSAAArja4.F 2>/var/tmp/VfMSBAAsja4.F
13:43:39.512 [16375] <2> onlfi_vfms_logf: INF - 0 active plexes
for /rootdg/pfi_concat: 0 are PFI 0 non-PFI
13:43:39.512 [16375] <2> onlfi_vfms_logf: INF pfi_find_active.3309: exiting with VXVM_E_SYS = 3
13:43:39.512 [16375] <2> onlfi_vfms_logf: INF pfi_snapshot.3866: No PFI snapshot. err= 3
Configure the VxVM mirrors as described in the Instant Recovery chapter
of the NetBackup Snapshot Client Administrator’s Guide.
■
When you use the VxFS_Checkpoint snapshot method, the backup fails if
the client’s file system does not support mountable checkpoints using the
Storage Checkpoint feature. Messages such as the following appear in the
/usr/openv/netbackup/logs/bpfis log:
14:54:27.530 [23563] <32> onlfi_freeze_fim_fs: FTL - VfMS error
11; see following messages:
14:54:27.530 [23563] <32> onlfi_freeze_fim_fs: FTL - Fatal
method error was reported
14:54:27.530 [23563] <32> onlfi_freeze_fim_fs: FTL - vfm_freeze:
method: VxFS_Checkpoint, type: FIM, function:
VxFS_Checkpoint_freeze 14:54:27.531 [23563] <32>
onlfi_freeze_fim_fs: FTL - VfMS method error 2; see following
message:
14:54:27.531 [23563] <32> onlfi_freeze_fim_fs: FTL - open_ckpt:
NetBackup status codes
NetBackup status codes
Cannot open checkpoint on /mnt_vxvm/2G_concat :
fsckpt_get_api_version returns 1; mountable checkpoints not
supported with this version
Do one of the following:
■
Upgrade the client file system to a version that supports mountable VxFS
Storage Checkpoints.
■
Configure the policy with a snapshot method that supports the client’s
current file system.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 157
Message: suspend requested by administrator
Explanation: Status code 157 is an informational message, which indicates that
the administrator suspended the job from the Activity Monitor. The job is in the
suspended state in the Activity Monitor. It can be resumed from the last checkpoint
by the administrator.
Recommended Action: The administrator can resume the job from the last
checkpoint from the Activity Monitor.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 158
Message: failed accessing daemon lock file
Explanation: The process cannot lock its lock file because an error was received
from a system call. This lock file synchronizes process activities (for example, it
prevents more than one daemon from running at a time).
Recommended Action: Do the following, as appropriate:
■
Examine the NetBackup error log to determine why the system call failed. Then
correct the problem. It may be a permission problem.
■
If the error log does not show the error, create a debug log directory for bprd
or bpdbm (depending on which process encountered the error). Increase the
unified logging level if nbpem, nbjm, or nbrb encountered the error. Use the
vxlogcfg command as explained in the following topic:
See "About unified logging" in the NetBackup Logging Reference Guide.
Retry the operation and check the resulting debug log.
155
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 159
Message: licensed use has been exceeded
Explanation: A configuration limit was exceeded.
For example, a job fails with this error code if a policy is set up that specifies the
following:
■
A storage unit that is on a SAN media server
■
A client that is not the SAN media server itself
SAN media servers can only back up themselves.
This status code is used when the creation of a storage unit on a SAN media server
fails because On demand only is not selected. On demand only is required for
storage units on a SAN media server.
Recommended Action: To determine the cause of the error, examine the
NetBackup All Log Entries report for the command that was run. See also the Activity
Monitor details for informative messages.
If the job fails on a SAN media server storage unit, ensure that only the local client
is specified in the policy. If remote clients are specified in the policy, do one of the
following: remove them and place them in a policy that specifies a different storage
unit or change the storage unit for that policy.
If you want to back up remote clients by using the SAN media server, you can
purchase a regular NetBackup media server license.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 160
Message: authentication failed
Explanation: One of the following occurs:
■
Two systems try to authenticate one another.
■
An initialization of the authentication libraries fails.
■
Communication to the authentication daemon (nbatd) fails.
■
Authentication of saved credentials fails.
Recommended Action: Do the following as appropriate in the order listed:
156
NetBackup status codes
NetBackup status codes
■
Add back the names that were removed and retry the operation.
■
Create the following debug log directories for the processes that are involved
in authentication between NetBackup systems:
■
Server: bprd, bpdbm, and bpcd.
■
Client: bpbackup, bprestore, and bpbkar.
Retry the operation and check the logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 161
Message: Evaluation software has expired.
Explanation: The time that was allowed for the NetBackup evaluation software
ended.
See www.veritas.com for ordering information.
Recommended Action: Obtain a licensed copy of NetBackup.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 162
Message: incorrect server platform for license
Explanation: The platform identifier in the license key does not match the platform
type on which the key was installed.
Recommended Action: Ensure that you use a license key that is intended for the
platform on which you plan to install.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 163
Message: media block size changed prior resume
Explanation: Status code 163 is an informational message. It indicates that the
media block size was changed before a backup job from the last checkpoint
resumed. Since the media block size must be consistent, the job was restarted from
the beginning.
157
NetBackup status codes
NetBackup status codes
Recommended Action: Check the Activity Monitor job details for the job ID of the
restarted job.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 164
Message: unable to mount media because it is in a DOWN, or otherwise not
available
Explanation: A restore was tried and the volume required for the restore was in
a DOWN drive in a robot. Or, the slot is empty that should contain the volume.
Recommended Action: Do the following, as appropriate:
■
If volume is in a DOWN drive, remove it and place it in its designated slot. Then,
retry the restore.
■
If the volume is in the wrong slot, use a robot inventory option to reconcile the
contents of the robot with the volume configuration.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 165
Message: NB image database contains no image fragments for requested backup
id/copy number
Explanation: A restore was tried and NetBackup has no record of the fragments
that are associated with the backup ID that has the files.
Recommended Action: Check the NetBackup Problems report for additional
information about the error. For detailed troubleshooting information, create a debug
log directory for either bpdm or bptm (whichever applies) and retry the operation.
Check the resulting debug log.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 166
Message: backups are not allowed to span media
Explanation: An end of media (EOM) was encountered while the backup image
was written. The backup was terminated because the NetBackup
DISALLOW_BACKUPS_SPANNING_MEDIA option was present in bp.conf (on UNIX) or
in the registry (on Windows). The backup is retried automatically with a different
158
NetBackup status codes
NetBackup status codes
volume if the backup tries attribute allows it in the NetBackup global attribute
configuration.
Recommended Action: None
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 167
Message: cannot find requested volume pool in EMM database
Explanation: A backup to a nonrobotic drive was tried and the tape manager
(bptm) cannot find or add the specified volume pool.
Recommended Action: Verify the Media and Device Management volume
configuration. Check the NetBackup Problems report for more information about
the error. For detailed troubleshooting information, create a bptm debug log directory
and retry the operation. Check the resulting debug log.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 168
Message: cannot overwrite media, data on it is protected
Explanation: A backup was tried to a volume that cannot be overwritten because
it contains the data that by default NetBackup does not overwrite. (This data includes
items such as tar, cpio, and ANSI.)
Recommended Action: Replace the volume with a new one or set the NetBackup
ALLOW_MEDIA_OVERWRITE option to the appropriate value.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 169
Message: Media ID is either expired or will exceed maximum mounts
Explanation: A backup or a catalog backup was tried and the volume selected for
use has reached its maximum number of mounts. The maximum number is specified
in the Media and Device Management 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.
Recommended Action: If the volume was suspended, wait until it expires and
then replace it. For NetBackup catalog backups, replace the media.
159
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 170
Message: third party copy backup failure
Explanation: Usually indicates a problem with the 3pc.conf file or the mover.conf
file. (For detailed causes, see recommended actions.)
For more information on these files, see the NetBackup Snapshot Client
Configuration document available at the following location:
https://www.veritas.com/content/support/en_US/article.TECH51377.html
For help accessing this document, see Snapshot Client Assistance in the NetBackup
Snapshot Client Administrator’s Guide.
Recommended Action: Do the following, as appropriate:
■
If a non third-party copy device is listed in 3pc.conf file, correct it or remove
the non third-party copy device entry.
■
If an incorrect LUN is specified in the 3pc.conf file or the device does not exist,
correct the 3pc.conf file as appropriate.
■
If an appropriate mover.conf file (with or without file name extension) cannot
be found, the /usr/openv/netbackup/logs/bptm log may show the following:
09:51:04 [22281] <2> setup_mover_tpc: no
mover.conf.vertex_std_tpc or mover.conf file exists, cannot
perform TPC backup
09:51:04 [22281] <16> bptm: unable to find or communicate with
Third-Party-Copy mover for policy vertex_std_tpc
Make sure that an appropriate mover.conf file exists in /usr/openv/netbackup
on the media server. This file can be any of the following:
■
mover.conf.policy_name file, where policy_name exactly matches the
name of the policy.
■
mover.conf.storage_unit_name, where storage_unit_name exactly matches
the name of the storage in the Backup Policy Management Policy
attributes dialog box (such as nut-4mm-robot-tl4-0).
■
mover.conf file (no extension) for the configurations that have only one
third-party copy device.
Note that NetBackup looks for an appropriate mover.conf file in the order.
160
NetBackup status codes
NetBackup status codes
■
If the SCSI pass-through path of the third-party copy device, as entered in the
mover.conf file, does not exist, the bptm log may show the following:
09:50:12 [22159] <16> setup_mover_tpc: open of passthru path
/dev/sg/cXtXlX failed, No such file or directory
09:50:12 [22159] <16> bptm: unable to find or communicate with
Third-Party-Copy mover for policy vertex_std_tpc
Correct the SCSI pass-through path of the third-party copy device that is entered
in the mover.conf file.
■
If the third-party copy device returned an error, you may see either of the
following messages in /usr/openv/netbackup/logs/bptm log:
cannot process extended copy error due to truncated sense data,
may be HBA problem
disk error occurred on extended copy command, key = 0x0, asc =
0x0, ascq = 0x0
(where key, asc, and ascq are all zero)
Your host-bus adapter (HBA) and its driver may need to be updated, or
NetBackup Snapshot Client may not support them. The supported host-bus
adapters are listed.
See the NetBackup Release Notes.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 171
Message: media ID must be 6 or less characters
Explanation: An operation that suspends or freezes a media ID (for example,
bpmedia). was tried. The media ID is longer than six alphanumeric characters.
Recommended Action: Retry the command with a valid media ID.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 172
Message: cannot read media header, may not be NetBackup media or is corrupted
Explanation: When you loaded a volume for a backup or restore, the tape manager
(bptm), did not find the expected tape header. This error can mean that a robotic
161
NetBackup status codes
NetBackup status codes
device volume is not in the slot number that is in the Media and Device Management
volume configuration. It also can mean that a read error (I/O error) occurred.
Recommended Action: Do the following, as appropriate:
■
If the volume is in a robot that supports bar codes, verify the robot contents by
using a robot inventory option.
■
If the volume was mounted on a nonrobotic drive, verify that the correct volume
was mounted and assigned.
■
Check the NetBackup Problems report. If it shows a fatal read error, try the
operation again with another drive, if possible.
■
If your configuration has multiple servers or HBAs with access to your tape
services, make sure that the SCSI Reserve or Release is configured correctly.
(Most likely, the tape services configuration is an SSO configuration.)
For more information on the storage server, please see the NetBackup
Administrator’s Guide, Volume II, available from the following location:
http://www.veritas.com/docs/DOC5332
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 173
Message: cannot read backup header, media may be corrupted
Explanation: When the tape manager (bptm) searches for a backup image to
restore, the following occurs: it cannot find the correct backup ID at the position on
the media where NetBackup expected it. This status code can indicate a drive
hardware problem.
Recommended Action: Do the following, as appropriate:
■
Check the NetBackup Problems report for clues as to what caused the error.
■
Try the restore on another drive if possible.
■
For detailed troubleshooting information, create a debug log directory for bptm
and retry the operation. Check the resulting debug log.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 174
Message: media manager - system error occurred
162
NetBackup status codes
NetBackup status codes
Explanation: An abnormal condition caused a tape manager (bptm) or disk manager
(bpdm) failure.
On UNIX, the file list that NetBackup generates for snapshot copy may not have
enough information to restore from the NetBackup tar copy. For example, block
number information is not correct because the NetBackup tar copy is not yet created.
Recommended Action: Do the following, as appropriate:
■
Check the NetBackup Problems report to see if it shows the cause of the
problem. If you see a Problems report message similar to the following, save
all logs and contact Veritas Technical Support:
attempted to write 32767 bytes, not a multiple of 512
■
On UNIX, if this error occurs during a restore, the tape drive may be incorrectly
configured. It may be configured to write in fixed-length mode when it should
write in variable length mode.
Verify your drive’s configuration by comparing it to what is recommended in the
NetBackup Device Configuration Guide.
If your configuration incorrectly specifies fixed-length mode, change it to variable
length mode and suspend the media that were written on that device. The images
that were written to those media may be restorable (platform dependent), but
single file restores are likely to fail.
■
If the problem occurs with a particular client only, verify that the client binaries
are correct, especially for bpcd.
■
If you can read or write any other images on this media, check the following
reports for clues:
■
■
Images on Media report
■
Media Contents report
Verify the following:
■
The media, by using the NetBackup image verify option.
■
That you used the correct media type for the device.
■
Check the system or the console log for errors (on UNIX) or the Event Viewer
Application log (on Windows).
■
For detailed debug information, create a debug log directory for either bptm or
bpdm (whichever applies) and retry the operation. Check the resulting debug
log.
On UNIX, if the bptm debug log shows an error similar to the following, the tape
drive is configured to write in fixed-length mode rather than variable length mode.
163
NetBackup status codes
NetBackup status codes
00:58:54 [2304] <16> write_data: write of 32768 bytes indicated
only 29696 bytes were written, errno = 0
The image being written encountered the end-of-media.
■
If the backup was configured for an OpenStorage disk storage unit, the
OpenStorage vendor's plug-in may not be installed on all media servers in the
storage unit's media server list. Either install the vendor plug-in on all of the
media servers or remove from the list the servers that do not have the plug-in
installed.
■
On UNIX, if this error occurs during a restore, refresh the Backup, Archive,
and Restore client console and retry the restore. This action refreshes the file
list displayed in the client console and passes the correct information about the
selected files.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 175
Message: not all requested files were restored
Explanation: When the bptm or the bpdm process restores files from an image, it
detected a fatal error condition and terminated the restore before it completed.
Under normal circumstances, this error should not occur.
Recommended Action: Do the following, as appropriate:
■
Check the NetBackup Problems report and the status lot or the progress log on
the client for additional information about the error.
■
For detailed troubleshooting information, create a debug log directory for either
bptm or bpdm (whichever applies) and retry the operation. Check the resulting
debug log.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 176
Message: cannot perform specified media import operation
Explanation: The tape manager (bptm) detected an error condition when it tried
to import a specific backup image.
Possible reasons for this error are as follows:
■
Media ID is already active in the NetBackup media catalog on this server
164
NetBackup status codes
NetBackup status codes
■
Media ID is not in the volume configuration
■
Fatal tape manager (bptm) error occurred
■
Total image was not obtained from Phase 1 of import
■
The barcode and media ID do not match in the volume database. One possible
reason for a mismatch is when using tapes previously written by a different
barcode, labels are placed into an ACSLS library using a new barcode label.
Another possible reason is when the administrator attempts to change the media
ID field (usingvmchange) to match the RVSN. When the inventory is updated,
the barcode and media ID are synchronized.
Recommended Action: Check the NetBackup Problems report to find the exact
cause of the failure and try the following:
■
If the media ID is already active, duplicate all images on the original media ID
to another volume. Then, manually expire the original media and redo the import.
■
If the media ID is not present in the volume configuration, add it.
■
If you received a fatal bptm error, verify that the following are active: the
NetBackup Volume Manager (vmd) on UNIX or the NetBackup Volume Manager
on Windows.
■
If the entire image is not present, perform import phase 1 on the media IDs that
have the remainder of the image.
■
If the barcode and media ID are a mismatch, use a barcode label that matches
the recorded media ID. Tapes can then be mounted in a drive with AVRD running
so that the recorded media ID is displayed. Then, a barcode with that label
needs to be placed on the tape.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 177
Message: could not deassign media due to Media Manager error
Explanation: The tape manager (bptm) cannot successfully unassign a media ID.
Recommended Action: Do the following, as appropriate:
■
Check the NetBackup Problems report for the cause of the problem.
■
Verify that the NetBackup Volume Manager (vmd) is active on UNIX or the
NetBackup Volume Manager service is active on Windows.
■
For detailed troubleshooting information, create a debug log directory for bptm
and retry the operation. Check the resulting debug log.
165
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 178
Message: Media ID is not in NetBackup volume pool
Explanation: NetBackup tried a backup of its catalogs and the media ID that was
specified for the catalog backup was not in the NetBackup volume pool. Volumes
for catalog backups must be in the NetBackup volume pool.
Recommended Action: Check the Media and Device Management volume
configuration to verify that the media IDs are present and in the NetBackup volume
pool.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 179
Message: density is incorrect for the media ID
Explanation: An operation such as "list contents" was tried on an invalid media
ID, such as a cleaning tape. Another possibility: a media ID in the NetBackup catalog
backup configuration does not match the media type that was entered in the volume
configuration.
Recommended Action: Check the volume configuration and the NetBackup
catalog backup configuration and correct any problems found.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 180
Message: tar was successful
Explanation: tar returned a successful exit status.
Recommended Action: None
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 181
Message: tar received an invalid argument
Explanation: One of the parameters that was passed to tar was not valid.
166
NetBackup status codes
NetBackup status codes
Recommended Action: Do the following, as appropriate:
■
■
On a UNIX client:
■
Ensure that the nbtar command in /usr/openv/netbackup/bin is the one
provided by NetBackup. If you are in doubt, reinstall it.
■
Check /usr/openv/netbackup/bin/version on the client to verify that the
client is running the correct level software. If the software is not at the correct
level, update the software per the directions in the NetBackup release notes.
On a Windows client, create a tar debug log directory, retry the operation, and
check the log.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 182
Message: tar received an invalid file name
Explanation: tar cannot write to the file that is specified with the -f parameter.
Recommended Action: Do the following, as appropriate:
■
Create a bpcd debug log directory on the client .
■
On a Windows client, create a tar debug log directory.
■
Increase the logging level on the client:
■
■
On a UNIX client, add the VERBOSE option to the
/usr/openv/netbackup/bp.conf file.
■
On PC clients, increase the debug or log level.
See "Changing the logging level on Windows clients" in the NetBackup
Logging Reference Guide.
Rerun the operation, check the resulting debug logs for the parameters that
were passed to tar and contact Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 183
Message: tar received an invalid archive
Explanation: The data that was passed to tar was corrupt.
Recommended Action: Do the following, as appropriate:
167
NetBackup status codes
NetBackup status codes
■
■
If the problem is with a UNIX client, create a /usr/openv/netbackup/logs/tar
debug log directory on the client and rerun the operation.
■
Check the tar debug log file for any error messages that explain the problem.
■
Restart the client to see if it clears the problem.
■
When you finish with your investigation of the problem, delete the
/usr/openv/netbackup/logs/ tar directory on the client.
If the problem is with a Microsoft Windows client, do the following in the order
presented:
■
Create a bpcd debug log directory on the client.
■
On a Windows client, create a tar debug log directory.
■
Increase the debug or log level.
See "Changing the logging level on Windows clients" in the NetBackup
Logging Reference Guide.
■
Rerun the operation and check the resulting debug logs.
■
Restart the client to see if it clears the problem.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 184
Message: tar had an unexpected error
Explanation: A system error that occurred in tar.
Recommended Action: Do the following, as appropriate:
■
■
If the problem is with a UNIX client, create a /usr/openv/netbackup/logs/tar
debug log directory on the client and rerun the operation.
■
Check the tar debug log file for any error messages that explain the problem.
■
Restart the client to see if it clears the problem.
■
When you finish your investigation of the problem, delete the
/usr/openv/netbackup/logs/tar directory on the client.
If the problem is with a Microsoft Windows client:
■
Create a bpcd debug log directory on the client .
■
Increase the debug or log level.
See "Changing the logging level on Windows clients" in the NetBackup
Logging Reference Guide.
168
NetBackup status codes
NetBackup status codes
■
On a Windows client, create a tar debug log directory.
■
Retry the operation and check the resulting debug logs.
■
Restart the client to see if it clears the problem.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 185
Message: tar did not find all the files to be restored
Explanation: The tar file list contained files that were not in the image.
Recommended Action: Do the following, as appropriate:
■
■
If the problem is with a UNIX client:
■
Enable bpcd debug logging by creating the
/usr/openv/netbackup/logs/bpcd directory on the client.
■
Rerun the operation, check the resulting bpcd log file for the parameters that
were passed to nbtar, and contact Technical Support.
If the problem is with a Microsoft Windows client:
■
Create a bpcd debug log directory on the client.
■
Increase the debug or log level.
See "Changing the logging level on Windows clients" in the NetBackup
Logging Reference Guide.
■
On a Windows client, create a tar debug log directory.
■
Retry the operation.
■
Check the resulting debug logs for the parameters that were passed to tar
and contact Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 186
Message: tar received no data
Explanation: NetBackup did not send data to tar.
Recommended Action: Do the following, as appropriate:
■
Retry the operation and check the status or the progress log on the client for
any error messages that reveal the problem.
169
NetBackup status codes
NetBackup status codes
■
Verify that the tape is available and readable.
■
Verify that the drive is in an UP state. Use the Device Monitor.
■
For detailed troubleshooting information:
■
Create a bptm debug log on the server.
■
On a Windows client, create a tar debug log.
■
Retry the operation and check the resulting debug logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 189
Message: the server is not allowed to write to the client’s file systems
Explanation: The client does not allow writes from the server.
Recommended Action: Perform the following to perform restores or install software
from the server:
■
On a UNIX client, delete DISALLOW_SERVER_FILE_WRITES from the
/usr/openv/netbackup/bp.conf file.
■
On a Microsoft Windows client, select Allow server-directed restores on the
General tab in the NetBackup Client Properties dialog box. To display this
dialog box, start the Backup, Archive, and Restore interface on the client and
select NetBackup Client Properties from the File menu.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 190
Message: found no images or media matching the selection criteria
Explanation: A verify, duplicate, or import was tried and no images that matched
the search criteria were found in the NetBackup catalog.
Recommended Action: Change the search criteria and retry.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 191
Message: no images were successfully processed
170
NetBackup status codes
NetBackup status codes
Explanation: One of the following has occurred:
■
A verify, duplicate, Auto Image Replication, automatic import, or import was
tried and failed for all selected images.
■
If the STS_EFILESYSTEM error code appears (error 2060063) for BasicDisk
or AdvancedDisk, the file system is not configured correctly. The Allocation Unit
Size of the NTFS file system is too small for the BasicDisk or AdvancedDisk
data writes. Or, the maximum fragment size that NetBackup configures is too
large.
■
If a backup or duplicate job is configured with a retention level greater than 25
and the storage unit specified in the policy is managed by a media server that
runs a version of NetBackup previous to NetBackup 8.0, the backup jobs
associated with the policy fail.
Recommended Action: Do the following, as appropriate:
■
Check the NetBackup Problems report for the cause of the error. To obtain
detailed troubleshooting information, create an admin debug log directory and
retry the operation. Check the resulting debug log.
■
If the backup or duplicate job failed for a policy configured with a retention level
greater than 25, you can either upgrade the media server to NetBackup 8.0 or
later or set the retention level between 0 and 25. Note that the retention period
for level 25 is always set to expire immediately and this value cannot be changed.
■
If the error was encountered during duplication of backups, check the duplication
progress log to help determine the root cause of the problem.
■
An Auto Image Replication job may cause this error. If the storage lifecycle
policy names or data classifications do not match the originating domain and
the target domain, the import job fails. Failed imports appear in the Problems
report when it is run on the target master server. The image is expired and
deleted during catalog cleanup. Note that the originating domain does not track
failed imports.
More information is available about troubleshooting this problem:
For more information on troubleshooting this problem, please see the About
Troubleshooting Auto Image Replication topic of the NetBackup Troubleshooting
Guide.
■
An automatic import job may cause this error. This job is an import job that
shows a storage lifecycle policy name.
More information is available about troubleshooting this problem:
For more information on troubleshooting this problem, please see the About
Troubleshooting Auto Image Replication topic of the NetBackup Troubleshooting
Guide.
171
NetBackup status codes
NetBackup status codes
■
If a Vault job encountered the error responsible for the duplication, check the
duplicate.log files in your sidxxx directories to determine the root cause:
UNIX:
/usr/openv/netbackup/vault/sessions/vault_name/sidxxx
Windows:
install_path\NetBackup\vault\sessions\vault_name\sidxxx
(where xxx is the session ID)
■
Reduce the maximum fragment size on the storage unit that writes to this file
system. This value is typically less than 20 GB. But you may need to adjust the
maximum fragment size as necessary until the STS_EFILESYSTEM errors no
longer occur. The value is based on how much data that the storage unit writes
to the image.
To change this value, in the NetBackup Administration Console, in the left
pane, expand NetBackup Management > Storage. Then in the right pane,
double-click the storage unit for this file system. In the Change Storage Unit
dialog box, change the value of the Maximum Fragment Size to 20480 MB (20
GB) by checking the Reduce fragment size to checkbox and entering the new
value.
■
Increase the Allocation Unit Size by reconfiguring the file system. This usually
requires that you format the file system, so this action may not be a feasible for
an existing file system. Consider this when you create a new file system for
BasicDisk images or AdvancedDisk images. Because setting this value is
different on each OS file system, refer to the appropriate OS or file system
documentation for instructions.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 192
Message: VxSS authentication is required but not available
Explanation: On one side of a NetBackup network connection, the system requires
VxSS authentication. On the other side of the connection, the other system is not
configured to use VxSS. VxSS authentication is used with the NetBackup Access
Control feature (NBAC). The connection was terminated because VxSS
authentication cannot be completed.
Recommended Action: Make sure that both systems are configured to use
NetBackup Access Control VxSS authentication with each other. Or, make sure
that both systems are not configured to use VxSS with each other. The first thing
to check is the Use VxSS Host properties value on each system. If one is configured
172
NetBackup status codes
NetBackup status codes
for REQUIRED, the other must be configured for REQUIRED or AUTOMATIC. If
one is configured for PROHIBITED, the other must be configured for PROHIBITED
or AUTOMATIC.
See the NetBackup Administrator’s Guide, Volume I, for the following information:
how to set the Access Control-related host properties, and how to configure a
system to use Access Control.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 193
Message: VxSS authentication is requested but not allowed
Explanation: On one side of a NetBackup network connection, the system requires
VxSS authentication. The system on the other side of the connection is not
configured to use VxSS. VxSS authentication is used with the NetBackup Access
Control feature (NBAC). The connection has been terminated because VxSS
authentication cannot be completed.
Recommended Action: Make sure that both systems are configured to use
NetBackup Access Control VxSS authentication with each other. Or, make sure
that both systems are not configured to use VxSS with each other. The first thing
to check is the Use VxSS Host properties value on each system. If one is configured
for REQUIRED, the other must be configured for REQUIRED or AUTOMATIC. If
one is configured for PROHIBITED, the other must be configured for PROHIBITED
or AUTOMATIC.
See the NetBackup Administrator’s Guide, Volume I, for the following information:
how to set the Access Control-related host properties how to configure a system
to use Access Control.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 194
Message: the maximum number of jobs per client is set to 0
Explanation: The NetBackup Maximum jobs per client global attribute is currently
set to 0. Set the value to 0 to disable backups and archives.
Recommended Action: To enable backups and archives, change the Maximum
jobs per client value to the wanted nonzero setting. This attribute is on the Global
NetBackup Attributes tab in the Master Server Properties dialog box.
173
NetBackup status codes
NetBackup status codes
See "Using the Host Properties window to access configuration settings" in the
NetBackup Troubleshooting Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 195
Message: client backup was not attempted
Explanation: A backup job was in the NetBackup scheduler but was not tried.
Recommended Action: Do the following, as appropriate:
■
Retry the backup either immediately with a manual backup or allow the normal
scheduler retries.
■
For additional information, check the All Log Entries report. For detailed
troubleshooting information, increase the logging level for the diagnostic and
debug logs for nbpem, nbjm, and nbrb.
Use the vxlogcfg command as explained in the following topic:
See "About unified logging" in the NetBackup Logging Reference Guide.
After the next backup try, check the logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 196
Message: client backup was not attempted because backup window closed
Explanation: A backup or an archive operation that the backup scheduler queued
was not tried because the backup window was no longer open.
Recommended Action: Do the following, as appropriate:
■
If possible, change the schedule to extend the backup window for this
combination of policy and schedule so it does not occur again.
■
If the backup must be run, use the Manual Backup command on the Policy
menu in the Backup Policy Management window to perform the backup.
Manual backups ignore the backup window.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 197
Message: the specified schedule does not exist in the specified policy
174
NetBackup status codes
NetBackup status codes
Explanation: A user backup or archive request specified the exact policy and
schedule to use when a backup is performed. The policy exists but does not contain
the schedule.
■
On Microsoft Windows clients, you can specify a policy or schedule on the
Backups tab in the NetBackup Client Properties dialog box. To display this
dialog box, start the Backup, Archive, and Restore interface on the client and
select NetBackup Client Properties on the File menu.
■
On UNIX clients, you can specify a policy or schedule by using the bp.conf
options, BPBACKUP_POLICY or BPBACKUP_SCHED.
Recommended Action: Do the following, as appropriate:
■
Check the client progress log (if available) to determine the policy and schedule
that were specified.
■
Check the configuration on the master server to determine if the schedule is
valid for the policy. If the schedule is not valid, either add the schedule to the
policy configuration or specify a valid schedule on the client.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 198
Message: no active policies contain schedules of the requested type for this client
Explanation: A user backup or archive was requested, and this client is not in a
policy that has a user backup or archive schedule.
Recommended Action: Determine if the client is in any policy that has a schedule
of the appropriate type (either user backup or archive).
■
If the client is in such a policy, check the general policy attributes to verify that
the policy is set to active.
■
If the client is not in such a policy, do either of the following:
■
Add a schedule of the appropriate type to an existing policy that has this
client.
■
Create a new policy that has this client and a schedule of the appropriate
type.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
175
NetBackup status codes
NetBackup status codes
NetBackup status code: 199
Message: operation not allowed during this time period
Explanation: A user backup or archive was requested and this client is not in a
policy that has the following: a user backup or archive schedule with an open backup
window. This error implies that an appropriate policy and schedule combination
exists for this client.
Recommended Action: Determine the policies to which this client belongs that
also have a schedule of the appropriate type (either user backup or archive).
■
If possible, retry the operation when the backup window is open.
■
If the backup window is not open during appropriate time periods, adjust a
backup window for a schedule in one of the policies.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 200
Message: scheduler found no backups due to run
Explanation: When the NetBackup scheduler process (nbpem) checked the policy
and the schedule configuration, it did not find any clients to back up.
This error may be due to the following:
■
No backup time windows are open (applies only to full and to incremental
schedules).
■
Policies are set to inactive.
■
The clients were recently backed up and are not due for another backup (based
on Frequency setting for the schedules).
■
Policies do not have any clients.
Recommended Action: Usually, this message can be considered informational
and does not indicate a problem. However, if you suspect a problem, do the
following:
■
Examine the NetBackup All Log Entries report for any messages in addition to
the one that indicates the scheduler found nothing to do.
■
Examine the policy configuration for all policies or the specific policy in question
to determine if any of the reasons in the Explanation section apply.
■
To obtain detailed troubleshooting information, increase the unified logging level
for the diagnostic and debug logs.
Use the vxlogcfg command as explained in the following procedure:
176
NetBackup status codes
NetBackup status codes
See "About unified logging" in the NetBackup Logging Reference Guide.
Retry the operation and check the resulting logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 201
Message: handshaking failed with server backup restore manager
Explanation: A process on the master server encountered an error when it
communicated with the media host (can be either the master or a media server).
This error means that the master and the media server processes were able to
initiate communication, but were not able to complete them. This problem can occur
during a backup, restore, or media list in a single or a multiple server configuration.
Recommended Action: Do the following, as appropriate:
■
■
Determine the activity that encountered the handshake failure by examining the
NetBackup All Log Entries report for the appropriate time period. If there are
media servers, determine if:
■
The handshake failure was encountered between the master and a media
server.
or
■
Only the master server was involved.
If necessary, create the following debug log directories and increase the logging
level:
■
bpcd on the NetBackup media host (can be either the master or a media
server).
■
If the error was encountered during a backup operation, increase the logging
level for the diagnostic and debug logs for nbpem, nbjm, and nbrb.
Use the vxlogcfg command as explained in the following procedure:
See "About unified logging" in the NetBackup Logging Reference Guide.
■
■
If the error was encountered during a restore operation, bprd on the master
server.
■
If the error was encountered during a media list operation, admin in the
NetBackup logs/admin directory on the master server.
Status code 201 may occur if nbjm fails after it connects to bpbrm or bpmount
but before the policy file list is sent. Examine the nbjm unified log (originator ID
117) or the bpbrm or the bpmount legacy logs for more detail on the cause of
the error.
177
NetBackup status codes
NetBackup status codes
■
Retry the operation and examine the resulting debug logs for information on
why the error occurred.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 202
Message: timed out connecting to server backup restore manager
Explanation: A master server process that tried to initiate communications with
the media host timed out (can be either the master or a media server). This problem
can occur during a backup or restore in either a single or a multiple server
configuration.
Recommended Action: Determine which activity encountered the connection
timeout failure by examining the All Log Entries report for the appropriate time
period. If there are media servers, determine if the timeout occurred between the
master and a media server or if only the master was involved.
■
Verify that the schedule specifies the correct storage unit.
■
Run the ping command from one host to another by using the following
combinations:
■
From the master server, ping the master and all media servers by using the
host names that are found in the storage unit configuration.
■
From each of the media servers, ping the master server by using the host
name that is specified in the NetBackup server list. On a UNIX or Linux
server, the master is the first SERVER entry in the bp.conf file. On a Windows
server, the master is designated on the Servers tab in the Master Server
Properties dialog box.
See "Using the Host Properties window to access configuration settings" in
the NetBackup Troubleshooting Guide.
■
Verify that the master server can communicate with bpcd on the host that has
the storage unit.
■
Perform the following procedures:
See "Testing the media server and clients" in the NetBackup Troubleshooting
Guide.
See "Resolving network communication problems" in the NetBackup
Troubleshooting Guide.
■
If necessary, create debug log directories for the following processes and retry
the operation. Then, check the resulting debug logs on the master server:
178
NetBackup status codes
NetBackup status codes
■
If the error occurred during a backup operation, increase the logging level
for the diagnostic and debug logs for nbpem, nbjm, and nbrb.
Use the vxlogcfg command as explained in the following procedure:
See "About unified logging" in the NetBackup Logging Reference Guide.
Also, check the bpcd legacy debug logs.
■
If the error occurs during a restore operation, check the bprd debug logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 203
Message: server backup restore manager’s network is unreachable
Explanation: A process on the master server cannot connect to a particular host
on the network when it tries to initiate communication with the media host. This
problem can occur during a backup or restore in either a single or a multiple server
configuration.
Recommended Action: Determine which activity encountered this failure by
examining the All Log Entries report for the appropriate time frame. If there is more
than one NetBackup server (one or more media servers), determine the following:
if the failure was between the master and a media server or if only the master server
was involved. Run the ping command from one host to another by using the
following combinations:
■
From the master server, ping the master and all media servers by using the host
names in the storage unit configuration.
■
From each of the media servers, ping the master server host by using the host
name that is specified in the NetBackup server list. On a UNIX or Linux server,
the master is the first SERVER entry in the bp.conf file. On a Windows server,
the master is designated on the Servers tab in the Master Server Properties
dialog.
See "Using the Host Properties window to access configuration settings" in the
NetBackup Troubleshooting Guide.
■
Perform the following procedures:
See "Testing the media server and clients" in the NetBackup Troubleshooting
Guide.
See "Resolving network communication problems" in the NetBackup
Troubleshooting Guide.
■
If necessary, create debug log directories for bprd and retry the operation. Then,
check the resulting debug logs on the master server. If the error occurred during
a restore, check the bprd debug logs.
179
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 204
Message: connection refused by server backup restore manager
Explanation: The media host refused a connection on the port number for bpcd.
This error can be encountered during a backup or restore.
Recommended Action: Run the ping command from one host to another by using
the following combinations:
■
From the master server, ping the master and all media servers by using the host
names in the storage unit configuration.
■
From each of the media servers, ping the master server by using the name that
was specified in the NetBackup server list. On a UNIX or Linux server, this
master is the first SERVER entry in the bp.conf file. On a Windows server, the
master is designated on the Servers tab in the Master Server Properties dialog
box. The following topic shows how to access this dialog box:
See "Using the Host Properties window to access configuration settings" in the
NetBackup Troubleshooting Guide.
■
On UNIX and Linux servers, verify that the bpcd entries in /etc/services or
NIS on all the servers are identical. Verify that the media host listens on the
correct port for connections to bpcd. To verify, run one of the following commands
(depending on platform and operating system):
netstat -a | grep bpcd
netstat -a | grep 13782 (or the value that was specified during the install)
rpcinfo -p | grep 13782 (or the value that was specified during the install)
On UNIX and Linux servers, it may be necessary to change the service number
for the following: bpcd in /etc/services and the NIS services map and send
SIGHUP signals to the inetd processes on the clients.
/bin/ps -ef | grep inetd
kill -HUP the_inetd_pid
or
/bin/ps -aux | grep inetd
kill -HUP the_inetd_pid
180
NetBackup status codes
NetBackup status codes
Note: On a Hewlett-Packard UNIX platform, use inetd -c to send a SIGHUP to
inetd.
■
On Windows servers, do the following:
■
Verify that the bpcd entries are correct in the following:
%SystemRoot%\system32\drivers\etc\services
■
Verify that the following numbers match the settings in the services file:
NetBackup Client Service Port number and NetBackup Request Service
Port number on the Network tab in the NetBackup Client Properties dialog
box. To display this dialog box, start the Backup, Archive, and Restore
interface and select NetBackup Client Properties on the File menu.
The values on the Network tab are written to the services file when the
NetBackup Client service starts.
■
Stop and restart the NetBackup services.
■
Perform the following procedures:
See "Testing the media server and clients" in the NetBackup Troubleshooting
Guide.
See "Resolving network communication problems" in the NetBackup
Troubleshooting Guide.
■
If necessary, create debug log directories for bprd and retry the operation. Then,
check the resulting debug logs on the master server:
■
If the error occurred during a backup operation, check the nbpem, nbjm, and
nbrb logs by using the vxlogview command.
■
If the error occurred during a restore operation, check the bprd debug logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 205
Message: cannot connect to server backup restore manager
Explanation: A process on the master server cannot connect to a process on a
host on the network. This error occurs when the process tries to initiate
communication with the server that has the storage unit. This problem can occur
during a backup or restore in either a single or a multiple server configuration.
Recommended Action: Run the ping command from one host to another by using
the following combinations:
181
NetBackup status codes
NetBackup status codes
■
From the master server, ping the master and all media servers by using the host
names in the storage unit configuration.
■
From each of the media servers, ping the master server by using the name that
is specified in the NetBackup server list. On a UNIX or Linux server, this master
is the first SERVER entry in the bp.conf file. On a Windows server, the master
is designated on the Servers tab in the Master Server Properties dialog box.
See "Using the Host Properties window to access configuration settings" in the
NetBackup Troubleshooting Guide.
■
On a UNIX or Linux server, verify that the bpcd entry in /etc/services or NIS
on all the servers are identical. Verify that the media host listens on the correct
port for connections to bpcd. To verify, run one of the following commands
(depending on platform and operating system):
netstat -a | grep bpcd
netstat -a | grep 13782 (or the value that is specified during the install)
rpcinfo -p | grep 13782 (or the value that is specified during the install)
■
On Windows servers, do the following:
■
Verify that the bpcd entries are correct in the services file:
%SystemRoot%\system32\drivers\etc\services
■
Verify that the following numbers match the settings in the services file:
NetBackup Client Service Port number and NetBackup Request Service
Port number on the Network tab in the NetBackup Client Properties dialog
box. To display this dialog box, start the Backup, Archive, and Restore
interface and select NetBackup Client Properties on the File menu.
The values on the Network tab are written to the services file when the
NetBackup Client service starts.
■
Stop and restart the NetBackup services.
■
Perform the following procedures:
See "Testing the media server and clients" in the NetBackup Troubleshooting
Guide.
See "Resolving network communication problems" in the NetBackup
Troubleshooting Guide.
■
Create a bpcd debug log directory on the server that has the storage unit and
retry the operation. Then, check for additional information in the debug log.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
182
NetBackup status codes
NetBackup status codes
NetBackup status code: 206
Message: access to server backup restore manager denied
Explanation: The master server tries to start a process on another server (or itself)
but does not appear in the NetBackup server list on that server. On a UNIX or Linux
server, the master is the first SERVER entry in the bp.conf file. On a Windows server,
the master is designated on the Servers tab in the Master Server Properties dialog
box.
See "Using the Host Properties window to access configuration settings" in the
NetBackup Troubleshooting Guide.
Recommended Action: Do the following, as appropriate:
■
Verify that the master server appears as a server in its own server list as well
as being listed on all media servers.
If you change the master server list, stop and restart the NetBackup Database
Manager (bpdbm) and NetBackup Request Daemon (bprd) to ensure that all
appropriate NetBackup processes use the new server entry.
■
If necessary, create debug log directories for bprd and retry the operation. Then,
check the resulting debug logs on the master server:
■
If the error occurred during a backup operation, check the nbpem, nbjm, and
nbrb logs by using the vxlogview command.
■
If the error occurred during a restore operation, check the bprd debug logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 207
Message: error obtaining date of last backup for client
Explanation: When nbpem tries to obtain the date of the last backup for a particular
client, policy, and schedule combination, an error occurs.
Recommended Action: Do the following, as appropriate:
■
Verify that the NetBackup Database Manager (bpdbm) process (on UNIX and
Linux) or the NetBackup Database Manager service (on Windows) is running.
■
Examine the All Log Entries report for the appropriate time frame to gather more
information about the failure.
■
For detailed troubleshooting information, create a bpdbm log directory on the
master server. Increase the logging level for the diagnostic and debug logs for
nbpem.
183
NetBackup status codes
NetBackup status codes
Use the vxlogcfg command as explained in the following topic:
See "About unified logging" in the NetBackup Logging Reference Guide.
Retry the operation, then check the resulting logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 209
Message: error creating or getting message queue
Explanation: When a NetBackup process tries to create an internal message
queue construct for inter-process communication, an error occurs. This error
indicates a problem on the master server. On UNIX and Linux systems, this error
may be due to a lack of system resources for System V inter-process communication.
Recommended Action: Create debug log directories on the master server and
retry the operation. Then, determine the type of system failure by examining the
logs. Start with the bprd debug log.
On UNIX and Linux servers, also gather the output of the ipcs -a command to
see what system resources are currently in use.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 210
Message: error receiving information on message queue
Explanation: When a NetBackup process tries to receive a message from a
NetBackup daemon using bprd on an internal message queue construct, an error
occurs. This error indicates a problem on the master server. On UNIX and Linux
systems, this error may be due to a lack of system resources for System V
inter-process communication.
Recommended Action: Create debug log directories on the master server and
retry the operation. Then, determine the type of system failure by examining the
logs. Start with the bprd debug log.
On UNIX and Linux servers, also gather the output of the ipcs -a command to
see what system resources are currently in use.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
184
NetBackup status codes
NetBackup status codes
NetBackup status code: 212
Message: error sending information on message queue
Explanation: When a NetBackup process tries to attach to an already existing
internal message queue construct for inter-process communication, an error occurs.
This error indicates a problem on the master server. On UNIX and Linux systems,
this error may be due to a lack of system resources for System V inter-process
communication.
Recommended Action: Create debug log directories on the master server and
retry the operation. Then, determine the type of system failure by examining the
logs. Start with the bprd debug log.
On UNIX and Linux servers, also, gather the output of the ipcs -a command to
see what system resources are currently in use.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 213
Message: no storage units available for use
Explanation: The NetBackup resource broker (nbrb) did not find any storage units
available for use. Either all storage units are unavailable or all storage units are
configured for On demand only. In addition, the policy and schedule does not
require a specific storage unit.
Recommended Action: Do the following, as appropriate:
■
Examine the Backup Status and All Log Entries report for the appropriate time
period to determine the policy or schedule that received the error.
■
Verify that the media server has not been deactivated for the storage unit or
units that are unavailable.
■
Verify that the storage unit’s drives are not down.
■
Verify the following attribute settings for all storage units:
■
For disk storage units, the Maximum concurrent jobs is not set to 0
■
For Media Manager storage units, the Maximum concurrent write drives
is not set to 0
■
Verify that the robot number and host name in the storage unit configuration
matches the Media and Device Management device configuration.
■
Determine if all storage units are set to On demand only for a combined policy
and schedule that does not require a specific storage unit. In this case, either
185
NetBackup status codes
NetBackup status codes
specify a storage unit for the policy and the schedule combination or turn off On
demand only for a storage unit.
■
If the storage unit is on a UNIX or Linux NetBackup media server, it may indicate
a problem with bpcd. Check /etc/inetd.conf on the media server to verify
that the bpcd entry is correct.
If the storage unit is on a Windows NetBackup media server, verify that the
NetBackup Client service was started on the Windows NetBackup media server.
■
For detailed troubleshooting information, increase the logging levels of nbrb
and mds on the master server.
Use the vxlogcfg command as explained in the following topic:
See "About unified logging" in the NetBackup Logging Reference Guide.
Retry the operation and check the resulting debug logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 215
Message: failed reading global config database information
Explanation: During the periodic checking of the NetBackup configuration, nbproxy
was unable to read the global configuration parameters.
Recommended Action: Do the following, as appropriate:
■
On UNIX and Linux master servers, verify that the NetBackup Database Manager
(bpdbm) process is running. On a Windows master server, verify that the
NetBackup Database Manager service is running.
■
Try to view the global configuration settings by using the NetBackup
administration interface (on UNIX and Linux systems), or by using Host Properties
(on Windows systems).
■
For detailed troubleshooting information, create debug log directories for nbproxy
and bpdbm on the master server and retry the operation. Check the resulting
debug logs for these processes. Also check the nbpem logs by using the
vxlogview command.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 216
Message: failed reading retention database information
186
NetBackup status codes
NetBackup status codes
Explanation: During its periodic checking of the NetBackup configuration, nbpem
did not read the list of retention levels and values.
Recommended Action: Do the following, as appropriate:
■
On a UNIX or Linux master server, verify that the NetBackup Database Manager
(bpdbm) process is running. On a Windows master server, verify that the
NetBackup Database Manager service is running.
■
For detailed troubleshooting information, create a debug log directory for bpdbm
on the master server.
Increase the logging level for nbpem by using the vxlogcfg command as
described in the following topic:
See "About unified logging" in the NetBackup Logging Reference Guide.
Retry the operation and check the resulting logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 217
Message: failed reading storage unit database information
Explanation: During its periodic checking of the NetBackup configuration, nbpem
did not read the storage unit configuration.
Recommended Action: Do the following, as appropriate:
■
On a UNIX or Linux server, verify that the NetBackup Database Manager (bpdbm)
process is running. On a Windows server, verify that the NetBackup Database
Manager service is running.
■
Try to view the storage unit configuration by using the NetBackup administration
interface.
■
For detailed troubleshooting information, create debug logs for nbproxy and
bpdbm on the master server and retry the operation. Check the resulting debug
logs. Also check the nbpem logs by using the vxlogview command.
Ensure that the correct master server is specified for the connection.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 218
Message: failed reading policy database information
Explanation: During the periodic checking of the NetBackup configuration, nbpem
did not read the backup policy configuration.
187
NetBackup status codes
NetBackup status codes
Recommended Action: Do the following, as appropriate:
■
On a UNIX or Linux server, verify that the NetBackup Database Manager (bpdbm)
process is running. On a Windows server, verify that the NetBackup Database
Manager service is running.
■
Try to view the policy configuration by using the NetBackup administration
interface.
■
For detailed troubleshooting information, create debug log directories for nbproxy
and bpdbm on the master server and retry the operation. Check the resulting
debug logs. Also check the nbpem logs by using the vxlogview command.
Ensure that the correct master server is specified for the connection.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 219
Message: the required storage unit is unavailable
Explanation: The policy or schedule for the backup requires a specific storage
unit, which is currently unavailable. This error also occurs for other tries to use the
storage unit within the current backup session.
Recommended Action: Look in the Job Details window for the failed job.
■
Verify that the schedule specifies the correct storage unit and the storage unit
exists.
■
Verify that the following devices are running: the Media Manager device daemon
(ltid) (UNIX or Linux server) or the NetBackup Device Manager service
(Windows server). Use bpps on UNIX and Linux and the Activity Monitor on
Windows or the Services application in the Windows Control Panel.
■
Verify the following attribute settings:
■
For a disk storage unit, Maximum concurrent jobs is not set to 0.
■
For a Media Manager storage unit, the Maximum concurrent drives attribute
is not set to 0.
■
If the storage unit is a tape, verify that at least one of the drives is in the UP
state. Use the Device Monitor.
■
Verify that the robot number and host in the storage unit configuration match
what is specified in the Media and Device Management device configuration.
■
Verify that the master server can communicate with the bpcd process on the
server that has the storage unit.
188
NetBackup status codes
NetBackup status codes
■
Verify that bpcd listens on the port for connections.
On a UNIX or Linux server where the storage unit is connected, if you run
netstat -a | grep bpcd, it should return something similar to the following:
*.bpcd
*.*
0
0
0
0 LISTEN
On a Windows NetBackup server where the storage unit is connected, run
netstat -a to print several lines of output. If bpcd listens, one of those lines
is similar to the following:
TCP
myhost:bpcd
0.0.0.0:0
LISTENING
■
Check the nbrb and the mds logs by using the vxlogview command.
■
If the cause of the problem is not obvious, perform some of the steps in the
following procedure:
See Resolving Network Communication Problems in the NetBackup
Troubleshooting Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 220
Message: database system error
Explanation: The bpdbm process (UNIX and Linux), or the NetBackup Database
Manager service (Windows) did not create a directory path for its configuration
catalogs. This error is due to a system call failure, which is usually due to a
permission problem or an out of space condition.
Recommended Action: Create a debug log directory for bpdbm. Increase the
logging level for the diagnostic and debug logs for nbemm.
Use the vxlogcfg command as explained in the following topic:
See "About unified logging" in the NetBackup Logging Reference Guide.
Retry the operation and check the resulting logs for information.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 221
Message: continue
189
NetBackup status codes
NetBackup status codes
Explanation: This status code is used to coordinate 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.
Recommended Action: Determine the cause of the status code that follows this
one.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 222
Message: done
Explanation: This status code is used to coordinate 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.
Recommended Action: Determine the cause of the status code that follows this
one.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 223
Message: an invalid entry was encountered
Explanation: A request to the bpdbm process (on UNIX and Linux) or the NetBackup
Database Manager service (on Windows) had invalid information or some information
that conflicted. This error is usually a result of the use of software from different
versions. Another cause can be incorrect parameters on a command.
Recommended Action: Verify that all NetBackup software is at the same version
level and the command parameters are specified correctly. If neither of these is the
problem, obtain detailed troubleshooting information by creating a bpdbm debug log
directory. Then retry the operation. Check the resulting debug log.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 224
Message: there was a conflicting specification
190
NetBackup status codes
NetBackup status codes
Explanation: A request to the bpdbm process (on UNIX and Linux) or the NetBackup
Database Manager service (on Windows) had some information that conflicted.
This error is usually a result of the use of software from different version levels
together.
Recommended Action: Verify that all NetBackup software is at the same version
level. If that is not the problem, obtain detailed troubleshooting information by
creating bpdbm and admin debug log directories. Then retry the operation. Check
the resulting debug logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 225
Message: text exceeded allowed length
Explanation: Text in a request exceeds a buffer size. The request was made to
the bpdbm process (on UNIX and Linux) or the NetBackup Database Manager
service (on Windows). This error is usually a result of the use of software from
different version levels.
Recommended Action: Verify that all NetBackup software is at the same version
level. If that is not the problem, create debug log directories for bpdbm and admin.
Then, retry the operation and examine the resulting debug logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 226
Message: the entity already exists
Explanation: The configuration already has an entity with the same name or
definition. For example: this status appears if you add a new policy when an existing
policy has the same name or definition such as attributes or clients.
Recommended Action: Correct your request and re-execute the command.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 227
Message: no entity was found
Explanation: The item requested was not in the catalog. For example, the entity
can be a file or it can be policy information.
191
NetBackup status codes
NetBackup status codes
Recommended Action: A query may have no matching images. Specify different
parameters or options for the operation and try the query again.
To restore selected files from a virtual machine to the original location, you must
specify the host name of the virtual machine. Do not specify the display name or
UUID as the destination.
More information is available about this message:
http://www.veritas.com/docs/TECH208764
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 228
Message: unable to process request
Explanation: An inconsistency exists in the catalog or a request was made that
would be improper to satisfy.
Recommended Action: Do the following, as appropriate:
■
If this status involves a media server, verify that its server list specifies the correct
master server. On a UNIX or Linux server, the master server is the first SERVER
entry in the bp.conf file. On a Windows server, the master is designated on the
Servers tab in the Master Server Properties dialog box.
See "Using the Host Properties window to access configuration settings" in the
NetBackup Troubleshooting Guide.
■
For detailed troubleshooting information, create a bpdbm debug log directory
and retry the operation. Then, check the resulting debug log.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 229
Message: events out of sequence - image inconsistency
Explanation: A request was made that can cause the image catalog to become
inconsistent if satisfied
Recommended Action: Obtain detailed troubleshooting information by creating
a debug log directory for bpdbm. Then, retry the operation, save the resulting debug
log, and contact Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
192
NetBackup status codes
NetBackup status codes
NetBackup status code: 230
Message: the specified policy does not exist in the configuration database
Explanation: The specified policy name does not exist.
Recommended Action: Correct your parameters or options and retry the operation.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 231
Message: schedule windows overlap
Explanation: The specified start and the duration times for one day of the schedule
overlap with another day of the schedule.
Recommended Action: Correct the schedule to eliminate the overlapping backup
windows.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 232
Message: a protocol error has occurred
Explanation: This error is an intermediate status code that usually precedes
another status code. It indicates the following: either the bpdbm process (on UNIX
and Linux) or the NetBackup Database Manager service (on Windows) or the
process that communicates with it has received unexpected information.
Recommended Action: Create a debug log directory for bpdbm. Then, retry the
operation, save the debug log, and contact Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 233
Message: premature eof encountered
Explanation: This status code is an intermediate one that usually precedes another
status code and is associated with a problem in network communication.
Recommended Action: During a restore, this status code means that tar (on the
client) received a stream of data that was not what it expected. If the restore is a
new configuration, verify that the tape drive is configured for variable mode.
193
NetBackup status codes
NetBackup status codes
See the NetBackup Device Configuration Guide.
If the communication failure is not due to an interrupt on a client system, save all
error information and contact Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 234
Message: communication interrupted
Explanation: This status code is an intermediate one that usually precedes another
status code and is associated with a problem in network communication. Either a
server or a client process received an interrupt signal.
Recommended Action: Save all error information and contact Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 235
Message: inadequate buffer space
Explanation: This code usually indicates a mismatch between server and client
software versions.
Recommended Action: Do the following, as appropriate:
■
■
Verify that all NetBackup software is at the same version level. Update earlier
versions of NetBackup software.
■
On UNIX and Linux, NetBackup servers and clients, check the
/usr/openv/netbackup/bin/version file.
■
On Windows NetBackup servers, check the
install_path\NetBackup\version.txt file or the About NetBackup item
on the Help menu.
■
On Microsoft Windows clients, check the About NetBackup item on the
Help menu.
If the problem persists, save all error information and contact Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
194
NetBackup status codes
NetBackup status codes
NetBackup status code: 236
Message: the specified client does not exist in an active policy within the
configuration database
Explanation: A client name was not specified or the specified client does not exist.
Recommended Action: Activate the required policy, correct the client name, or
add the client to a policy that meets your needs. After you make the correction,
retry the operation.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 237
Message: the specified schedule does not exist in an active policy in the
configuration database
Explanation: The specified schedule does not exist in the NetBackup configuration.
Recommended Action: Activate the required policy, correct the schedule name,
or create a schedule in a policy that meets your needs. After you make the
correction, retry the operation.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 238
Message: the database contains conflicting or erroneous entries
Explanation: The catalog has an inconsistent or a corrupted entry.
Recommended Action: Obtain detailed troubleshooting information for bpdbm (on
UNIX and Linux) or the NetBackup Database Manager service (on Windows) by
creating a debug log directory for it. Then, retry the operation, save the resulting
debug log, and contact Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 239
Message: the specified client does not exist in the specified policy
Explanation: The specified client is not a member of the specified policy.
195
NetBackup status codes
NetBackup status codes
Recommended Action: Correct the client name specification, specify a different
policy, or add the required client name to the policy. After you make the correction,
retry the operation.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 240
Message: no schedules of the correct type exist in this policy
Explanation: The appropriate schedule was not found in the specified policy. For
example, a user backup specified a policy name but no user backup schedule exists
in that policy.
Recommended Action: Specify a different policy or create a schedule of the
needed type in the policy. After you make the correction, retry the operation.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 241
Message: the specified schedule is the wrong type for this request
Explanation: The specified schedule for an immediate manual backup is not for
a full nor an incremental backup. It must be one of these.
Recommended Action: Specify only full or incremental schedules for manual
backups. If one does not exist in the policy, create one.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 242
Message: operation would cause an illegal duplication
Explanation: If the request is processed, it causes a duplicate entry (for example,
in the catalog or the configuration database). A duplicate catalog entry is usually
due to a mistake in the specification of media IDs for NetBackup catalog backups.
Recommended Action: Check the error reports to determine the specific
duplication that would occur. Correct the settings for the operation and retry it.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
196
NetBackup status codes
NetBackup status codes
NetBackup status code: 243
Message: the client is not in the configuration
Explanation: The specified client name was not in the catalog.
Recommended Action: Either correct the client name or add the client to the
wanted policy.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 245
Message: the specified policy is not of the correct client type
Explanation: A user backup specified a policy that is not the type that is required
for the client.
Recommended Action: Retry the operation by specifying a policy that is the
correct type for the client. If such a policy does not exist, create one.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 246
Message: no active policies in the configuration database are of the correct client
type
Explanation: A user backup request was not satisfied because no active policies
were the type that were required for the client.
Recommended Action: Create or activate an appropriate policy so the user backup
request can be satisfied.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 247
Message: the specified policy is not active
Explanation: Backups for the specified policy are disabled because the policy is
inactive.
Recommended Action: Activate the policy and retry the operation.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
197
NetBackup status codes
NetBackup status codes
NetBackup status code: 248
Message: there are no active policies in the configuration database
Explanation: No active policy was found that would satisfy the request.
Recommended Action: Activate the appropriate policy and retry the operation.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 249
Message: the file list is incomplete
Explanation: While the server waited for the client to finish sending the file list, it
timed out or a sequencing problem occurred.
Recommended Action: First, obtain additional information by creating debug logs.
Then try to recreate the error. The debug logs to create are as follows:
■
On the server, bptm, bpbrm, and bpdbm.
■
On UNIX, Linux, and Windows clients, bpbkar.
■
On other clients, bpcd.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 250
Message: the image was not created with TIR information
Explanation: This error is internal and should not appear to customers.
Recommended Action: Obtain detailed troubleshooting information by creating
debug logs for bptm or bpdbm on the server. Then, retry the operation and check
the resulting debug logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 251
Message: the tir information is zero length
Explanation: For a true-image backup, the client sent no file information to the
master server. NetBackup discovered this condition when it tried to write the TIR
information to media.
198
NetBackup status codes
NetBackup status codes
Recommended Action: Check the policy file list and the exclude and include lists
on the client to verify that the client has eligible files for backup. For example, this
status code can appear if the exclude list on the client excludes all files.
To obtain detailed troubleshooting information, create debug logs for bptm or bpdbm
on the server. Then, retry the operation and check the resulting debug logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 252
Message: An extended error status has been encountered, check detailed status
Explanation: If a process was unable to report the extended error status as the
final job status, the job exits with status 252. (The extended error status has a
number greater than 255.)
Recommended Action: To determine the actual error, examine the job details
display.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 253
Message: the catalog image .f file has been archived
Explanation: The catalog image .f file was archived.
Recommended Action: Refer to the catalog archiving help information to restore
the archived catalog image .f files.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 254
Message: server name not found in the NetBackup configuration
Explanation: This error should not occur through the normal use of NetBackup.
Recommended Action: Save all of the error information and contact Technical
Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
199
NetBackup status codes
NetBackup status codes
NetBackup status code: 256
Message: logic error encountered
Explanation: An internal Vault error occurred.
Recommended Action: Contact customer support and send the appropriate logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 257
Message: failed to get job data
Explanation: This error can indicate either of the following:
■
Vault failed to get job data because of a broken connection with the Job Manager
(nbjm).
■
Vault received empty job data. This error occurs if a user-specified job ID on
the vltrun -haltdups command is out of range. (That is, the job ID is not
among the job IDs created by Job Manager.)
Recommended Action: Contact customer support and send the appropriate logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 258
Message: Vault duplication was aborted by administrator request
Explanation: The administrator initiated an abort request on the active vault
duplication job.
Recommended Action: Ensure that the abort request was intentional.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 259
Message: vault configuration file not found
Explanation: This error should not occur.
Recommended Action: Contact customer support and send the appropriate logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
200
NetBackup status codes
NetBackup status codes
NetBackup status code: 260
Message: failed to send signal
Explanation: vltrun failed to send a signal to the Vault duplication job.
Recommended Action: Contact customer support and send the appropriate logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 261
Message: vault internal error 261
Explanation: This error code should not occur.
Recommended Action: Contact customer support and send the appropriate logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 262
Message: vault internal error 262
Explanation: This error code should not occur.
Recommended Action: Contact customer support and send the appropriate logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 263
Message: session ID assignment failed
Explanation: The unique identifier to be assigned to the Vault session is corrupt.
Recommended Action: Verify that the session ID that is stored in the
session.last file is valid.
UNIX and Linux:
/usr/openv/netbackup/vault/sessions/vault_name/session.last
Windows:
install_path\Netbackup\vault\sessions\vault_name\session.last
Make sure that the file system is not full and that no one has inadvertently edited
the session.last file. To correct the problem, store the highest session ID that
201
NetBackup status codes
NetBackup status codes
was assigned to a session for this Vault in the session.last file. If the problem
persists, contact customer support and send the appropriate logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 265
Message: session ID file is empty or corrupt
Explanation: The session ID that is stored in the following file is corrupt.
UNIX and Linux:
/usr/openv/netbackup/vault/sessions/vault_name/session.l
ast
Windows:
install_path\NetBackup\vault\sessions\vault_name\session
.last
Recommended Action: Ensure that the session ID that is stored in the
session.last file is not corrupt. Make sure that the file system is not full and that
no one has inadvertently edited the file. To correct the problem, store the highest
session ID that was assigned to a session for this Vault in the session.last file.
If the problem persists, contact customer support and send the appropriate logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 266
Message: cannot find robot, vault, or profile in the vault configuration
Explanation: NetBackup cannot find the specified profile_name or triplet
robot_name/vault_name/profile_name on the Vault command (vltrun, vlteject,
vltoffsitemedia) or in vltopmenu in the Vault configuration.
Recommended Action: Rerun the command with the correct profile_name or
triplet robot_name/vault_name/profile_name.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 267
Message: cannot find the local host name
202
NetBackup status codes
NetBackup status codes
Explanation: A Vault job obtains the local host name through an OS call. This
error occurs when the Vault job is unable to get the local host name.
Recommended Action: Issue a hostname command at the OS command prompt.
See the hostname (or gethostbyname) man page for an explanation of the conditions
that would cause it to fail.
See the OS System Administrator’s Guide for more information.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 268
Message: the vault session directory is either missing or inaccessible
Explanation: This error occurs when a Vault job cannot access the following:
UNIX and Linux: /usr/openv/netbackup/vault/sessions
Windows: install_path\NetBackup\vault\sessions
This directory is created when Vault is installed.
Recommended Action: Make sure that you are running on the master server
where Vault is installed and configured. Also ensure that no one accidentally
removed the sessions directory or changed permission on the directory path so it
is inaccessible to the Vault job.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 269
Message: no vault session ID was found
Explanation: This error is encountered when vltopmenu cannot find a sidxxx
session id directory for the specified profile. 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 and Linux: /usr/openv/netbackup/vault/sessions/vault_name
Windows: install_path\NetBackup\vault\sessions\vault_name
Recommended Action: Either specify a different profile for the Vault jobs that
were run or exit vltopmenu and run a Vault job for the specific profile. Then rerun
vltopmenu and select the profile.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
203
NetBackup status codes
NetBackup status codes
NetBackup status code: 270
Message: unable to obtain process id, getpid failed
Explanation: This error occurs when a Vault process is unable to obtain its process
ID by means of the getpid() OS system call.
Recommended Action: Look at the system log for any unusual system problems.
Wait a while and then try running the process again when system resources are
freed up.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 271
Message: vault XML version mismatch
Explanation: The Vault upgrade process failed.
Recommended Action: Enable logging, start nbvault, and then examine the
nbvault logs to determine the cause of the failure. If the upgrade process fails
again, contact your customer support representative.
The following are the locations of the nbvault logs:
UNIX and Linux: /usr/openv/netbackup/logs/nbvault/
Windows: install_path\NetBackup\logs\nbvault
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 272
Message: execution of a vault notify script failed
Explanation: This error occurs when the Vault process is unable to run a Vault
notify script due to permissions problems or coding problems in the script. It also
occurs if the script returns an error.
Recommended Action: Ensure that the notify script is executable and runs without
errors. You must debug the script by running it manually to eliminate coding errors.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 273
Message: invalid job id
204
NetBackup status codes
NetBackup status codes
Explanation: This error can occur in either of the following situations:
■
The specified job is not an active Vault job
■
The specified active Vault job is not at the duplication step
Recommended Action: Specify the job ID of the active Vault job that is currently
at the duplication step or operation.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 274
Message: no profile was specified
Explanation: This error should not occur.
Recommended Action: Contact customer support and send the appropriate logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 275
Message: a session is already running for this vault
Explanation: This error occurs when you start a session for a vault and another
session is already running for this vault. Only one session is allowed for a vault at
any given time.
Recommended Action: Start the Vault session after the previous session has
completed.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 276
Message: invalid session ID
Explanation: This error should not occur.
Recommended Action: Contact customer support and send the appropriate logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 277
Message: unable to print reports
205
NetBackup status codes
NetBackup status codes
Explanation: This error should not occur.
Recommended Action: Contact customer support and send the appropriate logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 278
Message: unable to collect pre eject information from the API
Explanation: This error occurs when robotic information cannot be retrieved before
ejection.
Recommended Action: Ensure that all Media and Device Management daemons
are running or the robot is live and up.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 279
Message: eject process is complete
Explanation: This error occurs when the eject process is completed successfully.
Recommended Action: None
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 280
Message: there are no volumes to eject
Explanation: This error occurs when media to be ejected are not in the library.
Recommended Action: Ensure that the media to be ejected are not removed
from the library manually.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 281
Message: vault core error
Explanation: An internal Vault error occurred.
Recommended Action: Contact customer support and send the appropriate logs.
206
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 282
Message: cannot connect to nbvault server
Explanation: The vault job cannot connect to the NetBackup Vault Manager service
(nbvault on UNIX and Linux, nbvault.exe on Windows).
Possible causes are the following:
■
The &CompanyName; Private Branch Exchange service (VRTSpbx) or NetBackup
Request Manager (bprd) is down.
■
The NetBackup Vault Manager service is down, possibly because of the following:
the Vault is not licensed, the vault.xml configuration file is corrupt, or the
vault.xml configuration file upgrade failed during an upgrade installation.
Recommended Action: To determine the reason for failure, examine the logs for
the service or services that are down and the operating system logs (EventLog on
Windows). Restart the service or services that are down after resolving the problem.
The following are the locations of the nbvault logs:
UNIX and Linux: /usr/openv/netbackup/logs/nbvault/
Windows: install_path\NetBackup\logs\nbvault
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 283
Message: error(s) occurred during vault report generation
Explanation: Vault encountered errors during the report generation phase.
Recommended Action: Check logs for details of the failure.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 284
Message: error(s) occurred during vault report distribution
Explanation: Vault encountered errors during the report distribution phase. Potential
reasons include the following:
207
NetBackup status codes
NetBackup status codes
■
Reports were not emailed (possibly because of malformed email addresses in
the vault.xml file).
■
On Windows, the third-party mail client (such as blat) is not configured properly.
■
The reports destination directory is not present or it does not have appropriate
permissions.
■
The printer is not set up correctly or the printer command in vault.xml is
incorrect.
Recommended Action: Check logs for details of the failure.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 285
Message: unable to locate vault directory
Explanation: A Vault job or a command for a missing or a corrupt directory of the
session in question returns this error.
Recommended Action: The Vault directory is created when the Vault package
is installed on the master server. Ensure that the Vault job or command is started
as root on the master server. Ensure that the Vault directory was not removed
inadvertently or made inaccessible to the root user.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 286
Message: vault internal error
Explanation: This error should never occur.
Recommended Action: Contact customer support and send the appropriate logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 287
Message: vault eject failed
Explanation: This error occurs when Vault fails to eject any of the media that was
identified for eject during a Vault Session. Potential reasons: Media and Device
Management services are down, the robot is down, or no empty slots are available
in the media access port (MAP).
208
NetBackup status codes
NetBackup status codes
Recommended Action: Ensure that the Media and Device Management services
are running, the robot is up, and empty slots are available in the media access port
(MAP).
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 288
Message: vault eject partially succeeded
Explanation: This error occurs when not all of the media that was identified for
eject during a Vault session can be ejected.
Potential reasons include the following:
■
Some of the media is in use by NetBackup
■
Some of the media are in a drive
■
Not enough empty slots are available in the media access port (MAP)
Recommended Action: Ensure that the media are not loaded in a drive and in
use by other processes. Ensure that empty slots are available in the media access
port (MAP).
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 289
Message: cannot consolidate reports of sessions from container and slot-based
vaults
Explanation: This error occurs when you consolidate reports and at least one
session uses slots and another uses containers.
Recommended Action: Change the report consolidation so that only reports for
one type of vault operation are consolidated, either slots or containers.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 290
Message: one or more errors detected during eject processing
Explanation: This error occurs when more than one error is encountered during
an eject procedure by vltopmenu. Any "eject" errors that range from 291 to 300
may have occurred in any of the sessions being ejected.
209
NetBackup status codes
NetBackup status codes
Recommended Action: For detailed information, review the Vault debug log in
the following directory:
UNIX and Linux: /usr/openv/netbackup/logs/vault
Windows: install_path\NetBackup\logs\vault
Also review the summary.log in each of the sidxxx directories that had problems:
UNIX and Linux: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx
Windows: install_path\NetBackup\vault\sessions\vault_name\sidxxx
(where xxx is the session ID)
After the problem is identified and corrected, the media that were not ejected may
need to be ejected manually by means of vlteject or vltopmenu.
This error often indicates that the media were left in the off-site Vault volume group
but physically reside in the robot or the robotic MAP.
To solve this problem, do one of the following:
■
Manually remove any media that are in the off-site Vault volume group but are
still in the robotic library.
■
Inventory the robotic library. An inventory puts any media that were in the off-site
Vault volume group back into the robotic volume group. Then rerun the Vault
sessions that failed.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 291
Message: number of media has exceeded capacity of MAP; must perform manual
eject using vltopmenu or vlteject
Explanation: This error occurs in the following situation: a Vault job is run for a
profile that selected automatic eject mode and the number of media to be ejected
exceeds the MAP capacity.
Recommended Action: Use vltopmenu to manually eject the media for the
selected profile and session ID. The vltopmenu option lets you eject the selected
media, a MAP-full (or less) at a time.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
210
NetBackup status codes
NetBackup status codes
NetBackup status code: 292
Message: eject process failed to start
Explanation: This error occurs when the following cannot start the eject process:
the Vault job, the vlteject command, or the use of the vltopmenu.
Recommended Action: For detailed information about the problem, review the
Vault debug log in the following directory:
UNIX and Linux: /usr/openv/netbackup/logs/vault
Windows: install_path\NetBackup\logs\vault
Also review the summary.log in each of the sidxxx directories that had problems:
UNIX and Linux: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx
Windows:install_path\NetBackup\vault\sessions\vault_name\sidxxx
(where xxx is the session ID)
Use the robtest utility to ensure that you can communicate with the Vault robotic
library. After the problem is resolved, rerun the Vault session, vlteject command,
or vltopmenu command.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 293
Message: eject process has been aborted
Explanation: This error occurs when the eject process is canceled. This error can
be encountered during a Vault job or with the vlteject or the vltopmenu eject
command.
This error can occur because of one of the following conditions:
■
Could not open a pipe to vmchange -verify_eject call.
■
Unexpected output from vmchange -verify_eject call.
■
No MAP elements exist to eject media into.
■
The robotic library had problems putting media into the MAP.
■
The user pressed Return in interactive mode and did not first remove the media
from the MAP. In this case, the media that were in the MAP are put back into
their original slots in the robotic library.
Recommended Action: For detailed information about why the process was
canceled, review the Vault debug log in the following directory:
211
NetBackup status codes
NetBackup status codes
UNIX and Linux: /usr/openv/netbackup/logs/vault
Windows: install_path\NetBackup\logs\vault
Also review the summary.log in each of the sidxxx directories that had problems:
UNIX and Linux:
/usr/openv/netbackup/vault/sessions/vault_name/sidxxx
Windows:
install_path\NetBackup\vault\sessions\vault_name\sidxxx
(where xxx is the session ID)
This error often indicates that the media were left in the off-site Vault volume group
but physically reside in the robot or the robotic MAP.
To solve this problem, do one of the following:
■
Manually remove any media that are in the off-site Vault volume group but are
still in the robotic library.
■
Inventory the robotic library. An inventory puts any media that were in the off-site
Vault volume group back into the robotic volume group. Then, rerun the Vault
sessions that failed.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 294
Message: vault catalog backup failed
Explanation: During a Vault job, the catalog backup step failed.
Recommended Action: Review the Vault debug log in the following directory for
detailed information about why the process failed:
UNIX and Linux: /usr/openv/netbackup/logs/vault
Windows: install_path\NetBackup\logs\vault
To find the actual problem that caused the catalog backup (bpbackupdb) to fail,
review the summary.log in each of the sidxxx directories that had problems:
UNIX and Linux: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx
Windows: install_path\NetBackup\vault\sessions\vault_name\sidxxx
(where xxx is the session ID)
Correct the problem and rerun the Vault job.
212
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 295
Message: eject process could not obtain information about the robot
Explanation: This error occurs when the eject process cannot collect information
about the robotic library and its associated MAPs and volumes.
Recommended Action: For detailed information about why the process fails,
review the Vault debug log in the following directory:
UNIX and Linux: /usr/openv/netbackup/logs/vault
Windows: install_path\NetBackup\logs\vault
Also review the summary.log in each of the sidxxx directories that had problems:
UNIX and Linux: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx
Windows: install_path\NetBackup\vault\sessions\vault_name\sidxxx
(where xxx is the session ID)
Correct the error and rerun the Vault session, vlteject command, or vltopmenu
eject command.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 296
Message: process called but nothing to do
Explanation: This error occurs in the following situations:
■
vlteject is called with -eject but the system has no tapes to eject
■
vlteject is called with -eject and the eject is already done
■
vlteject is called with -report and the reports are already done
■
vlteject is called with -eject and -report, and both the eject and the reports
are done
Recommended Action: This error is an informative one and does not require any
action.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
213
NetBackup status codes
NetBackup status codes
NetBackup status code: 297
Message: all volumes are not available to eject
Explanation: This error occurs when a try is made to eject a non-existent or bad
media ID during the eject phase of the following: a Vault session, a vlteject
command, or a vltopmenu command.
Possible reasons for this error are as follows:
■
The bad media ID was added by means of the vlt_ejectlist_notify script.
■
The bad media ID is already in the MAP or not in the robotic library.
■
The bad media ID is in a robotic drive.
■
The bad media ID is in transit in the robotic library.
Recommended Action: Remove or correct the defective media ID from the
vlt_ejectlist_notify script and rerun the Vault session. If the bad media ID is
in the MAP or a drive or in transit, something is misconfigured.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 298
Message: the library is not ready to eject volumes
Explanation: This error occurs if the robotic library is not in a state to support
ejecting media.
Possible reasons for this error include the following:
■
Currently, the library ejects media
■
The library waits to eject media
■
Currently, the library injects media
■
The library waits to inject media
Recommended Action: Wait until the robotic library can support the eject action
and rerun the Vault session, vlteject command, or vltopmenu command.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 299
Message: there is no available MAP for ejecting
214
NetBackup status codes
NetBackup status codes
Explanation: The robotic library you vault from does not have a MAP available
for use and so media cannot be ejected.
Recommended Action: Wait until the robotic library’s MAP is available for use
and rerun the Vault session, vlteject command, or vltopmenu command.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 300
Message: vmchange eject verify not responding
Explanation: During the eject process, the vmchange command is called with a
-verify_eject call until all of the volumes for the request are in the MAP. This
command call failed. Or it did not return the proper information to the Vault eject
process.
Recommended Action: Do the following, as appropriate:
■
Review the Vault debug log in the following directory for detailed information
about why the process failed:
UNIX: /usr/openv/netbackup/logs/vault
Windows: install_path\NetBackup\logs\vault
■
Also review the summary.log in each of the sidxxx directories that had problems:
UNIX:/usr/openv/netbackup/vault/sessions/vault_name/sidxxx
Windows:install_path\NetBackup\vault\sessions\vault_name\sidxxx
(where xxx is the session ID)
This error often indicates that the media were left in the off-site Vault volume
group but physically reside in the robot or the robotic MAP. To solve this problem,
do one of the following:
■
Manually remove any media that are in the off-site Vault volume group but are
still in the robot.
■
Inventory the robot. An inventory puts any media that were in the off-site Vault
volume group back into the robotic volume group. Then, rerun the Vault sessions
that failed.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 301
Message: vmchange api_eject command failed
215
NetBackup status codes
NetBackup status codes
Explanation: During the eject process, the vmchange command is called with an
-api_eject call to begin the process to eject media. This command call failed.
Recommended Action: Review the Vault debug log in the following directory for
detailed information about why the process failed:
UNIX: /usr/openv/netbackup/logs/vault
Windows: install_path\NetBackup\logs\vault
Also review the summary.log in each of the sidxxx directories that had problems:
UNIX: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx
Windows: install_path\NetBackup\vault\sessions\vault_name\sidxxx
(where xxx is the session ID)
When the problem is resolved, rerun the Vault session, vlteject command, or
vltopmenu command.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 302
Message: error encountered trying backup of catalog (multiple tape catalog backup)
Explanation: This error occurs when the NetBackup command that was used for
stage one of the two-stage catalog backup fails.
Recommended Action: For the actual error that caused the failure, review the
Vault debug log in the following directory:
UNIX: /usr/openv/netbackup/logs/vault
Windows: install_path\NetBackup\logs\vault
Review the summary.log in each of the sidxxx directories that had problems:
UNIX: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx
Windows: install_path\NetBackup\vault\sessions\vault_name\sidxxx
(where xxx is the session ID)
In addition, review the admin debug log in the following directory:
UNIX: /usr/openv/netbackup/logs/admin
Windows: install_path\NetBackup\logs\admin
Correct the error and rerun the Vault session.
216
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 303
Message: error encountered executing Media Manager command
Explanation: This error occurs when a Media and Device Management command
fails during a Vault job.
Recommended Action: For the actual error that caused the command to fail,
review the Vault debug log in the following directory:
UNIX: /usr/openv/netbackup/logs/vault
Windows: install_path\NetBackup\logs\vault
Also review the summary.log in each of the sidxxx directories that had problems:
UNIX: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx
Windows: install_path\NetBackup\vault\sessions\vault_name\sidxxx
(where xxx is the session ID)
Try running the command (with the same arguments as in the log file) to see the
actual error. Ensure that the Media and Device Management daemons are running.
Also ensure that the robot is functional and you can communicate with it (for
example, inventory the robot through the GUI).
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 304
Message: specified profile not found
Explanation: This error occurs when the profile name that is specified on the Vault
command is not defined in the Vault configuration.
Recommended Action: Rerun the Vault command with a profile name that is
defined in the Vault configuration.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 305
Message: multiple profiles exist
217
NetBackup status codes
NetBackup status codes
Explanation: This error may occur when duplicate profile names are defined in
multiple Vault configurations and only the profile name is specified on the Vault
command.
Recommended Action: Rerun the Vault command with the triplet
robot_name/vault_name/profile_name. The triplet uniquely identifies the profile in
your Vault configuration.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 306
Message: vault duplication partially succeeded
Explanation: This error occurs when all selected images are not duplicated
successfully.
Recommended Action: Check the Vault and induplicate logs for cause of the
failure.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 307
Message: eject process has already been run for the requested Vault session
Explanation: This error occurs when vlteject is run to eject media for a session
ID for which media has already been ejected.
Recommended Action: Rerun vlteject for another session ID for which media
has not been ejected.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 308
Message: no images duplicated
Explanation: This error occurs when Vault failed to duplicate any images.
Recommended Action: For more information, review the Vault debug log in the
following directory:
UNIX: /usr/openv/netbackup/logs/vault
Windows: install_path\NetBackup\logs\vault
218
NetBackup status codes
NetBackup status codes
Also review the summary.log in each of the sidxxx directories that had problems:
UNIX: /usr/openv/netbackup/vault/sessions/<vault_name/>sidxxx
Windows: install_path\NetBackup\vault\sessions\vault_name\sidxxx
(where vault_name is the name of the vault, and xxx is the session ID)
Look for the log entry that gives the total number of images processed. A common
cause of failure is a lack of resources, such as no more media available in the
specified pools for duplication. Correct the problem and rerun the Vault job. Note
that the NetBackup scheduler retries a Vault job that terminates with this error.
Review the admin debug log for duplicate entries and the bptm debug log.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 309
Message: report requested without eject being run
Explanation: This error occurs when a report is run that requires media to have
been ejected first.
Recommended Action: Perform one of these actions:
■
Rerun vlteject or vltopmenu to eject the media for the session before you
generate the reports.
■
Reconfigure the profile to allow the eject step to be performed when the next
Vault session for this profile runs.
■
Disable the report generation in the profile for the reports that require media to
be ejected.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 310
Message: Updating of Media Manager database failed
Explanation: This error occurs when Vault physically ejects tapes but fails to
update the EMM database to reflect the eject operation. A typical reason for this
failure is that EMM detected a mismatch between the media type and its volume
group.
Recommended Action: To find the root cause of the error, review the Vault debug
logs in the following directory:
UNIX: /usr/openv/netbackup/logs/vault
219
NetBackup status codes
NetBackup status codes
Windows: install_path\NetBackup\logs\vault
To fix the issue may involve making configuration changes.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 311
Message: Iron Mountain Report is already created for this session
Explanation: This error occurs when an Iron Mountain report has already been
generated for the session.
Recommended Action: None. This report cannot be generated again.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 312
Message: invalid container database entry
Explanation: NetBackup Vault found an invalid entry while it read the container
database. Each container entry in the container database must follow the expected
format. The container database exists in file cntrDB, which is located at
install_path/netbackup/vault/sessions/cntrDB.
Recommended Action: To get the line number of an invalid record in the container
database, read the log file under the directory netbackup/logs/vault. Be aware
that a Vault log may not exist unless the directory netbackup/logs/vault existed
before the error occurred. Open the container database file cntrDB and correct that
invalid entry. Note that this error occurs every time Vault reads this entry in cntrDB
until either this invalid entry is deleted or it is corrected.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 313
Message: container does not exist in container database
Explanation: The specified container does not have an entry in the container
database. The container database exists in file cntrDB, which is located at
install_path/netbackup/vault/sessions/cntrDB.
220
NetBackup status codes
NetBackup status codes
Recommended Action: Verify that you put some media into this container by
using the vltcontainers command. Verify that you did not delete it by using the
vltcontainers -delete command.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 314
Message: container database truncate operation failed
Explanation: An error occurs while truncating the container database. This error
may occur during the modification or deletion of an entry from the container
database. The container database exists in file cntrDB, which is located at
install_path/netbackup/vault/sessions/cntrDB.
Recommended Action: See the log file under the directory netbackup/logs/vault
for more details. Be aware that a log file is not created unless the
netbackup/logs/vault directory has already been created.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 315
Message: failed appending to container database
Explanation: This error can occur while appending a container record to the
container database. This error may occur with the addition, modification, or deletion
of an entry from the container database. The container database exists in file cntrDB,
which is located at install_path/netbackup/vault/sessions/cntrDB.
Recommended Action: Read the relevant log file under the directory
install_path/netbackup/logs/vault for more details. Be aware that if this
directory does not already exist, a log file is not created.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 316
Message: container_id is not unique in container database
Explanation: NetBackup Vault has found a previously-existing entry for this
container ID in the container database while adding it to the container database.
Each container record in the container database must have a unique container ID.
221
NetBackup status codes
NetBackup status codes
Note that the container database exists in file cntrDB, which is located at
install_path/netbackup/vault/sessions/cntrDB.
Recommended Action: Verify that you have specified the correct container ID.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 317
Message: container database close operation failed
Explanation: This error occurs while closing the container database. This error
may occur during the reading, addition, modification, or deletion of an entry from
the container database. Note that the container database exists in file cntrDB, which
is located at install_path/netbackup/vault/sessions/cntrDB.
Recommended Action: Read the relevant log file under the directory
netbackup/logs/vault for more details. Be aware that if this directory does not
already exist, a log file is not created.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 318
Message: container database lock operation failed
Explanation: This error occurs while locking the container database. This error
may occur during the addition, modification, or deletion of an entry from the container
database. Note that the container database exists in file cntrDB, which is located
at install_path/netbackup/vault/sessions/cntrDB.
Recommended Action: Read the relevant log file under the directory
netbackup/logs/vault for more details. Be aware that if this directory does not
already exist, a log file not created.
If some other Vault operation uses the container database and locks it, wait until
that operation completes and the container database is unlocked.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 319
Message: container database open operation failed
Explanation: This error occurs while opening the container database. This error
may occur during the reading, addition, modification, or deletion of an entry from
222
NetBackup status codes
NetBackup status codes
the container database. Note that the container database exists in file cntrDB, which
is located at install_path/netbackup/vault/sessions/cntrDB.
Recommended Action: Read the relevant log file under the directory
netbackup/logs/vault for more details. Be aware that if this directory does not
already exist, a log file is not created.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 320
Message: the specified container is not empty
Explanation: This error occurs if you try to delete a container from the container
database, but the container still holds media. You can only delete empty containers.
Recommended Action: Verify that you have specified the correct container ID.
If you still want to delete this container from the container database, first empty it
by doing either of the following:
■
Inject all of the media that it contains into a robot.
■
Clear the Vault container ID fields for these media from the EMM database by
using vmchange -vlt cid with a value of -.
Try to delete the container again.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 321
Message: container cannot hold any media from the specified robot
Explanation: This error occurs while trying to place media from an unexpected
EMM database host into a container. All the media that are placed in a container
should belong to the same EMM database host. For example, you have media from
a robot that belongs to one EMM database host. Then you try to put this media into
a container that already holds media from the robots that belong to a different EMM
database host.
Recommended Action: Verify that you specified the correct container ID and
media IDs. Read the relevant log file under the directory
install_path/netbackup/logs/vault for more details. Be aware that if this
directory does not already exist, a log file is not created.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
223
NetBackup status codes
NetBackup status codes
NetBackup status code: 322
Message: cannot find vault in vault configuration file
Explanation: NetBackup Vault cannot find an entry for the specified Vault name
into the Vault configuration file. Note that the Vault configuration file is located at
install_path/netbackup/db/vault/vault.xml.
Recommended Action: Verify that you specified the correct Vault name. Read
the relevant log file under the directory netbackup/logs/vault for more details.
Be aware that if this directory does not already exist, a log file is not created.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 323
Message: cannot find robot in vault configuration file
Explanation: NetBackup Vault cannot find an entry for the specified robot number
in the Vault configuration file. Note that the Vault configuration file is located at
install_path/netbackup/db/vault/vault.xml.
Recommended Action: Verify that you specified the correct robot number. Read
the relevant log file under the directory netbackup/logs/vault for more details.
Be aware that if this directory does not already exist, a log file is not created.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 324
Message: invalid data found in retention map file for duplication
Explanation: This error occurs when the retention mapping file (either generic or
for a specific vault) contains invalid data. If the file contains too much or too little
data or the user defines invalid retention levels in the file, this error occurs.
The retention mapping file is used as follows: in a Vault session when a Vault profile
duplication is configured with the Use mappings retention level configured for one
of the copies for duplication. The product installs a mapping file template named
retention_mappings in install_path/netbackup/db/vault.
To specify a mappings file for any single vault, copy the retention_mappings template
to another file and append the name of the vault. For example,
netbackup/db/vault/retention_mappings.V1
Recommended Action: Check the entries in the retention_mappings file.
224
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 325
Message: unable to find policy/schedule for image using retention mapping
Explanation: This error occurs with duplication of the backup policy or the schedule
of an image by Vault. The Use mappings option on the Duplication tab of the Profile
dialog box is selected, but the policy or the schedule no longer exists.
Recommended Action: Verify whether or not the backup policy or the schedule
that created the image still exists. If either one or both do not exist, the image is
not duplicated through the Vault profile.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 326
Message: specified file contains no valid entry
Explanation: The specified file contains no valid entries for media IDs or the
alphanumeric equivalent of barcodes. As per the expected format, each line should
contain only one string that represents either a media ID or the barcode numeric
equivalent.
Recommended Action: Verify that each entry in the specified file does not exceed
the string size limit: six characters for media IDs and 16 characters for the numeric
equivalent of barcodes. Correct the invalid entries in the specified file and try the
same operation again. Read the relevant log file under the directory
install_path/netbackup/logs/vault for more details. Be aware that if this
directory does not already exist, a log file is not created.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 327
Message: no media ejected for the specified vault session
Explanation: This error occurs while moving media ejected by the specified Vault
session to a container. Either the specified Vault session has not ejected any media,
or you specified an incorrect Vault name or session ID.
Recommended Action: Verify that you have specified the correct combination of
Vault name and session ID. Verify that the specified Vault session has ejected at
least one piece of media. Read the relevant log file under the directory
225
NetBackup status codes
NetBackup status codes
netbackup/logs/vault for more details. Be aware that if this directory does not
already exist, a log file is not created.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 328
Message: invalid container ID
Explanation: This error occurs while adding a container record to the container
database. The container ID is found invalid. Note that the container database exists
in the cntrDB file that is located at
install_path/netbackup/vault/sessions/cntrDB.
Recommended Action: Verify that the container ID does not contain any space
characters, and that the string size is a maximum of 29 characters long.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 329
Message: invalid recall status
Explanation: This error occurs while adding a container record to the container
database. The container recall status is found invalid. Note that the container
database exists in the cntrDB file that is located at
install_path/netbackup/vault/sessions/cntrDB.
Recommended Action: Verify that the recall status is either 1 or 0.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 330
Message: invalid database host
Explanation: This error occurs while adding a container record to the container
database. The EMM database host name is found invalid. Note that the container
database exists in the cntrDB file that is located at
install_path/netbackup/vault/sessions/cntrDB.
Recommended Action: Verify that the EMM database host name does not contain
any space characters, and that the string size is a maximum of 256 characters long.
226
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 331
Message: invalid container description
Explanation: This error occurs while adding a container record to the container
database. The container description is found invalid. Note that the container
database exists in the cntrDB file that is located at
install_path/netbackup/vault/sessions/cntrDB.
Recommended Action: Verify that the string size of the container description is
a maximum of 25 characters long.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 332
Message: error getting information from EMM database
Explanation: This error can occur while the backup process communicates with
the EMM database to retrieve some information.
Recommended Action: Do the following, as appropriate:
■
On UNIX, verify that the NetBackup Volume Manager (vmd) is running. On
Windows, verify that the NetBackup Volume Manager service is running.
■
See the process-specific error log directory for more details.
UNIX: /usr/openv/netbackup/logs/process_name
Windows: install_path\NetBackup\logs\process_name
For example, if you get this error while running a Vault command (such as
vltcontainers or vltopmenu), look at the following logs to learn why:
/usr/openv/netbackup/logs/vault
Note: The log file cannot be created unless the appropriate log directory (for
example, /usr/openv/netbackup/logs/vault) is already created.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
227
NetBackup status codes
NetBackup status codes
NetBackup status code: 333
Message: error getting information from media manager command line
Explanation: This error occurs when Vault cannot retrieve robot information such
as map information, volume information, library status, and so on. It is an internal
error.
Recommended Action: Contact customer support and send the appropriate logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 334
Message: unable to receive response from robot; robot not ready.
Explanation: This error occurs when a problem exists with the robot.
Recommended Action: Ensure that all Media and Device Management daemons
are running or the robot is live and up.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 335
Message: failure occurred while suspending media for eject
Explanation: This error occurs when Vault cannot suspend the media. It is an
internal error.
Recommended Action: Contact customer support and send the appropriate logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 336
Message: failure occurred while updating session information
Explanation: Vault cannot update the session files. It is an internal error.
Recommended Action: Contact customer support and send the appropriate logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
228
NetBackup status codes
NetBackup status codes
NetBackup status code: 337
Message: failure occurred while updating the eject.mstr file
Explanation: Vault cannot update the eject list file. It is an internal error.
Recommended Action: Contact customer support and send the appropriate logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 338
Message: vault eject timed out
Explanation: This error occurs when a problem exists with the robot.
Recommended Action: Do the following, as appropriate:
■
Remove the media from the MAP if it is already full.
■
Make sure that the MAP is closed properly.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 339
Message: vault configuration file format error
Explanation: The Vault configuration file is malformed. Unless the file has been
manually modified, this error is internal. Note that the Vault configuration file is
located at install_path/netbackup/db/vault/vault.xml.
Recommended Action: Contact customer support and send the appropriate logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 340
Message: vault configuration tag not found
Explanation: An optional attribute may not appear in the Vault configuration file.
This internal error generally does not cause problems in Vault's operation. Note
that the Vault configuration file is located at
install_path/netbackup/db/vault/vault.xml.
Recommended Action: If the Vault's operation is affected, contact customer
support and send the appropriate logs.
229
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 341
Message: vault configuration serialization failed
Explanation: Vault failed to write out the Vault configuration file. It is an internal
error. Note that the Vault configuration file is located at
install_path/netbackup/db/vault/vault.xml.
Recommended Action: Contact customer support and send the appropriate logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 342
Message: cannot modify - stale view
Explanation: This error can occur if an administration interface (NetBackup
Administration Console or Vault Administration menu user interface) tries to
modify the following:
■
A robot or vault or profile in between the read
■
Operations of the same robot or vault
■
Profile by another instance of an administration interface
Recommended Action: Check the latest attributes of the robot or vault or profile.
To check, refresh the view in the NetBackup Administration Console or retrieve
the attributes in the Vault Administration menu user interface again. Then retry
the operation.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 343
Message: robot already exists
Explanation: This error can occur during addition of a robot while a robot with the
same name already exists.
Recommended Action: Refresh the view in the NetBackup Administration
Console or retrieve the attributes in the Vault Administration menu user interface
again to see the robot.
230
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 344
Message: vault already exists
Explanation: This error can occur during addition of a vault if a vault with the same
name already exists in the same robot.
Recommended Action: Choose a different name for the vault.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 345
Message: profile already exists
Explanation: This error can occur during addition of a profile if a profile with the
same name already exists within the same vault.
Recommended Action: Choose a different name for the profile.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 346
Message: duplicate MAP
Explanation: A duplicate MAP was added in the Vault configuration file. It is an
internal error.
Recommended Action: Contact customer support and send the appropriate logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 347
Message: vault configuration cache not initialized
Explanation: This error should never occur.
Recommended Action: Contact customer support and send the appropriate logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
231
NetBackup status codes
NetBackup status codes
NetBackup status code: 348
Message: specified report does not exist
Explanation: An invalid Vault report was requested for generation. It is an internal
error.
Recommended Action: Contact customer support and send the appropriate logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 349
Message: incorrect catalog backup policy
Explanation: This error can occur when a Vault session tries to run a catalog
backup. The specified policy for the catalog backup in the Vault profile is either
blank or is not of type NBU-Catalog.
Recommended Action: Verify that you specified a catalog backup policy for the
catalog backup in the Vault profile and that the policy is of type NBU-Catalog.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 350
Message: incorrect vault catalog backup schedule
Explanation: This error can occur when a Vault session tries to run a catalog
backup. The specified Vault catalog backup schedule for catalog backup in the
Vault profile is either blank or is not of type Vault Catalog Backup.
Recommended Action: Verify that you specified a Vault Catalog Backup schedule
for the catalog backup in the Vault profile. Also verify that the schedule is of type
Vault Catalog Backup.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 351
Message: all configured vault steps failed
Explanation: This error occurs when multiple Vault steps are configured for a
session and all of them fail.
Recommended Action: For duplication and catalog backup steps, use the Activity
Monitor to check the status of the respective jobs that Vault started. For Eject step
232
NetBackup status codes
NetBackup status codes
status, check the Detailed Status tab of the Job Details dialog box for the Vault
job.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 400
Message: Server Group Type is Invalid
Explanation: The creation of a server group fails because the server group type
is invalid.
Recommended Action: Do the following, as appropriate:
■
Select a valid server group type: MediaSharing, NetBackup OpsCenter, or
AltServerRestore.
■
For detailed troubleshooting information, create the admin debug log directory
and retry the operation. Check the resulting debug logs. Additional debug
information can be found in the logs for nbemm (originator ID 111) which uses
unified logging.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 401
Message: Server Group Already Exists
Explanation: The attempt to create a server group failed. The server group already
exists.
Recommended Action: Do the following, as appropriate:
■
Verify that the specified server group name is not in use.
■
Create the server group by specifying a name that is not currently in use.
■
For detailed troubleshooting information, create the admin debug log directory
and retry the operation. Check the resulting debug logs. Additional debug
information can be found in the log for nbemm (originator ID 111), which uses
unified logging.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 402
Message: Server Group Already Exists with a different type
233
NetBackup status codes
NetBackup status codes
Explanation: The attempt to create a server group failed. The server group name
is already in use by a server group with a different group type.
Recommended Action: Do the following, as appropriate:
■
Verify that the specified server group name is not in use.
■
Try to create the server group by specifying a name that is not currently in use.
■
For detailed troubleshooting information, create the admin debug log directory
and retry the operation. Check the resulting debug logs. Additional debug
information can be found in the log for nbemm (originator ID 111), which uses
unified logging.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 403
Message: Server Group Active State is not valid
Explanation: The attempt to create a server group failed. The server group state
was invalid.
Recommended Action: Do the following, as appropriate:
■
Valid server group states are: ACTIVE and INACTIVE
■
For detailed troubleshooting information, create the admin debug log directory
and retry the operation. Check the resulting debug logs. Additional debug
information can be found in the log for nbemm (originator ID 111), which uses
unified logging.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 404
Message: Server Group does not exist
Explanation: An operation was tried by using a server group that does not exist.
Recommended Action: Do the following, as appropriate:
■
Verify that the specified media is correct.
■
Verify the media ownership.
■
Verify that the server group exists.
234
NetBackup status codes
NetBackup status codes
■
Verify that the server where the operation is performed is a member of the
owning server group. If not, try the operation from a server that is a member of
the server group.
■
For detailed troubleshooting information, create the admin debug log directory
and retry the operation. Check the resulting debug logs. Additional debug
information can be found in the log for nbemm (originator IDs 111 and 143),
which uses unified logging.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 405
Message: Member’s server type not compatible with Server Group
Explanation: The attempt to add or update a server group failed. A member’s
server type was not valid for the specified server group type.
Recommended Action: Do the following, as appropriate:
■
The Media Sharing server group can contain the following types of servers:
Master, Media, NDMP, and cluster.
■
For detailed troubleshooting information, create the admin debug log directory
and retry the operation. Check the resulting debug logs. Additional debug
information can be found in the log for nbemm (originator IDs 111 and 143),
which uses unified logging.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 406
Message: The computer specified is not a member of the server group specified
Explanation: A server that is not a member of the server group that owns the
media performed an operation on a media.
Recommended Action: Do the following, as appropriate:
■
Verify that the specified media is correct.
■
Verify the media ownership.
■
Verify that the server where the operation is performed is a member of the
owning server group. If not, try the operation from a server that is a member of
the server group.
■
For detailed troubleshooting information, create the admin debug log directory
and retry the operation. Check the resulting debug logs. Additional debug
235
NetBackup status codes
NetBackup status codes
information can be found in the log for nbemm (originator IDs 111 and 143),
which use unified logging.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 407
Message: Member’s NetBackup version not compatible with Server Group
Explanation: The attempt to add or update a server group failed. One of the server
group member’s NetBackup version is not valid for the specified server group type.
Recommended Action: Do the following, as appropriate:
■
Ensure that each member server has a valid NetBackup version for the specified
server group type.
■
For detailed troubleshooting information, create the admin debug log directory
and retry the operation. Check the resulting debug logs. Additional debug
information can be found in the log for nbemm (originator IDs 111 and 143), which
uses unified logging.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 408
Message: Server Group is in use
Explanation: The attempt to delete a server group that failed because the server
group owns one or more media.
Recommended Action: Do the following, as appropriate:
■
Ensure that the server group is not the owner of any media by running
bpmedialist -owner group_name from the master server.
■
For detailed troubleshooting information, create the admin debug log directory
and retry the operation. Check the resulting debug logs. Additional debug
information can be found in the log for nbemm (originator IDs 111 and 143),
which uses unified logging.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 409
Message: Member already exists in server group
236
NetBackup status codes
NetBackup status codes
Explanation: The attempt to add or update a server group failed because one of
the server group members is the same as the one being added.
Recommended Action: Do the following, as appropriate:
■
Ensure that the server group member that you add does not already exist in the
group.
■
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 501
Message: You are not authorized to use this application.
Explanation: The user is not authorized to use one of the NetBackup Java
Administration utilities on the host that is specified in the login dialog box.
Recommended Action: Check the auth.conf file on the host that is specified in
the NetBackup Java login dialog box for the proper authorization. If the auth.conf
file does not exist, it must be created with the proper entry for this user name. More
details on the auth.conf file are available.
See NetBackup Administrator's Guide, Volume I.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 502
Message: No authorization entry exists in the auth.conf file for user name
username. None of the NetBackup Java applications are available to you.
Explanation: The user name is not authorized to use any NetBackup Java
applications on the host that is specified in the logon dialog box.
Recommended Action: Check the auth.conf file on the computer (host name)
specified in the NetBackup Java logon dialog box for the proper authorization. If
the file does not exist, create it with the proper entry for this user name. More details
on the auth.conf file are available.
See NetBackup Administrator's Guide, Volume I.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 503
Message: Invalid user name.
237
NetBackup status codes
NetBackup status codes
Explanation: For UNIX host logon, the NetBackup Java application server on the
host where the logon is requested does not recognize the user name.
For Windows host logon, the NetBackup Java authentication service on the host
where the logon is requested does not have sufficient privileges to grant the request.
Recommended Action: Do the following, as appropriate:
■
For UNIX hosts: the user name must be a valid user name in the passwd file on
the host that is specified in the logon dialog box.
■
For Windows hosts: refer to the LogonUser function in the section titled
Client/Server Access Control Functions of the Windows Platform Software
Developer’s Kit to determine the required privileges.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 504
Message: Incorrect password.
Explanation: For logon to a UNIX host, the user name is recognized on the host
where the logon is requested, but the supplied password is incorrect.
For logon to a Windows host, the attempt to log in the user failed. The failure can
be due to an unrecognized user in the specified domain.
Recommended Action: Do the following, as appropriate:
■
Enter the correct password.
■
On Windows hosts: The exact error can be found in the bpjava-msvc log file.
For more details, refer to the LogonUser function in the section Client/Server Access
Control Functions of the Windows Platform Software Developer’s Kit.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 505
Message: Cannot connect to the NetBackup Java authentication service on host
on the configured port - (port_number). Check the log file for more details.
Explanation: The initial connection from the NetBackup Java interface to its
authentication service on (host) was on the configured_port_number that was
mentioned in the error message. Either the port is in use by another application or
the NetBackup Java interface and its application server are not configured with the
238
NetBackup status codes
NetBackup status codes
same port. The default port is 13722. The NetBackup Administration Console
log file should contain more detail about this error.
Recommended Action: Do the following, as appropriate:
■
On UNIX, compare the bpjava-msvc entry in the /etc/services file with the
BPJAVA_PORT entry in the /usr/openv/java/nbj.conf file
On Windows, compare the bpjava-msvc entry in the
%systemroot%\system32\drivers\etc\services file with the
install_path\java\setconf.bat file (Windows). The entries must match.
■
Ensure that no other application uses the port that is configured for the
NetBackup Java interface.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 506
Message: Cannot connect to the NetBackup Java user service on host on port
port_number. If successfully logged in before, retry your last operation. Check the
log file for more details.
Explanation: After the NetBackup Java authentication service validates the user
name, a NetBackup Java user service is used for all other service requests from
the NetBackup Java interface. Communication was tried between the NetBackup
Java interface and the user service on host (host) on the port number that was
specified in the error message. More information about various port configuration
options is available.
See NetBackup Administrator's Guide, Volume I.
The NetBackup Administration Console log file should contain more detail about
this error.
■
On UNIX: the port configuration options are specified in the
/usr/openv/netbackup/bp.conf file or through the NetBackup Administration
Console Host Properties.
■
On Windows: from the NetBackup Administration Console, select Host
Properties. Select Properties on the Actions menu. The Port Ranges tab
contains the port options.
Recommended Action: Do the following, as appropriate:
■
Restart the NetBackup Java interface and log in again.
■
If the problem persists, enable detailed debug logging.
■
Restart the NetBackup Java interface and examine the logs.
239
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 507
Message: Socket connection to the NetBackup Java user service has been broken.
Retry your last operation. Check the log file for more details.
Explanation: The connection was broken to the NetBackup Java application server
that is running on the NetBackup host (where you are logged in). The NetBackup
Administration Console log file should contain more detail about this error.
Recommended Action: Do the following, as appropriate:
■
Retry the last operation.
■
If the problem persists, restart the NetBackup Java interface and try again.
■
If the problem still persists, enable detailed debug logging.
See "Setting Media Manager debug logging to a higher level" in the NetBackup
Logging Reference Guide.
■
Restart the NetBackup Java interface and examine the logs.
Note: You may have network or system problems unrelated to NetBackup.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 508
Message: Cannot write file.
Explanation: This cause of this error is one of the following:
■
The NetBackup Java user service tries to write to a file that does not have write
permissions. The solution is to enable write privileges.
■
The NetBackup Java user service tries to write to a temporary file whose unique
name cannot be constructed. This condition is unlikely, but can result from an
exhaustion of system resources (from the filling of the name space).
Recommended Action: Retrieve the specific details from the user service log
files.
Enable detailed debug logging as explained in the following topic:
See "Setting Media Manager debug logging to a higher level" in the NetBackup
Logging Reference Guide.
240
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 509
Message: Cannot execute program.
Explanation: The NetBackup Java authentication or user service reported an error
that relates to the creation (or demise) of a child job process. The NetBackup Java
service programs create separate jobs to accomplish specific tasks, as follows. The
NetBackup Java authentication service creates the NetBackup Java user service.
When it is created and connected to, the NetBackup Java user service creates all
other child processes on behalf of requests from the NetBackup Java interface.
The cause of status code 509 can be found in the appropriate log file, either for
bpjava-msvc, bpjava-susvc, or bpjava-usvc.
The cause can be categorized as one of the following:
■
A job (started by either the NetBackup Java authentication service or user
service) no longer exists and did not report its result status.
■
The NetBackup Java service cannot monitor a job (started by either the
NetBackup Java authentication service or user service). The reason it cannot
monitor is probably due to a lack of system resources (insufficient memory).
■
The maximum number of non-transient Activity Monitor jobs (>100) has already
been started.
Recommended Action: Do the following, as appropriate:
■
If the problem persists, restart the NetBackup Java interface and try again.
■
If the problem still persists, enable detailed debug logging as explained in the
following topic:
See "Setting debug logging to a higher level" in the NetBackup Logging
Reference Guide.
■
Restart the NetBackup Java interface and examine the logs.
The error is probably the result of a system resource issue. When detailed debug
logging is enabled, you can retrieve the details from the bpjava-msvc,
bpjava-susvc, or bpjava-usvc log files.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 510
Message: File already exists: file_name
241
NetBackup status codes
NetBackup status codes
Explanation: The NetBackup Java user service try to create a file that already
exists.
Recommended Action: Remove the file, which can be identified in the user service
log files.
See "Troubleshooting error messages in the NetBackup Administration Console"
in the NetBackup Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 511
Message: NetBackup Java application server interface error.
Explanation: In some instances, this message concludes with
Check the log file for more details.
This generic error for all non-socket IO/connection-broken related errors (status
code 507) can occur when data is processed from the NetBackup Java
authentication or user services. The Java exception provides some additional detail
about the error.
This error usually results from system or network problems.
Recommended Action: Do the following, as appropriate:
■
If the problem persists, restart the NetBackup Java interface and try again.
■
If the problem still persists, enable detailed debug logging as explained in the
following topic:
See "Setting Media Manager debug logging to a higher level" in the NetBackup
Logging Reference Guide.
■
Restart the NetBackup Java interface and examine the logs.
The error is probably the result of a system resource issue. When detailed debug
logging is enabled, the details can be retrieved from the bpjava-msvc,
bpjava-susvc, or bpjava-usvc log files.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 512
Message: Internal error - a bad status packet was returned by NetBackup Java
application server that did not contain an exit status code.
242
NetBackup status codes
NetBackup status codes
Explanation: The NetBackup Java authentication or user service returned a data
packet that indicated an error, but no status code or error message was contained
within it.
Recommended Action: Do the following, as appropriate:
■
If the problem persists, restart the NetBackup Java interface and try again.
■
If the problem still persists, enable detailed debug logging as explained in the
following topic:
See "Setting Media Manager debug logging to a higher level" in the NetBackup
Logging Reference Guide.
■
Restart the NetBackup Java interface and examine the logs.
The error is probably the result of a system resource issue. When detailed debug
logging is enabled, the details can be retrieved from the bpjava-msvc,
bpjava-susvc, or bpjava-usvc log files.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 513
Message: bpjava-msvc: the client is not compatible with this server version
(server_version).
Explanation: The NetBackup Java application server (on the remote host you log
in to) is not the same version as the NetBackup Java interface on your local host.
The two are therefore incompatible.
Recommended Action: Do the following, as appropriate:
■
Log in to a different NetBackup remote host.
■
Upgrade the NetBackup software on either of the following: the computer that
is specified in the logon dialog box or the local host where you started the
NetBackup Java interface.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 514
Message: NetBackup Java: bpjava-msvc is not compatible with this application
version (application_version). You may try logon to a different NetBackup host or
exit the application. The remote NetBackup host has to be configured with the same
version of NetBackup as the host you started the application on.
Explanation: In some instances, this message concludes with
243
NetBackup status codes
NetBackup status codes
Check the log file for more details.
The NetBackup Java application server (on the remote host you log in to) is not the
same version as the NetBackup Java interface on your local host. The two are
therefore incompatible.
Recommended Action: Do the following, as appropriate:
■
Log in to a different NetBackup remote host.
■
Upgrade the NetBackup software on either of the following: the specified
computer in the logon dialog box or the local host where you started the
NetBackup Java interface.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 516
Message: Could not recognize or initialize the requested locale - (locale_NetBackup
Java_was_started_in).
Explanation: This status concerns the UNIX locale configuration (or Windows
regional settings) defined on the host that was specified in the NetBackup Java
logon dialog box. At logon, the locale configuration is passed to the NetBackup
Java authentication service. Status 516 is generated if the locale is not recognized
or if the locale of the user service cannot be initialized.
The rules in the following files determine how a valid locale is recognized:
/usr/openv/msg/.conf on UNIX and install_path\msg\lc.conf on Windows.
When the locale is validated, initialization of the locale in the user service’s
environment is tried (by means of setlocale).
Recommended Action: On the specified host in the NetBackup Java logon dialog
box, check the configuration file to ensure that a mapping is available for the
indicated locale.
For information on locale configuration and mapping, refer to the NetBackup
Administrator's Guide, Volume II.
If there is a mapping, try to set the mapped locale on the host that was specified in
the NetBackup Java logon dialog box. This system may not be configured properly.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
244
NetBackup status codes
NetBackup status codes
NetBackup status code: 517
Message: Cannot connect to the NetBackup Java user service by VNETD on host
on port configured_port_number. If successfully logged on beforehand, retry your
last operation. Check the log file for more details.
Explanation: After the NetBackup Java authentication service validates the user
name on the logon dialog box for access, all Administration console service requests
use an NetBackup Java user service. Communication between the Administration
console and user service is tried to host (host) on the specified port number in the
error message by using VNETD. (The NetBackup Java configuration option
NBJAVA_CONNECT_OPTION is set to 1.) The NetBackup Administration Console
log file should contain more detail about this error.
Recommended Action: Do the following, as appropriate:
■
On UNIX: Compare the VNETD entry in the /etc/services file with the
VNETD_PORT entry in /usr/openv/java/nbj.conf
On Windows: Compare the VNETD entry with the VNETD_PORT entry in the
install_path\java\setconf.bat file.
These entries must match.
■
Ensure that no other application uses the port that is configured for VNETD.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 518
Message: No ports available in range (port_number) through (port_number) per
the NBJAVA_CLIENT_PORT_WINDOW configuration option.
Explanation: All the ports in the specified range are in use. Too many users
(concurrent) of the NetBackup Java interface or too few configured ports can cause
this error.
Recommended Action: Do the following, as appropriate:
■
Restart the NetBackup Java interface and try again.
■
If the problem persists, increase the range of ports by changing the
NBJAVA_CLIENT_PORT_WINDOW option in the /usr/openv/java/nbj.conf
file (UNIX) or the install_path\java\setconf.bat file (Windows).
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
245
NetBackup status codes
NetBackup status codes
NetBackup status code: 519
Message: Invalid NBJAVA_CLIENT_PORT_WINDOW configuration option value:
(option_value).
Explanation: The value for the NetBackup Java configuration option
NBJAVA_CLIENT_PORT_WINDOW is invalid.
Recommended Action: Correct the value in file /usr/openv/java/nbj.conf
(UNIX) or install_path\java\setconf.bat file (Windows).
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 520
Message: Invalid value for NetBackup Java configuration option (option_name):
(option_value).
Explanation: The specified NetBackup Java configuration option has an invalid
value.
Recommended Action: Correct the value in file /usr/openv/java/nbj.conf
(UNIX) or install_path\java\setconf.bat file (Windows).
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 521
Message: NetBackup Java Configuration file (file_name) does not exist.
Explanation: The configuration file for the NetBackup Java interface was not found.
Recommended Action: Make sure that the configuration file the NetBackup Java
interface exists and is properly formatted.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 522
Message: NetBackup Java Configuration file (file_name) is not readable due to
the following error: (message).
Explanation: The specified NetBackup Java configuration file exists but is not
readable.
Recommended Action: Correct the file as specified in the message.
246
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 523
Message: NetBackup Java application server protocol error.
Explanation: In some instances, this message concludes with the following:
Check the log file for more details.
The NetBackup Java interface received an incorrectly formatted protocol sequence
from its application server.
Recommended Action: Do the following, as appropriate:
■
If the problem persists, restart the NetBackup Java interface and try again.
■
If the problem still persists, enable detailed debug logging as explained in the
following topic:
See "Setting Media Manager debug logging to a higher level" in the NetBackup
Logging Reference Guide.
■
Restart the NetBackup Java interface and examine the logs.
Note: The error is probably the result of a system resource issue. When detailed
debug logging ID is enabled, the details can be retrieved from the bpjava-msvc,
bpjava-susvc, or bpjava-usvc log files.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 525
Message: Cannot connect to the NetBackup Java authentication service by VNETD
on (host) on port (vnetd_configured_port_number). Check the log file for more
details.
Explanation: The NetBackup Java authentication service authenticates the user
name that is provided in the logon dialog box. Communication between the
NetBackup Administration Console and the authentication service is tried to host
host on the configured VNETD port number that error message specifies. The
NetBackup Administration Console log file should contain more detail about this
error.
Recommended Action: Do the following, as appropriate:
247
NetBackup status codes
NetBackup status codes
■
On UNIX: Compare the VNETD entry in the /etc/services file with the
VNETD_PORT entry in /usr/openv/java/nbj.conf
On Windows: Compare the VNETD entry with the VNETD_PORT entry in the
install_path\java\setconf.bat file.
These entries must match.
■
Ensure that no other application uses the port that is configured for VNETD.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 526
Message: bpjava authentication service connection failed
Explanation: Cannot connect to the bpjava authentication service by NetBackup
PBX at port 1556 (default).
Recommended Action: Do the following, as appropriate:
■
If the target server is running an invalid version of NetBackup, the Java GUI
attempts a further connection by the VNETD port 13724. No action is required.
■
Check that the PBX service or daemon has been started on the server and that
NetBackup services are running.
■
Check if the Java GUI properties (java/nbj.conf) have been set up to connect
to a PBX port other than 1556.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 527
Message: bpjava user service connection if connection to pbx on port 1556 fails
Explanation: Unable to connect to the bpjava user service using NetBackup PBX
at port 1556 (default).
Recommended Action: Do the following, as appropriate:
■
Check that the PBX service or daemon has been started on the server and that
NetBackup services are running.
■
If the target server is running an invalid version of NetBackup, the Java GUI
attempts a further connection by the VNETD port 13724. No action is required.
■
Check if the Java GUI properties (java/nbj.conf) have been modified to attempt
a PBX port other than 1556.
248
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 537
Message: Connection to the NetBackup database was not successful. Ensure that
the database service is running.
Explanation: The NetBackup database service should be running while the Account
Lockout option is enabled.
Recommended Action: Start the NetBackup database service.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 538
Message: unable to login
Explanation: Verification of the X.509 certificate failed while connecting to the
bpjava user on the host. This error can be caused by a clock skew between the
NetBackup host and this computer. This issue occurs when the difference in time
between the host from where you invoke the Remote Administration Console and
the master server is greater than 24 hours.
Recommended Action: Synchronize the time on both hosts or decrease the
difference in time to less than 24 hours.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 552
Message: The Certificate Revocation List (CRL) could not be downloaded and,
therefore, the certificate revocation status could not be verified. For more information,
see the NetBackup logs.
Explanation: The Certificate Revocation List (CRL) could not be downloaded. The
possible causes include the following:
■
The certmapinfo.json file is missing.
■
The certmapinfo.json file does not contain the CRL path.
■
The CRL file is missing.
■
The CRL file is corrupted.
■
The CRL file could not be locked.
249
NetBackup status codes
NetBackup status codes
■
The CRL file could not be unlocked.
Recommended Action: For more information, see the bpjava logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 600
Message: an exception condition occurred
Explanation: The synthetic backup job encountered an exception condition.
Recommended Action: Contact customer support and send the appropriate debug
logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 601
Message: unable to open listen socket
Explanation: The bpsynth process cannot open a socket to listen for incoming
connections from the bptm or the bpdm processes that were started for the following:
for reading backup images or for writing the synthetic image on the media servers.
Recommended Action: Check the OS error that was reported in the error message,
which bpsynth logged in the NetBackup error log. This error helps to diagnose the
problem. Ensure that the bpsynth binary matches the installed NetBackup version.
Retry the synthetic backup job. If the problem persists, contact customer support
and provide the appropriate logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 602
Message: cannot set non-blocking mode on the listen socket
250
NetBackup status codes
NetBackup status codes
Explanation: The bpsynth process is unable to set the non-blocking socket option
on the listen socket.
Recommended Action: Check the OS error that was reported in the error message,
which was logged in the NetBackup error log. The error helps to diagnose the
problem. Ensure that the bpsynth binary matches the installed NetBackup version.
If the condition persists, contact customer support and send the appropriate logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 603
Message: cannot register handler for accepting new connections
Explanation: The bpsynth process cannot register the listen socket with the ACE
reactor.
Recommended Action: Ensure that the bpsynth binary matches the installed
NetBackup version. Retry the synthetic backup job. If the problem persists, contact
customer support and send the appropriate logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 604
Message: no target storage unit specified for the new job
Explanation: A mismatch occurred between the storage units that are known to
NetBackup and the specified target storage unit.
Recommended Action: Retry the synthetic backup job. If the problem persists,
contact customer support and provide appropriate logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
251
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 605
Message: received error notification for the job
Explanation: This error code is no longer used.
Recommended Action: Submit a problem report along with the appropriate logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 606
Message: no robot on which the media can be read
Explanation: bpsynth returns this error when it cannot find a robot on which to
read a particular media ID that contains backup images to be synthesized. The
media ID is included in the message that bpsynth logs. This error should not occur.
Recommended Action: Contact customer support and provide the appropriate
logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 607
Message: no images were found to synthesize
Explanation: The database query to obtain the images to synthesize for the given
policy did not return any images.
Recommended Action: Ensure that a synthetic full backup has one full image
(real or synthetic) and one or more subsequent incremental images (differential or
cumulative) to synthesize. For a cumulative synthetic backup, there must be two
or more incremental (differential or cumulative) images to synthesize. Adjust your
schedules so the appropriate backup jobs complete successfully before the synthetic
252
NetBackup status codes
NetBackup status codes
job is run. The scheduler does not retry a synthetic backup job that fails with this
error code.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 608
Message: storage unit query failed
Explanation: The database query to obtain all storage units failed.
Recommended Action: Verify that the bpdbm process is running and that no errors
were logged to the NetBackup error log. Restart the bpdbm process (on UNIX), or
the NetBackup Database Manager Service (on Windows) and retry the synthetic
backup job. If the problem persists, contact customer support and send the
appropriate logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 609
Message: reader failed
Explanation: The bptm or the bpdm reader process was terminated with an error.
Recommended Action: See the NetBackup error log for the errors that the bpsynth
and bptm or bpdm reader logged. The error message should contain the actual error
that the bptm or the bpdm reader reports.
See the NetBackup Troubleshooting Guide for information on the error that the
bptm or the bpdm reader reports. The media may not be present or is defective or
the drive that was used for reading the media is defective. If the problem persists,
contact customer support and send the appropriate logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
253
NetBackup status codes
NetBackup status codes
NetBackup status code: 610
Message: endpoint terminated with an error
Explanation: An error indication was received on the connection to the bptm or
the bpdm process.
Recommended Action: Review the errors in the NetBackup error log that the
following processes logged: bpsynth and bptm or bpdm. Refer to the debug logs
for these processes for more information. The connection may have broken due to
the following: an error condition that the bptm or the bpdm process detects or network
problems between the master and the media server. Check the network connectivity
between the master and the media server. Retry the job and if the problem persists,
contact customer support, and send the appropriate logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 611
Message: no connection to reader
Explanation: A connection to the bptm or the bpdm reader process does not exist
to communicate with the reader.
Recommended Action: This error should not occur. Submit a problem report
along with the appropriate logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 612
Message: cannot send extents to bpsynth
Explanation: This error code is no longer used.
Recommended Action: Submit a problem report along with the appropriate logs.
A complete list of required logs and configuration information is available.
254
NetBackup status codes
NetBackup status codes
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 613
Message: cannot connect to read media server
Explanation: The bpsynth process was unable to connect to the media server to
read a backup image.
Recommended Action: Ensure that network connectivity exists between the
master server and the specified media server. Examine the NetBackup error log
for any error messages that bpsynth logged. For more information, refer to the
debug logs for bpsynth on the master server and bpcd and bptm or bpdm on the
media server.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 614
Message: cannot start reader on the media server
Explanation: The bpsynth process was unable to start the bptm or the bpdm
process to read a backup image to be synthesized.
Recommended Action: Do the following, as appropriate:
■
Examine the NetBackup error log for any errors that bpsynth logged. For more
information, refer to the following debug logs: for bpsynth on the master server
and for bpcd and bptm or bpdm on the media server. Ensure that the bptm or the
bpdm binaries on the media server are executable and are not corrupt. Try
running bptm or bpdm commands locally on the media server to ensure that the
binary is executable and not corrupt. For instance, you can run the following
command
/bp/bin/bptm -count -rn 0 -rt 8
where robot number is 0 and the robot type is 8. The robot type that corresponds
to the robot number can be taken from the command line that is logged in the
255
NetBackup status codes
NetBackup status codes
debug log for bptm. This command displays the counts for the up, shared, and
assigned drives in the robot.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 615
Message: internal error 615
Explanation: This error code is no longer used.
Recommended Action: Submit a problem report along with the appropriate logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 616
Message: internal error 616
Explanation: This error code is no longer used.
Recommended Action: Submit a problem report along with the appropriate logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 617
Message: no drives available to start the reader process
Explanation: No drives are available to start the bptm process to read a backup
image to be synthesized.
Recommended Action: Ensure that sufficient drives are available before you
restart the job.
256
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 618
Message: internal error 618
Explanation: This error code is no longer used.
Recommended Action: Contact customer support and send the appropriate logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 619
Message: internal error 619
Explanation: This error code is no longer used.
Recommended Action: Contact customer support and send the appropriate logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 620
Message: internal error 620
Explanation: This error code is no longer used.
Recommended Action: Contact customer support and send the appropriate logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
257
NetBackup status codes
NetBackup status codes
NetBackup status code: 621
Message: unable to connect to bpcoord
Explanation: This error code is no longer used.
Recommended Action: Submit a problem report along with the appropriate logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 622
Message: connection to the peer process does not exist
Explanation: The underlying connection to the peer bptm or bpdm process does
not exist. This error should not occur.
Recommended Action: Contact customer support and send the appropriate logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 623
Message: execution of a command in a forked process failed
Explanation: The failure normally occurs during the execution of a command on
a media server through bpcd. Examine the NetBackup error log for additional error
messages. Also refer to the debug logs for bpsynth (on the master server) and
bpcd (on the media server) to get an explanation of the failure. A common cause
of the failure is insufficient memory, file system full, or insufficient swap space.
Recommended Action: Retry the job and if the problem persists, contact customer
support and send the appropriate logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
258
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 624
Message: unable to send a start command to a reader or a writer process on
media server
Explanation: The bpsynth process is unable to send a command to the bptm or
the bpdm process on the media server.
Recommended Action: Ensure that network connectivity exists between the
master and the media server. Look for additional error messages in the NetBackup
error log. More detailed information is present in the debug logs for bpsynth (on
master server) and bptm or bpdm on the media server. If the problem persists,
contact customer support and send the appropriate logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 625
Message: data marshalling error
Explanation: Problems were encountered while sending data over the connection.
This error should not occur.
Recommended Action: Contact customer support and send the appropriate logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 626
Message: data un-marshalling error
Explanation: Problems were encountered in the parsing of the messages that
bpsynth received. This error should not occur.
Recommended Action: Contact customer support and send the appropriate logs.
259
NetBackup status codes
NetBackup status codes
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 627
Message: unexpected message received from bpsynth
Explanation: This error code is no longer used.
Recommended Action: Submit a problem report along with the appropriate logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 628
Message: insufficient data received
Explanation: This error occurs in the following situation: partial data is read from
the input socket and cannot be parsed until the remaining data that comprises the
message is read. The lower layers encounter this error; it should not cause a process
to be terminated.
Recommended Action: If this error causes the bpsynth binary to hang or
malfunction, contact customer support and send the appropriate logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 629
Message: no message was received from bptm
Explanation: This error is returned when no message is received from the bptm
process in response to the command or query that was executed by using bptm.
260
NetBackup status codes
NetBackup status codes
Recommended Action: Look for additional error messages in the following logs:
the NetBackup error log and the debug logs for bpsynth on the master server and
bptm on the media server. A system condition (insufficient memory, file system full,
insufficient swap space) on the media server may prevent the bptm process from
sending the response. Verify the network connectivity between the master and the
media server. If no explanation is found for the failure and the problem persists,
contact customer support and send the appropriate logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 630
Message: unexpected message was received from bptm
Explanation: This error code is no longer used.
Recommended Action: Contact customer support and send the appropriate logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 631
Message: received an error from bptm request to suspend media
Explanation: The bpsynth process was unable to suspend a media that contained
one or more images to be synthesized. A message in the bpsynth legacy log lists
the media IDs to be suspended. The bpsynth log also includes a failure message
to indicate which particular media in the list was not suspended. media (ordinal)
indicates the unsuspended media by means of its order in the list. For example, if
the unsuspended media was the second media in the list, the failure message says
media (1).
Recommended Action: Examine the bptm debug log for more information on the
reason for the suspend failure. The bpsynth process ignores this error and continues
to process. It has the potential to fail later if the media with the images to be read
261
NetBackup status codes
NetBackup status codes
gets assigned to another backup or restore job. If the synthetic backup job fails, fix
the condition that lead to the suspend failure and retry the job.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 632
Message: received an error from bptm request to un-suspend media
Explanation: The bpsynth process was unable to un-suspend a media that it
suspended at the start of the synthetic backup job. A message in the bpsynth legacy
log lists the media IDs to be un-suspended. The bpsynth log also includes a failure
message to indicate which particular media in the list was not un-suspended. media
(ordinal) indicates the media by means of its order in the list. For example, if the
media that was not un-suspended was the second media in the list, the failure
message says media (1).
Recommended Action: Look at the debug log for the bptm process on the media
server for an explanation of the un-suspend failure and the media ID. Try to
un-suspend the tape manually by using the bpmedia command.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 633
Message: unable to listen and register service by vnetd
Explanation: This error code is no longer used.
Recommended Action: Submit a problem report along with the appropriate logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 634
Message: no drives available to start the writer process
Explanation: The bpsynth process cannot start the synthetic backup job because
no drives were available in the target storage unit for the writer. The storage unit
may be in use by a restore or another synthetic backup job.
262
NetBackup status codes
NetBackup status codes
Recommended Action: Ensure that the target storage unit that is configured for
the synthetic backup schedule has an available drive to write the synthetic backup
image.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 635
Message: unable to register handle with the reactor
Explanation: Unable to register a handle with the ACE reactor to monitor events
on the handle. This error can occur in bpsynth.
Recommended Action: Examine NetBackup error log for any errors that were
logged for the job. Refer to the debug logs for bpsynth for more information. Retry
the synthetic backup job. If the problem persists, contact customer support and
send the appropriate logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 636
Message: read from input socket failed
Explanation: The read from an input socket failed. The underlying connection has
been broken.
Recommended Action: The bpsynth process encountered an error while reading
from an input socket. The socket may be between bpsynth and bptm or bpdm.
The errno that was logged to the NetBackup error log indicates the reason for the
failure. For more information, refer to the following: the debug log for bpsynth (on
the master server) and for the bptm or the bpdm reader or writer processes (on the
media server). Check the network connectivity between the master and the media
server. Rerun the synthetic backup job. If the problem persists, contact customer
support and send the appropriate logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
263
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 637
Message: write on output socket failed
Explanation: The write to an output socket failed. The underlying connection has
been broken.
Recommended Action: The bpsynth process encountered an error while writing
to an output socket. The socket is between bpsynth and bptm or bpdm.
The errno that logged to the NetBackup error log indicates the reason for the failure.
For more information, refer to the following: the debug log for bpsynth (on the
master server) and for the bptm or the bpdm reader or writer process (on the media
server). Check the connectivity between the master and the media server. Retry
the synthetic backup job. If the problem persists, contact customer support and
send the appropriate logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 638
Message: invalid arguments specified
Explanation: The bpsynth command fails with this error code if incorrect arguments
were specified.
Recommended Action: Refer to the bpsynth command line arguments (by using
-help) for the correct argument specification. If the synthetic backup job was started
manually by the command line, correct the arguments to bpsynth and rerun the
job. If the synthetic backup job was scheduled or started with the console, ensure
that the bpsynth and the nbjm binaries match the installed NetBackup version.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 639
Message: specified policy does not exist
264
NetBackup status codes
NetBackup status codes
Explanation: The policy that was specified on the bpsynth command does not
exist in the database. Either the command line or nbjm initiated the bpsynth
command. If nbjm initiated it, the policy may have been deleted after nbjm started
bpsynth and before bpsynth issued the database query.
Recommended Action: If bpsynth is initiated with the command line, rerun the
command for an existing policy. If the problem persists after you verify the following,
contact customer support and send the appropriate logs:
■
The synthetic backup job was scheduled or started by using the NetBackup
Administration Console (manual start).
■
The policy exists in the bppllist command configuration.
■
Check the logs for nbjm, which uses unified logging (OID 117).
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 640
Message: specified schedule was not found
Explanation: The schedule on the bpsynth command did not exist in the specified
policy definition in the database due to either of the following:
■
The command line initiated the bpsynth command
■
The specified schedule was deleted from the policy after nbjm started bpsynth,
before bpsynth issued the database query.
Recommended Action: If the command line initiated bpsynth, do the following:
rerun the command with the correct synthetic schedule label defined in the policy
of the synthetic backup job to be run. If the synthetic backup job was scheduled or
started with the NetBackup Administration Console, define a new schedule in
the policy and retry the job. If the problem persists, contact customer support and
send the appropriate logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
265
NetBackup status codes
NetBackup status codes
NetBackup status code: 641
Message: invalid media type specified in the storage unit
Explanation: The media type that was specified in the target storage unit is invalid
for synthetic backup. Synthetic backup images can only be written to disk, disk
staging, and Media Manager type of storage units.
Recommended Action: Ensure that the target storage unit that was configured
for synthetic backup is a disk, disk staging, or Media Manager type (not NDMP
type). Rerun synthetic backup with the appropriate storage unit.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 642
Message: duplicate backup images were found
Explanation: The database query returned duplicate backup IDs. This error should
not occur.
Recommended Action: Contact customer support and send the appropriate logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 643
Message: unexpected message received from bpcoord
Explanation: This error code is no longer used.
Recommended Action: Submit a problem report along with the appropriate logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 644
Message: extent directive contained an unknown media ID
266
NetBackup status codes
NetBackup status codes
Explanation: This error code is no longer used.
Recommended Action: Contact customer support and send the appropriate logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 645
Message: unable to start the writer on the media server
Explanation: The bpsynth process was unable to start the following: the bptm or
the bpdm process on the media server that is associated with the target storage unit
to write the synthetic image.
Recommended Action:
Examine the NetBackup error log for any messages that bpsynth logged. For more
information, refer to the following: the debug logs for bpsynth on the master server
and bpcd and bptm or bpdm on the media server. Ensure that the bptm or the bpdm
binaries on the media server are executable and are not corrupt. Try to run the
bptm or the bpdm commands locally on the media server to ensure that the binary
is executable and not corrupt. For instance, you can run the following command:
install_path/netbackup/bin/bptm -count -rn 0 -rt 8
where robot number is 0 and robot type is 8. The robot type that corresponds to
the robot number can be taken from the command line that is logged in the debug
log for bptm. This command displays the counts for the up, shared, and assigned
drives in the robot. In case the synthetic image is to be written to a disk storage
unit, verify the bpdm binary by running the following command:
install_path/netbackup/bin/bpdm
It should print the following:
bpdm: media manager operation not specified
Retry the synthetic backup job. If the problem persists, contact customer support
and send the appropriate logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
267
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 646
Message: unable to get the address of the local listen socket
Explanation: The bpsynth process cannot obtain the address of the opened listen
socket. The bpsynth process needs the address to receive incoming connections
from the bptm or the bpdm processes, which were started to read the source images.
This problem should not happen. The library call used to retrieve the address of
the listen socket relies on the underlying system call to obtain the socket address.
The errno that the system call reports is included in the error message and should
help to diagnose the problem.
Recommended Action: Rerun the synthetic backup job. If the problem persists,
contact customer support and send the appropriate logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 647
Message: validation of synthetic image failed
Explanation: This error is returned when bpsynth receives an error from the
database call to validate the synthetic image.
Recommended Action: This error may indicate a problem in the synthetic backup
process. Examine the NetBackup error log for any messages that the following
processes logged: bpsynth and bptm or bpdm. Look at the debug logs for these
processes for additional information. If you cannot resolve the problem, contact
customer support and send the appropriate logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
268
NetBackup status codes
NetBackup status codes
NetBackup status code: 648
Message: unable to send extent message to BPXM
Explanation: The bpsynth process cannot send extent information to the bptm or
the bpdm process that was started to read a specified backup image to synthesize.
Recommended Action: This error indicates a communication problem between
bpsynth and the bptm or the bpdm reader process on the media server. Ensure that
the media server is accessible and that the bptm or the bpdm process is running on
the media server. Examine the NetBackup error log for any errors that the following
logged: bpsynth (on the master server) and the bptm or the bpdm reader process
(on the media server). Examine the debug logs for bpsynth and bptm or bpdm for
additional information. Rerun the synthetic backup job. If the problem persists,
contact customer support and send the appropriate logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 649
Message: unexpected message received from BPXM
Explanation: This error code is no longer used.
Recommended Action: Submit a problem report along with the appropriate logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 650
Message: unable to send extent message to bpcoord
Explanation: This error code is no longer used.
Recommended Action: Submit a problem report along with the appropriate logs.
A complete list of required logs and configuration information is available.
269
NetBackup status codes
NetBackup status codes
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 651
Message: unable to issue the database query for policy
Explanation: The bpsynth process was unable to send the database query for
policy.
Recommended Action: This error indicates a communication problem between
bpsynth and bpdbm. Ensure that bpdbm is running and the bpdbm binary matches
the installed NetBackup version. Examine the NetBackup error log for any errors
that bpdbm and bpsynth logged. Examine the debug logs for bpsynth and bpdbm
for additional information. Restart the bpdbm process (on UNIX) or the NetBackup
Database Manager Service (on Windows) and rerun the synthetic backup job. If
the problem persists, contact customer support and send the appropriate logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 652
Message: unable to issue the database query for policy information
Explanation: The bpsynth process was unable to send the database query for
detailed information about the policy.
Recommended Action: This error indicates a communication problem between
bpsynth and bpdbm. Ensure that bpdbm is running. Examine the NetBackup error
log for any errors that bpdbm and bpsynth logged. Examine the debug logs for
bpsynth and bpdbm for additional information. Restart the bpdbm process (on UNIX)
or the NetBackup Database Manager Service (on Windows) and rerun the synthetic
backup job. If the problem persists, contact customer support and send the
appropriate logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
270
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 653
Message: unable to send a message to bpccord
Explanation: This error code is no longer used.
Recommended Action: Contact customer support and send the appropriate logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 654
Message: internal error 654
Explanation: This error code is no longer used.
Recommended Action: Contact customer support and send the appropriate logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 655
Message: no target storage unit was specified by command line
Explanation: No target storage unit was specified on the bpsynth command line
(-S).
Recommended Action: Rerun bpsynth with the target storage unit specified by
the -S option.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
271
NetBackup status codes
NetBackup status codes
NetBackup status code: 656
Message: unable to send start synth message to bpcoord
Explanation: This error code is no longer used.
Recommended Action: Contact customer support and send the appropriate logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 657
Message: unable to accept connection from the reader
Explanation: The bpsynth process was unable to accept the connection from the
bptm or the bpdm reader process that runs on the media server.
Recommended Action: Examine the NetBackup error log for any errors that
bpsynth and bptm or the bpdm reader process logged. The message that bpsynth
logged includes the error (errno) reported by the system call. Refer to the debug
logs for bpsynth on the master server and bptm or the bpdm process on the media
servers for more information. Ensure that network connectivity exists between the
master and the media servers. If the problem persists, contact customer support
and send the appropriate logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 658
Message: unable to accept connection from the writer
Explanation: The bpsynth process was unable to accept the connection from the
bptm or the bpdm writer process that runs on the media server.
Recommended Action: Examine the NetBackup error log for any errors that
bpsynth and the bptm or the bpdm writer process logged. The message that bpsynth
logged includes the error (errno) reported by the system call. Also refer to the
debug logs for bpsynth on the master server and bptm or the bpdm process on the
272
NetBackup status codes
NetBackup status codes
media server for more information. Ensure that network connectivity exists between
the master and the media servers. If the problem persists, contact customer support
and send the appropriate logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 659
Message: unable to send a message to the writer child process
Explanation: The bpsynth process was unable to send the message that contains
the following to the bptm or the bpdm writer: the host name and the port number of
the bptm or the bpdm reader.
Recommended Action: Examine the NetBackup error log for any errors that
bpsynth and the bptm or the bpdm writer process logged. Refer to the following for
more information: the debug logs for bpsynth on the master server and the bptm
or the bpdm process on the media server. Ensure that network connectivity exists
between the master and the media servers. If the problem persists, contact customer
support and send the appropriate logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 660
Message: a synthetic backup request for media resources failed
Explanation: The request for resources failed due to an internal NetBackup error.
Recommended Action: Create logs as explained in the following topic:
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Rerun the job and send the logs to customer support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
273
NetBackup status codes
NetBackup status codes
NetBackup status code: 661
Message: unable to send exit message to the BPXM reader
Explanation: The bpsynth process cannot send the exit message to indicate the
end of extents messages to the following: bptm or the bpdm reader process on the
media server. The network connection between the master and the media server
may have terminated or the bptm or the bpdm reader process has terminated.
Recommended Action: Check the network connectivity between the master and
the media server. Examine the NetBackup error log for any errors that bpsynth
and bptm or the bpdm reader process logged. Examine the debug logs for bpsynth
on the master server and bptm or the bpdm reader process on the media servers
for more detailed information. If the problem persists, contact customer support and
provide the appropriate logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 662
Message: unknown image referenced in the synth context message from BPXM
Explanation: The bpsynth process received an extent message from the bptm or
the bpdm reader with reference to a media ID that was unknown to bpsynth. This
error should not occur.
Recommended Action: Contact customer support and provide the appropriate
logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 663
Message: image does not have a fragment map
Explanation: The bpsynth process received an image without a fragment map
from bpdbm. This error should not occur.
274
NetBackup status codes
NetBackup status codes
Recommended Action: Contact customer support and provide the appropriate
logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 664
Message: zero extents in the synthetic image, cannot proceed
Explanation: The bpsynth process receives zero extents from bpdbm. This error
should not occur.
Recommended Action: Contact customer support and provide the appropriate
logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 665
Message: termination requested by bpcoord
Explanation: This error code is no longer used.
Recommended Action: Contact customer support and send the appropriate logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 667
Message: unable to open pipe between bpsynth and bpcoord
Explanation: This error code is no longer used.
Recommended Action: Contact customer support and send the appropriate logs.
275
NetBackup status codes
NetBackup status codes
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 668
Message: pipe fgets call from bpcoord failed
Explanation: This error code is no longer used.
Recommended Action: Contact customer support and send the appropriate logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 669
Message: bpcoord startup validation failure
Explanation: This error code is no longer used.
Recommended Action: Contact customer support and send the appropriate logs.
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 670
Message: send buffer is full
Explanation: This error code is no longer used.
Recommended Action: Contact customer support and provide the appropriate
logs.
A complete list of required logs and configuration information is available.
276
NetBackup status codes
NetBackup status codes
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 671
Message: query for list of component images failed
Explanation: A new synthetic image cannot be formed because of a problem with
the required component images. For example: a new, synthetic full backup is tried
from the previous full image from Sunday and from the five differential incremental
images from Monday through Friday. This error occurs if any of those images
(except the most recent image on Friday) have expired.
Recommended Action: Run a non-synthetic backup (either a new full or new
cumulative), depending on the type of backup that failed.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 800
Message: resource request failed
Explanation: The nbjm process was unable to get the required resources for a
job. An EMM reason string that appears in the Activity Monitor job details display
and in the nbjm debug log accompanies this status code. The EMM reason string
identifies the reason for the failed resource request.
Recommended Action: Locate the EMM reason string, correct the problem, and
rerun the job.
Some generic EMM reason strings (such as Disk volume is down) may require
generating some reports to determine the cause of the failure. Generate the report
by using either bperror or various log entry reports, such as Reports > Disk
Reports > Disk Logs in the NetBackup Administration Console.
Click here to view technical notes and other information in the Veritas knowledge
base about this status code.
NetBackup status code: 801
Message: JM internal error
Explanation: The nbjm process encountered an internal error.
277
NetBackup status codes
NetBackup status codes
Recommended Action: If the problem persists, submit a report with the following
items.
■
Unified logging files on the NetBackup server for nbpem (originator ID 116), nbjm
(117), nbrb (118), and PBX (103). All unified logging is written to
/usr/openv/logs (UNIX) or install_path\NetBackup\logs (Windows).
■
Legacy logs:
■
On the NetBackup master server for bpbrm, bpjobd, bpcompatd, bpdbm,
and nbproxy
■
On the media server for bpcd, bpbrm, and bptm or bpdm
■
On the client for bpcd and bpbkar
Legacy logs are in subdirectories under /usr/openv/netbackup/logs/ (UNIX)
or install_path\Netbackup\logs\ (Windows). If the directories do not exist,
create directories for each of these processes and rerun the job.
■
Contents of /usr/openv/db/jobs/trylogs (UNIX) or
install_path\NetBackup\db\jobs\trylogs (Windows).
■
bpdbjobs output: run bpdbjobs to obtain the state and status of all jobs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 802
Message: JM internal protocol error
Explanation: nbjm returns this error whenever a protocol error occurs with an
external process that tries to communicate with nbjm. External processes include
bptm, tpreq, bplabel, dqts, vmphyinv, or nbpem.
Recommended Action: Ensure that the NetBackup software on the master and
the media server is from an official NetBackup release.
If the problem persists, submit a report with the following items.
■
Unified logging files on the NetBackup server for nbpem (originator ID 116), nbjm
(117), nbrb (118), and PBX (103). All unified logging is written to
/usr/openv/logs (UNIX) or install_path\NetBackup\logs (Windows).
■
Legacy logs:
■
On the NetBackup master server for bpbrm, bpjobd, bpcompatd, bpdbm,
and nbproxy
■
On the media server for bpcd, bpbrm, and bptm or bpdm
278
NetBackup status codes
NetBackup status codes
■
On the client for bpcd and bpbkar
Legacy logs are in subdirectories under /usr/openv/netbackup/logs/ (UNIX)
or install_path\Netbackup\logs\ (Windows). If the directories do not exist,
create directories for each of these processes and rerun the job.
■
Contents of /usr/openv/db/jobs/trylogs (UNIX) or
install_path\NetBackup\db\jobs\trylogs (Windows).
■
bpdbjobs output: run bpdbjobs to obtain the state and status of all jobs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 803
Message: JM terminating
Explanation: A service request for an existing or a new job was received when
the nbjm process shutdown.
Recommended Action: If nbjm was not terminated explicitly (by entering the
/usr/openv/netbackup/bin/bp.kill_all command on UNIX or
install_path\NetBackup\bin\bpdown on Windows), submit a report with the
following items.
■
Unified logging files on the NetBackup server for nbpem (originator ID 116), nbjm
(117), nbrb (118), and PBX (103). All unified logging is written to
/usr/openv/logs (UNIX) or install_path\NetBackup\logs (Windows).
■
Legacy logs:
■
On the NetBackup master server for bpbrm, bpjobd, bpcompatd, bpdbm,
and nbproxy
■
On the media server for bpcd, bpbrm, and bptm or bpdm
■
On the client for bpcd and bpbkar
Legacy logs are in subdirectories under /usr/openv/netbackup/logs/ (UNIX)
or install_path\Netbackup\logs\ (Windows). If the directories do not exist,
create directories for each of these processes and rerun the job.
■
Contents of /usr/openv/db/jobs/trylogs (UNIX) or
install_path\NetBackup\db\jobs\trylogs (Windows).
■
bpdbjobs output: run bpdbjobs to obtain the state and status of all jobs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
279
NetBackup status codes
NetBackup status codes
NetBackup status code: 805
Message: Invalid jobid
Explanation: The nbjm process received an invalid job ID in the request.
Recommended Action:
The requested operation may refer to a job that no longer exists or is not known to
nbjm. Or the job ID is invalid (less than or equal to 0). Ensure that the command
used to start the job did not specify a job ID already in use by another job.
If the problem persists, submit a report with the following items.
■
Unified logging files on the NetBackup server for nbpem (originator ID 116), nbjm
(117), nbrb (118), and PBX (103). All unified logging is written to
/usr/openv/logs (UNIX) or install_path\NetBackup\logs (Windows).
■
Legacy logs:
■
On the NetBackup master server for bpbrm, bpjobd, bpcompatd, bpdbm, and
nbproxy
■
On the media server for bpcd, bpbrm, and bptm or bpdm
■
On the client for bpcd and bpbkar
Legacy logs are in subdirectories under /usr/openv/netbackup/logs/ (UNIX)
or install_path\Netbackup\logs\ (Windows). If the directories do not exist,
you must create directories for each of these processes and rerun the job.
■
Contents of /usr/openv/db/jobs/trylogs (UNIX) or
install_path\NetBackup\db\jobs\trylogs (Windows).
■
bpdbjobs output: run bpdbjobs to obtain the state and status of all jobs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 806
Message: this mpx group is unjoinable
Explanation: This error is a timing problem. It can happen if the job was added to
a multiplexed group when bpbrm terminates due to an error condition. The Resource
Broker (nbrb) does the allocation of a multiplexed group and the Job Manager
(nbjm) starts and monitors the bpbrm process.
Recommended Action: If the failed job is scheduled and the retry count allows
it, nbpem submits the job again. If the failed job was initiated manually, submit it
again.
280
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 807
Message: not externalized
Explanation: Not available.
Recommended Action: Not available.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 811
Message: failed to communicate with resource requester
Explanation: 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.
Recommended Action: Do the following, as appropriate:
■
Verify the connectivity between the master and the media server.
■
Verify the Private Branch Exchange (PBX) configuration and permissions. More
information on PBX is available.
See "Resolving PBX problems" in the NetBackup Troubleshooting Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 812
Message: failed to communicate with Resource Broker
Explanation: The Job Manager (nbjm) tries to make a request to the Resource
Broker (nbrb). The request fails because of a communication problem.
Recommended Action: Do the following, as appropriate:
■
Verify the connectivity between the master server and the EMM server.
■
Verify the Private Branch Exchange (PBX) configuration and permissions. More
information on PBX is available.
See "Resolving PBX problems" in the NetBackup Troubleshooting Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
281
NetBackup status codes
NetBackup status codes
NetBackup status code: 813
Message: duplicate reference string specified
Explanation: The reference string is the file name specified on the -f option of
the tpreq command. The specified file name on tpreq is already in use by another
tpreq.
Recommended Action: Choose a unique name that is not already in use.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 818
Message: retention level mismatch
Explanation: A job fails with this error code if the retention level of the allocated
media does not match the retention level that is configured in the policy.
Recommended Action: Contact NetBackup Technical Support and provide relevant
supporting materials.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 819
Message: unable to communicate with JM proxy
Explanation: The Job Manager cannot communicate with nbproxy.
Recommended Action: Restart the Job Manager. If the condition persists, please
contact NetBackup Support and provide relevant supporting materials.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 823
Message: no BRMComm to join
Explanation: The job was unable to join the multiplex group. This error is an
internal error.
Recommended Action: Submit a report with the following items.
■
Unified logging files on the NetBackup server for nbpem (originator ID 116), nbjm
(117), nbrb (118), and PBX (103). All unified logging is written to
/usr/openv/logs (UNIX) or install_path\NetBackup\logs (Windows).
282
NetBackup status codes
NetBackup status codes
■
The following legacy logs:
■
On the NetBackup master server for bpbrm, bpjobd, bpcompatd, bpdbm, and
nbproxy
■
On the media server for bpcd, bpbrm, and bptm or bpdm
■
On the client for bpcd and bpbkar
Legacy logs are in subdirectories under /usr/openv/netbackup/logs/ (UNIX)
or install_path\Netbackup\logs\ (Windows). If the directories do not exist,
create directories for each of these processes and rerun the job.
■
Contents of /usr/openv/db/jobs/trylogs (UNIX) or
install_path\NetBackup\db\jobs\trylogs (Windows).
■
bpdbjobs output: run bpdbjobs to obtain the state and status of all jobs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 830
Message: drive(s) unavailable or down
Explanation: All configured drive that can be used for this job are down.
One of the following has occurred:
■
No drives are configured for the media that was requested for the job.
■
The job requires an NDMP drive path, but no NDMP drive paths are up or
configured.
■
The job cannot use an NDMP drive path, but these are the only drive paths that
are up or configured for the drive.
Recommended Action: Do the following:
■
Make sure that the drives and drive paths are up and correct for the media that
you configure.
■
Verify that ltid is running on the required media server, and that the media
server is active for tape.
■
Use the device monitor to startup the drives paths if they are down.
■
If the drives are downed again, clean the drives.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
283
NetBackup status codes
NetBackup status codes
NetBackup status code: 831
Message: image has been validated
Explanation: A job retry attempt fails because the image from the previous attempt
has already been validated. This error can occur if nbjm shuts down before it receives
the job success status. This status code indicates a timing problem only.
Recommended Action: No corrective action is required.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 832
Message: failed to write discover data to a file
Explanation: The Job Manager (nbjm) is unable to write a temporary file in the
netbackup/bin/bpsched.d directory.
Recommended Action: Make sure that the file system is not full.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 833
Message: error parsing discovered XML data
Explanation: The Job Manager was unable to parse the XML document that was
returned from discovery. This error is an internal error.
Recommended Action: Submit a report with the following items:
■
Unified logging files on the NetBackup server for nbpem (originator ID 116), nbjm
(117), nbrb (118), and PBX (103). All unified logging is written to
/usr/openv/logs (UNIX) or install_path\NetBackup\logs (Windows).
■
The following legacy logs:
■
On the NetBackup master server for bpbrm, bpjobd, bpcompatd, bpdbm, and
nbproxy
■
On the media server for bpcd, bpbrm, and bptm or bpdm
■
On the client for bpcd and bpbkar
Legacy logs are in subdirectories under /usr/openv/netbackup/logs/ (UNIX)
or install_path\Netbackup\logs\ (Windows). If the directories do not exist,
create directories for each of these processes and rerun the job.
284
NetBackup status codes
NetBackup status codes
■
Contents of /usr/openv/db/jobs/trylogs (UNIX) or
install_path\NetBackup\db\jobs\trylogs (Windows).
■
bpdbjobs output: run bpdbjobs to obtain the state and status of all jobs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 900
Message: retry nbrb request later
Explanation: The NetBackup Resource Broker (nbrb service) was unable to
respond to a request.
Recommended Action: Do the following, as appropriate:
■
For detailed information, examine the unified logging files on the NetBackup
server for the nbrb service (originator ID 118). All unified logging is written to
/usr/openv/logs (UNIX) or install_path\NetBackup\logs (Windows).
■
If necessary, set global logging to a higher level by using Host Properties >
Master Server > Properties > Logging. Retry the operation and examine the
nbrb logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 901
Message: RB internal error
Explanation: The NetBackup Resource Broker (nbrb service) encountered an
internal error.
Recommended Action: Do the following, as appropriate:
■
For detailed information, examine the unified logging files on the NetBackup
server for the nbrb service (originator ID 118). All unified logging is written to
/usr/openv/logs (UNIX) or install_path\NetBackup\logs (Windows).
■
If necessary, set global logging to a higher level, by using Host Properties >
Master Server > Properties > Logging. Retry the operation and examine the
nbrb logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
285
NetBackup status codes
NetBackup status codes
NetBackup status code: 902
Message: RB invalid argument
Explanation: The NetBackup Resource Broker (nbrb service) detected an invalid
argument.
Recommended Action: Do the following, as appropriate:
■
For detailed information, examine the unified logging files on the NetBackup
server for the nbrb service (originator ID 118). All unified logging is written to
/usr/openv/logs (UNIX) or install_path\NetBackup\logs (Windows).
■
If necessary, set global logging to a higher level, by using Host Properties >
Master Server > Properties > Logging. Retry the operation and examine the
nbrb logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 903
Message: RB communication error
Explanation: The NetBackup Resource Broker (nbrb service) encountered a
communication error.
Recommended Action: Do the following, as appropriate:
■
For detailed information, examine the unified logging files on the NetBackup
server for the nbrb service (originator ID 118). All unified logging is written to
/usr/openv/logs (UNIX) or install_path\NetBackup\logs (Windows).
■
If necessary, set global logging to a higher level, by using Host Properties >
Master Server > Properties > Logging. Retry the operation and examine the
nbrb logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 904
Message: RB max reallocation tries exceeded
Explanation: Under some conditions, failed mounts are retried; the number of
retries for the resource request has been exceeded.
Recommended Action: For detailed information, examine the unified logging files
on the NetBackup server for the nbrb service (originator ID 118) and for nbemm
286
NetBackup status codes
NetBackup status codes
(originator ID 111). All unified logging is written to /usr/openv/logs (UNIX) or
install_path\NetBackup\logs (Windows). Also examine the legacy bptm log.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 905
Message: RB media server mismatch
Explanation: If you have any storage units that are specified for multiple copies,
they must be on the same media server.
Recommended Action: Do the following, as appropriate:
■
Configure the backup schedule with a storage unit or storage unit groups that
can be run on the same media server.
■
For detailed information, examine the unified logging files on the NetBackup
server for the nbrb service (originator ID 118). All unified logging is written to
/usr/openv/logs (UNIX) or install_path\NetBackup\logs (Windows).
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 906
Message: RB operator denied mount request
Explanation: By using the Device Management node in the NetBackup
Administration Console or the vmoprcmd command, the operator denied a mount
request.
Recommended Action: Do the following, as appropriate:
■
Determine the cause of the mount request denial and retry the job.
■
For detailed information, examine the unified logging files on the NetBackup
server for the nbrb service (originator ID 118). All unified logging is written to
/usr/openv/logs (UNIX) or install_path\NetBackup\logs (Windows).
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 907
Message: RB user canceled resource request
Explanation: A user-initiated action caused a Resource Broker (nbrb) request to
be canceled.
287
NetBackup status codes
NetBackup status codes
Recommended Action: Do the following, as appropriate:
■
Determine the action that resulted in cancelation of the resource request.
■
For detailed information, examine the unified logging files on the NetBackup
server for the nbrb service (originator ID 118). All unified logging is written to
/usr/openv/logs (UNIX) or install_path\NetBackup\logs (Windows).
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 908
Message: RB was reset
Explanation: The NetBackup Resource Broker (nbrb) resources and database
were reset. Any nbrb requests that remain may fail when RB is reset. (An example
of a process that resets the database is catalog recovery.)
Recommended Action: Do the following, as appropriate:
■
Determine the action that reset nbrb resources and the nbemm database.
■
For detailed information, examine the unified logging files on the NetBackup
server for the nbrb service (originator ID 118). All unified logging is written to
/usr/openv/logs (UNIX) or install_path\NetBackup\logs (Windows).
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 912
Message: RB disk volume mount failed
Explanation: The attempt to mount a disk volume failed. Possible reasons are
hardware problems, inconsistent EMM database, or a NetBackup Resource Broker
(nbrb) error.
Recommended Action: Do the following, as appropriate:
■
For detailed information, examine the unified logging files on the NetBackup
server for the nbrb service (originator ID 118). Unified logging is written to
/usr/openv/logs (UNIX) or install_path\NetBackup\logs (Windows).
■
If necessary, set global logging to a higher level: Host Properties > Master
Server > Properties > Logging. Retry the operation and examine the nbrb
logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
288
NetBackup status codes
NetBackup status codes
NetBackup status code: 914
Message: RB media reservation not found
Explanation: The read media for a duplicate or synthetic backup job must be
reserved at the start of the job. Status 914 occurs when the NetBackup Resource
Broker (nbrb) receives an allocation request for a read media that was never
reserved. It can result from an internal error in bpduplicate, nbjm, or nbrb.
Recommended Action: Do the following, as appropriate:
■
Examine the unified logging files on the NetBackup server for the nbrb service
(originator ID 118). Unified logging is written to /usr/openv/logs (UNIX) or to
install_path\NetBackup\logs (Windows).
■
If necessary, set global logging to a higher level: Host Properties > Master
Server > Properties > Logging. Retry the operation and examine the nbrb
logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 915
Message: RB disk volume mount must retry
Explanation: A shared disk job has failed because RB is unable to mount the disk
volume. Shared disk requires that volume file systems be unmounted and remounted
before other media servers can use them.
Recommended Action: Do the following, as appropriate:
■
Verify that processes are not in the disk volume mount directories, which prevents
them from being unmounted. If the problem persists, restart NetBackup on the
media server.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 916
Message: Resource request timed out
Explanation: A job request for resources has failed because resources were not
available before the configured time limit expired. Some jobs may specify a timeout
when they ask for drives or other resources. If jobs consistently cause this error,
more jobs may be scheduled than the number of available drives. The drives in the
Resource Broker job queue are not completed soon enough to allow new jobs to
start before they timeout.
289
NetBackup status codes
NetBackup status codes
Recommended Action: Distribute the scheduled job start times over a wider
period of time.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 917
Message: RB multiplexing group not found
Explanation: The NetBackup Resource Broker (nbrb) has received a request for
an unknown multiplex group ID. This error can be caused by a timing problem when
RB is killed and restarted. It can also be caused by an internal error in nbjm or nbrb.
Recommended Action: Restart nbjm and nbrb. If the problem persists, write a
problem report with the appropriate logs including the nbjm and nbrb logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 918
Message: RB does not have a multiplexing group that uses this media ID or drive
name
Explanation: The NetBackup Resource Broker (nbrb) has received a request for
an unallocated media or drive.
Recommended Action: The nbrbutil command may cause this error. Rerun the
command with an allocated media ID or drive. Also, this error may be internal. If
the problem persists, write a problem report with the appropriate logs including
nbjm and nbrb.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1000
Message: Client is offline
Explanation: An attempt was made to run a manual job for a client that is offline.
Recommended Action: Wait until the client is brought online or manually bring
the client online by using the GUI or the bpclient command before you submit the
manual job.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
290
NetBackup status codes
NetBackup status codes
NetBackup status code: 1001
Message: discovery document error
Explanation: The Policy Execution Manager (pem) is unable to parse the XML
document that was returned from the discovery operation. This error is an internal
error.
Recommended Action: Submit a report with the following items.
■
Unified logging files on the NetBackup server for nbpem (originator ID 116), nbjm
(117), nbrb (118), and PBX (103). All unified logging is written to
/usr/openv/logs (UNIX and Linux) or install_path\NetBackup\logs
(Windows).
■
The following legacy logs:
■
On the NetBackup master server for bpbrm, bpjobd, bpcompatd, bpdbm, and
nbproxy
■
On the media server for bpcd, bpbrm, and bptm or bpdm
■
On the client for bpcd and bpbkar
Legacy logs are in subdirectories under /usr/openv/netbackup/logs/ (UNIX
and Linux) or install_path\Netbackup\logs\ (Windows). If the directories
do not exist, create directories for each of these processes and rerun the job.
■
Contents of /usr/openv/db/jobs/trylogs (UNIX and Linux) or
install_path\NetBackup\db\jobs\trylogs (Windows).
■
bpdbjobs output: run bpdbjobs to obtain the state and status of all jobs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1002
Message: Discovery detected a failed client
Explanation: The query rules cannot exclude one or more clients, and these clients
cannot be selected for backup. A host name problem may be the cause of this error.
Recommended Action: See the job details log for more specific information.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1057
Message: A data corruption has been detected.
291
NetBackup status codes
NetBackup status codes
Explanation: The data consistency check detected a data loss or data corruption
in the Media Server Deduplication Pool (MSDP) and reported the affected backups.
Recommended Action: Search storaged.log on the server for the affected
backups and contact technical support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1058
Message: A data inconsistency has been detected and corrected automatically.
Explanation: The data consistency check detected a potential data loss and fixed
it automatically in the Media Server Deduplication Pool (MSDP).
Recommended Action: Search the storaged.log file on the pertinent media
server. Contact support to investigate the root cause if the problem persists.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1401
Message: Invalid arguments received
Explanation: Invalid input arguments pass to the Hold Service.
Recommended Action: Ensure that all the required parameters are passed with
the correct values.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1402
Message: Hold ID or Hold name argument is invalid
Explanation: The nbholdutil command contains an invalid -holdid or -holdname
option that passes to the root Hold Service.
Recommended Action: Check the -holdid and -holdname options for valid
values.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
292
NetBackup status codes
NetBackup status codes
NetBackup status code: 1403
Message: Backup ID argument is invalid
Explanation: The nbholdutil command contains an invalid -backupid option
that passes to the root Hold Service.
Recommended Action: Check the -backupid option for a valid value.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1405
Message: No images are found.
Explanation: The nbholdutil command contains a -backupid for an image that
cannot be found.
Recommended Action: Check that the -backupid option is for a valid image.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1407
Message: Invalid hold state
Explanation: This code is reserved for future use.
Recommended Action: Not available.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1408
Message: Database error
Explanation: The hold service fails to get hold related information.
Recommended Action: Make sure that the Hold database and the DBM services
are running.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1409
Message: Unable to connect to database
293
NetBackup status codes
NetBackup status codes
Explanation: The hold service fails to connect to the Hold database.
Recommended Action: Make sure that the Hold database and the DBM services
are running.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1410
Message: No data found
Explanation: No images or hold copies are found for the given values.
Recommended Action: Make sure that all the required parameters are passed
with their correct values.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1411
Message: Catalog error
Explanation: You try to update the image catalog.
Recommended Action: Check that the image copy on which the hold operation
is applied is valid and not expired.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1412
Message: Hold record is being updated
Explanation: A hold operation is in the process of being updated.
Recommended Action: Retry the operation at a later time or restart the nbim
service.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1413
Message: Requested hold is not found
Explanation: The nbholdutil command requests a hold that does not exist.
294
NetBackup status codes
NetBackup status codes
Recommended Action: Check the -holdname and -holdid options. You can use
nbholdutil -list command.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1414
Message: Duplicate hold found
Explanation: You try to create a hold whose name is used by another hold.
Recommended Action: Try a different name.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1415
Message: Duplicate image found
Explanation: Reserved for future use.
Recommended Action: Not available.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1416
Message: Partially failed due to duplicate image
Explanation: Reserved for future use.
Recommended Action: Not available.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1417
Message: Partially failed due to unhold image
Explanation: Backup image copy is already removed from the specified hold.
Recommended Action: Make sure that you provide the correct backup ID and
that it is present in the current hold.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
295
NetBackup status codes
NetBackup status codes
NetBackup status code: 1418
Message: Requested image is not found
Explanation: The backup image with the specified backup ID is not found. Either
the image is expired or the given backup ID is invalid.
Recommended Action: Not available.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1419
Message: Partially failed due to invalid image copy
Explanation: Reserved for future use.
Recommended Action: Not available.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1420
Message: Cannot expire on hold image copy.
Explanation: You try to expire an image copy (by using bpexpdate or the
NetBackup Administration Console) that is on hold.
Recommended Action: Remove all holds from this backup image. Or remove
holds from all images on this backup ID to expire the backup image.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1421
Message: Active holds cannot be changed
Explanation: You try to update a hold that is in an active state.
Recommended Action: Restart the NBIM service
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1422
Message: Cannot deassign media on hold
296
NetBackup status codes
NetBackup status codes
Explanation: The user tries to de-assign a media having an image copy that is on
hold.
Recommended Action: Lift the holds on the image copies that are backed up on
the media being de-assigned.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1423
Message: Unable to retrieve hold status of the image copies
Explanation: Reserved for future use.
Recommended Action: Not available.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1425
Message: Requested hold is not found
Explanation: The hold service cannot find holds with the specified hold name or
hold ID.
Recommended Action: Use the nbholdutil -list to list all holds. Check that
the specified -holdname and -holdid options are valid.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1426
Message: Retired holds cannot be changed
Explanation: Reserved for future use.
Recommended Action: Not available.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1500
Message: Storage unit does not exist or cannot be used where specified
Explanation: The storage unit or storage unit group that you specify for one or
more destinations in storage lifecycle policy is not valid.
297
NetBackup status codes
NetBackup status codes
Recommended Action: Do the following, as appropriate:
■
Verify that the specified storage unit or storage unit group exists in the NetBackup
database.
■
Verify that the specified storage unit is not of type BasicDisk or Staging,
because storage lifecycle policies do not support them.
■
Verify that the storage unit is not specified for snapshot destinations in storage
lifecycle policy. Snapshot destinations do not require a storage unit in the storage
lifecycle policy.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1501
Message: Source operation cannot be used where specified
Explanation: The source that you specify for one or more duplication destinations
in storage lifecycle policy is not valid.
Recommended Action: Do the following, as appropriate:
■
Verify that the specified source refers to a valid destination in the list of
destinations in storage lifecycle policy.
■
Verify that the Backup or Snapshot destination type does not have any source
specified. If you use nbstl to configure storage lifecycle policy, use value zero
(0) as the source for a backup or snapshot destination type.
■
Verify that the destination that refers to the specified source is not a Snapshot
destination type. NetBackup cannot duplicate a backup image that uses snapshot
copy as a source.
■
Verify that the specified source does not refer to the destination itself for which
the source is mentioned.
■
Verify that the specified list of destinations in a storage lifecycle has a circular
dependency for the source.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1502
Message: Retention type cannot be used where specified
Explanation: The retention type that you specify for one or more destinations in
storage lifecycle policy is not valid.
298
NetBackup status codes
NetBackup status codes
Recommended Action: Do the following, as appropriate:
■
Verify that the retention type that you specify in the storage lifecycle policy is
either of Fixed, Staged capacity managed, or Expire after duplication.
■
Verify that the Expire after duplication retention type is used for a destination
only if it is specified as a source to other destinations in storage lifecycle policy.
■
Verify that the Staged capacity managed retention type is used in storage
lifecycle policy only for the disk destinations that support Capacity management
capabilities.
■
Verify that the Snapshot destination type in storage lifecycle policy uses Fixed
retention type only.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1503
Message: Volume pool does not exist or cannot be used where specified
Explanation: The volume pool that you specify for one or more destinations in the
storage lifecycle policy is not valid.
Recommended Action: Do the following, as appropriate:
■
Verify that the specified volume pool exists in NetBackup database.
■
Verify that the volume pool is not specified for the Backup destination type in
storage lifecycle policy.
■
Verify that the volume pool is not specified for the Snapshot destination type
in storage lifecycle policy.
■
Verify that the volume pool is not specified for the Duplication destination type
that uses disk storage units in storage lifecycle policy.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1504
Message: Server group does not exist or cannot be used where specified
Explanation: The media server group that you specify for one or more destinations
in storage lifecycle policy is not valid.
Recommended Action: Do the following, as appropriate:
■
Verify that the specified media server group exists in NetBackup database.
299
NetBackup status codes
NetBackup status codes
■
Verify that the media server group is not specified for Backup destination types
in storage lifecycle policy.
■
Verify that the server group is not specified for Snapshot destination types in
storage lifecycle policy.
■
Verify that the media server group is not specified for Duplication destination
types that use disk storage unit in storage lifecycle policy.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1505
Message: alternate read server does not exist or cannot be used where specified
Explanation: The alternate read server that you specify for one or more destinations
in storage lifecycle policy is not valid.
Recommended Action: Do the following, as appropriate:
■
Verify that the specified alternate read server exists in the NetBackup database.
■
Verify that the alternate read server is not specified for Backup destination types
in storage lifecycle policy.
■
Verify that the alternate read server is not specified for Snapshot destination
types in storage lifecycle policy.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1506
Message: data classification does not exist
Explanation: The data classification that you specify in the storage lifecycle policy
is not valid.
Recommended Action: Verify that the specified data classification exists in the
NetBackup database.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1507
Message: Invalid deferred operation flag
Explanation: The deferred operation flag is not valid for the SLP operation.
300
NetBackup status codes
NetBackup status codes
Recommended Action: Do the following:
■
If you used the nbstl -defop command, make sure that the specified argument
is one of the following: f, F, t, or T.
For more information on the nbstl command, see the NetBackup Commands
Reference Guide.
■
Make sure that the flag is not set for the primary SLP operations: Backup,
snapshot, and import.
■
Make sure that the source copy has fixed retention.
■
Refer to the detailed log messages for more details.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1508
Message: Storage lifecycle policy exceeds maximum copies
Explanation: The list of destinations that you specify in the storage lifecycle policy
exceeds 10, the maximum number of allowed backup copies.
Recommended Action: Verify that the number of destinations that you specify in
the storage lifecycle policy does not exceed 10.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1509
Message: Storage lifecycle policy exceeds maximum backup operations
Explanation: The number of Backup type destinations that you specify in storage
lifecycle policy exceeds the maximum number of simultaneous copies allowed.
Recommended Action: Verify that the number of Backup type destinations that
you specify in the storage lifecycle policy is less than or equal to 4. (The default
value of the maximum number of allowed simultaneous copies parameter is
4.)
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1510
Message: storage lifecycle policy cannot have more than one snapshot operation
301
NetBackup status codes
NetBackup status codes
Explanation: The list of destinations that you specify in the storage lifecycle policy
exceeds the maximum number of allowed snapshot destinations.
Recommended Action: Verify that the storage lifecycle policy is not configured
with more than one “Snapshot” type of destinations.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1511
Message: storage lifecycle policy must have at least one fixed retention or snapshot
rotation operation
Explanation: The specified storage lifecycle policy does not have any destination
with a retention type of Fixed.
Recommended Action: Verify that the specified storage lifecycle policy has at
least one destination that is configured with a Fixed retention type.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1512
Message: storage lifecycle policy must have at least one backup, import, or
snapshot operation
Explanation: The specified storage lifecycle policy does not have any backup
destination.
Recommended Action: Verify that the storage lifecycle policy has at least one
Backup type of destination.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1513
Message: invalid priority
Explanation: The duplication priority that you specify in the storage lifecycle policy
is not valid.
Recommended Action: Verify that the duplication priority that you specify in the
storage lifecycle policy is in the range of 0 to 99999.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
302
NetBackup status codes
NetBackup status codes
NetBackup status code: 1514
Message: invalid operation type
Explanation: The destination type that you specify on one or more destinations
in the storage lifecycle policy is not valid.
Recommended Action: Do the following, as appropriate:
■
Verify that the destination type that you specify on each destination in storage
lifecycle policy is either Backup, Duplication, or Snapshot.
■
If you are use the nbstl command to configure storage lifecycle policy, the
following are the valid values for the destination type: 0 indicates Backup, 1
indicates Duplication, and 2 indicates Snapshot.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1515
Message: Multiplexing value is not valid or cannot be used where specified
Explanation: The preserve multiplexing flag that you specify on one or more
destinations is not valid.
Recommended Action: Do the following, as appropriate:
■
If you use the nbstl command to configure storage lifecycle policy, then verify
that the valid values are used to indicate the preserve multiplexing flag for each
destination. The value “T” or “t” indicates true (Preserve multiplexing). The value
“F” or “f” indicates false (do not preserve multiplexing).
■
Verify that destinations of type Backup are not configured to preserve
multiplexing.
■
Verify that destinations of type Snapshot are not configured to preserve
multiplexing.
■
Verify that destinations of type Duplication that are using disk storage units are
not configured to preserve multiplexing.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1516
Message: all storage units or groups must be on the same media server
Explanation: The destinations of type Backup specified in storage lifecycle policy
are not accessible by the same media server.
303
NetBackup status codes
NetBackup status codes
Recommended Action: Verify that all the destinations of type Backup are
accessible by at least one common media server.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1517
Message: Invalid retention level
Explanation: The retention level that you specify for one or more destinations in
storage lifecycle policy is not valid.
Recommended Action: Verify that the retention level that you specify on each
destination in storage lifecycle policy is in the range of 0 to 100.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1518
Message: backup image is not supported by storage lifecycle policy
Explanation: The backup image is unsupported by the configured storage lifecycle
policy.
Recommended Action: Do the following, as appropriate:
■
Verify that if a NetBackup policy is configured to perform snapshot backups and
uses storage lifecycle policy as its storage destination, then the specified storage
lifecycle policy must be configured with a snapshot destination. Otherwise,
backup images that are created by those NetBackup policies are not processed
further by storage lifecycle policy for any lifecycle operations.
■
Verify that NetBackup policies that use the storage lifecycle policy as a storage
destination are not configured to perform “snapshots-only” operations. They
must create backups in addition to snapshots. The Storage lifecycle policy even
though configured with a snapshot destination, performs lifecycle operations on
such images only if they have at least one backup copy.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1519
Message: Images are in process
Explanation: The operation in progress cannot complete because the SLP
processing of the images is not complete.
304
NetBackup status codes
NetBackup status codes
Recommended Action: Wait until the image processing is done, then retry the
operation. Or, terminate the SLP processing for the needed images.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1521
Message: Database not available
Explanation: The import manager is not able to access the NetBackup database.
Recommended Action: Do one of the following:
■
Make sure that the database service is running.
■
Make sure that the disk is not full.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1522
Message: Error executing database query
Explanation: An SQL error is in the import manager.
Recommended Action: Examine the log files for the nbstserv process or originator
ID 369 for more information.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1523
Message: Invalid fragment
Explanation: NetBackup received from a storage device a replication notification
event in an unrecognized format.
Recommended Action: Check the NetBackup Problems Report for details.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1524
Message: Duplicate image record
305
NetBackup status codes
NetBackup status codes
Explanation: NetBackup received from a storage device a replication notification
event for a backup ID that already exists in the NetBackup catalog.
Recommended Action: Do one of the following:
■
Check the NetBackup Problems Report for details.
■
Delete the duplicate image from storage because NetBackup cannot do it.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1525
Message: Invalid lsu
Explanation: NetBackup received a replication notification event that indicates an
image exists on an unknown or unconfigured disk volume (LSU).
Recommended Action: Do one of the following:
■
Configure the LSU as a valid disk volume in a valid disk pool, and create a valid
storage unit for it. Associate this storage unit with an import storage lifecycle
policy.
■
Reconfigure the replication on your storage devices to use a replication target
disk volume (LSU) that NetBackup recognizes.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1526
Message: Storage lifecycle policy exceeds maximum import operations
Explanation: The storage lifecycle policy definition cannot be created or modified
as specified because it can contain only one import destination.
Recommended Action: Configure the storage lifecycle policy with only one import
destination.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1527
Message: storage lifecycle policy can have only one of backup, import, and
snapshot operations
306
NetBackup status codes
NetBackup status codes
Explanation: The storage lifecycle policy definition cannot be created or modified
as specified because a storage lifecycle policy with an import destination cannot
also have backup or snapshot destinations.
Recommended Action: Configure the storage lifecycle policy with only one import
destination and additional destinations of type duplication only.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1528
Message: The source copy for an Auto Image Replication is not capable of
replication
Explanation: The storage lifecycle policy (SLP) definition cannot be created or
modified as specified because you have selected an Auto Image Replication
destination that duplicates a copy not capable of duplication across master servers.
Recommended Action: Do one of the following:
■
If you use the command line, ensure that you specify the correct SLP destination
index number for the source copy.
■
Use the appropriate indentation to indicate the correct source storage lifecycle
policy destination in the GUI.
■
Ensure that the source uses a storage unit that is capable of replication. The
storage unit is specified by the SLP destination index on the CLI or by indentation
in the GUI. That is, check the properties of the disk volumes within the disk pool
that the storage unit specifies.
■
After you set a replication target, you must refresh the disk pool. In the
NetBackup Administration Console, in the left pane, expand Media and
Device Management Devices > Disk Pools. In the right pane, select the disk
pool that you want to update. In the Change Disk Pool dialog box, click Refresh
to configure the replication settings for the disk pool.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1529
Message: The source copy for Auto Image Replication must specify a storage unit
Explanation: One of the following may have occurred:
307
NetBackup status codes
NetBackup status codes
■
The storage lifecycle policy definition cannot be created or modified as specified
because an Auto Image Replication destination is specified which duplicates a
copy that may not be capable of duplication across master servers.
■
You are trying a replication by using a storage unit group. Auto Image Replication
does not support replicating from or replicating to a storage unit group. That is,
the source copy cannot be in a storage unit group, and the target cannot be a
storage unit group.
Recommended Action: Do one or more of the following:
■
If you use the command line, ensure that you specify the correct storage lifecycle
policy destination index number for the source copy.
■
Ensure that you use the appropriate indentation to indicate the correct source
storage lifecycle policy destination in the GUI.
■
Ensure that the source that is specified by either the storage lifecycle policy
destination index on the CLI or by indentation in the GUI uses a storage unit
(not a storage unit group, storage lifecycle policy or Any Available) that is capable
of replication. That is, check the properties of the disk volumes within the disk
pool that the storage unit specifies.
■
Ensure that you are not using a storage unit group for replication. For the source
copy, select a storage unit that is not in a storage unit group. For the target, do
not select a storage unit group.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1530
Message: Only one Auto Image Replication allowed per copy
Explanation: The storage lifecycle policy definition cannot be created or modified
as specified because an Auto Image Replication destination is specified which
duplicates a copy which already has an Auto Image Replication specifying it as a
source copy.
Recommended Action: Do one of the following:
■
If you use the command line, ensure that you specify the correct storage lifecycle
policy destination index number for the source copy.
■
Ensure that you use the appropriate indentation to indicate the correct source
storage lifecycle policy destination in the GUI.
■
Ensure that the source that is specified by either the storage lifecycle policy
destination index on the CLI or by indentation in the GUI does not have more
than one Auto Image Replication destination specifying it as its source copy.
308
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1531
Message: An import storage lifecycle policy requires one copy with remote retention
type
Explanation: The storage lifecycle policy definition cannot be created or modified
as specified because an imported image must make at least one copy by using the
(imported) remote retention type.
Recommended Action: Add a destination to the storage lifecycle policy that uses
the remote retention type.
Do one of the following:
■
Change one of the destinations in the storage lifecycle policy to use the remote
retention type. If the storage lifecycle policy has only one destination that is an
import destination, then it must be a remote retention type.
■
Add a destination to the storage lifecycle policy which uses the remote retention
type.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1532
Message: Import failed because the imported image specifies an SLP name which
does not exist
Explanation: The image imported does not match any configured storage lifecycle
policy and was immediately expired.
Recommended Action: Do one of the following:
■
Verify that the storage lifecycle policy in the source domain where you configured
an Auto Image Replication matches the storage lifecycle policy in the destination
domain where you configured the import. The match is case-sensitive.
■
Add a storage lifecycle policy with an import destination using the same name
as your storage lifecycle policy in the source domain.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
309
NetBackup status codes
NetBackup status codes
NetBackup status code: 1533
Message: Import failed because the imported image data class is different than
the SLP data class
Explanation: The image that is imported has a data classification which does not
match any of the import storage lifecycle policy data classifications and was
immediately expired.
Recommended Action: Do one of the following:
■
Change the data classification of the storage lifecycle policy in the source domain
where you configured an Auto Image Replication to match the following: the
data classification in the destination domain where you have configured the
import. The match is case-sensitive.
Verify that the storage lifecycle policy in the source domain where you configured
an Auto Image Replication matches the following: the storage lifecycle policy in
the destination domain where you configured the import. The match is
case-sensitive.
■
Change the data classification of the storage lifecycle policy in the destination
domain where you configured an Auto Image Replication to match the following:
the data classification in the source domain where you have configured the
import. The match is case-sensitive.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1534
Message: Import failed because the imported image specifies an SLP name with
no import operation
Explanation: The imported image specifies a storage lifecycle policy name that
is not an import storage lifecycle policy and is immediately expired.
Recommended Action: Use a different storage lifecycle policy name in the source
domain where you configured an Auto Image Replication. This name must match
a storage lifecycle policy name with an import destination in the destination domain
where you have configured the import. The match is case-sensitive.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1535
Message: Import failed because the imported image backup ID conflicts with an
existing image
310
NetBackup status codes
NetBackup status codes
Explanation: NetBackup attempted to import an image with a backup ID that
already exists in the image catalog.
Recommended Action: Delete the duplicate image from storage because
NetBackup cannot delete it. Use the following command:
# bpimage -deletecopy # -backupid backupid
where # is the copy number of the image that you want to delete.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1536
Message: The storage unit or storage unit group cannot be deleted because an
SLP references it
Explanation: You cannot delete a storage unit or storage unit group if a storage
lifecycle policy (SLP) references it. The SLP may be an older version. The
NetBackup Administration Console displays the most recent version of an SLP
while the reference to the storage unit or storage unit group may be located in an
earlier version.
Recommended Action: Use the nbstl command to view and change the older
SLP versions. Do the following in the order listed:
■
Run the following command to display all versions of each SLP:
# nbstl -L -all_versions
■
Determine the name and version of each SLP that references the storage unit
or storage unit group.
■
Run the following command to replace the storage unit (group) to be deleted
with the name of a different storage unit.
# nbstl <SLP_name> -modify_version <version_number>...
For more information on storage lifecycle policy versions, see the NetBackup
Administrator’s Guide, Volume I.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1537
Message: Backup policy and storage lifecycle policy have conflicting configurations
311
NetBackup status codes
NetBackup status codes
Explanation: Some of the backup policy characteristics are not compatible with
one of the SLP characteristics that is referenced in the policy attributes or policy
schedules.
Recommended Action: In the NetBackup Administration Console, locate the
Change Storage Lifecycle Policy dialog for the SLP in question. Then run the
Validation Report to display the specific conflicts that pertain to the SLP. Correct
those conflicts.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1538
Message: Data classification in the SLP conflicts with backup policy
Explanation: The Data classification that you specify in the SLP does not match
the data classification that is specified in the backup policy.
Recommended Action: Do one of the following:
■
Change the policy to reference an SLP with a matching data classification
■
Change the data classification in either the backup policy or the SLP so that
they match.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1539
Message: Backup policy generates snapshots but storage lifecycle policy does
not handle them
Explanation: The backup policy generates snapshots because you have selected
the Perform snapshot backups and the Retain snapshot for Instant Recovery
or SLP management on the Change Policy dialog box. The referenced SLP cannot
process snapshots because it does not include a Snapshot operation.
Recommended Action: Do one of the following:
■
Change the backup policy to use an SLP that provides snapshot support.
■
Change the backup policy so it does not generate snapshots.
■
Change the SLP to include a snapshot operation.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
312
NetBackup status codes
NetBackup status codes
NetBackup status code: 1540
Message: SLP expects snapshots but backup policy does not create them with
SLP management enabled
Explanation: The maximum snapshot limit for this policy is reached and no existing
snapshot is eligible for rotation.
Recommended Action: Find and expire the existing snapshot which is no longer
needed.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1541
Message: Snapshot creation failed. The maximum snapshot limit for the policy
has been exceeded and no existing snapshots are eligible for expiration.
Explanation: One of the following is true:
■
None of the existing snapshot copies is eligible for expiration because all the
copies are in snapshot duplication pending mode.
■
None of the existing snapshot copies is eligible for expiration, because they
have not yet reached their retention period (fixed retention).
Recommended Action: Do not try to expire a snapshot copy that is still pending
or has not reached its retention period. Check the maximum snapshot limit setting
in your Backup Policy>Attributes>Snapshot Options.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1542
Message: An existing snapshot is no longer valid and cannot be mounted for
subsequent operations
Explanation: An existing snapshot has become corrupted or the snapshot no
longer contains all the required data. It cannot be mounted and cannot be used for
any further NetBackup operations, including backup from snapshot or restore. Any
pending SLP operations have been automatically canceled
Recommended Action: Run a new backup job to generate a new snapshot.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
313
NetBackup status codes
NetBackup status codes
NetBackup status code: 1543
Message: Policy type is not compatible with SLP operations
Explanation: Policies of the type that you specify cannot be used with the
referenced SLP because they do not support the SLP operations, including SLP
characteristics such as snapshot operations.
Recommended Action: Choose a different SLP that is compatible with the policy
type.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1545
Message: Schedule type is not compatible with SLP operations
Explanation: A policy schedule refers to an SLP as its storage destination, but
the schedule type is not compatible with the operations performed by the SLP.
Recommended Action: Choose a different SLP that is compatible with the
schedule type.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1546
Message: Capacity managed retention type is not compatible with SLP operations
Explanation: Capacity managed retention has been chosen as the retention type
for an SLP operation. That retention type does not support the SLP operations.
Recommended Action: Choose a different SLP that is compatible with the
schedule type.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1547
Message: Expire after copy retention requires a dependent copy
Explanation: When the retention type for an SLP operation is expire after copy,
a dependent copy for that operation must use the expire after copy operation as
its source.
Recommended Action: No operations can be performed on this snapshot. Expire
it from the catalog.
314
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1548
Message: Retention type is not compatible with snapshot operation
Explanation: The retention type that you selected for the snapshot operation in
an SLP is not supported for snapshots.
Possible scenario: You configure the backup policy for Replication Director, and in
the Attributes tab you select Any Available for the Policy storage. In the schedule
for the backup policy, you select Override policy storage selection and select an
SLP from the drop-down menu. The SLP contains a storage unit that uses a Fixed
retention type. The backup policy validation fails and asks you to set the Maximum
Snapshot Limit to Managed by SLP Retention.
Recommended Action: Do one of the following:
■
Choose a different retention type.
■
If the backup policy is configured for Replication Director, open the backup
policy. In the Attributes tab, click Options to display the Replication Director
options. If the values for the Maximum Snapshots do not include Managed
by SLP Retention, select 0 (zero) instead. A value of 0 indicates the Managed
by SLP Retention selection.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1549
Message: TIR information selection is not compatible with SLP operations
Explanation: The backup policy has TIR information collection that is enabled and
uses an SLP as its storage destination. One or more of the operations in the SLP
do not support TIR information collection.
Recommended Action: Do one of the following:
■
Remove the TIR information selection from the backup policy.
■
Choose a different SLP to use with the backup policy.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
315
NetBackup status codes
NetBackup status codes
NetBackup status code: 1552
Message: The source and target storage units are not valid replication partners.
Explanation: The nbstl command has configured the lifecycle policy. One of the
following is true:
■
The target storage unit or group that is specified for the replication operation is
not a replication partner for the source storage unit or group.
■
Volumes that are configured in the target storage unit or group are not replication
targets for the volumes that are configured in the source storage unit or group.
■
You use the fully qualified name for the storage server. The storage server
creation process requires the short version of the name as displayed in the
bpstsinfo -li output.
Recommended Action: Do one of the following:
■
Run the following command to get a list of matching target storage units or
groups for the given source storage unit or group:
# nbdevquery -listreptargets -stunit source_stu_or_group
■
Rerun the nbstl command with the target storage unit or group from the list
that the nbdevquery command displays.
■
Run the bpstsinfo -li command and check the output for the storage server
name. The name that you use to create the storage server must match this
name.
■
Ensure that NetBackup is configured after the storage server configuration is
complete. If not, use the Change Disk Pool dialog of the NetBackup
Administration Console or the nbdevconfig -updatedp command to refresh
each disk pool of the storage server.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1553
Message: Checkpoints are not allowed with SLP operations
Explanation: The backup policy has checkpoint restart capability enabled and
uses an SLP as its storage destination. The SLP contains one or more operations
that do not support checkpoint restart.
Recommended Action: Do one of the following:
■
Remove the checkpoint restart selection from the backup policy.
316
NetBackup status codes
NetBackup status codes
■
Choose a different SLP to use with the backup policy.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1554
Message: Storage unit snapshot capability is not compatible with operation
characteristics
Explanation: The snapshot capability of a storage unit does not support the SLP
operation that uses it.
Recommended Action: Choose a storage unit that supports the correct capabilities.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1556
Message: The SLP deletion failed because a backup policy refers to it.
Explanation: An attempt to delete an SLP has failed because the SLP is still
referenced in one or more backup policies.
Recommended Action: Change the backup policies to use other SLPs or storage
units. Then try again to delete the SLP.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1557
Message: Must specify mirror retention when target storage unit is mirror capable.
Explanation: You have specified a target storage unit that is mirror-capable for a
replication operation in a storage lifecycle policy, but the retention is not mirror type.
Recommended Action: If you used a nbstl command to configure the storage
lifecycle policy, rerun the command after the following: Specify the mirror retention
type for the replication operation corresponding to the storage unit that is
mirror-capable. Use the bpstulist -U command to view the storage unit properties.
If the error occurs when you configure the storage lifecycle policy by using the GUI,
submit a problem report and provide the appropriate logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
317
NetBackup status codes
NetBackup status codes
NetBackup status code: 1558
Message: Mirror retention is not allowed when target storage unit is not mirror
capable.
Explanation: When you configured the replication operation in a storage lifecycle
policy, you specified a mirror retention for a target storage unit that is not
mirror-capable.
Recommended Action: If you used a nbstl command to configure the storage
lifecycle policy, rerun the command after you do the following: Specify the
appropriate retention type (other than mirror retention) for the replication operation
corresponding to the storage unit that is non-mirror capable. Use the bpstulist
-U command to view the storage unit properties. If the error occurs when you
configure the storage lifecycle policy by using the GUI, submit a problem report and
provide the appropriate logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1559
Message: SLP referenced in policy or schedule not found
Explanation: The SLP named in the attributes of a backup policy or in one of the
policy schedules cannot be found.
Recommended Action: Check the spelling of the SLP used in the policy. The
SLP displayed in the NetBackup Administration Console or the nbstl command
can be used to list the SLPs that have been defined. Select one of the defined SLPs
to use in the backup policy or create one with the desired name.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1560
Message: Fixed or rotation retention required without a replication operation
Explanation: An SLP that contains an Auto Image Replication operation must
contain at least one operation with a Fixed Snapshots or Maximum Snapshots
retention type.
Recommended Action: Add an operation with the required retention or change
the retention of an existing operation.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
318
NetBackup status codes
NetBackup status codes
NetBackup status code: 1561
Message: Policy using NDMP conflicts with multiple Backup From Snapshot
operations in storage lifecycle policy
Explanation: If the backup policy uses NDMP through either the policy type or the
data mover type, it cannot use an SLP that contains multiple Backup From
Snapshot operations.
Recommended Action: Do one of the following:
■
Change the policy type or data mover type so that it is not NDMP.
■
Use a different SLP that does not contain multiple Backup From Snapshot
operations.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1562
Message: Backup schedule generates snapshots but storage lifecycle policy does
not handle them
Explanation: A backup policy schedule generates snapshots but the SLP that is
referenced by that schedule does not contain a Snapshot operation. Thus, the SLP
cannot process snapshots.
Recommended Action: Select an SLP that begins with a Snapshot operation so
that it can process the snapshot generated by the backup policy and schedule.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1563
Message: SLP expects snapshots but backup schedule does not create them
Explanation: A backup policy schedule refers to an SLP that starts with a Snapshot
operation and expects to process snapshots. The backup policy and the relevant
schedule do not generate snapshots.
Recommended Action: Select an SLP that does not begin with a Snapshot
operation.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
319
NetBackup status codes
NetBackup status codes
NetBackup status code: 1564
Message: Storage lifecycle policy contains errors
Explanation: NetBackup calls the SLP validation functions in bpdbm. Other error
status values are returned.
Recommended Action: Check the other errors that are displayed.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1565
Message: Policy snapshot method is not compatible with SLP snapshot operations
Explanation: The snapshot method chosen in the backup policy does not provide
support for the snapshot operations defined in the referenced SLP.
Recommended Action: Use a different SLP that does not contain unsupported
operations.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1566
Message: Storage unit required for snapshot operation when no other operation
present
Explanation: NetBackup can determine which storage unit to use for a Snapshot
operation if there are other operations in the SLP. If the Snapshot operation is the
only operation in the SLP, a storage unit must be provided.
Recommended Action: Add a storage unit to the Snapshot operation.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1567
Message: Only one NDMP backup of a snapshot per backup ID is allowed
Explanation: A backup policy of type NDMP refers to an SLP that contains more
than one Backup From Snapshot operation.
Recommended Action: Do one of the following:
■
Modify the SLP so that it contains only one Backup From Snapshot operation.
■
Modify the backup policy so that it uses a different SLP.
320
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1568
Message: Only one Index From Snapshot operation is allowed per storage
lifecycle policy
Explanation: You have defined an SLP that contains more than one Index From
Snapshot operation. Only one Index From Snapshot operation is allowed in an
SLP.
Recommended Action: Change the backup policies to use other SLPs or storage
units. Then try again to delete the SLP.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1569
Message: Snapshot storage unit is not configured for primary snapshots. It cannot
be used in snapshot operation.
Explanation: A snapshot-capable storage unit must be configured to handle primary
snapshots if you want to use a Snapshot operation in an SLP.
Recommended Action: Do one of the following:
■
Select a different storage unit that is snapshot-capable to use in the Snapshot
operation.
■
Change the configuration of the desired storage unit so that it supports primary
snapshot operations.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1570
Message: Policy type does not support Index from Snapshot
Explanation: The backup policy type does not support Index from Snapshot
operations. The SLP referenced by the policy contains an Index from Snapshot
operation
Recommended Action: Select a different SLP that does not contain an Index
from Snapshot operation
321
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1571
Message: Data mover type specified in policy does not support Index from
Snapshot
Explanation: The data mover type selected in the backup policy does not support
Index from Snapshot operations. The SLP referenced by the policy contains an
Index from Snapshot operation.
Recommended Action: Select a different SLP that does not contain an Index
from Snapshot operation.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1572
Message: Storage unit must be specified for this operation
Explanation: An SLP operation has been defined but no storage unit has been
included in the operation. Other than Snapshot operations in some circumstances,
all SLP operations require a storage unit to be defined.
Recommended Action: Add a storage unit to the SLP operation.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1573
Message: Backup image cannot be expired because its SLP processing is not yet
complete
Explanation: You tried to expire one or more copies of an SLP-managed image.
The SLP processing that depends on those copies is not complete. The image
cannot be expired.
Recommended Action: Do one of the following:
■
Wait until SLP processing for that image is complete, then retry the expiration
operation.
■
Use the nbstlutil -cancel command to cancel further processing on the
relevant image. Then retry the expiration operation.
322
NetBackup status codes
NetBackup status codes
■
Add the -force_not_complete option to the bpexpdate command to force
expiration even if the image-copy is not SLP complete.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1574
Message: Data Classification name cannot be 'Any' while creating new data
classification
Explanation: You cannot use 'Any' as the data classification name when you
create a new data classification.
Recommended Action: Use a different name and try again.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1575
Message: Data Classification auto creation failed
Explanation: You are automatically creating a new data classification that is the
same as the data classification of the image that is being imported. The data
classification of the image should reside on the master server where the image is
being imported.
Recommended Action: Manually create the data classification on the master
server with the same name as that of the image being imported.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1576
Message: Topology validation failed
Explanation: The validation of the SLP topology fails.
Recommended Action: Do the following:
■
Check that the media servers that are associated with the storage servers are
running.
■
Check the connectivity between the media server (or client) and the storage
server (NetApp OnCommand server).
■
Check the detailed messages supplied with this error to determine the
vendor-specific errors.
323
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1577
Message: Storage unit in the SLP does not match the accelerator attribute in policy
Explanation: The storage unit you have selected for the SLP does not support
the accelerator backup.
Recommended Action: Select a different storage unit for the SLP that does
support the accelerator backup operation.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1578
Message: Invalid window close options
Explanation: The window close option is not valid for the SLP operation.
Recommended Action: If you used the nbstl -wcopt command, make sure that
the specified argument is either SFN or SHN.
For more information on the nbstl command, please see the NetBackup Commands
Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1579
Message: One or more images were not processed because the window closed
Explanation: The processing window closes before all the images are processed.
The remaining unprocessed images are processed when the window reopens.
Recommended Action: This behavior is expected and no action is necessary.
Processing resumes when the next window opens.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1580
Message: VMware policy with PFI enabled requires an SLP
324
NetBackup status codes
NetBackup status codes
Explanation: When the 'Persistent Frozen Image' is enabled for a VMware policy,
Replication Director protects the virtual machines. This policy configuration requires
an SLP. This error message is shown at policy validation time.
Recommended Action: Use the VMware policy without Replication Director, or
provide an SLP that has at least a Snapshot operation.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1581
Message: Non-application consistent VMware policy is not compatible with
snapdupe operations
Explanation: Backup for Snapshot operations are not supported on Replication
Director based VMware policies when Application Consistency is disabled. This
error message is shown at policy validation time.
Recommended Action: Enable Application Consistency, or remove the Backup
from Snapshot operation from the SLP definition.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1582
Message: Application consistent VMware policy requires VM quiesce
Explanation: Replication Director based VMware policies require that when
Application Consistency is enabled, the virtual machines are quiesced. This error
message is shown at policy validation time.
Recommended Action: Disable Application Consistency or enable virtual machine
quiesce.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1583
Message: VMware policy with PFI enabled requires VIP auto discovery
Explanation: Persistent Frozen Image Replication Director based VMware policies
require automatic discovery of virtual machines. The manual selection of virtual
machines is not supported. You can select automatic discovery in the NetBackup
Administration Console. The user can change the setting by using the CLI, but
policy validation detects it and generates this error message.
325
NetBackup status codes
NetBackup status codes
Recommended Action: Enable automatic discovery of virtual machines.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1584
Message: VMware policy with 'Persistent Frozen Image' enabled requires schedule
type of Full Backup
Explanation: Replication Director based VMware policies support only full schedule
at this time.
Recommended Action: Use a full schedule and remove all incremental schedules.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1585
Message: Backup image cannot be expired because not all dependent copies are
expired
Explanation: Other images in the NetBackup catalog are dependent upon the
image that is currently being requested for expiration. The selected image cannot
be expired at this time. Regular catalog cleanup and expiration operations handle
this properly. The dependent images are expired first. But if they are still in SLP
processing, they cannot be expired, and therefore the selected image cannot be
expired.
Recommended Action: Wait for the dependent images to be eligible for expiration
when their SLP state transitions into IMAGE_COMPLETE state. Also, you can
cancel the SLP operations on the dependent images.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1586
Message: SLP operation was canceled
Explanation: You cancel a running SLP operation, and someone else tries to
validate the copy.
Recommended Action: No action is required.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
326
NetBackup status codes
NetBackup status codes
NetBackup status code: 1587
Message: Storage lifecycle policy cannot have both target and untarget replication
to remote master
Explanation: Do not define the SLP with a combination of a targeted replication
operation and an untargeted replication operation.
Recommended Action: Do not mix the targeted and untargeted replication
operation to a remote master.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1588
Message: Target master server is already used in one of the replications to remote
master
Explanation:
Recommended Action: Define all targeted replication operations with distinct
target master server.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1589
Message: Cannot connect to specified target master server
Explanation: All services must be up and running on source domain as well as
target domain.
Recommended Action: Check that all services on source domain and target
domain are running.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1590
Message: Cannot find specified target import SLP
Explanation: This error generally occurs when you run the nbstl command.
Recommended Action: Enter a valid name of the target domain SLP with the
import operation, in the targeted replication operation of the source domain’s SLP.
327
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1591
Message: No import SLP(s) found with compatible replication target device.
Explanation: In the target domain, the import SLP is present, but the replication
target device is not compatible.
Recommended Action: Correct one or more of the possible problems.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1592
Message: Trusted master servers are being referred by one or more Storage
Lifecycle Policies (SLPs) on the source or target domain.
Explanation: The user tries to delete a trusted master server from a system. For
example, when the user configures Targeted Auto Image Replication between
domain A (source domain) and domain B (target domain), domain B must be
identified as a trusted master server in domain A. The SLPs are configured to
replicate images from domain A to domain B. If the user tries to delete domain A’s
trusted master entry for domain B when the SLPs still refer to domain B, you will
receive this error code.
Recommended Action: Delete or change the SLPs so they do not refer to domain
B, then try to delete domain B from domain A again.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1593
Message: Replication Director for VMware policy requires mapped backups
Explanation: Replication Director based VMware policies support individual files
and folders recovery for all the protection virtual machines. Therefore, the virtual
machine mapping is selected automatically in the NetBackup Administration
Console. The user can change its setting by using the CLI, but policy validation
detects it and generates this error message.
Recommended Action: Enable mapping.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
328
NetBackup status codes
NetBackup status codes
NetBackup status code: 1594
Message: Failed to determine disk media ID
Explanation: While importing the image in the target domain, the operation could
not determine the disk media ID. The storage server, disk pool, and storage unit
must each have a valid configuration.
Recommended Action: Recheck the storage server, disk pool, and storage unit
configurations.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1596
Message: Select a storage lifecycle policy that has no snapshot operation as a
policy’s Storage Destination
Explanation: Standard storage unit or a storage lifecycle policy that has no
snapshot operation is expected as a policy’s storage destination.
Recommended Action: Select a storage lifecycle policy that has no snapshot
operation as the policy storage destination.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1597
Message: Replication Director for Oracle policy requires an SLP
Explanation: If you select Use Replication Director on an Oracle policy, you
must specify a snapshot SLP as the Override policy storage selection on the full
schedule.
Recommended Action: Configure an SLP with a Snapshot as the first operation
and Replication as a subsequent operation. Specify this SLP as the Override policy
storage selection on the Full schedule.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1598
Message: Oracle policy with PFI and FI enabled requires an SLP
329
NetBackup status codes
NetBackup status codes
Explanation: If you select Perform snapshot backups and Retain snapshot for
Instant Recovery or SLP management on an Oracle policy, you must set up an
SLP as the Override policy storage selection on the full schedule.
Recommended Action: Configure an SLP with a Snapshot as the first operation.
Specify this SLP as the Override policy storage selection on the Full schedule.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1599
Message: Application schedule storage selection cannot be a snapshot SLP
Explanation: You have specified An SLP with Snapshot as the first action for the
Override policy storage selection on the Application schedule.
Recommended Action: Specify a non-SLP storage (basic disk, tape, advanced
disk, etc.) or an SLP with Backup as the first operation for an Override policy storage
selection on the Application schedule
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1600
Message: The Policy storage is a snapshot SLP and the Application schedule
does not override the policy storage selection. Snapshot SLP storage is not allowed
on an Application schedule.
Explanation: You have selected an SLP with Snapshot as the first operation for
the Policy storage in the Attributes tab and the Application schedule does not
override the Policy storage.
Recommended Action: Specify a non-SLP storage (basic disk, tape, advanced
disk, etc.) or an SLP with Backup as the first operation for the Policy storage or as
the Override policy storage selection on the Application schedule.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1601
Message: Full schedule requires a snapshot SLP
Explanation: The current policy configuration requires a snapshot SLP as the
Override policy storage selection on the Full schedule.
330
NetBackup status codes
NetBackup status codes
Recommended Action: Configure an SLP with a Snapshot as the first operation.
Specify this SLP as the Override policy storage selection on the Full schedule.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1602
Message: The Policy storage is not a snapshot SLP and the Full schedule does
not override the policy storage selection. Snapshot SLP storage is required on the
Full schedule.
Explanation: You have specified an SLP with Backup as the first operation for the
policy storage in the Attributes tab and the Full schedule does not override the
policy storage.
Recommended Action: Specify either an SLP with a Snapshot as the first operation
for the Policy storage or as the Override policy storage selection on the Full
schedule.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1603
Message: Failed to save target SLP volume information
Explanation: This error occurs internally when NetBackup tries to create a storage
lifecycle policy with the targeted replication operation. While it configures the
replication operation, it caches the selected target domain SLP volume information
in the EMM of the source domain. If the caching fails, it logs an appropriate message
in the nbemm logs.
Recommended Action: Take action as dictated by the EMM logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1604
Message: No import SLP(s) found with compatible data class.
Explanation: No import SLP is found with a compatible data classification or the
target has no import SLP at all.
Recommended Action:
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
331
NetBackup status codes
NetBackup status codes
NetBackup status code: 1800
Message: Invalid client list
Explanation: For Enterprise Vault-type policies, verify that multiple clients are not
added to the list of clients if you specify any of the following Enterprise Vault 8.0
directives in the backup selection:
■
EV_INDEX_LOCATION=
■
EV_VAULT_STORE_DB=
■
EV_OPEN_PARTITION=
■
EV_CLOSED_PARTITIONS=
■
EV_FINGERPRINT_DB=
■
EV_READY_PARTITIONS=
Recommended Action: Specify only one client in the policy, or remove the directive
from the backup selection that does not support multiple client.
See the Troubleshooting section of the NetBackup for Enterprise Vault Agent
Administrator’s Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1915
Message: Cannot delete instance group that contains instances (delete or move
instances first)
Explanation: User tries to delete an instance group that contains instances.
Recommended Action: First delete the instances individually by selecting them
under the instances node in the NetBackup Administration Console or by using
the nboraadm -delete_instances. After all the instances in the group have been
deleted, try again to delete the group.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1916
Message: Database error, cannot access the instance repository
Explanation: The user tries to view the list of instances in the NetBackup
Administration Console, but the Sybase database is down.
332
NetBackup status codes
NetBackup status codes
Recommended Action: Make sure that all NetBackup services are started and
that nbdb installed correctly.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1917
Message: Cannot add instance group, this group name is already in use
Explanation: User tries to add an instance group with the same name as an
existing group. All instance groups must have unique names.
Recommended Action: Do one of the following:
■
CLI: Retry the nboraadm -add_instance_group command again with a different
group name.
■
GUI: Type a different group name in the appropriate field, and try to add the
group again.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1918
Message: Cannot find a group by this name
Explanation: The user tries to delete or modify an instance group that does not
exist. If this error occurs on the command line, the group name may be spelled
incorrectly. Because of the cache in the NetBackup Administration Console, an
instance group name may yet appear in the list of instance groups even though the
group does not exist anymore.
Recommended Action: Do one of the following:
■
CLI: Make sure that the group name is spelled correctly. Note that group names
are case-sensitive. If you believe that the name is correct, run nboraadm
-list_instance_groups to verify what groups exist.
■
GUI: Refresh the view (F5 key).
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1919
Message: This instance or instance group was modified by another process, refresh
before editing
333
NetBackup status codes
NetBackup status codes
Explanation: In the NetBackup Administration Console, the user tries to edit,
modify, or delete an instance or instance group that another process has modified.
Recommended Action: Refresh the view (F5 key).
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1920
Message: An instance with this name and client already exists
Explanation: A user tries to add an instance whose name already exists in the
repository (ORACLE SID), client, and home directory. These three identifiers make
an instance unique, so at least one must be changed to add another instance.
In the GUI, a user tries to add a new instance to an unrefreshed display, so they
try to add it again.
Recommended Action: Do one of the following:
■
CLI: Use nboraadm -list_instances to view the instances that already exist.
■
GUI: Refresh the view (F5 key).
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1921
Message: The specified instance cannot be found
Explanation: The user tries to modify or delete an instance that does not exist.
Recommended Action: Do one of the following:
■
CLI: Make sure that the instance name is spelled correctly, because you specify
the instance by typing the instance name (ORACLE SID). On Windows, the
instance name is not case-sensitive. On UNIX, the instance name is
case-sensitive
■
GUI: Refresh the view (F5 key).
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1922
An instance with this name/client is already registered
334
NetBackup status codes
NetBackup status codes
Explanation: A user tries to register a duplicate instance. An instance with the
same name, client, and home directory has already been registered in the repository
(ORACLE SID). These three identifiers make an instance unique, so at least one
identifier must be changed to register another instance.
Recommended Action: Do one of the following:
■
CLI: Run nboraadm -list_instances to view what instances already exist.
■
GUI: Refresh the view (F5 key).
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1924
Message: Domain is a required field for Windows instances
Explanation: The user tries to register a Windows instance, but a domain is not
specified.
Recommended Action: Specify a domain in the domain field, then try to register
the instance again.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1925
Message: The requested operation(s) failed
Explanation: A generic, unspecified error occurred. Different versions of NetBackup
may exist on the client and the server. Or, you ran the nboraadm command with
the wrong parameters.
Recommended Action: Recheck the command line arguments. If the error persists,
check the debug logs for clues or contact Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1926
Message: The entry specified already exists
Explanation: The user tries to add a database administrator by running nboraadm,
but that user has already been added. A user name and a client name make a
unique entry.
Recommended Action: The DBA has already been added, so no action is needed.
335
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1927
Message: The entry specified does not exist
Explanation: The user tries to add a database administrator using nboraadm, but
that user does not exist in the DBA list.
Recommended Action: The user has already been deleted, so no action is likely
needed. Use the nbboraadm -list_dbas command to verify the list of DBAs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 1928
Message: The credentials for 1 or more instances could not be verified
Explanation: The validation failed. No specific information has returned that
explains the reason why. The user name or password may be incorrect, or an issue
exists connecting to the client.
Recommended Action: Make sure that the client is running at least this version
of NetBackup, and is configured to use the correct master server. Make sure that
you correctly entered the user name, password, and auxiliary fields such as domain
(Windows) or TNS (Oracle or RMAN).
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2000
Message: Unable to allocate new media for backup, storage unit has none
available.
Explanation: The NetBackup Media and Device Selection component (MDS) did
not allocate a new tape volume for backups. The storage unit has no more volumes
available in the volume pool for this backup. NetBackup does not change storage
units during the backup.
Recommended Action: Try the following:
■
Check the NetBackup Problems report to determine the storage unit that is out
of media.
■
If the storage unit is a robot with empty slots, add more volumes and specify
the correct volume pool. If no empty slots exist, move some media to non-robotic
336
NetBackup status codes
NetBackup status codes
and add new volumes. If you have difficulty keeping track of your available
volumes, try the available_media script located in the following directory:
On UNIX: /usr/openv/netbackup/bin/goodies/available_media
On Windows: install_path\NetBackup\bin\goodies\available_media.cmd
This script lists all volumes in the volume configuration, and information on the
volumes currently assigned to NetBackup.
■
Set up a scratch volume pool as a reserve of unassigned tapes. If NetBackup
needs a new tape and none are available in the current volume pool, it moves
a tape from the scratch pool into the volume pool that the backup uses.
■
If the storage unit and volume pool appear to have media, verify the following:
■
Use the NetBackup Media List report to check if the volume is FROZEN or
SUSPENDED. If so, use the bpmedia command to unfreeze it or unsuspend
it, if so desired.
■
The volume has not expired or exceeded its maximum number of mounts.
■
The EMM database host name for the device is correct. If you change the
EMM database host name, stop and restart the Media Manager device
daemon (ltid for a UNIX server) or the NetBackup Device Manager service
(Windows server).
■
The correct host is specified for the storage unit in the NetBackup
configuration. The host connection must be the server (master or media)
with drives connected to it.
■
The Media and Device Management volume configuration has media in the
correct volume pool. Unassigned or active media is available at the required
retention level. Use the NetBackup Media List report to show the retention
levels, volume pools, and status for all volumes. Use the NetBackup Media
Summary report to check for active volumes at the correct retention levels.
■
Create the bptm debug log directory, and set the MDS VxUL logging (OID 143)
to debug level 2. Then retry the operation.
■
If this storage unit is new and this attempt to use it is the first, stop and restart
NetBackup on the master server. The MDS unified logging files (OID 143) at
debug level 2 usually show the NetBackup media selection process.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2001
Message: No drives are available for this job
337
NetBackup status codes
NetBackup status codes
Explanation: A job requested a tape drive, but no eligible drive path was configured
for the job.
Recommended Action: Try the following:
■
Verify that the required drives and robots are configured and up.
■
Verify that ltid is active and a drive path exists that is configured on the drive
for the media server that the storage unit requires.
■
If the job requires an NDMP drive path, verify that one exists.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2002
Message: Invalid STU identifier type
Explanation: A job has asked for allocation using an invalid storage unit identifier
type. The only valid storage unit identifier types are 0 (specific STU), 1 (group) or
2 (ANY).
Recommended Action: This error is internal. Call NetBackup support for resolution.
Check the following logs:
■
The mds unified logging files (OID 143) from the master server at debug level
2.
■
The nbrb unified logging files (OID 118) from the master server at debug level
3.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2003
Message: Drive is not allocated.
Explanation: MDS has been asked to deallocate a drive that is not allocated.
Recommended Action: This error is internal to the MDS component of NetBackup.
Check the following logs:
■
The MDS unified logging files (OID 143) from the master server at debug level
2.
■
The nbrb unified logging files (OID 118) from the master server at debug level
3.
338
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2004
Message: Drive is already allocated
Explanation: MDS has been erroneously asked to allocate a drive that is already
allocated.
Recommended Action: A drive may have been reset while it was allocated for a
job. Wait for the jobs that use the drive to complete.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2005
Message: MDS has received an invalid message from a media server.
Explanation: bptm or bpdm on a media server has sent an improperly formatted
message to MDS.
Recommended Action: This error is internal. Call NetBackup support if this error
causes jobs to fail.
Check the following logs:
■
The mds unified logging files (OID 143) from the master server at debug level
2.
■
The nbrb unified logging files (OID 118) from the master server at debug level
3.
■
The bptm legacy log from the media server, with VERBOSE=5.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2006
Message: NDMP credentials are not defined in EMM.
Explanation: No eligible media server is configured with NDMP credentials to
access the NDMP storage unit. Or, NetBackup tried to restore an NDMP image
from a disk storage unit when the media server does not have a valid version of
NetBackup.
Recommended Action: If the job uses an NDMP device, verify that the media
server has NDMP credentials that are configured for the filer.
339
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2007
Message: Storage unit is not compatible with requesting job
Explanation: A job has asked for a storage unit that cannot be used for the job.
Recommended Action: A job tries to run on a media server that is running an
older version of NetBackup. The job may require a feature that is not available on
the media server being requested. Verify that the storage unit type and the media
server that the policy and storage unit call out support the feature.
This error can occur when the policy being run is not compatible with the storage
units requested by the policy:
■
Catalog backups are directed to shared disk storage units.
■
Multiplexed jobs are directed to storage units that do not have the multiplex
feature configured.
■
NDMP backup policies are directed to non-NDMP storage units.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2008
Message: All compatible drive paths are down
Explanation: All configured drives that can be used for this job are down.
Recommended Action: Verify that ltid is running on the required media server,
and that the media server is active for tape. Using a device monitor, bring up the
drive paths if they are down. If the drives are downed again, clean the drives.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2009
Message: All compatible drive paths are down but media is available
Explanation: All configured drives that can be used for this job are down.
Recommended Action: Verify that ltid is running on the required media server,
and that the media server is active for tape. Using a device monitor, bring up the
drive paths if they are down. If the drives are downed again, clean the drives.
340
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2010
Message: Job type is invalid
Explanation: The job type that is specified in an allocation request to the Resource
Broker is not valid for the operation requested.
Recommended Action: This error is internal. Call NetBackup Technical Support
if this error causes jobs to fail.
Check the following logs:
■
The mds unified logging files (OID 143) from the master server at debug level
2.
■
The nbrb unified logging files (OID 118) from the master server at debug level
3.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2011
Message: The media server reported a system error
Explanation: An allocation for the media server is in an inconsistent state.
Recommended Action: This error is internal. Call NetBackup support if this error
causes jobs to fail.
Check the following logs:
■
The mds unified logging files (OID 143) from the master server at debug level
2.
■
The nbrb unified logging files (OID 118) from the master server at debug level
3.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2012
Message: Media has conflicts in EMM
Explanation: You cannot use the requested media because it is marked as having
conflicts in the nbemm database.
341
NetBackup status codes
NetBackup status codes
Recommended Action: The media is marked as having conflicts. The upgrade
from NetBackup 5.x has found multiple volume databases where two tapes in
different volume databases have the same media ID. Call Technical Support to
resolve this situation.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2013
Message: Error record insert failed
Explanation: A database record insert has failed.
Recommended Action: This error is internal. Call NetBackup support if this error
causes jobs to fail.
Check the following logs:
■
The mds unified logging files (OID 143) from the master server at debug level
2.
■
The nbrb unified logging files (OID 118) from the master server at debug level
3.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2014
Message: Media is not assigned
Explanation: A job requires assigned media, but the requested media is not
assigned.
Recommended Action: Verify that the job requested the desired media. For
example, if you want to list contents of the media, make sure that you have specified
the correct media ID.
Check the following logs:
■
The mds unified logging files (OID 143) from the master server at debug level
2.
■
The nbrb unified logging files (OID 118) from the master server at debug level
3.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
342
NetBackup status codes
NetBackup status codes
NetBackup status code: 2015
Message: Media is expired
Explanation: A job is trying to write to media that has already expired.
Recommended Action: Make sure that non-expired media is available for the
job.
Check the following logs:
■
The mds unified logging files (OID 143) from the master server at debug level
2.
■
The nbrb unified logging files (OID 118) from the master server at debug level
3.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2016
Message: Media is assigned to another server
Explanation: A job cannot use the media on the storage server, because the
media is assigned to another storage server.
Recommended Action: Check the following logs:
■
The mds unified logging files (OID 143) from the master server at debug level
2.
■
The nbrb unified logging files (OID 118) from the master server at debug level
3.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2017
Message: Media needs to be unmounted from a drive
Explanation: The requested media needs to be unmounted from the drive it is in
before it can be used for another job.
Recommended Action: Identify the media that is requested by the job that returns
this error. If it is used by another job, wait for that job to complete.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
343
NetBackup status codes
NetBackup status codes
NetBackup status code: 2018
Message: Number of cleanings is invalid
Explanation: A cleaning media has an invalid number of cleanings that remain.
Recommended Action: On the Change Media screen, set the number of cleanings
remaining for the cleaning media to a number greater than or equal to zero (0).
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2019
Message: Media is in a drive that is not configured on local system
Explanation: A job is configured to use a media volume that has no drive path
configured to an eligible media server for the job. A media volume is misplaced or
all drive paths are down for the media server accessible by the storage unit that is
configured for a job.
Recommended Action: If drive paths are down, identify the media server that is
configured for use by the storage unit, and bring up the drive path to that media
server.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2020
Message: Robotic library is down on server
Explanation: NetBackup has marked the robot as down for the required media
server.
Recommended Action: Verify that the media server that is required for this
allocation is running, and verify that ltid is up on that media server.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2021
Message: Allocation record insert failed
Explanation: The NetBackup mds component was unable to update the database
for a device allocation.
Recommended Action: This error is internal. Check the following logs:
344
NetBackup status codes
NetBackup status codes
■
The mds unified logging files (OID 143) from the master server at debug level
2.
■
The nbrb unified logging files (OID 118) from the master server at debug level
3.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2022
Message: Allocation status record insert failed
Explanation: The NetBackup mds component was unable to update the database
with device allocation status information.
Recommended Action: This error is internal. Check the following logs to help
identify the problem:
■
The mds unified logging files (OID 143) from the master server at debug level
2.
■
The nbrb unified logging files (OID 118) from the master server at debug level
3.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2023
Message: Allocation identifier is not known to EMM
Explanation: The NetBackup mds component cannot find the device allocation
record that is needed to allocate the device for this job.
Recommended Action: This error is internal. Check the following logs to help
identify the problem:
■
The mds unified logging files (OID 143) from the master server at debug level
2.
■
The nbrb unified logging files (OID 118) from the master server at debug level
3.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2024
Message: Allocation request update failed
345
NetBackup status codes
NetBackup status codes
Explanation: The NetBackup mds component was unable to update the database
for a device allocation.
Recommended Action: This error is internal. Check the following logs to help
identify the problem:
■
The mds unified logging files (OID 143) from the master server at debug level
2.
■
The nbrb unified logging files (OID 118) from the master server at debug level
3.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2025
Message: Allocation request delete failed
Explanation: The NetBackup mds component was unable to delete a device
allocation from the database.
Recommended Action: This error is internal. Check the following logs to help
identify the problem:
■
The mds unified logging files (OID 143) from the master server at debug level
2.
■
The nbrb unified logging files (OID 118) from the master server at debug level
3.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2026
Message: Allocation status request delete failed
Explanation: The NetBackup mds component was unable to modify an allocation
status record for this job.
Recommended Action: This error is internal. Check the following logs to help
identify the problem:
■
The mds unified logging files (OID 143) from the master server at debug level
2.
■
The nbrb unified logging files (OID 118) from the master server at debug level
3.
346
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2027
Message: Media server is not active
Explanation: This job requires a media server that is not currently available.
Recommended Action: Do one or more of the following:
■
Verify that the media server that is required for this allocation is running.
■
If this is a tape job, verify that ltid is running on the media server. If a media
server has gone offline and returned online, a delay of several minutes may
occur before a job can use that media server.
■
Use the vmoprcmd command to show the state of the media server. If the job is
trying to access a disk storage unit, verify that the nbrmms process is running
on the media server. If the job is trying to access a tape storage unit, verify that
ltid is running on the media server.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2028
Message: Media is reserved
Explanation: The NetBackup mds component cannot allocate media because
another job has that media exclusively reserved.
Recommended Action: If multiple duplication jobs attempt to use the same tape
media for read, each job reserves the media. NetBackup should allow more than
one job to get a reservation for the tape media.
This error is internal. Check the following logs to help identify the problem:
■
The mds unified logging files (OID 143) from the master server at debug level
2.
■
The nbrb unified logging files (OID 118) from the master server at debug level
3.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2029
Message: EMM database is inconsistent
347
NetBackup status codes
NetBackup status codes
Explanation: An inconsistency in the NetBackup database prevents allocations
for this job.
Recommended Action: This error is internal. Check the following logs to help
identify the problem:
■
The mds unified logging files (OID 143) from the master server at debug level
2.
■
The nbrb unified logging files (OID 118) from the master server at debug level
3.
Run the nbrbutil -resetall command to get the NetBackup allocation database
back into a consistent state. Note that this command cancels all jobs including those
that are currently running.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2030
Message: Insufficient disk space or high water mark would be exceeded
Explanation: Insufficient disk space is available to run this job.
Recommended Action: Try the following possible solutions:
■
If there are images on the disk that can be expired, expire them, and run
nbdelete to delete the images from disk.
■
It may be that NetBackup creates disk images more quickly than they expire. If
so, modifications to policies may be necessary to change the rate of image
creation and expiration for the disk.
■
It may be helpful to lower the high water mark and low water mark for the disk
group.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2031
Message: Media is not defined in EMM
Explanation: The media that is required for this job is not defined in the EMM
database.
Recommended Action: A media volume that is required for a restore job has
been deleted from the EMM database. If the media is available, use bpimport to
import it.
348
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2032
Message: Media is in use according to EMM
Explanation: The NetBackup database indicates that the media is in use but is
not allocated to another job.
Recommended Action: This error is internal. Check the following logs to help
identify the problem:
■
The mds unified logging files (OID 143) from the master server at debug level
2.
■
The nbrb unified logging files (OID 118) from the master server at debug level
3.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2033
Message: Media has been misplaced
Explanation: Job requires media that is not in the expected robotic slot.
Recommended Action: Verify that the media that is required by the job is in the
proper robotic slot as shown by vmquery.
If the error persists, the following logs may be useful in understanding the problem:
■
The mds unified logging files (OID 143) from the master server at debug level
2.
■
The nbrb unified logging files (OID 118) from the master server at debug level
3.
■
The verbose bptm logs on the media server(s) that access this media.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2034
Message: Retry the allocation request later
Explanation: Resources that are required for a job are currently in use.
349
NetBackup status codes
NetBackup status codes
Recommended Action: This error should never appear as a job return status. In
the mds and nbrb vxul logs, it indicates that a job should queue because resources
are busy.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2035
Message: Request needs to pend
Explanation: A job requires operator intervention before it can continue.
Recommended Action: This error should never appear as a job return status. In
the mds and nbrb vxul logs, it indicates that a job should post a request for operator
intervention to the NetBackup device monitor.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2036
Message: Drive is in a robotic library that is up
Explanation: Operator has attempted to assign a pending tape mount request to
a drive that is in a robot that is up.
Recommended Action: A request for non-robotic media may have caused a
pending request in the device monitor, and the operator has assigned the request
to a drive that is not a standalone drive. This error is not fatal. The request will pend
again in the NetBackup device monitor. Assign the pending mount to a standalone
drive or to a drive that is in AVR mode (non-robotic).
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2037
Message: Drive is not ready
Explanation: The required tape is in a drive, but the drive is not in a ready state.
Recommended Action: This error may occur when a request for non-robotic
media had caused a pending request in the device monitor, and the operator has
assigned the request to a drive that is not in a ready state. This error is not a fatal
error. The request will pend again in the NetBackup device monitor. Verify that
required tape is in the drive it is assigned to, and that the drive ready light has come
on. It may take some time for the drive to become ready after the tape has been
350
NetBackup status codes
NetBackup status codes
inserted. If the drive never goes to a ready state after a tape has been inserted,
there may be a problem with the drive.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2038
Message: Media loaded in drive is not write-enabled
Explanation: This error may occur when a storage unit request for non-robotic
media had caused a pending request in the device monitor, and the operator has
inserted media that is not write enabled into the drive.
Recommended Action: This is not a fatal error. The request will pend again in
the NetBackup device monitor. If you are sure that it is OK to write on this tape,
verify that the required tape has its write enable switch set to allow write.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2039
Message: SCSI reservation conflict detected
Explanation: The NetBackup bptm component was unable to read or write a tape
drive because another job unexpectedly holds a SCSI reservation for the drive.
Recommended Action: This error should never occur at job resource allocation
time, but may occur during i/o for a tape job. The verbose bptm logs on the media
server may be useful in understanding the problem.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2040
Message: Maximum job count has been reached for the storage unit
Explanation: Storage cannot be allocated because it would exceed maximum job
count. The maximum job count is configurable for each storage unit. Multiple copy
jobs may cause this same error, if there are more copies targeted for a storage unit
than the amount of copies for which the storage unit was configured.
Recommended Action: Target a different storage unit with one of the copies, or
increase the maximum job count for the storage unit.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
351
NetBackup status codes
NetBackup status codes
NetBackup status code: 2041
Message: Storage unit is down
Explanation: A disk storage unit has been designated as down and cannot be
used.
Recommended Action: Run the bperror -disk command to indicate why the
disk is considered down.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2042
Message: Density mismatch detected
Explanation: This error is an internal NetBackup error. A job has requested media
with the wrong density. A mismatch may exist between the image catalog and the
media database.
Recommended Action: Restore the jobs request tape media by media ID density.
If the requested density does not match the configured density for the media, it
cannot be allocated.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2043
Message: Requested slot is empty
Explanation: Media is not found in the expected slot in the robot.
Recommended Action: The robot may need to be inventoried.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2044
Message: Media is assigned to another application
Explanation: Requested media cannot be allocated because it is assigned to an
application other than NetBackup.
Recommended Action: Verify that the media that is required for the job is assigned
to NetBackup.
352
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2045
Message: Storage unit is disabled since max job count is less than 1
Explanation: Storage unit cannot be used because its maximum job count is set
to 0.
Recommended Action: Increase the maximum job count (or maximum concurrent
drive count) to a value greater than 0.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2046
Message: Media is unmountable
Explanation: Media has been marked as unusable due to mount errors.
Recommended Action: Clean the drives in the media's robot. Determine if any
of the media is bad.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2047
Message: Media is write protected
Explanation: The media cannot be used for a write job because it is write protected.
Recommended Action: Make sure that media in the scratch pool is not write
protected.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2048
Message: Media is in use by the ACS robotic library
Explanation: ACS media that is required by this job is in use on another system.
Recommended Action: Make sure that the required media is not in use by another
application.
353
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2049
Message: Media not found in the ACS robotic library
Explanation: Media that this job needs is not found in the ACS robotic library.
Recommended Action: Make sure that the required media is available in the ACS
robot.
For more information, see the section on configuring ACSLS robots in the NetBackup
Device Configuration Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2050
Message: ACS media has an unreadable external label
Explanation: This job needs the ACS media that cannot be used because its
external label or barcode is unreadable.
Recommended Action: Correct the barcode label problem for this media.
For more information, see the section on configuring ACSLS robots in the NetBackup
Device Configuration Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2051
Message: ACS media is not in the drive's domain
Explanation: Media that is required for this job is in an ACS robot that is not
accessible.
Recommended Action: Verify that the robot that contains the required media is
accessible to a NetBackup media server.
For more information, refer to the section on configuring ACSLS robots in the
NetBackup Device Configuration Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
354
NetBackup status codes
NetBackup status codes
NetBackup status code: 2052
Message: An ACS Library Storage Module (LSM) is offline
Explanation: The required ACS LSM is offline.
Recommended Action: Bring the ACS LSM online.
For more information, see the section on configuring ACSLS robots in the NetBackup
Device Configuration Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2053
Message: Media is in an inaccessible drive
Explanation: The required media is currently loaded in a DOWN or otherwise
inaccessible drive.
Recommended Action: Locate the media and correct the problem that has caused
the drive or drive path to be down.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2054
Message: Media is in a drive that is currently in a DOWN state
Explanation: Required media is currently loaded in a drive that is down.
Recommended Action: Locate the media and correct the problem that has caused
the drive or drive path to be down.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2055
Message: ACS physical drive is not available
Explanation: The media server cannot load ACS media because a drive is not
available.
Recommended Action: Locate and install an ACS drive.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
355
NetBackup status codes
NetBackup status codes
NetBackup status code: 2056
Message: The file name used for the mount request already exists
Explanation: The tpreq command cannot load this media because the specified
file name already exists.
Recommended Action: Specify a different file name for tpreq, or run the
tpunmount command for the media which has been loaded using tpreq with the
conflicting file name.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2057
Message: The scan host of the drive is not active
Explanation: The scan host for a standalone drive is offline, so the drive cannot
be allocated.
Recommended Action: If the problem persists, restart the NetBackup media
servers that have paths to this drive.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2058
Message: LTID needs to be restarted on media servers before the device can be
used
Explanation: A drive cannot be used because an ltid restart is required. This
error may occur when configuration changes have been made on a media server,
but ltid has not been subsequently restarted.
Recommended Action: When the media server is not in a busy state, stop and
restart ltid on that media server.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2059
Message: The robotic library is not available
Explanation: The robot that is required for a drive cannot be found in the nbemm
database.
356
NetBackup status codes
NetBackup status codes
Recommended Action: Verify that the robot that the jobs require is properly
configured. If the error persists, the following logs may be useful in understanding
the problem: The mds unified logging files (OID 143) from the master server at debug
level 2.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2060
Message: Media needs to be rewound or unmounted from a drive
Explanation: The NetBackup mds component uses this error internally to inform
the Resource Broker that a tape needs to be unloaded. It should never appear as
a job error status.
Recommended Action: Not applicable.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2061
Message: The host is not an active node of a cluster
Explanation: A cluster failover has occurred while a job is running. A job may be
waiting for a span on a media server that has failed over.
Recommended Action: Restart the failed job.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2062
Message: Throttled job count has been reached for the storage unit
Explanation: This error is not returned as a job status.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2063
Message: Server is not licensed for the Remote Client Option
Explanation: The media server required for this job does not have the Remote
Client Option enabled. A SAN media server is asked to back up a client that is not
also a media server, or a VMware backup is tried on a SAN media server.
357
NetBackup status codes
NetBackup status codes
Recommended Action: Backup this client on a media server that is licensed to
do so. Verify that the media server has connectivity to the master server when
adding its licenses.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2064
Message: Job history indicates that no media is available
Explanation: When a job is run on a media server that is installed with invalid
NetBackup software, there are some situations where the job starts, but media is
not available for the job. In this case, the master server stops using that storage
unit for a period of time (12 hours), and returns this error for jobs requested the
storage unit.
Recommended Action: Make sure that media is available for the storage unit. If
necessary, upgrade the software on the media server. Add media if necessary. If
media is available, wait 12 hours until the storage unit can be used again. To make
the storage unit immediately usable, run the following command on the master
server to release the hold:
nbrbutil -releaseAllocHolds
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2065
Message: Job history indicates that no drive is available
Explanation: When a job is run on a media server that is installed with invalid
NetBackup software, there are some situations where the job starts, but the drives
that are designated for the job are busy or otherwise unavailable, causing the job
to fail. In this case, the NetBackup master server stops using that drive for a period
of time (several minutes), and returns this error for jobs requesting that drive.
Recommended Action: Upgrade the media server software. Make sure all of the
drives in the storage unit are up and available for use. Clean all drives that need
cleaning.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2066
Message: Disk pool not found
358
NetBackup status codes
NetBackup status codes
Explanation: A job has been targeted for a disk pool that does not exist in the
nbemm database.
Recommended Action: Verify that the storage unit that this job uses is configured
for use with a properly configured disk pool.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2067
Message: Disk volume not found
Explanation: A read job requires a disk volume that does not exist in the nbemm
database. Or a write job is configured for a disk pool with no configured volumes.
Recommended Action: Verify that the disk storage that this job uses is configured
for use with a disk pool that has volumes configured. For a read job, verify that the
volume that is required for reading exists in the nbemm database.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2068
Message: Disk volume mount point not found
Explanation: A disk volume is not configured with a mount point or not completely
configured in the nbemm database.
Recommended Action: Verify that the configuration is correct for the disk group
and for the disk volumes in the disk group.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2069
Message: Disk volume mount point record insert failed
Explanation: A database update has failed while trying to allocate a disk job.
Recommended Action: This error is internal. If the problem persists, please call
NetBackup support for resolution. Check the following logs to help identify the
problem:
■
The mds unified logging files (OID 143) from the master server at debug level
2.
359
NetBackup status codes
NetBackup status codes
■
The nbrb unified logging files (OID 118) from the master server at debug level
3.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2070
Message: The specified mount path will not fit in the allocated space
Explanation: A disk volume mount point path is larger than the allowed maximum.
Recommended Action: This error is internal. If the problem persists, please call
NetBackup support for resolution. Check the following logs to help identify the
problem:
■
The mds unified logging files (OID 143) from the master server at debug level
2.
■
The nbrb unified logging files (OID 118) from the master server at debug level
3.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2071
Message: Unable to find any storage servers for the request
Explanation: NetBackup was unable to find a storage server for this disk job.
Recommended Action: Verify that the storage servers serving the disk group that
the job requires are configured and enabled. Verify that they are in an UP state.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2072
Message: Invalid operation on static mount point
Explanation: An incorrectly configured mount point has been found for a disk
volume.
Recommended Action: This error is internal. If the problem persists, please call
NetBackup support for resolution. Check the following logs to help identify the
problem:
■
The mds unified logging files (OID 143) from the master server at debug level
2.
360
NetBackup status codes
NetBackup status codes
■
The nbrb unified logging files (OID 118) from the master server at debug level
3.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2073
Message: Disk pool is down
Explanation: Required disk pool cannot be used because it is in a DOWN state.
Recommended Action: Run the bperror -disk command to determine why the
disk pool was put into a DOWN state. Correct the problem, and use the nbdevconfig
command to return the disk pool to an UP state.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2074
Message: Disk volume is down
Explanation: Required disk volume cannot be used because it is in a DOWN state.
Recommended Action: You may be able to see why the disk volume was put
into a DOWN state by runningbperror -disk. Correct the problem, and use
nbdevconfig to return the disk volume to an UP state.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2075
Message: Fibre Transport resources are not available
Explanation: A job is configured to require Fibre Transport for this SAN client, but
no available Fibre Transport connection exists.
Recommended Action: Configure the job to switch to LAN transport if Fibre
Transport is not available. Verify that the job type being run is compatible with Fibre
Transport. Using nbdevquery, verify that the Disk Pool being requested is enabled
for use with Fibre Transport. Verify that there are Fibre Transport connections that
are up between the client and media server required for the job. Check the following
logs to help identify the problem:
■
The mds unified logging files (OID 143) from the master server at debug level
2.
361
NetBackup status codes
NetBackup status codes
■
The nbrb unified logging files (OID 118) from the master server at debug level
3.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2076
Message: DSM returned an unexpected error
Explanation: The Disk Service Manager component of NetBackup has returned
an unexpected error.
Recommended Action: This error is internal. If the problem persists, please call
NetBackup support for resolution. Check the following logs to help identify the
problem:
■
The mds unified logging files (OID 143) from the master server at debug level
2.
■
The nbrb unified logging files (OID 118) from the master server at debug level
3.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2078
Message: The maximum number of mounts for the disk volume have been
exceeded
Explanation: A disk volume cannot be used by a job because it is mounted by too
many other users.
Recommended Action: This error is internal. If the problem persists, please call
NetBackup support for resolution. Check the following logs to help identify the
problem:
■
The mds unified logging files (OID 143) from the master server at debug level
2.
■
The nbrb unified logging files (OID 118) from the master server at debug level
3.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
362
NetBackup status codes
NetBackup status codes
NetBackup status code: 2079
Message: DSM has detected that an invalid file system is mounted on the volume
Explanation: NetBackup did not find the file system it expected on a disk volume.
Recommended Action: Verify that the disk volumes and their associated mount
points that NetBackup uses are not used by other applications.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2080
Message: Disk volume has no max writers count
Explanation: Disk volume is not properly configured for a usable number of
mountpoints.
Recommended Action: Verify proper disk configuration by using nbdevquery.
This error is internal. If the problem persists, please call NetBackup support for
resolution. Check the following logs to help identify the problem:
■
The mds unified logging files (OID 143) from the master server at debug level
2.
■
The nbrb unified logging files (OID 118) from the master server at debug level
3.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2081
Message: Disk volume has no max readers count
Explanation: Disk volume is not properly configured for a usable number of
mountpoints.
Recommended Action: Verify the proper disk configuration by using nbdevquery.
This error is internal. If the problem persists, please call NetBackup support for
resolution. Check the following logs to help identify the problem:
■
The mds unified logging files (OID 143) from the master server at debug level
2.
■
The nbrb unified logging files (OID 118) from the master server at debug level
3.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
363
NetBackup status codes
NetBackup status codes
NetBackup status code: 2082
Message: The drive needs to be marked as available
Explanation: Drive cannot be used because it is allocated with loaded media, but
MDS has not made it available for use.
Recommended Action: Run the nbrbutil -dump command on the master server
to show allocations for this job. If the problem persists, run the nbrbutil
-releaseMDS command to release the allocation for the drive so it can be used.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2083
Message: The media affinity group is not defined in EMM
Explanation: MDS expected to find a group of reservations for this media, but did
not find the expected reservation group.
Recommended Action: This error is internal. If the problem persists, check the
following logs to help identify the problem:
■
The mds unified logging files (OID 143) from the master server at debug level
2.
■
The nbrb unified logging files (OID 118) from the master server at debug level
3.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2084
Message: Media affinity group record insert failed
Explanation: MDS cannot update reservation group information for this tape media.
Recommended Action: This error is internal. If the problem persists, check the
following logs to help identify the problem:
■
The mds unified logging files (OID 143) from the master server at debug level
2.
■
The nbrb unified logging files (OID 118) from the master server at debug level
3.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
364
NetBackup status codes
NetBackup status codes
NetBackup status code: 2085
Message: Disk volume is not available
Explanation: The job requires more disk volumes than are currently configured.
Recommended Action: Ensure that the disk group has disk volumes configured.
A multiple copy job cannot target two copies for the same disk volume.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2086
Message: Disk volume cannot be used for more than one copy in the same job
Explanation: Not enough eligible disk volumes are configured for this multiple
copy job.
Recommended Action: Use the nbdevquery -listdv command to verify that
the expected disk volume is configured. For a multiple copy job, ensure that unique
eligible disk volumes exist for each copy. A multiple copy job cannot target two
copies for the same disk volume.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2087
Message: Media allocation would exceed maximum partially full media limit
Explanation: You cannot run this job because it would exceed configured limit of
maximum partially full media.
Recommended Action: This error may occur with a multiple copy job or a
duplication job. If the problem persists, you may need to increase maximum partially
full media setting on the disk pool.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2088
Message: Cleaning media is not available
Explanation: You cannot run a cleaning job because no cleaning media is
configured for the drive.
Recommended Action: Add a cleaning volume to the robot containing the drive.
365
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2089
Message: FT client is not running
Explanation: This job requires Fibre Transport, but the Fibre Transport client is
not running on the client that is required for this job.
Recommended Action: Do one or more of the following:
■
Verify that the Private Branch Exchange (PBX) service is installed and running.
Run the bpps -x command to ensure that pbx_exchange is listed in the
processes that are running.
■
Verify that the client is configured as a SAN Client. Run the bpclntcmd
-sanclient command to return the current state of the SAN Client. A response
of 0 (zero) indicates that SAN Client is not configured. Rerun the command as
bpclntcmd -sanclient 1.
■
Verify that the client is not also a media server, master server, or EMM server.
The SAN Client process runs only on a NetBackup client.
■
Verify that a valid license for the SAN Client feature resides on the master server.
SAN Client is a separately licensed feature which requires a key called "SAN
Client" on the master server.
■
Verify that no server entries for the SAN Client exist on the NetBackup master
server. Remove any SERVER=clientname entry in the master server for the SAN
Client. If the master server has the SAN Client listed also as a server, it may
shutdown the SAN Client.
■
Restart the SAN Client service. The SAN Client restarts when the server reboots,
but does not automatically restart after you run the bpclntcmd command. To
start the SAN Client service, run the client startup script or use the Service
Manager in Windows.
For more information, see the Troubleshooting chapter of the NetBackup SAN Client
and Fibre Transport Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2090
Message: FT client has no devices configured
366
NetBackup status codes
NetBackup status codes
Explanation: This job requires Fibre Transport, but Fibre Transport devices are
not configured on the client that is required for this job.
Recommended Action: Verify that Fibre Transport devices are installed on the
client. For further information, see the Troubleshooting chapter of the NetBackup
SAN Client and Fibre Transport Guide available at the following location:
http://www.veritas.com/docs/DOC5332
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2091
Message: FT client devices are offline
Explanation: This job requires Fibre Transport, but all Fibre Transport devices
are offline on the client that is required for this job.
Recommended Action: Do one or more of the following:
■
Verify that the Private Branch Exchange (PBX) service is installed and running.
Run the bpps -x command to ensure that pbx_exchange is listed in the
processes that are running.
■
Verify that the client is configured as a SAN Client. Run the bpclntcmd
-sanclient command to return the current state of the SAN Client. A response
of 0 (zero) indicates that SAN Client is not configured. Rerun the command as
bpclntcmd -sanclient 1.
■
Verify that the client is not also a media server, master server, or EMM server.
The SAN Client process runs only on a NetBackup client.
■
Verify that a valid license for the SAN Client feature resides on the master server.
SAN Client is a separately licensed feature which requires a key called "SAN
Client" on the master server.
■
Verify that no server entries for the SAN Client exist on the NetBackup master
server. Remove any SERVER=clientname entry in the master server for the SAN
Client. If the master server has the SAN Client also listed as a server, it may
shutdown the SAN Client.
■
Restart the SAN Client service. The SAN Client restarts when the server restarts,
but does not automatically restart after you run the bpclntcmd command. To
start the SAN Client service, run the client startup script or use the Service
Manager in Windows.
For further information, see the Troubleshooting chapter of the NetBackup SAN
Client and Fibre Transport Guide.
367
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2092
Message: FT server devices for client are offline
Explanation: This job requires Fibre Transport, but all Fibre Transport devices
are offline on the media server required for this job.
Recommended Action: Do one of the following:
■
Verify that marked QLogic Target ports exist in the server. The nbftsrvr and
nbfdrv64 processes exit if the system has no ports available for Target Mode
use.
■
Verify that a valid license for the SAN Client feature resides on the master server.
SAN Client is a separately licensed feature that requires a key called "SAN
Client" on the master server. The Fibre Transport server performs a license
check during startup.
■
Determine if a reboot is required for the installation of the Fibre Transport server.
Solaris installations require that you reboot the media server after you install
Fibre Transport to load the Fibre Transport drivers on the marked target ports.
In addition, reboot the Linux servers if you choose to not unload the existing
QLogic drivers during the installation of Fibre Transport.
For further information, see the Troubleshooting chapter of the NetBackup SAN
Client and Fibre Transport Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2093
Message: No FT servers for this client are running
Explanation: This job requires Fibre Transport, but no Fibre Transport devices
are configured with connectivity to the media server that is required for this job.
Recommended Action: Do one of the following:
■
Verify that marked QLogic Target ports exist in the server. The nbftsrvr and
nbfdrv64 processes exit if the system has no ports available for Target Mode
use.
■
Verify that a valid license for the SAN Client feature resides on the master server.
SAN Client is a separately licensed feature which requires a key called "SAN
368
NetBackup status codes
NetBackup status codes
Client" on the master server. The Fibre Transport server performs a license
check during startup.
■
Determine if a reboot is required for the installation of the Fibre Transport server.
Solaris installations require that you reboot the media server after you install
Fibre Transport to load the Fibre Transport drivers on the marked target ports.
In addition, reboot the Linux servers if you choose to not unload the existing
QLogic drivers during the installation of Fibre Transport.
For further information, see the NetBackup SAN Client and Fibre Transport
Troubleshooting Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2094
Message: STU cannot run Lifecycle backups
Explanation: The storage lifecycle job cannot run because the targeted disk pool
is not enabled for Storage Lifecycles.
Recommended Action: Run the nbdevquery -listdp command to check the
configuration of the disk pool. If the Lifecycle attribute is not enabled for the disk
pool, run the nbdevconfig -changedp -setattribute command to enable it.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2095
Message: STU cannot run VMware backup
Explanation: The media server that is configured for this job's storage unit cannot
run VMware backups.
Recommended Action: To run a VMware backup, the media server must run a
valid version of NetBackup. Verify that a valid version of NetBackup is running or
configure the backup for a media server that runs a valid version of NetBackup.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2096
Message: NDMP operation does not support multiple inline copies
Explanation: The backup cannot run because it is an NDMP policy and is
configured for multiple copies.
369
NetBackup status codes
NetBackup status codes
Recommended Action: NetBackup cannot make multiple copies of NDMP policies.
Configure the backup for a single storage unit destination.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2097
Message: Storage unit group does not exist in EMM configuration
Explanation: You cannot run this job because it is configured to use a storage
unit group that does not exist in the NetBackup configuration.
Recommended Action: Reconfigure the policy to use a storage unit or storage
unit group that exists in the configuration.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2098
Message: Media pool is not eligible for this job
Explanation: This job is configured to use a pool that does not exist in the
NetBackup configuration.
Recommended Action: Change the configured media pool for the job to use a
pool that is configured, or create the required media pool. Make sure that the media
pool you have configured for the job is not a scratch pool.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2099
Message: Required drive or drive path is not configured
Explanation: This job requires a drive that does not exist in the NetBackup
configuration.
Recommended Action: Run the vmoprcmd command to verify the drive
configuration. Configure the drives that are necessary for the media type that is
used.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
370
NetBackup status codes
NetBackup status codes
NetBackup status code: 2100
Message: Maximum number of mounts has been exceeded for tape media
Explanation: The job cannot run because the required media has exceeded
configured maximum mounts.
Recommended Action: Increase the maximum allowed mounts for the media.
You may need to retire this media if it has exceeded the maximum number of mounts
you have configured.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2101
Message: Media server not found in EMM database
Explanation: The possible causes include the following:
■
For a tape backup, the media server that performed the backup is not in the
EMM database.
■
For an OpenStorage optimized duplication job, the media server in common
between the source environment and the target environment does not have the
credentials for both storage servers.
Recommended Action: Do the following as appropriate:
■
For a restore from tape, you can use the Force Media Server Restore option to
force NetBackup to replace the missing media server with a new media server.
■
For optimized duplication, ensure that the media server in common has
credentials for both storage servers. More information about OpenStorage
optimized duplication is available.
See the NetBackup OpenStorage Solutions Guide for Disk.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2102
Message: Storage unit does not support spanning
Explanation: A disk job has requested a span for a disk type that does not support
spanning.
Recommended Action: Some disk types do not support spanning. Run the
nbdevconfig -listdg command to determine if a disk group supports spanning.
371
NetBackup status codes
NetBackup status codes
If this error persists, ensure that enough space is available on your disk storage
units for the new jobs that are running.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2103
Message: Media server mismatch
Explanation: This error may occur when a multiple copy job is configured for the
storage units that have no common media server.
Recommended Action: All copies of a multiple copy job must run on the same
media server. Configure the storage units that have drive paths or disk access from
a common media server.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2104
Message: Storage units are not available
Explanation: This error may occur for multiple copy jobs that are configured so
that no possible storage unit combination can be used.
Recommended Action: Verify that all criteria in met for the policy with the storage
units that are configured.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2105
Message: Storage unit requested for replication job is not replication capable
Explanation: This error can occur when a replication job requests a storage unit
for write, but the disk that the storage unit calls out is not replication enabled.
Recommended Action: Make sure that replication jobs include status configured
for replication enabled disks in their storage unit specifiers.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2106
Message: Disk storage server is down
372
NetBackup status codes
NetBackup status codes
Explanation: This error can occur when a job uses a disk storage unit whose disk
group resides on a storage server that NetBackup has marked down. This error
can also occur when a cloud storage backup fails.
Recommended Action: Verify that all media servers that are configured for the
storage server can communicate with the storage server. The bpstsinfo command
queries the storage server periodically, so you can use the bpstsinfo log set to
verbosity level 5 on the media server.
If the error is related to a cloud storage backup failure, you should verify the following
information:
■
The cacert.pem file is on both the NetBackup master and the media server in
the following locations:
■
UNIX/Linux: /usr/open/var/webtruststore
■
Windows: install_path/var/webtruststore
■
The cacert.pem file is the same on the NetBackup master and the media server.
■
The machine certificate is in the following location:
■
UNIX/Linux: /usr/openv/var/vxss/credentials
■
Windows: install_path/var/vxss/credentials
■
The NetBackup CloudStore Service is active.
■
The Enable insecure communication with 8.0 and earlier hosts option on
the NetBackup master server is selected if the media server is version 8.0 or
earlier. The option is available in the NetBackup Administration Console on
the Security Management > Global Security Settings > Secure
Communication tab.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2107
Message: Requested media server does not have credentials or is not configured
for the storage server
Explanation: A job has requested disk media for a media server that does not
have credentials to access the disk storage server. During optimized duplication
between two storage servers of the same type, a media server that is configured
for the write side storage unit may not have credentials to access the read side
storage server.
Recommended Action: Optimized duplication requires a media server with
credentials for both the read side and write side storage servers. Add the needed
373
NetBackup status codes
NetBackup status codes
credentials or limit the media servers that the write side storage unit calls out to
those that are credentialed for the read media.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2108
Message: Requested NDMP machine does not have credentials or is not configured
in NetBackup
Explanation: A job requests the use of an NDMP machine that is not configured
in NetBackup.
Recommended Action: Jobs for NDMP policies require that the NDMP host that
is specified as the client in the policy be configured in NetBackup. The credentials
that are defined for any server must access the NDMP host.
Verify that the required NDMP host is configured. If the configured NDMP host is
a fully qualified name and the NDMP host name in the policy is not, run the following
command to add an alias to the NDMP host:
# nbemmcmd -machinealias -addalias -alias string -machinename string
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2109
Message: Requested Fibre Transport client machine was not found in NetBackup
configuration
Explanation: A job requests a Fibre Transport client machine that is not found in
the NetBackup configuration.
Recommended Action: Fibre Transport backup and restore operations require
each Fibre Transport client to be configured in NetBackup. Verify that the client that
is requested for the job is configured as a Fibre Transport client.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2110
Message: Requested machine is not configured in NetBackup
Explanation: A job has requested a machine that is not configured in NetBackup.
374
NetBackup status codes
NetBackup status codes
Recommended Action: The policy that you use to run the job may indicate which
server the job requires. If not, find the server that the job looks for by setting the
MDS VxUL logging (OID 143) to debug level 2 and retry the job. The MDS log
usually indicates which host name caused the problem.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2111
Message: All storage units are configured with On Demand Only and are not
eligible for jobs requesting ANY storage unit
Explanation: A job has requested any available storage unit, but all storage units
are configured with On Demand Only.
Recommended Action: Change the policy to use a specific storage unit instead
of any available storage unit, or configure at least one storage unit without the On
Demand Only setting.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2112
Message: NetBackup media server version is too low for the operation
Explanation: The storage unit or storage unit group points to a media server that
runs an earlier version of software than the master server. Hence, the media server
cannot use all the functionality of the newer NetBackup version. This mismatch of
software affects many write operations such as backup operations and duplication
write operations.
Recommended Action: Point the storage unit to a media server with a newer
version of software.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2113
Message: Invalid or no disk array credentials are added for vserver
Explanation: Invalid or no credentials found in Disk Array Hosts credential section
for NetApp Storage Virtual Machine's interface name having management access
enabled.
375
NetBackup status codes
NetBackup status codes
Recommended Action: Under the Disk Array Hosts credentials section, add admin
credentials of NetApp Storage Virtual Machine's interface that has management
access enabled. Ensure that the right Storage Virtual Machine's interface name is
entered that holds the snapshot/replica to be indexed. Ensure that the Storage
Virtual Machine (SVM) user account with the ONTAPi application is in the unlocked
state.
See the NetBackup Replication Director Solutions Guide for more information.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2504
Message: Direct expiration of a mirror copy is not allowed
Explanation: The mirror copy alone cannot be expired. It expires when the parent
copy expires.
Recommended Action: None
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2517
Message: Backup set identifier may only contain a-z, A-Z, 0-9 and .-+_
Explanation: An Oracle backup set identifier (TAG) contains an invalid character
outside of the following characters: a-z, A-Z, 0-9 and special characters ., -, +, and
_.
Recommended Action: Remove the invalid character from the backup set identifier.
This value is specified in the Attributes tab of the GUI Policy utility.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2521
Message: Datafile copy tag may only contain a-z, A-Z, 0-9 and .-+_
Explanation: The Datafile copy tag contains an invalid character outside of the
following characters: a-z, A-Z, 0-9 and special characters ., -, +, and _.
Recommended Action: Remove the invalid character from the Datafile copy tag.
This value is specified in the Oracle tab of the GUI Policy utility.
376
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2522
Message: Oracle policy cannot include a pluggable database with a FRA backup.
Explanation: NetBackup does not support FRA with Oracle 12c pluggable
databases.
Recommended Action: Check the Oracle Intelligent Policy. If the policy has
Protect Instances and Databases selected and includes pluggable databases,
then the backup selection cannot be Fast Recovery Area (FRA). You can either
select a different backup selection or select the Oracle 12c instance and Fast
Recovery Area (FRA).
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2523
Message: Failed to add client to NetBackup configuration.
Explanation: There was an internal error when a client was added to the
configuration. This type of error can occur after the domain name is changed.
Recommended Action: Save the nbemm and bpdbm logs and contact Veritas
Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2524
Message: Catalog backup failed because the passphrase for the disaster recovery
package is not set.
Explanation: During the catalog backup, the disaster recovery package is created.
NetBackup requires the passphrase when it creates the disaster recovery package.
If the passphrase has not already been set, the catalog backup fails.
Recommended Action: To set the passphrase for the disaster recovery package,
do one of the following:
■
In the NetBackup Administration Console, expand Security Management
> Global Security Settings. On the Disaster Recovery tab, set the passphrase.
■
Use the nbseccmd –drpkgpassphrase command.
377
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2525
Message: The passphrase for the disaster recovery package is not set. You must
set it for the catalog backups to be successful.
Explanation: During the catalog backup, the disaster recovery package is created.
NetBackup requires the passphrase when it creates the disaster recovery package.
If the passphrase is not set earlier, the catalog backup fails.
The error message is displayed when you configure the catalog backup policy. You
should set the passphrase before you configure the catalog backup policy.
Recommended Action: To set the passphrase for the disaster recovery package,
do one of the following:
■
In the NetBackup Administration Console, expand Security Management
> Global Security Settings. On the Disaster Recovery tab, set the passphrase.
■
Use the nbseccmd –drpkgpassphrase command.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2800
Message: Standard policy restore error
Explanation: Some or all of the restore operation files failed. When performing a
Snapshot Client restore, you may have selected a different path from the path in
the policy's Backup Selections list.
For example, vol6 is mounted on /mnt/vol6 and vol7 is mounted on /mnt/vol7.
These mount points are specified in the backup selection. If you select only the
parent directory (/mnt), the restore fails with status code 2800.
Recommended Action: Try the following possible solutions in the order presented:
■
Ensure that the client server list contains entries for the master server and any
media servers that can be used during a backup or restore.
■
Examine the status or the progress log on the client for messages about why
the restore failed. Also, check the All Log Entries report on the server.
■
Check the following logs for additional failure information:
■
NetBackup tar log
■
Master server: bprd, nbjm
378
NetBackup status codes
NetBackup status codes
■
Media server: bpbrm, bptm, bpdm
■
Client: tar
■
Make sure that the required media server is available for the restore, or use the
Media host override option.
■
Verify that the media that is required for the restore is present and that the robot
has been inventoried.
■
Verify that no network issues exist between the media server and the client.
■
Select the original path that is listed in the Backup Selections tab.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2801
Message: Oracle policy restore error
Explanation: An error caused the restore of the Oracle data to fail.
Recommended Action: Try the following possible solutions in the order presented:
■
Ensure that the client server list contains entries for the master server and any
media servers that can be used during a backup or restore.
■
Examine the status or the progress log on the client for messages on why the
restore failed. Also, check the All Log Entries report on the server.
■
Check ownership and permission on directories where files are restored.
■
Check ownership and permission on the Oracle instance that you restore.
■
Check the NetBackup dbclient and user_ops logs for additional failure
information.
■
If restoring to an alternate client using RMAN, more information is available in
the following technical article:
http://www.veritas.com/docs/TECH5840
Check that the Oracle user on the client can successfully communicate with the
master server by using the bpclntcmd -pn command.
■
Check that the Oracle user on the client can see the backup images on the
master by using the bplist command.
■
On UNIX and Linux hosts, check that the oracle user has sufficient permissions
to read /etc/services, /etc/nsswitch.conf, and
/usr/openv/netbackup/bp.conf.
379
NetBackup status codes
NetBackup status codes
■
Ensure that the Oracle database is linked correctly, according to the NetBackup
for Oracle Administrator's Guide (for example, $ORACLE_HOME/lib/libobk.so).
More information is available in the following technical article:
http://www.veritas.com/docs/TECH72307
■
Correct the problems that you find and retry the restore.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2802
Message: Informix-On-BAR policy restore error
Explanation: An error caused the restore of the Informix data to fail.
Recommended Action: Try the following possible solutions in the order presented:
■
Ensure that the client server list contains entries for the master server and any
media servers that can be used during a backup or restore.
■
Examine the status or the progress log on the client for messages on why the
restore failed. Also, check the All Log Entries report on the server.
■
Check ownership and permission on directories where files are restored.
■
Check ownership and permission on the Informix instance that you restore.
■
Check the NetBackup infxbsa and user_ops logs from the client, and the bprd
log from the master server for additional failure information.
■
Check the Informix BAR_ACT_LOG, BAR_DEBUG_LOG, and MSGPATH logs
for additional failure information.
■
For large database restores, you may need to increase the client read timeout
value.
■
If you are restoring to an alternate client, review the checklist in the following
article:
http://www.veritas.com/docs/TECH21719
■
Correct the problems that you find and retry the restore.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2803
Message: Sybase policy restore error
Explanation: An error caused the restore of the Sybase data to fail.
380
NetBackup status codes
NetBackup status codes
Recommended Action: Try the following possible solutions in the order presented:
■
Ensure that the client server list contains entries for the master server and any
media servers that can be used during a backup or restore.
■
Examine the status or the progress log on the client for messages on why the
restore failed. Also, check the All Log Entries report on the server.
■
Check ownership and permission on the Sybase instance that you restore and
on the directories where files are restored.
■
Check the NetBackup sybackup log for additional failure information.
■
Create the following log folders, then retry the restore:
On the client:
/usr/openv/netbackup/logs/bphdb
/usr/openv/netbackup/logs/bprestore
/usr/openv/netbackup/logs/tar
/usr/openv/netbackup/logs/sybackup
chmod 777 /usr/openv/netbackup/logs/sybackup
chmod 777 /usr/openv/netbackup/logs/bphdb
On the media server:
/usr/openv/netbackup/logs/bptm
/usr/openv/netbackup/logs/bpbrm
On the master server:
/usr/openv/netbackup/logs/bprd
■
Correct the problems that you find and retry the restore.
To set the debug level on UNIX and Linux clients, enter the following line in the
bp.conf file:
VERBOSE = 5
For a Sybase alternate client restore, the user ID (UID) of the restoring Sybase
backup server must match the UID of the Sybase backup server from the source
host.
For an alternate client restore, authorize the alternate client to access images for
the original client.
Verify that the alternate client can browse the backup images for the original client:
# /usr/openv/netbackup/bin/bplist -C <origClient> -t 7 -l -R /
# install_path\netbackup\bin\bplist -t 7 -l -R /
381
NetBackup status codes
NetBackup status codes
On the alternate client, use the bpclntcmd command to test connectivity and name
resolution. The command should display the name of the master server on the first
line. The second line must contain the IP address of the network interface that the
alternate client used when communicating with the master server. The first word
on the second line is the name of the alternate client as resolved on the master
server from the IP address. The second word on the second line may be 'NULL' if
the alternate client is not being backed up. Otherwise, it is the name of the alternate
client (or an alias) which is defined in a backup policy on the master server.
# /usr/openv/netbackup/bin/bpclntcmd -pn
Make sure that CLIENT_READ_TIMEOUT on the alternate client and media server
is set large enough to allow the tapes to be read, the data transferred, and the
database instance to write the data to disk.
See the following technical article for information about the steps for a Sybase
alternative client restore operation:
http://www.veritas.com/docs/TECH24125
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2804
Message: MS-SharePoint policy restore error
Explanation: An error caused the restore of the SharePoint data to fail.
Recommended Action: Try the following possible solutions in the order presented:
■
Ensure that the client server list contains entries for the master server and any
media servers that can be used during a backup or restore.
■
Examine the status or the progress log on the client for messages on why the
restore failed. Also, check the All Log Entries report on the server.
■
Check ownership and permission on directories where files are restored.
■
Create the following log folders on the SQL Server, the front-end web server,
the media server, and the master server:
install_path\NetBackup\logs\tar
install_path\NetBackup\logs\bpresolver
install_path\NetBackup\logs\bpbrm (media server)
install_path\NetBackup\logs\bprd (master server)
If you use granular restore technology (GRT), the following log folders also
apply:
382
NetBackup status codes
NetBackup status codes
install_path\NetBackup\logs\ncf
install_path\NetBackup\logs\ncflbc
install_path\NetBackup\logs\ncfgre
install_path\NetBackup\logs\nbfsd
install_path\NetBackup\logs\spsv2ra
■
Check all SharePoint server Event Viewers (application and system) for any
errors.
■
Connect to the server where the SharePoint front-end server runs and launch
the restore using Backup, Archive, and Restore GUI.
■
Make sure that the restore is being launched correctly.
See the NetBackup for Microsoft SharePoint Administrator’s Guide.
■
Correct the problems that you find and retry the restore.
■
If you need to restore a VMware job, you must ensure that the media server is
added to the additional server list. To access this list in the NetBackup
Administration Console, expand Host Properties > Master Server.
Double-click the name of the server to view the properties. Select the Servers
tab to display the server list. In the Servers properties dialog box, select the
Additional Servers tab and add the media server to the server list.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2805
Message: MS-Windows policy restore error
Explanation: An error caused some or all of the files to fail the restore operation.
Recommended Action: Try the following possible solutions in the order presented:
■
Ensure that the client server list contains entries for the master server and any
media servers that can be used during a backup or restore.
■
Examine the status or the progress log on the client for messages on why the
restore failed. Also, check the All Log Entries report on the server.
■
Check that you have selected the correct restore type on the Backup, Archive,
and Restore GUI.
■
Check ownership and permission on directories where files are restored.
■
Check the following logs for additional failure information:
■
Master server: bprd, nbjm
■
Media server: bpbrm, bptm, bpdm
383
NetBackup status codes
NetBackup status codes
■
■
Client: tar
Correct the problems that you find and retry the restore.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2806
Message: NetWare policy restore error
Explanation: An error caused the restore of the NetWare data to fail.
Recommended Action: Try the following possible solutions in the order presented:
■
Ensure that the client server list contains entries for the master server and any
media servers that can be used during a backup or restore.
■
Examine the status or the progress log on the client for messages on why the
restore failed. Also, check the All Log Entries report on the server.
■
Check ownership and permission on directories where files are restored.
■
Check the NetBackup tar log for additional failure information. Also check the
following log files: bpcd, bpsrv, bprest, and user_ops.
■
For target restores, ensure that you have create and write rights to the volume
that you are trying to restore. In the BP.INI file, ensure that the
Allow_Server_Write parameter is set to yes.
■
If you launched a non-target restore from the NetBackup Administration
Console, ensure that the Allow server directed restores parameter is selected.
■
Correct the problems that you find and retry the restore.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2807
Message: SQL-BackTrack policy restore error
Explanation: An error caused the restore of the SQL-BackTrack data to fail.
Recommended Action: Try the following possible solutions in the order presented:
■
Ensure that the client server list contains entries for the master server and any
media servers that can be used during a backup or restore.
■
Examine the status or the progress log on the client for messages on why the
restore failed. Also, check the All Log Entries report on the server.
384
NetBackup status codes
NetBackup status codes
■
Check ownership and permission on directories where files are restored and on
the SQL-BackTrack instance that you are restoring.
■
Check the NetBackup backtrack log for additional failure information.
■
Ensure that the No.Restrictions file has been added on the master server in
case of an alternate client restore.
■
Correct the problems that you find and retry the restore.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2808
Message: Windows File System policy restore error
Explanation: An error caused some or all of the files to fail the restore operation.
Recommended Action: Try the following possible solutions in the order presented:
■
Ensure that the client server list contains entries for the master server and any
media servers that can be used during a backup or restore.
■
Examine the status or the progress log on the client for messages on why the
restore failed. Also, check the All Log Entries report on the server.
■
Check that you have selected the correct restore type on the Backup, Archive,
and Restore GUI.
■
Check ownership and permission on directories where files are restored.
■
Check that the destination directories or files exist. If so, select the Overwrite
existing files option on the Backup, Archive, and Restore GUI.
■
Check the following logs for additional failure information:
■
■
Master server: bprd, nbjm
■
Media server: bpbrm, bptm, bpdm
■
Client: tar
Correct the problems that you find and retry the restore.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2809
Message: MS-SQL-Server policy restore error
Explanation: An error caused the restore of the SQL Server data to fail.
385
NetBackup status codes
NetBackup status codes
Recommended Action: Try the following possible solutions in the order presented:
■
Ensure that the client server list contains entries for the master server and any
media servers that can be used during a backup or restore.
■
Examine the status or the progress log on the client for messages on why the
restore failed. Also, check the All Log Entries report on the server.
■
Check ownership and permission on directories where files are restored and on
the SQL instance that you are restoring.
■
Check ownership and permission on the SQL Server instance and on the
directories where files are restored.
■
Check the following logs for additional failure information on the client side:
install_path\NetBackup\logs\dbclient
install_path\NetBackup\logs\bpbkar (Snapshot Client)
install_path\NetBackup\logs\bpfis (Snapshot Client)
install_path\NetBackup\logs\bppfi (instant recovery)
■
Check the SQL server Event Viewers (application and system) for any errors
or messages that are related to the restore operation.
■
Increase restore verbose levels.
See the NetBackup for SQL Server Administrator’s Guide.
Review this guide to verify that you launched the restore correctly.
■
Connect to the server where SQL is running and launch the restore from that
server using the Backup, Archive, and Restore GUI.
■
Correct the problems that you find and retry the restore.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2810
Message: MS-Exchange policy restore error
Explanation: An error caused the restore of the Exchange data to fail.
Recommended Action: Try the following possible solutions in the order presented:
■
Ensure that the client server list contains entries for the master server and any
media servers that can be used during a backup or restore.
■
Examine the status or the progress log on the client for messages on why the
restore failed. Also, check the All Log Entries report on the server.
386
NetBackup status codes
NetBackup status codes
■
Check ownership and permission of the Exchange instance that you restore
and the directories where files are restored.
■
Verify the following log files depending on the type of restore being performed.
All the log folders are located in the install_path\NetBackup\logs folder.
■
beds - All restore operations.
■
tar - All restore operations.
Restores with Granular Recovery Technology (GRT):
■
nbfsd - This log appears on the client and the media server.
■
ncf - This log uses unified logging and appears on the destination client or
proxy client.
■
ncflbc - This log is for nblbc.exe. It appears on the destination client or
proxy client.
■
ncfgre - This log is for nbgre.exe. It appears on the destination client or
proxy client.
Instant Recovery and Instant Recovery off-host:
■
bpbkar - For off-host Instant Recovery restores, bpbkar logs on the alternate
client.
■
bpfis - This log applies to Instant Recovery rollback restores. For off-host
Instant Recovery backups, bpfis logs exist on both the primary and the
alternate clients.
■
bppfi - For off-host Instant Recovery restores, bppfi logs on both the primary
and the alternate clients.
■
Check the Exchange Server Event Viewer for Application and System messages
that are related to the restore operation.
■
Connect to the server where Exchange is running and launch the restore from
that server using the Backup, Archive, and Restore GUI.
■
Verify that you launched the restore correctly.
See the NetBackup for Microsoft Exchange Server Administrator’s Guide.
■
Correct the problems that you find and retry the restore.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2811
Message: SAP policy restore error
387
NetBackup status codes
NetBackup status codes
Explanation: An error caused the restore of the SAP data to fail.
Recommended Action: Try the following possible solutions in the order presented:
■
Ensure that the client server list contains entries for the master server and any
media servers that can be used during a backup or restore.
■
Examine the status or the progress log on the client for messages on why the
restore failed. Also, check the All Log Entries report on the server.
■
Check ownership and permission of the SAP instance that you restore and the
directories where the files are restored.
■
Ensure that the No.Restrictions file has been created on the master server
in case of an alternate client restore.
■
Check the following logs for additional failure information: backint, tar,
dbclient, bprestore, and user_ops.
■
Correct the problems that you find and retry the restore.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2812
Message: DB2 policy restore error
Explanation: An error caused the restore of the DB2 data to fail.
Recommended Action: Try the following possible solutions in the order presented:
■
Ensure that the client server list contains entries for the master server and any
media servers that can be used during a backup or restore.
■
Examine the status or the progress log on the client for messages on why the
restore failed. Also, check the All Log Entries report on the server.
■
Check ownership and permission of the DB2 instance that you restore and the
directories where the files are restored.
■
Check the NetBackup bpdb2 log for additional failure information.
■
Ensure that the No.Restrictions file has been created on the master server
in case of restore.
■
Correct the problems that you find and retry the restore.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
388
NetBackup status codes
NetBackup status codes
NetBackup status code: 2813
Message: NDMP policy restore error
Explanation: An error caused some or all of the files to fail the restore operation.
Recommended Action: Try the following possible solutions in the order presented:
■
Ensure that the client server list contains entries for the master server and any
media servers that can be used during a backup or restore.
■
Examine the status or the progress log on the client for messages on why the
restore failed. Also, check the All Log Entries report on the server.
■
Check the ownership and permission on directories where files are restored.
■
Verify that the destination NDMP host supports DAR. If not, disable DAR.
■
Check the ndmpagent (Originator ID 134) log for additional failure information.
■
Check the NetBackup bptm log for additional failure information.
■
Check that the Force rollback even if it destroy snapshots option of the
point-in-time rollback restore is set (checked) or not set (unchecked).
For more information on rollback restore, please see the NetBackup Replication
Director Solutions Guide from the following location:
http://www.veritas.com/docs/DOC5332
■
Correct the problems that you find and retry the restore.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2814
Message: FlashBackup policy restore error
Explanation: An error caused some or all of the files to fail the restore operation.
Recommended Action: Try the following possible solutions in the order presented:
■
Ensure that the client server list contains entries for the master server and any
media servers that can be used during a backup or restore.
■
Examine the status or the progress log on the client for messages on why the
restore failed. Also, check the All Log Entries report on the server.
■
Check ownership and permission on directories where files are restored.
■
Check the NetBackup tar log for additional failure information.
■
Enable and verify VxMS logs for additional failure information.
■
For VMware restores, enable the bpvmutil logs.
389
NetBackup status codes
NetBackup status codes
■
If you run a VMware restore, make sure that the user account that is specified
in the VMware credentials has full administration rights on the target vCenter
and the ESX server.
■
Correct the problems that you find and retry the restore.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2815
Message: AFS policy restore error
Explanation: An error caused some or all of the files to fail the restore operation.
Recommended Action: Try the following possible solutions in the order presented:
■
Ensure that the client server list contains entries for the master server and any
media servers that can be used during a backup or restore.
■
Examine the status or the progress log on the client for messages on why the
restore failed. Also, check the All Log Entries report on the server.
■
Check ownership and permission on directories where files are restored.
■
Check the NetBackup tar log for additional failure information.
■
Correct the problems that you find and retry the restore.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2816
Message: DataStore policy restore error
Explanation: An error caused the restore of the DataStore data to fail.
Recommended Action: Try the following possible solutions in the order presented:
■
Ensure that the client server list contains entries for the master server and any
media servers that can be used during a backup or restore.
■
Examine the status or the progress log on the client for messages on why the
restore failed. If you run one PureDisk disaster recovery, check the output from
the /opt/pdinstall/DR_Restore_all.sh script on the PureDisk node. Also,
check the All Log Entries report on the server.
■
Check ownership and permission on directories where files are restored.
■
Check ownership and permission on the database instance that you restore.
■
Check the NetBackup exten_client log for additional failure information.
390
NetBackup status codes
NetBackup status codes
■
If you restore a Netezza appliance, collect the log files from
/nz/kit/log/restoresvf/*.
■
Correct the problems that you find and retry the restore.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2817
Message: FlashBackup Windows policy restore error
Explanation: An error caused some or all of the files to fail the restore operation.
Recommended Action: Try the following possible solutions in the order presented:
■
Ensure that the client server list contains entries for the master server and any
media servers that can be used during a backup or restore.
■
Examine the status or the progress log on the client for messages on why the
restore failed. Also, check the All Log Entries report on the server.
■
Check ownership and permission on directories where files are restored.
■
Check the NetBackup tar log for additional failure information.
■
Correct the problems that you find and retry the restore.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2818
Message: NetBackup Catalog policy restore error
Explanation: An error caused the restore of the NetBackup catalog to fail.
Recommended Action: Try the following possible solutions in the order presented:
■
Ensure that the client server list contains entries for the master server and any
media servers that can be used during a backup or restore.
■
Examine the status or the progress log on the client for messages on why the
restore failed. Also, check the All Log Entries report on the server.
■
Ensure that NetBackup is at the same version and patch level as the computer
where the catalog image was created.
■
Ensure that the path where you restore the catalog is same as when it was
backed up.
■
Ensure that sufficient disk space exists on the target system where the restore
runs.
391
NetBackup status codes
NetBackup status codes
■
Ensure that the current master server host name matches the host name of the
computer where the catalog image was created.
■
Check ownership and permission on directories where files are restored.
■
Check the NetBackup tar, admin, bptm, and bpbrm logs for additional failure
information.
■
Correct the problems that you find and retry the restore.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2819
Message: Enterprise Vault policy restore error
Explanation: An error caused the restore of the Enterprise Vault data to fail.
Recommended Action: Try the following possible solutions in the order presented:
■
Ensure that the client server list contains entries for the master server and any
media servers that can be used during a backup or restore.
■
Examine the status or the progress log on the client for messages on why the
restore failed. Also, check the All Log Entries report on the server.
■
Check ownership and permission on directories where files are restored.
■
Check the NetBackup tar log for additional failure information. Also, check the
Enterprise Vault server Event Viewer (application and system) for errors or
clues.
■
Connect to the server where the Enterprise Vault front-end runs. Launch the
restore by using the Backup, Archive, and Restore GUI.
■
Verify that you launched the restore correctly.
See the NetBackup for Enterprise Vault Agent Server Administrator’s Guide.
■
Correct the problems that you find and retry the restore.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2820
Message: NetBackup VMware policy restore error
Explanation: An error caused the restore of the VMware policy data to fail, as
follows:
392
NetBackup status codes
NetBackup status codes
■
393
If a virtual CD or DVD ISO is not available on the host where you restore the
virtual machine, the restore fails. The vCenter interface may include the following
message:
Invalid configuration for Device '1'.
■
If the virtual machine to restore and the virtual machine that contains the hotadd
restore host do not reside in the same data center, the restore fails.
■
The restore host cannot access the VMware datastore over the selected transport
mode. The job log on the restore host may contain messages like the following
example:
FTL - Virtual machine restore: VxMS initialization failed.
■
You attempted to restore a file that has a path name longer than 1023 characters.
A backup of a Linux virtual machine backs up all files, including those with path
names longer than 1023 characters. But you cannot restore the long path-name
files individually.
■
For the restore, the virtual machine's hardware version (such as 7) is later than
the hardware version that the target server supports. If VMware Tools cannot
convert the virtual machine's hardware version to an earlier version, the restore
fails. Messages similar to the following appear in the detailed status log:
Info bpVMutil(pid=6268) INF - vmwareLogger: WaitForTaskCompleteEx:
The virtual machine version is not compatible with the version of the
host <hostname>.
■
You attempted to restore a large virtual machine with one or more VMDKs that
are formatted as Thick Provision Eager Zeroed. Because of the size of the
virtual machine or its VMDKs, creation of the virtual machine may take more
than 2 hours. As a result, the restore failed.
Recommended Action: Check the job details in the Activity Monitor and take
action as dictated by that information, as follows:
■
Ensure that an .ISO file that is presented to a virtual machine as a virtual CD or
DVD during backup is available on the destination host.
■
For a successful hotadd restore, ensure that the two virtual machines are in the
same VMware data center.
■
Select a different transport mode and retry the restore.
■
You cannot restore restore a file that has a path name longer than 1023
characters.
NetBackup status codes
NetBackup status codes
■
If possible, restore the VM to a VMware server that supports the VM's hardware
version.
■
In Backup, Archive, and Restore, change the restored virtual disk to Thick
Provision Lazy Zeroed or Thin Provisioning.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2821
Message: Hyper-V policy restore error
Explanation: On a Hyper-V restore operation, a connectivity issue between the
Hyper-V host and the media server causes bptm to fail to write to the socket.
Recommended Action: Try the following:
■
Update the NIC drivers and firmware if necessary.
■
Ensure that the network hardware between the media server and the client
operates properly.
■
Add NetBackup processes and directories to the Antivirus Exclusion List since
antivirus applications may close the established socket.
■
Increase TCP resiliency on the Windows hosts (master servers, media servers,
and clients) by setting the TcpMaxDataRetransmissions registry key to a value
of 10. The default value is 5.
More information is available from Microsoft about the
TcpMaxDataRetransmissions registry key:
http://msdn.microsoft.com/en-us/library/aa915651.aspx
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2826
Message: Master server failed to connect to backup restore manager on media
server for restore
Explanation: A process on the master server cannot connect to a process on a
host on the network. This error occurs when the process tries to initiate
communication with the server that has the storage unit. This problem can occur
during a restore in either a single or a multiple server configuration.
Recommended Action: Try the following possible solution in the order presented:
■
From the master server, ping the master and all media servers by using the host
names in the storage unit configuration.
394
NetBackup status codes
NetBackup status codes
■
From each of the media servers, ping the master server by using the name that
is specified in the NetBackup server list. On a UNIX or Linux server, this master
is the first SERVER entry in the bp.conf file. On a Windows server, the master
is designated on the Servers tab in the Master Server Properties dialog box.
■
Check that all of the services are running on the media server.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2827
Message: Client failed to connect to the media server for restore
Explanation: The client cannot connect to the media server for a restore operation.
Recommended Action: Try the following possible solution in the order presented:
■
From the master server, ping the master and all media servers by using the host
names in the storage unit configuration.
■
Check that all services are running on the media server.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2828
Message: Restore failed because the MS-SQL-Server services are down
Explanation: The SQL Server services are down on the system where the
NetBackup client and the NetBackup for SQL Server agent are running. So the
NetBackup for SQL Server agent cannot connect to the SQL Server.
Recommended Action: Check that the SQL Server instance service is running
and that NetBackup processes have permission to access the SQL Server instance
service.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2829
Message: Restore failed due to MS-SQL-Server database in use
Explanation: SQL Server database is busy with another operation and cannot
restore the requested database on the system where the NetBackup client and the
NetBackup for SQL Server agent are running.
395
NetBackup status codes
NetBackup status codes
Recommended Action: After the database finishes its current operation, try to
restore the database. Or, the database administrator needs to check if the database
is busy and what operation it is performing.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2830
Message: Restore failed due to an incorrect path in the MS-SQL-Server MOVE
script
Explanation: The MOVE template that is generated for the database restore using
the NetBackup MS SQL Client has an incorrect path that was specified for the
database/log file for the keyword TO.
Recommended Action: Check the MOVE script and correct the path that was
specified for the database log file for the keyword TO.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2831
Message: Restore error
Explanation: An error caused the restore to fail.
Recommended Action: Try the following possible solutions in the order presented:
■
Ensure that the client server list contains entries for the master server and any
media servers that can be used during a backup or restore.
■
Examine the status or the progress log on the client for messages on why the
restore failed. Also, check the All Log Entries report on the server.
■
Check ownership and permission on directories where files are restored.
■
Correct the problems that you find and retry the restore.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2832
Message: Restore failed due to rename file format error
Explanation: The rename file that is used to specify details about virtual machine
alternate client location restores cannot be read because it has an invalid format.
396
NetBackup status codes
NetBackup status codes
Recommended Action: If you want to execute the nbrestorevm command and
manually enter the rename file, verify that the file complies with the format specified
in the NetBackup Commands Reference Guide. For additional information, check
the job details in the Activity Monitor and the bprd log on the master server.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2833
Message: Restore failed due to partition restore error
Explanation: This error is encountered when restoring a raw partition, which
indicates that the backup image is defective.
Recommended Action: If another backup copy exists, make that image the primary
copy and attempt to restore from it. For additional information, check the job details
in the Activity Monitor, the bprd log on the master server, and the bptm log on the
media server.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2834
Message: Restore failed due to failure to read change block bitmap
Explanation: NetBackup cannot read the change block bitmap header of the
backup image, which indicates that the backup image is defective.
Recommended Action: If another backup copy exists, make that image the primary
copy and attempt to restore from it. For additional information, check the job details
in the Activity Monitor, the bprd log on the master server, and the bptm log on the
media server.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2835
Message: Restore failed due to corrupt image
Explanation: NetBackup reads an invalid backup image header type, which
indicates that the backup image is defective.
Recommended Action: If another backup copy exists, make that image the primary
copy and attempt to restore from it. For additional information, check the job details
397
NetBackup status codes
NetBackup status codes
in the Activity Monitor, the bprd log on the master server, and the bptm log on the
media server.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2836
Message: Restore failed because the bitmap size read from the image header
differs from the expected size.
Explanation: The bitmap size in the backup image header is inconsistent with the
bitmap size found in the NetBackup internal database. This failure indicates that
the backup image is defective.
Recommended Action: If another backup copy exists, make that image the primary
copy and attempt to restore from it. For additional information, check the job details
in the Activity Monitor, the bprd log on the master server, and the bptm log on the
media server.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2837
Message: Restore failed due to invalid metadata
Explanation: Invalid metadata cannot be added to the backup image header,
which indicates that the backup image is defective.
Recommended Action: If another backup copy exists, make that image the primary
copy and attempt to restore from it. For additional information, check the job details
in the Activity Monitor, the bprd log on the master server, and the bptm log on the
media server.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2838
Message: Restore failed because no raw partitions were found
Explanation: No raw partitions were found in the backup image, which may indicate
that the backup image is defective.
Recommended Action: Verify that the backup image contains a list of raw
partitions. This error may indicate that the backup image is defective. For additional
398
NetBackup status codes
NetBackup status codes
information, check the job details in the Activity Monitor, the bprd log on the master
server, and the bptm log on the media server.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2839
Message: Restore failed due to invalid raw partition ID
Explanation: NetBackup cannot identify the raw partition ID, which indicates that
the backup image is defective.
Recommended Action: If another backup copy exists, make that image the primary
copy and attempt to restore from it. For additional information, check the job details
in the Activity Monitor, the bprd log on the master server, and the bptm log on the
media server.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2840
Message: Restore failed due to out of sequence raw partitions
Explanation: Raw partition file numbers are out of sequence, which indicates that
the backup image is defective.
Recommended Action: If another backup copy exists, make that image the primary
copy and attempt to restore from it. For additional information, check the job details
in the Activity Monitor, the bprd log on the master server, and the bptm log on the
media server.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2841
Message: Restore failed due to failure to read the header from the backup image
Explanation: The restore cannot read the backup image header, which indicates
that the backup image is defective.
Recommended Action: If another backup copy exists, make that image the primary
copy and attempt to restore from it. For additional information, check the job details
in the Activity Monitor, the bprd log on the master server, and the bptm log on the
media server.
399
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2842
Message: Restore failed due to failure to read the VMware bitmap
Explanation: The restore operation is unable to retrieve the VMware bitmap from
the backup image, which indicates that the backup image is defective.
Recommended Action: If another backup copy exists, make that image the primary
copy and attempt to restore from it. For additional information, check the job details
in the Activity Monitor, the bprd log on the master server, and the bptm log on the
media server.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2843
Message: Restore failed due to failure to start VxMS
Explanation: The restore is unable to load VxMS. VxMS is a library used to map
physical addresses of files and volumes.
Recommended Action: Verify that the media server and the recovery host
environment has adequate memory and correct file permissions. For additional
information, check the job details in the Activity Monitor and the bprd log on the
master server.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2844
Message: Restore failed due to failure to read the FIID file
Explanation: The restore operation is unable to read the FIID file, which indicates
that the backup image is defective.
Recommended Action: If another backup copy exists, make that image the primary
copy and attempt to restore from it. For additional information, check the job details
in the Activity Monitor, the bprd log on the master server, and the bptm log on the
media server.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
400
NetBackup status codes
NetBackup status codes
NetBackup status code: 2845
Message: Restore failed due to failure to retrieve the bitmap
Explanation: The restore operation cannot retrieve the backup image bitmap from
the NetBackup internal database, which indicates that the backup image is defective.
Recommended Action: If another backup copy exists, make that image the primary
copy and attempt to restore from it. For additional information, check the job details
in the Activity Monitor, the bprd log on the master server, and the bptm log on the
media server.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2846
Message: Restore failed due to failure to retrieve the fsmap
Explanation: The restore operation cannot retrieve the backup image's file system
map from the NetBackup internal database, which indicates that the backup image
is defective.
Recommended Action: If another backup copy exists, make that image the primary
copy and attempt to restore from it. For additional information, check the job details
in the Activity Monitor, the bprd log on the master server, and the bptm log on the
media server.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2847
Message: Restore failed due to failure to start the bptm writer
Explanation: The restore operation is unable to start the bptm writer process.
Recommended Action: Verify that the media server and the recovery host
environment has adequate memory and correct file permissions. For additional
information, check the job details in the Activity Monitor and the bprd log on the
master server.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2848
Message: Restore failed due to failure to create the virtual machine
401
NetBackup status codes
NetBackup status codes
Explanation: The following are possible causes:
■
Credentials for the VMware server do not have sufficient permissions to create
a virtual machine.
■
Insufficient space on a datastore.
■
Incompatible VM configuration or vmdk configuration.
■
Error or task cancelation on the VMware server.
For additional information, check the job details in the Activity Monitor, the bprd log
on the master server, and the bptm log on the media server.
Recommended Action: Do the following:
■
Check that the VMware server has sufficient permissions.
■
Increase the space available for the datastore.
■
Resolve any configuration incompatibilities.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2849
Message: Restore failed due to failure to delete the virtual machine snapshot
Explanation: The restore operation failed due to an error during the delete virtual
machine snapshot operation.
Recommended Action: Do the following:
■
Check that the VMware server has sufficient permissions to delete a virtual
machine snapshot.
■
Increase the space available for the datastore.
■
Error or task cancellation on the VMware server.
For additional information, check the job details in the Activity Monitor, the bprd log
on the master server, and the bptm log on the media server.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2850
Message: Restore error
Explanation: An error caused the restore to fail.
Recommended Action: Try the following possible solutions in the order presented:
402
NetBackup status codes
NetBackup status codes
■
Ensure that the client server list contains entries for the master server and any
media servers that can be used during a backup or restore.
■
Examine the status or the progress log on the client for messages on why the
restore failed. Also, check the All Log Entries report on the server.
■
Check ownership and permission on directories where files are restored.
■
Correct the problems that you find and retry the restore.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2864
Message: The disaster recovery package could not be imported.
Explanation: The operation was not successful because the disaster recovery
package was corrupt.
Recommended Action: Ensure that you are using the disaster recovery package
that was emailed to you or a copy of the same package.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2865
Message: The database table could not be loaded.
Explanation: The operation was not successful because the host identity could
not be restored in the NetBackup database.
Recommended Action: Ensure that the NetBackup database is accessible while
the NetBackup database process is running. Use the following command to check
if the database is accessible:
■
On UNIX: /usr/openv/db/bin/nbdb_ping
■
On Windows: install_path\NetBackup\bin\nbdb_ping
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 2866
Message: The specified passphrase is incorrect.
Explanation: The operation was not successful, because the passphrase does
not match the one that was set at the time of the catalog backup.
403
NetBackup status codes
NetBackup status codes
Recommended Action: Ensure that the specified passphrase is the same as the
one that you set at the time of the catalog backup that is associated with this disaster
recovery package.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4200
Message: Operation failed: Unable to acquire snapshot lock
Explanation: The snapshot is being accessed by another operation such as a
restore, browse, or copy to storage unit.
Recommended Action: Retry the operation when the snapshot is no longer used
by another operation.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4201
Message: Incorrect snapshot method configuration or snapshot method not
compatible for protecting backup selection entries
Explanation: The policy uses an incorrect snapshot method, or the prerequisite
for this snapshot method is not configured properly.
Recommended Action: Verify the following:
■
The required correct storage array credential for the snapshot method (wherever
applicable) is configured in NetBackup.
■
The required software for the snapshot method is configured correctly on the
client.
■
You can choose the snapshot method to protect the entries of the backup
selection (for example, file system).
■
The entries that are specified in the backup selection are compatible with the
snapshot method configured in the policy.
See the NetBackup Snapshot Client Administration Guide for more information
about configuring a snapshot method.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
404
NetBackup status codes
NetBackup status codes
NetBackup status code: 4202
Message: Invalid or incompatible storage unit configured
Explanation: Invalid or incorrect storage destination configured for this policy.
Recommended Action: Verify the following:
■
The storage destination that is used for the policy is compatible. For example,
the snapshot method OST_FIM operates only on an SLP configured as storage
destination.
■
The configuration parameter that was provided for the snapshot method is
correct. For example, verify that the snapshot resources are correct and the
configuration parameters for the configured snapshot method are correct.
■
You can choose the snapshot method to protect the entries of the backup
selection (for example, file system).
See the NetBackup Snapshot Client Administration Guide for more information
about configuring a snapshot method.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4203
Message: Invalid or unsupported backup selection filelist
Explanation: Incompatible entry found in backup selection for the configured
snapshot method.
Recommended Action: Verify the following:
■
The entries that are given in the backup selection can be protected by the
snapshot method. For example, a file system that was created on top of an HP
EVA disk cannot be protected using the snapshot method for IBM.
■
The volume is mounted on the specified path for NAS volumes (NFS mount
points or CIFS share).
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4204
Message: Incompatible client found
Explanation: Invalid user on client or incompatible client found.
Recommended Action: Verify the following:
405
NetBackup status codes
NetBackup status codes
■
You have logged into the client with the same domain-user as the one registered
with the NetBackup client service.
■
The primary client and target or remote client are compatible.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4205
Message: Incorrect or no credentials found
Explanation: Either NetBackup cannot find the supporting software for the
configured snapshot method or invalid credentials have been supplied.
Recommended Action: Verify the following:
■
If you created an NDMP policy or configured an NAS Data Mover, check that
the NDMP host is configured with the correct credentials.
■
The disk array host or storage server credentials are correct.
■
The third party software or supporting software that is required by the configured
snapshot method is installed on the client.
See the NetBackup Snapshot Client Administration Guide for more information
about snapshot methods.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4206
Message: Authentication error occurred. NetBackup Client Service is running as
Local System, this is likely incorrect.
Explanation: None of the backup selections are accessible and the NetBackup
Client Service is running as Local System. These conditions indicate that you may
not have credentials to access the storage server.
Recommended Action: Update the NetBackup Client Service in the Windows
services to use the proper credentials that allow access to the storage server.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4207
Message: Could not fetch snapshot metadata or state files
406
NetBackup status codes
NetBackup status codes
Explanation: Snapshot metadata that the NetBackup client requires is missing or
cannot be fetched from the NetBackup master server.
Recommended Action: Verify the following:
■
The NetBackup client can communicate with the NetBackup master.
■
The state file location on the NetBackup client has write permission. The typical
location of the NetBackup state file on the NetBackup client is as follows:
Windows: C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\
UNIX: /usr/openv/netbackup/online_util/fi_cntl
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4208
Message: Could not send snapshot metadata or statefiles
Explanation: Snapshot metadata that is created by the client cannot be transferred
on the master server.
Recommended Action: Verify the following:
■
The NetBackup client can communicate with the NetBackup master.
■
The state file location on the NetBackup client has write permission. The typical
location of the NetBackup state file on the NetBackup client is as follows:
Windows: C:\Program Files\Veritas\NetBackup\db\snapshot\<client>
UNIX: /usr/openv/netbackup/db/snapshot/<client>
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4209
Message: Snapshot metadata or statefiles cannot be created
Explanation: Not able to create snapshot metadata.
Recommended Action: Verify the following:
■
The logs contain a failure that precedes this error which restricts the creation
of metadata content.
■
The state file location on the NetBackup client has write permission. The typical
location of the NetBackup state file on the NetBackup client is as follows:
Windows: C:\Program Files\Veritas\NetBackup\db\snapshot\<client>
UNIX: /usr/openv/netbackup/db/snapshot/<client>
407
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4210
Message: Incorrect or no content found in snapshot metadata
Explanation: Incorrect or invalid content in the snapshot state files.
Recommended Action: Verify that the specified state file is present on the host.
The NetBackup state file is normally located in the following NetBackup client
directory:
■
Windows: C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\
■
UNIX: /usr/openv/netbackup/online_util/fi_cntl
Contact Veritas NetBackup support for assistance.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4211
Message: Snapshot not accessible or invalid snapshot
Explanation: The snapshot is not accessible. The target device may be mapped
to multiple host bus adapters (HBAs).
Recommended Action: Verify the following:
■
The connection between the NetBackup client and the storage management
host-array is intact.
■
The host-specific permission is enabled on the storage array.
■
The snapshot exists on the storage array or filer.
■
The snapshot target device is not mapped to multiple HBAs. If it is, unmap one
of the HBAs and continue. Support of multiple paths for a device that requires
the multi-path software.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4212
Message: Recreation of snapshot failed
Explanation: Snapshot cannot be recreated. This error can occur during snapshot
restores on a Windows platform.
408
NetBackup status codes
NetBackup status codes
Recommended Action: Verify that the restore flow of operations has succeeded.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4213
Message: Snapshot import failed
Explanation: The snapshot import operation failed, or building and enabling the
snapshot I/O stack failed.
Recommended Action: Verify the following:
■
The snapshot device is accessible on the client.
■
The client has all the required software for building the snapshot I/O stack. This
should be equivalent to the I/O stack of the primary client whose entity was
required to be protected.
■
The communication between the NetBackup client and the master server is
intact.
■
The copy-back restore target device is not mapped to multiple HBAs. If it is,
unmap one of the HBAs and continue. Support of multiple paths for a device
requires the multi-path software.
■
Make sure that the iSCSI session is established between the node and the
target.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4214
Message: Snapshot mount failed
Explanation: Unable to mount the snapshot or run the subsequent set of snapshot
operations. The user needs to make the snapshot accessible to the next set of
operations to complete a NetBackup job (for example, backup from snapshot,
indexing, restore wherever applicable).
Recommended Action: Verify the following:
■
You can use the required file system type to mount the given snapshot.
■
The required permission exists on the client to enable snapshots for reading
and traversing.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
409
NetBackup status codes
NetBackup status codes
NetBackup status code: 4215
Message: Snapshot deletion failed
Explanation: The snapshot cannot be deleted.
Recommended Action: Verify the following:
■
The snapshot exists on the storage array. It may have been deleted outside of
NetBackup.
■
The client has permission to delete the snapshot.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4216
Message: Snapshot cleanup failed
Explanation: Unable to clean up various supporting pieces for snapshot creation.
Recommended Action: Verify that you have enabled the permission to delete the
files.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4217
Message: Snapshot restore failed
Explanation: Unable to restore data from the snapshot.
Recommended Action: Verify the following:
■
The snapshot exists.
■
You have enough permission to overwrite or create files in the restore directory
or folder.
■
The communication between NetBackup and the storage array-filer is intact.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4218
Message: Snapshot deport failed
Explanation: The requested snapshot cannot be deported or masked from the
NetBackup client.
410
NetBackup status codes
NetBackup status codes
Recommended Action: Verify the following:
■
The snapshot exists.
■
The communication between NetBackup and the storage array-filer is intact.
■
The required credentials for the storage server have been supplied in NetBackup.
■
Any required software and license for the third-party software are configured.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4219
Message: Command operation failed: Third-party command or API execution failed
Explanation: Third-party command or API execution failed.
Recommended Action: Do the following:
■
From the NetBackup logs, identify the failing command or API.
■
Ensure that you have the required permission to execute these commands.
■
If possible, execute the command manually to gather more details about the
failure.
■
Check your configuration to determine the cause of the failing command or the
API.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4220
Message: Command operation failed: System command or API execution failed
Explanation: The system command or the API execution failed.
Recommended Action: Verify the following:
■
From the NetBackup logs, identify the failing command or API.
■
Take corrective actions based on the error that is reported as a result of the
command execution.
■
Ensure that you have the required permission to execute these commands.
■
If possible, execute the command manually to gather more details about the
failure.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
411
NetBackup status codes
NetBackup status codes
NetBackup status code: 4221
Message: Found an invalid or unsupported configuration
Explanation: NetBackup found an invalid or unsupported configuration.
Recommended Action: Verify the following:
■
From the NetBackup logs, identify the failing entity and its error.
■
Check the support matrix to determine the correct setup for the configuration.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4222
Message: Operation failed: Unable to acquire policy lock to take snapshot
Explanation: A policy has generated overlapping snapshot jobs. One snapshot
job is in progress for a particular policy when the same policy requests a second
snapshot job.
Recommended Action: No manual intervention is required. The NetBackup Policy
Execution Manager (PEM) retries the job based on the Job retry delay setting on
the master server. To view or set this property, go to Host Properties>Master
Server>Global Parameters. Contact NetBackup Support if you continue to get
this error and you have ensured that no overlapping snapshot jobs are in progress.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4223
Message: Operation not completed
Explanation: The user runs the nbrestorevm -ir_done command to complete
the VM Instant Recovery operation, but the VM continues to run from the NetBackup
storage. The operation cannot be completed because Storage vMotion may be
running or not started.
Recommended Action: Make sure that Storage vMotion is completed and that
you move the VM from NetBackup storage to the production datastore.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4224
Message: STS Internal Error
412
NetBackup status codes
NetBackup status codes
Explanation: One of the following has occurred inside the STS plug-in:
■
Insufficient system memory in the client or the storage server.
■
Storage server busy.
■
An invalid request was received in the communication between the storage
server and the STS plug-in.
Recommended Action: Please contact Veritas Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4225
Message: Unauthorized operation attempted by client or media on storage server
Explanation: The storage server received an unauthorized request or did not
identify the host.
Recommended Action: Verify the following:
■
Valid storage server credentials are configured.
■
The client has the required privileges per the vendor specification. Please refer
to the NetBackup Replication Director Solutions Guide for more details.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4226
Message: Communication failure occurred with storage server
Explanation: NetBackup cannot communicate with the storage server or a protocol
failure has occurred with the storage server.
Recommended Action: Verify the following:
■
The appropriate storage server services are running.
■
The client and the media server can communicate with the storage server.
■
The client and the media server can resolve the storage server name.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4227
Message: STS Plug-in error occurred
413
NetBackup status codes
NetBackup status codes
Explanation: The STS plug-in framework is not working.
One of the following has occurred:
■
A required STS library cannot be loaded or initialized.
■
An invalid plug-in operation is attempted.
Recommended Action: Please contact Veritas Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4228
Message: Storage server or plug-in version mismatch
Explanation: The STS plug-in framework encountered an incompatible storage
server version.
Recommended Action: Verify that the client and the media server support the
version of the storage server.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4229
Message: Insufficient resources or capabilities found by storage server
Explanation: The storage server does not have sufficient resources or capabilities
available. For example, not enough space exists on the storage that the storage
server manages. Also, appropriate feature licenses are not enabled on the storage
server.
Recommended Action: Verify the following:
■
The storage server recognizes the identified device from the backup selection.
■
The required features are enabled on the storage.
■
The required feature licenses are applied on the storage.
■
The storage server has sufficient available storage space for NetBackup triggered
snapshots.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4230
Message: Invalid storage topology or storage server configuration error
414
NetBackup status codes
NetBackup status codes
Explanation: An invalid configuration causes the STS Plug-in to fail. Examples of
this failure include an invalid topology configuration, storage configuration, or server
configuration.
Recommended Action: Do the following:
■
Verify that the storage is correctly configured per the vendor specification.
■
Verify that the underlying storage supports the topology that is specified in the
storage lifecycle policy.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4231
Message: STS Unexpected Error
Explanation: The STS Plug-in failed with an unexpected error.
Recommended Action: Please contact Veritas Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4232
Message: Invalid Discovery Query URI
Explanation: The query URI for the discovery policy cannot be parsed.
Recommended Action: Examine the URI using the policy editor for syntax errors.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4233
Message: BIOS UUID client reference not allowed for vCloud
Explanation: Use of BIOS UUID as a client reference is not allowed for vCloud
because they are not unique.
Recommended Action: Select another form of client reference for the policy,
possibly instance UUID.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
415
NetBackup status codes
NetBackup status codes
NetBackup status code: 4234
Message: VMware server login failure
Explanation: The configured user name, password, and port do not allow login to
the server.
Recommended Action: Correct the credentials that are configured for the
designated server.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4235
Message: vCloud keyword used when vCloud not enabled
Explanation: The policy uses a vCloud related keyword, but a vCloud server
credential is not configured.
Recommended Action: Configure a vCloud director credential, or remove any
vCloud related keywords from the policy query.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4236
Message: vCloud policy includes multiple organizations
Explanation: Executing the query for the policy selected VMs from multiple vCloud
organizations and this has not been enabled in the policy.
Recommended Action: Correct the policy query to select only VMs from a single
organization, or change the policy to enable VMs from multiple organizations.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4237
Message: Client does not meet policy requirements
Explanation: The VM cannot be backed up because it does not meet the
requirements for the selected client reference.
Recommended Action: Modify the VM to meet the requirements for the configured
client reference, or change the policy to use a different client reference.
416
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4238
Message: No server credentials configured for policy
Explanation: The discovery policy requires credentials for a server to execute the
policy.
Recommended Action: Verify that the appropriate server credentials have been
entered for the type of discovery policy.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4239
Message: Unable to find the virtual machine
Explanation: Possible causes of this error:
■
The virtual machine name is not entered correctly (for example, the name is
misspelled).
■
The virtual machine identifier type is not selected correctly for the policy. For
example, the virtual machine display name is entered, but the virtual machine
identifier for the policy indicates virtual machine host name.
■
The virtual machine is renamed, deleted, or moved.
Recommended Action: Verify the following:
■
The virtual machine identifier configured for the policy and the name (display
name, host name, UUID) entered for the virtual machine on the policy agree.
■
You can view the virtual machine in the VMware user interface.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4240
Message: Operation not supported
Explanation: A likely cause is a Veritas programming error.
Recommended Action: Please contact Veritas Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
417
NetBackup status codes
NetBackup status codes
NetBackup status code: 4243
Message: Unable to connect to the VirtualCenter server
Explanation: The connection to the VirtualCenter server cannot be made. Possible
causes of this error:
■
If there are too many VM snapshot jobs that are started using the same
VirtualCenter server, the VirtualCenter server connection limit is exceeded.
■
There is an intermittent network connection between the VMware backup host
and the VirtualCenter server.
Recommended Action: If there are too many VM snapshot jobs, limit the VM jobs
using the VMware Resource Limit to limit the concurrent jobs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4245
Message: Invalid pathname for backup selection
Explanation: NDMP pathname for NetApp clustered Data ONTAP is expected
with the format /vserver_name/vol_name.
Recommended Action: The IP address cannot be used in the pathname.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4246
Message: The requested operation was partially successful.
Explanation: Potential causes of this error are:
■
Not all backup selections apply to all selected clients
■
The backup selection refers to an invalid volume name
■
The backup selection refers to a directory
Recommended Action: Do the following:
■
Create a separate policy for each client
■
Specify the correct volume name for the Vserver
■
Specify a volume name and not a directory within a volume
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
418
NetBackup status codes
NetBackup status codes
NetBackup status code: 4247
Message: Index from snapshot for Replication Director NDMP Policy is not
supported on AIX media server
Explanation: Index from the snapshot for Replication Director NDMP Policy is
supported only on Linux, Windows, HP-UX, and the Solaris media server.
Recommended Action: Please associate a supported media server other than
the AIX media server for the storage unit referred to in the SLP against the index
from the snapshot operation.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4248
Message: Index from snapshot operation failed with an internal error
Explanation: Index from snapshot operation failed with an internal error.
Recommended Action: Check the NetBackup administration logs for more details.
Ensure that there is enough space on the media server to create the index database.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4249
Message: Index from snapshot operation failed, catalog already exists
Explanation: Index from snapshot operation fails when there already is a full
catalog created for the given source image.
Recommended Action: Check that there is no existing catalog for the specified
source image. Check the NetBackup administration logs for more details.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4250
Message: Index from snapshot operation failed, unable to find child image or file
information
Explanation: Index from snapshot operation failed. No child images found for the
backup ID that needs to be indexed.
Recommended Action: Check the NetBackup administration logs for more details.
419
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4251
Message: Index from snapshot operation failed. Failed to write into index database.
Explanation: Error occurred on media server while writing into index database.
Recommended Action: Typically, the index database is created under
NB_INSTALL_DIR/tmp; for example, /usr/openv/netbackup/tmp. It can be
overridden by SNAPDIFF_DB_PATH in the NetBackup configuration file. Ensure
that there is enough space on the media server to create the index database. Check
the NetBackup administration logs for more details.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4252
Message: Index from snapshot operation failed. Entry does not belong to any of
the backup selection entries.
Explanation: The file entry going to be indexed does not belong to any of the
backup selection entries.
Recommended Action: Check the NetBackup administration logs for more details.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4253
Message: Index from snapshot operation failed. SLP version mismatch for current
and previous backup image.
Explanation: Index from snapshot operation failed. There is an SLP version
mismatch for the current and previous backup image.
Recommended Action: Check the NetBackup administration logs for more details.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4254
Message: Invalid or no path found to create index database
420
NetBackup status codes
NetBackup status codes
Explanation: There is an invalid path or no path to create the index database.
This path is required to create an index database in an index from snapshot
operation.
Recommended Action: Typically, the index database is created under
NB_INSTALL_DIR/tmp; for example, /usr/openv/netbackup/tmp. It can be
overridden by adding SNAPDIFF_DB_PATH in the NetBackup configuration. Check
if the defined path exists.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4255
Message: Index from snapshot using SnapDiff is disabled by the user
Explanation: The user can disable the index from snapshot operation by using
SnapDiff through the NetBackup configuration key USE_SNAPDIFF. If the value
of the key is set to 0, then the index from the snapshot operation using SnapDiff is
disabled.
Recommended Action: To enable the index from snapshot by using SnapDiff,
change the value of the NetBackup configuration key USE_SNAPDIFF by using
the bpsetconfig CLI. The possible values of the key are as follows:
■
Set to 0; do not perform the index from snapshot operation by using SnapDiff.
■
Set to 1; the index from snapshot by using SnapDiff is enabled only for the
incremental schedule.
■
Set to 2; the index from snapshot by using SnapDiff is enabled for all schedule
types.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4256
Message: Index from snapshot is not supported for the file system associated with
backup selection
Explanation: The index from snapshot is not supported for the file system
associated with one of the backup selection entries.
Recommended Action: Currently, the index from the snapshot operation using
SnapDiff is supported for NFS, CIFS file systems. It is also supported when the
policy type is NDMP. Change the policy with the backup selection entries that have
a file system that is supported for the index from snapshot operations by using
SnapDiff.
421
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4257
Message: Index from snapshot is not supported for the storage server
Explanation: Index from snapshot using SnapDiff is not supported for the storage
server that is used for snapshot creation.
Recommended Action: Please check that the index from snapshot using SnapDiff
is supported for the storage server. If it is not, then change the SLP with the STU
associated with the storage server having support for index from snapshot using
SnapDiff.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4258
Message: Transient error encountered while taking Hyper-V VM snapshot
Explanation: The Hyper-V VSS writer experienced a transient error. VM might be
moving or doing another conflicting operation. If the backup process is retried, the
error may not reoccur.
Recommended Action: Check the event log for Hyper-V VMMS (Log Name:
Microsoft-Windows-Hyper-V-VMMS/Admin) for more information.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4259
Message: Failed to find VirtualCenter host name in VMware Lookup Service
Explanation: The Platform Services Controller system name for the vCenter cannot
be resolved to the NetBackup virtual machine server name for a vCenter.
Recommended Action: Use the system name as configured in the Platform
Services Controller as the NetBackup virtual machine server name.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4260
Message: Encountered SSO login failure
422
NetBackup status codes
NetBackup status codes
Explanation: Login failed when attempting to log on to the VMware Single Sign-On
service.
Recommended Action: Ensure that the credentials that you entered for the
NetBackup virtual machine server are authorized for Single Sign-On.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4261
Message: Encountered VMware Internal Server Error
Explanation: This message indicates a generic VMware Internal Server Error. A
known cause of this error is when the Tags or Categories that are defined in the
vCenter do not have a Description.
Recommended Action: Refer to the details that are given in the error message
and the related VMware Knowledge Base article. Check the NetBackup VxUL logs
(libvcloudsuite).
Related VMware Knowledge Base article: http://kb.vmware.com/kb/2124204
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4262
Message: Encountered VMware vCloud Suite API failure
Explanation: This message indicates a generic VMware API failure. A known
cause of this error is when NetBackup master servers or other hosts that perform
automatic virtual machine selection do not have network connectivity to the VMware
Platform Services Controller.
Recommended Action: Refer to the VMware vCenter Server 6.0 Deployment
Guide and the related VMware Knowledge Base article.
Related VMware Knowledge Base article: http://kb.vmware.com/kb/2106283
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4263
Message: Encountered VMware SOAP API failure
Explanation: This message indicates an error when NetBackup attempted to
connect to the VMware Single Sign-On service. A known cause of this error is when
423
NetBackup status codes
NetBackup status codes
the clock settings are different between the NetBackup host that is used for virtual
machine selection and the vCenter.
Recommended Action: Refer to the details that are given in the error message
and the related VMware Knowledge Base article. Check the NetBackup VxUL logs
(libvcloudsuite).
VMware Knowledge Base article: http://kb.vmware.com/kb/2125193
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4264
Message: Encountered unexpected error while processing TagView XML
Explanation: This message indicates that the XML file containing the VMware
Tag information is corrupt.
Recommended Action: If the error is from a test query, try the operation again.
If the parent (Discovery) job fails, try the job again with a Reuse VMware selection
query results value of 0 in the failing policy clients tab to regenerate the XML file.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4265
Message: Encountered a VMware Virtual Machine Server that does not support
Tags
Explanation: This message indicates that an ESX server is included in the Virtual
Machine Server list, which does not support Tags.
Recommended Action: Refer to the NetBackup for VMware Administrator's Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4266
Message: Encountered a VMware Virtual Machine Server that does not offer Tag
APIs
Explanation: This message indicates that a 5.1 or 5.5 vCenter is included in the
Virtual Machine Server list, which does not offer VMware Tag APIs.
Recommended Action: Refer to the NetBackup for VMware Administrator's Guide.
424
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4267
Message: Failed to initialize Java Runtime Environment
Explanation: This error message indicates that NetBackup cannot find the Java
Runtime Environment that is required to access the VMware Tag information.
Recommended Action: Install the version of the NetBackup Remote Administration
Console that corresponds to the NetBackup Client installation. The version of the
NetBackup Remote Administration Console must match the NetBackup Client
version.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4268
Message: Failed to retrieve resource pool information
Explanation: NetBackup was not able to retrieve resource pool properties from
vSphere.
Recommended Action: Check the resource pool path. If it is incorrect, specify
the correct resource pool path that exists in destination vCenter server.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4269
Message: Found multiple virtual machines with same identity
Explanation: Multiple virtual machines with the same display name exist under
the destination resource pool or vApp. NetBackup cannot identify the virtual machine
that needs to be overwritten.
Recommended Action: Select a different display name for restore or rename the
virtual machines in the destination resource pool or vApp. Only one virtual machine
with the same display name can exist in the resource pool or vApp.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
425
NetBackup status codes
NetBackup status codes
NetBackup status code: 4270
Message: A snapshot of the virtual machine exists and the policy option specifies
aborting the backup
Explanation: The virtual machine being backed up already has an existing snapshot
and the backup policy requires that NetBackup abort the backup in this circumstance.
Recommended Action: Either remove the snapshot and restart the backup job
or modify the policy to ignore or remove existing snapshots. NetBackup removes
existing snapshots only if NetBackup created them.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4271
Message: Maximum virtual machine snapshots exceeded
Explanation: NetBackup was unable to remove an existing virtual machine
snapshot because more than the maximum allowed number of snapshots exist on
the virtual machine.
Recommended Action: Remove the virtual machine's snapshots and restart the
backup job.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4272
Message: Maximum delta files exceeded
Explanation: One of the virtual machine’s disks had more than the maximum
allowed number of delta files. Therefore, NetBackup was unable to create a virtual
machine snapshot.
Recommended Action: Consolidate the virtual machine’s disks and restart the
backup job.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4273
Message: Unable to lock the backup or restore host for virtual machine snapshot
operations
426
NetBackup status codes
NetBackup status codes
Explanation: NetBackup was configured to serialize the virtual machine snapshot
operations on the backup or restore host. However, NetBackup was unable to
acquire the lock that controls snapshot serialization within the allowed time.
Recommended Action: Restart the backup job when no other virtual machine
snapshot operations are in process. If NetBackup cannot acquire the lock frequently,
adjust the NetBackup job configuration as necessary to allow the virtual machine
snapshots to run at different times or to run on different hosts. Alternatively,
reconfigure NetBackup so that the snapshot serialization is not required.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4274
Message: Failed to remove virtual machine snapshot
Explanation: NetBackup was unable to remove a virtual machine snapshot.
Recommended Action: Delete the virtual machine snapshot manually.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4275
Message: Unable to consolidate Virtual Machine Disks
Explanation: NetBackup was unable to consolidate a virtual machine's disks.
NetBackup tries to consolidate disks as follows:
■
Before a virtual machine snapshot is created at the start of a virtual machine
backup.
■
After a virtual machine snapshot is deleted while the backup nears completion.
Recommended Action: Consolidate the virtual machine’s disks manually and
restart the job.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4276
Message: Unable to retrieve Virtual Machine Disk information
Explanation: NetBackup was unable to retrieve a virtual machine’s disk information.
427
NetBackup status codes
NetBackup status codes
Recommended Action: Review the job details and the bpfis log for any additional
information that is related to the error. Correct the underlying issues that cause the
failure and restart the job.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4277
Message: Virtual machine path contains unsupported characters
Explanation: The virtual machine path contains the characters that NetBackup
does not support.
Recommended Action: Rename the virtual machine and/or folder path to one
that contains only supported characters.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4278
Message: Unable to retrieve virtual machine information
Explanation: NetBackup was unable to retrieve a virtual machine’s information.
Recommended Action: Review the job details and the bpfis log for any additional
information that is related to the error. Correct the underlying issues that cause the
failure and restart the job.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4279
Message: Unable to retrieve virtual machine vCloud information
Explanation: NetBackup was unable to retrieve a virtual machine’s vCloud
information.
Recommended Action: Review the job details and the bpfis log for any additional
information that is related to the error. Correct the underlying issues that caused
the failure and restart the job.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
428
NetBackup status codes
NetBackup status codes
NetBackup status code: 4280
Message: Virtual machine contains independent and Raw Device Mapping disks
only
Explanation: The virtual machine included only independent disks and the Raw
Device Mapping disks, so NetBackup found no data to protect.
Recommended Action: Remove the virtual machine from the backup policy
selection or modify the virtual machine to include additional disks.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4281
Message: Virtual machine contains independent disks only
Explanation: The virtual machine included only independent disks, so NetBackup
found no data to protect.
Recommended Action: Remove the virtual machine from the backup policy
selection or modify the virtual machine to include additional disks.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4282
Message: Virtual machine contains Raw Device Mapping disks only
Explanation: The virtual machine included only Raw Device Mapping disks, so
NetBackup found no data to protect.
Recommended Action: Remove the virtual machine from the backup policy
selection or modify the virtual machine to include additional disks.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4283
Message: Error detected while processing disk identifiers
Explanation: NetBackup encountered more than one Virtual Machine Disk with
the same UUID.
Recommended Action: Modify the virtual machine so that none of the UUIDs for
its disks duplicate the UUID for any other virtual machine.
429
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4287
Message: A NetBackup snapshot of the virtual machine exists and the policy option
specifies aborting the backup
Explanation: One or more NetBackup created snapshots exist on the virtual
machine and the Existing snapshot handling option in the policy specifies aborting
the backup. The snapshots that NetBackup creates start with the NBU_SNAPSHOT
or NBU_RESTORE strings in the snapshot name.
Possible causes of an existing NetBackup snapshot are the following:
■
A snapshot from a previous backup has not been deleted (an orphaned
snapshot). NetBackup should have deleted the snapshot when the backup
completed.
■
Two policies try to back up the virtual machine at the same time. The backup
for one of the policies detects the snapshot that the other policy created.
Recommended Action: Do the following, as appropriate:
■
Manually remove the orphaned snapshot.
For VMware, you can use the VMware vSphere interface to remove virtual
machine snapshots. For Hyper-V, you can use nbhypervtool.exe to remove
NetBackup snapshots that were created with the WMI backup method. For more
information on nbhypervtool.exe, refer to the NetBackup Commands Reference
Guide.
■
Reduce the likelihood of orphaned snapshots by changing the resource limits
to reduce the load on the appropriate VMware or Hyper-V resource. The
Resource Limit dialog is in the NetBackup Administration Console under
Host Properties > Master Servers. The NetBackup guides for VMware and
Hyper-V describe the available settings.
■
Change the NetBackup policy schedules to avoid simultaneous backups of the
virtual machine.
■
For VMware only: Change the NetBackup policy's Existing snapshot handling
parameter to a different option (such as Continue Backup).
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
430
NetBackup status codes
NetBackup status codes
NetBackup status code: 4290
Message: Failed to create virtual machine snapshot. Virtual machine is busy
performing another operation.
Explanation: A virtual machine snapshot cannot be created because the virtual
machine is performing another operation that conflicts with the snapshot creation
process. This usually happens if the virtual machine is undergoing a storage
migration or a live migration.
Recommended Action: Retry the snapshot job after the virtual machine has
completed the conflicting operation.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 4293
Message: Invalid credentials or an access violation
Explanation: The credentials that were provided while accessing the host/server
are invalid or the host/server denied the access. The requested operation cannot
be completed.
Recommended Action: Verify that there are valid credentials configured for the
host/server that is being accessed and that the user has valid privileges to make
the request.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5400
Message: Backup error - None of the request objects were found in the database
Explanation: The backup selection list did not contain any objects that were found
in the database. An object can either be a data file or a tablespace.
Recommended Action: Check the backup selection list. Add the objects that are
part of the database or remove the database instance from the policy.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5401
Message: Backup error - FRA (Fast Recovery Area) was requested, but it was
not found in the database
431
NetBackup status codes
NetBackup status codes
Explanation: The backup request was for the FRA, but the FRA was not found in
the database.
Recommended Action: Add an FRA area to the database or remove the database
instance from the policy.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5402
Message: OS Authentication error - Could not connect to the database. Please
check the OS credentials
Explanation: A connection to the database cannot be established using the
operating system credentials provided.
Recommended Action: Confirm that the credentials are properly set. On Windows,
you may need to replace a process level token. First, select Start>Control
Panel>Administrative Tools>Local Security Policy. Then, expand Local Policies
in the left pane, click User Rights Assignment, and double-click Replace a process
level token in the right pane. Add the user you want to run the client policies as.
Restart the server for this right to take effect.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5403
Message: Oracle Authentication error - Could not connect to the database. Please
check the Oracle credentials
Explanation: A connection to the database cannot be established using the Oracle
database credentials that are provided.
Recommended Action: Confirm that the credentials are properly set.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5404
Message: ASM validation error - PROXY backup is not supported for ASM
Explanation: The backup request was for a PROXY type of backup. Automatic
Storage Management (ASM) was found. Proxy backups are not supported with
ASM.
432
NetBackup status codes
NetBackup status codes
Recommended Action: Move the database to non-ASM storage or remove the
database instance from the policy.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5405
Message: Recovery Catalog Authentication error - Could not connect to the
Recovery Catalog. Please check the Recovery Catalog credentials.
Explanation: A connection to the Recovery Catalog database cannot be established
using the Recovery Catalog credentials provided.
Recommended Action: Confirm that the Recovery Catalog credentials are properly
set.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5406
Message: Archive log only backup requested, but database is not in ARCHIVELOG
Mode
Explanation: The requested operation requires that the database archive log mode
to be set to ARCHIVELOG mode or MANUAL mode.
Recommended Action: Confirm that the database archive log mode is properly
set to either ARCHIVELOG or MANUAL.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5407
Message: Database is in the wrong state (must be OPEN) for the requested action
Explanation: The requested operation requires that the database be in an OPEN
mode.
Recommended Action: Confirm that the database mode is set to OPEN. Possible
Oracle commands startup, startup open read only, or startup open.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
433
NetBackup status codes
NetBackup status codes
NetBackup status code: 5408
Message: OS Authentication error - Could not find credentials. If this instance is
part of an instance group, make sure that the group has the credentials that match
this OS Type
Explanation: The credentials that are needed to connect to the instance cannot
be found.
Recommended Action: If the instance is on a UNIX client, make sure that its
instance group contains UNIX credentials. If the instance is on a Windows client,
make sure that its instance group contains Windows credentials.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5409
Message: Cloning is NOT supported for this client platform
Explanation: The platform that runs on this client does not support the Guided
Recovery cloning operation.
Recommended Action: Refer to the release notes or the NetBackup Master
Compatibility List for the supported platforms for the cloning feature at the following
URL:
http://www.netbackup.com/compatibility
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5410
Message: Oracle Intelligent Policy is NOT supported for this client platform
Explanation: The platform that runs on this client does not support the Oracle
Intelligent Policy feature.
Recommended Action: Refer to the release notes or the NetBackup Master
Compatibility List for the supported platforms for this feature at the following URL:
http://www.netbackup.com/compatibility
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5411
Message: Cannot do a hot backup of a database in NOARCHIVELOG mode
434
NetBackup status codes
NetBackup status codes
Explanation: The requested operation requires the database archive log mode to
be set to ARCHIVELOG mode.
Recommended Action: Confirm that the database archive log mode is properly
set to ARCHIVELOG or change to an offline (cold) database backup.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5412
Message: Database is in the wrong state (must be OPEN or MOUNTED) for an
Archive Log Backup
Explanation: An Oracle policy requests an archive log backup, but the database
is not in an OPEN or MOUNTED state.
Recommended Action: Put the database in an OPEN or MOUNTED state and
retry the backup.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5413
Message: Database is in the wrong state (must be OPEN or MOUNTED) for an
FRA backup
Explanation: An Oracle policy requests a Fast Recovery Area (FRA) backup, but
the database is not in an OPEN or MOUNTED state.
Recommended Action: Put the database in an OPEN or MOUNTED state and
retry the backup.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5414
Message: The requested operation is not supported with this client version
Explanation: The requested operation is not supported by this version of the
NetBackup Client service.
Recommended Action: Upgrade the NetBackup Client service to enable this
operation.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
435
NetBackup status codes
NetBackup status codes
NetBackup status code: 5415
Message: Cannot shut down read-only standby database
Explanation: NetBackup does not perform a cold backup on a standby database
that is in read-only mode.
Recommended Action: Do not select the cold database backup option on the
Oracle tab of the policy.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5416
Message: Oracle cannot resolve the TNS connection identifier
Explanation: Oracle cannot resolve the TNS connection ID, so NetBackup doesn't
know which database to connect to.
Recommended Action: Verify the following:
■
The correct TNS identifier.
■
The correctly configured tnsnames.ora file.
■
The correct path for the TNS_ADMIN environment variable.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5417
Message: An error has occurred checking if the NFS server is an appliance.
Explanation: NetBackup cannot verify that the database backup share is on an
appliance.
Recommended Action: Verify that the database backup share is exported from
a NetBackup appliance.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5418
Message: The NFS server is not an appliance.
Explanation: The database backup share is not located on an appliance.
436
NetBackup status codes
NetBackup status codes
Recommended Action: Verify that the database backup share is exported from
a NetBackup appliance.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5419
Message: The database backup share directory is not available on the appliance.
Explanation: NetBackup cannot access the database backup share directory on
the appliance.
Recommended Action: Verify that the database backup share directory exists
on the NetBackup appliance.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5420
Message: Whole Database - Datafile Copy Share selection is not supported for
this client platform.
Explanation: Snapshot Client is not supported on this platform so we cannot
support it for the Whole Database - Datafile Copy Share selection.
Recommended Action: Back up the database using a different method.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5421
Message: None of the requested pluggable databases were found.
Explanation: The backup request for the database was for a specific list of
pluggable databases. This list of pluggable databases was verified in the database
and none of the requested pluggable databases were found in the database.
Recommended Action: Check the detailed status of the associated jobs in the
activity monitor for more information. Confirm the list of the pluggable databases
that are specified in the Oracle Intelligent Policy are correct and in the requested
database. Update the list of pluggable databases in policy. If the pluggable
databases were specified using the command line, please confirm their spelling.
Retry the backup once the updates are complete.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
437
NetBackup status codes
NetBackup status codes
NetBackup status code: 5422
Message: Partial success - one or more of the requested pluggable databases
were not found.
Explanation: The backup request for the database was for a specific list of
pluggable databases. This list of pluggable databases was verified in the database
and one or more of the requested pluggable databases were not found in the
database. The databases found were backed up.
Recommended Action: Check the detailed status of the associated jobs in the
activity monitor for more information. Confirm the list of pluggable databases that
are specified in the Oracle Intelligent Policy are correct and in the requested
database. Update the list of pluggable databases in policy. If the pluggable
databases were specified using the command line, please confirm their spelling.
Retry the backup once the updates are complete.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5423
Message: None of the requested tablespaces were found in the requested
pluggable databases.
Explanation: The backup request for the database was for specific lists of pluggable
databases and tablespaces. These lists were verified in the database and none of
the requested tablespaces were found in any of the requested pluggable databases.
Recommended Action: Check the detailed status of the associated jobs in the
activity monitor for more information. Confirm the list of tablespaces that are specified
in the Oracle Intelligent Policy are correct and in the requested pluggable databases.
Update the lists, where applicable, in policy. If the pluggable databases or
tablespaces were specified using the command line, please confirm their spelling.
Retry the backup once the updates are complete.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5424
Message: Partial success - one or more of the requested pluggable databases
did not contain any of the requested tablespaces.
Explanation: The backup request for the database was for specific lists of pluggable
databases and tablespaces. These lists were verified in the database and one or
more of the requested pluggable databases did not contain any of the requested
438
NetBackup status codes
NetBackup status codes
tablespaces. The tablespaces that were found in the pluggable databases were
backed up.
Recommended Action: Check the detailed status of the associated jobs in the
activity monitor for more information. Confirm the list of tablespaces that are specified
in the Oracle Intelligent Policy are correct and in the requested pluggable databases.
Update the lists, where applicable, in policy. If the pluggable databases or
tablespaces were specified using the command line, please confirm their spelling.
Retry the backup once the updates are complete.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5425
Message: None of the requested data files were found in the requested pluggable
databases.
Explanation: The backup request for the database was for specific lists of pluggable
databases and data files. These lists were verified in the database and none of the
requested data files were found in any of the requested pluggable databases.
Recommended Action: Check the detailed status of the associated jobs in the
activity monitor for more information. Confirm the list of data files that are specified
in the Oracle Intelligent Policy are correct and in the requested pluggable databases.
Update the lists, where applicable, in policy. If the pluggable databases or data files
were specified using the command line, please confirm their spelling. Retry the
backup once the updates are complete.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5426
Message: Partial success - one or more of the requested pluggable databases
did not contain any of the requested data files.
Explanation: The backup request for the database was for specific lists of pluggable
databases and data files. These lists were verified in the database and one or more
of the requested pluggable databases did not contain any of the requested data
files. The data files that were found in the pluggable databases were backed up.
Recommended Action: Check the detailed status of the associated jobs in the
activity monitor for more information. Confirm the list of data files that are specified
in the Oracle Intelligent Policy are correct and in the requested pluggable databases.
Update the lists, where applicable, in policy. If the pluggable databases or data files
439
NetBackup status codes
NetBackup status codes
were specified using the command line, please confirm their spelling. Retry the
backup once the updates are complete.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5427
Message: Partial success - more than one error was encountered, please refer to
the Detailed Status tab in the Job Details and review logs for more information.
Explanation: Multiple errors were encountered while the request was processed.
Some items were successfully processed. The database objects (pluggable
database, tablespace, and data files) that were successful are contained in the
backup.
Recommended Action: Check the detailed status of the associated jobs in the
activity monitor for more information on the errors. Depending on the errors, make
the appropriate changes to the policy. Retry the backup once the updates are
complete.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5428
Message: No database backup shares were found.
Explanation: No database backup shares were found during backup.
Recommended Action: Configure the appliance database backup share and then
backup the files to the share using the database vendor’s tools. NetBackup does
not retry this job after failure.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5429
Message: No new files or files that are related to the instance or database were
found in the database backup share.
Explanation: No new files or files that are related to the instance or databases
(configured in the OIP) found in the database backup share.
Recommended Action: Make sure that a backup is on the database backup share
before the policy is executed. If the policy contained an incremental schedule, then
440
NetBackup status codes
NetBackup status codes
verify that the database backup share contained new files. NetBackup does not
retry this job after failure.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5430
Message: Database must be in ARCHIVELOG mode to perform a cold backup of a
pluggable database.
Explanation: A cold backup of a pluggable database was requested. This
configuration is not an Oracle supported environment. The database must be in
ARCHIVELOG mode to perform a cold backup of a pluggable database.
Recommended Action: Change the database to ARCHIVELOG mode or change
the backup request from a cold backup to a hot backup. Retry the backup once the
updates are complete.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5431
Message: The requested operation did not get a response from the NetBackup
appliance.
Explanation: The requested operation did not get a response from the NetBackup
appliance within the configured timeout.
Recommended Action: The default timeout is set to 60 seconds. Configure a
new timeout on the NetBackup master server. After the timeout is configured on
the master server, confirm the NetBackup appliance is active and retry the operation.
■
On Windows: Add a registry DWORD entry that is called APPLIANCE_TIMEOUT with
a value in seconds at
HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\NetBackup\CurrentVersion\Config
■
On UNIX: Change the APPLIANCE_TIMEOUT setting in the bp.conf file
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5432
Message: The requested NetBackup appliance operation is unsuccessful.
Explanation: NetBackup sent a request to the NetBackup appliance and the
requested operation did not complete successfully.
441
NetBackup status codes
NetBackup status codes
Recommended Action: Review the NetBackup appliance error message log, the
NetBackup Appliance Troubleshooting Guide, or contact the NetBackup appliance
administrator for help.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5433
Message: The NetBackup request did not complete due to a NetBackup appliance
communication issue.
Explanation: NetBackup cannot communicate with the NetBackup appliance. This
issue can be due to network issues or the NetBackup appliance is not online.
Recommended Action: Review the NetBackup appliance error message log, the
NetBackup Appliance Troubleshooting Guide, or contact the NetBackup appliance
administrator for help.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5434
Message: Cannot validate the identity of the NetBackup appliance.
Explanation: NetBackup cannot validate the identity of the NetBackup appliance.
Recommended Action: Review the NetBackup appliance error message log, the
NetBackup Appliance Troubleshooting Guide, or contact the NetBackup appliance
administrator for help.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5435
Message: Recovery point operations (-create, -delete, or -list) must be initiated
from a master server.
Explanation: A NetBackup client does not have permission to use this nborair
-create, -delete, or -list command options. These options are run from the
master server using root user (UNIX) or administrator (Windows) access.
Recommended Action: Contact the NetBackup administrator to run the nborair
-create, -delete, or -list command options from the master server. The
NetBackup administrator must have root user (UNIX) or administrator (Windows)
access on the master server.
442
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5436
Message: No recovery point was found.
Explanation: No recovery points were found on the selected NetBackup appliance.
Recommended Action: Confirm there is a recovery point created. If there is no
recovery point, create a recovery point and retry the operation.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5437
Message: Partial success - recovery points from one or more database shares
were not found.
Explanation: NetBackup was unsuccessful in finding recovery points for one or
more database shares.
Recommended Action: Review the NetBackup debug logs (bprd, nboarir) for
more details about the error. Also, review the NetBackup appliance debug logs for
further details.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5438
Message: The requested export path information is not found.
Explanation: NetBackup was unsuccessful finding information about the requested
export path.
Recommended Action: List all recovery points and see if the requested export
path /recovery point is available. Review the NetBackup debug logs (bprd,
nboarir) for more details about the error. Also, review the NetBackup appliance
debug logs for further details.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
443
NetBackup status codes
NetBackup status codes
NetBackup status code: 5439
Message: Validation unsuccessful. The recovery point was not created from the
specified backup ID.
Explanation: The recovery point mounted at the specified path was not created
from the specified backup ID.
Recommended Action: Confirm that you requested the correct mount path. Also,
confirm that you have requested the correct backup ID in the create recovery point
process. Check with the NetBackup administrator for the correct backup ID in the
create recovery point process and system administrator for the correct export mount
path.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5440
Message: Required environment variable is not set.
Explanation: For the validate operation on Windows, the environment variable
ORACLE_HOME is required to be set.
Recommended Action: You need to set the required environment variable
ORACLE_HOME with the appropriate value and perform the validate operation again.
Review the NetBackup debug logs (nborair) for more information.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5441
Message: Attempt to open Oracle direct NFS file was unsuccessful.
Explanation: NetBackup attempted to open Oracle direct NFS file and was
unsuccessful.
Recommended Action: When NetBackup performs the validate operation on
Windows, we get the mount path that is associated with the set export path from
Oracle direct NFS file. Confirm that the correct value is set in the environment
variable ORACLE_HOME. Review the NetBackup debug logs (nborair) for more
information.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
444
NetBackup status codes
NetBackup status codes
NetBackup status code: 5442
Message: Attempt to retrieve the device information from the NFS mount path was
unsuccessful.
Explanation: The attempt to retrieve the NFS server and export path details was
unsuccessful.
Recommended Action: Confirm that the provided mount path is correct and that
the path is rightly mounted (UNIX) or Oracle direct NFS file (Windows) has the
correct entries. Review the NetBackup debug logs (nborair) for more information.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5443
Message: Backup ID cannot be used for Oracle instant recovery.
Explanation: The specified backup ID does not contain a snapshot that can be
used for instant recovery.
Recommended Action: Use the nborair command with –list_images option to
view which images should be used for instant recovery and specify a different
backup ID.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5444
Message: The NetBackup appliance credentials retrieval was unsuccessful.
Explanation: NetBackup cannot find the credentials of the NetBackup appliance.
Recommended Action: Review the NetBackup appliance error message log, the
NetBackup Appliance Troubleshooting Guide, or contact the NetBackup appliance
administrator for help.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5445
Message: Oracle instant recovery share cannot be used for backup operations.
Explanation: Copilot instant recovery shares cannot not be used for backup
operations.
445
NetBackup status codes
NetBackup status codes
Recommended Action: A Copilot instant recovery share cannot be used in a
backup policy.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5446
Message: Partial success - backup of one or more of the requested shares
unsuccessful.
Explanation: NetBackup was unsuccessful in backing up one or more shares due
to failure or an unsupported configuration.
Recommended Action: Review the detailed status of the backup job and the
bpdbsbora debug logs.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5447
Message: Could not resolve appliance host name from IP address.
Explanation: The appliance is configured in NetBackup with its IP address.
Recommended Action: Update the NetBackup server list or media server list to
use the appliance host name.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5448
Message: Could not match the appliance to a server in the client’s server list.
Explanation: The appliance IP address did not match any entries in the client’s
server list.
Recommended Action: Add the appliance host name to the client’s server list.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5449
Message: The script is not approved for execution.
446
NetBackup status codes
NetBackup status codes
Explanation: The script that is listed in the policy was not in the default location
or any authorized location.
Recommended Action: Move the script to the default location or add the path as
an authorized location using the nbsetconfig or bpsetconfig command. The
default location for UNIX is: /usr/openv/netbackup/ext/db_ext. The default
location for Windows is: install_path\netbackup\dbext.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5450
Message: No scripts or paths are approved for execution on this client.
Explanation: DB_SCRIPT_PATH=none was set on this client to prevent scripts from
executing.
Recommended Action: Consult the client administrator for information as to why
none was set on this client.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5451
Message: The script is stored in a remote location.
Explanation: The script exists in a remote network location and cannot be executed.
Recommended Action: Move the script to a local authorized location for execution.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5452
Message: The script cannot be accessed for execution.
Explanation: The script either does not exist or is not accessible by the NetBackup
client service.
Recommended Action: Confirm that the script and its location are on the local
system and NetBackup can access the script. For Windows clients, be sure to verify
that the user running the NetBackup client service has read and execute
permissions for the script.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
447
NetBackup status codes
NetBackup status codes
NetBackup status code: 5500
Message: The NetBackup core web service service internal error
Explanation: An internal error occurred in the NetBackup core web service.
Recommended Action: Submit a problem report and provide the appropriate logs
and the request that caused the error. The NetBackup core web service sends log
messages to the NBSL log (OID=443).
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5501
Message: Supplied URI is too short
Explanation: The URL in the HTTP request is incomplete and does not have the
components required for the request.
Recommended Action: Check the URL that is supplied in the HTTP request and
correct if necessary. Resubmit the request. If the problem persists, submit a problem
report and provide the appropriate logs and the URL for the request. The NetBackup
core web service sends log messages to the NBSL log (OID=443).
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5502
Message: Supplied URI is not supported
Explanation: The core web service receives a request for an unsupported URL.
Recommended Action: Check the list of supported uniform resource identifiers
(URIs) by the core web service and retry with a supported URI. The NetBackup
core web service sends log messages to the NBSL log (OID=443).
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5503
Message: NetBackup core web service is terminating
Explanation: The NetBackup Service Layer (NBSL) service is in the process of
shutting down when it receives the HTTP request.
448
NetBackup status codes
NetBackup status codes
Recommended Action: Ensure that the NetBackup core web service is enabled.
Restart NBSL and retry the request. The NetBackup core web service sends log
messages to the NBSL log (OID=443).
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5504
Message: Query string in URI is bad
Explanation: The query string in the received HTTP request is bad.
Recommended Action: Correct the query string in the request then retry the
request. If the problem persists, submit a problem report with the appropriate logs
and the URL of the request. The NetBackup core web service sends log messages
to the NBSL log (OID=443).
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5505
Message: Client name is required
Explanation: The core web service receives a vmimagelist request with the client
name that is not supplied in the query filter.
Recommended Action: Include the correct client name in the vmimagelist request,
then retry the request. If the problem persists, submit a problem report with the
appropriate logs and the URL of the request. The NetBackup core web service
sends log messages to the NBSL log (OID=443).
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5506
Message: Failed to communicate with core web service proxy
Explanation: The core web service is unable to communicate with nbproxy to
process the incoming request.
Recommended Action: Restart NBSL, then retry the request. If the problem
persists, submit a problem report with the appropriate logs and the URL of the
request. The NetBackup core web service sends log messages to the NBSL log
(OID=443).
449
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5507
Message: Unknown jobid
Explanation: The core web service receives a request for job details (for example
/job/<jobid>), but NetBackup does not recognize the supplied jobid.
Recommended Action: Retry the request with a jobid that NetBackup recognizes
and has not yet been deleted.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5508
Message: Error in parsing XML document
Explanation: The core web service is unable to parse the XML response document
that bprd sent in response to the restore precheck request.
Recommended Action: Check the arguments that are passed to the restore
pre-check request, then retry the request. If the problem persists, submit a problem
report with the appropriate logs and the request details. The NetBackup core web
service sends log messages to the NBSL log (OID=443).
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5626
Message: After you upgrade both the source and the target master server, you
must update the trust relationship on both of the servers. After you update the trust
relationship, you can make configuration changes related to the trusted master
servers.
Explanation: The trust relationship implementation for remote master servers has
been changed for targeted Auto Image Replication (A.I.R.) on version 8.1 and later.
After you upgrade both the source and the target master servers from a pre-8.1
version to a version that is 8.1 or later, you must update the trust relationship
between both of the master servers. If you do not update the trust, you cannot
create or modify any storage lifecycle policies on the source master server.
Recommended Action: Run one of the following commands on both the source
and the target master server.
450
NetBackup status codes
NetBackup status codes
Run the following command if you are using user credentials; you are prompted to
provide the password:
nbseccmd -setuptrustedmaster -update -masterserver
master_server_name -remotemasterserver remote_master_server
-domainname domain_name -username username -fpfile filename
Run the following command if you are using an authorization token; you are
prompted to provide the token:
nbseccmd -setuptrustedmaster -update -masterserver
master_server_name -remotemasterserver remote_master_server
-domainname domain_name -fpfile filename
Run the following command if you are using the answer file:
nbseccmd -setuptrustedmaster -update -info answer_file
For more information about the nbseccmd command, see the NetBackup Commands
Reference Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5761
Message: Failed to initialize Windows Socket library
Explanation: On Windows, NetBackup encountered an error initializing the
Microsoft Windows socket communication library.
Recommended Action: None
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5762
Message: Peer is not a NetBackup Master or Media Server
Explanation: A NetBackup host returns this code if it does not recognize the
NetBackup server.
Recommended Action: Verify that the requesting NetBackup server is indeed
the master server as recognized by the NetBackup host returning this status code.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
451
NetBackup status codes
NetBackup status codes
NetBackup status code: 5763
Message: Encountered error during socket communication
Explanation: A Logging Assistant process encounters a socket communication
problem while operating on the master server or the NetBackup host.
Recommended Action: If NetBackup is otherwise functioning correctly, this error
requires Veritas Support assistance.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5764
Message: Command specified for execution is invalid or not allowed
Explanation: A Logging Assistant process encounters this error on a NetBackup
host.
Recommended Action: Contact Veritas Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5765
Message: Failed to execute specified command (CreateProcess or exec)
Explanation: A Logging Assistant process encounters this error on a NetBackup
host while it performs the requested action. This error may indicate problems with
system resources or even a product defect.
Recommended Action: Retry the Logging Assistant action. If the error persists,
contact Veritas Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5766
Message: Failed to execute specified command (fork)
Explanation: A Logging Assistant process encounters this error on a NetBackup
host while it performs the requested action. This error may indicate problems with
system resources on the host.
Recommended Action: Retry the Logging Assistant action. If the error persists,
contact Veritas Technical Support.
452
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5767
Message: Failed to get exit code of child process
Explanation: A Logging Assistant process encounters this error on a NetBackup
host on a failure to get the exit status of a child process while it performs a requested
action. One possible cause for this error can be manual intervention.
Recommended Action: If this error is not the result of manual intervention, contact
Veritas Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5768
Message: Failed to read complete output of executed command
Explanation: Socket connection problems exist between the Logging Assistant
processes on master server and the NetBackup host.
Recommended Action: Retry the Logging Assistant action. If the error persists,
contact Veritas Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5769
Message: Failed to reap exit code of child process
Explanation: Returned by a Logging Assistant process on UNIX/Linux NetBackup
host on failure to get exit status of the child process while performing requested
action. One possible cause for this error can be manual intervention.
Recommended Action: If this error is not the result of manual intervention, contact
Veritas Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5770
Message: Failed to get cluster configuration
Explanation: This status code should not be encountered.
453
NetBackup status codes
NetBackup status codes
Recommended Action: None
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5771
Message: Failed to write output received from remote command
Explanation: Socket connection problems exist between the Logging Assistant
processes on the master server.
Recommended Action: If this error is not the result of manual intervention, contact
Veritas Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5772
Message: Failed to read unified logging configuration file
Explanation: A VxUL configuration file is missing or malformed.
Recommended Action: Check the existence and the format of the VxUL
configuration file that was mentioned along with the error message on the specified
NetBackup host.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5773
Message: Failed to get virtual name of Master Server
Explanation: This status code should not be encountered.
Recommended Action: None
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5774
Message: Specified logs are not valid
Explanation: A product may be defective.
Recommended Action: Contact Veritas Technical Support.
454
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5775
Message: Invalid option specified
Explanation: A product may be defective.
Recommended Action: Contact Veritas Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5776
Message: Failed to spawn new process
Explanation: A product may be defective.
Recommended Action: Contact Veritas Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5777
Message: Failed to create the staging directory on Master Server
Explanation: Logging Assistant failed to create the specified staging directory on
the master server.
Recommended Action: Verify that the specified path already exists. If not, try to
create it manually.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5778
Message: Failed to read Logging Assistant database
Explanation: Logging Assistant is unable to read database file path and file
contents.
Recommended Action: Check permissions of the Logging Assistant database
file:
UNIX: /usr/openv/var/global/logasst.db
455
NetBackup status codes
NetBackup status codes
Windows: <Install Path>\Veritas\NetBackup\var\global\logasst.db
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5779
Message: Failed to lock Logging Assistant database
Explanation: Logging Assistant may be defective.
Recommended Action: If the error persists, contact Veritas Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5780
Message: Failed to set non-inherit flag on database file handle
Explanation: This error can occur only on Windows.
Recommended Action: Contact Veritas Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5781
Message: Failed to prepare to save Logging Assistant database
Explanation: Logging Assistant may be defective.
Recommended Action: If the error persists, contact Veritas Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5782
Message: Failed to start to write Logging Assistant database
Explanation: Logging Assistant may be defective.
Recommended Action: If the error persists, contact Veritas Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
456
NetBackup status codes
NetBackup status codes
NetBackup status code: 5783
Message: Failed to save Logging Assistant database
Explanation: Logging Assistant may be defective.
Recommended Action: If the error persists, contact Veritas Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5784
Message: Failed to access or write the readme or progress file
Explanation: The parent directory from which to read or in which to write the
README or Progress file is missing or has incorrect permissions.
Recommended Action: Please check the specified path.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5786
Message: Logging Assistant record does not exist
Explanation: Another GUI instance has deleted the Logging Assistant record.
Recommended Action: Refresh the Logging Assistant GUI, then check if the
record has been deleted.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5787
Message: Logging Assistant record already exists
Explanation: None
Recommended Action: None
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5788
Message: Debug logging has not been set up for Logging Assistant record
Explanation: The Logging Assistant GUI is out of sync.
457
NetBackup status codes
NetBackup status codes
Recommended Action: Refresh the Logging Assistant GUI view and retry.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5789
Message: Failed to interpret bpdbjobs output for job detail
Explanation: The Logging Assistant encountered interpreting information fetched
from the Jobs database. The Logging Assistant cannot make pre-selections for
debug logging to set up based on the Job database.
Recommended Action: Manually select the debug logging to set up. Contact
Veritas Technical Support to investigate the Job Analysis failure.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5790
Message: Failed to fetch PureDisk configuration setting from Windows registry
Explanation: NetBackup cannot read the PureDisk configuration information.
Recommended Action: Contact Veritas Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5794
Message: Failed to calculate debug logs size for preview
Explanation: Logging Assistant may be defective.
Recommended Action: If the error persists, contact Veritas Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5796
Message: Logging Assistant agent encountered failure writing on socket to Master
Server
Explanation: A socket connection problem exists between Logging Assistant
processes on the master server and the NetBackup host.
458
NetBackup status codes
NetBackup status codes
Recommended Action: Retry the Logging Assistant action. If the error persists,
contact Veritas Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5798
Message: Failed to list disk volumes on Master Server using bpmount
Explanation: This error occurs when the Logging Assistant enumerates partitions
on Windows while fetching free disk space information.
Recommended Action: If the error persists, contact Veritas Technical Support.
You may still be able to manually establish free space information and initiate the
intended action such as log collection.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5799
Message: Failed to get disk space information of volumes or mount points
Explanation: Logging Assistant tries to fetch free disk space information.
Recommended Action: If the error persists, contact Veritas Technical Support.
You may still be able to manually establish free space information and initiate the
intended action such as log collection.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5800
Message: Failed to execute bpdbjobs to fetch job details
Explanation: Logging Assistant may be defective.
Recommended Action: If the error persists, contact Veritas Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5801
Message: Failed to fetch job details. Check if job exists.
459
NetBackup status codes
NetBackup status codes
Explanation: The specified Job ID for Job Analysis that suggests what debug
logging to set up does not exist in the Jobs database.
Recommended Action: If the specified job ID does exist, contact Veritas Technical
Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5803
Message: Failed to modify PureDisk configuration file
Explanation: None
Recommended Action: Contact Veritas Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5804
Message: Failed to modify Java GUI configuration file (Debug.properties)
Explanation: None
Recommended Action: Contact Veritas Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5805
Message: Remote host NetBackup version not supported by the Logging Assistant
Explanation: The Logging Assistant supports setting up debug logging on (and
collecting debug logs from) hosts that run NetBackup version 7.7 or higher.
Recommended Action: None
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5806
Message: Unexpected contents of PureDisk configuration file (pdregistry.cfg)
Explanation: None
Recommended Action: Contact Veritas Technical Support.
460
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5807
Message: Failed to copy nbcplogs/nbsu output file from remote host
Explanation: The Logging Assistant contacts bpcd to copy the nbcplogs and nbsu
output files from the NetBackup host.
Recommended Action: Check that the connection from the master server to bpcd
can be set up by using bptestbpcd.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5808
Message: Failed to load PBX configuration to change log level
Explanation: A PBX configuration file may be missing or malformed.
Recommended Action: Check the existence and format of the PBX configuration
file and the error message on the specified NetBackup host.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5809
Message: Invalid PBX Debug Log Level specified
Explanation: The PBX logging level is invalid.
Recommended Action: Set the PBX logging level to an appropriate value.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5811
Message: Temporary directory to use for logs collection does not exist
Explanation: The Logging Assistant failed to create the temporary directory on a
NetBackup host in which to collect the nbcplogs or nbsu output.
Recommended Action: Check the directory permissions on the NetBackup host.
Also verify that the parent directory of the specified temporary directory exists.
461
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5812
Message: nbcplogs exited with error
Explanation: This status code should not be encountered.
Recommended Action: Contact Veritas Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5813
Message: nbcplogs did not collect any logs
Explanation: None
Recommended Action: Check that the debug logs on the host are available to
collect. If the debug logs relevant to the Logging Assistant record exist on the host,
contact Veritas Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5814
Message: nbsu exited with error
Explanation: None
Recommended Action: Contact Veritas Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5815
Message: No activity for the Logging Assistant record is in progress
Explanation: The Logging Assistant GUI is out of sync.
Recommended Action: Refresh the Logging Assistant GUI and retry.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
462
NetBackup status codes
NetBackup status codes
NetBackup status code: 5816
Message: Collect debug logs operation canceled
Explanation: Not available.
Recommended Action: Not available.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5817
Message: Collect nbsu operation canceled
Explanation: Not available.
Recommended Action: Not available.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5819
Message: Cancel operation requested
Explanation: Not available.
Recommended Action: Not available.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5820
Message: Not a valid Logging Assistant temporary directory for clean-up
Explanation: Not available.
Recommended Action: Not available.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5821
Message: Failed to get policy details
Explanation: To suggest debug logging to set up, the Logging Assistant fetches
policy information that is associated with the job ID submitted for analysis. However,
the policy does not exist.
463
NetBackup status codes
NetBackup status codes
Recommended Action: If the associated policy does exist, please contact Veritas
Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5902
Message: Fingerprint of the certificate could not be generated.
Explanation: The CA certificate may not be in the trust store.
Recommended Action: Run the nbcertcmd –getCACertificate command and
try to generate the CA certificate again.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5903
Message: CA certificate could not be verified.
Explanation: The CA certificate that is on the host cannot be used to perform the
request. Trust is not established with the NetBackup host to which you are trying
to communicate. The CA certificate is not in the trust store in the host certificate
database or the trust store has more than one certificate with the same name
(usually, a generic name like localhost.localdomain). The web service certificate
may also have expired.
Recommended Action: The NetBackup host must trust the CA. Check if the CA
certificate was added to the trust store with the nbcertcmd –listCACertDetails
command. Run the nbcertcmd –getCACertificate command to add the certificate
to the trust store.
If the trust store has multiple certificates with the same (generic) name, contact
Veritas Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5904
Message: Internal error.
Explanation: One of the internal services has failed to respond.
Recommended Action: Rerun the operation. If the problem continues, save all
of the error log information and contact Veritas Technical Support.
464
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5905
Message: The host ID is not valid.
Explanation: The master server does not recognize the specified host ID.
Recommended Action: Check the specified host ID using the nbcertcmd
–listCertDetails command. If the specified NetBackup host is part of multiple
NetBackup domains, ensure that you are providing the correct host ID that
corresponds to the specified NetBackup domain.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5906
Message: The token is not valid.
Explanation: The generated token is not valid.
Recommended Action: Redo the action. If the problem continues, save all of the
error log information and contact Veritas Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5907
Message: Unknown resource requested.
Explanation: The certificate that you are trying to view or to execute related
operations does not exist.
Recommended Action: Verify the certificate details that you provided. Details
can include a serial number, host ID, or host name.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5908
Message: Unknown error occurred.
Explanation: The certificate generation, renewal, or retrieval operation failed.
465
NetBackup status codes
NetBackup status codes
Recommended Action: Save all of the error log information and contact Veritas
Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5909
Message: Token does not exist for this token value.
Explanation: The token value that you provided is not correct.
Recommended Action: Provide the correct token value and rerun the operation.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5910
Message: Host name is not specified.
Explanation: The operation failed to retrieve the required information.
Recommended Action: Rerun the operation. If the problem continues, save all
of the error log information and contact Veritas Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5913
Message: A token with this name already exists.
Explanation: The token name that you are using to create the new token already
exists.
Recommended Action: Provide a new name and then recreate the token.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5914
Message: The security service is not available.
Explanation: The NetBackup web service is not reachable or is not running on
the master server.
466
NetBackup status codes
NetBackup status codes
Recommended Action: Check the network connectivity of the host on which you
are performing the operation. Contact the NetBackup administrator to correct the
status of the NetBackup web service.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5915
Message: Request timed out.
Explanation: A request to the NetBackup web service has failed due to a network
timeout.
Recommended Action: Check the network connectivity of the host on which you
are performing the operation. Contact the NetBackup administrator to correct the
status of the NetBackup web service.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5916
Message: Token name is not specified.
Explanation: The operation failed to retrieve the token information from the request
because the token name was not specified by the user in the request.
Recommended Action: Rerun the operation. If the problem continues, save all
of the error log information and contact Veritas Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5917
Message: The reissue token cannot have the usage count greater than one.
Explanation: The re-issue token cannot be a multi-use token.
Recommended Action: A multi-use token cannot be associated with the host.
The re-issue token cannot be a multi-use token. Take appropriate action and
generate the required token.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
467
NetBackup status codes
NetBackup status codes
NetBackup status code: 5918
Message: The maximum usage count for the token should be provided within the
valid range, which is from 1 to 99999.
Explanation: A token can be used from 1 to 99,999 times. The maximum usage
count that you selected has exceeded the allowable usage count.
Recommended Action: Select a valid usage count.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5919
Message: Validity period specified for this token is not valid. The maximum validity
period that you can specify is 999 days.
Explanation: A token can have a validity period from 1 – 999 days. The validity
period specified exceeded the allowable validity period.
Recommended Action: Select a valid period.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5920
Message: The specified token is associated with a different host name.
Explanation: The specified token is not associated with the requesting host.
Recommended Action: Verify that you are using the correct token. If the specified
NetBackup host is associated with multiple NetBackup domains, ensure that you
are using the token that corresponds to the appropriate NetBackup domain.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5921
Message: The specified token is associated with a different host ID.
Explanation: The specified token is not associated with the host.
Recommended Action: Verify that you are using the correct token.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
468
NetBackup status codes
NetBackup status codes
NetBackup status code: 5922
Message: The reissue token cannot be associated with the host name.
Explanation: You cannot generate a token using both the host ID and the host
name.
Recommended Action: Use either the host ID or the host name and try to
regenerate the token.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5925
Message: The required data is missing.
Explanation: Certificate generation or renewal is requested, but the Certificate
Signing Request (CSR) file sent with the request is empty.
Recommended Action: Ensure that all of the required inputs provided are correct
and retry the operation. If the problem continues, save all of the error log information
and contact Veritas Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5926
Message: Certificate signing request is not valid.
Explanation: The certificate that signed the request file is not in the expected
format.
Recommended Action: Regenerate the certificate request file, rerun the operation,
and ensure that the data has not changed in transit.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5927
Message: The specified file could not be opened.
Explanation: The specified file might not exist or you do not have permission to
access the file.
Recommended Action: Use a valid file name and try to open the file or check
permissions.
469
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5929
Message: The certificate is not in the Active state, so it cannot be renewed.
Explanation: A certificate has three states: active, revoked, and expired. You
cannot renew revoked certificates.
Recommended Action: Send the certificate re-issue request after performing
corrective actions. If you want to use the same credential (key pair), then the new
certificate can be generated using the re-issue token. You can use the following
command:
nbcertcmd –getCertificate
If you plan to change credentials, see the NetBackup Security and Encryption Guide
for workflow details.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5930
Message: The request could not be authorized.
Explanation: The master server is unable to validate the client certificate. Possible
causes for this are as follows:
■
The client certificate has expired. You can run the nbcertcmd –getCertDetails
or nbcertcmd –getCertDetails –cluster command to confirm.
■
The client key pair has changed and the host has obtained (or renewed) a
certificate from another master server.
■
The certificate for the host has been revoked.
■
A web authentication token is required for a NetBackup web application operation
(nbcertcmd). You will see this error if the user has not been authenticated.
Recommended Action: Use a re-issue token with the nbcertcmd
–getCertificate command. If the user has not been authenticated, use the bpnbat
–login –logintype WEB command to get a web authentication token.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
470
NetBackup status codes
NetBackup status codes
NetBackup status code: 5931
Message: The host ID is empty.
Explanation: The host ID cannot be found in the revoke certificate request.
Recommended Action: Resend the request. If the problem continues, save all
of the error log information and contact Veritas Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5932
Message: Token usage count is not set.
Explanation: An attempt to generate an authorization token with a zero usage
count was performed.
Recommended Action: Generate a token with valid parameters. The allowable
count is from 1 to 99, 999.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5933
Message: The maximum token usage limit has been reached.
Explanation: An authorization token has a fixed usage count. If the usage count
exceeds the allowable usage count, the token cannot be used.
Recommended Action: Create a new token.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5934
Message: The token has expired.
Explanation: The token validity period has reached the maximum limit and has
expired. This token can no longer be used.
Recommended Action: Create a new token.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
471
NetBackup status codes
NetBackup status codes
NetBackup status code: 5936
Message: The specified token name is not in a valid format.
Explanation: The name specified for the token contains invalid characters.
Recommended Action: Specify a valid token name. The valid characters are A-Z,
a-z, 0-9, and _.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5938
Message: The revocation reason code is not valid.
Explanation: NetBackup supports only revocation reason codes from 1 to 5.
Recommended Action: Specify a valid reason code and then try to revoke the
certificate.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5939
Message: This revocation reason code is not supported by the server.
Explanation: NetBackup supports only revocation reason codes from 1 to 5.
Recommended Action: Specify a valid reason code and then try to revoke the
certificate.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5940
Message: Reissue token is mandatory; please provide a reissue token.
Explanation: A certificate reissue requires a reissue token that is associated with
a specific host ID.
Recommended Action: Generate a reissue token for the required host and then
request a certificate reissue. Use the following command (or the NetBackup
Administration Console) to generate the reissue token:
nbcertcmd -createToken -name name_of_token -reissue
[-host host_name | -hostId host_id]
472
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5941
Message: The host ID is not associated with any host.
Explanation: The specified host ID is not known to the master server.
Recommended Action: Verify that the specified host ID corresponds to the
specified master server. Use the nbcertcmd –listCertDetails command on the
specified NetBackup host to find the host ID that corresponds to the specified master
server.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5942
Message: Certificate could not be read from the local certificate store.
Explanation: The certificate was not added to the local certificate store or it may
be lost or corrupted. You may also have no administrator privileges on the given
NetBackup host.
Recommended Action: Check if you have administrator privileges on the specified
NetBackup host. If you have the required privileges, use the –force option with the
nbcertcmd -getCertificate command to regenerate the existing certificate. You
may have to supply a token with this command, depending on the certificate
deployment security levels specified on the master server.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5943
Message: Lock cannot be acquired on the file for writing.
Explanation: There was an error updating the file.
Recommended Action: Rerun the operation. If the problem continues, save all
of the error log information and contact Veritas Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
473
NetBackup status codes
NetBackup status codes
NetBackup status code: 5944
Message: The host alias list has multiple host names.
Explanation: The certificate signing request contains multiple host names and
only a single host name is supported.
Recommended Action: Specify a single host name in the certificate signing
request and resend the request to the master server.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5945
Message: Host alias is not specified.
Explanation: The certificate signing request does not contain a host name.
Recommended Action: Specify a host name in the certificate signing request and
resend the request to the master server.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5946
Message: Token is mandatory; please provide a token.
Explanation: The certificate deployment security level on the master server does
not support the auto deployment of the certificate for the given host.
Recommended Action: Generate an authorization token and then run the
nbcertcmd -getCertificate command to request a certificate.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5947
Message: The host is not registered with the server.
Explanation: The specified host could not be found.
Recommended Action: Specify the correct host name or use a valid authorization
token and rerun the operation.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
474
NetBackup status codes
NetBackup status codes
NetBackup status code: 5948
Message: Certificate could not be written to the local certificate store.
Explanation: You might not have administrator privileges on the specified
NetBackup host to add the certificate to the local certificate store.
Recommended Action: Check if you have administrator privileges on the given
NetBackup host. If you have the required privileges, redo the action. If the problem
continues, save all of the error log information and contact Veritas Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5949
Message: Certificate does not exist.
Explanation: A certificate from the specified server does not exist on the NetBackup
host.
Recommended Action: Ensure that the appropriate certificate is deployed. See
the NetBackup Security and Encryption Guide for details on how to deploy
certificates.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5950
Message: Certificate already exists.
Explanation: A certificate from the specified server already exists on the requesting
NetBackup host.
Recommended Action: Use the nbcertcmd -getCertificate –force command
to overwrite the existing certificate, if required.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5953
Message: The certificate deployment level is not valid.
Explanation: The certificate deployment level that you are trying to set is invalid.
Recommended Action: Select a certificate deployment level between 0 - 2 and
rerun the command to set the certificate deployment level. For more information
on certificate deployment levels, see the NetBackup Security and Encryption Guide.
475
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5954
Message: The host name could not be resolved to the requesting host's IP address.
Explanation: The master server is unable to resolve the host name to the peer IP
address of the NetBackup host that is requesting the certificate.
Recommended Action: Verify and correct your network configurations so that
the master server can resolve the host name to the peer IP address. Alternatively,
you can use an authorization token to deploy the certificate.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5955
Message: The host name is not known to the master server.
Explanation: The host name is not on the known hosts list.
Recommended Action: Ensure that the host entry exists on one of the following
locations: the server configuration list, the EMM database, at least 1 catalog image
(not more than 6 months old), the clients listed in policies, or the client DB entry.
Alternatively, you can use an authorization token to deploy the certificate.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5956
Message: The existing certificate deployment level on the master server does not
allow this operation.
Explanation: The certificate deployment security level set for the host does not
let you deploy the host ID-based security certificate or add the CA certificate to the
trust store without verification.
Recommended Action: If you see this error message while you are retrieving the
host ID-based certificate, ensure that you use a valid authorization token with the
-getCertificate option.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
476
NetBackup status codes
NetBackup status codes
NetBackup status code: 5957
Message: The master server is unable to connect to the CA.
Explanation: The master server is unable to connect to the NetBackup AT broker.
Recommended Action: Check the status of the NetBackup AT broker on the
master server. Restart the service, if required.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5958
Message: The master server is unable to access the CA certificate.
Explanation: The Web service user on the master server does not have the
required permissions to access the CA certificate.
Recommended Action: Ensure that the web service user has the required
permissions to read the CA certificate on the master server.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5959
Message: The NetBackup AT credentials of the web service user are not valid.
Explanation: The web service users’ AT credentials are invalid or have expired.
Recommended Action: Stop the web service on the master server, run the
nbcertconfig –u –user webservice_user command, and restart the web service.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5960
Message: NetBackup AT configuration on the master server could not be initialized.
Explanation: The AT configuration initialization failed or the web service user does
not have the required permissions to access its certificate store.
Recommended Action: Ensure that the web service user has the required
permissions to access the certificate store on the master server.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
477
NetBackup status codes
NetBackup status codes
NetBackup status code: 5962
Message: The host name does not match the existing name in the certificate.
Explanation: The host ID certificate renewal is attempted for the host whose host
name is changed.
Recommended Action: If the NetBackup host administrator wants to get the
certificate for the given host with the new name, then perform the following steps:
1.
The NetBackup host administrator should ask the NetBackup administrator to
revoke the certificate of the host by using the -host host_name | -hostId
host_id options. The NetBackup administrator can use the following command:
nbcertcmd -revokeCertificate -reasonCode value
-host old_host_name | -hostId host_id
2.
The NetBackup host administrator should ask the NetBackup administrator to
generate a reissue token for a specific host. The NetBackup administrator can
use the following command:
nbcertcmd –createToken -name token_name -reissue
-host old_host_name | -hostId host_id
3.
After the NetBackup host administrator receives the reissue token, the following
command can be used (specify the received token when prompted):
nbcertcmd -getCertificate -token –force
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5963
Message: Entity does not exist.
Explanation: The user is referring to an entity that does not exist when using a
specific command. The possible entities are either an authorization token or a host
ID-based certificate. The user may be referring to a token with the wrong token
name or the user may be referring to a certificate with an incorrect serial number.
Recommended Action: Check that the argument values supplied in the command
are correct.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
478
NetBackup status codes
NetBackup status codes
NetBackup status code: 5964
Message: Data conversion error.
Explanation: There was an internal error while processing data.
Recommended Action: Rerun the operation. If the problem continues, save all
of the error log information and contact Veritas Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5965
Message: The host ID associated with this reissue token is assigned to another
host. You need to revoke the certificate for the host ID before you continue.
Explanation: The user specified the nbcertcmd –getCertificate command
using a reissue token. The user is trying to reissue a host ID to a host with a host
name that is different than the one registered with the server. When a host is going
through a name change and wants to ensure that its identity is maintained in the
NetBackup domain, the user should revoke the existing certificate with the existing
host name.
Recommended Action: The user must revoke the current certificate with the
existing host name and then reissue the token to request a certificate using the
new host name.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5966
Message: The host has an active certificate. You need to revoke the certificate
before you can disassociate the host from its host ID.
Explanation: The user is trying to decouple an existing host and it has active
certificates. In this case, the server will reject the decouple request as only the hosts
that have revoked certificates can be decoupled from their existing host IDs.
Recommended Action: The user must revoke the certificate for this host and only
then mark it as decoupled from the associated host ID.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5967
Message: The file already exists.
479
NetBackup status codes
NetBackup status codes
Explanation: The user provided a specific file name to perform an operation, but
the file already exists at the specified location.
Recommended Action: The user can rename/move/delete the existing file or
submit a new file name.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5968
Message: The host information could not be retrieved while creating the certificate
signing request.
Explanation: While creating a certificate signing request for a given host, specific
information such as the host name, host aliases, and host key pair is retrieved from
the host. The nbcertcmd command failed to retrieve this information.
Recommended Action: Try the following possible solutions:
■
Retry the current operation.
■
Retry the current operation by restarting the system.
■
If the problem continues, contact Veritas Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5969
Message: Response from the NetBackup Web Management Console service
could not be parsed.
Explanation: The response received from the NetBackup web management
console service while executing current operation is in an unknown or incorrect
format.
Recommended Action: Retry the current operation. If the problem continues,
contact Veritas Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5970
Message: The server time could not be fetched.
Explanation: The current server time could not be retrieved.
480
NetBackup status codes
NetBackup status codes
Recommended Action: Rerun the operation. If the problem continues, save all
of the error log information and contact Veritas Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5971
Message: The token contains characters that are not supported.
Explanation: The token value passed in the token file contains characters that
are not supported. NetBackup only supports the following characters as part of the
token value (A-Z, a-z, and 0-9).
Recommended Action: Check the token value passed in the token file and ensure
that it contains valid characters (A-Z, a-z, and 0-9). Ensure that the file encoding
format is ANSI.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5972
Message: The certificate could not be revoked. It was already revoked or expired.
Explanation: When revocation of the already revoked or expired certificate is tried,
it will not allow the revocation.
Recommended Action: Specify the active certificate and then try to revoke the
certificate.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5973
Message: The token type is not valid.
Explanation: To create a token, a valid token type is required.
Recommended Action: Specify one of the following token types:
■
0 - Default token
■
1 - Reissue token
If you have not provided the token type, the default token type (0) is automatically
selected.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
481
NetBackup status codes
NetBackup status codes
NetBackup status code: 5974
Message: The specified token requires a host ID.
Explanation: To create a reissue token, a corresponding host ID is required.
Recommended Action: Provide a host ID of the host for which you want to create
a token.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5978
Message: Failed to refresh the certificate revocation list (CRL) and security level.
Explanation: This error can be due to following reasons:
■
Recommended Action: Failed to fetch the CRL via the HTTP request
■
Failed to save the CRL on the disk
■
Failed to fetch the security level via the HTTP request
■
Failed to update the certmapinfo.json with CRL and security level information
■
Failed to get the CRL because a client in the DMZ could not connect to the
HTTP tunnel on the media server
Recommended Action: Do the following, as appropriate:
■
On the master server, examine the unified logs on the NetBackup server for
nbwebservice (OID 466 and 484).
■
On the media server, examine the pbx (OID 103), nbpxytnl (OID 490), and
nbpxyhelper (OID 486) logs. pbx is logged to the following directories:
Windows: install_path\VxPBX\log
UNIX: /opt/VRTSpbx/log
■
■
Ensure that the following are online:
■
Master server
■
NetBackup web service (nbwmc)
■
NetBackup relational database (NBDB)
On the host where the error occurred, examine the legacy logs for nbcertcmd.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
482
NetBackup status codes
NetBackup status codes
NetBackup status code: 5979
Message: The certificate revocation list (CRL) in the certificate is invalid.
Explanation: The error can be due to following reasons:
■
Explanation: The host failed to get the CRL when it requested the certificate
via the HTTP request.
■
The CRL is empty or has an invalid format.
Recommended Action: Do the following, as appropriate:
■
On the host where the error occurred, examine the legacy logs for nbcertcmd.
Use these logs to help troubleshoot issues that appear in the web services.
■
On the master server, examine the unified logs for nbwebservice (OIDs 466
and 484).
■
Restart the services on the master server. Then, retry the following command
for the host to fetch the CRL:
./nbcertcmd -getCrl
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5980
Message: The security level in the certificate is invalid.
Explanation: The host failed to get the security level with the certificate via the
HTTP request.
Recommended Action: Do the following, as appropriate:
■
On the master server, examine the unified logs on the NetBackup server for
nbwebservice (OID 466 and 484).
■
On the host where the error occurred, examine the legacy logs for nbcertcmd.
■
Run the following command for the host to fetch the CRL and the security level:
./nbcertcmd -getCrl
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5982
Message: The certificate revocation list (CRL) is unavailable.
Explanation: This error can occur for the following reasons:
483
NetBackup status codes
NetBackup status codes
■
(Scenario 1) The NetBackup web service has not yet generated a CRL. The
NetBackup web service attempts to generate a new CRL on startup. If the CRL
has not been generated it means one of two things: NetBackup is working to
create it. Or, there was a problem generating the CRL.
■
(Scenario 2) The host does not have a CRL cached for the current domain.
Recommended Action: Do the following, as appropriate:
For Scenario 1, do the following:
■
Retry the command or operation.
■
Verify that nbatd is running on the master server, then retry the operation.
■
Restart the services on the master server, then retry the operation.
■
On the master server, examine the unified logs on the NetBackup server for
nbwebservice (all OIDs).
■
On the master server and on the host where the error occurred, examine the
unified logs for nbatd (OID 18).
For Scenario 2, do the following:
■
Run the following command for the master server and then retry the operation:
./nbcertcmd -getCrl -server master server name
■
On all hosts involved in the communication, examine the unified logs for
nbpxyhelper (OID 486).
■
On the host where the error occurred, examine the legacy logs for nbcertcmd.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5983
Message: The host certificate is revoked.
Explanation: The host certificate is present in the certification revocation list (CRL)
and is revoked.
Recommended Action: Do the following, as appropriate:
■
On the host where the error occurred, examine the legacy logs on the NetBackup
server for nbcertcmd.
■
On all of the hosts involved in the communication, examine the unified logs for
nbpxyhelper (OID 486).
■
If the certificate was revoked in error, reissue a certificate for the host.
484
NetBackup status codes
NetBackup status codes
■
If the certificate was revoked as intended, an attempted security breach may
have occurred.
■
Contact your Security Administrator.
■
To reissue a certificate for the host, see the NetBackup Security and Encryption
Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5986
Message: The certificate request for the host was rejected because the host could
not be validated as a master server.
Explanation: The master server-specific parameters were sent with the nbcertcmd
-getCertificate command, but the certificate was requested for a non-master
server host.
Recommended Action: Ensure that you do not send the master server-specific
parameters when you deploy the certificate on a non-master server host.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5987
Message: Cannot fetch the host ID of the NetBackup master server. The master
server does not have the certificate.
Explanation: The master server does not have the certificate or the NetBackup
Service Layer (NBSL) on the master server is down.
Recommended Action: Ensure that the following occurs:
■
NBSL is running on the master server
■
If NBSL is running on the master server, ensure that the host ID-based certificate
is deployed on the master server
■
If the host ID-based certificate is deployed and if you still see this error, refer to
the Resolving the master server host name change issue procedure..
Resolving the master server host name change issue
This error may occur if the master server host name is changed from a Fully Qualified
Domain Name (FQDN) to a short name (or vice versa) in any of the following
scenarios:
■
NetBackup installation after a disaster
485
NetBackup status codes
NetBackup status codes
■
Manual update in the NetBackup configuration file (bp.conf file on the UNIX or
Windows registry).
In the following example, NetBackup is installed on a master server with a short
name and the catalog backup is run. After a disaster, NetBackup is installed on the
master server in a disaster recovery mode, but this time with FQDN. However, the
identity of the master server (or disaster recovery package) is restored with the
short name. This can cause failure when reissuing the client certificates,
automatically renewing the client certificates and deploying new certificates on
clients.
To resolve this issue, use the following steps:
1.
Log on to the master server.
2.
Run following command:
UNIX:
/usr/openv/netbackup/bin/nbcertcmd -ping
Windows:
Install_path\NetBackup\bin\nbcertcmd -ping
3.
■
If the command is executed successfully, proceed to next step.
■
If it fails with the exist status code 8509 (The specified server name was
not found in the web service certificate), then carry out the steps that are
provided in the following technote:
https://www.veritas.com/support/en_US/article.000126751
Proceed to the next step.
Stop and start the NetBackup Web Management Console service on the master
server. Use following the NetBackup command:
UNIX:
/usr/openv/netbackup/bin/nbwmc -terminate
/usr/openv/netbackup/bin/nbwmc -start
Windows:
install_path\NetBackup\wmc\bin\nbwmc.exe -stop -srvname "NetBackup
Web Management Console"
install_path\NetBackup\wmc\bin\nbwmc.exe -start -srvname
"NetBackup Web Management Console"
4.
Perform the user login on the master server. Use the following command:
install_path/netbackup/bin/bpnbat -login -loginType WEB
486
NetBackup status codes
NetBackup status codes
For example:
install_path\netbackup\bin\bpnbat -login -loginType WEB
Authentication Broker [abc.example.com is default]:
Authentication port [0 is default]:
Authentication type (NIS, NISPLUS, WINDOWS, vx, unixpwd,
ldap)[WINDOWS is default]:
Domain [abc.example.com is default]:
Login Name [administrator is default]:
Password:
Operation completed successfully.
5.
Note the value of the key Client_Name for the master server. For a clustered
master server, note the value of the key Cluster_Name This can be found at
the following locations:
UNIX:/usr/openv/netbackup/bp.conf
Windows:HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\NetBackup\CurrentVersion\Config
This value can either be the FQDN or the short name. For example,
abc.example.com.
6.
Note the host ID of the master server. You can obtain its value by using the
following command:
install_path/netbackup/bin/nbcertcmd -listCertDetails
For a clustered master setup, use the following command:
install_path\netbackup\bin\nbcertcmd -listCertDetails -cluster
This command may return multiple records (if only one record is returned,
select the host ID provided in that record).
■
If the host name obtained in step 5 is FQDN, then pick the record where
the “Issued By” entry matches its short name.
■
If the host name obtained in step 5 is a short name, then pick the record
where the “Issued By” entry matches its FQDN.
For example:
install_path\netbackup\bin\nbcertcmd -listCertDetails
Master Server : abc
Host ID : xxxxxx-4201-4c6a-xxxx-xxxxx
Issued By : /CN=broker/OU=root@abc/O=vx
Serial Number : 0x62e108c90000000c
Expiry Date : Aug 21 08:42:54 2018 GMT
487
NetBackup status codes
NetBackup status codes
488
SHA1 Fingerprint : 50:89:AE:66:12:9A:29:4A:66:E9:DB:71:37:
C7:EA:94:8C:C6:0C:A0
Master Server : xyz
Host ID : yyyyyy-4785-4252-yyyy-yyyyy
Issued By : /CN=broker/OU=root@xyz.master1.com/O=vx
Serial Number : 0x6ede87a70000000a
Expiry Date : Aug 21 09:52:13 2018 GMT
SHA1 Fingerprint : FE:08:C2:09:AC:5D:82:57:7A:96:5C:C1:4A:
E6:EC:CA:CC:99:09:D2
Operation completed successfully.
Here, 2 records are returned. For the first record, the issuer name provided in
the “Issued By” field matches the short name of the client_name obtained in
step 5. Select the host ID that appears in the first record.
7.
Add a host ID-to-host name mapping. Map the host ID of the master server
that you have obtained in step 6 to the host name that you have obtained in
step 5.
Use the following command:
install_path/netbackup/bin/admincmd/nbhostmgmt -a -i host_ID -hm
host_name
For example:
install_path/netbackup/bin/admincmd/nbhostmgmt -a -i
xxxxxx-4201-4c6a-xxxx-xxxxx -hm abc.example.com
abc.example.com is successfully mapped to xxxxxx-4201-4c6a-xxxx-xxxxx.
You can also add this host ID-to-host name mapping using the NetBackup
Administration Console. Use the Security Management > Host Management
> Hosts tab.
8.
Renew the host ID-based certificate of the master server by using the following
command:
install_path/netbackup/bin/nbcertcmd -renewCertificate
For a clustered master server, use the following command:
install_path\netbackup\bin\nbcertcmd -renewCertificate -cluster
NetBackup status codes
NetBackup status codes
9.
Continue with the certificate deployment on a client (this can be either a reissue
certificate, the automatic renewal of a certificate, or a new certificate
deployment).
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5988
Message: The host name is not part of the host ID-to-host name mapping list.
Explanation: The requesting host name is not mapped with the respective host
ID.
Recommended Action: Map the host name to the associated host ID. In the
NetBackup Administration Console, use the Security Management > Host
Management > Hosts tab or the nbhostmgmt command to add mappings.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 5989
Message: The reissue token is mandatory as a certificate was already issued to
this host. Revoke the existing certificate if it is active and map this host name to
the associated host ID.
Explanation: The host names that are used during the installation and re-installation
are different; however, the host names are associated with same host ID. This can
happen if the host name used earlier is a shortname and the one used now is in
FQDN or vice versa. You need to identify the host record in the NetBackup
Administration Console, using the Security Management > Host Management
> Hosts tab or the nbhostmgmt command and use the host ID to generate the
reissue token. You can also ensure that the client name of the host matches the
one in the above listing.
Recommended Action: To deploy a certificate using this new name, you need to
provide a reissue token for the existing host ID. For successful re-installation using
the new host name, ensure the following:
■
The certificate is revoked if it is active.
■
The host names are mapped to the associated host ID. In the NetBackup
Administration Console, use the Security Management > Host Management
> Hosts tab or the nbhostmgmt command to add mappings.
■
Ensure that the client name for the host matches the primary host name
associated with the issued host ID.
489
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 6000
Message: The provided path is not whitelisted
Explanation: A NetBackup host displays this code if it is not allowed to access
the provided path.
Recommended Action: Veritas recommends using the NetBackup default paths
for progress logs or rename file options; for example, use the user_ops folder. If
you cannot use the NetBackup default path in your setup, you should add custom
paths to the NetBackup configuration. For more information on how to add a custom
path, see "BPCD_WHITELIST_PATH option for NetBackup servers and clients" in
the NetBackup Administrator's Guide, Volume I.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 6530
Message: Unable to start SharePoint web service on server
Explanation: The NetBackup SharePoint GRT web service,
Veritas.NetBackup.SPServiceHost.exe, does not start on the front-end server.
Recommended Action: The SharePoint GRT web service,
Veritas.NetBackup.SPServiceHost.exe, is deployed by default on the NetBackup
clients and starts only during the restores of SharePoint 2016 backups. After the
restore is completed, the web service is stopped.
Verify that SharePoint 2016 has been installed correctly on the front-end server.
You can also try to manually start the service,
Veritas.NetBackup.SPServiceHost.exe, from the command line. Verify that the
service starts during the restore and stops after the restore is completed.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 6531
Message: Validation of operating system user/password failed for client
Explanation: The SharePoint credentials are missing or the NetBackup client
service is not running with SharePoint administrator rights.
490
NetBackup status codes
NetBackup status codes
Recommended Action: Configure the SharePoint credentials on all of the nodes
that are used to browse, backup, or restore.
See "Configuring the logon account for the NetBackup Client Service for NetBackup
for SharePoint" in the NetBackup for Microsoft SharePoint Server Administrator’s
Guide.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 6600
Message: The BigData policy job failed. Check and verify that you have entered
valid credentials and provided correct entries for the application server or the backup
hosts.
Explanation: This error occurs when there is an issue with validating a BigData
policy.
Recommended Action: Check and verify that you have entered the valid
credentials, provided correct entries for the application server or the backup hosts,
and resolved any network connectivity issues.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 6601
Message: One or more of the input parameters or arguments are invalid.
Explanation: The input parameter or the argument can become invalid for the
following reasons:
■
An incorrect or no value is specified for the application server or the backup
host.
■
NetBackup could not reach the application server or the backup host.
■
NetBackup could not find the object to complete the job.
■
An appropriate plug-in is currently unavailable.
Recommended Action: Check and verify that you have entered valid credentials
and provided the correct entries for the application server or the backup host. Ensure
that the BigData framework libraries are correctly installed on the computer.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
491
NetBackup status codes
NetBackup status codes
NetBackup status code: 6602
Message: Insufficient memory or inadequate resources available to complete the
job.
Explanation: This error occurs because of the following reasons:
■
The memory allocation to the system is insufficient.
■
The resources that are available to the system are inadequate.
Recommended Action: Ensure that sufficient memory is allocated and adequate
resources are available to the system.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 6603
Message: Cannot complete the operation. Access to the server is denied due to
a lack of system permissions.
Explanation: The user does not have the permissions that are required to complete
an operation.
Recommended Action: Check to see if the user has the required permissions to
access the application server and to complete a backup or restore operation. Ensure
that you have added the backup host to the relevant access lists.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 6604
Message: Failed to complete the operation. The number of open objects on the
server has reached its limit.
Explanation: There are multiple concurrent jobs running on the application server.
Recommended Action: Increase the limit of open objects. To increase the limit
of open objects, see the appropriate plug-in support guide. Alternatively, you can
check the open file settings on the backup host. For example, ulimit -n on UNIX
systems.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 6605
Message: Unable to process the request because the server resources are busy.
492
NetBackup status codes
NetBackup status codes
Explanation: The server resources are either busy or unavailable and this causes
the job to fail.
Recommended Action: Retry the operation.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 6606
Message: Failed to complete the operation. The object already exists.
Explanation: The file system folder or the virtual machine already exists.
Recommended Action: Do the following, as appropriate:
■
If one or more virtual machines exist with the same name, you can either rename
or delete one of the virtual machines.
■
Check the NetBackup logs (bpbkar logs or nbappdiscv logs) for more
information.
■
In addition, you may want to remove the relevant state file.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 6607
Message: The version of NetBackup does not match the version of the BigData
framework libraries.
Explanation: There is a version mismatch between NetBackup and the BigData
framework libraries.
Recommended Action: Ensure that NetBackup and the BigData framework
libraries are correctly installed.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 6608
Message: The version of NetBackup does not match the version of the plug-in
libraries.
Explanation: There is a version mismatch between NetBackup and the plug-in
libraries for BigData applications.
493
NetBackup status codes
NetBackup status codes
Recommended Action: Ensure that NetBackup and the relevant plug-in libraries
are correctly installed.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 6609
Message: The NetBackup plug-in cannot complete the operation because the
object is invalid.
Explanation: This error can occur because of the following reasons:
■
The application type is either not specified or its value is empty.
■
An appropriate plug-in may not be available to complete the operation.
Recommended Action: Do the following, as appropriate:
■
Check and verify that you have entered the correct entries for the application
server or the backup hosts.
■
Ensure that you have installed the correct plug-in to successfully complete the
operation.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 6610
Message: An internal error occurred in the NetBackup processes.
Explanation: There is an internal error in the NetBackup processes.
Recommended Action: Check the NetBackup debug logs for more information.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 6612
Message: Unable to process the request because the server resources are either
busy or unavailable. Retry the operation.
Explanation: The application server or the backup host is either busy or
unavailable.
Recommended Action: Retry the operation.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
494
NetBackup status codes
NetBackup status codes
NetBackup status code: 6614
Message: Failed to complete the operation.
Explanation: The application server or the backup host shuts down abruptly or
crashes while a job is in progress.
Recommended Action: Retry the operation after the system is up and running.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 6616
Message: The operation type is currently not supported.
Explanation: This error can occur because of the following reasons:
■
The selected schedule type is not supported.
■
The application server does not support the operation. For example, the snapshot
operation may not be supported for certain directories.
Recommended Action: Ensure the plug-in supports the type of backups or
operations that you are trying to complete.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 6617
Message: A system call failed.
Explanation: An internal error occurred in the application server or the operating
system.
Recommended Action: Check the system logs or the operating system logs for
more details.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 6618
Message: NetBackup cannot find the file to complete the operation.
Explanation: A file that needs to be backed up is not found or the access
permission to the file has changed.
Recommended Action: Verify the location of the file. Check if the file was deleted
during the backup job. Ensure that the file has the required access permissions.
495
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 6619
Message: An error occurred because of a network connectivity issue.
Explanation: A network problem caused a socket read failure.
Recommended Action: To resolve the network connectivity issues, check the
system logs and try again.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 6620
Message: The server has exceeded its connection limit.
Explanation: The server has reached the maximum limit of open connections.
Recommended Action: Increase the limit of open objects. To increase the limit
of open objects, see the appropriate plug-in support guide. Alternatively, you can
check the open file settings on the backup host. For example, ulimit -n on UNIX
systems.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 6621
Message: An error occurred because the network protocol is not supported.
Explanation: The protocol used to communicate with the application server may
not be supported.
Recommended Action: Verify and resolve any network connectivity issues. To
resolve the network connectivity issues, check the system logs and try again.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 6622
Message: An internal error occurred in the NetBackup process.
Explanation: An internal error occurred in the NetBackup process.
Recommended Action: Check the NetBackup logs for more details.
496
NetBackup status codes
NetBackup status codes
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 6623
Message: Failed to connect to the application server or the backup host. The
server is either shut down or not reachable.
Explanation: This error can occur because of the following reasons:
■
The application server is either shut down or it is not reachable.
■
The application server was unable to establish a connection with the backup
host.
Recommended Action: Verify and resolve any network connectivity issues. Ensure
that the application server and the backup host are up and running.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 6625
Message: The backup host is either unauthorized to complete the operation or it
is unable to establish a connection with the application server.
Explanation: This error can occur because of the following reasons:
■
The backup host is not authorized to complete an operation.
■
The backup host cannot establish a connection with the application server.
■
The backup host is not added to the relevant access lists.
Recommended Action: Ensure the following:
■
The backup host has the required permissions.
■
The firewall issue between the backup host and the application server is resolved.
■
The backup host is added to the relevant access lists.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 6626
Message: The server name is invalid.
Explanation: The name of the application server is incorrect or invalid.
497
NetBackup status codes
NetBackup status codes
Recommended Action: Ensure that you have provided the correct name for the
application server.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 6628
Message: Unable to establish a network connection due to an error with the Domain
Name Service (DNS).
Explanation: There is an error within the DNS.
Recommended Action: Verify and resolve any network connectivity issues or
DNS issues. To resolve the network connectivity issues, check the system logs and
try again.
Click here to view technical notes and other information in the Veritas Knowledge
Base about this status code.
NetBackup status code: 6629
Message: Unable to complete the operation. Failed to authorize the user or the
server.
Explanation: The user or the server is unauthorized to complete an operation.
Recommended Action: Ensure that the user has the required permissions and
that the server (application server or a backup host) is added to the relevant access
lists.
Click