NetBackup™ Status Codes

Reference Guide

UNIX, Windows, and Linux

Release 10.2
NetBackup™ Status Codes Reference Guide
Last updated: 2023-03-16

Legal Notice
Copyright © 2023 Veritas Technologies LLC. All rights reserved.

Veritas, the Veritas Logo, Veritas Alta, 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

2625 Augustine Drive
Santa Clara, CA 95054

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) [email protected]

Japan [email protected]

Documentation
Make sure that you have the current version of the documentation. Each document displays
the date of the last update on page 2. 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:

[email protected]

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 ................................................. 82

NetBackup status codes ................................................................ 82

NetBackup status code: 0 ........................................................ 82
NetBackup status code: 1 ........................................................ 83
NetBackup status code: 2 ........................................................ 88
NetBackup status code: 3 ........................................................ 89
NetBackup status code: 4 ........................................................ 89
NetBackup status code: 5 ........................................................ 89
NetBackup status code: 6 ........................................................ 91
NetBackup status code: 7 ........................................................ 94
NetBackup status code: 8 ........................................................ 94
NetBackup status code: 9 ........................................................ 94
NetBackup status code: 10 ....................................................... 95
NetBackup status code: 11 ....................................................... 95
NetBackup status code: 12 ....................................................... 97
NetBackup status code: 13 ....................................................... 99
NetBackup status code: 14 ..................................................... 102
NetBackup status code: 15 ..................................................... 103
NetBackup status code: 16 ..................................................... 103
NetBackup status code: 17 ..................................................... 103
NetBackup status code: 18 ..................................................... 104
NetBackup status code: 19 ..................................................... 104
NetBackup status code: 20 ..................................................... 105
NetBackup status code: 21 ..................................................... 108
NetBackup status code: 22 ..................................................... 108
NetBackup status code: 23 ..................................................... 109
NetBackup status code: 24 ..................................................... 109
NetBackup status code: 25 ..................................................... 110
NetBackup status code: 26 ..................................................... 114
NetBackup status code: 27 ..................................................... 115
NetBackup status code: 28 ..................................................... 115
NetBackup status code: 29 ..................................................... 116
NetBackup status code: 30 ..................................................... 116
NetBackup status code: 31 ..................................................... 116
NetBackup status code: 32 ..................................................... 117
NetBackup status code: 33 ..................................................... 117
 Contents 5

NetBackup status code: 34 ..................................................... 117

NetBackup status code: 35 ..................................................... 118
NetBackup status code: 36 ..................................................... 118
NetBackup status code: 37 ..................................................... 118
NetBackup status code: 38 ..................................................... 119
NetBackup status code: 39 ..................................................... 120
NetBackup status code: 40 ..................................................... 120
NetBackup status code: 41 ..................................................... 121
NetBackup status code: 42 ..................................................... 125
NetBackup status code: 43 ..................................................... 125
NetBackup status code: 44 ..................................................... 125
NetBackup status code: 45 ..................................................... 126
NetBackup status code: 46 ..................................................... 126
NetBackup status code: 47 ..................................................... 128
NetBackup status code: 48 ..................................................... 128
NetBackup status code: 49 ..................................................... 129
NetBackup status code: 50 ..................................................... 129
NetBackup status code: 51 ..................................................... 131
NetBackup status code: 52 ..................................................... 132
NetBackup status code: 53 ..................................................... 132
NetBackup status code: 54 ..................................................... 133
NetBackup status code: 55 ..................................................... 134
NetBackup status code: 56 ..................................................... 134
NetBackup status code: 57 ..................................................... 134
NetBackup status code: 58 ..................................................... 135
NetBackup status code: 59 ..................................................... 136
NetBackup status code: 60 ..................................................... 138
NetBackup status code: 61 ..................................................... 138
NetBackup status code: 63 ..................................................... 139
NetBackup status code: 64 ..................................................... 139
NetBackup status code: 65 ..................................................... 140
NetBackup status code: 66 ..................................................... 140
NetBackup status code: 67 ..................................................... 141
NetBackup status code: 68 ..................................................... 141
NetBackup status code: 69 ..................................................... 142
NetBackup status code: 70 ..................................................... 143
NetBackup status code: 71 ..................................................... 143
NetBackup status code: 72 ..................................................... 144
NetBackup status code: 73 ..................................................... 144
NetBackup status code: 74 ..................................................... 144
NetBackup status code: 75 ..................................................... 145
NetBackup status code: 76 ..................................................... 145
NetBackup status code: 77 ..................................................... 145
 Contents 6

NetBackup status code: 78 ..................................................... 146

NetBackup status code: 79 ..................................................... 146
NetBackup status code: 80 ..................................................... 147
NetBackup status code: 81 ..................................................... 147
NetBackup status code: 82 ..................................................... 148
NetBackup status code: 83 ..................................................... 148
NetBackup status code: 84 ..................................................... 149
NetBackup status code: 85 ..................................................... 151
NetBackup status code: 86 ..................................................... 152
NetBackup status code: 87 ..................................................... 153
NetBackup status code: 88 ..................................................... 153
NetBackup status code: 89 ..................................................... 154
NetBackup status code: 90 ..................................................... 155
NetBackup status code: 91 .................................................... 156
NetBackup status code: 92 .................................................... 156
NetBackup status code: 93 .................................................... 157
NetBackup status code: 94 ..................................................... 158
NetBackup status code: 95 .................................................... 158
NetBackup status code: 96 .................................................... 159
NetBackup status code: 97 .................................................... 161
NetBackup status code: 98 ..................................................... 161
NetBackup status code: 99 ..................................................... 162
NetBackup status code: 100 ................................................... 162
NetBackup status code: 101 ................................................... 163
NetBackup status code: 102 ................................................... 163
NetBackup status code: 103 ................................................... 163
NetBackup status code: 104 ................................................... 164
NetBackup status code: 105 ................................................... 164
NetBackup status code: 106 ................................................... 164
NetBackup status code: 108 ................................................... 165
NetBackup status code: 109 ................................................... 165
NetBackup status code: 110 .................................................... 166
NetBackup status code: 111 .................................................... 166
NetBackup status code: 112 .................................................... 167
NetBackup status code: 114 .................................................... 168
NetBackup status code: 116 .................................................... 168
NetBackup status code: 117 .................................................... 169
NetBackup status code: 118 .................................................... 171
NetBackup status code: 120 ................................................... 172
NetBackup status code: 121 ................................................... 173
NetBackup status code: 122 ................................................... 173
NetBackup status code: 123 ................................................... 173
NetBackup status code: 124 ................................................... 174
 Contents 7

NetBackup status code: 125 ................................................... 174

NetBackup status code: 126 ................................................... 174
NetBackup status code: 127 ................................................... 175
NetBackup status code: 128 ................................................... 175
NetBackup status code: 129 ................................................... 175
NetBackup status code: 130 ................................................... 176
NetBackup status code: 131 ................................................... 177
NetBackup status code: 132 ................................................... 178
NetBackup status code: 133 ................................................... 178
NetBackup status code: 134 ................................................... 179
NetBackup status code: 135 ................................................... 180
NetBackup status code: 136 ................................................... 180
NetBackup status code: 140 ................................................... 181
NetBackup status code: 141 ................................................... 181
NetBackup status code: 142 ................................................... 181
NetBackup status code: 143 ................................................... 182
NetBackup status code: 144 ................................................... 182
NetBackup status code: 145 ................................................... 183
NetBackup status code: 146 ................................................... 183
NetBackup status code: 147 ................................................... 184
NetBackup status code: 148 ................................................... 184
NetBackup status code: 149 ................................................... 184
NetBackup status code: 150 ................................................... 185
NetBackup status code: 152 ................................................... 185
NetBackup status code: 153 ................................................... 185
NetBackup status code: 154 ................................................... 185
NetBackup status code: 155 ................................................... 186
NetBackup status code: 156 ................................................... 186
NetBackup status code: 157 ................................................... 188
NetBackup status code: 158 ................................................... 188
NetBackup status code: 159 ................................................... 188
NetBackup status code: 160 ................................................... 189
NetBackup status code: 161 ................................................... 190
NetBackup status code: 162 ................................................... 190
NetBackup status code: 163 ................................................... 191
NetBackup status code: 164 ................................................... 191
NetBackup status code: 165 ................................................... 191
NetBackup status code: 166 ................................................... 192
NetBackup status code: 167 ................................................... 192
NetBackup status code: 168 ................................................... 192
NetBackup status code: 169 ................................................... 193
NetBackup status code: 170 ................................................... 193
NetBackup status code: 171 ................................................... 195
 Contents 8

NetBackup status code: 172 ................................................... 195

NetBackup status code: 173 ................................................... 195
NetBackup status code: 174 ................................................... 196
NetBackup status code: 175 ................................................... 197
NetBackup status code: 176 ................................................... 198
NetBackup status code: 177 ................................................... 199
NetBackup status code: 178 ................................................... 199
NetBackup status code: 179 ................................................... 199
NetBackup status code: 180 ................................................... 200
NetBackup status code: 181 ................................................... 200
NetBackup status code: 182 ................................................... 200
NetBackup status code: 183 ................................................... 201
NetBackup status code: 184 ................................................... 201
NetBackup status code: 185 ................................................... 202
NetBackup status code: 186 ................................................... 203
NetBackup status code: 189 ................................................... 203
NetBackup status code: 190 ................................................... 204
NetBackup status code: 191 ................................................... 204
NetBackup status code: 192 ................................................... 206
NetBackup status code: 193 ................................................... 206
NetBackup status code: 194 ................................................... 207
NetBackup status code: 195 ................................................... 207
NetBackup status code: 196 ................................................... 208
NetBackup status code: 197 ................................................... 208
NetBackup status code: 198 ................................................... 208
NetBackup status code: 199 ................................................... 209
NetBackup status code: 200 ................................................... 209
NetBackup status code: 201 ................................................... 210
NetBackup status code: 202 ................................................... 211
NetBackup status code: 203 ................................................... 212
NetBackup status code: 204 ................................................... 213
NetBackup status code: 205 ................................................... 215
NetBackup status code: 206 ................................................... 216
NetBackup status code: 207 ................................................... 217
NetBackup status code: 209 ................................................... 217
NetBackup status code: 210 ................................................... 218
NetBackup status code: 212 ................................................... 218
NetBackup status code: 213 ................................................... 218
NetBackup status code: 215 ................................................... 219
NetBackup status code: 216 ................................................... 220
NetBackup status code: 217 ................................................... 220
NetBackup status code: 218 ................................................... 221
NetBackup status code: 219 ................................................... 221
 Contents 9

NetBackup status code: 220 ................................................... 222

NetBackup status code: 221 ................................................... 223
NetBackup status code: 222 ................................................... 223
NetBackup status code: 223 ................................................... 224
NetBackup status code: 224 ................................................... 224
NetBackup status code: 225 ................................................... 224
NetBackup status code: 226 ................................................... 225
NetBackup status code: 227 ................................................... 225
NetBackup status code: 228 ................................................... 225
NetBackup status code: 229 ................................................... 226
NetBackup status code: 230 ................................................... 226
NetBackup status code: 231 ................................................... 226
NetBackup status code: 232 ................................................... 226
NetBackup status code: 233 ................................................... 227
NetBackup status code: 234 ................................................... 227
NetBackup status code: 235 ................................................... 227
NetBackup status code: 236 ................................................... 228
NetBackup status code: 237 ................................................... 228
NetBackup status code: 238 ................................................... 229
NetBackup status code: 239 ................................................... 229
NetBackup status code: 240 ................................................... 229
NetBackup status code: 241 ................................................... 229
NetBackup status code: 242 ................................................... 230
NetBackup status code: 243 ................................................... 230
NetBackup status code: 245 ................................................... 230
NetBackup status code: 246 ................................................... 231
NetBackup status code: 247 ................................................... 231
NetBackup status code: 248 ................................................... 231
NetBackup status code: 249 ................................................... 231
NetBackup status code: 250 ................................................... 232
NetBackup status code: 251 ................................................... 232
NetBackup status code: 252 ................................................... 232
NetBackup status code: 253 ................................................... 233
NetBackup status code: 254 ................................................... 233
NetBackup status code: 256 ................................................... 233
NetBackup status code: 257 ................................................... 233
NetBackup status code: 258 ................................................... 234
NetBackup status code: 259 ................................................... 234
NetBackup status code: 260 ................................................... 234
NetBackup status code: 261 ................................................... 234
NetBackup status code: 262 ................................................... 235
NetBackup status code: 263 ................................................... 235
NetBackup status code: 265 ................................................... 235
 Contents 10

NetBackup status code: 266 ................................................... 236

NetBackup status code: 267 ................................................... 236
NetBackup status code: 268 ................................................... 236
NetBackup status code: 269 ................................................... 237
NetBackup status code: 270 ................................................... 237
NetBackup status code: 271 ................................................... 237
NetBackup status code: 272 ................................................... 238
NetBackup status code: 273 ................................................... 238
NetBackup status code: 274 ................................................... 238
NetBackup status code: 275 ................................................... 239
NetBackup status code: 276 ................................................... 239
NetBackup status code: 277 ................................................... 239
NetBackup status code: 278 ................................................... 239
NetBackup status code: 279 ................................................... 240
NetBackup status code: 280 ................................................... 240
NetBackup status code: 281 ................................................... 240
NetBackup status code: 282 ................................................... 240
NetBackup status code: 283 ................................................... 241
NetBackup status code: 284 ................................................... 241
NetBackup status code: 285 ................................................... 242
NetBackup status code: 286 ................................................... 242
NetBackup status code: 287 ................................................... 242
NetBackup status code: 288 ................................................... 242
NetBackup status code: 289 ................................................... 243
NetBackup status code: 290 ................................................... 243
NetBackup status code: 291 ................................................... 244
NetBackup status code: 292 ................................................... 244
NetBackup status code: 293 ................................................... 245
NetBackup status code: 294 ................................................... 246
NetBackup status code: 295 ................................................... 246
NetBackup status code: 296 ................................................... 247
NetBackup status code: 297 ................................................... 247
NetBackup status code: 298 ................................................... 248
NetBackup status code: 299 ................................................... 248
NetBackup status code: 300 ................................................... 248
NetBackup status code: 301 ................................................... 249
NetBackup status code: 302 ................................................... 250
NetBackup status code: 303 ................................................... 250
NetBackup status code: 304 ................................................... 251
NetBackup status code: 305 ................................................... 251
NetBackup status code: 306 ................................................... 251
NetBackup status code: 307 ................................................... 252
NetBackup status code: 308 ................................................... 252
 Contents 11

NetBackup status code: 309 ................................................... 253

NetBackup status code: 310 ................................................... 253
NetBackup status code: 311 .................................................... 253
NetBackup status code: 312 ................................................... 254
NetBackup status code: 313 ................................................... 254
NetBackup status code: 314 ................................................... 254
NetBackup status code: 315 ................................................... 255
NetBackup status code: 316 ................................................... 255
NetBackup status code: 317 ................................................... 255
NetBackup status code: 318 ................................................... 256
NetBackup status code: 319 ................................................... 256
NetBackup status code: 320 ................................................... 256
NetBackup status code: 321 ................................................... 257
NetBackup status code: 322 ................................................... 257
NetBackup status code: 323 ................................................... 257
NetBackup status code: 324 ................................................... 258
NetBackup status code: 325 ................................................... 258
NetBackup status code: 326 ................................................... 259
NetBackup status code: 327 ................................................... 259
NetBackup status code: 328 ................................................... 259
NetBackup status code: 329 ................................................... 260
NetBackup status code: 330 ................................................... 260
NetBackup status code: 331 ................................................... 260
NetBackup status code: 332 ................................................... 261
NetBackup status code: 333 ................................................... 261
NetBackup status code: 334 ................................................... 261
NetBackup status code: 335 ................................................... 262
NetBackup status code: 336 ................................................... 262
NetBackup status code: 337 ................................................... 262
NetBackup status code: 338 ................................................... 262
NetBackup status code: 339 ................................................... 263
NetBackup status code: 340 ................................................... 263
NetBackup status code: 341 ................................................... 263
NetBackup status code: 342 ................................................... 263
NetBackup status code: 343 ................................................... 264
NetBackup status code: 344 ................................................... 264
NetBackup status code: 345 ................................................... 264
NetBackup status code: 346 ................................................... 265
NetBackup status code: 347 ................................................... 265
NetBackup status code: 348 ................................................... 265
NetBackup status code: 349 ................................................... 265
NetBackup status code: 350 ................................................... 266
NetBackup status code: 351 ................................................... 266
 Contents 12

NetBackup status code: 400 ................................................... 266

NetBackup status code: 401 ................................................... 267
NetBackup status code: 402 ................................................... 267
NetBackup status code: 403 ................................................... 267
NetBackup status code: 404 ................................................... 268
NetBackup status code: 405 ................................................... 268
NetBackup status code: 406 ................................................... 269
NetBackup status code: 407 ................................................... 269
NetBackup status code: 408 ................................................... 270
NetBackup status code: 409 ................................................... 270
NetBackup status code: 410 ................................................... 270
NetBackup status code: 411 .................................................... 270
NetBackup status code: 412 ................................................... 271
NetBackup status code: 413 ................................................... 271
NetBackup status code: 501 ................................................... 271
NetBackup status code: 502 ................................................... 272
NetBackup status code: 503 ................................................... 272
NetBackup status code: 504 ................................................... 272
NetBackup status code: 505 ................................................... 273
NetBackup status code: 506 ................................................... 273
NetBackup status code: 507 ................................................... 274
NetBackup status code: 508 ................................................... 275
NetBackup status code: 509 ................................................... 275
NetBackup status code: 510 ................................................... 276
NetBackup status code: 511 ................................................... 276
NetBackup status code: 512 ................................................... 277
NetBackup status code: 513 ................................................... 277
NetBackup status code: 514 ................................................... 278
NetBackup status code: 516 ................................................... 278
NetBackup status code: 517 ................................................... 279
NetBackup status code: 518 ................................................... 279
NetBackup status code: 519 ................................................... 280
NetBackup status code: 520 ................................................... 280
NetBackup status code: 521 ................................................... 280
NetBackup status code: 522 ................................................... 281
NetBackup status code: 523 ................................................... 281
NetBackup status code: 525 ................................................... 282
NetBackup status code: 526 ................................................... 282
NetBackup status code: 527 ................................................... 283
NetBackup status code: 537 ................................................... 283
NetBackup status code: 538 ................................................... 283
NetBackup status code: 552 ................................................... 284
NetBackup status code: 555 ................................................... 284
 Contents 13

NetBackup status code: 600 ................................................... 284

NetBackup status code: 601 ................................................... 285
NetBackup status code: 602 ................................................... 285
NetBackup status code: 603 ................................................... 286
NetBackup status code: 604 ................................................... 286
NetBackup status code: 605 ................................................... 286
NetBackup status code: 606 ................................................... 287
NetBackup status code: 607 ................................................... 287
NetBackup status code: 608 ................................................... 287
NetBackup status code: 609 ................................................... 288
NetBackup status code: 610 ................................................... 288
NetBackup status code: 611 ................................................... 289
NetBackup status code: 612 ................................................... 289
NetBackup status code: 613 ................................................... 289
NetBackup status code: 614 ................................................... 290
NetBackup status code: 615 ................................................... 290
NetBackup status code: 616 ................................................... 291
NetBackup status code: 617 ................................................... 291
NetBackup status code: 618 ................................................... 291
NetBackup status code: 619 ................................................... 291
NetBackup status code: 620 ................................................... 292
NetBackup status code: 621 ................................................... 292
NetBackup status code: 622 ................................................... 292
NetBackup status code: 623 ................................................... 293
NetBackup status code: 624 ................................................... 293
NetBackup status code: 625 ................................................... 294
NetBackup status code: 626 ................................................... 294
NetBackup status code: 627 ................................................... 294
NetBackup status code: 628 ................................................... 295
NetBackup status code: 629 ................................................... 295
NetBackup status code: 630 ................................................... 295
NetBackup status code: 631 ................................................... 296
NetBackup status code: 632 ................................................... 296
NetBackup status code: 633 ................................................... 297
NetBackup status code: 634 ................................................... 297
NetBackup status code: 635 ................................................... 297
NetBackup status code: 636 ................................................... 298
NetBackup status code: 637 ................................................... 298
NetBackup status code: 638 ................................................... 299
NetBackup status code: 639 ................................................... 299
NetBackup status code: 640 ................................................... 299
NetBackup status code: 641 ................................................... 300
NetBackup status code: 642 ................................................... 300
 Contents 14

NetBackup status code: 643 ................................................... 301

NetBackup status code: 644 ................................................... 301
NetBackup status code: 645 ................................................... 301
NetBackup status code: 646 ................................................... 302
NetBackup status code: 647 ................................................... 303
NetBackup status code: 648 ................................................... 303
NetBackup status code: 649 ................................................... 304
NetBackup status code: 650 ................................................... 304
NetBackup status code: 651 ................................................... 304
NetBackup status code: 652 ................................................... 305
NetBackup status code: 653 ................................................... 305
NetBackup status code: 654 ................................................... 305
NetBackup status code: 655 ................................................... 306
NetBackup status code: 656 ................................................... 306
NetBackup status code: 657 ................................................... 306
NetBackup status code: 658 ................................................... 307
NetBackup status code: 659 ................................................... 307
NetBackup status code: 660 ................................................... 308
NetBackup status code: 661 ................................................... 308
NetBackup status code: 662 ................................................... 309
NetBackup status code: 663 ................................................... 309
NetBackup status code: 664 ................................................... 309
NetBackup status code: 665 ................................................... 310
NetBackup status code: 667 ................................................... 310
NetBackup status code: 668 ................................................... 310
NetBackup status code: 669 ................................................... 311
NetBackup status code: 670 ................................................... 311
NetBackup status code: 671 ................................................... 311
NetBackup status code: 800 ................................................... 312
NetBackup status code: 801 ................................................... 312
NetBackup status code: 802 ................................................... 313
NetBackup status code: 803 ................................................... 313
NetBackup status code: 805 ................................................... 314
NetBackup status code: 806 ................................................... 315
NetBackup status code: 807 ................................................... 315
NetBackup status code: 811 ................................................... 315
NetBackup status code: 812 ................................................... 316
NetBackup status code: 813 ................................................... 316
NetBackup status code: 818 ................................................... 316
NetBackup status code: 819 ................................................... 317
NetBackup status code: 823 ................................................... 317
NetBackup status code: 830 ................................................... 318
NetBackup status code: 831 ................................................... 318
 Contents 15

NetBackup status code: 832 ................................................... 318

NetBackup status code: 833 ................................................... 319
NetBackup status code: 859 ................................................... 319
NetBackup status code: 860 ................................................... 320
NetBackup status code: 861 ................................................... 320
NetBackup status code: 900 ................................................... 320
NetBackup status code: 901 ................................................... 321
NetBackup status code: 902 ................................................... 321
NetBackup status code: 903 ................................................... 321
NetBackup status code: 904 ................................................... 322
NetBackup status code: 905 ................................................... 322
NetBackup status code: 906 ................................................... 322
NetBackup status code: 907 ................................................... 323
NetBackup status code: 908 ................................................... 323
NetBackup status code: 912 ................................................... 324
NetBackup status code: 914 ................................................... 324
NetBackup status code: 915 ................................................... 324
NetBackup status code: 916 ................................................... 325
NetBackup status code: 917 ................................................... 325
NetBackup status code: 918 ................................................... 325
NetBackup status code: 925 ................................................... 326
NetBackup status code: 927 ................................................... 326
NetBackup status code: 928 ................................................... 326
NetBackup status code: 1000 .................................................. 327
NetBackup status code: 1001 .................................................. 327
NetBackup status code: 1002 .................................................. 328
NetBackup status code: 1004 .................................................. 328
NetBackup status code: 1005 .................................................. 328
NetBackup status code: 1006 .................................................. 329
NetBackup status code: 1007 .................................................. 329
NetBackup status code: 1008 .................................................. 329
NetBackup status code: 1009 .................................................. 330
NetBackup status code: 1010 .................................................. 330
NetBackup status code: 1011 .................................................. 330
NetBackup status code: 1012 .................................................. 330
NetBackup status code: 1013 .................................................. 331
NetBackup status code: 1014 .................................................. 331
NetBackup status code: 1019 .................................................. 331
NetBackup status code: 1020 .................................................. 332
NetBackup status code: 1021 .................................................. 332
NetBackup status code: 1022 .................................................. 332
NetBackup status code: 1023 .................................................. 333
NetBackup status code: 1024 .................................................. 334
 Contents 16

NetBackup status code: 1057 .................................................. 334

NetBackup status code: 1058 .................................................. 334
NetBackup status code: 1227 .................................................. 334
NetBackup status code: 1229 .................................................. 335
NetBackup status code: 1260 .................................................. 336
NetBackup status code: 1288 .................................................. 336
NetBackup status code: 1289 .................................................. 337
NetBackup status code: 1290 .................................................. 338
NetBackup status code: 1291 .................................................. 338
NetBackup status code: 1292 .................................................. 338
NetBackup status code: 1293 .................................................. 339
NetBackup status code: 1294 .................................................. 339
NetBackup status code: 1295 .................................................. 340
NetBackup status code: 1296 .................................................. 340
NetBackup status code: 1297 .................................................. 340
NetBackup status code: 1298 .................................................. 340
NetBackup status code: 1299 .................................................. 341
NetBackup status code: 1401 .................................................. 342
NetBackup status code: 1402 .................................................. 342
NetBackup status code: 1403 .................................................. 342
NetBackup status code: 1405 .................................................. 342
NetBackup status code: 1407 .................................................. 343
NetBackup status code: 1408 .................................................. 343
NetBackup status code: 1409 .................................................. 343
NetBackup status code: 1410 .................................................. 343
NetBackup status code: 1411 .................................................. 344
NetBackup status code: 1412 .................................................. 344
NetBackup status code: 1413 .................................................. 344
NetBackup status code: 1414 .................................................. 344
NetBackup status code: 1415 .................................................. 344
NetBackup status code: 1416 .................................................. 345
NetBackup status code: 1417 .................................................. 345
NetBackup status code: 1418 .................................................. 345
NetBackup status code: 1419 .................................................. 345
NetBackup status code: 1420 .................................................. 346
NetBackup status code: 1421 .................................................. 346
NetBackup status code: 1422 .................................................. 346
NetBackup status code: 1423 .................................................. 346
NetBackup status code: 1425 .................................................. 347
NetBackup status code: 1426 .................................................. 347
NetBackup status code: 1500 .................................................. 347
NetBackup status code: 1501 .................................................. 347
NetBackup status code: 1502 .................................................. 348
 Contents 17

NetBackup status code: 1503 .................................................. 349

NetBackup status code: 1504 .................................................. 349
NetBackup status code: 1505 .................................................. 350
NetBackup status code: 1506 .................................................. 350
NetBackup status code: 1507 .................................................. 350
NetBackup status code: 1508 .................................................. 351
NetBackup status code: 1509 .................................................. 351
NetBackup status code: 1510 .................................................. 351
NetBackup status code: 1511 .................................................. 351
NetBackup status code: 1512 .................................................. 352
NetBackup status code: 1513 .................................................. 352
NetBackup status code: 1514 .................................................. 352
NetBackup status code: 1515 .................................................. 353
NetBackup status code: 1516 .................................................. 353
NetBackup status code: 1517 .................................................. 353
NetBackup status code: 1518 .................................................. 354
NetBackup status code: 1519 .................................................. 354
NetBackup status code: 1521 .................................................. 354
NetBackup status code: 1522 .................................................. 355
NetBackup status code: 1523 .................................................. 355
NetBackup status code: 1524 .................................................. 355
NetBackup status code: 1525 .................................................. 356
NetBackup status code: 1526 .................................................. 356
NetBackup status code: 1527 .................................................. 356
NetBackup status code: 1528 .................................................. 357
NetBackup status code: 1529 .................................................. 357
NetBackup status code: 1530 .................................................. 358
NetBackup status code: 1531 .................................................. 358
NetBackup status code: 1532 .................................................. 359
NetBackup status code: 1533 .................................................. 359
NetBackup status code: 1534 .................................................. 360
NetBackup status code: 1535 .................................................. 360
NetBackup status code: 1536 .................................................. 361
NetBackup status code: 1537 .................................................. 361
NetBackup status code: 1538 .................................................. 362
NetBackup status code: 1539 .................................................. 362
NetBackup status code: 1540 .................................................. 362
NetBackup status code: 1541 .................................................. 363
NetBackup status code: 1542 .................................................. 363
NetBackup status code: 1543 .................................................. 363
NetBackup status code: 1545 .................................................. 364
NetBackup status code: 1546 .................................................. 364
NetBackup status code: 1547 .................................................. 364
 Contents 18

NetBackup status code: 1548 .................................................. 364

NetBackup status code: 1549 .................................................. 365
NetBackup status code: 1552 .................................................. 365
NetBackup status code: 1553 .................................................. 366
NetBackup status code: 1554 .................................................. 366
NetBackup status code: 1556 .................................................. 367
NetBackup status code: 1557 .................................................. 367
NetBackup status code: 1558 .................................................. 367
NetBackup status code: 1559 .................................................. 368
NetBackup status code: 1560 .................................................. 368
NetBackup status code: 1561 .................................................. 368
NetBackup status code: 1562 .................................................. 369
NetBackup status code: 1563 .................................................. 369
NetBackup status code: 1564 .................................................. 369
NetBackup status code: 1565 .................................................. 370
NetBackup status code: 1566 .................................................. 370
NetBackup status code: 1567 .................................................. 370
NetBackup status code: 1568 .................................................. 370
NetBackup status code: 1569 .................................................. 371
NetBackup status code: 1570 .................................................. 371
NetBackup status code: 1571 .................................................. 371
NetBackup status code: 1572 .................................................. 372
NetBackup status code: 1573 .................................................. 372
NetBackup status code: 1574 .................................................. 373
NetBackup status code: 1575 .................................................. 373
NetBackup status code: 1576 .................................................. 373
NetBackup status code: 1577 .................................................. 373
NetBackup status code: 1578 .................................................. 374
NetBackup status code: 1579 .................................................. 374
NetBackup status code: 1580 .................................................. 374
NetBackup status code: 1581 .................................................. 375
NetBackup status code: 1582 .................................................. 375
NetBackup status code: 1583 .................................................. 375
NetBackup status code: 1584 .................................................. 375
NetBackup status code: 1585 .................................................. 376
NetBackup status code: 1586 .................................................. 376
NetBackup status code: 1587 .................................................. 376
NetBackup status code: 1588 .................................................. 377
NetBackup status code: 1589 .................................................. 377
NetBackup status code: 1590 .................................................. 377
NetBackup status code: 1591 .................................................. 377
NetBackup status code: 1592 .................................................. 378
NetBackup status code: 1593 .................................................. 378
 Contents 19

NetBackup status code: 1594 .................................................. 378

