cancel
Showing results for 
Search instead for 
Did you mean: 

How does NetBackup sequence/prioritize scratch tape re-use

Genericus
Moderator
Moderator
   VIP   

Question about scratch tape re-use - Does anyone know what process NetBackup uses to determine scratch tape use? The sequence of prioritizing re-using tapes?

 

I had always assumed that scratch tapes were FIFO - as tapes expired and went into the scratch pool they would get re-used in some sort of order. I assumed it was first in, first out.

I am trying to grab and remove a specific barcode tape range, so as they expire and go into the scratch pool, I move them into another pool so they are not used.

For example, I have tapes with barcodes starting with 0 and tapes starting with 1. I have over 400 scratch tapes starting with 0, I got 30 back, 10 were ones I needed to move. When I came in this morning, one of these new scratch tapes was in use.

It does not have a low mount count, so that is not it.

Maybe based on last use time?

 

Thanks!

NetBackup 9.1.0.1 on Solaris 11, writing to Data Domain 9800 7.7.4.0
duplicating via SLP to LTO5 & LTO8 in SL8500 via ACSLS
1 ACCEPTED SOLUTION

Accepted Solutions

quebek
Moderator
Moderator
   VIP    Certified

Hi

Please take a look at below quotation:

"If more than one volume qualifies, NetBackup chooses the volume that was least recently used.
NetBackup then adds it to the media catalog and assigns it the specified retention level."

This was taken from NetBackup7.7_AdminGuideII_Server.pdf chapter How NetBackup selects media - you may want to review this documentation...

View solution in original post

1 REPLY 1

quebek
Moderator
Moderator
   VIP    Certified

Hi

Please take a look at below quotation:

"If more than one volume qualifies, NetBackup chooses the volume that was least recently used.
NetBackup then adds it to the media catalog and assigns it the specified retention level."

This was taken from NetBackup7.7_AdminGuideII_Server.pdf chapter How NetBackup selects media - you may want to review this documentation...