This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
netbackup [2018/08/22 08:48] ss_wiki_admin created |
netbackup [2020/08/11 08:58] (current) ss_wiki_admin |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ==== Custom scripts ==== | ==== Custom scripts ==== | ||
| + | == Disk performance benchmark == | ||
| + | <code bash> | ||
| + | / | ||
| + | </ | ||
| + | |||
| + | == Drive down checker == | ||
| <code bash drive_down_checker.ksh> | <code bash drive_down_checker.ksh> | ||
| #!/bin/ksh | #!/bin/ksh | ||
| Line 24: | Line 30: | ||
| fi | fi | ||
| </ | </ | ||
| + | |||
| + | == Release SCSI reservations on Tape Drives == | ||
| + | In shared environments it is imperative that SCSI traffic passes through the network/SAN infrastructure unmolested and without corruption, otherwise issues such as SCSI reservations can arise due to devices not releasing their reservations correctly and/or being unable to acquire them. | ||
| + | |||
| + | Disabling SCSI reservations in Netbackup may be a workaround - Netbackup will then handle drive reservations and conflicts internally. | ||
| + | |||
| + | Release reservations manually with the following command: | ||
| + | <code bash> | ||
| + | vmoprcmd -crawlreleasebyname < | ||
| + | </ | ||
| + | |||
| + | == Release Netbackup Resource == | ||
| + | <code bash> | ||
| + | nbrbutil -dump | ||
| + | nbrbutil -releaseMDS <key> | ||
| + | nbrbutil -reportInconsistentAllocations | ||
| + | nbrbutil -releaseDrive <drive name> | ||
| + | </ | ||
| + | Allocations can also be investigated and removed by deleting files in / | ||