NetBackup status code: 1596 .................................................. 379
NetBackup status code: 1597 .................................................. 379
NetBackup status code: 1598 .................................................. 379
NetBackup status code: 1599 .................................................. 379
NetBackup status code: 1600 .................................................. 380
NetBackup status code: 1601 .................................................. 380
NetBackup status code: 1602 .................................................. 380
NetBackup status code: 1603 .................................................. 381
NetBackup status code: 1604 .................................................. 381
NetBackup status code: 1608 .................................................. 381
NetBackup status code: 1609 .................................................. 382
NetBackup status code: 1610 .................................................. 382
NetBackup status code: 1611 .................................................. 382
NetBackup status code: 1612 .................................................. 383
NetBackup status code: 1613 .................................................. 383
NetBackup status code: 1614 .................................................. 383
NetBackup status code: 1615 .................................................. 383
NetBackup status code: 1616 .................................................. 384
NetBackup status code: 1617 .................................................. 384
NetBackup status code: 1618 .................................................. 384
NetBackup status code: 1630 .................................................. 385
NetBackup status code: 1633 .................................................. 385
NetBackup status code: 1634 .................................................. 385
NetBackup status code: 1635 .................................................. 386
NetBackup status code: 1636 .................................................. 386
NetBackup status code: 1637 .................................................. 386
NetBackup status code: 1800 .................................................. 386
NetBackup status code: 1915 .................................................. 387
NetBackup status code: 1916 .................................................. 387
NetBackup status code: 1917 .................................................. 388
NetBackup status code: 1918 .................................................. 388
NetBackup status code: 1919 .................................................. 388
NetBackup status code: 1920 .................................................. 389
NetBackup status code: 1921 .................................................. 389
NetBackup status code: 1922 .................................................. 390
NetBackup status code: 1924 .................................................. 390
NetBackup status code: 1925 .................................................. 390
NetBackup status code: 1926 .................................................. 390
NetBackup status code: 1927 .................................................. 391
NetBackup status code: 1928 .................................................. 391
NetBackup status code: 1932 .................................................. 391
NetBackup status code: 1933 .................................................. 392
 Contents 20

NetBackup status code: 1946 .................................................. 392

NetBackup status code: 1952 .................................................. 392
NetBackup status code: 1953 .................................................. 393
NetBackup status code: 1954 .................................................. 393
NetBackup status code: 1955 .................................................. 393
NetBackup status code: 1956 .................................................. 393
NetBackup status code: 1957 .................................................. 394
NetBackup status code: 1958 .................................................. 394
NetBackup status code: 1960 .................................................. 395
NetBackup status code: 1961 .................................................. 395
NetBackup status code: 1962 .................................................. 395
NetBackup status code: 1967 .................................................. 396
NetBackup status code: 1968 .................................................. 396
NetBackup status code: 1969 .................................................. 396
NetBackup status code: 1970 .................................................. 396
NetBackup status code: 2000 .................................................. 397
NetBackup status code: 2001 .................................................. 398
NetBackup status code: 2002 .................................................. 398
NetBackup status code: 2003 .................................................. 399
NetBackup status code: 2004 .................................................. 399
NetBackup status code: 2005 .................................................. 399
NetBackup status code: 2006 .................................................. 400
NetBackup status code: 2007 .................................................. 400
NetBackup status code: 2008 .................................................. 401
NetBackup status code: 2009 .................................................. 401
NetBackup status code: 2010 .................................................. 401
NetBackup status code: 2011 .................................................. 402
NetBackup status code: 2012 .................................................. 402
NetBackup status code: 2013 .................................................. 402
NetBackup status code: 2014 .................................................. 403
NetBackup status code: 2015 .................................................. 403
NetBackup status code: 2016 .................................................. 404
NetBackup status code: 2017 .................................................. 404
NetBackup status code: 2018 .................................................. 404
NetBackup status code: 2019 .................................................. 404
NetBackup status code: 2020 .................................................. 405
NetBackup status code: 2021 .................................................. 405
NetBackup status code: 2022 .................................................. 405
NetBackup status code: 2023 .................................................. 406
NetBackup status code: 2024 .................................................. 406
NetBackup status code: 2025 .................................................. 406
NetBackup status code: 2026 .................................................. 407
NetBackup status code: 2027 .................................................. 407
 Contents 21

NetBackup status code: 2028 .................................................. 408

NetBackup status code: 2029 .................................................. 408
NetBackup status code: 2030 .................................................. 409
NetBackup status code: 2031 .................................................. 409
NetBackup status code: 2032 .................................................. 409
NetBackup status code: 2033 .................................................. 410
NetBackup status code: 2034 .................................................. 410
NetBackup status code: 2035 .................................................. 410
NetBackup status code: 2036 .................................................. 411
NetBackup status code: 2037 .................................................. 411
NetBackup status code: 2038 .................................................. 411
NetBackup status code: 2039 .................................................. 412
NetBackup status code: 2040 .................................................. 412
NetBackup status code: 2041 .................................................. 412
NetBackup status code: 2042 .................................................. 412
NetBackup status code: 2043 .................................................. 413
NetBackup status code: 2044 .................................................. 413
NetBackup status code: 2045 .................................................. 413
NetBackup status code: 2046 .................................................. 413
NetBackup status code: 2047 .................................................. 414
NetBackup status code: 2048 .................................................. 414
NetBackup status code: 2049 .................................................. 414
NetBackup status code: 2050 .................................................. 414
NetBackup status code: 2051 .................................................. 415
NetBackup status code: 2052 .................................................. 415
NetBackup status code: 2053 .................................................. 415
NetBackup status code: 2054 .................................................. 416
NetBackup status code: 2055 .................................................. 416
NetBackup status code: 2056 .................................................. 416
NetBackup status code: 2057 .................................................. 416
NetBackup status code: 2058 .................................................. 417
NetBackup status code: 2059 .................................................. 417
NetBackup status code: 2060 .................................................. 417
NetBackup status code: 2061 .................................................. 418
NetBackup status code: 2062 .................................................. 418
NetBackup status code: 2063 .................................................. 418
NetBackup status code: 2064 .................................................. 418
NetBackup status code: 2065 .................................................. 419
NetBackup status code: 2066 .................................................. 419
NetBackup status code: 2067 .................................................. 419
NetBackup status code: 2068 .................................................. 420
NetBackup status code: 2069 .................................................. 420
NetBackup status code: 2070 .................................................. 420
 Contents 22

NetBackup status code: 2071 .................................................. 421

NetBackup status code: 2072 .................................................. 421
NetBackup status code: 2073 .................................................. 421
NetBackup status code: 2074 .................................................. 422
NetBackup status code: 2075 .................................................. 422
NetBackup status code: 2076 .................................................. 422
NetBackup status code: 2078 .................................................. 423
NetBackup status code: 2079 .................................................. 423
NetBackup status code: 2080 .................................................. 423
NetBackup status code: 2081 .................................................. 424
NetBackup status code: 2082 .................................................. 424
NetBackup status code: 2083 .................................................. 424
NetBackup status code: 2084 .................................................. 425
NetBackup status code: 2085 .................................................. 425
NetBackup status code: 2086 .................................................. 425
NetBackup status code: 2087 .................................................. 426
NetBackup status code: 2088 .................................................. 426
NetBackup status code: 2089 .................................................. 426
NetBackup status code: 2090 .................................................. 427
NetBackup status code: 2091 .................................................. 427
NetBackup status code: 2092 .................................................. 428
NetBackup status code: 2093 .................................................. 429
NetBackup status code: 2094 .................................................. 429
NetBackup status code: 2095 .................................................. 430
NetBackup status code: 2096 .................................................. 430
NetBackup status code: 2097 .................................................. 430
NetBackup status code: 2098 .................................................. 431
NetBackup status code: 2099 .................................................. 431
NetBackup status code: 2100 .................................................. 431
NetBackup status code: 2101 .................................................. 431
NetBackup status code: 2102 .................................................. 432
NetBackup status code: 2103 .................................................. 432
NetBackup status code: 2104 .................................................. 432
NetBackup status code: 2105 .................................................. 433
NetBackup status code: 2106 .................................................. 433
NetBackup status code: 2107 .................................................. 434
NetBackup status code: 2108 .................................................. 434
NetBackup status code: 2109 .................................................. 435
NetBackup status code: 2110 .................................................. 435
NetBackup status code: 2111 .................................................. 435
NetBackup status code: 2112 .................................................. 435
NetBackup status code: 2113 .................................................. 436
NetBackup status code: 2114 .................................................. 436
 Contents 23

NetBackup status code: 2205 .................................................. 437

NetBackup status code: 2206 .................................................. 437
NetBackup status code: 2213 .................................................. 438
NetBackup status code: 2300 .................................................. 438
NetBackup status code: 2301 .................................................. 438
NetBackup status code: 2302 .................................................. 439
NetBackup status code: 2303 .................................................. 439
NetBackup status code: 2304 .................................................. 439
NetBackup status code: 2305 .................................................. 440
NetBackup status code: 2306 .................................................. 440
NetBackup status code: 2307 .................................................. 440
NetBackup status code: 2308 .................................................. 440
NetBackup status code: 2309 .................................................. 441
NetBackup status code: 2310 .................................................. 441
NetBackup status code: 2311 .................................................. 441
NetBackup status code: 2312 .................................................. 441
NetBackup status code: 2313 .................................................. 442
NetBackup status code: 2314 .................................................. 442
NetBackup status code: 2317 .................................................. 442
NetBackup status code: 2318 .................................................. 442
NetBackup status code: 2319 .................................................. 443
NetBackup status code: 2320 .................................................. 443
NetBackup status code: 2322 .................................................. 443
NetBackup status code: 2323 .................................................. 444
NetBackup status code: 2324 .................................................. 444
NetBackup status code: 2325 .................................................. 444
NetBackup status code: 2326 .................................................. 445
NetBackup status code: 2328 .................................................. 445
NetBackup status code: 2329 .................................................. 445
NetBackup status code: 2330 .................................................. 445
NetBackup status code: 2331 .................................................. 446
NetBackup status code: 2334 .................................................. 446
NetBackup status code: 2335 .................................................. 446
NetBackup status code: 2336 .................................................. 447
NetBackup status code: 2337 .................................................. 447
NetBackup status code: 2339 .................................................. 447
NetBackup status code: 2340 .................................................. 448
NetBackup status code: 2341 .................................................. 448
NetBackup status code: 2342 .................................................. 448
NetBackup status code: 2343 .................................................. 449
NetBackup status code: 2344 .................................................. 449
NetBackup status code: 2345 .................................................. 450
NetBackup status code: 2346 .................................................. 450
 Contents 24

NetBackup status code: 2347 .................................................. 450

NetBackup status code: 2348 .................................................. 450
NetBackup status code: 2349 .................................................. 451
NetBackup status code: 2351 .................................................. 451
NetBackup status code: 2352 .................................................. 451
NetBackup status code: 2353 .................................................. 451
NetBackup status code: 2354 ................................................. 452
NetBackup status code: 2355 .................................................. 452
NetBackup status code: 2356 .................................................. 452
NetBackup status code: 2357 .................................................. 453
NetBackup status code: 2358 .................................................. 453
NetBackup status code: 2359 .................................................. 453
NetBackup status code: 2360 .................................................. 453
NetBackup status code: 2361 .................................................. 454
NetBackup status code: 2362 .................................................. 454
NetBackup status code: 2363 .................................................. 454
NetBackup status code: 2364 .................................................. 455
NetBackup status code: 2365 .................................................. 455
NetBackup status code: 2367 .................................................. 456
NetBackup status code: 2368 .................................................. 456
NetBackup status code: 2369 .................................................. 456
NetBackup status code: 2370 .................................................. 456
NetBackup status code: 2372 .................................................. 457
NetBackup status code: 2373 .................................................. 457
NetBackup status code: 2374 .................................................. 457
NetBackup status code: 2375 .................................................. 457
NetBackup status code: 2376 .................................................. 458
NetBackup status code: 2377 .................................................. 458
NetBackup status code: 2378 .................................................. 458
NetBackup status code: 2379 .................................................. 458
NetBackup status code: 2380 .................................................. 459
NetBackup status code: 2381 .................................................. 459
NetBackup status code: 2382 .................................................. 459
NetBackup status code: 2383 .................................................. 459
NetBackup status code: 2384 .................................................. 460
NetBackup status code: 2385 .................................................. 460
NetBackup status code: 2386 .................................................. 460
NetBackup status code: 2387 .................................................. 460
NetBackup status code: 2388 .................................................. 461
NetBackup status code: 2389 .................................................. 461
NetBackup status code: 2390 .................................................. 461
NetBackup status code: 2391 .................................................. 462
NetBackup status code: 2392 .................................................. 462
 Contents 25

NetBackup status code: 2393 .................................................. 462

NetBackup status code: 2395 .................................................. 462
NetBackup status code: 2396 .................................................. 463
NetBackup status code: 2397 .................................................. 463
NetBackup status code: 2398 .................................................. 463
NetBackup status code: 2399 .................................................. 464
NetBackup status code: 2400 .................................................. 464
NetBackup status code: 2401 .................................................. 464
NetBackup status code: 2402 .................................................. 465
NetBackup status code: 2450 .................................................. 465
NetBackup status code: 2451 .................................................. 465
NetBackup status code: 2504 .................................................. 466
NetBackup status code: 2505 .................................................. 466
NetBackup status code: 2517 .................................................. 467
NetBackup status code: 2521 .................................................. 467
NetBackup status code: 2522 .................................................. 467
NetBackup status code: 2523 .................................................. 467
NetBackup status code: 2524 .................................................. 468
NetBackup status code: 2525 .................................................. 468
NetBackup status code: 2526 .................................................. 469
NetBackup status code: 2527 .................................................. 469
NetBackup status code: 2528 .................................................. 469
NetBackup status code: 2531 .................................................. 470
NetBackup status code: 2532 .................................................. 470
NetBackup status code: 2607 .................................................. 470
NetBackup status code: 2610 .................................................. 471
NetBackup status code: 2611 .................................................. 471
NetBackup status code: 2612 .................................................. 471
NetBackup status code: 2613 .................................................. 472
NetBackup status code: 2800 .................................................. 472
NetBackup status code: 2801 .................................................. 473
NetBackup status code: 2802 .................................................. 474
NetBackup status code: 2803 .................................................. 474
NetBackup status code: 2804 .................................................. 476
NetBackup status code: 2805 .................................................. 477
NetBackup status code: 2806 .................................................. 478
NetBackup status code: 2807 .................................................. 478
NetBackup status code: 2808 .................................................. 479
NetBackup status code: 2809 .................................................. 479
NetBackup status code: 2810 .................................................. 480
NetBackup status code: 2811 .................................................. 481
NetBackup status code: 2812 .................................................. 482
NetBackup status code: 2813 .................................................. 482
 Contents 26

NetBackup status code: 2814 .................................................. 483

NetBackup status code: 2815 .................................................. 483
NetBackup status code: 2816 .................................................. 484
NetBackup status code: 2817 .................................................. 484
NetBackup status code: 2818 .................................................. 485
NetBackup status code: 2819 .................................................. 486
NetBackup status code: 2820 .................................................. 486
NetBackup status code: 2821 .................................................. 488
NetBackup status code: 2822 .................................................. 488
NetBackup status code: 2824 .................................................. 489
NetBackup status code: 2826 .................................................. 493
NetBackup status code: 2827 .................................................. 494
NetBackup status code: 2828 .................................................. 494
NetBackup status code: 2829 .................................................. 494
NetBackup status code: 2830 .................................................. 495
NetBackup status code: 2831 .................................................. 495
NetBackup status code: 2832 .................................................. 495
NetBackup status code: 2833 .................................................. 496
NetBackup status code: 2834 .................................................. 496
NetBackup status code: 2835 .................................................. 496
NetBackup status code: 2836 .................................................. 497
NetBackup status code: 2837 .................................................. 497
NetBackup status code: 2838 .................................................. 497
NetBackup status code: 2839 .................................................. 498
NetBackup status code: 2840 .................................................. 498
NetBackup status code: 2841 .................................................. 498
NetBackup status code: 2842 .................................................. 499
NetBackup status code: 2843 .................................................. 499
NetBackup status code: 2844 .................................................. 499
NetBackup status code: 2845 .................................................. 500
NetBackup status code: 2846 .................................................. 500
NetBackup status code: 2847 .................................................. 500
NetBackup status code: 2848 .................................................. 501
NetBackup status code: 2849 .................................................. 501
NetBackup status code: 2850 .................................................. 502
NetBackup status code: 2864 .................................................. 503
NetBackup status code: 2865 .................................................. 503
NetBackup status code: 2866 .................................................. 503
NetBackup status code: 2869 .................................................. 503
NetBackup status code: 2870 .................................................. 504
NetBackup status code: 2877 .................................................. 504
NetBackup status code: 2880 .................................................. 504
NetBackup status code: 2881 .................................................. 505
 Contents 27

NetBackup status code: 2882 .................................................. 505

NetBackup status code: 2883 .................................................. 505
NetBackup status code: 2887 .................................................. 506
NetBackup status code: 2888 .................................................. 506
NetBackup status code: 2893 .................................................. 507
NetBackup status code: 2897 .................................................. 507
NetBackup status code: 3000 .................................................. 507
NetBackup status code: 3002 .................................................. 507
NetBackup status code: 3003 .................................................. 508
NetBackup status code: 3004 .................................................. 508
NetBackup status code: 3005 .................................................. 508
NetBackup status code: 3006 .................................................. 509
NetBackup status code: 3007 .................................................. 509
NetBackup status code: 3008 .................................................. 509
NetBackup status code: 3009 .................................................. 509
NetBackup status code: 3010 .................................................. 510
NetBackup status code: 3011 .................................................. 510
NetBackup status code: 3012 .................................................. 510
NetBackup status code: 3013 .................................................. 511
NetBackup status code: 3014 .................................................. 511
NetBackup status code: 3016 .................................................. 511
NetBackup status code: 3017 .................................................. 511
NetBackup status code: 3018 .................................................. 512
NetBackup status code: 3019 .................................................. 512
NetBackup status code: 3021 .................................................. 512
NetBackup status code: 3022 .................................................. 512
NetBackup status code: 3023 .................................................. 513
NetBackup status code: 3024 .................................................. 513
NetBackup status code: 3025 .................................................. 513
NetBackup status code: 3026 .................................................. 513
NetBackup status code: 3027 .................................................. 514
NetBackup status code: 3028 .................................................. 514
NetBackup status code: 3030 .................................................. 514
NetBackup status code: 3031 .................................................. 515
NetBackup status code: 3032 .................................................. 515
NetBackup status code: 3033 .................................................. 515
NetBackup status code: 3034 .................................................. 515
NetBackup status code: 3035 .................................................. 516
NetBackup status code: 3036 .................................................. 516
NetBackup status code: 3037 .................................................. 516
NetBackup status code: 3041 .................................................. 516
NetBackup status code: 3042 .................................................. 517
NetBackup status code: 3043 .................................................. 517
 Contents 28

NetBackup status code: 3044 .................................................. 517

NetBackup status code: 3045 .................................................. 518
NetBackup status code: 3047 .................................................. 518
NetBackup status code: 3200 .................................................. 518
NetBackup status code: 3201 .................................................. 518
NetBackup status code: 3202 .................................................. 519
NetBackup status code: 3203 .................................................. 519
NetBackup status code: 3204 .................................................. 519
NetBackup status code: 3205 .................................................. 520
NetBackup status code: 3206 .................................................. 520
NetBackup status code: 3207 .................................................. 520
NetBackup status code: 3208 .................................................. 520
NetBackup status code: 3209 .................................................. 521
NetBackup status code: 3210 .................................................. 521
NetBackup status code: 3211 .................................................. 521
NetBackup status code: 3212 .................................................. 521
NetBackup status code: 3213 .................................................. 522
NetBackup status code: 3214 .................................................. 522
NetBackup status code: 3215 .................................................. 522
NetBackup status code: 3216 .................................................. 522
NetBackup status code: 3217 .................................................. 523
NetBackup status code: 3218 .................................................. 523
NetBackup status code: 3219 .................................................. 523
NetBackup status code: 3220 .................................................. 524
NetBackup status code: 3221 .................................................. 524
NetBackup status code: 3222 .................................................. 524
NetBackup status code: 3223 .................................................. 524
NetBackup status code: 3224 .................................................. 525
NetBackup status code: 3225 .................................................. 525
NetBackup status code: 3232 .................................................. 525
NetBackup status code: 3234 .................................................. 526
NetBackup status code: 3235 .................................................. 526
NetBackup status code: 3236 .................................................. 526
NetBackup status code: 3245 .................................................. 527
NetBackup status code: 3246 .................................................. 527
NetBackup status code: 3251 .................................................. 528
NetBackup status code: 3252 .................................................. 528
NetBackup status code: 3253 .................................................. 528
NetBackup status code: 3254 .................................................. 529
NetBackup status code: 3255 .................................................. 529
NetBackup status code: 3256 .................................................. 530
NetBackup status code: 3257 .................................................. 530
NetBackup status code: 3258 .................................................. 531
 Contents 29

NetBackup status code: 3259 .................................................. 531

NetBackup status code: 3260 .................................................. 531
NetBackup status code: 3261 .................................................. 532
NetBackup status code: 3262 .................................................. 532
NetBackup status code: 3263 .................................................. 533
NetBackup status code: 3264 .................................................. 533
NetBackup status code: 3265 .................................................. 533
NetBackup status code: 3266 .................................................. 534
NetBackup status code: 3267 .................................................. 534
NetBackup status code: 3268 .................................................. 535
NetBackup status code: 3269 .................................................. 535
NetBackup status code: 3270 .................................................. 536
NetBackup status code: 3271 .................................................. 536
NetBackup status code: 3272 .................................................. 537
NetBackup status code: 3273 .................................................. 537
NetBackup status code: 3274 .................................................. 537
NetBackup status code: 3275 .................................................. 538
NetBackup status code: 3276 .................................................. 538
NetBackup status code: 3277 .................................................. 538
NetBackup status code: 3280 .................................................. 539
NetBackup status code: 3281 .................................................. 539
NetBackup status code: 3282 .................................................. 539
NetBackup status code: 3283 .................................................. 540
NetBackup status code: 3284 .................................................. 540
NetBackup status code: 3286 .................................................. 540
NetBackup status code: 3287 .................................................. 541
NetBackup status code: 3288 .................................................. 541
NetBackup status code: 3289 .................................................. 541
NetBackup status code: 3290 .................................................. 542
NetBackup status code: 3291 .................................................. 542
NetBackup status code: 3292 .................................................. 542
NetBackup status code: 3293 .................................................. 543
NetBackup status code: 3294 .................................................. 543
NetBackup status code: 3295 .................................................. 543
NetBackup status code: 3296 .................................................. 543
NetBackup status code: 3297 .................................................. 544
NetBackup status code: 3298 .................................................. 544
NetBackup status code: 3299 .................................................. 544
NetBackup status code: 3300 .................................................. 544
NetBackup status code: 3301 .................................................. 545
NetBackup status code: 3304 .................................................. 545
NetBackup status code: 3306 .................................................. 545
NetBackup status code: 3307 .................................................. 546
 Contents 30

NetBackup status code: 3308 .................................................. 546

NetBackup status code: 3309 .................................................. 546
NetBackup status code: 3310 .................................................. 546
NetBackup status code: 3311 .................................................. 547
NetBackup status code: 3312 .................................................. 547
NetBackup status code: 3313 .................................................. 547
NetBackup status code: 3314 .................................................. 548
NetBackup status code: 3315 .................................................. 548
NetBackup status code: 3316 .................................................. 548
NetBackup status code: 3317 .................................................. 549
NetBackup status code: 3318 .................................................. 549
NetBackup status code: 3319 .................................................. 549
NetBackup status code: 3321 .................................................. 549
NetBackup status code: 3322 .................................................. 550
NetBackup status code: 3323 .................................................. 550
NetBackup status code: 3324 .................................................. 550
NetBackup status code: 3325 .................................................. 550
NetBackup status code: 3326 .................................................. 551
NetBackup status code: 3327 .................................................. 551
NetBackup status code: 3328 .................................................. 551
NetBackup status code: 3329 .................................................. 552
NetBackup status code: 3330 .................................................. 552
NetBackup status code: 3331 .................................................. 553
NetBackup status code: 3332 .................................................. 554
NetBackup status code: 3333 .................................................. 555
NetBackup status code: 3335 .................................................. 555
NetBackup status code: 3336 .................................................. 555
NetBackup status code: 3337 .................................................. 555
NetBackup status code: 3340 .................................................. 556
NetBackup status code: 3341 .................................................. 556
NetBackup status code: 3342 .................................................. 556
NetBackup status code: 3346 .................................................. 556
NetBackup status code: 3600 .................................................. 557
NetBackup status code: 3601 .................................................. 557
NetBackup status code: 3602 .................................................. 558
NetBackup status code: 3603 .................................................. 558
NetBackup status code: 3605 .................................................. 558
NetBackup status code: 3606 .................................................. 558
NetBackup status code: 3607 .................................................. 559
NetBackup status code: 3608 .................................................. 559
NetBackup status code: 3609 .................................................. 559
NetBackup status code: 3612 .................................................. 560
NetBackup status code: 3613 .................................................. 560
 Contents 31

NetBackup status code: 3614 .................................................. 560

NetBackup status code: 3615 .................................................. 560
NetBackup status code: 3616 .................................................. 561
NetBackup status code: 3617 .................................................. 561
NetBackup status code: 3618 .................................................. 562
NetBackup status code: 3619 .................................................. 562
NetBackup status code: 3620 .................................................. 562
NetBackup status code: 3800 .................................................. 562
NetBackup status code: 3801 .................................................. 563
NetBackup status code: 3802 .................................................. 563
NetBackup status code: 3803 .................................................. 563
NetBackup status code: 3804 .................................................. 564
NetBackup status code: 3805 .................................................. 564
NetBackup status code: 3806 .................................................. 564
NetBackup status code: 3807 .................................................. 564
NetBackup status code: 3808 .................................................. 565
NetBackup status code: 3809 .................................................. 565
NetBackup status code: 3810 .................................................. 565
NetBackup status code: 3811 .................................................. 565
NetBackup status code: 3812 .................................................. 566
NetBackup status code: 3813 .................................................. 566
NetBackup status code: 3814 .................................................. 566
NetBackup status code: 3815 .................................................. 567
NetBackup status code: 3816 .................................................. 567
NetBackup status code: 3817 .................................................. 567
NetBackup status code: 3818 .................................................. 567
NetBackup status code: 3819 .................................................. 568
NetBackup status code: 3820 .................................................. 568
NetBackup status code: 3821 .................................................. 568
NetBackup status code: 3822 .................................................. 568
NetBackup status code: 3823 .................................................. 569
NetBackup status code: 3824 .................................................. 569
NetBackup status code: 3825 .................................................. 569
NetBackup status code: 3826 .................................................. 569
NetBackup status code: 3827 .................................................. 570
NetBackup status code: 3828 .................................................. 570
NetBackup status code: 3829 .................................................. 570
NetBackup status code: 3830 .................................................. 570
NetBackup status code: 3831 .................................................. 571
NetBackup status code: 3832 .................................................. 571
NetBackup status code: 3883 .................................................. 571
NetBackup status code: 3834 .................................................. 572
NetBackup status code: 3835 .................................................. 572
 Contents 32

NetBackup status code: 3836 .................................................. 572

NetBackup status code: 3837 .................................................. 572
NetBackup status code: 3838 .................................................. 573
NetBackup status code: 3839 .................................................. 573
NetBackup status code: 3840 .................................................. 573
NetBackup status code: 3841 .................................................. 573
NetBackup status code: 3842 .................................................. 574
NetBackup status code: 3843 .................................................. 574
NetBackup status code: 3844 .................................................. 574
NetBackup status code: 3845 .................................................. 574
NetBackup status code: 3846 .................................................. 575
NetBackup status code: 3847 .................................................. 575
NetBackup status code: 3900 .................................................. 575
NetBackup status code: 3901 .................................................. 575
NetBackup status code: 3902 .................................................. 576
NetBackup status code: 3903 .................................................. 576
NetBackup status code: 3904 .................................................. 576
NetBackup status code: 3905 .................................................. 577
NetBackup status code: 3906 .................................................. 577
NetBackup status code: 3907 .................................................. 577
NetBackup status code: 3908 .................................................. 578
NetBackup status code: 3909 .................................................. 578
NetBackup status code: 3910 .................................................. 578
NetBackup status code: 3911 .................................................. 579
NetBackup status code: 3912 .................................................. 579
NetBackup status code: 3913 .................................................. 579
NetBackup status code: 4000 .................................................. 580
NetBackup status code: 4001 .................................................. 580
NetBackup status code: 4002 .................................................. 580
NetBackup status code: 4003 .................................................. 580
NetBackup status code: 4004 .................................................. 581
NetBackup status code: 4005 .................................................. 581
NetBackup status code: 4006 .................................................. 581
NetBackup status code: 4007 .................................................. 582
NetBackup status code: 4008 .................................................. 582
NetBackup status code: 4011 .................................................. 582
NetBackup status code: 4012 .................................................. 582
NetBackup status code: 4013 .................................................. 583
NetBackup status code: 4014 .................................................. 583
NetBackup status code: 4015 .................................................. 583
NetBackup status code: 4016 .................................................. 583
NetBackup status code: 4017 .................................................. 584
NetBackup status code: 4019 .................................................. 584
 Contents 33

NetBackup status code: 4020 .................................................. 584

NetBackup status code: 4021 .................................................. 584
NetBackup status code: 4022 .................................................. 585
NetBackup status code: 4023 .................................................. 585
NetBackup status code: 4024 .................................................. 585
NetBackup status code: 4025 .................................................. 586
NetBackup status code: 4026 .................................................. 586
NetBackup status code: 4027 .................................................. 586
NetBackup status code: 4028 .................................................. 586
NetBackup status code: 4029 .................................................. 587
NetBackup status code: 4030 .................................................. 587
NetBackup status code: 4031 .................................................. 587
NetBackup status code: 4032 .................................................. 587
NetBackup status code: 4033 .................................................. 588
NetBackup status code: 4034 .................................................. 588
NetBackup status code: 4035 .................................................. 588
NetBackup status code: 4036 .................................................. 588
NetBackup status code: 4037 .................................................. 589
NetBackup status code: 4038 .................................................. 589
NetBackup status code: 4039 .................................................. 589
NetBackup status code: 4040 .................................................. 589
NetBackup status code: 4041 .................................................. 590
NetBackup status code: 4042 .................................................. 590
NetBackup status code: 4043 .................................................. 590
NetBackup status code: 4044 .................................................. 590
NetBackup status code: 4045 .................................................. 591
NetBackup status code: 4046 .................................................. 591
NetBackup status code: 4047 .................................................. 591
NetBackup status code: 4048 .................................................. 591
NetBackup status code: 4049 .................................................. 592
NetBackup status code: 4050 .................................................. 592
NetBackup status code: 4200 .................................................. 592
NetBackup status code: 4201 .................................................. 592
NetBackup status code: 4202 .................................................. 593
NetBackup status code: 4203 .................................................. 593
NetBackup status code: 4204 .................................................. 594
NetBackup status code: 4205 .................................................. 594
NetBackup status code: 4206 .................................................. 594
NetBackup status code: 4207 .................................................. 595
NetBackup status code: 4208 .................................................. 595
NetBackup status code: 4209 .................................................. 596
NetBackup status code: 4210 .................................................. 596
NetBackup status code: 4211 .................................................. 596
 Contents 34

