I think the reboot question is valid based on the "can't lock raw device for 
read" message.  If some other entity is preventing NBU from gaining access to 
the device that entity has to be "kicked off" somehow.

Another option would be run a 'chkdsk /f /r' against that volume.  That will 
typically "kick everyone off" in the same manner that a reboot would.  I 
suspect you'll see something like:

"Chkdsk cannot run because the volume is in use by another
process.  Chkdsk may run if this volume is dismounted first.
ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
Would you like to force a dismount on this volume? (Y/N)"

If you do see that message, the process preventing chkdsk from running is 
probably the same one preventing NBU from doing its backup.

+----------------------------------------------------------------------
|This was sent by mojomagix AT yahoo DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------


_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu