Strictly cleaning density needs to be ‘compatible’ with the drive density.  It uses the same rule are read compatibility, so in our ADIC (Quantum) libraries we can use a CLNxxxL1 tape in LTO-1, LTO-2, LTO-3.  But if you put it into LTO-4 the drive ejects it.  NetBackup then tries to load it again, and your cleaning remaining tick rapidly down to zero.

 

However our StK (Sun) L700s use a quite different bar code scheme for cleaning tapes, and the suffix must be Cn (where n is density) or CU (universal).  We use CU, so the barcodes are CLNxxxCU.

 

Of course the actual cleaning tapes are the exact same, but the barcodes must be recognised by the library.  If your library has intelligence, check its GUI to see what it thinks your cleaning tape is.

 

As Rusty says, using manual cleaning by putting a tape in the IE station seems to bypass some checks, at least bypasses NBU.

 

 

Worst case, you (or someone) can take the cleaning tape and manually put it in the tape drive…or use robtest to load it and then move it back to the cap when it is done.

 

Then you can have breathing room to work through the issue.

 

Are you not able to use library based cleaning where NetBackup isn’t even aware of the cleaning tape?

 

 

 

What is the density of your tape drives? Cleaning tape density needs to be the same as drive density.

 

Please send output of the following:

 

vmquery -m CLN001

 

tpconfig -l

 

Regards

 

M.