NetBackup status code: 4212 .................................................. 597

NetBackup status code: 4213 .................................................. 597
NetBackup status code: 4214 .................................................. 598
NetBackup status code: 4215 .................................................. 598
NetBackup status code: 4216 .................................................. 598
NetBackup status code: 4217 .................................................. 599
NetBackup status code: 4218 .................................................. 599
NetBackup status code: 4219 .................................................. 599
NetBackup status code: 4220 .................................................. 600
NetBackup status code: 4221 .................................................. 600
NetBackup status code: 4222 .................................................. 600
NetBackup status code: 4223 .................................................. 601
NetBackup status code: 4224 .................................................. 601
NetBackup status code: 4225 .................................................. 601
NetBackup status code: 4226 .................................................. 602
NetBackup status code: 4227 .................................................. 603
NetBackup status code: 4228 .................................................. 603
NetBackup status code: 4229 .................................................. 603
NetBackup status code: 4230 .................................................. 604
NetBackup status code: 4231 .................................................. 604
NetBackup status code: 4232 .................................................. 604
NetBackup status code: 4233 .................................................. 604
NetBackup status code: 4234 .................................................. 605
NetBackup status code: 4235 .................................................. 605
NetBackup status code: 4236 .................................................. 605
NetBackup status code: 4237 .................................................. 606
NetBackup status code: 4238 .................................................. 606
NetBackup status code: 4239 .................................................. 606
NetBackup status code: 4240 .................................................. 607
NetBackup status code: 4241 .................................................. 607
NetBackup status code: 4243 .................................................. 607
NetBackup status code: 4245 .................................................. 608
NetBackup status code: 4246 .................................................. 608
NetBackup status code: 4248 .................................................. 608
NetBackup status code: 4249 .................................................. 608
NetBackup status code: 4250 .................................................. 609
NetBackup status code: 4251 .................................................. 609
NetBackup status code: 4252 .................................................. 609
NetBackup status code: 4253 .................................................. 610
NetBackup status code: 4254 .................................................. 610
NetBackup status code: 4255 .................................................. 610
NetBackup status code: 4256 .................................................. 611
NetBackup status code: 4257 .................................................. 611
 Contents 35

NetBackup status code: 4258 .................................................. 611

NetBackup status code: 4259 .................................................. 612
NetBackup status code: 4260 .................................................. 612
NetBackup status code: 4261 .................................................. 612
NetBackup status code: 4262 .................................................. 612
NetBackup status code: 4263 .................................................. 613
NetBackup status code: 4264 .................................................. 613
NetBackup status code: 4265 .................................................. 613
NetBackup status code: 4266 .................................................. 614
NetBackup status code: 4267 .................................................. 614
NetBackup status code: 4268 .................................................. 614
NetBackup status code: 4269 .................................................. 615
NetBackup status code: 4270 .................................................. 615
NetBackup status code: 4271 .................................................. 615
NetBackup status code: 4272 .................................................. 615
NetBackup status code: 4273 .................................................. 616
NetBackup status code: 4274 .................................................. 616
NetBackup status code: 4275 .................................................. 616
NetBackup status code: 4276 .................................................. 617
NetBackup status code: 4277 .................................................. 617
NetBackup status code: 4278 .................................................. 617
NetBackup status code: 4279 .................................................. 618
NetBackup status code: 4280 .................................................. 618
NetBackup status code: 4281 .................................................. 618
NetBackup status code: 4282 .................................................. 618
NetBackup status code: 4283 .................................................. 619
NetBackup status code: 4287 .................................................. 619
NetBackup status code: 4290 .................................................. 620
NetBackup status code: 4292 .................................................. 620
NetBackup status code: 4293 .................................................. 621
NetBackup status code: 4294 .................................................. 621
NetBackup status code: 4295 .................................................. 621
NetBackup status code: 4296 .................................................. 622
NetBackup status code: 4297 .................................................. 622
NetBackup status code: 4298 .................................................. 622
NetBackup status code: 4299 .................................................. 622
NetBackup status code: 4301 .................................................. 623
NetBackup status code: 4302 .................................................. 623
NetBackup status code: 4307 .................................................. 623
NetBackup status code: 4308 .................................................. 623
NetBackup status code: 4309 .................................................. 624
NetBackup status code: 4310 .................................................. 624
NetBackup status code: 4311 .................................................. 624
 Contents 36

NetBackup status code: 4312 .................................................. 625

NetBackup status code: 4313 .................................................. 625
NetBackup status code: 4315 .................................................. 626
NetBackup status code: 4500 .................................................. 626
NetBackup status code: 4501 .................................................. 626
NetBackup status code: 4502 .................................................. 626
NetBackup status code: 4503 .................................................. 627
NetBackup status code: 4504 .................................................. 627
NetBackup status code: 4505 .................................................. 627
NetBackup status code: 4506 .................................................. 627
NetBackup status code: 4507 .................................................. 628
NetBackup status code: 4508 .................................................. 628
NetBackup status code: 4509 .................................................. 628
NetBackup status code: 4510 .................................................. 629
NetBackup status code: 4511 .................................................. 629
NetBackup status code: 4512 .................................................. 629
NetBackup status code: 4513 .................................................. 629
NetBackup status code: 4514 .................................................. 630
NetBackup status code: 4515 .................................................. 630
NetBackup status code: 4516 .................................................. 630
NetBackup status code: 4517 .................................................. 630
NetBackup status code: 4518 .................................................. 631
NetBackup status code: 4519 .................................................. 631
NetBackup status code: 4520 .................................................. 631
NetBackup status code: 4521 .................................................. 631
NetBackup status code: 4604 .................................................. 632
NetBackup status code: 4605 .................................................. 632
NetBackup status code: 4606 .................................................. 632
NetBackup status code: 4607 .................................................. 632
NetBackup status code: 4608 .................................................. 633
NetBackup status code: 4609 .................................................. 633
NetBackup status code: 4610 .................................................. 633
NetBackup status code: 4700 .................................................. 634
NetBackup status code: 4701 .................................................. 634
NetBackup status code: 4702 .................................................. 634
NetBackup status code: 4703 .................................................. 634
NetBackup status code: 4704 .................................................. 635
NetBackup status code: 4705 .................................................. 635
NetBackup status code: 4706 .................................................. 635
NetBackup status code: 4707 .................................................. 635
NetBackup status code: 4708 .................................................. 636
NetBackup status code: 4709 .................................................. 636
NetBackup status code: 4710 .................................................. 636
 Contents 37

NetBackup status code: 4711 .................................................. 637

NetBackup status code: 4712 .................................................. 637
NetBackup status code: 4713 .................................................. 637
NetBackup status code: 4714 .................................................. 637
NetBackup status code: 4715 .................................................. 638
NetBackup status code: 4716 .................................................. 638
NetBackup status code: 4718 .................................................. 638
NetBackup status code: 4719 .................................................. 638
NetBackup status code: 4720 .................................................. 639
NetBackup status code: 4721 .................................................. 639
NetBackup status code: 4722 .................................................. 639
NetBackup status code: 4723 .................................................. 640
NetBackup status code: 4724 .................................................. 640
NetBackup status code: 4725 .................................................. 640
NetBackup status code: 4726 .................................................. 640
NetBackup status code: 4727 .................................................. 641
NetBackup status code: 4728 .................................................. 641
NetBackup status code: 4729 .................................................. 641
NetBackup status code: 4730 .................................................. 642
NetBackup status code: 4731 .................................................. 642
NetBackup status code: 4732 .................................................. 642
NetBackup status code: 4733 .................................................. 642
NetBackup status code: 4734 .................................................. 643
NetBackup status code: 4735 .................................................. 643
NetBackup status code: 4736 .................................................. 643
NetBackup status code: 4737 .................................................. 644
NetBackup status code: 4739 .................................................. 644
NetBackup status code: 4740 .................................................. 644
NetBackup status code: 4741 .................................................. 644
NetBackup status code: 4743 .................................................. 645
NetBackup status code: 4744 .................................................. 645
NetBackup status code: 4745 .................................................. 645
NetBackup status code: 4746 .................................................. 645
NetBackup status code: 4747 .................................................. 646
NetBackup status code: 4748 .................................................. 646
NetBackup status code: 4749 .................................................. 646
NetBackup status code: 4750 .................................................. 646
NetBackup status code: 4751 .................................................. 647
NetBackup status code: 4755 .................................................. 647
NetBackup status code: 4769 .................................................. 647
NetBackup status code: 4770 .................................................. 647
NetBackup status code: 4771 .................................................. 648
NetBackup status code: 4772 .................................................. 648
 Contents 38

NetBackup status code: 4773 .................................................. 648

NetBackup status code: 4774 .................................................. 648
NetBackup status code: 4775 .................................................. 649
NetBackup status code: 4776 .................................................. 649
NetBackup status code: 4777 .................................................. 649
NetBackup status code: 4778 .................................................. 650
NetBackup status code: 4779 .................................................. 650
NetBackup status code: 4780 .................................................. 650
NetBackup status code: 4781 .................................................. 650
NetBackup status code: 4782 .................................................. 651
NetBackup status code: 4783 .................................................. 651
NetBackup status code: 4784 .................................................. 651
NetBackup status code: 4785 .................................................. 651
NetBackup status code: 4786 .................................................. 652
NetBackup status code: 4787 .................................................. 652
NetBackup status code: 4788 .................................................. 652
NetBackup status code: 4789 .................................................. 653
NetBackup status code: 4790 .................................................. 653
NetBackup status code: 4793 .................................................. 653
NetBackup status code: 4794 .................................................. 653
NetBackup status code: 4795 .................................................. 654
NetBackup status code: 4900 .................................................. 654
NetBackup status code: 5400 .................................................. 654
NetBackup status code: 5401 .................................................. 654
NetBackup status code: 5402 .................................................. 655
NetBackup status code: 5403 .................................................. 655
NetBackup status code: 5404 .................................................. 655
NetBackup status code: 5405 .................................................. 656
NetBackup status code: 5406 .................................................. 656
NetBackup status code: 5407 .................................................. 656
NetBackup status code: 5408 .................................................. 657
NetBackup status code: 5409 .................................................. 657
NetBackup status code: 5410 .................................................. 657
NetBackup status code: 5411 .................................................. 658
NetBackup status code: 5412 .................................................. 658
NetBackup status code: 5413 .................................................. 658
NetBackup status code: 5414 .................................................. 658
NetBackup status code: 5415 .................................................. 659
NetBackup status code: 5416 .................................................. 659
NetBackup status code: 5417 .................................................. 659
NetBackup status code: 5418 .................................................. 660
NetBackup status code: 5419 .................................................. 660
NetBackup status code: 5420 .................................................. 660
 Contents 39

NetBackup status code: 5421 .................................................. 660

NetBackup status code: 5422 .................................................. 661
NetBackup status code: 5423 .................................................. 661
NetBackup status code: 5424 .................................................. 662
NetBackup status code: 5425 .................................................. 662
NetBackup status code: 5426 .................................................. 662
NetBackup status code: 5427 .................................................. 663
NetBackup status code: 5428 .................................................. 663
NetBackup status code: 5429 .................................................. 664
NetBackup status code: 5430 .................................................. 664
NetBackup status code: 5431 .................................................. 664
NetBackup status code: 5432 .................................................. 665
NetBackup status code: 5433 .................................................. 665
NetBackup status code: 5434 .................................................. 665
NetBackup status code: 5435 .................................................. 666
NetBackup status code: 5436 .................................................. 666
NetBackup status code: 5437 .................................................. 666
NetBackup status code: 5438 .................................................. 666
NetBackup status code: 5439 .................................................. 667
NetBackup status code: 5440 .................................................. 667
NetBackup status code: 5441 .................................................. 667
NetBackup status code: 5442 .................................................. 668
NetBackup status code: 5443 .................................................. 668
NetBackup status code: 5444 .................................................. 668
NetBackup status code: 5445 .................................................. 669
NetBackup status code: 5446 .................................................. 669
NetBackup status code: 5447 .................................................. 669
NetBackup status code: 5448 .................................................. 669
NetBackup status code: 5449 .................................................. 670
NetBackup status code: 5450 .................................................. 670
NetBackup status code: 5451 .................................................. 670
NetBackup status code: 5452 .................................................. 670
NetBackup status code: 5453 .................................................. 671
NetBackup status code: 5454 .................................................. 671
NetBackup status code: 5455 .................................................. 671
NetBackup status code: 5456 .................................................. 672
NetBackup status code: 5457 .................................................. 672
NetBackup status code: 5458 .................................................. 673
NetBackup status code: 5459 .................................................. 673
NetBackup status code: 5461 .................................................. 674
NetBackup status code: 5462 .................................................. 674
NetBackup status code: 5500 .................................................. 674
NetBackup status code: 5501 .................................................. 675
 Contents 40

NetBackup status code: 5502 .................................................. 675

NetBackup status code: 5503 .................................................. 675
NetBackup status code: 5504 .................................................. 675
NetBackup status code: 5505 .................................................. 676
NetBackup status code: 5506 .................................................. 676
NetBackup status code: 5507 .................................................. 676
NetBackup status code: 5508 .................................................. 676
NetBackup status code: 5509 .................................................. 677
NetBackup status code: 5510 .................................................. 677
NetBackup status code: 5511 .................................................. 677
NetBackup status code: 5512 .................................................. 677
NetBackup status code: 5513 .................................................. 678
NetBackup status code: 5514 .................................................. 678
NetBackup status code: 5626 .................................................. 678
NetBackup status code: 5631 .................................................. 679
NetBackup status code: 5761 .................................................. 679
NetBackup status code: 5762 .................................................. 680
NetBackup status code: 5763 .................................................. 680
NetBackup status code: 5764 .................................................. 680
NetBackup status code: 5765 .................................................. 680
NetBackup status code: 5766 .................................................. 681
NetBackup status code: 5767 .................................................. 681
NetBackup status code: 5768 .................................................. 681
NetBackup status code: 5769 .................................................. 681
NetBackup status code: 5770 .................................................. 682
NetBackup status code: 5771 .................................................. 682
NetBackup status code: 5772 .................................................. 682
NetBackup status code: 5773 .................................................. 683
NetBackup status code: 5774 .................................................. 683
NetBackup status code: 5775 .................................................. 683
NetBackup status code: 5776 .................................................. 683
NetBackup status code: 5777 .................................................. 683
NetBackup status code: 5778 .................................................. 684
NetBackup status code: 5779 .................................................. 684
NetBackup status code: 5780 .................................................. 684
NetBackup status code: 5781 .................................................. 684
NetBackup status code: 5782 .................................................. 685
NetBackup status code: 5783 .................................................. 685
NetBackup status code: 5784 .................................................. 685
NetBackup status code: 5786 .................................................. 685
NetBackup status code: 5787 .................................................. 686
NetBackup status code: 5788 .................................................. 686
NetBackup status code: 5789 .................................................. 686
 Contents 41

NetBackup status code: 5790 .................................................. 686

NetBackup status code: 5794 .................................................. 686
NetBackup status code: 5796 .................................................. 687
NetBackup status code: 5798 .................................................. 687
NetBackup status code: 5799 .................................................. 687
NetBackup status code: 5800 .................................................. 688
NetBackup status code: 5801 .................................................. 688
NetBackup status code: 5803 .................................................. 688
NetBackup status code: 5804 .................................................. 688
NetBackup status code: 5805 .................................................. 688
NetBackup status code: 5806 .................................................. 689
NetBackup status code: 5807 .................................................. 689
NetBackup status code: 5808 .................................................. 689
NetBackup status code: 5809 .................................................. 689
NetBackup status code: 5811 .................................................. 690
NetBackup status code: 5812 .................................................. 690
NetBackup status code: 5813 .................................................. 690
NetBackup status code: 5814 .................................................. 690
NetBackup status code: 5815 .................................................. 691
NetBackup status code: 5816 .................................................. 691
NetBackup status code: 5817 .................................................. 691
NetBackup status code: 5819 .................................................. 691
NetBackup status code: 5820 .................................................. 692
NetBackup status code: 5821 .................................................. 692
NetBackup status code: 5902 .................................................. 692
NetBackup status code: 5903 .................................................. 692
NetBackup status code: 5904 .................................................. 693
NetBackup status code: 5905 .................................................. 693
NetBackup status code: 5906 .................................................. 693
NetBackup status code: 5907 .................................................. 694
NetBackup status code: 5908 .................................................. 694
NetBackup status code: 5909 .................................................. 694
NetBackup status code: 5910 .................................................. 694
NetBackup status code: 5913 .................................................. 695
NetBackup status code: 5914 .................................................. 695
NetBackup status code: 5915 .................................................. 695
NetBackup status code: 5916 .................................................. 695
NetBackup status code: 5917 .................................................. 696
NetBackup status code: 5918 .................................................. 696
NetBackup status code: 5919 .................................................. 696
NetBackup status code: 5920 .................................................. 696
NetBackup status code: 5921 .................................................. 697
NetBackup status code: 5922 .................................................. 697
 Contents 42

NetBackup status code: 5925 .................................................. 697

NetBackup status code: 5926 .................................................. 698
NetBackup status code: 5927 .................................................. 698
NetBackup status code: 5929 .................................................. 698
NetBackup status code: 5930 .................................................. 698
NetBackup status code: 5931 .................................................. 699
NetBackup status code: 5932 .................................................. 699
NetBackup status code: 5933 .................................................. 699
NetBackup status code: 5934 .................................................. 700
NetBackup status code: 5936 .................................................. 700
NetBackup status code: 5938 .................................................. 700
NetBackup status code: 5939 .................................................. 700
NetBackup status code: 5940 .................................................. 701
NetBackup status code: 5941 .................................................. 701
NetBackup status code: 5942 .................................................. 701
NetBackup status code: 5943 .................................................. 702
NetBackup status code: 5944 .................................................. 702
NetBackup status code: 5945 .................................................. 702
NetBackup status code: 5946 .................................................. 703
NetBackup status code: 5947 .................................................. 703
NetBackup status code: 5948 .................................................. 703
NetBackup status code: 5949 .................................................. 703
NetBackup status code: 5950 .................................................. 704
NetBackup status code: 5953 .................................................. 704
NetBackup status code: 5954 .................................................. 704
NetBackup status code: 5955 .................................................. 705
NetBackup status code: 5956 .................................................. 705
NetBackup status code: 5957 .................................................. 705
NetBackup status code: 5958 .................................................. 705
NetBackup status code: 5959 .................................................. 706
NetBackup status code: 5960 .................................................. 706
NetBackup status code: 5962 .................................................. 706
NetBackup status code: 5963 .................................................. 707
NetBackup status code: 5964 .................................................. 707
NetBackup status code: 5965 .................................................. 707
NetBackup status code: 5966 .................................................. 708
NetBackup status code: 5967 .................................................. 708
NetBackup status code: 5968 .................................................. 708
NetBackup status code: 5969 .................................................. 709
NetBackup status code: 5970 .................................................. 709
NetBackup status code: 5971 .................................................. 709
NetBackup status code: 5972 .................................................. 710
NetBackup status code: 5973 .................................................. 710
 Contents 43

NetBackup status code: 5974 .................................................. 710

NetBackup status code: 5976 .................................................. 711
NetBackup status code: 5977 .................................................. 711
NetBackup status code: 5978 .................................................. 711
NetBackup status code: 5979 .................................................. 712
NetBackup status code: 5980 .................................................. 712
NetBackup status code: 5982 .................................................. 713
NetBackup status code: 5983 .................................................. 714
NetBackup status code: 5986 .................................................. 715
NetBackup status code: 5987 .................................................. 715
NetBackup status code: 5988 .................................................. 719
NetBackup status code: 5989 .................................................. 719
NetBackup status code: 5990 .................................................. 720
NetBackup status code: 5991 .................................................. 721
NetBackup status code: 5992 .................................................. 721
NetBackup status code: 5993 .................................................. 721
NetBackup status code: 5994 .................................................. 721
NetBackup status code: 5995 .................................................. 722
NetBackup status code: 5996 .................................................. 722
NetBackup status code: 5997 .................................................. 723
NetBackup status code: 5998 .................................................. 723
NetBackup status code: 5999 .................................................. 724
NetBackup status code: 6000 .................................................. 724
NetBackup status code: 6071 .................................................. 724
NetBackup status code: 6072 .................................................. 725
NetBackup status code: 6073 .................................................. 725
NetBackup status code: 6074 .................................................. 725
NetBackup status code: 6075 .................................................. 725
NetBackup status code: 6078 .................................................. 726
NetBackup status code: 6079 .................................................. 726
NetBackup status code: 6080 .................................................. 726
NetBackup status code: 6082 .................................................. 727
NetBackup status code: 6083 .................................................. 727
NetBackup status code: 6084 .................................................. 727
NetBackup status code: 6085 .................................................. 727
NetBackup status code: 6100 .................................................. 728
NetBackup status code: 6101 .................................................. 728
NetBackup status code: 6102 .................................................. 728
NetBackup status code: 6103 .................................................. 729
NetBackup status code: 6104 .................................................. 729
NetBackup status code: 6105 .................................................. 729
NetBackup status code: 6106 .................................................. 730
NetBackup status code: 6107 .................................................. 730
 Contents 44

NetBackup status code: 6108 .................................................. 730

NetBackup status code: 6109 .................................................. 730
NetBackup status code: 6405 .................................................. 730
NetBackup status code: 6406 .................................................. 731
NetBackup status code: 6416 .................................................. 731
NetBackup status code: 6423 .................................................. 731
NetBackup status code: 6430 .................................................. 732
NetBackup status code: 6431 .................................................. 732
NetBackup status code: 6435 .................................................. 733
NetBackup status code: 6437 .................................................. 733
NetBackup status code: 6438 .................................................. 733
NetBackup status code: 6440 .................................................. 734
NetBackup status code: 6441 .................................................. 734
NetBackup status code: 6459 .................................................. 734
NetBackup status code: 6530 .................................................. 735
NetBackup status code: 6531 .................................................. 735
NetBackup status code: 6600 .................................................. 735
NetBackup status code: 6601 .................................................. 736
NetBackup status code: 6602 .................................................. 736
NetBackup status code: 6603 .................................................. 737
NetBackup status code: 6604 .................................................. 737
NetBackup status code: 6605 .................................................. 737
NetBackup status code: 6606 .................................................. 737
NetBackup status code: 6607 .................................................. 738
NetBackup status code: 6608 .................................................. 738
NetBackup status code: 6609 .................................................. 738
NetBackup status code: 6610 .................................................. 739
NetBackup status code: 6612 .................................................. 739
NetBackup status code: 6614 .................................................. 739
NetBackup status code: 6616 .................................................. 739
NetBackup status code: 6617 .................................................. 740
NetBackup status code: 6618 .................................................. 740
NetBackup status code: 6619 .................................................. 740
NetBackup status code: 6620 .................................................. 741
NetBackup status code: 6621 .................................................. 741
NetBackup status code: 6622 .................................................. 741
NetBackup status code: 6623 .................................................. 741
NetBackup status code: 6625 .................................................. 742
NetBackup status code: 6626 .................................................. 742
NetBackup status code: 6628 .................................................. 743
NetBackup status code: 6629 .................................................. 743
NetBackup status code: 6630 .................................................. 743
NetBackup status code: 6631 .................................................. 743
 Contents 45

NetBackup status code: 6633 .................................................. 744

NetBackup status code: 6634 .................................................. 744
NetBackup status code: 6635 .................................................. 744
NetBackup status code: 6640 .................................................. 744
NetBackup status code: 6641 .................................................. 745
NetBackup status code: 6642 .................................................. 745
NetBackup status code: 6643 .................................................. 745
NetBackup status code: 6644 .................................................. 746
NetBackup status code: 6646 .................................................. 746
NetBackup status code: 6647 .................................................. 746
NetBackup status code: 6649 .................................................. 746
NetBackup status code: 6650 .................................................. 747
NetBackup status code: 6652 .................................................. 747
NetBackup status code: 6653 .................................................. 747
NetBackup status code: 6654 .................................................. 747
NetBackup status code: 6655 .................................................. 748
NetBackup status code: 6656 .................................................. 748
NetBackup status code: 6657 .................................................. 748
NetBackup status code: 6658 .................................................. 749
NetBackup status code: 6659 .................................................. 749
NetBackup status code: 6661 .................................................. 749
NetBackup status code: 6662 .................................................. 750
NetBackup status code: 6663 .................................................. 750
NetBackup status code: 6664 .................................................. 750
NetBackup status code: 6665 .................................................. 751
NetBackup status code: 6666 .................................................. 751
NetBackup status code: 6667 .................................................. 751
NetBackup status code: 6668 .................................................. 752
NetBackup status code: 6669 .................................................. 752
NetBackup status code: 6670 .................................................. 752
NetBackup status code: 6671 .................................................. 753
NetBackup status code: 6672 .................................................. 753
NetBackup status code: 6673 .................................................. 753
NetBackup status code: 6674 .................................................. 753
NetBackup status code: 6675 .................................................. 754
NetBackup status code: 6676 .................................................. 754
NetBackup status code: 6677 .................................................. 754
NetBackup status code: 6678 .................................................. 754
NetBackup status code: 6679 .................................................. 755
NetBackup status code: 6680 .................................................. 755
NetBackup status code: 6681 .................................................. 755
NetBackup status code: 6682 .................................................. 755
NetBackup status code: 6683 .................................................. 756
 Contents 46

NetBackup status code: 6684 .................................................. 756

NetBackup status code: 6685 .................................................. 756
NetBackup status code: 6686 .................................................. 756
NetBackup status code: 6687 .................................................. 757
NetBackup status code: 6688 .................................................. 757
NetBackup status code: 6689 .................................................. 757
NetBackup status code: 6690 .................................................. 757
NetBackup status code: 6691 .................................................. 758
NetBackup status code: 6692 .................................................. 758
NetBackup status code: 6693 .................................................. 758
NetBackup status code: 6694 .................................................. 759
NetBackup status code: 6695 .................................................. 759
NetBackup status code: 6696 .................................................. 759
NetBackup status code: 6697 .................................................. 760
NetBackup status code: 6698 .................................................. 760
NetBackup status code: 6699 .................................................. 760
NetBackup status code: 6700 .................................................. 760
NetBackup status code: 6701 .................................................. 761
NetBackup status code: 6702 .................................................. 761
NetBackup status code: 6703 .................................................. 761
NetBackup status code: 6704 .................................................. 762
NetBackup status code: 6705 .................................................. 762
NetBackup status code: 6706 .................................................. 762
NetBackup status code: 6707 .................................................. 762
NetBackup status code: 6708 .................................................. 763
NetBackup status code: 6709 .................................................. 763
NetBackup status code: 6710 .................................................. 764
NetBackup status code: 6711 .................................................. 764
NetBackup status code: 6712 .................................................. 765
NetBackup status code: 6713 .................................................. 765
NetBackup status code: 6714 .................................................. 766
NetBackup status code: 6715 .................................................. 766
NetBackup status code: 6716 .................................................. 766
NetBackup status code: 6717 .................................................. 767
NetBackup status code: 6718 .................................................. 767
NetBackup status code: 6719 .................................................. 767
NetBackup status code: 6720 .................................................. 768
NetBackup status code: 6721 .................................................. 768
NetBackup status code: 6722 .................................................. 768
NetBackup status code: 6723 .................................................. 769
NetBackup status code: 6724 .................................................. 769
NetBackup status code: 6725 .................................................. 770
NetBackup status code: 6726 .................................................. 770
 Contents 47

NetBackup status code: 6727 .................................................. 770

NetBackup status code: 6728 .................................................. 770
NetBackup status code: 6729 .................................................. 771
NetBackup status code: 6730 .................................................. 771
NetBackup status code: 6731 .................................................. 771
NetBackup status code: 6732 .................................................. 772
NetBackup status code: 6733 .................................................. 772
NetBackup status code: 6734 .................................................. 772
NetBackup status code: 6735 .................................................. 773
NetBackup status code: 6736 .................................................. 773
NetBackup status code: 6737 .................................................. 773
NetBackup status code: 6738 .................................................. 773
NetBackup status code: 6739 .................................................. 774
NetBackup status code: 6740 .................................................. 774
NetBackup status code: 6741 .................................................. 774
NetBackup status code: 6742 .................................................. 774
NetBackup status code: 6743 .................................................. 775
NetBackup status code: 6744 .................................................. 775
NetBackup status code: 6745 .................................................. 775
NetBackup status code: 6746 .................................................. 776
NetBackup status code: 6747 .................................................. 776
NetBackup status code: 6748 .................................................. 776
NetBackup status code: 6749 .................................................. 777
NetBackup status code: 6750 .................................................. 777
NetBackup status code: 6751 .................................................. 777
NetBackup status code: 6752 .................................................. 778
NetBackup status code: 6753 .................................................. 778
NetBackup status code: 6754 .................................................. 778
NetBackup status code: 6755 .................................................. 779
NetBackup status code: 6756 .................................................. 779
NetBackup status code: 6757 .................................................. 779
NetBackup status code: 6758 .................................................. 780
NetBackup status code: 6759 .................................................. 780
NetBackup status code: 6760 .................................................. 780
NetBackup status code: 6761 .................................................. 781
NetBackup status code: 6762 .................................................. 781
NetBackup status code: 6763 .................................................. 781
NetBackup status code: 6764 .................................................. 782
NetBackup status code: 6765 .................................................. 782
NetBackup status code: 6766 .................................................. 782
NetBackup status code: 6767 .................................................. 783
NetBackup status code: 6768 .................................................. 783
NetBackup status code: 6772 .................................................. 783
 Contents 48

NetBackup status code: 6773 .................................................. 784

NetBackup status code: 6774 .................................................. 784
NetBackup status code: 6775 .................................................. 784
NetBackup status code: 6776 .................................................. 785
NetBackup status code: 6777 .................................................. 785
NetBackup status code: 6778 .................................................. 786
NetBackup status code: 6779 .................................................. 786
NetBackup status code: 6780 .................................................. 787
NetBackup status code: 6781 .................................................. 787
NetBackup status code: 6782 .................................................. 788
NetBackup status code: 6783 .................................................. 788
NetBackup status code: 6784 .................................................. 788
NetBackup status code: 6785 .................................................. 789
NetBackup status code: 6786 .................................................. 790
NetBackup status code: 6787 .................................................. 790
NetBackup status code: 6788 .................................................. 791
NetBackup status code: 6789 .................................................. 792
NetBackup status code: 6791 .................................................. 793
NetBackup status code: 6792 .................................................. 793
NetBackup status code: 6793 .................................................. 794
NetBackup status code: 6794 .................................................. 794
NetBackup status code: 6797 .................................................. 795
NetBackup status code: 6798 .................................................. 795
NetBackup status code: 6800 .................................................. 796
NetBackup status code: 6801 .................................................. 796
NetBackup status code: 6802 .................................................. 796
NetBackup status code: 6803 .................................................. 797
NetBackup status code: 6804 .................................................. 797
NetBackup status code: 6805 .................................................. 797
NetBackup status code: 6806 .................................................. 798
NetBackup status code: 6807 .................................................. 798
NetBackup status code: 6808 .................................................. 798
NetBackup status code: 6809 .................................................. 798
NetBackup status code: 6810 .................................................. 799
NetBackup status code: 6811 .................................................. 799
NetBackup status code: 6812 .................................................. 799
NetBackup status code: 6813 .................................................. 800
NetBackup status code: 6814 .................................................. 800
NetBackup status code: 6815 .................................................. 800
NetBackup status code: 6816 .................................................. 801
NetBackup status code: 6817 .................................................. 801
NetBackup status code: 6818 .................................................. 802
NetBackup status code: 6819 .................................................. 802
 Contents 49

NetBackup status code: 6820 .................................................. 802

NetBackup status code: 6821 .................................................. 803
NetBackup status code: 6822 .................................................. 803
NetBackup status code: 6823 .................................................. 804
NetBackup status code: 6824 .................................................. 804
NetBackup status code: 6831 .................................................. 804
NetBackup status code: 6832 .................................................. 805
NetBackup status code: 6833 .................................................. 805
NetBackup status code: 7100 .................................................. 806
NetBackup status code: 7101 .................................................. 806
NetBackup status code: 7102 .................................................. 806
NetBackup status code: 7103 .................................................. 807
NetBackup status code: 7104 .................................................. 807
NetBackup status code: 7105 .................................................. 807
NetBackup status code: 7106 .................................................. 807
NetBackup status code: 7107 .................................................. 808
NetBackup status code: 7108 .................................................. 808
NetBackup status code: 7109 .................................................. 808
NetBackup status code: 7110 .................................................. 808
NetBackup status code: 7112 .................................................. 809
NetBackup status code: 7113 .................................................. 809
NetBackup status code: 7114 .................................................. 809
NetBackup status code: 7115 .................................................. 809
NetBackup status code: 7116 .................................................. 810
NetBackup status code: 7117 .................................................. 810
NetBackup status code: 7118 .................................................. 810
NetBackup status code: 7119 .................................................. 810
NetBackup status code: 7120 .................................................. 811
NetBackup status code: 7121 .................................................. 811
NetBackup status code: 7122 .................................................. 811
NetBackup status code: 7123 .................................................. 811
NetBackup status code: 7125 .................................................. 812
NetBackup status code: 7126 .................................................. 812
NetBackup status code: 7127 .................................................. 812
NetBackup status code: 7128 .................................................. 813
NetBackup status code: 7129 .................................................. 813
NetBackup status code: 7130 .................................................. 813
NetBackup status code: 7131 .................................................. 813
NetBackup status code: 7132 .................................................. 814
NetBackup status code: 7133 .................................................. 814
NetBackup status code: 7134 .................................................. 814
NetBackup status code: 7135 .................................................. 815
NetBackup status code: 7136 .................................................. 815
 Contents 50

NetBackup status code: 7137 .................................................. 815

NetBackup status code: 7138 .................................................. 815
NetBackup status code: 7139 .................................................. 816
NetBackup status code: 7140 .................................................. 816
NetBackup status code: 7141 .................................................. 816
NetBackup status code: 7142 .................................................. 816
NetBackup status code: 7143 .................................................. 817
NetBackup status code: 7144 .................................................. 817
NetBackup status code: 7146 .................................................. 817
NetBackup status code: 7147 .................................................. 818
NetBackup status code: 7148 .................................................. 818
NetBackup status code: 7149 .................................................. 818
NetBackup status code: 7151 .................................................. 818
NetBackup status code: 7152 .................................................. 819
NetBackup status code: 7153 .................................................. 819
NetBackup status code: 7154 .................................................. 819
NetBackup status code: 7155 .................................................. 819
NetBackup status code: 7156 .................................................. 820
NetBackup status code: 7157 .................................................. 820
NetBackup status code: 7158 .................................................. 820
NetBackup status code: 7159 .................................................. 821
NetBackup status code: 7160 .................................................. 821
NetBackup status code: 7161 .................................................. 821
NetBackup status code: 7162 .................................................. 821
NetBackup status code: 7163 .................................................. 822
NetBackup status code: 7164 .................................................. 822
NetBackup status code: 7165 .................................................. 822
NetBackup status code: 7166 .................................................. 823
NetBackup status code: 7167 .................................................. 823
NetBackup status code: 7168 .................................................. 823
NetBackup status code: 7200 .................................................. 823
NetBackup status code: 7201 .................................................. 824
NetBackup status code: 7202 .................................................. 824
NetBackup status code: 7203 .................................................. 824
NetBackup status code: 7204 .................................................. 825
NetBackup status code: 7205 .................................................. 825
NetBackup status code: 7206 .................................................. 825
NetBackup status code: 7207 .................................................. 826
NetBackup status code: 7208 .................................................. 827
NetBackup status code: 7209 .................................................. 828
NetBackup status code: 7210 .................................................. 828
NetBackup status code: 7211 .................................................. 828
NetBackup status code: 7212 .................................................. 828
 Contents 51

NetBackup status code: 7213 .................................................. 829

NetBackup status code: 7214 .................................................. 830
NetBackup status code: 7215 .................................................. 830
NetBackup status code: 7216 .................................................. 830
NetBackup status code: 7217 .................................................. 831
NetBackup status code: 7218 .................................................. 831
NetBackup status code: 7219 .................................................. 831
NetBackup status code: 7220 .................................................. 831
NetBackup status code: 7221 .................................................. 832
NetBackup status code: 7222 .................................................. 832
NetBackup status code: 7223 .................................................. 832
NetBackup status code: 7224 .................................................. 833
NetBackup status code: 7225 .................................................. 833
NetBackup status code: 7226 .................................................. 834
NetBackup status code: 7227 .................................................. 834
NetBackup status code: 7228 .................................................. 835
NetBackup status code: 7229 .................................................. 835
NetBackup status code: 7230 .................................................. 835
NetBackup status code: 7231 .................................................. 836
NetBackup status code: 7232 .................................................. 836
NetBackup status code: 7233 .................................................. 836
NetBackup status code: 7234 .................................................. 837
NetBackup status code: 7235 .................................................. 837
NetBackup status code: 7236 .................................................. 837
NetBackup status code: 7237 .................................................. 838
NetBackup status code: 7238 .................................................. 838
NetBackup status code: 7239 .................................................. 838
NetBackup status code: 7240 .................................................. 839
NetBackup status code: 7241 .................................................. 839
NetBackup status code: 7243 .................................................. 839
NetBackup status code: 7245 .................................................. 840
NetBackup status code: 7246 .................................................. 840
NetBackup status code: 7247 .................................................. 840
NetBackup status code: 7248 .................................................. 841
NetBackup status code: 7249 .................................................. 841
NetBackup status code: 7250 .................................................. 841
NetBackup status code: 7251 .................................................. 842
NetBackup status code: 7252 .................................................. 842
NetBackup status code: 7253 .................................................. 842
NetBackup status code: 7254 .................................................. 843
NetBackup status code: 7255 .................................................. 843
NetBackup status code: 7256 .................................................. 843
NetBackup status code: 7258 .................................................. 844
 Contents 52

NetBackup status code: 7259 .................................................. 844

NetBackup status code: 7260 .................................................. 845
NetBackup status code: 7261 .................................................. 845
NetBackup status code: 7262 .................................................. 845
NetBackup status code: 7263 .................................................. 846
NetBackup status code: 7264 .................................................. 846
NetBackup status code: 7265 .................................................. 846
NetBackup status code: 7266 .................................................. 847
NetBackup status code: 7267 .................................................. 847
NetBackup status code: 7268 .................................................. 847
NetBackup status code: 7269 .................................................. 847
NetBackup status code: 7270 .................................................. 848
NetBackup status code: 7271 .................................................. 848
NetBackup status code: 7272 .................................................. 848
NetBackup status code: 7273 .................................................. 849
NetBackup status code: 7275 .................................................. 849
NetBackup status code: 7276 .................................................. 849
NetBackup status code: 7277 .................................................. 849
NetBackup status code: 7278 .................................................. 850
NetBackup status code: 7279 .................................................. 850
NetBackup status code: 7281 .................................................. 850
NetBackup status code: 7282 .................................................. 851
NetBackup status code: 7283 .................................................. 851
NetBackup status code: 7284 .................................................. 851
NetBackup status code: 7285 .................................................. 852
NetBackup status code: 7286 .................................................. 852
NetBackup status code: 7287 .................................................. 852
NetBackup status code: 7288 .................................................. 853
NetBackup status code: 7289 .................................................. 853
NetBackup status code: 7290 .................................................. 853
NetBackup status code: 7291 .................................................. 853
NetBackup status code: 7292 .................................................. 854
NetBackup status code: 7293 .................................................. 854
NetBackup status code: 7294 .................................................. 854
NetBackup status code: 7295 .................................................. 855
NetBackup status code: 7296 .................................................. 855
NetBackup status code: 7297 .................................................. 856
NetBackup status code: 7298 .................................................. 856
NetBackup status code: 7299 .................................................. 857
NetBackup status code: 7300 .................................................. 857
NetBackup status code: 7400 .................................................. 857
NetBackup status code: 7401 .................................................. 857
NetBackup status code: 7402 .................................................. 858
 Contents 53

NetBackup status code: 7403 .................................................. 858

NetBackup status code: 7404 .................................................. 858
NetBackup status code: 7405 .................................................. 858
NetBackup status code: 7406 .................................................. 859
NetBackup status code: 7407 .................................................. 859
NetBackup status code: 7408 .................................................. 859
NetBackup status code: 7409 .................................................. 860
NetBackup status code: 7410 .................................................. 860
NetBackup status code: 7411 .................................................. 860
NetBackup status code: 7412 .................................................. 860
NetBackup status code: 7413 .................................................. 861
NetBackup status code: 7414 .................................................. 861
NetBackup status code: 7415 .................................................. 861
NetBackup status code: 7416 .................................................. 861
NetBackup status code: 7417 .................................................. 862
NetBackup status code: 7418 .................................................. 862
NetBackup status code: 7419 .................................................. 862
NetBackup status code: 7420 .................................................. 862
NetBackup status code: 7421 .................................................. 863
NetBackup status code: 7422 .................................................. 863
NetBackup status code: 7423 .................................................. 863
NetBackup status code: 7424 .................................................. 863
NetBackup status code: 7425 .................................................. 864
NetBackup status code: 7426 .................................................. 864
NetBackup status code: 7432 .................................................. 864
NetBackup status code: 7433 .................................................. 864
NetBackup status code: 7434 .................................................. 865
NetBackup status code: 7435 .................................................. 865
NetBackup status code: 7436 .................................................. 865
NetBackup status code: 7437 .................................................. 866
NetBackup status code: 7450 .................................................. 866
NetBackup status code: 7451 .................................................. 866
NetBackup status code: 7452 .................................................. 866
NetBackup status code: 7453 .................................................. 867
NetBackup status code: 7454 .................................................. 867
NetBackup status code: 7455 .................................................. 867
NetBackup status code: 7456 .................................................. 868
NetBackup status code: 7457 .................................................. 868
NetBackup status code: 7458 .................................................. 868
NetBackup status code: 7459 .................................................. 868
NetBackup status code: 7460 .................................................. 869
NetBackup status code: 7461 .................................................. 869
NetBackup status code: 7462 .................................................. 869
 Contents 54

NetBackup status code: 7463 .................................................. 870

NetBackup status code: 7464 .................................................. 870
NetBackup status code: 7465 .................................................. 870
NetBackup status code: 7466 .................................................. 870
NetBackup status code: 7467 .................................................. 871
NetBackup status code: 7468 .................................................. 871
NetBackup status code: 7469 .................................................. 871
NetBackup status code: 7472 .................................................. 872
NetBackup status code: 7473 .................................................. 872
NetBackup status code: 7600 .................................................. 872
NetBackup status code: 7601 .................................................. 872
NetBackup status code: 7603 .................................................. 873
NetBackup status code: 7604 .................................................. 873
NetBackup status code: 7607 .................................................. 873
NetBackup status code: 7609 .................................................. 873
NetBackup status code: 7610 .................................................. 874
NetBackup status code: 7611 .................................................. 874
NetBackup status code: 7612 .................................................. 874
NetBackup status code: 7613 .................................................. 874
NetBackup status code: 7614 .................................................. 875
NetBackup status code: 7617 .................................................. 875
NetBackup status code: 7618 .................................................. 875
NetBackup status code: 7619 .................................................. 875
NetBackup status code: 7622 .................................................. 876
NetBackup status code: 7623 .................................................. 876
NetBackup status code: 7624 .................................................. 876
NetBackup status code: 7625 .................................................. 877
NetBackup status code: 7627 .................................................. 877
NetBackup status code: 7628 .................................................. 878
NetBackup status code: 7631 .................................................. 879
NetBackup status code: 7632 .................................................. 879
NetBackup status code: 7633 .................................................. 879
NetBackup status code: 7634 .................................................. 879
NetBackup status code: 7635 .................................................. 880
NetBackup status code: 7636 .................................................. 880
NetBackup status code: 7637 .................................................. 880
NetBackup status code: 7638 .................................................. 881
NetBackup status code: 7639 .................................................. 881
NetBackup status code: 7640 .................................................. 881
NetBackup status code: 7641 .................................................. 882
NetBackup status code: 7642 .................................................. 882
NetBackup status code: 7643 .................................................. 883
NetBackup status code: 7645 .................................................. 883
 Contents 55

NetBackup status code: 7647 .................................................. 883

NetBackup status code: 7648 .................................................. 883
NetBackup status code: 7649 .................................................. 884
NetBackup status code: 7650 .................................................. 884
NetBackup status code: 7651 .................................................. 884
NetBackup status code: 7652 .................................................. 884
NetBackup status code: 7653 .................................................. 885
NetBackup status code: 7654 .................................................. 886
NetBackup status code: 7655 .................................................. 886
NetBackup status code: 7656 .................................................. 887
NetBackup status code: 7657 .................................................. 887
NetBackup status code: 7658 .................................................. 888
NetBackup status code: 7659 .................................................. 888
NetBackup status code: 7660 .................................................. 888
NetBackup status code: 7662 .................................................. 889
NetBackup status code: 7663 .................................................. 889
NetBackup status code: 7800 .................................................. 890
NetBackup status code: 7801 .................................................. 890
NetBackup status code: 7802 .................................................. 890
NetBackup status code: 7803 .................................................. 890
NetBackup status code: 7804 .................................................. 891
NetBackup status code: 7805 .................................................. 891
NetBackup status code: 7806 .................................................. 891
NetBackup status code: 7807 .................................................. 891
NetBackup status code: 7808 .................................................. 892
NetBackup status code: 7809 .................................................. 892
NetBackup status code: 7810 .................................................. 892
NetBackup status code: 7811 .................................................. 893
NetBackup status code: 7812 .................................................. 893
NetBackup status code: 7813 .................................................. 893
NetBackup status code: 7814 .................................................. 894
NetBackup status code: 7815 .................................................. 894
NetBackup status code: 7850 .................................................. 894
NetBackup status code: 7851 .................................................. 895
NetBackup status code: 7852 .................................................. 895
NetBackup status code: 7853 .................................................. 895
NetBackup status code: 7854 .................................................. 895
NetBackup status code: 7855 .................................................. 896
NetBackup status code: 7856 .................................................. 896
NetBackup status code: 7857 .................................................. 896
NetBackup status code: 7858 .................................................. 897
NetBackup status code: 7859 .................................................. 897
NetBackup status code: 7860 .................................................. 897
 Contents 56

NetBackup status code: 7861 .................................................. 897

NetBackup status code: 7862 .................................................. 897
NetBackup status code: 7863 .................................................. 898
NetBackup status code: 7864 .................................................. 898
NetBackup status code: 7865 .................................................. 898
NetBackup status code: 7866 .................................................. 898
NetBackup status code: 7867 .................................................. 899
NetBackup status code: 7868 .................................................. 899
NetBackup status code: 7869 .................................................. 899
NetBackup status code: 7870 .................................................. 899
NetBackup status code: 7871 .................................................. 900
NetBackup status code: 7872 .................................................. 900
NetBackup status code: 7873 .................................................. 900
NetBackup status code: 7874 .................................................. 900
NetBackup status code: 7875 .................................................. 901
NetBackup status code: 7876 .................................................. 901
NetBackup status code: 7877 .................................................. 901
NetBackup status code: 7878 .................................................. 902
NetBackup status code: 7879 .................................................. 902
NetBackup status code: 7880 .................................................. 902
NetBackup status code: 7881 .................................................. 902
NetBackup status code: 7882 .................................................. 903
NetBackup status code: 7883 .................................................. 903
NetBackup status code: 7884 .................................................. 903
NetBackup status code: 7885 .................................................. 903
NetBackup status code: 7886 .................................................. 904
NetBackup status code: 7887 .................................................. 904
NetBackup status code: 7888 .................................................. 904
NetBackup status code: 7889 .................................................. 904
NetBackup status code: 7890 .................................................. 905
NetBackup status code: 7891 .................................................. 905
NetBackup status code: 7892 .................................................. 905
NetBackup status code: 7893 .................................................. 906
NetBackup status code: 7894 .................................................. 906
NetBackup status code: 7895 .................................................. 906
NetBackup status code: 7896 .................................................. 906
NetBackup status code: 7897 .................................................. 907
NetBackup status code: 8000 .................................................. 907
NetBackup status code: 8001 .................................................. 907
NetBackup status code: 8002 .................................................. 907
NetBackup status code: 8009 .................................................. 908
NetBackup status code: 8016 .................................................. 908
NetBackup status code: 8018 .................................................. 908
 Contents 57

NetBackup status code: 8019 .................................................. 909

NetBackup status code: 8021 .................................................. 909
NetBackup status code: 8051 .................................................. 909
NetBackup status code: 8053 .................................................. 910
NetBackup status code: 8054 .................................................. 910
NetBackup status code: 8055 .................................................. 910
NetBackup status code: 8056 .................................................. 910
NetBackup status code: 8100 .................................................. 911
NetBackup status code: 8101 .................................................. 911
NetBackup status code: 8102 .................................................. 911
NetBackup status code: 8103 .................................................. 912
NetBackup status code: 8104 .................................................. 912
NetBackup status code: 8105 .................................................. 912
NetBackup status code: 8106 .................................................. 912
NetBackup status code: 8107 .................................................. 913
NetBackup status code: 8200 .................................................. 913
NetBackup status code: 8201 .................................................. 913
NetBackup status code: 8203 .................................................. 913
NetBackup status code: 8204 .................................................. 914
NetBackup status code: 8205 .................................................. 914
NetBackup status code: 8207 .................................................. 914
NetBackup status code: 8208 .................................................. 915
NetBackup status code: 8209 .................................................. 915
NetBackup status code: 8211 .................................................. 915
NetBackup status code: 8212 .................................................. 916
NetBackup status code: 8216 .................................................. 916
NetBackup status code: 8217 .................................................. 916
NetBackup status code: 8220 .................................................. 917
NetBackup status code: 8221 .................................................. 917
NetBackup status code: 8224 .................................................. 917
NetBackup status code: 8226 .................................................. 917
NetBackup status code: 8227 .................................................. 918
NetBackup status code: 8228 .................................................. 918
NetBackup status code: 8229 .................................................. 918
NetBackup status code: 8234 .................................................. 919
NetBackup status code: 8235 .................................................. 919
NetBackup status code: 8236 .................................................. 919
NetBackup status code: 8237 .................................................. 920
NetBackup status code: 8238 .................................................. 920
NetBackup status code: 8240 .................................................. 921
NetBackup status code: 8250 .................................................. 921
NetBackup status code: 8251 .................................................. 921
NetBackup status code: 8252 .................................................. 922
 Contents 58

NetBackup status code: 8253 .................................................. 922

NetBackup status code: 8300 .................................................. 922
NetBackup status code: 8301 .................................................. 923
NetBackup status code: 8302 .................................................. 923
NetBackup status code: 8303 .................................................. 924
NetBackup status code: 8304 .................................................. 924
NetBackup status code: 8305 .................................................. 925
NetBackup status code: 8306 .................................................. 925
NetBackup status code: 8307 .................................................. 926
NetBackup status code: 8308 .................................................. 927
NetBackup status code: 8310 .................................................. 927
NetBackup status code: 8311 .................................................. 928
NetBackup status code: 8312 .................................................. 929
NetBackup status code: 8313 .................................................. 930
NetBackup status code: 8314 .................................................. 930
NetBackup status code: 8315 .................................................. 930
NetBackup status code: 8316 .................................................. 931
NetBackup status code: 8350 .................................................. 931
NetBackup status code: 8351 .................................................. 931
NetBackup status code: 8352 .................................................. 932
NetBackup status code: 8401 .................................................. 932
NetBackup status code: 8402 .................................................. 933
NetBackup status code: 8403 .................................................. 933
NetBackup status code: 8404 .................................................. 934
NetBackup status code: 8405 .................................................. 934
NetBackup status code: 8406 .................................................. 935
NetBackup status code: 8407 .................................................. 936
NetBackup status code: 8408 .................................................. 936
NetBackup status code: 8409 .................................................. 937
NetBackup status code: 8410 .................................................. 937
NetBackup status code: 8411 .................................................. 938
NetBackup status code: 8412 .................................................. 939
NetBackup status code: 8413 .................................................. 939
NetBackup status code: 8414 .................................................. 940
NetBackup status code: 8415 .................................................. 940
NetBackup status code: 8416 .................................................. 941
NetBackup status code: 8417 .................................................. 942
NetBackup status code: 8418 .................................................. 942
NetBackup status code: 8419 .................................................. 943
NetBackup status code: 8420 .................................................. 944
NetBackup status code: 8421 .................................................. 944
NetBackup status code: 8422 .................................................. 945
NetBackup status code: 8423 .................................................. 945
 Contents 59

NetBackup status code: 8424 .................................................. 946

NetBackup status code: 8425 .................................................. 947
NetBackup status code: 8426 .................................................. 947
NetBackup status code: 8427 .................................................. 948
NetBackup status code: 8428 .................................................. 948
NetBackup status code: 8429 .................................................. 949
NetBackup status code: 8430 .................................................. 949
NetBackup status code: 8431 .................................................. 949
NetBackup status code: 8432 .................................................. 950
NetBackup status code: 8433 .................................................. 951
NetBackup status code: 8434 .................................................. 951
NetBackup status code: 8435 .................................................. 951
NetBackup status code: 8436 .................................................. 952
NetBackup status code: 8437 .................................................. 953
NetBackup status code: 8438 .................................................. 953
NetBackup status code: 8439 .................................................. 954
NetBackup status code: 8440 .................................................. 955
NetBackup status code: 8441 .................................................. 955
NetBackup status code: 8442 .................................................. 955
NetBackup status code: 8443 .................................................. 956
NetBackup status code: 8444 .................................................. 956
NetBackup status code: 8445 .................................................. 957
NetBackup status code: 8446 .................................................. 957
NetBackup status code: 8453 .................................................. 958
NetBackup status code: 8454 .................................................. 960
NetBackup status code: 8455 .................................................. 960
NetBackup status code: 8456 .................................................. 961
NetBackup status code: 8459 .................................................. 961
NetBackup status code: 8460 .................................................. 962
NetBackup status code: 8469 .................................................. 964
NetBackup status code: 8500 .................................................. 965
NetBackup status code: 8503 .................................................. 965
NetBackup status code: 8504 .................................................. 965
NetBackup status code: 8505 .................................................. 966
NetBackup status code: 8506 .................................................. 966
NetBackup status code: 8507 .................................................. 966
NetBackup status code: 8508 .................................................. 967
NetBackup status code: 8509 .................................................. 967
NetBackup status code: 8510 .................................................. 968
NetBackup status code: 8511 .................................................. 968
NetBackup status code: 8512 .................................................. 968
NetBackup status code: 8516 .................................................. 969
NetBackup status code: 8517 .................................................. 969
 Contents 60

NetBackup status code: 8604 .................................................. 969

NetBackup status code: 8617 .................................................. 970
NetBackup status code: 8618 .................................................. 970
NetBackup status code: 8619 .................................................. 971
NetBackup status code: 8620 .................................................. 971
NetBackup status code: 8621 .................................................. 971
NetBackup status code: 8622 .................................................. 972
NetBackup status code: 8623 .................................................. 972
NetBackup status code: 8625 .................................................. 972
NetBackup status code: 8629 .................................................. 973
NetBackup status code: 8630 .................................................. 973
NetBackup status code: 8631 .................................................. 973
NetBackup status code: 8632 .................................................. 974
NetBackup status code: 8633 .................................................. 974
NetBackup status code: 8634 .................................................. 975
NetBackup status code: 8635 .................................................. 975
NetBackup status code: 8636 .................................................. 976
NetBackup status code: 8638 .................................................. 976
NetBackup status code: 8639 .................................................. 976
NetBackup status code: 8640 .................................................. 977
NetBackup status code: 8641 .................................................. 977
NetBackup status code: 8642 .................................................. 977
NetBackup status code: 8656 .................................................. 978
NetBackup status code: 8657 .................................................. 978
NetBackup status code: 8658 .................................................. 979
NetBackup status code: 8676 .................................................. 980
NetBackup status code: 8677 .................................................. 981
NetBackup status code: 8678 .................................................. 981
NetBackup status code: 8679 .................................................. 981
NetBackup status code: 8680 .................................................. 981
NetBackup status code: 8700 .................................................. 982
NetBackup status code: 8701 .................................................. 982
NetBackup status code: 8702 .................................................. 982
NetBackup status code: 8703 .................................................. 983
NetBackup status code: 8704 .................................................. 983
NetBackup status code: 8706 .................................................. 983
NetBackup status code: 8707 .................................................. 984
NetBackup status code: 8708 .................................................. 984
NetBackup status code: 8709 .................................................. 984
NetBackup status code: 8710 .................................................. 984
NetBackup status code: 8711 .................................................. 985
NetBackup status code: 8712 .................................................. 985
NetBackup status code: 8713 .................................................. 985
 Contents 61

NetBackup status code: 8714 .................................................. 985

NetBackup status code: 8715 .................................................. 986
NetBackup status code: 8716 .................................................. 986
NetBackup status code: 8717 .................................................. 986
NetBackup status code: 8718 .................................................. 986
NetBackup status code: 8719 .................................................. 987
NetBackup status code: 8720 .................................................. 987
NetBackup status code: 8722 .................................................. 987
NetBackup status code: 8723 .................................................. 988
NetBackup status code: 8724 .................................................. 988
NetBackup status code: 8725 .................................................. 988
NetBackup status code: 8727 .................................................. 988
NetBackup status code: 8728 .................................................. 989
NetBackup status code: 8729 .................................................. 989
NetBackup status code: 8730 .................................................. 989
NetBackup status code: 8731 .................................................. 990
NetBackup status code: 8732 .................................................. 990
NetBackup status code: 8733 .................................................. 991
NetBackup status code: 8739 .................................................. 991
NetBackup status code: 8740 .................................................. 991
NetBackup status code: 8753 .................................................. 992
NetBackup status code: 8754 .................................................. 992
NetBackup status code: 8755 .................................................. 993
NetBackup status code: 8756 .................................................. 993
NetBackup status code: 8757 .................................................. 994
NetBackup status code: 8759 .................................................. 994
NetBackup status code: 8760 .................................................. 994
NetBackup status code: 8761 .................................................. 994
NetBackup status code: 8762 .................................................. 995
NetBackup status code: 8763 .................................................. 995
NetBackup status code: 8764 .................................................. 995
NetBackup status code: 8765 .................................................. 996
NetBackup status code: 8766 .................................................. 996
NetBackup status code: 8767 .................................................. 997
NetBackup status code: 8768 .................................................. 997
NetBackup status code: 8769 .................................................. 997
NetBackup status code: 8770 .................................................. 998
NetBackup status code: 8771 .................................................. 998
NetBackup status code: 8772 .................................................. 998
NetBackup status code: 8773 .................................................. 999
NetBackup status code: 8774 .................................................. 999
NetBackup status code: 8775 .................................................. 999
NetBackup status code: 8776 .................................................. 999
 Contents 62

NetBackup status code: 8777 ................................................ 1000

NetBackup status code: 8778 ................................................ 1000
NetBackup status code: 8779 ................................................ 1000
NetBackup status code: 8787 ................................................ 1010
NetBackup status code: 8788 ................................................ 1010
NetBackup status code: 8789 ................................................ 1011
NetBackup status code: 8790 ................................................ 1011
NetBackup status code: 8791 ................................................ 1012
NetBackup status code: 8792 ................................................ 1012
NetBackup status code: 8793 ................................................ 1013
NetBackup status code: 8794 ................................................ 1013
NetBackup status code: 8798 ................................................ 1013
NetBackup status code: 8799 ................................................ 1019
NetBackup status code: 8800 ................................................ 1019
NetBackup status code: 8813 ................................................ 1019
NetBackup status code: 8814 ................................................ 1020
NetBackup status code: 8816 ................................................ 1020
NetBackup status code: 8817 ................................................ 1020
NetBackup status code: 8818 ................................................ 1020
NetBackup status code: 8819 ................................................ 1021
NetBackup status code: 8820 ................................................ 1021
NetBackup status code: 8821 ................................................ 1022
NetBackup status code: 8822 ................................................ 1022
NetBackup status code: 8823 ................................................ 1022
NetBackup status code: 8824 ................................................ 1022
NetBackup status code: 8825 ................................................ 1023
NetBackup status code: 8836 ................................................ 1023
NetBackup status code: 8837 ................................................ 1023
NetBackup status code: 8842 ................................................ 1024
NetBackup status code: 8900 ................................................ 1024
NetBackup status code: 8901 ................................................ 1024
NetBackup status code: 8902 ................................................ 1025
NetBackup status code: 8951 ................................................ 1025
NetBackup status code: 8952 ................................................ 1025
NetBackup status code: 8953 ................................................ 1026
NetBackup status code: 8954 ................................................ 1026
NetBackup status code: 8955 ................................................ 1026
NetBackup status code: 8956 ................................................ 1026
NetBackup status code: 8957 ................................................ 1027
NetBackup status code: 8958 ................................................ 1027
NetBackup status code: 8959 ................................................ 1027
NetBackup status code: 8960 ................................................ 1028
NetBackup status code: 8962 ................................................ 1028
 Contents 63

