Now, some might say that I’m not the smartest card in the deck for what I’m about to note, but sometimes I don’t notice new commands when they appear in NetWorker, particularly if I skimmed through release notes.
I was pleasantly surprised today to find that a new command had slipped in at some point called “jbverify”. I can immediately see it however entering my stable of must-use commands, particularly in a support environment.
To quote the man page, jbverify:
[V]erifies the devices defined in the NetWorker database, making sure that each one of them is configured properly by checking them for accessibility and usability.
This is the sort of diagnostic tool that support people live for, and sites suddenly experiencing strange jukebox issues should think of as a matter of course.
When run on my lab server this afternoon, I got the following badly formatted but still very useful output:
# jbverify 14866:jbverify: Jbverify is running on host nox, Linux 2.6.18-128.1.6.el5 14912:jbverify: Processing stand-alone devices... 14913:jbverify: Processing /d/nsr/02/_AF_readonly 14915:jbverify: Finished processing /d/nsr/02/_AF_readonly 14913:jbverify: Processing /d/nsr/idata/backup/_AF_readonly 14915:jbverify: Finished processing /d/nsr/idata/backup/_AF_readonly 14913:jbverify: Processing /d/nsr/01/_AF_readonly 14915:jbverify: Finished processing /d/nsr/01/_AF_readonly 14913:jbverify: Processing /d/nsr/idata/backup 14915:jbverify: Finished processing /d/nsr/idata/backup 14913:jbverify: Processing /d/nsr/idata/clone/_AF_readonly 14915:jbverify: Finished processing /d/nsr/idata/clone/_AF_readonly 14913:jbverify: Processing /d/nsr/01 14915:jbverify: Finished processing /d/nsr/01 14913:jbverify: Processing /d/nsr/03 14915:jbverify: Finished processing /d/nsr/03 14913:jbverify: Processing /d/nsr/03/_AF_readonly 14915:jbverify: Finished processing /d/nsr/03/_AF_readonly 14913:jbverify: Processing /d/nsr/02 14915:jbverify: Finished processing /d/nsr/02 14913:jbverify: Processing /d/nsr/idata/clone 14915:jbverify: Finished processing /d/nsr/idata/clone 14917:jbverify: Finished processing stand-alone devices. 14918:jbverify: Processing jukebox devices... 14920:jbverify: Processing jukebox LTO1_LIB: 14733:jbverify: Testing drive 1 (/dev/nst0) of JB LTO1_LIB 14927:jbverify: Jukebox LTO1_LIB on nox successfully processed. 14929:jbverify: Finished processing jukebox devices. ********************************************************************** Summary report of jbverify ======= ====== == ======== Hostname Device Handle Blocksize Jukebox Drv No. Status -------- ------------- --------- ------- ------- ------ nox /d/nsr/02/_AF_readonly 131072 N/A N/A Pass nox /d/nsr/idata/backup/_AF_readonly 131072 N/A N/A Pass nox /d/nsr/01/_AF_readonly 131072 N/A N/A Pass nox /d/nsr/idata/backup 131072 N/A N/A Pass nox /d/nsr/idata/clone/_AF_readonly 131072 N/A N/A Pass nox /d/nsr/01 131072 N/A N/A Pass nox /d/nsr/03 131072 N/A N/A Pass nox /d/nsr/03/_AF_readonly 131072 N/A N/A Pass nox /d/nsr/02 131072 N/A N/A Pass nox /d/nsr/idata/clone 131072 N/A N/A Pass nox /dev/nst0 65536 LTO1_LIB 1 Pass **********************************************************************
If you’ve come from NetBackup, the nature of this program is somewhat reminsicent of the robtest utility. I don’t claim EMC are special for having introduced this tool, but I do applaud that it’s there (and lament that I didn’t notice it sooner).
(One thing to note: after running jbverify, make sure you reset your jukebox.)