NetBackup 4.5 Troubleshooting Guide for Windows - Symantec

More documents

Recommendations

Info

Status Codes NetBackup 4.5 Troubleshooting Guide for Windows Explanation: An attempt was made to read the drive database, but it was found to be of an unknown format or version. The database is corrupt or there has been a mismatch of software components. Recommended Action: Check integrity of the drive database file ltidevs, located in the directory /usr/openv/volmgr/database (UNIX) or in the folder install_path\Volmgr\database (Windows). Display the device configuration to determine whether or not the database is corrupt, and restore a saved copy of the database file from catalog backups, or delete it and recreate the device configuration as needed. Device Management Status Code: 30 Message: Request terminated because media id will exceed maximum mount count Explanation: A mount request has been canceled because the media being requested has reached the maximum mount count associated with the media. Recommended Action: Replace the media or change the maximum mount count to a higher value, based on site policy. A media management interface can be used to view and change the maximum mounts allowed for the media. Check that the number of mounts for the media is set to a reasonable value given the media’s usage history, and correct it as needed using vmchange. Device Management Status Code: 31 Message: Requested number of drives are not configured Explanation: A tape mount request was submitted, and there are not enough drives in the configuration that match the requested density. Recommended Action: Ensure that ltid (the Media Manager device daemon on UNIX or the NetBackup Device Manager service on Windows) was stopped and restarted after changes were last made to the device configuration. Display the device configuration (using tpconfig -d or other means) to see the list of configured drives. Check the man page (command description) for tpreq to find the list of valid densities. Resubmit the mount request using a valid density that corresponds to a drive in the device configuration. Device Management Status Code: 32 Message: Error in getting semaphore Explanation: An attempt was made by ltid (the Media Manager device daemon on UNIX or the NetBackup Device Manager service on Windows) to obtain a semaphore used for arbitrating access to shared memory, and the request failed due to a system error. The error probably indicates a lack of system resources for semaphores, or mismatched software components. 324 NetBackup Troubleshooting Guide - Windows NT/2000 NetBackup 4.5 Troubleshooting Guide for Windows
NetBackup 4.5 Troubleshooting Guide for Windows Recommended Action: Chapter 5, Media Manager Status Codes and Messages 325 Status Codes 1. Examine command output (if available), debug logs, and system logs for messages related to the error. 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 ltid (the device daemon on UNIX or NetBackup Device Manager service on Windows). 2. On UNIX servers, gather the output of the ipcs -a command to see what resources are currently in use. Check the installed software components and verify that they are all at a compatible release version. Device Management Status Code: 33 Message: Error in SEMAPHORE operation Explanation: A process was unable to perform a semaphore operation (such as lock or unlock) associated with resources maintained by ltid. (ltid is the Media Manager device daemon on UNIX or the NetBackup Device Manager service on Windows.) Recommended Action: 1. Examine command output (if available), debug logs, and system logs for messages related to the error. a. 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 daemons/services, or execute the command’s verbose option, if available. b. Retry the operation and examine the logs. 2. On UNIX servers, gather the output of the ipcs -a command to see what resources are currently in use. Device Management Status Code: 34 Message: Error in getting semaphore for operator Explanation: A process was unable to perform a semaphore operation (such as lock or unlock) associated with resources maintained by ltid (the Media Manager device daemon on UNIX or the NetBackup Device 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:
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Media Manager Status Codes and Mess
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
Page 263 and 264:
Page 265 and 266:
Page 267 and 268:
Page 269 and 270:
Page 271 and 272:
Page 273 and 274:
Page 275 and 276:
Page 277 and 278:
Page 279 and 280:
Page 281 and 282:
Page 283 and 284:
Page 285 and 286:
Page 287 and 288: NetBackup 4.5 Troubleshooting Guide
Page 337: NetBackup 4.5 Troubleshooting Guide
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?