NetBackup status code: 8963 ................................................ 1028

NetBackup status code: 9050 ................................................ 1030
NetBackup status code: 9051 ................................................ 1030
NetBackup status code: 9052 ................................................ 1030
NetBackup status code: 9053 ................................................ 1031
NetBackup status code: 9101 ................................................ 1031
NetBackup status code: 9102 ................................................ 1031
NetBackup status code: 9103 ................................................ 1031
NetBackup status code: 9104 ................................................ 1032
NetBackup status code: 9108 ................................................ 1032
NetBackup status code: 9128 ................................................ 1033
NetBackup status code: 9129 ................................................ 1033
NetBackup status code: 9130 ................................................ 1033
NetBackup status code: 9131 ................................................ 1034
NetBackup status code: 9132 ................................................ 1034
NetBackup status code: 9201 ................................................ 1034
NetBackup status code: 9202 ................................................ 1035
NetBackup status code: 9250 ................................................ 1035
NetBackup status code: 9251 ................................................ 1036
NetBackup status code: 9252 ................................................ 1037
NetBackup status code: 9253 ................................................ 1037
NetBackup status code: 9300 ................................................ 1037
NetBackup status code: 9301 ................................................ 1038
NetBackup status code: 9302 ................................................ 1038
NetBackup status code: 9303 ................................................ 1039
NetBackup status code: 9304 ................................................ 1039
NetBackup status code: 9305 ................................................ 1039
NetBackup status code: 9306 ................................................ 1040
NetBackup status code: 9307 ................................................ 1041
NetBackup status code: 9308 ................................................ 1041
NetBackup status code: 9309 ................................................ 1042
NetBackup status code: 9310 ................................................ 1043
NetBackup status code: 9311 ................................................ 1043
NetBackup status code: 9312 ................................................ 1043
NetBackup status code: 9313 ................................................ 1043
NetBackup status code: 9314 ................................................ 1044
NetBackup status code: 9315 ................................................ 1044
NetBackup status code: 9316 ................................................ 1044
NetBackup status code: 9317 ................................................ 1045
NetBackup status code: 9318 ................................................ 1045
NetBackup status code: 9319 ................................................ 1045
NetBackup status code: 9324 ................................................ 1046
NetBackup status code: 9325 ................................................ 1046
 Contents 64

NetBackup status code: 9326 ................................................ 1046

NetBackup status code: 9327 ................................................ 1046
NetBackup status code: 9328 ................................................ 1047
NetBackup status code: 9329 ................................................ 1047
NetBackup status code: 9330 ................................................ 1048
NetBackup status code: 9331 ................................................ 1048
NetBackup status code: 9332 ................................................ 1048
NetBackup status code: 9333 ................................................ 1048
NetBackup status code: 9334 ................................................ 1049
NetBackup status code: 9335 ................................................ 1049
NetBackup status code: 9336 ................................................ 1050
NetBackup status code: 9337 ................................................ 1050
NetBackup status code: 9338 ................................................ 1050
NetBackup status code: 9339 ................................................ 1051
NetBackup status code: 9340 ................................................ 1051
NetBackup status code: 9350 ................................................ 1051
NetBackup status code: 9351 ................................................ 1051
NetBackup status code: 9352 ................................................ 1052
NetBackup status code: 9353 ................................................ 1052
NetBackup status code: 9354 ................................................ 1052
NetBackup status code: 9355 ................................................ 1052
NetBackup status code: 9356 ................................................ 1053
NetBackup status code: 9357 ................................................ 1053
NetBackup status code: 9400 ................................................ 1053
NetBackup status code: 9401 ................................................ 1053
NetBackup status code: 9402 ................................................ 1054
NetBackup status code: 9403 ................................................ 1054
NetBackup status code: 9404 ................................................ 1054
NetBackup status code: 9405 ................................................ 1054
NetBackup status code: 9490 ................................................ 1055
NetBackup status code: 9491 ................................................ 1055
NetBackup status code: 9492 ................................................ 1056
NetBackup status code: 9600 ................................................ 1056
NetBackup status code: 9616 ................................................ 1056
NetBackup status code: 9700 ................................................ 1057
NetBackup status code: 9701 ................................................ 1057
NetBackup status code: 9702 ................................................ 1057
NetBackup status code: 9703 ................................................ 1057
NetBackup status code: 9704 ................................................ 1058
NetBackup status code: 9705 ................................................ 1058
NetBackup status code: 9706 ................................................ 1058
NetBackup status code: 9708 ................................................ 1059
NetBackup status code: 9709 ................................................ 1059
 Contents 65

NetBackup status code: 9710 ................................................ 1059

NetBackup status code: 9711 ................................................ 1059
NetBackup status code: 9712 ................................................ 1060
NetBackup status code: 9713 ................................................ 1060
NetBackup status code: 9714 ................................................ 1060
NetBackup status code: 9715 ................................................ 1060
NetBackup status code: 9716 ................................................ 1061
NetBackup status code: 9717 ................................................ 1061
NetBackup status code: 9718 ................................................ 1061
NetBackup status code: 9719 ................................................ 1062
NetBackup status code: 9720 ................................................ 1062
NetBackup status code: 9722 ................................................ 1062
NetBackup status code: 9723 ................................................ 1062
NetBackup status code: 9724 ................................................ 1063
NetBackup status code: 9725 ................................................ 1063
NetBackup status code: 9726 ................................................ 1063
NetBackup status code: 9731 ................................................ 1064
NetBackup status code: 9732 ................................................ 1064
NetBackup status code: 9733 ................................................ 1064
NetBackup status code: 9734 ................................................ 1064
NetBackup status code: 9735 ................................................ 1065
NetBackup status code: 9736 ................................................ 1065
NetBackup status code: 9737 ................................................ 1065
NetBackup status code: 9738 ................................................ 1066
NetBackup status code: 9739 ................................................ 1066
NetBackup status code: 9740 ................................................ 1066
NetBackup status code: 9741 ................................................ 1067
NetBackup status code: 9743 ................................................ 1067
NetBackup status code: 9744 ................................................ 1068
NetBackup status code: 9745 ................................................ 1068
NetBackup status code: 9746 ................................................ 1068
NetBackup status code: 9747 ................................................ 1069
NetBackup status code: 9748 ................................................ 1069
NetBackup status code: 9749 ................................................ 1069
NetBackup status code: 9751 ................................................ 1070
NetBackup status code: 9752 ................................................ 1070
NetBackup status code: 9760 ................................................ 1070
NetBackup status code: 9764 ................................................ 1071
NetBackup status code: 9765 ................................................ 1071
NetBackup status code: 9766 ................................................ 1071
NetBackup status code: 9767 ................................................ 1072
NetBackup status code: 9768 ................................................ 1072
NetBackup status code: 9769 ................................................ 1072
 Contents 66

NetBackup status code: 9770 ................................................ 1072

NetBackup status code: 9771 ................................................ 1073
NetBackup status code: 9772 ................................................ 1073
NetBackup status code: 9773 ................................................ 1073
NetBackup status code: 9776 ................................................ 1074
NetBackup status code: 9778 ................................................ 1074
NetBackup status code: 9800 ................................................ 1074
NetBackup status code: 9801 ................................................ 1074
NetBackup status code: 9802 ................................................ 1075
NetBackup status code: 9803 ................................................ 1075
NetBackup status code: 9804 ................................................ 1075
NetBackup status code: 9805 ................................................ 1076
NetBackup status code: 9806 ................................................ 1076
NetBackup status code: 9807 ................................................ 1076
NetBackup status code: 9808 ................................................ 1076
NetBackup status code: 9809 ................................................ 1077
NetBackup status code: 9810 ................................................ 1077
NetBackup status code: 9811 ................................................ 1077
NetBackup status code: 9812 ................................................ 1077
NetBackup status code: 9813 ................................................ 1078
NetBackup status code: 9814 ................................................ 1078
NetBackup status code: 9815 ................................................ 1078
NetBackup status code: 9816 ................................................ 1078
NetBackup status code: 9818 ................................................ 1079
NetBackup status code: 9819 ................................................ 1079
NetBackup status code: 9820 ................................................ 1079
NetBackup status code: 9821 ................................................ 1079
NetBackup status code: 9822 ................................................ 1080
NetBackup status code: 9823 ................................................ 1080
NetBackup status code: 9830 ................................................ 1080
NetBackup status code: 9032 ................................................ 1081
NetBackup status code: 9833 ................................................ 1081
NetBackup status code: 9834 ................................................ 1081
NetBackup status code: 9835 ................................................ 1081
NetBackup status code: 9836 ................................................ 1082
NetBackup status code: 9837 ................................................ 1082
NetBackup status code: 9838 ................................................ 1082
NetBackup status code: 9839 ................................................ 1082
NetBackup status code: 9841 ................................................ 1083
NetBackup status code: 9842 ................................................ 1083
NetBackup status code: 9843 ................................................ 1083
NetBackup status code: 9844 ................................................ 1083
NetBackup status code: 9845 ................................................ 1084
 Contents 67

NetBackup status code: 9846 ................................................ 1084

NetBackup status code: 9847 ................................................ 1084
NetBackup status code: 9848 ................................................ 1084
NetBackup status code: 9849 ................................................ 1085
NetBackup status code: 9850 ................................................ 1085
NetBackup status code: 9851 ................................................ 1085
NetBackup status code: 9853 ................................................ 1085
NetBackup status code: 9854 ................................................ 1086
NetBackup status code: 9855 ................................................ 1086
NetBackup status code: 9856 ................................................ 1086
NetBackup status code: 9857 ................................................ 1087
NetBackup status code: 9858 ................................................ 1087
NetBackup status code: 9859 ................................................ 1087
NetBackup status code: 9860 ................................................ 1088
NetBackup status code: 9861 ................................................ 1088
NetBackup status code: 9862 ................................................ 1088
NetBackup status code: 9863 ................................................ 1088
NetBackup status code: 9865 ................................................ 1089
NetBackup status code: 9866 ................................................ 1089
NetBackup status code: 9867 ................................................ 1090
NetBackup status code: 9868 ................................................ 1090
NetBackup status code: 9869 ................................................ 1091
NetBackup status code: 9870 ................................................ 1091
NetBackup status code: 9871 ................................................ 1091
NetBackup status code: 9872 ................................................ 1092
NetBackup status code: 9873 ................................................ 1092
NetBackup status code: 9874 ................................................ 1092
NetBackup status code: 9876 ................................................ 1093
NetBackup status code: 9877 ................................................ 1093
NetBackup status code: 9878 ................................................ 1093
NetBackup status code: 9879 ................................................ 1093
NetBackup status code: 9882 ................................................ 1094
NetBackup status code: 9883 ................................................ 1094
NetBackup status code: 9888 ................................................ 1094
NetBackup status code: 9890 ................................................ 1095
NetBackup status code: 9891 ................................................ 1095
NetBackup status code: 9894 ................................................ 1095
NetBackup status code: 9895 ................................................ 1096
NetBackup status code: 9896 ................................................ 1096
NetBackup status code: 9897 ................................................ 1097
NetBackup status code: 9901 ................................................ 1097
NetBackup status code: 9902 ................................................ 1098
NetBackup status code: 9903 ................................................ 1098
 Contents 68

NetBackup status code: 9904 ................................................ 1098

NetBackup status code: 9905 ................................................ 1098
NetBackup status code: 9906 ................................................ 1099
NetBackup status code: 9907 ................................................ 1099
NetBackup status code: 9909 ................................................ 1099
NetBackup status code: 9910 ................................................ 1099
NetBackup status code: 9911 ................................................ 1100
NetBackup status code: 9912 ................................................ 1100
NetBackup status code: 9913 ................................................ 1100
NetBackup status code: 9914 ................................................ 1100
NetBackup status code: 9915 ................................................ 1101
NetBackup status code: 9916 ................................................ 1101
NetBackup status code: 9917 ................................................ 1101
NetBackup status code: 9918 ................................................ 1102
NetBackup status code: 9919 ................................................ 1102
NetBackup status code: 9920 ................................................ 1102
NetBackup status code: 9921 ................................................ 1102
NetBackup status code: 9922 ................................................ 1103
NetBackup status code: 9923 ................................................ 1103
NetBackup status code: 9926 ................................................ 1103
NetBackup status code: 9928 ................................................ 1103
NetBackup status code: 9929 ................................................ 1104
NetBackup status code: 9930 ................................................ 1104
NetBackup status code: 9931 ................................................ 1104
NetBackup status code: 9934 ................................................ 1105
NetBackup status code: 9935 ................................................ 1105
NetBackup status code: 9936 ................................................ 1105
NetBackup status code: 9937 ................................................ 1105
NetBackup status code: 9938 ................................................ 1106
NetBackup status code: 9939 ................................................ 1106
NetBackup status code: 9940 ................................................ 1106
NetBackup status code: 9941 ................................................ 1106
NetBackup status code: 9942 ................................................ 1107
NetBackup status code: 9944 ................................................ 1107
NetBackup status code: 9946 ................................................ 1107
NetBackup status code: 9947 ................................................ 1107
NetBackup status code: 9948 ................................................ 1108
NetBackup status code: 9949 ................................................ 1108
NetBackup status code: 9968 ................................................ 1108
NetBackup status code: 9969 ................................................ 1108
NetBackup status code: 9970 ................................................ 1109
NetBackup status code: 9971 ................................................ 1109
NetBackup status code: 9972 ................................................ 1109
 Contents 69

NetBackup status code: 9973 ................................................ 1109

NetBackup status code: 9974 ................................................ 1110
NetBackup status code: 9975 ................................................ 1110
NetBackup status code: 9976 ................................................ 1110
NetBackup status code: 9977 ................................................ 1110
NetBackup status code: 9978 ................................................ 1111
NetBackup status code: 9979 ................................................ 1111
NetBackup status code: 9980 ................................................ 1111
NetBackup status code: 9981 ................................................ 1112
NetBackup status code: 9982 ................................................ 1112
NetBackup status code: 9983 ................................................ 1112
NetBackup status code: 9984 ................................................ 1112
NetBackup status code: 9986 ................................................ 1113
NetBackup status code: 9990 ................................................ 1113
NetBackup status code: 9991 ................................................ 1113
NetBackup status code: 9992 ................................................ 1114
NetBackup status code: 9993 ................................................ 1114
NetBackup status code: 9996 ................................................ 1114
NetBackup KMS status codes ...................................................... 1114
NetBackup KMS status code: 1 .............................................. 1115
NetBackup KMS status code: 2 .............................................. 1115
NetBackup KMS status code: 3 .............................................. 1115
NetBackup KMS status code: 4 .............................................. 1115
NetBackup KMS status code: 5 .............................................. 1116
NetBackup KMS status code: 6 .............................................. 1116
NetBackup KMS status code: 7 .............................................. 1116
NetBackup KMS status code: 8 .............................................. 1116
NetBackup KMS status code: 9 .............................................. 1116
NetBackup KMS status code: 10 ............................................ 1117
NetBackup KMS status code: 11 ............................................ 1117
NetBackup KMS status code: 12 ............................................ 1117
NetBackup KMS status code: 13 ............................................ 1117
NetBackup KMS status code: 14 ............................................ 1117
NetBackup KMS status code: 15 ............................................ 1117
NetBackup KMS status code: 16 ............................................ 1118
NetBackup KMS status code: 17 ............................................ 1118
NetBackup KMS status code: 18 ............................................ 1118
NetBackup KMS status code: 19 ............................................ 1118
NetBackup KMS status code: 20 ............................................ 1118
NetBackup KMS status code: 21 ............................................ 1119
NetBackup KMS status code: 22 ............................................ 1119
NetBackup KMS status code: 23 ............................................ 1119
NetBackup KMS status code: 24 ............................................ 1119
 Contents 70

NetBackup KMS status code: 25 ............................................ 1119

NetBackup KMS status code: 26 ............................................ 1119
NetBackup KMS status code: 27 ............................................ 1120
NetBackup KMS status code: 28 ............................................ 1120
NetBackup KMS status code: 29 ............................................ 1120
NetBackup KMS status code: 30 ............................................ 1120
NetBackup KMS status code: 31 ............................................ 1120
NetBackup KMS status code: 32 ............................................ 1120
NetBackup KMS status code: 33 ............................................ 1121
NetBackup KMS status code: 34 ............................................ 1121
NetBackup KMS status code: 35 ............................................ 1121
NetBackup KMS status code: 36 ............................................ 1121
NetBackup KMS status code: 37 ............................................ 1121
NetBackup KMS status code: 38 ............................................ 1121
NetBackup KMS status code: 39 ............................................ 1122
NetBackup KMS status code: 40 ............................................ 1122
NetBackup KMS status code: 41 ............................................ 1122
NetBackup KMS status code: 42 ............................................ 1122
NetBackup KMS status code: 44 ............................................ 1122
NetBackup KMS status code: 45 ............................................ 1123
NetBackup KMS status code: 46 ............................................ 1123
NetBackup KMS status code: 47 ............................................ 1123
NetBackup KMS status code: 48 ............................................ 1123
NetBackup KMS status code: 49 ............................................ 1123
NetBackup KMS status code: 50 ............................................ 1124
NetBackup KMS status code: 51 ............................................ 1124
NetBackup KMS status code: 52 ............................................ 1124
NetBackup KMS status code: 53 ............................................ 1124
NetBackup KMS status code: 54 ............................................ 1124
NetBackup KMS status code: 55 ............................................ 1125
NetBackup KMS status code: 56 ............................................ 1125
NetBackup KMS status code: 57 ............................................ 1125
NetBackup KMS status code: 58 ............................................ 1125
NetBackup KMS status code: 59 ............................................ 1125
NetBackup KMS status code: 60 ............................................ 1126
NetBackup KMS status code: 61 ............................................ 1126
NetBackup KMS status code: 62 ............................................ 1126
NetBackup KMS status code: 63 ............................................ 1126
NetBackup KMS status code: 1287 ......................................... 1127
 Contents 71

Chapter 2 Media Manager status codes ..................................... 1128

Media Manager status codes ....................................................... 1128

Media Manager status code 1 ................................................ 1128
Media Manager status code 2 ................................................ 1128
Media Manager status code 3 ................................................ 1129
Media Manager status code 4 ................................................ 1129
Media Manager status code 5 ................................................ 1130
Media Manager status code 6 ................................................ 1130
Media Manager status code 7 ................................................ 1130
Media Manager status code 8 ................................................ 1130
Media Manager status code 9 ................................................ 1131
Media Manager status code 10 .............................................. 1131
Media Manager status code 11 .............................................. 1132
Media Manager status code 12 .............................................. 1132
Media Manager status code 13 .............................................. 1133
Media Manager status code 14 .............................................. 1133
Media Manager status code 15 .............................................. 1133
Media Manager status code 16 .............................................. 1134
Media Manager status code 18 .............................................. 1134
Media Manager status code 19 .............................................. 1135
Media Manager status code 20 .............................................. 1135
Media Manager status code 21 .............................................. 1135
Media Manager status code 22 .............................................. 1136
Media Manager status code 23 .............................................. 1136
Media Manager status code 25 .............................................. 1136
Media Manager status code 26 .............................................. 1136
Media Manager status code 27 .............................................. 1137
Media Manager status code 28 .............................................. 1137
Media Manager status code 32 .............................................. 1138
Media Manager status code 34 .............................................. 1138
Media Manager status code 35 .............................................. 1138
Media Manager status code 36 .............................................. 1139
Media Manager status code 37 .............................................. 1139
Media Manager status code 39 .............................................. 1140
Media Manager status code 40 .............................................. 1140
Media Manager status code 41 .............................................. 1140
Media Manager status code 42 .............................................. 1141
Media Manager status code 43 .............................................. 1141
Media Manager status code 44 .............................................. 1142
Media Manager status code 45 .............................................. 1142
Media Manager status code 46 .............................................. 1143
Media Manager status code 47 .............................................. 1143
 Contents 72

Media Manager status code 48 .............................................. 1144

Media Manager status code 49 .............................................. 1144
Media Manager status code 50 .............................................. 1144
Media Manager status code 51 .............................................. 1145
Media Manager status code 52 .............................................. 1145
Media Manager status code 53 .............................................. 1145
Media Manager status code 54 .............................................. 1146
Media Manager status code 55 .............................................. 1146
Media Manager status code 57 .............................................. 1147
Media Manager status code 58 .............................................. 1147
Media Manager status code 59 .............................................. 1148
Media Manager status code 60 .............................................. 1148
Media Manager status code 61 .............................................. 1148
Media Manager status code 62 .............................................. 1149
Media Manager status code 63 .............................................. 1149
Media Manager status code 64 .............................................. 1149
Media Manager status code 65 .............................................. 1150
Media Manager status code 67 .............................................. 1150
Media Manager status code 68 .............................................. 1151
Media Manager status code 69 .............................................. 1151
Media Manager status code 70 .............................................. 1152
Media Manager status code 71 .............................................. 1153
Media Manager status code 72 .............................................. 1153
Media Manager status code 73 .............................................. 1154
Media Manager status code 74 .............................................. 1154
Media Manager status code 75 .............................................. 1154
Media Manager status code 76 .............................................. 1155
Media Manager status code 78 .............................................. 1155
Media Manager status code 79 .............................................. 1155
Media Manager status code 80 .............................................. 1156
Media Manager status code 81 .............................................. 1156
Media Manager status code 82 .............................................. 1157
Media Manager status code 83 .............................................. 1158
Media Manager status code 84 .............................................. 1158
Media Manager status code 85 .............................................. 1158
Media Manager status code 86 .............................................. 1159
Media Manager status code 87 .............................................. 1159
Media Manager status code 88 .............................................. 1159
Media Manager status code 89 .............................................. 1160
Media Manager status code 90 .............................................. 1160
Media Manager status code 92 .............................................. 1161
Media Manager status code 93 .............................................. 1161
Media Manager status code 94 .............................................. 1161
 Contents 73

Media Manager status code 95 .............................................. 1162

Media Manager status code 96 .............................................. 1162
Media Manager status code 97 .............................................. 1163
Media Manager status code 101 ............................................ 1164
Media Manager status code 102 ............................................ 1164
Media Manager status code 104 ............................................ 1165
Media Manager status code 105 ............................................ 1165
Media Manager status code 109 ............................................ 1165
Media Manager status code 110 ............................................. 1166
Media Manager status code 111 ............................................. 1167
Media Manager status code 112 ............................................. 1167
Media Manager status code 113 ............................................. 1167
Media Manager status code 114 ............................................. 1167
Media Manager status code 115 ............................................. 1168
Media Manager status code 116 ............................................. 1168
Media Manager status code 117 ............................................. 1169
Media Manager status code 118 ............................................. 1169
Media Manager status code 119 ............................................. 1169
Media Manager status code 121 ............................................ 1170
Media Manager status code 122 ............................................ 1170
Media Manager status code 126 ............................................ 1170
Media Manager status code 127 ............................................ 1171
Media Manager status code 129 ............................................ 1171
Media Manager status code 130 ............................................ 1172
Media Manager status code 131 ............................................ 1172
Media Manager status code 132 ............................................ 1173
Media Manager status code 133 ............................................ 1173
Media Manager status code 134 ............................................ 1174
Media Manager status code 135 ............................................ 1174
Media Manager status code 136 ............................................ 1174
Media Manager status code 137 ............................................ 1175
Media Manager status code 138 ............................................ 1175
Media Manager status code 139 ............................................ 1175
Media Manager status code 140 ............................................ 1176
Media Manager status code 141 ............................................ 1176
Media Manager status code 142 ............................................ 1176
Media Manager status code 143 ............................................ 1177
Media Manager status code 144 ............................................ 1177
Media Manager status code 145 ............................................ 1177
Media Manager status code 146 ............................................ 1177
Media Manager status code 147 ............................................ 1178
Media Manager status code 148 ............................................ 1178
Media Manager status code 149 ............................................ 1178
 Contents 74

Media Manager status code 150 ............................................ 1179

Media Manager status code 152 ............................................ 1179
Media Manager status code 153 ............................................ 1180
Media Manager status code 155 ............................................ 1180
Media Manager status code 160 ............................................ 1180
Media Manager status code 162 ............................................ 1181
Media Manager status code 163 ............................................ 1181
Media Manager status code 164 ............................................ 1181
Media Manager status code 165 ............................................ 1182
Media Manager status code 166 ............................................ 1182
Media Manager status code 167 ............................................ 1182
Media Manager status code 168 ............................................ 1183
Media Manager status code 169 ............................................ 1183
Media Manager status code 171 ............................................ 1183
Media Manager status code 172 ............................................ 1183
Media Manager status code 173 ............................................ 1184
Media Manager status code 175 ............................................ 1184
Media Manager status code 176 ............................................ 1184
Media Manager status code 177 ............................................ 1184
Media Manager status code 181 ............................................ 1185
Media Manager status code 182 ............................................ 1186
Media Manager status code 185 ............................................ 1186
Media Manager status code 186 ............................................ 1186
Media Manager status code 187 ............................................ 1187
Media Manager status code 188 ............................................ 1188
Media Manager status code 189 ............................................ 1189
Media Manager status code 190 ............................................ 1189
Media Manager status code 191 ............................................ 1190
Media Manager status code 192 ............................................ 1190
Media Manager status code 193 ............................................ 1190
Media Manager status code 194 ............................................ 1190
Media Manager status code 195 ............................................ 1191
Media Manager status code 196 ............................................ 1191
Media Manager status code 198 ............................................ 1191
Media Manager status code 199 ............................................ 1192

Chapter 3 Device configuration status codes ............................ 1193

Device configuration status codes ................................................ 1193

Device configuration status code 0 ......................................... 1193
Device configuration status code 1 ......................................... 1193
Device configuration status code 2 ......................................... 1194
Device configuration status code 3 ......................................... 1194
 Contents 75

Device configuration status code 7 ......................................... 1195

Device configuration status code 8 ......................................... 1195
Device configuration status code 9 ......................................... 1195
Device configuration status code 10 ........................................ 1195
Device configuration status code 11 ........................................ 1196
Device configuration status code 13 ........................................ 1196
Device configuration status code 14 ........................................ 1196
Device configuration status code 15 ........................................ 1197
Device configuration status code 16 ........................................ 1197
Device configuration status code 17 ........................................ 1198
Device configuration status code 18 ........................................ 1198
Device configuration status code 19 ........................................ 1198
Device configuration status code 21 ........................................ 1199
Device configuration status code 22 ........................................ 1199
Device configuration status code 24 ........................................ 1199
Device configuration status code 25 ........................................ 1200
Device configuration status code 27 ........................................ 1200
Device configuration status code 28 ........................................ 1200
Device configuration status code 29 ........................................ 1201
Device configuration status code 30 ........................................ 1201
Device configuration status code 31 ........................................ 1201
Device configuration status code 33 ........................................ 1202
Device configuration status code 34 ........................................ 1202
Device configuration status code 35 ........................................ 1202
Device configuration status code 36 ........................................ 1203
Device configuration status code 37 ........................................ 1203
Device configuration status code 38 ........................................ 1203
Device configuration status code 39 ........................................ 1203
Device configuration status code 40 ........................................ 1204
Device configuration status code 41 ........................................ 1204
Device configuration status code 42 ........................................ 1204
Device configuration status code 44 ........................................ 1204
Device configuration status code 48 ........................................ 1205
Device configuration status code 49 ........................................ 1205
Device configuration status code 51 ........................................ 1206
Device configuration status code 52 ........................................ 1206
Device configuration status code 53 ........................................ 1206
Device configuration status code 55 ........................................ 1207
Device configuration status code 56 ........................................ 1207
Device configuration status code 57 ........................................ 1207
Device configuration status code 58 ........................................ 1208
Device configuration status code 59 ........................................ 1208
Device configuration status code 60 ........................................ 1208
 Contents 76

Device configuration status code 61 ........................................ 1209

Device configuration status code 62 ........................................ 1209
Device configuration status code 63 ........................................ 1209
Device configuration status code 64 ........................................ 1210
Device configuration status code 65 ........................................ 1210
Device configuration status code 66 ........................................ 1210
Device configuration status code 67 ........................................ 1210
Device configuration status code 68 ........................................ 1211
Device configuration status code 69 ........................................ 1211
Device configuration status code 70 ........................................ 1211
Device configuration status code 71 ........................................ 1211
Device configuration status code 72 ........................................ 1212
Device configuration status code 73 ........................................ 1212
Device configuration status code 74 ........................................ 1212
Device configuration status code 75 ........................................ 1213
Device configuration status code 76 ........................................ 1213
Device configuration status code 77 ........................................ 1213
Device configuration status code 78 ........................................ 1213
Device configuration status code 79 ........................................ 1214
Device configuration status code 81 ........................................ 1214
Device configuration status code 82 ........................................ 1215
Device configuration status code 83 ........................................ 1215
Device configuration status code 84 ........................................ 1215
Device configuration status code 85 ........................................ 1216
Device configuration status code 86 ........................................ 1216
Device configuration status code 87 ........................................ 1216
Device configuration status code 88 ........................................ 1217
Device configuration status code 89 ........................................ 1217
Device configuration status code 90 ........................................ 1217
Device configuration status code 91 ........................................ 1218
Device configuration status code 92 ........................................ 1218
Device configuration status code 93 ........................................ 1218
Device configuration status code 95 ........................................ 1219
Device configuration status code 96 ........................................ 1219
Device configuration status code 97 ........................................ 1219
Device configuration status code 98 ........................................ 1219
Device configuration status code 99 ........................................ 1220
Device configuration status code 100 ...................................... 1220
Device configuration status code 101 ...................................... 1220
 Contents 77

Chapter 4 Device management status codes ............................ 1221

Device management status codes ................................................ 1221
Device management status code 1 ......................................... 1221
Device management status code 2 ......................................... 1221
Device management status code 3 ......................................... 1222
Device management status code 4 ......................................... 1222
Device management status code 5 ......................................... 1223
Device management status code 6 ......................................... 1223
Device management status code 7 ......................................... 1223
Device management status code 8 ......................................... 1224
Device management status code 10 ....................................... 1224
Device management status code 12 ....................................... 1225
Device management status code 13 ....................................... 1225
Device management status code 14 ....................................... 1225
Device management status code 15 ....................................... 1226
Device management status code 16 ....................................... 1226
Device management status code 17 ....................................... 1226
Device management status code 19 ....................................... 1227
Device management status code 20 ....................................... 1227
Device management status code 21 ....................................... 1227
Device management status code 22 ....................................... 1227
Device management status code 23 ....................................... 1228
Device management status code 24 ....................................... 1228
Device management status code 25 ....................................... 1229
Device management status code 26 ....................................... 1229
Device management status code 27 ....................................... 1229
Device management status code 28 ....................................... 1230
Device management status code 30 ....................................... 1230
Device management status code 32 ....................................... 1230
Device management status code 33 ....................................... 1231
Device management status code 35 ....................................... 1231
Device management status code 36 ....................................... 1232
Device management status code 37 ....................................... 1232
Device management status code 38 ....................................... 1232
Device management status code 39 ....................................... 1233
Device management status code 40 ....................................... 1233
Device management status code 41 ....................................... 1233
Device management status code 42 ....................................... 1234
Device management status code 44 ....................................... 1234
Device management status code 46 ....................................... 1234
Device management status code 47 ....................................... 1235
Device management status code 48 ....................................... 1235
 Contents 78

