NetBackup 4.5 Troubleshooting Guide for Windows - Symantec

More documents

Recommendations

Info

Status Codes NetBackup 4.5 Troubleshooting Guide for Windows 2. Ensure that the specified robot number and volume group are compatible. If volumes in the volume group have a given robot number (for example, 0), then volumes with a different robot number (for example, 1) cannot be added to that volume group. Volumes cannot be moved directly from one robotic volume group to another robotic volume group since the intermediate steps (some volume entries changed, some not) would cause a conflict with robot numbers. Choose a different volume group on the request, or let the volume group be automatically selected. Volume group selection depends on the specific interface being used. Media Manager Status Code: 56 Message: invalid database version header Explanation: vmd could not find a recognizable volume database version in the volume database, and cannot initialize with the database currently in place. (vmd is the Media Manager volume daemon on UNIX and the NetBackup Volume Manager service on Windows.) Recommended Action: 1. Examine the daemon debug log for a more detailed message on the error. a. If not already enabled, enable debug logging by creating the necessary directories/folders. Increase the level of verbosity by adding the VERBOSE option in the vm.conf file and restarting the volume daemon, or start vmd with the verbose option. b. Retry the operation and examine the logs. 2. From catalog backups or another source if available, restore an earlier version of the database file, /usr/openv/volmgr/database/volDB (UNIX) or install_path\Volmgr\database\volDB (Windows), and restart vmd. Media Manager Status Code: 57 Message: error auto-generating volume group Explanation: A request was made to add or change volumes in the volume configuration using automatic generation of the volume group name. A unique volume group name could not be generated because the available combinations were used up. Recommended Action: Consolidate volumes into volume groups within the targeted robot number so that a new volume group can be automatically generated, or provide a specific volume group name. 228 NetBackup Troubleshooting Guide - Windows NT/2000 NetBackup 4.5 Troubleshooting Guide for Windows
NetBackup 4.5 Troubleshooting Guide for Windows Chapter 5, Media Manager Status Codes and Messages 229 Status Codes Media Manager Status Code: 58 Message: daemon cannot obtain socket Explanation: vmd could not bind to its socket. (vmd is the Media Manager volume daemon on UNIX and the NetBackup Volume Manager service on Windows.) A system call failed when vmd attempted to bind to its configured port number. This is usually caused by another process having acquired the port before the vmd daemon or service started. Recommended Action: 1. Examine the daemon debug log for a more detailed message on the system error. a. If not already enabled, enable debug logging by creating the necessary directories/folders. Increase the level of verbosity by adding the VERBOSE option in the vm.conf file and restarting the volume daemon, or start vmd with the verbose option. b. Retry the operation and examine the logs. 2. If another process has the port, use other system commands to determine the process. Based on the result, either change the port number in your services file or map, or terminate the process that has acquired the port. 3. UNIX only: Another possible cause for this error is terminating vmd with the kill command. If you have to stop vmd, the recommended method is to use the Terminate Media Manager Volume Daemon option on the Special menu in vmadm (or the equivalent command line request, vmctrldbm -t). Using the kill command to stop this process can leave it unable to bind to its assigned port the next time it is restarted. When the socket problem has occurred, the daemon debug log contains lines similar to the following: unable to obtain bound socket, Address already in use (125) Media Manager Status Code: 59 Message: daemon failed accepting connection Explanation: vmd could not accept a new connection due to a system call failure. (vmd is the Media Manager volume daemon on UNIX and the NetBackup Volume Manager service on Windows.) Recommended Action: NetBackup 4.5 Troubleshooting Guide for Windows
Page 1 and 2:
NetBackup 4.5 Troubleshooting Guide
Page 3 and 4:
Contents NetBackup 4.5 Troubleshoot
Page 5 and 6:
Page 7 and 8:
Page 9 and 10:
Preface Audience Organization NetBa
Page 11 and 12:
Page 13 and 14:
Page 15 and 16:
Introduction 1 This chapter explain
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
General Test and Troubleshooting Pr
Page 45 and 46:
NetBackup Configuration 1 Servers N
Page 47 and 48:
Page 49 and 50:
Windows NT/2000 Master Server Polic
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Reports NetBackup 4.5 Troubleshooti
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Media Manager Logs NetBackup 4.5 Tr
Page 65 and 66:
64 = Backup Status 128 = Media Devi
Page 67 and 68:
Page 69 and 70:
NetBackup Status Codes and Messages
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Messages NetBackup 4.5 Troubleshoot
Page 189 and 190:
Page 191 and 192: NetBackup 4.5 Troubleshooting Guide
Page 215 and 216: Media Manager Status Codes and Mess
Page 241: NetBackup 4.5 Troubleshooting Guide
Page 293 and 294:
Page 295 and 296:
Page 297 and 298:
Page 299 and 300:
Page 301 and 302:
Page 303 and 304:
Page 305 and 306:
Page 307 and 308:
Page 309 and 310:
Page 311 and 312:
Page 313 and 314:
Page 315 and 316:
Page 317 and 318:
Page 319 and 320:
Page 321 and 322:
Page 323 and 324:
Page 325 and 326:
Page 327 and 328:
Page 329 and 330:
Page 331 and 332:
Page 333 and 334:
Page 335 and 336:
Page 337 and 338:
Page 339 and 340:
Page 341 and 342:
Page 343 and 344:
Page 345 and 346:
Page 347 and 348:
Page 349 and 350:
Page 351 and 352:
Page 353 and 354:
Page 355 and 356:
Page 357 and 358:
Page 359 and 360:
Page 361 and 362:
Page 363 and 364:
Page 365 and 366:
Page 367 and 368:
Page 369 and 370:
Page 371 and 372:
Page 373 and 374:
Page 375 and 376:
Page 377 and 378:
Page 379 and 380:
Page 381 and 382:
Page 383 and 384:
Page 385 and 386:
Page 387 and 388:
Page 389 and 390:
Page 391 and 392:
Page 393 and 394:
Page 395 and 396:
Page 397 and 398:
Page 399 and 400:
Page 401 and 402:
Page 403 and 404:
Page 405 and 406:
Page 407 and 408:
Page 409 and 410:
Page 411 and 412:
Page 413 and 414:
Page 415 and 416:
Page 417 and 418:
Page 419 and 420:
Page 421 and 422:
Page 423 and 424:
Page 425 and 426:
Page 427 and 428:
Page 429 and 430:
Page 431 and 432:
Page 433 and 434:
Page 435 and 436:
Figure 6. Starting NetBackup Master
Page 437 and 438:
Figure 7. Backup or Archive to Tape
Page 439 and 440:
Page 441 and 442:
Page 443 and 444:
Backups - Macintosh Clients NetBack
Page 445 and 446:
Page 447 and 448:
Page 449 and 450:
Page 451 and 452:
Restores - NetWare Clients NetBacku
Page 453 and 454:
NetBackup Directories and Files Bac
Page 455 and 456:
Page 457 and 458:
Page 459 and 460:
Page 461 and 462:
Page 463 and 464:
Page 465 and 466:
Startup Process NetBackup 4.5 Troub
Page 467 and 468:
Page 469 and 470:
Barcode Operations NetBackup 4.5 Tr
Page 471 and 472:
Media Manager Components Media Mana
Page 473 and 474:
Page 475 and 476:
Page 477 and 478:
Page 479 and 480:
Page 481 and 482:
Page 483 and 484:
Page 485 and 486:
Robotic Test Utilities C Each of th
Page 487 and 488:
Backup Exec Tape Reader for NetBack
Page 489 and 490:
Page 491 and 492:
Page 493 and 494:
◆ Backup Exec 8.x Device & Media
Page 495 and 496:
Page 497 and 498:
Examples NetBackup 4.5 Troubleshoot
Page 499 and 500:
Page 501 and 502:
Troubleshooting with the Debug Logs
Page 503 and 504:
Page 505 and 506:
Page 507 and 508:
Glossary access control list (ACL)
Page 509 and 510:
ack up backup The act of copying an
Page 511 and 512:
configuration consolidated eject co
Page 513 and 514:
disaster recovery disk disk-image b
Page 515 and 516:
global attributes GDM Dashboard GDM
Page 517 and 518:
inject inport inode install_path jb
Page 519 and 520:
media media access port media host
Page 521 and 522:
NetBackup Device Manager service Ne
Page 523 and 524:
port A location used for transferri
Page 525 and 526:
estore retention level retention pe
Page 527 and 528:
session Session (Vault) shared driv
Page 529 and 530:
tape overhead tape spanning tar tar
Page 531 and 532:
TSH - Tape Stacker Half-inch A Medi
Page 533 and 534:
wildcard characters Microsoft Windo
Page 535 and 536:
Index Numerics 3pc.conf file 123 A
Page 537 and 538:
E F NetBackup 4.5 Troubleshooting G
Page 539 and 540:
O P NetBackup 4.5 Troubleshooting G
Page 541 and 542:
show all

NetBackup 4.5 Troubleshooting Guide for Windows - Symantec

Create successful ePaper yourself

Delete template?

Save as template?