Virtual tapes because bptm thinks that the virtual tape virtual write protect tab is set

[Jamie_Jamison]

I've been at work long enough today so that I think that this is amusing. I'm running NetBackup 6.5.1 on Solaris 10 and attempting to implement a VTL on a DataDomain DDR565 restorer. For some reason when a backup job starts bptm starts reporting that the tapes in my virtual tape pool have their virtual write protect tabs set. NetBackup then attempts to grab another tape only to find the same thing, and so on and so forth until all of the tapes in the pool have been run through.

10/31/2008 8:38:56 PM - requesting resource kira-hcart-robot-tld-1-moe
10/31/2008 8:38:56 PM - requesting resource kira.zgi.com.NBU_CLIENT.MAXJOBS.moe.zgi.com
10/31/2008 8:38:56 PM - requesting resource kira.zgi.com.NBU_POLICY.MAXJOBS.moe.zgi.com-IT1
10/31/2008 8:38:58 PM - granted resource kira.zgi.com.NBU_CLIENT.MAXJOBS.moe.zgi.com
10/31/2008 8:38:58 PM - granted resource kira.zgi.com.NBU_POLICY.MAXJOBS.moe.zgi.com-IT1
10/31/2008 8:38:58 PM - granted resource VTL004
10/31/2008 8:38:58 PM - granted resource moe.zgi.com-nrst0a-LTO1
10/31/2008 8:38:58 PM - granted resource kira-hcart-robot-tld-1-moe
10/31/2008 8:38:59 PM - estimated 539664008 kbytes needed
10/31/2008 8:39:00 PM - started process bpbrm (18640)
10/31/2008 8:39:00 PM - connecting
10/31/2008 8:39:01 PM - connected; connect time: 00:00:01
10/31/2008 8:39:05 PM - mounting VTL004
10/31/2008 8:39:31 PM - Error bptm(pid=18652) error requesting media, TpErrno = Request terminated because media is write protected
10/31/2008 8:39:31 PM - Error bptm(pid=18652) FREEZING media id VTL004, it is write protected and cannot be used for backups
10/31/2008 8:39:31 PM - current media VTL004 complete, requesting next media Any

While I find this amusing I do need to get these backups running. Has anyone else had this problem?

Thanks,

Jamie Jamison

[sdo]

Is this a new device?  Has it ever worked?  What might have changed recently?

[Omar_Villa]

I think this point more to the CDL software, what you have? EDL or FalconStor? because netbackup only see what the virtualization sotfware shows, so I will suggest to start from the CDL side, on thing to try is add just one vTape to your VTL run an inventory and see how it came up on NBU, also creating a temp VTL to see if the actual VTL is kind of corrupted, all this virtualization stuff depends a lot of the MetaData if something is wrong with a lot of weird stuff came up on the Netbackup side.

Please let us know.

Best Regards