Device management status code 49 ....................................... 1236

Device management status code 50 ....................................... 1236
Device management status code 52 ....................................... 1236
Device management status code 53 ....................................... 1237
Device management status code 55 ....................................... 1237
Device management status code 56 ....................................... 1237
Device management status code 58 ....................................... 1237
Device management status code 59 ....................................... 1237
Device management status code 60 ....................................... 1238
Device management status code 61 ....................................... 1238
Device management status code 62 ....................................... 1239
Device management status code 63 ....................................... 1239
Device management status code 64 ....................................... 1239
Device management status code 65 ....................................... 1239
Device management status code 66 ....................................... 1240
Device management status code 69 ....................................... 1240
Device management status code 70 ....................................... 1240
Device management status code 71 ....................................... 1241
Device management status code 72 ....................................... 1241
Device management status code 73 ....................................... 1241
Device management status code 74 ....................................... 1241
Device management status code 75 ....................................... 1242
Device management status code 76 ....................................... 1242
Device management status code 77 ....................................... 1242
Device management status code 78 ....................................... 1243
Device management status code 79 ....................................... 1243
Device management status code 80 ....................................... 1243
Device management status code 81 ....................................... 1244
Device management status code 82 ....................................... 1244
Device management status code 83 ....................................... 1244
Device management status code 84 ....................................... 1244

Chapter 5 Robotic status codes ..................................................... 1245

Robotic status codes ................................................................. 1245
Robotic status code 200 ....................................................... 1245
Robotic status code 201 ....................................................... 1245
Robotic status code 202 ....................................................... 1246
Robotic status code 203 ....................................................... 1247
Robotic status code 204 ....................................................... 1247
Robotic status code 205 ....................................................... 1247
Robotic status code 206 ....................................................... 1248
Robotic status code 207 ....................................................... 1248
 Contents 79

Robotic status code 208 ....................................................... 1248

Robotic status code 209 ....................................................... 1249
Robotic status code 210 ....................................................... 1249
Robotic status code 211 ....................................................... 1250
Robotic status code 212 ....................................................... 1250
Robotic status code 213 ....................................................... 1251
Robotic status code 214 ....................................................... 1251
Robotic status code 215 ....................................................... 1251
Robotic status code 216 ....................................................... 1252
Robotic status code 217 ....................................................... 1252
Robotic status code 218 ....................................................... 1252
Robotic status code 219 ....................................................... 1253
Robotic status code 220 ....................................................... 1253
Robotic status code 221 ....................................................... 1253
Robotic status code 222 ....................................................... 1254
Robotic status code 223 ....................................................... 1254
Robotic status code 224 ....................................................... 1254
Robotic status code 225 ....................................................... 1255
Robotic status code 226 ....................................................... 1255
Robotic status code 228 ....................................................... 1256
Robotic status code 229 ....................................................... 1256
Robotic status code 230 ....................................................... 1256
Robotic status code 232 ....................................................... 1257
Robotic status code 233 ....................................................... 1257
Robotic status code 234 ....................................................... 1258
Robotic status code 235 ....................................................... 1258
Robotic status code 236 ....................................................... 1258
Robotic status code 237 ....................................................... 1259
Robotic status code 238 ....................................................... 1259
Robotic status code 239 ....................................................... 1259
Robotic status code 240 ....................................................... 1259
Robotic status code 242 ....................................................... 1260
Robotic status code 243 ....................................................... 1260
Robotic status code 244 ....................................................... 1260
Robotic status code 245 ....................................................... 1260
Robotic status code 246 ....................................................... 1261
Robotic status code 249 ....................................................... 1261
Robotic status code 250 ....................................................... 1262
Robotic status code 251 ....................................................... 1262
Robotic status code 252 ....................................................... 1262
Robotic status code 253 ....................................................... 1262
Robotic status code 254 ....................................................... 1262
Robotic status code 255 ....................................................... 1262
 Contents 80

Robotic status code 256 ....................................................... 1263

Robotic status code 257 ....................................................... 1263
Robotic status code 258 ....................................................... 1263
Robotic status code 259 ....................................................... 1263
Robotic status code 260 ....................................................... 1264
Robotic status code 261 ....................................................... 1264
Robotic status code 262 ....................................................... 1264

Chapter 6 Robotic error codes ....................................................... 1266

Robotic error codes ................................................................... 1266

Robot Error status code 1 ..................................................... 1266
Robot Error status code 2 ..................................................... 1266
Robot Error status code 3 ..................................................... 1267
Robot Error status code 4 ..................................................... 1267
Robot Error status code 5 ..................................................... 1267
Robot Error status code 6 ..................................................... 1268
Robot Error status code 7 ..................................................... 1268
Robot Error status code 8 ..................................................... 1268
Robot Error status code 9 ..................................................... 1268
Robot Error status code 10 ................................................... 1269
Robot Error status code 11 .................................................... 1269
Robot Error status code 12 ................................................... 1270
Robot Error status code 13 ................................................... 1270
Robot Error status code 14 ................................................... 1270
Robot Error status code 16 ................................................... 1270
Robot Error status code 17 ................................................... 1271

Chapter 7 Security services status codes ................................... 1272

Security services status codes ..................................................... 1272
Security services status code 93 ............................................ 1272
Security services status code 94 ............................................ 1272
Security services status code 95 ............................................ 1273
Security services status code 96 ............................................ 1273
Security services status code 97 ............................................ 1273
Security services status code 98 ............................................ 1273
Security services status code 99 ............................................ 1274
Security services status code 100 ........................................... 1274
Security services status code 101 ........................................... 1274
Security services status code 102 ........................................... 1274
Security services status code 103 ........................................... 1274
Security services status code 104 ........................................... 1275
Security services status code 105 ........................................... 1275
 Contents 81

Security services status code 106 ........................................... 1275

Security services status code 107 ........................................... 1275

Chapter 8 NetBackup alert notification status codes ............... 1277

NetBackup alert notification status codes ....................................... 1277
 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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 83
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: Review 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).
 NetBackup status codes 84
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 - Attempting to
create snapshots for D:\Directory1
1:59:41.229 PM: [2076.2088] <4>
V_Snapshot::V_Snapshot_CreateSnapshot: INF - CREATE request:
C:\Program Files\VERITAS\NetBackup\bin\bpfis create -fim VSP
"D:\ Directory1"
1:59:41.799 PM: [2076.2088] <4>
V_Snapshot::V_Snapshot_ParseBpfisOutput: INF - Snapshot
creation, FIS_ID: 1058813981
1:59:41.799 PM: [2076.2088] <4>
V_Snapshot::V_Snapshot_ParseBpfisOutput: INF - Snapshot creation
EXIT STATUS 11: system call failed
 NetBackup status codes 85
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.
 NetBackup status codes 86
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. Review 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. Review the job details for the cause of the failure. In a full or a differential
backup, transaction logs are truncated for the 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:
 NetBackup status codes 87
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.

One of the following situations can cause the clock discrepancy issue:
■ If the NetApp filer and NetBackup NDMP backup host have a time difference
of more than one hour, a clock discrepancy warning is displayed. This 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 one
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 one 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.
When a VMware agentless restore is performed, the restore can cause one of the
following issues:
■ Failed to detach the vmdk %s or the SCSI controller to which %s vmdk is
attached from the destination VM %s during cleanup.
Manually detach the vmdk or the controller.
■ Deletion of temporary VM %s failed with error %d.
Manually delete the specified VM.
 NetBackup status codes 88
NetBackup status codes

■ Failed to clean the staging location %s on destination VM %s.

Manually delete the staging location.
■ Failed to attach the temporary vmdk %s to the destination VM %s with error
%d.
Make sure that the target VM has at least one Paravirtual controller with available
LUNs.
■ Failed to upload the process rename file to the destination VM %s with error
%d.
Make sure there is sufficient space available in target VM. Review the bpVMutil
log file on the target VM for additional information on this issue.
■ Failed to restore the selected files and folders.
Review the tar log to troubleshoot this issue.
■ Failed to identify the newly attached device on destination VM %s. One possible
cause is that the destination VM user credentials have insufficient permissions.
It is recommended destination VM user credentials have root or administrative
privileges.
Click here to view technical notes and other information on the Veritas Technical
Support website 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.
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 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.
■ See the troubleshooting topic of the appropriate guide for a description of
troubleshooting tools:
 NetBackup status codes 89
NetBackup status codes

■ 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 on the Veritas Technical
Support website 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.
Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 5

Message: Restore failed completely.
 NetBackup status codes 90
NetBackup status codes

Explanation: The following issues can cause this issue:

■ The vCPU for Azure was consumed past the threshold limit.
■ When you restore a replicated copy of EC2 instance to an alternate location,
the key-pair names must be same on the source and the destination region.
■ The source snapshot is removed from the cloud provider.
■ The following are possible causes of granular restore failure:
■ Granular restore is not supported for the file systems and destination hosts
that are created on LVM, LDM, storage pool, all variants of FAT, and volumes
without drive letters.
■ The destination free disk space.
■ The destination file system was read-only.
■ Invalid destination path.
■ Before NetBackup Snapshot Manager version 10.0, vxms indexing was not
supported. The granular restore (GRT) failed when a GRT is attempted from
an older version of NetBackup Snapshot Manager and the source disk had
lvm configured.

Recommended Action: To correct this issue, try the following solutions as

appropriate:
■ If using Azure, contact your cloud provider to increase the threshold limit.
■ If you try to restore a replicated copy of EC2, create a new key-pair in the
destination region. The new key-pair must be consistent with the key-pair in the
source region.
■ Source snapshot must be retained on the cloud provider until the image expiration
duration is selected in the protection plan.
When a VMware agentless restore is performed, the restore can cause one of the
following issues:
■ Failed to upload recovery tool on destination VM %s with error %d.
Make sure there is sufficient space or permissions available at the staging
location.
■ Failed to extract the recovery tool on the destination VM.
Confirm there is sufficient space available at the staging location %s in the target
VM.
When a granular restore fails, perform the following:
■ For lvm and ldm disks granular restore, upgrade the Snapshot Manager to
version 10.0.
 NetBackup status codes 91
NetBackup status codes

■ Ensure that restore destination path is accessible with sufficient privileges and
disk space.
■ The file wise restore error and warning report is available on source host
(Windows or Linux) as follows:
■ Windows host path:
C:\ProgramData\Veritas\CloudPoint\restore\<job-id>/

■ Linux host path: /root/veritas/<job-id>/

These locations provide the details of the disk wise restored file status.
For example:

D#.log -> Existing log file which shows higher level failure
D#-Error.log ->This file is generated only when an error
(at least one) is displayed during the copy process.

This file logs the Actual Exception / OS exception.

D#-Warning.log -> This file is generated only when a warning message
(at least one) is displayed during the restore task.

Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 6

Message: User backup failed
Explanation: The possible causes for this error are as follows:
■ The cloud provider credentials are not updated.
■ Situations that cause a restore operation to fail:
■ For example, if you restore a disk snapshot to the same instance and if the
existing disk is still attached to the instance, the restore operation fails.

Recommended Action: Do the following, as appropriate:

■ Ensure that the appropriate plug-in is configured in the web UI with the
appropriate credentials. If the credentials are changed, ensure that they are
updated from the web UI.
■ Detach the disk from the target instance.
 NetBackup status codes 92
NetBackup status codes

Table 1-1 Restore failed due to SSL certificate issues or connectivity issues
between Snapshot Manager and Azure or Azure Stack

Message Recommended action

Unable to retrieve the certificate CRL. If you Copy the latest CRL into the ECA_CRL_PATH
have configured the ECA_CRL_PATH, ensure path or ensure the CRL distribution point
that valid CRLs are present at the location. URL, from the respective host certificate, is
Check if the CRL URL is accessible from the accessible from the Snapshot Manager.
Snapshot Manager.

The Azure or Azure Stack servers’ certificate Contact your security administrator to ensure
is revoked. Ensure that the certificates are that the server presents a valid certificate.
not revoked by certificate authority.
■ If the certificate was revoked in error,
reissue a certificate for the host.
■ If the certificate was revoked as intended,
an attempted security breach may have
occurred.

The certificate revocation list (CRL) is expired. Ensure that the latest CRL’s are uploaded at
Ensure that the ECA_CRL_PATH is updated the ECA_CRL_PATH path.
with the latest CRL.
You can update the NetBackup CRL cache
manually by using the following command on
Snapshot Manager:

docker exec -i flexsnap-certauth bash -c

'/usr/openv/pdde/pdopensource
/nbcertcmdtool/nbcertcmdtool -atLibPath
/usr/openv/pdde/pdopensource/nbcertcmdtool
-updateCRLCache'

The certificate revocation list (CRL) is not yet Review your Snapshot Manager's system
valid. time or provide a valid CRL.

The date of last update of the certificate Check the CRL using the openssl command
revocation list (CRL) is not in a valid format. or contact your Security Administrator.

The date of next update of the certificate Check the CRL using the openssl command
revocation list (CRL) is not in a valid format. or contact your Security Administrator.
 NetBackup status codes 93
NetBackup status codes

Table 1-1 Restore failed due to SSL certificate issues or connectivity issues
between Snapshot Manager and Azure or Azure Stack
(continued)

Message Recommended action

The Azure or Azure Stack server certificate Review the certificate and ensure the validity
is expired. Ensure that the server has a valid of it by checking the certificate to make sure
certificate. that the end date is valid.

Check if the Snapshot Manager's clock is in

sync with the specified server. Correct the
time on the host, if necessary, and rerun the
operation. If the problem continues, save all
of the error log information and contact
Veritas Technical Support.

The Azure or Azure stack servers certificate Check if the Snapshot Manager’s clock is in
is not yet valid. sync with the specified server. Correct the
time on the host, if necessary, and rerun the
operation. If the problem continues, save all
of the error log information and contact
Veritas Technical Support.

Unable to find the public root and intermediate Ensure that the certificate file is configured
certificates of the Azure Stack server. correctly at the ECA_TRUST_STORE_PATH
located in the bp.conf file on the Snapshot
Manager.

Rerun the operation. If the problem persists,

save all of the error log information and
contact Veritas Technical Support.

Failed to load the Certificate Revocation List Ensure that the valid CRL file is configured
(CRL) from CRL cache. Ensure that the valid on the Snapshot Manager for Azure or Azure
CRL file is configured on the Snapshot Stack by the ECA_CRL_PATH.
Manager for Azure or Azure Stack by
ECA_CRL_PATH.

Failed to connect to the Azure or Azure Stack Ensure network connectivity between the
server. Ensure network connectivity between Snapshot Manager and the Azure or Azure
Snapshot Manager and the Azure or Azure Stack server.
Stack server.

Cannot use the specified SSL cipher for Contact Veritas Technical Support.
Azure or Azure Stack server.
 NetBackup status codes 94
NetBackup status codes

Table 1-1 Restore failed due to SSL certificate issues or connectivity issues
between Snapshot Manager and Azure or Azure Stack
(continued)

Message Recommended action

Operation failed with cURL error: Rerun the operation. If the problem persists,
save all of the error log information and
contact Veritas Technical Support.

Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 9

Message: a necessary extension package is not installed or not configured properly
 NetBackup status codes 95
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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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 db_FLISTsend failed: system call

failed (11)
06/27/95 01:04:01 romb romb media manager terminated by parent
process
 NetBackup status codes 96
NetBackup status codes

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 semsys:seminfo_semmni=300
set semsys:seminfo_semmns=300
set semsys:seminfo_semmsl=300
set semsys:seminfo_semmnu=600

Set these attributes to a value great enough to provide resources to all

applications on your system.
 NetBackup status codes 97
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.
In case of NetApp storage, ensure that the following configurations are done in
NetApp system manager:
■ Enable Make snapshot (.snapshot) directory visible option.
■ Disable Automatically delete older Snapshot copies.
Click here to view technical notes and other information on the Veritas Technical
Support website 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
 NetBackup status codes 98
NetBackup status codes

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
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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 99
NetBackup status codes

NetBackup status code: 13

Message: file read failed
Explanation: A read of a file or socket failed.
The possible causes include the following:
■ 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:

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)'
 NetBackup status codes 100
NetBackup status codes

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.
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:

 NetBackup status codes 101
NetBackup status codes

■ 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:

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: INF - Processing /var

bpbkar: ERR - get_disk_info() failed, status 13
bpbkar: ERR - tpc_get_disk_info() failed: err 13
bpbkar: ERR - bpbkar FATAL exit status = 13: file read failed
bpbkar: INF - 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):
 NetBackup status codes 102
NetBackup status codes

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 on the Veritas Technical
Support website about this status code.

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.
 NetBackup status codes 103
NetBackup status codes

■ 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
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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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 of the error information and contact Veritas
Technical Support.
Click here to view technical notes and other information on the Veritas Technical
Support website 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 of the error information and contact Veritas
Technical Support.
 NetBackup status codes 104
NetBackup status codes

Click here to view technical notes and other information on the Veritas Technical
Support website 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.
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 on the Veritas Technical
Support website 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.
 NetBackup status codes 105
NetBackup status codes

■ 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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 20

Message: invalid command parameter
Explanation: The following issues may cause this error:
■ 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.
■ The wrong parameters are used when you run a command line.
■ If you protect the NAS arrays using the VSO FIM snapshot method, Data mover
is not supported to perform off-host backup.
■ For BigData policies, the media server and the backup hosts must use the same
NetBackup version.
Recommended Action: Do the following, as appropriate:
■ Review 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. Review 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
 NetBackup status codes 106
NetBackup status codes

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
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
 NetBackup status codes 107
NetBackup status codes

cache partition is not already in use. If the cache partition is already in use,
status code 20 occurs.
Review 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.

■ 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, review the
/usr/openv/netbackup/bin/version file.

■ On Windows NetBackup servers, review the

install_path\NetBackup\version.txt file or the About NetBackup item
on the Help menu.
■ On Microsoft Windows clients, review 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 you protect NAS arrays using VSO FIM snapshot method, perform off-host
backup using an alternate client.
■ For BigData policies, the media server and the backup hosts must use the same
NetBackup version.
■ 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 review the resulting log.
 NetBackup status codes 108
NetBackup status codes

Click here to view technical notes and other information on the Veritas Technical
Support website 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.
■ 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 on the Veritas Technical
Support website 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.
 NetBackup status codes 109
NetBackup status codes

■ 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 on the Veritas Technical
Support website 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:
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 on the Veritas Technical
Support website 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:
 NetBackup status codes 110
NetBackup status codes

■ 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/22 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/22 14:05:48 ruble crabtree.null.com successfully wrote
backup id crabtree.null.com_1643637900, copy 1, fragment 1,
440864 Kbytes at 628.538 Kbytes/sec
01/31/22 14:05:51 netbackup crabtree.null.com CLIENT
crabtree.null.com POLICY Remote3SysFullW SCHED Sirius EXIT
STATUS 24 (socket write failed)

■ 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 on the Veritas Technical
Support website 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 the NetBackup
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.
 NetBackup status codes 111
NetBackup status codes

For RHV, the error might occur when the virtualization server is unreachable.
For VMware, the error might occur when the feature
VIRTUALIZATION_HOSTS_SECURE_CONNECT_ENABLED is enabled and the virtualization
servers CA certificate’s are not added in ECA configured trust store.
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

■ 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
 NetBackup status codes 112
NetBackup status codes

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 Veritas Technical Support website to ensure that all recommended
NetBackup patches are installed.
■ 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.
■ 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 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.
■ 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.
 NetBackup status codes 113
NetBackup status codes

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.
■ 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.

■ For RHV:
■ Ensure that the RHV credentials are correct and the virtualization server is
accessible.

■ For VMware:
 NetBackup status codes 114
NetBackup status codes

■ When the VIRTUALIZATION_HOSTS_SECURE_CONNECT_ENABLED option is

enabled, you must verify the placement of the certificates and CRLs. Verify
whether the VMware virtualization servers' (vCenter, ESX, ESXi) certificates
and CRLs are added to the respective ECA configured trust store and the
CRL path.
■ Ensure that the certificates and the CRL files are in the correct format and
the trust store file and the CRL files are not corrupted.
■ Only the PEM certificate format for file-based trust store & Windows trust
store are supported for virtualization servers. P7b or DER format file based
trust store is not supported. When this feature is enabled, the certificate ECA
store should either be Windows certificate store or file based PEM format
store.

■ For Nutanix AHV:

■ Ensure that the CA certificate is added to the NetBackup trust store. Refer
to the Nutanix AHV Administrator’s Guide for more details.

Click here to view technical notes and other information on the Veritas Technical
Support website 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.
This error may also occur during certificate enrollment if the public key infrastructure
(PKI) artifacts are not valid. For example: The error may occur if the NetBackup
8.2 or later master server cannot identify the issuer of the host certificate.
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 review the resulting
debug log.
If the error has occurred during the certificate enrollment process, verify the following:
■ Verify the PKI artifacts by running these commands:
■ nbcertcmd -listAllCertificates [-jks] - Run on the master server to
display the web server certificate information from Java keystore.
 NetBackup status codes 115
NetBackup status codes

■ nbcertcmd -listCACertDetails -ECA - Run on the host to list the details

of the CA certificates that are stored its trust store.

■ Ensure that the issuers of the client and server certificates are available in each
other’s trust stores.
Click here to view technical notes and other information on the Veritas Technical
Support website 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
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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 116
NetBackup status codes

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 on the Veritas Technical
Support website about this status code.

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 117
NetBackup status codes

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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 33

Message: failed while trying to send mail
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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 118
NetBackup status codes

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
For Hyper-V, Hyper-V servers or SCVMM servers with IPv6 addresses are not
supported. For VMware, using IPv6 addresses to refer to NetBackup clients are
not supported.
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.
■ 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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 37

Message: operation requested by an invalid server
 NetBackup status codes 119
NetBackup status codes

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.
If a server or NetBackup Remote Administration Console has more than one host
name (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, 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.
When a VMware agentless restore is performed, the restore can cause one of the
following issues:
■ The operating system where the files were backed up does not match the
operating system where NetBackup attempted to restore the files.
Select a virtual machine for the restore that has the same operating system as
the backup virtual machine. Confirm that the operating system type that is
specified in target VM properties matches to the operating system that is installed
in the target VM.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 38

Message: could not get group information
 NetBackup status codes 120
NetBackup status codes

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 40

Message: network connection broken
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.
 NetBackup status codes 121
NetBackup status codes

■ 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, 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.
■ 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 on the Veritas Technical
Support website 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.
■ NetBackup uses the available bandwidth to its 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.
 NetBackup status codes 122
NetBackup status codes

■ Connection between the master server and a NAT client failed.

Recommended Action: Do the following, as appropriate:
■ If you backup to many files, use Host Properties on the NetBackup server to
change Client read timeout to a much higher value (for example: 4000). These
settings are on the Universal Settings tab in the Master Server Properties
dialog box. The default for this time out 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 time out 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:
■ 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

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.
 NetBackup status codes 123
NetBackup status codes

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.
■ 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.
 NetBackup status codes 124
NetBackup status codes

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
time out 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 time-out interval.
■ Check the Veritas Technical Support website to ensure that all recommended
NetBackup patches are installed.
■ 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).
■ 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.

■ If connection between the master server and a NAT client failed, do the following:
■ Ensure that the subscriber service on the client is up and running.
■ If the problem persists, restart the client services and ensure that the
subscriber service is connected with the NetBackup Messaging Broker (or
nbmqbroker) service.
 NetBackup status codes 125
NetBackup status codes

Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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.
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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 44

Message: network write failed
 NetBackup status codes 126
NetBackup status codes

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

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.
 NetBackup status codes 127
NetBackup status codes

■ 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.
■ The server from where you enroll the external certificate for a remote host is
not listed in the SERVER configuration option on the remote host.
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
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.
 NetBackup status codes 128
NetBackup status codes

■ 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:
https://www.veritas.com/support/en_US/article.100029136
■ If the error occurs during external certificate enrollment, do the following:
■ Add the server name from where you want to enroll the external certificate
for a remote host in its SERVER configuration option.

Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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:
■ 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,
 NetBackup status codes 129
NetBackup status codes

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 50

Message: Client process aborted
Explanation: One of the following has occurred:
 NetBackup status codes 130
NetBackup status codes

■ The client backup terminates abnormally. For example, a NetBackup master or

media server is shut down 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.
■ When NBUX is deployed on AKS, the max pods per node setting limits the
number of pods (User and System) that can be created on the nodes from node
pool. This number need to be set according to calculation:
■ MAX pods per node = (RAM size * 2) + number of kube-system pods[10] +
No of nodes + 2

■ When NBUX is deployed on AKS, vnet needs to have sufficient number of free
IP addresses.
■ MAX pods per node = (RAM size * 2) + number of kube-system pods[10] +
No of nodes + 2

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 the 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.
 NetBackup status codes 131
NetBackup status codes

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.
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.

■ Review the following when NetBackup is deployed on a Kubernetes deployment:

■ Check the number of pending pods. Post that to ensure that the issue
occurred due to the node pool level max pods setting, and check if the
workflow runner or data mover pods are in pending state. Delete the node
pool and recreate the node pool with appropriate number to max pods using
the following formula:
■ MAX pods per node = (RAM size * 2) + number of kube-system pods[10]
+ No of nodes + 2

■ Check the number of pending pods. Post that to ensure that there are sufficient
number of free IPs are available. The administrator needs to ensure that sufficient
number of IPs are available.
Click here to view technical notes and other information on the Veritas Technical
Support website 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, bpdbm, 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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 132
NetBackup status codes

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.
■ 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 on the Veritas Technical
Support website 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.
 NetBackup status codes 133
NetBackup status codes

■ 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 on the Veritas Technical
Support website about this status code.

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.
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

 NetBackup status codes 134
NetBackup status codes

■ 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 on the Veritas Technical
Support website 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.
Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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
 NetBackup status codes 135
NetBackup status codes

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:

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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 58

Message: can’t connect to client
Explanation: The following items can cause this issue:
■ The server was unable to connect to the client.
■ The Hadoop or HBase application server port is not specified correctly when
the credentials are provided using the tpconfig command.
Recommended Action: Resolve network communication problems.
 NetBackup status codes 136
NetBackup status codes

See "Resolving network communication problems" in the NetBackup Troubleshooting

Guide.
When using Hadoop or HBase, verify that the application server port number is
updated correctly when using the tpconfig command.
Click here to view technical notes and other information on the Veritas Technical
Support website 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.
■ 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.
 NetBackup status codes 137
NetBackup status codes

■ 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.
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:
 NetBackup status codes 138
NetBackup status codes

https://www.veritas.com/support/en_US/article.100029136
Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

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.
For more information, review this technical article:
https://www.veritas.com/support/en_US/article.100039945
 NetBackup status codes 139
NetBackup status codes

Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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.

■ 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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 140
NetBackup status codes

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 on the Veritas Technical
Support website 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.
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.
 NetBackup status codes 141
NetBackup status codes

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

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.
 NetBackup status codes 142
NetBackup status codes

■ 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 on the Veritas Technical
Support website 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.
■ Solaris, AIX, or HP operating systems are not supported on the backup hosts
that are used during Red Hat Virtualization backups.
Recommended Action: Do the following, as appropriate:
■ VMware Intelligent Policy: Check for duplication of the VM_name of the VMs in
the policy.
■ 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.
■ NetBackup Snapshot Client: Remove the ALL_LOCAL_DRIVES entry from the file
list.
■ For more information on the supported operating systems for backup hosts,
refer to the NetBackup Web UI RHV Administrator's Guide.
 NetBackup status codes 143
NetBackup status codes

■ For the errors that are related to Hypervisor policy and Nutanix AHV, refer to
the Nutanix AHV Administrator’s Guide.
Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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.
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.

 NetBackup status codes 144
NetBackup status codes

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 74

Message: client timed out waiting for bpstart_notify to complete
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.
 NetBackup status codes 145
NetBackup status codes

Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 77

Message: execution of the specified system command returned a nonzero status
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.
 NetBackup status codes 146
NetBackup status codes

■ 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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 147
NetBackup status codes

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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 81

Message: Media Manager volume daemon (vmd) is not active
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.
 NetBackup status codes 148
NetBackup status codes

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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.
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:
 NetBackup status codes 149
NetBackup status codes

■ 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
/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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 84

Message: media write error
 NetBackup status codes 150
NetBackup status codes

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).
■ 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.
 NetBackup status codes 151
NetBackup status codes

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.

■ If you receive this error message when a GLACIER or LIFECYCLE backup job
fails, the error is related to the Amazon lifecycle policy and occurs in the following
situations:
■ The Amazon lifecycle policy that NetBackup uses cannot be applied. The
Amazon GLACIER or LIFECYCLE storage class is not supported for the
region to which the bucket belongs. Recreate the disk pool with the bucket
in the supported region.
■ A different Amazon lifecycle policy other than what NetBackup uses already
exists. Remove the policy that is not used by NetBackup and rerun the job.
■ The error occurred while creating the Amazon lifecycle policy that NetBackup
uses to back up data to Amazon. Check the bptm logs for more details.

Click here to view technical notes and other information on the Veritas Technical
Support website 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).
 NetBackup status codes 152
NetBackup status codes

■ 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.
■ 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 on the Veritas Technical
Support website 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.
 NetBackup status codes 153
NetBackup status codes

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 on the Veritas Technical
Support website about this status code.

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.
When Amazon AWS is used as cloud storage:
■ Verify that you have SSL enabled for communication.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 88

Message: OpenStorage WORM lock error.
Explanation: The OpenStorage plug-in encountered an error during a WORM lock
operation.
 NetBackup status codes 154
NetBackup status codes

Recommended Action: Look at the OpenStorage storage server and ensure that
configuration of the storage device is consistent with NetBackup. Review the bptm
and the bpdm logs for more detailed messages and OST error codes for more
information about these failures.
Click here to view technical notes and other information on the Veritas Technical
Support website 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.
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).
 NetBackup status codes 155
NetBackup status codes

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 on the Veritas Technical
Support website 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.
■ 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.
 NetBackup status codes 156
NetBackup status codes

■ 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 on the Veritas Technical
Support website 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.
■ 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 on the Veritas Technical
Support website 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.
 NetBackup status codes 157
NetBackup status codes

■ 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.
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 on the Veritas Technical
Support website 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:
 NetBackup status codes 158
NetBackup status codes

■ 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 on the Veritas Technical
Support website 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:
■ 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 on the Veritas Technical
Support website 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.
 NetBackup status codes 159
NetBackup status codes

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 on the Veritas Technical
Support website 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.
■ 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.
 NetBackup status codes 160
NetBackup status codes

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.

■ 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
 NetBackup status codes 161
NetBackup status codes

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 on the Veritas Technical
Support website 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.
Click here to view technical notes and other information on the Veritas Technical
Support website 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.
 NetBackup status codes 162
NetBackup status codes

Click here to view technical notes and other information on the Veritas Technical
Support website 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.
■ 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 on the Veritas Technical
Support website 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.
 NetBackup status codes 163
NetBackup status codes

■ 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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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.
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 on the Veritas Technical
Support website 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
 NetBackup status codes 164
NetBackup status codes

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 Guide.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 104

Message: invalid file pathname
Explanation: None
Recommended Action: None
Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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:
 NetBackup status codes 165
NetBackup status codes

■ 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 are used 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 on the Veritas Technical
Support website 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.
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 on the Veritas Technical
Support website 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:
 NetBackup status codes 166
NetBackup status codes

■ 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.
■ If the error appears in the web UI while performing a Microsoft SQL Server
restore, review the date provided. The date must be in ISO 8601 format.
Click here to view technical notes and other information on the Veritas Technical
Support website 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.
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 on the Veritas Technical
Support website 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:
 NetBackup status codes 167
NetBackup status codes

■ 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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 112

Message: Undefined error or there are no files specified in the policy backup
selection.
Explanation: This code is displayed for the following reasons:
■ A restore was requested with no files in the file list.
■ The backup selection in the policy is not correctly specified.
■ No VMs to backup with the provided backup selection.
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.
■ Ensure that the correct backup selections are specified in the policy and they
are in the correct format.
The supported backup selection are:
■ For subscription: /Subscription IDif Subscription ID is
1950a258-227b-4e31-a9cf-717495945fc2 then specify the backup selection
as - / 1950a258-227b-4e31-a9cf-717495945fc2
■ For resource group: /Subscription ID/Resource Groupif Subscription
ID is 1950a258-227b-4e31-a9cf-717495945fc2 and Resource Group
name is TestRG, specify the backup selection as - /
1950a258-227b-4e31-a9cf-717495945fc2/TestRG
 NetBackup status codes 168
NetBackup status codes

■ For VM Name: /Subscription ID/Resoutrce Group/VM Nameif

Subscription ID is 1950a258-227b-4e31-a9cf-717495945fc2, Resource
Group name is TestRG, and the VM name is MyVM, specify the backup
selection as - / 1950a258-227b-4e31-a9cf-717495945fc2/TestRG/MyVM
When performing a backup or restore of a Cassandra database, perform the
following as appropriate:
■ Verify that the following setting is commented out from the sudoers list on
Cassandra nodes:
#Defaults:!requiretty

Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

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 on the Veritas Technical
Support website 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 theNetBackup Security and Encryption
Guide.
■ 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/[email protected]/O=vx
 NetBackup status codes 169
NetBackup status codes

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
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 on the Veritas Technical
Support website 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:
 NetBackup status codes 170
NetBackup status codes

■ 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
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/[email protected]/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
 NetBackup status codes 171
NetBackup status codes

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 on the Veritas Technical
Support website 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.
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:

 NetBackup status codes 172
NetBackup status codes

Name: machine3.mycompany.com
Domain: [email protected]
Issued by: /CN=broker/[email protected]/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
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 on the Veritas Technical
Support website 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:
 NetBackup status codes 173
NetBackup status codes

■ 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 on the Veritas Technical
Support website about this status code.

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 174
NetBackup status codes

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.
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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 175
NetBackup status codes

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.
Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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.
 NetBackup status codes 176
NetBackup status codes

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:
■ 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 on the Veritas Technical
Support website 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. The NetBackup
APIs can report this error when an unexpected internal error occurs in processing
the request.
Recommended Action: Do the following, as appropriate:
 NetBackup status codes 177
NetBackup status codes

■ 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.
■ Retry the operation and check the resulting debug logs.
If the policy validation fails, it is due to one of following reasons:
■ A certificate mismatch is present on the client. Remove the Snapshot Manager
CA certificate from the following location and validate the policy again:
install_location/var/global/cloudpoint/certificates

■ The Snapshot Manager is not accessible.

■ If the NetBackup APIs produce this error, examine the unified logs for
nbwebservice on the master server. For details on the web services logs, see
the section on the NetBackup Web Services logging within the NetBackup
Logging Reference Guide.
When a VMware agentless restore is performed, the restore can cause one of the
following issues:
■ Failed to stage recovery tool on path %s in destination VM %s with error code
%d.
Make sure that the staging location path that is used exists and the provided
target VM credentials have root or admin privileges.
■ Failed to get the staging location for destination VM %s with error %d.
Make sure that there is TMP or TEMP environment path available in the target
VM or provided target VM credentials has root or admin privileges.
■ Failed to retrieve the guest VM%s operating system (OS) details with error code
%d.
Make sure that latest VMware Tools are installed and running in the target VM.
Click here to view technical notes and other information on the Veritas Technical
Support website 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
 NetBackup status codes 178
NetBackup status codes

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 on the Veritas Technical
Support website 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
Click here to view technical notes and other information on the Veritas Technical
Support website 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
 NetBackup status codes 179
NetBackup status codes

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.
Click here to view technical notes and other information on the Veritas Technical
Support website 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
 NetBackup status codes 180
NetBackup status codes

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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
■ 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.
 NetBackup status codes 181
NetBackup status codes

Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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:
■ 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:
 NetBackup status codes 182
NetBackup status codes

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 Technical 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
and try the backup again.
Click here to view technical notes and other information on the Veritas Technical
Support website 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 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 on the Veritas Technical
Support website 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.
 NetBackup status codes 183
NetBackup status codes

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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.
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
 NetBackup status codes 184
NetBackup status codes

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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.
Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 185
NetBackup status codes

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 153

Message: server is not the master server
Explanation: This status code is reserved for future use.
Recommended Action: None
Click here to view technical notes and other information on the Veritas Technical
Support website 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.
 NetBackup status codes 186
NetBackup status codes

■ 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 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 on the Veritas Technical
Support website 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.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 156

Message: Snapshot error encountered
Explanation: The following are possible causes of this status code:
■ The cloud provider credentials are not updated.
■ The cloud provider snapshot limit has been exceeded.
■ The Snapshot Manager server cannot be reached.
■ The universal share is on WORM enabled storage and Oracle Copilot backup
with instant access is not supported on this storage option.
 NetBackup status codes 187
NetBackup status codes

■ A new disk is attached to the host and the discovery of required assets is not
completed.
■ Snapshots fail as the shadow copy storage because they are not in the respective
driver.
■ Snapshot can fail with the error asset hierarchy is incomplete which can
be due to ebsnvme-id returning /dev/sda when it should return sda for the boot
disk.
■ Asset is deleted.
■ Asset is in an updating state. (Example: The VM is starting or stopping)
Recommended Action: Perform the following, as appropriate:
■ Ensure that the appropriate plug-in is configured in the web UI with the
appropriate credentials. If the credentials are changed, ensure that they are
updated from the web UI.
■ Ensure that the snapshot limit of the cloud provider is sufficient.
■ Check the ncfnbcs logs.
■ Select a different storage option for Oracle Copilot backup with instant access.
For more information, review the Oracle Copilot with instant access and universal
share chapter in the NetBackup Web UI Oracle Administrator’s Guide.
■ The snapshot is successful when the asset is discovered in next discovery cycle.
Or, the user can manually initiate a discovery when a new asset is added.
■ Restart the shadow copy service.
■ Right click on the C drive and then select Configure Shadow Copies….
■ Select C drive and click Settings.
■ Click schedule and then OK.
■ Select another drive and repeat the steps. If there are no other drives then
click OK.
■ Refer to Configuring VSS to store shadow copies on the originating drive in
the NetBackup Snapshot Manager Install and Upgrade Guide.

■ Unsubscribe the protection plan from the asset.

■ To discover the asset, start a manual discovery or it would be discovered in the
next autodiscovery.
■ If the Snapshot fails with the error asset hierarchy is incomplete, refer to
the following technical article:
 NetBackup status codes 188
NetBackup status codes

■ CloudPoint snapshot is failing with "The host level snapshot of cannot be

performed as asset hierarchy is incomplete" due to ebsnvme-id returning
/dev/sda when it should just return sda for the boot disk.

Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 159

Message: licensed use has been exceeded
 NetBackup status codes 189
NetBackup status codes

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 on the Veritas Technical
Support website 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.
■ If using Snapshot Manager: The authentication with the Snapshot Manager has
failed.
■ If configuring Snapshot Manager, the authentication with the Snapshot Manager
has failed.
■ If configuring a storage provider, the validation of storage credentials has failed.
Recommended Action: Do the following, as appropriate:
 NetBackup status codes 190
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 review the debug logs.
The following actions relate to Snapshot Manager:
■ Ensure that the Snapshot Manager credentials are correct.
■ Verify that the credentials that were entered while registering are valid.
■ If the credentials and the Snapshot Manager port number are updated, ensure
that they are updated in NetBackup.
■ Ensure that the Snapshot Manager credentials are correct.
■ Verify that the credentials that were entered while registering Snapshot Manager
are valid.
■ Verify that the credentials that were entered while configuring a storage provider
are valid.
■ If the credentials and the Snapshot Manager port number are updated, ensure
that they are updated in NetBackup.
Click here to view technical notes and other information on the Veritas Technical
Support website 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.
Recommended Action: Obtain a licensed copy of NetBackup. For information on
licensing, contact your NetBackup sales or partner representative.
Click here to view technical notes and other information on the Veritas Technical
Support website 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.
 NetBackup status codes 191
NetBackup status codes

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 on the Veritas Technical
Support website 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.
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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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.
 NetBackup status codes 192
NetBackup status codes

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 on the Veritas Technical
Support website 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
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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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.)
 NetBackup status codes 193
NetBackup status codes

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 on the Veritas Technical
Support website 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.
Click here to view technical notes and other information on the Veritas Technical
Support website 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 Guide.
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
 NetBackup status codes 194
NetBackup status codes

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.
■ 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.
■ 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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 195
NetBackup status codes

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 on the Veritas Technical
Support website 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
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 onfigured 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.
Click here to view technical notes and other information on the Veritas Technical
Support website 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.
 NetBackup status codes 196
NetBackup status codes

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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 174

Message: media manager - system error occurred
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
 NetBackup status codes 197
NetBackup status codes

■ 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.

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 on the Veritas Technical
Support website 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.
 NetBackup status codes 198
NetBackup status codes

Click here to view technical notes and other information on the Veritas Technical
Support website 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
■ 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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 199
NetBackup status codes

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.
Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 200
NetBackup status codes

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 on the Veritas Technical
Support website 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.
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 on the Veritas Technical
Support website 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.

 NetBackup status codes 201
NetBackup status codes

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 Veritas Technical Support.
Click here to view technical notes and other information on the Veritas Technical
Support website 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:
■ 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 on the Veritas Technical
Support website 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:
 NetBackup status codes 202
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 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.
■ 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 on the Veritas Technical
Support website 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 Veritas 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.
 NetBackup status codes 203
NetBackup status codes

■ Retry the operation.

■ Check the resulting debug logs for the parameters that were passed to tar
and contact Veritas Technical Support.
Click here to view technical notes and other information on the Veritas Technical
Support website 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.
■ 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 on the Veritas Technical
Support website 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.
 NetBackup status codes 204
NetBackup status codes

Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 191

Message: no images were successfully processed
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.
 NetBackup status codes 205
NetBackup status codes

■ 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.
■ 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.
 NetBackup status codes 206
NetBackup status codes

■ Ensure that the Logical Storage Unit (LSU) name or the Domain Volume name
has less than 50 ASCII characters, including a hyphen (-) and an underscore
(_), and that the name does not have a blank space.
Click here to view technical notes and other information on the Veritas Technical
Support website 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
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 on the Veritas Technical
Support website 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
 NetBackup status codes 207
NetBackup status codes

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 on the Veritas Technical
Support website 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.
See "Using the Host Properties window to access configuration settings" in the
NetBackup Troubleshooting Guide.
Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 208
NetBackup status codes

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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 197

Message: the specified schedule does not exist in the specified policy
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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 198

Message: no active policies contain schedules of the requested type for this client
 NetBackup status codes 209
NetBackup status codes

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 on the Veritas Technical
Support website about this status code.

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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 200

Message: The scheduler found that no backups are due. Or, the target hosts do
not need to be upgraded.
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:
 NetBackup status codes 210
NetBackup status codes

■ 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:
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 on the Veritas Technical
Support website 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.
 NetBackup status codes 211
NetBackup status codes

■ 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.
■ 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 on the Veritas Technical
Support website 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.
 NetBackup status codes 212
NetBackup status codes

■ 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:
■ 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 on the Veritas Technical
Support website 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:
 NetBackup status codes 213
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 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.
Click here to view technical notes and other information on the Veritas Technical
Support website 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
 NetBackup status codes 214
NetBackup status codes

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

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.
 NetBackup status codes 215
NetBackup status codes

■ 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 on the Veritas Technical
Support website 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:
■ 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
 NetBackup status codes 216
NetBackup status codes

■ 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 on the Veritas Technical
Support website about this status code.

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.
 NetBackup status codes 217
NetBackup status codes

■ If the error occurred during a restore operation, check the bprd debug logs.

Click here to view technical notes and other information on the Veritas Technical
Support website 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, 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.
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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 218
NetBackup status codes

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 on the Veritas Technical
Support website about this status code.

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 on the Veritas Technical
Support website 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.
 NetBackup status codes 219
NetBackup status codes

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
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 on the Veritas Technical
Support website 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:
 NetBackup status codes 220
NetBackup status codes

■ 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.
■ 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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 216

Message: failed reading retention database information
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 on the Veritas Technical
Support website 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:
 NetBackup status codes 221
NetBackup status codes

■ 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 on the Veritas Technical
Support website 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.
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 on the Veritas Technical
Support website 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.
 NetBackup status codes 222
NetBackup status codes

■ 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.
■ 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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 220

Message: database system error
 NetBackup status codes 223
NetBackup status codes

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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 221

Message: continue
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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 224
NetBackup status codes

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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 224

Message: there was a conflicting specification
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. 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 on the Veritas Technical
Support website 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.
 NetBackup status codes 225
NetBackup status codes

Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 227

Message: no entity was found
Explanation: The asset configured for protection is not found in the NetBackup
database.
Recommended Action: Do the following, as appropriate:
■ Ensure that the appropriate plug-in is configured from the web UI.
■ Ensure that the discovery of the asset is complete and the appropriate asset is
visible in the web UI.
Click here to view technical notes and other information on the Veritas Technical
Support website 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.
 NetBackup status codes 226
NetBackup status codes

■ 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 on the Veritas Technical
Support website 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 Veritas Technical Support.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 232

Message: a protocol error has occurred
 NetBackup status codes 227
NetBackup status codes

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 Veritas Technical Support.
Click here to view technical notes and other information on the Veritas Technical
Support website 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.
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 Veritas Technical Support.
Click here to view technical notes and other information on the Veritas Technical
Support website 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 of the error information and contact Veritas
Technical Support.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 235

Message: inadequate buffer space
 NetBackup status codes 228
NetBackup status codes

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 Veritas Technical
Support.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

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 on the Veritas Technical
Support website 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.
 NetBackup status codes 229
NetBackup status codes

Click here to view technical notes and other information on the Veritas Technical
Support website 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 Veritas Technical Support.
Click here to view technical notes and other information on the Veritas Technical
Support website 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.
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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 241

Message: the specified schedule is the wrong type for this request
 NetBackup status codes 230
NetBackup status codes

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 231
NetBackup status codes

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

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 on the Veritas Technical
Support website 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.
 NetBackup status codes 232
NetBackup status codes

■ On other clients, bpcd.

Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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.
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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 233
NetBackup status codes

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 on the Veritas Technical
Support website 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 Veritas
Technical Support.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

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 on the Veritas Technical
Support website 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.
 NetBackup status codes 234
NetBackup status codes

Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 235
NetBackup status codes

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 on the Veritas Technical
Support website 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
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 on the Veritas Technical
Support website 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
 NetBackup status codes 236
NetBackup status codes

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 267

Message: cannot find the local host name
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 on the Veritas Technical
Support website 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.
 NetBackup status codes 237
NetBackup status codes

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 271

Message: vault XML version mismatch
Explanation: The Vault upgrade process failed.
 NetBackup status codes 238
NetBackup status codes

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 273

Message: invalid job id
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 on the Veritas Technical
Support website 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.
 NetBackup status codes 239
NetBackup status codes

Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 277

Message: unable to print reports
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 on the Veritas Technical
Support website 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.
 NetBackup status codes 240
NetBackup status codes

Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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.
Click here to view technical notes and other information on the Veritas Technical
Support website 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 Veritas Private Branch Exchange service (VRTSpbx) or NetBackup Request
Manager (bprd) is down.
 NetBackup status codes 241
NetBackup status codes

■ 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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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:
■ 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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 242
NetBackup status codes

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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).
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 on the Veritas Technical
Support website 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:
 NetBackup status codes 243
NetBackup status codes

■ 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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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.
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.
 NetBackup status codes 244
NetBackup status codes

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

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
 NetBackup status codes 245
NetBackup status codes

(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 on the Veritas Technical
Support website 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:
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.
 NetBackup status codes 246
NetBackup status codes

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 on the Veritas Technical
Support website 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.
Click here to view technical notes and other information on the Veritas Technical
Support website 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
 NetBackup status codes 247
NetBackup status codes

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

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.
 NetBackup status codes 248
NetBackup status codes

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 299

Message: there is no available MAP for ejecting
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 on the Veritas Technical
Support website 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
 NetBackup status codes 249
NetBackup status codes

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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 301

Message: vmchange api_eject command failed
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)
 NetBackup status codes 250
NetBackup status codes

When the problem is resolved, rerun the Vault session, vlteject command, or
vltopmenu command.

Click here to view technical notes and other information on the Veritas Technical
Support website 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.

Click here to view technical notes and other information on the Veritas Technical
Support website 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
 NetBackup status codes 251
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 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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 305

Message: multiple profiles exist
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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 306

Message: Vault duplication partially succeeded
Explanation: This error occurs when all of the selected images are not successfully
duplicated.
 NetBackup status codes 252
NetBackup status codes

Recommended Action: Check the Vault logs in the vault directory and the
bpduplicate logs in the admin directory for the cause of the failure. These log
directories are located at /usr/openv/netbackup/logs on UNIX and
installed-dir\NetBackup\logs\ on Windows.

Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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
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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 253
NetBackup status codes

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 on the Veritas Technical
Support website 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
Windows: install_path\NetBackup\logs\vault
To fix the issue may involve making configuration changes.
Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 254
NetBackup status codes

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 on the Veritas Technical
Support website 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.

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 on the Veritas Technical
Support website 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.
 NetBackup status codes 255
NetBackup status codes

Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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.
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 on the Veritas Technical
Support website 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.
 NetBackup status codes 256
NetBackup status codes

Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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
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 on the Veritas Technical
Support website 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:
 NetBackup status codes 257
NetBackup status codes

■ 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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 323

Message: cannot find robot in vault configuration file
 NetBackup status codes 258
NetBackup status codes

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 on the Veritas Technical
Support website 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.

Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 259
NetBackup status codes

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 on the Veritas Technical
Support website 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
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 on the Veritas Technical
Support website 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.
 NetBackup status codes 260
NetBackup status codes

Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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.
Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 261
NetBackup status codes

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 daemon (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 on the Veritas Technical
Support website about this status code.

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 on the Veritas Technical
Support website 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.
 NetBackup status codes 262
NetBackup status codes

Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 263
NetBackup status codes

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 on the Veritas Technical
Support website 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.
Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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
 NetBackup status codes 264
NetBackup status codes

■ 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 on the Veritas Technical
Support website 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.
Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 265
NetBackup status codes

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 266
NetBackup status codes

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 on the Veritas Technical
Support website 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
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 on the Veritas Technical
Support website 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, 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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 267
NetBackup status codes

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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 402

Message: Server Group Already Exists with a different type
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 on the Veritas Technical
Support website 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
 NetBackup status codes 268
NetBackup status codes

■ 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 on the Veritas Technical
Support website 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.
■ 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 on the Veritas Technical
Support website 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.
 NetBackup status codes 269
NetBackup status codes

Click here to view technical notes and other information on the Veritas Technical
Support website 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
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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 270
NetBackup status codes

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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 409

Message: Member already exists in server group
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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 410

Message: A backup host pool with this name already exists.
Explanation: A backup host pool with the same name already exists.
Recommended Action: Use a unique name for the backup host pool.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 411

Message: The backup host pool group state is not active.
Explanation: When you create a backup host pool, the group state must be active.
 NetBackup status codes 271
NetBackup status codes

Recommended Action: While creating a backup host pool, provide -grpstate

ACTIVE as the parameter value.

Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 412

Message: The backup host pool does not exist.
Explanation: The provided backup host pool name does not exist.
Recommended Action: Use the nbsvrgrp -list command to check if the backup
host pool exists.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 413

Message: The host entry in the backup host pool already exists.
Explanation: The host entry in the backup host pool already exists.
Recommended Action: The specified host is already a part of the backup host
pool. No user action is required.
Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 272
NetBackup status codes

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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 503

Message: Invalid user name.
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 on the Veritas Technical
Support website 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:
 NetBackup status codes 273
NetBackup status codes

■ 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 on the Veritas Technical
Support website 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
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 on the Veritas Technical
Support website 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.
 NetBackup status codes 274
NetBackup status codes

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
ConsoleHost 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.
Click here to view technical notes and other information on the Veritas Technical
Support website 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, set the debug logging for media manager to a higher
level.
■ 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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 275
NetBackup status codes

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.
Set the debug logging for media manager to a higher level.
Click here to view technical notes and other information on the Veritas Technical
Support website 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:
 NetBackup status codes 276
NetBackup status codes

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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 510

Message: File already exists: file_name
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 on the Veritas Technical
Support website 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:
 NetBackup status codes 277
NetBackup status codes

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 on the Veritas Technical
Support website 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.
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 on the Veritas Technical
Support website 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:
 NetBackup status codes 278
NetBackup status codes

■ 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 on the Veritas Technical
Support website 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

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 on the Veritas Technical
Support website 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.
 NetBackup status codes 279
NetBackup status codes

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 on the Veritas Technical
Support website about this status code.

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 on the Veritas Technical
Support website 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.
 NetBackup status codes 280
NetBackup status codes

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 on the Veritas Technical
Support website about this status code.

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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.
 NetBackup status codes 281
NetBackup status codes

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 on the Veritas Technical
Support website 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.
Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 282
NetBackup status codes

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:
■ 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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 283
NetBackup status codes

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.
Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 284
NetBackup status codes

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.
■ 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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 555

Message: Unable to logon.
Explanation: A user made an attempt to sign in with a smart card or with SAML
single single-on authentication. However, NBAC is enabled on the host and is not
supported for these authentication types.
Recommended Action: Use another authentication mechanism. For example,
authenticate with either a user name and password or with the Windows Active
Directory logon credentials.
Click here to view technical notes and other information on the Veritas Technical
Support website 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.
 NetBackup status codes 285
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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 602

Message: cannot set non-blocking mode on the listen socket
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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 286
NetBackup status codes

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 on the Veritas Technical
Support website 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.
Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 287
NetBackup status codes

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 on the Veritas Technical
Support website 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
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 on the Veritas Technical
Support website 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.
 NetBackup status codes 288
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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

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.
 NetBackup status codes 289
NetBackup status codes

Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information on the Veritas Technical
Support website 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.
 NetBackup status codes 290
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 on the Veritas Technical
Support website 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
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 on the Veritas Technical
Support website 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.
 NetBackup status codes 291
NetBackup status codes

Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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.
Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 619

Message: internal error 619
 NetBackup status codes 292
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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

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 on the Veritas Technical
Support website 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.
 NetBackup status codes 293
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 on the Veritas Technical
Support website 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.
Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 294
NetBackup status codes

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 on the Veritas Technical
Support website 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.
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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 295
NetBackup status codes

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 on the Veritas Technical
Support website 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.
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 on the Veritas Technical
Support website 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.
 NetBackup status codes 296
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 on the Veritas Technical
Support website 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
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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 297
NetBackup status codes

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 on the Veritas Technical
Support website 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.
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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 298
NetBackup status codes

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.
Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 299
NetBackup status codes

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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 639

Message: specified policy does not exist
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 on the Veritas Technical
Support website 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:
 NetBackup status codes 300
NetBackup status codes

■ 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 on the Veritas Technical
Support website about this status code.

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 on the Veritas Technical
Support website 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.
 NetBackup status codes 301
NetBackup status codes

Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 644

Message: extent directive contained an unknown media ID
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 on the Veritas Technical
Support website 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
 NetBackup status codes 302
NetBackup status codes

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.
Click here to view technical notes and other information on the Veritas Technical
Support website 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.
 NetBackup status codes 303
NetBackup status codes

Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 304
NetBackup status codes

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 on the Veritas Technical
Support website 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.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information on the Veritas Technical
Support website 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.
 NetBackup status codes 305
NetBackup status codes

Click here to view technical notes and other information on the Veritas Technical
Support website 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 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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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.
 NetBackup status codes 306
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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

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 on the Veritas Technical
Support website 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
 NetBackup status codes 307
NetBackup status codes

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 on the Veritas Technical
Support website 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
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 on the Veritas Technical
Support website 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.
 NetBackup status codes 308
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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 309
NetBackup status codes

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 on the Veritas Technical
Support website 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.
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 on the Veritas Technical
Support website 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.
 NetBackup status codes 310
NetBackup status codes

Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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.
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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 311
NetBackup status codes

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 on the Veritas Technical
Support website 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.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup
Logging Reference Guide.
Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 312
NetBackup status codes

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 on the Veritas Technical
Support website about this status code.
https://www.veritas.com/content/support/en_US/dpp.NetBackup?q="Status Code
800"

NetBackup status code: 801

Message: JM internal error
Explanation: The nbjm process encountered an internal error.
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).
 NetBackup status codes 313
NetBackup status codes

■ bpdbjobs output: run bpdbjobs to obtain the state and status of all jobs.

Click here to view technical notes and other information on the Veritas Technical
Support website 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
■ 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 on the Veritas Technical
Support website 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.
 NetBackup status codes 314
NetBackup status codes

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 on the Veritas Technical
Support website about this status code.

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
 NetBackup status codes 315
NetBackup status codes

■ 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 on the Veritas Technical
Support website 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.

Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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.
 NetBackup status codes 316
NetBackup status codes

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

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 on the Veritas Technical
Support website 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.
 NetBackup status codes 317
NetBackup status codes

Recommended Action: Contact Veritas Technical Support and provide relevant

supporting materials.
Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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).

■ 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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 318
NetBackup status codes

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 on the Veritas Technical
Support website about this status code.

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 on the Veritas Technical
Support website 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.
 NetBackup status codes 319
NetBackup status codes

Click here to view technical notes and other information on the Veritas Technical
Support website 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.
■ 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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 859

Message: Exceeded maximum number of retries, unable to deactivate deployment
host.
Explanation: NetBackup Job Manager service waited 3 minutes for the media
server to be deactivated and the deployment job was aborted.
Recommended Action: Retry the deployment job on the target host.
Click here to view technical notes and other information in the Veritas Technical
Support website about this status code.
 NetBackup status codes 320
NetBackup status codes

NetBackup status code: 860

Message: Exceeded maximum number of retries, unable to activate deployment
host.
Explanation: NetBackup Job Manager service waited 3 minutes for the media
server to be activated and the deployment job aborted.
Recommended Action: Wait until the host is active, or run vmoprcmd
-activate_host -h hostname to activate the host.

Click here to view technical notes and other information in the Veritas Technical
Support website about this status code.

NetBackup status code: 861

Message: The entry for exclude_file_list parameter in the job param file is not
present.
Explanation: NetBackup is unable to find exclude_file_list entry in job param
file.
Recommended Action: Retry the backup job again. If the issue persists, update
the backup policy to reconfigure the exclude selections.
Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 321
NetBackup status codes

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 on the Veritas Technical
Support website about this status code.

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 on the Veritas Technical
Support website 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:
 NetBackup status codes 322
NetBackup status codes

■ 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 on the Veritas Technical
Support website 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
(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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 906

Message: RB operator denied mount request
 NetBackup status codes 323
NetBackup status codes

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 on the Veritas Technical
Support website 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.
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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 324
NetBackup status codes

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 on the Veritas Technical
Support website about this status code.

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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 915

Message: RB disk volume mount must retry
 NetBackup status codes 325
NetBackup status codes

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 on the Veritas Technical
Support website 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.
Recommended Action: Distribute the scheduled job start times over a wider period
of time.
Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 918

Message: RB does not have a multiplexing group that uses this media ID or drive
name
 NetBackup status codes 326
NetBackup status codes

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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 925

Message: Backup host pool name is not provided in the Resource Broker request.
Explanation: The backup host pool is not configured or not found.
Recommended Action: Ensure that the backup host pool is configured in the
backup policy.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 927

Message: No backup host from configured backup host pool is available for job
execution.
Explanation: Either all the backup hosts are in use and have reached the limit for
job execution or all the backup hosts are down.
Recommended Action: Ensure all NetBackup services are up and running on
backup host. If the services are already running, then the backup host is running
at full capacity for dynamic streaming. You must wait for the active jobs to complete.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 928

Message: The NetBackup version of the backup hosts and the configured backup
host pool must be of the same version.
Explanation: All the backup hosts in a backup host pool must be the same
NetBackup version.
Recommended Action: Ensure that all backup hosts in a backup host pool are
the same NetBackup version.
 NetBackup status codes 327
NetBackup status codes

Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 328
NetBackup status codes

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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 1004

Message: Failed to get the Snapshot Manager name.
Explanation: Snapshot or backup job cannot find the associated Snapshot Manager
to start a job. This issue may happen if the required NetBackup service is not
reachable.
Recommended Action: Check if the NetBackup Web Management Console (nbwmc)
service is up and running. Then stop and restart the service if necessary.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1005

Message: Missing one or more of the required policy values for
unix_eca_cert_path, unix_eca_trust_store_path, or
unix_eca_private_key_path.

Explanation: Configured policy fields unix_eca_crl_path,

unix_eca_crl_check_level, or unix_eca_key_passphrasefile are present but
one of the required fields have been omitted (Required fields: unix_eca_cert_path,
unix_eca_trust_store_path, or unix_eca_private_key_path).

Recommended Action: Reset policy fields unix_eca_crl_path,

unix_eca_crl_check_level, and unix_eca_key_passphrasefile if you only have
windows clients. Otherwise, set required fields unix_eca_cert_path,
unix_eca_trust_store_path, and unix_eca_private_key_path.

Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.
 NetBackup status codes 329
NetBackup status codes

NetBackup status code: 1006

Message: Missing one or more of the required policy values for win_eca_cert_path,
win_eca_trust_store_path, or win_eca_private_key_path.

Explanation: Configured policy fields win_eca_crl_path,

win_eca_crl_check_level, or win_eca_key_passphrasefile are present but one
of the required fields have been omitted (Required fields: win_eca_cert_path,
win_eca_trust_store_path, win_eca_private_key_path).

Recommended Action: Reset policy fields win_eca_crl_path,

win_eca_crl_check_level, and win_eca_key_passphrasefile if you only have
UNIX clients. Otherwise, set required fields win_eca_cert_path,
win_eca_trust_store_path, and win_eca_private_key_path.

Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1007

Message: Cannot specify policy values for win_eca_cert_path,
win_eca_trust_store_path, win_eca_private_key_path, and
win_eca_key_passphrasefile when the policy value win_eca_cert_store is
specified.
Explanation: The policy field win_eca_cert_store requires the policy field
win_eca_crl_check_level to be specified. The win_eca_cert_path,
win_eca_trust_store_path, win_eca_private_key_path, and
win_eca_key_passphrasefile fields do not need to be set.

Recommended Action: Set the required policy field win_eca_crl_check_level

and reset policy fields win_eca_cert_path, win_eca_trust_store_path,
win_eca_private_key_path, and win_eca_key_passphrasefile or reset the
policy field win_eca_cert_store.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1008

Message: Missing required field unix_eca_crl_path.
Explanation: The policy field unix_eca_crl_path is required only when
unix_eca_crl_check_level is use_path.

Recommended Action: Set the policy field unix_eca_crl_path or change

unix_eca_crl_check_level to either use_cdp or disabled.
 NetBackup status codes 330
NetBackup status codes

Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1009

Message: Missing required field win_eca_crl_path.
Explanation: The policy field win_eca_crl_path is required only when
win_eca_crl_check_level is use_path.

Recommended Action: Set the policy field win_eca_crl_path or change

win_eca_crl_check_level to either use_cdp or disabled.

Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1010

Message: Field unix_eca_crl_check_level must be use_path if field
unix_eca_crl_path is specified.

Explanation: The policy field unix_eca_crl_check_level must be set to use_path

when unix_eca_crl_path is specified.
Recommended Action: Set the policy field unix_eca_crl_check_level to
use_path or reset the policy field unix_eca_crl_path.

Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1011

Message: Field win_eca_crl_check_level must be use_path if field
win_eca_crl_path is specified.

Explanation: The policy field win_eca_crl_check_level must be set to use_path

when win_eca_crl_path is specified.
Recommended Action: Set the policy field win_eca_crl_check_level to use_path
or reset the policy field win_eca_crl_path.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1012

Message: Missing required field win_eca_crl_check_level.
 NetBackup status codes 331
NetBackup status codes

Explanation: When the policy field win_eca_cert_store is specified it also requires

win_eca_crl_check_level to be specified.

Recommended Action: Set the policy field win_eca_crl_check_level and also

set the policy field win_eca_crl_path if win_eca_crl_check_level is use_path.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1013

Message: Invalid deployment_cert_source value, file must be specified.
Explanation: Cannot specify a cert_store value for deployment_cert_source if
win_eca_cert_store is not specified.

Recommended Action: Change deployment_cert_source value from cert_store

to file.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1014

Message: Invalid deployment_cert_source value, cert_store must be specified.
Explanation: Cannot specify the file value for the deployment_cert_source
when win_eca_cert_store is specified.
Recommended Action: Change the deployment_cert_source value from file
to cert_store.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1019

Message: Failed to get Snapshot Manager capability.
Explanation: NetBackup is unable to retrieve the Snapshot Manager capability
parameters from the EMM database.
Recommended Action: Perform the following, as appropriate:
■ Ensure that the NetBackup service - nbemm is up and running.
■ Perform a refresh configuration operation of the Snapshot Manager using the
tpconfig command to reset capability parameters in EMM.
 NetBackup status codes 332
NetBackup status codes

Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1020

Message: Failed to get the last backup snapshot ID.
Explanation: For vendor change tracking (VCT) based backups, NetBackup is
unable to find the snapshot identifier for last reference snapshot image.
Recommended Action: Ensure that the last reference snapshot image exists
before you retry a VCT-based incremental backup.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1021

Message: The maintenance version that is specified is not the same base version
as installed version.
Explanation: The package name that is specified using either nbinstallcmd
-package option or bpplinfo -deployment_package option must match the first
three version numbers of the installed package.
For example:
■ If package the name is maint.nbclient_8.2.2.2 the installed package version
must start with 8.2.2.
Recommended Action: Change package name to match the base version.
For example:
■ If package the name is maint.nbclient_8.2.3.2 then change to
maint.nbclient.8.2.2.2 which matches the base release version 8.2.2 of
the installed package maint.nbclient.8.2.2.1.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1022

Message: The maintenance version that is specified cannot be older than installed
version, or no update required.
Explanation: The package name that is specified using either nbinstallcmd
-package option or bpplinfo -deployment_package option must be the same
or newer than the installed package.
 NetBackup status codes 333
NetBackup status codes

For example:
■ If the installed package name is maint.nbclient_8.2.2.2 the version that is
specified in the new maint.nbclient package name must be 8.2.2.[2-9].
The update may not be required because of the following:
■ The specified maintenance release has no updates applicable to the target host.
■ The maintenance release is already installed on the target host.
Recommended Action: Change the maint.client or maint.nbserver package
names version to be the same or newer than the installed package version. For
example:
For example:
■ If installed package is maint.nbclient_8.3.0.5 then any new maint.nbclient
package names version must be 8.3.0.[5-9].
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1023

Message: Invalid package name specified.
Explanation: The package name that is specified using either nbinstallcmd
-package option or bpplinfo -deployment_package option is invalid.

Recommended Action: Change package name to match the format required

<name>_<version>. Where the <version> Is a valid a NetBackup release like
8.2.1.

The format of the package name must be one of the following:

■ nbclient_<version>

■ nbserver_<version>

■ nbeeb_<version>

■ nbeeb.client_<version>

■ nbeeb.server_<version>

■ maint.nbclient_<version>

■ maint.nbserver_<version>

Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.
 NetBackup status codes 334
NetBackup status codes

NetBackup status code: 1024

Message: The BigData policy cannot be used to protect Nutanix AHV VMs using
a backup host with NetBackup version 8.3 or later.
Explanation: NetBackup does not support the BigData policy to protect Nutanix
AHV virtual machines starting in NetBackup 9.0. The BigData policy needs to be
converted to a Hypervisor policy.
Recommended Action: Migrate the policy by editing the existing BigData policy
and selecting the policy type as Hypervisor. Refer to the Migrating BigData policy
to Hypervisor policy topic in the NetBackup for Nutanix Acropolis Hypervisor (AHV)
Administrator’s Guide.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1057

Message: A data corruption has been detected.
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 Veritas Technical Support.
Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 1227

Message: Key group does not have an active key.
Explanation: Did not retrieve an active key record detail in a key group from the
Key Management Service (KMS).
 NetBackup status codes 335
NetBackup status codes

Recommended Action: See the errorDetails in the JSON output for additional
details.
Check whether required keys are present in Key Management Service (KMS) by
running the following commands:
■ Run the following to verify that the key record is in an active state: nbkmscmd
-listkeys -name <kms name> -keyGroupName <key_group_name>

■ Run the following to create a new key if key is not present in a group: nbkmscmd
-createKey -name <configuration name> -KeyName <name of the key
to be created> -keyGroupName < key group name>

■ Run the following to activate the key if any of the key records are not in an active
state in a group: nbkmsutil -modifykey -keyname <key_name> -kgname
<key_group_name> -activate

If the issue persists, visit the Veritas Technical Support website. The Veritas
Technical Support website offers additional information to help you troubleshoot
this issue.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1229

Message: Key group was not found.
Explanation: Did not retrieve the key group details from the Key Management
Service (KMS).
Recommended Action: See the errorDetails in the JSON output for additional
details.
■ Run the following to verify whether the group is present in the KMS server:
nbkmscmd -listkeys -name <kms name> -keyGroupName <key_group_name>

■ Run the following to create a key group in the KMS server: nbkmscmd
-createKey -name <configuration name> -KeyName <name of the key
to be created> -keyGroupName <name of the key group associated
with the key>

If the issue persists, visit the Veritas Technical Support website. The Veritas
Technical Support website offers additional information to help you troubleshoot
this issue.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.
 NetBackup status codes 336
NetBackup status codes

NetBackup status code: 1260

Message: Key record was not found.
Explanation: Did not retrieve the key record details from the Key Management
Service (KMS). This issue may be because an active key record is not found in a
group.
Recommended Action: See the errorDetails in the JSON output for additional
details.

Check whether required keys are present in Key Management Service (KMS) by
running the following commands:
1. Get configured KMS information by running: nbkmscmd -listKMSConfig -name
<kms_configuration_name>

■ If the Enabled for Backup option is set to false for the existing KMS server
then set it to true state by running: nbkmscmd -updateKMSConfig
■ If the KMS configuration is not present for the KMS server then add a new
KMS configuration with the Enabled for Backup option by running:
nbkmscmd -configureKMS

Verify that the desired key groups are present in the KMS server where Enabled
For Backup is set to true.

2. Get list of keys by running: nbkmscmd -listKeys -name

<kms_configuration_name>

3. If the key is not present then run nbkmscmd -createKey -name

<configuration name> -KeyName <name of the key to be created>
-keyGroupName <name of the key group associated with the key> to
add the key record to the KMS server.
If the issue persists, visit the Veritas Technical Support website. The Veritas
Technical Support website offers additional information to help you troubleshoot
this issue.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1288

Message: Failed to retrieve the Key Management Service (KMS) details.
Explanation: Failed to retrieve the details of the configured Key Management
Service (KMS).
 NetBackup status codes 337
NetBackup status codes

Recommended Action: See the errorDetails in JSON output for additional

details.
This error can occur due to NetBackup Key Management Service (KMS) is not
running or the NetBackup Key Management Service (KMS) is not configured.

Verify if the NetBackup Key Management Service (KMS) is running and configured
by running the following:
1. Run the nbkmscmd -listKMSConfig -name <kms_configuration_name>
command to verify if the nbkms service is configured.
2. If the nbkms service is not configured then run the nbkmscmd -configureKMS
to configure the NetBackup KMS service.
3. Run the nbkmscmd -discoverNBkms command if the nbkmscmd -configureKMS
command recommends running this command.
4. Verify that the nbkms service is configured by running the nbkmscmd
-listKMSConfig -name <kms_configuration_name> command.

5. Verify that the nbkms service is up and in a running state by executing the
nbkmscmd -validateKMSConfig -name <kms_ configuration_name>
command.
If the issue persists, visit the Veritas Technical Support website. The Veritas
Technical Support website offers additional information to help you troubleshoot
this issue.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1289

Message: Failed to create the Key Management Service (KMS) configuration.
Explanation: Failed to create the Key Management Service (KMS) with the given
configuration.
Recommended Action: See the errorDetails in JSON output for additional
details. Retry the operation and if the issue persists, visit the Veritas Technical
Support website. The Veritas Technical Support website offers additional information
to help you troubleshoot this issue.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.
 NetBackup status codes 338
NetBackup status codes

NetBackup status code: 1290

Message: Failed to update the KMS configuration.
Explanation: The following items are possible reasons that the KMS configuration
update did not succeed:
■ None of the attributes are provided.
■ The NetBackup KMS configuration is to be updated, however KMIP attributes
are provided. The KMIP attributes are not valid for NetBackup KMS configuration
update.
Recommended Action: When you update the KMS configuration, ensure the
following:
■ Provide at least one attribute.
■ To update the NetBackup KMS configuration, ensure that the KMIP attributes
are not provided.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1291

Message: The NetBackup Key Management Service (NBKMS) is already configured,
but not registered.
Explanation: The NetBackup KMS is not automatically registered during upgrade.
Recommended Action: Run the nbkmscmd command to discover NetBackup KMS.
For more information on the nbkmscmd command, see the NetBackup Commands
Reference Guide.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1292

Message: The NetBackup Key Management Service (NBKMS) cannot be registered
because it is not configured.
Explanation: An attempt was made to register the NetBackup KMS, whereas the
NetBackup KMS is not yet configured. Make sure NetBackup KMS is configured
and the service is running before registering.
Recommended Action: Run the nbkmscmd command to configure NetBackup
KMS. This step automatically registers NetBackup KMS. For more information on
the nbkmscmd command, see the NetBackup Commands Reference Guide.
 NetBackup status codes 339
NetBackup status codes

Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1293

Message: The JSON string cannot be processed.
Explanation: There is a parsing issue in the output received from External Key
Management Service (EKMS).
Recommended Action: See the errorDetails in the response JSON output for
additional details. A retry of the same operation should resolve the issue. For more
details, review the nbkmiputil and nbwebservice logs. If the issue persists, visit
the Veritas Technical Support website. The Veritas Technical Support website offers
additional information to help you troubleshoot this issue.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1294

Message: Time-out has occurred sending the JSON string to the NetBackup key
management utility.
Explanation: The time-out occurs at the time of retrieving the key record details
from External Key Management Service (EKMS). The time-out may be because of
the EKMS server name or a port is not configured in KMS configuration.
Recommended Action: See the errorDetails in the JSON output for additional
details.
Verify the KMS server name and the port number in the KMS configuration using
the nbkmscmd -listKMSConfig command. If everything seems to proper in the
KMS configuration, run the nbkmscmd -validateKMSConfig -name <KMS
Configuration Name> command.

A retry of the same operation can resolve the issue. For more details, review the
nbkmiputil and nbwebservice logs. If the issue persists, visit the Veritas Technical
Support website. The Veritas Technical Support website offers additional information
to help you troubleshoot this issue.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.
 NetBackup status codes 340
NetBackup status codes

NetBackup status code: 1295

Message: The JSON string cannot be read from the NetBackup key management
utility as the utility is executed.
Explanation: There is a parsing issue in the output that was received from External
Key Management Service (EKMS).
Recommended Action: See the errorDetails in JSON output for additional
details. A retry of the same operation can resolve the issue. For more details, review
the nbkmiputil and nbwebservice logs. If the issue persists, visit the Veritas
Technical Support website. The Veritas Technical Support website offers additional
information to help you troubleshoot this issue.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1296

Message: The KMS configuration cannot be validated.
Explanation: The NetBackup KMS should be configured and the service should
be running before it can be validated.
Recommended Action: Ensure that the nbkms service is up and running.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1297

Message: The KMS key cannot be created.
Explanation: The required attributes to create KMS key are missing or incorrect.
Recommended Action: Ensure that the required KMS key attributes are provided.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1298

Message: Cannot communicate with one or more key management servers.
Explanation: One or more KMS servers are configured in the given NetBackup
domain. A key is queried to nbwmc as a part of a backup or a restore job. While a
key from a KMS server is retrieved, some communication errors are seen. Some
of the errors can be KMS not reachable or the credentials that are used to connect
to the KMS server are not valid.
 NetBackup status codes 341
NetBackup status codes

Recommended Action: Run the nbkmscmd -validateKMSConfig -name <KMS

Configuration Name> command to retrieve and review the error details. You can
use the nbkmscmd -listKMSConfig command to see the configured KMS server
and the <KMS Configuration Name>.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1299

Message: The KMS configuration pre-check failed.
Explanation: This error occurs if any of the following conditions is not met:
■ You should specify either credId or pkiAttributes. Do not specify both at the
same time.
■ One of the following fields is mandatory: credId or pkiAttributes.
■ The kmsServerAttributes field is mandatory and it cannot be blank.
■ The certificate is mandatory and it cannot be blank.
■ The CA Certificate is mandatory and it cannot be blank.
■ The private key is mandatory and it cannot be blank.
■ The operation is not supported for the following KMS type: NBKMS.
Recommended Action: Verify the following as needed:
■ You need to specify either credId or pkiAttributes. Do not specify both at
the same time.
■ Verify that you have one of the following mandatory fields: credId or
pkiAttributes.

■ Verify that the mandatory field kmsServerAttributes is not blank.

■ Review the certificate. The certificate is mandatory and it cannot be blank.
■ Review the CA Certificate. The CA Certificate is mandatory and it cannot be
blank.
■ Review the private key. The private key is mandatory and it cannot be blank.
■ Verify that NBKMS is not used. The operation is not supported for that KMS type.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.
 NetBackup status codes 342
NetBackup status codes

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 343
NetBackup status codes

NetBackup status code: 1407

Message: Invalid hold state
Explanation: The hold state is invalid.
Recommended Action: Retry the operation and if the issue persists, visit
support.veritas.com. The Veritas Technical Support website site offers additional
information to help you troubleshoot this issue.
Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 1409

Message: Unable to connect to database
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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 344
NetBackup status codes

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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.
Recommended Action: Check the -holdname and -holdid options. You can use
nbholdutil -list command.

Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 1415

Message: Duplicate image found
 NetBackup status codes 345
NetBackup status codes

Explanation: Reserved for future use.

Recommended Action: Not available
Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

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 on the Veritas Technical
Support website 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
 NetBackup status codes 346
NetBackup status codes

Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 1422

Message: Cannot deassign media on hold
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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 347
NetBackup status codes

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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.
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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 1501

Message: Source operation cannot be used where specified
 NetBackup status codes 348
NetBackup status codes

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 a 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.
■ For cloud snapshot replication, the source must be snapshot operation.
Click here to view technical notes and other information on the Veritas Technical
Support website 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.
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.
■ For cloud snapshot replication only, fixed retention type is supported.
 NetBackup status codes 349
NetBackup status codes

Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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.
■ 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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 350
NetBackup status codes

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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.
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.
 NetBackup status codes 351
NetBackup status codes

Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 1510

Message: storage lifecycle policy cannot have more than one snapshot operation
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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 1511

Message: storage lifecycle policy must have at least one fixed retention or snapshot
rotation operation
 NetBackup status codes 352
NetBackup status codes

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

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.
 NetBackup status codes 353
NetBackup status codes

■ 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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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.
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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 1517

Message: Invalid retention level
 NetBackup status codes 354
NetBackup status codes

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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.
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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 1521

Message: Database not available
 NetBackup status codes 355
NetBackup status codes

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 1524

Message: Duplicate image record
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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 356
NetBackup status codes

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 1527

Message: storage lifecycle policy can have only one of backup, import, and snapshot
operations
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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 357
NetBackup status codes

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 on the Veritas Technical
Support website 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:
■ 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.
 NetBackup status codes 358
NetBackup status codes

■ 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 on the Veritas Technical
Support website 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.
Click here to view technical notes and other information on the Veritas Technical
Support website 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.
 NetBackup status codes 359
NetBackup status codes

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

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.
 NetBackup status codes 360
NetBackup status codes

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 1535

Message: Import failed because the imported image backup ID conflicts with an
existing image
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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 361
NetBackup status codes

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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 1537

Message: Backup policy and storage lifecycle policy have conflicting configurations
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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 362
NetBackup status codes

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 363
NetBackup status codes

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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 1542

Message: An existing snapshot is no longer valid or 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 on the Veritas Technical
Support website about this status code.

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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 364
NetBackup status codes

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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.
Click here to view technical notes and other information on the Veritas Technical
Support website 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
 NetBackup status codes 365
NetBackup status codes

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.
■ For cloud snapshot replication only, fixed retention type is supported.
Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

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.
 NetBackup status codes 366
NetBackup status codes

■ 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 on the Veritas Technical
Support website 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.
■ Choose a different SLP to use with the backup policy.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1554

Message: Storage unit snapshot capability is not compatible with operation
characteristics
 NetBackup status codes 367
NetBackup status codes

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

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
 NetBackup status codes 368
NetBackup status codes

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

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:
 NetBackup status codes 369
NetBackup status codes

■ 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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 370
NetBackup status codes

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1568

Message: Only one Index From Snapshot operation is allowed per storage lifecycle
policy
 NetBackup status codes 371
NetBackup status codes

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1571

Message: Data mover type specified in policy does not support Index from
Snapshot
 NetBackup status codes 372
NetBackup status codes

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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.
■ 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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 373
NetBackup status codes

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1577

Message: Storage unit in the SLP does not match the accelerator attribute in policy
 NetBackup status codes 374
NetBackup status codes

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 1580

Message: VMware policy with PFI enabled requires an SLP
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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 375
NetBackup status codes

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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.
Recommended Action: Enable automatic discovery of virtual machines.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1584

Message: VMware policy with 'Persistent Frozen Image' enabled requires schedule
type of Full Backup
 NetBackup status codes 376
NetBackup status codes

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

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.
 NetBackup status codes 377
NetBackup status codes

Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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.
Click here to view technical notes and other information on the Veritas Technical
Support website 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.
 NetBackup status codes 378
NetBackup status codes

Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

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.
 NetBackup status codes 379
NetBackup status codes

Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 1598

Message: Oracle policy with PFI and FI enabled requires an SLP
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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 1599

Message: Application schedule storage selection cannot be a snapshot SLP
 NetBackup status codes 380
NetBackup status codes

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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.
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 on the Veritas Technical
Support website 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.
 NetBackup status codes 381
NetBackup status codes

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 1608

Message: The region asset that is used as a cloud snapshot replication destination
does not exist. Enter a valid region asset.
Explanation: The region asset that is specified does not exist in the NetBackup
asset database. This error is also encountered, if the cloud provider plug-in is not
configured with the specified region.
Recommended Action: Verify the region asset ID and perform the operation again.
 NetBackup status codes 382
NetBackup status codes

Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1609

Message: The region asset is already used as a cloud snapshot replication
destination. Provide a different region asset.
Explanation: In a single schedule, a region asset cannot be used for multiple cloud
snapshot replication destinations.
Recommended Action: Use multiple schedules or use a different region asset.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1610

Message: The provided region assets associate with a different Snapshot Managers.
The provided region assets must associate with the same Snapshot Manager.
Explanation: This error is encountered when a protection plan is created or modified
and the provided region assets are associated with different Snapshot Managers.
Recommended Action: Ensure that specified region assets associate with the
same Snapshot Manager. Update the cloud provider plug-in configuration details
accordingly.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1611

Message: The assets that are subscribed to the protection plan belong to different
Snapshot Managers. Subscribed assets must belong to the same Snapshot
Manager.
Explanation: A single protection plan cannot protect the assets that are associated
with multiple Snapshot Managers.
Recommended Action: For the assets that are associated with different Snapshot
Managers, create different protection plans.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.
 NetBackup status codes 383
NetBackup status codes

NetBackup status code: 1612

Message: Some of the selected assets belong to a Snapshot Manager other than
the Snapshot Manager of the snapshot replication destination region asset. The
assets must belong to the same Snapshot Manager.
Explanation: You cannot replicate assets to the snapshot replication destination
region that is associated with a different Snapshot Manager.
Recommended Action: Ensure that the region assets associate with the same
Snapshot Manager. Update the cloud provider plug-in configuration details
accordingly.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1613

Message: For some of the selected assets, the source region is same as the cloud
snapshot replication destination region. The source region and the cloud snapshot
replication destination region must be different.
Explanation: The region of the asset you want to protect, and the cloud snapshot
replication destination region cannot be same.
Recommended Action: The source region and the cloud snapshot replication
destination region must be different.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1614

Message: Cloud snapshot replication is supported only for Amazon cloud assets.
Explanation: Cloud snapshot replication is supported only for Amazon cloud assets.
Recommended Action: Skip the assets that do not belong to Amazon cloud
provider.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1615

Message: Cloud snapshot replication is not supported for the asset type region.
Explanation: You cannot replicate or protect a region asset.
Recommended Action: Skip the asset with type region.
 NetBackup status codes 384
NetBackup status codes

Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1616

Message: Checkpoints are only allowed for the Backup from Snapshot storage
lifecycle policy operation.
Explanation: For a NAS-Data-Protection policy, you must configure Backup from
Snapshot storage lifecycle operation in policy to enable the checkpoint
functionality.
Recommended Action: Update the backup policy to use Backup from Snapshot
storage lifecycle operation before checkpoint functionality is enabled.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1617

Message: Cloud snapshot indexing is not supported for the specified asset.
Explanation: Following are the probable causes:
■ The specified asset is not in the same region as the Snapshot Manager.
■ Unsupported file systems are configured on the host machine to be indexed.
Recommended Action: Perform the following, as appropriate:
■ Ensure that the Snapshot Manager is deployed in the same region as the
specified asset.
■ Review the Snapshot Manager supported versions for indexing.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1618

Message: This retention period is incompatible with WORM storage expiration
duration. The lock minimum and maximum duration can be found in disk pool
properties. An update to disk pool properties may be needed if configuration changes
have been made to the underlying storage.
Explanation: WORM storage devices may impose a limitation on the duration of
lock times. Choosing a retention period (or retention level), that isn’t within the
allowed range of the storage volume, results in an image which cannot be WORM
locked.
 NetBackup status codes 385
NetBackup status codes

Recommended Action: The following procedure may be necessary once you are
sure that the retention level matches the range the underlying the storage volume
allows. This procedure only applies if the NetBackup Administration Console is in
use to create the policy.
To adjust the retention level
1 Save the policy schedule with the desired retention level, but with storage
selected as any available.
2 Edit the policy again, and now select the desired storage unit in the policy
attributes.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1630

Message: While configuring a NetBackup policy with the Veritas snapshot option
(VSO) FIM, you must select an SLP as Policy storage destination.
Explanation: The policy which uses the Veritas snapshot option (VSO) of FIM does
not support STU as policy storage. NetBackup only supports an SLP (storage
lifecycle policy) as a policy storage.
Recommended Action: Select Policy storage as storage lifecycle policy. If you
select STU as the Policy storage option, select Override policy storage selection
with the SLP option.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1633

Message: Invalid media server is provided in the API request.
Explanation: The media server name that is provided in the API request is invalid.
Recommended Action: Provide a valid NetBackup media server name.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1634

Message: Unable to process the EMM request.
Explanation: There are multiple reasons for EMM process failure in this situation.
Recommended Action: Perform the following as appropriate:
 NetBackup status codes 386
NetBackup status codes

■ Check whether the EMM service is up and running.

■ To diagnose the issue, review the EMM server logs for issues and troubleshoot
as necessary.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1635

Message: Unable to connect with the EMM server.
Explanation: There are multiple reasons for the EMM server connection failure.
Recommended Action: Troubleshoot any EMM server connection failure issues.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1636

Message: Backup time range filter is not supported in the API request.
Explanation: You cannot use both values at once (greater than and lesser than)
in the API request.
Recommended Action: Change the API request so that it does not use the backup
time range filter (greater than and lesser than).
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1637

Message: Duplicate filters are not supported in the API request.
Explanation: The same filter can only be used once in the API request.
Recommended Action: You cannot use the same filter twice in the API request.
Review the API request and remove any of the same filters that are used twice.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1800

Message: Invalid client list
 NetBackup status codes 387
NetBackup status codes

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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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.
Recommended Action: Make sure that all NetBackup services are started and
that nbdb installed correctly.
 NetBackup status codes 388
NetBackup status codes

Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 1919

Message: Another process modified this instance, database, or instance group.
Explanation: In the NetBackup Administration Console, the user tries to edit,
modify, or delete an instance, database, or instance group that another process
has modified.
 NetBackup status codes 389
NetBackup status codes

Recommended Action: Refresh the view (F5 key) in the NetBackup

Administration Console.
Do the following as appropriate:
■ When the Oracle APIs are used, if the If-Match header value does not match
the returned ETag value for the object you attempt to modify. Retrieve the latest
version of the object’s ETag and attempt your operation again.
Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 1921

Message: The specified instance or database cannot be found.
Explanation: The user tries to modify or to delete an instance or a database that
does not exist.
Recommended Action: Do one of the following:
■ CLI: Make sure that the instance or the database name is spelled correctly. If
working with a RAC database, the database unique name is case-sensitive.
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 on the Veritas Technical
Support website about this status code.
 NetBackup status codes 390
NetBackup status codes

NetBackup status code: 1922

An instance with this name/client is already registered
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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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 Veritas Technical Support.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1926

Message: The entry specified already exists
 NetBackup status codes 391
NetBackup status codes

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.
Click here to view technical notes and other information on the Veritas Technical
Support website 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 on the Veritas Technical
Support website 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 on the Veritas Technical
Support website about this status code.

NetBackup status code: 1932

Message: An instance, database, or instance group cannot be deleted or renamed
when it is included in a policy.
Explanation: An instance, database, or instance group cannot be deleted or
renamed when it is included in a NetBackup policy.
You cannot remove the last credential (unregister), modify a credential, or remove
credentials for a RAC or an Oracle instance if they are in a policy.
 NetBackup status codes 392
NetBackup status codes

Recommended Action: Remove the instance, database, or instance group from

all policies. Once the instance, database, or instance group is removed from all
policies you can retry the deletion or the modification process.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1933

Message: Cannot change instance or database state without credentials.
Explanation: An instance or a database must be registered before you can change
it to active or inactive.
Recommended Action: Verify that the database is registered before you attempt
to change the database state.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1946

Message: The current version of NetBackup on the client is incorrect for the
validation of the requested credential type.
Explanation: This error can occur by attempting to register an Oracle instance if
the client does not support the required NetBackup version. The error appears if
you attempt registration in the following ways:
■ Without using OS credentials.
■ Using Oracle Wallet credentials.
Recommended Action: Upgrade the NetBackup client to the current version of
NetBackup.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1952

Message: An availability group cannot be deleted when it is included in a policy.
First remove the availability group from all policies.
Explanation: A user attempted to delete an availability group but the availability
group is included in one or more policies.
Recommended Action: Remove the availability group from the policies in which
it is included. Then try again to delete the availability group.
 NetBackup status codes 393
NetBackup status codes

Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1953

Message: Unable to delete the asset because metadata for it exists. Expire any
backup images that contain the asset and try again.
Explanation: You cannot delete an asset that a backup image references.
Recommended Action: Expire any backup images that contain the asset and try
the operation again.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1954

Message: Moving an instance to a different RAC cluster is not allowed.
Explanation: A RAC instance cannot not be moved from one RAC cluster to
another.
Recommended Action: The instance must be delete and added into a different
RAC cluster.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1955

Message: Registering a RAC instance is not allowed.
Explanation: Instances in a RAC cluster cannot be registered.
Recommended Action: Credentials must be provided for all nodes of the RAC
cluster at the database level. If you need to back up a node in the RAC cluster as
a single instance you must delete the instance. After you delete that instance you
must add it as a single instance and add the single instance to the backup policy.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1956

Message: A registered, single instance cannot be moved to a RAC cluster.
Explanation: A single instance that has already been registered cannot be moved
into an existing RAC cluster.
 NetBackup status codes 394
NetBackup status codes

Recommended Action: To add an existing instance to an existing RAC cluster

you must delete that instance and then add it into the RAC cluster.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1957

Message: Unable to register a RAC cluster as it does not contain any RAC
instances.
Explanation: A RAC cluster that contains no RAC instances cannot be registered
with NetBackup.
Recommended Action: Add at least one RAC instance to your RAC cluster within
NetBackup.
Click here to view technical notes and other information on the Veritas Technical
Support website about this status code.

NetBackup status code: 1958

Message: Oracle Wallet credentials cannot be used with Oracle or OS credentials.
Explanation: The operation being performed used Oracle Wal