Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations biv343 on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

NW does not automatically use recyclable tapes

Status
Not open for further replies.

goony

Technical User
Apr 15, 2003
170
US
I have backups that are set to 3 weeks for browse, 1 month for retention. When Networker declares the tapes to be 'expired', I put them back into the jukebox and do an inventory on that tape.

When networker gets around to needing a tape, it doesn't use these recyclable tapes and instead sits waiting for media. I have to then label some of these tapes in order to satisfy Networker. My autochanger has Media Management=ENABLED and in the tape pools I have Recycle To Other Pools=YES and Recycle From Other Pools=YES.

Below is output from an NSRJB command- all of the tapes with the asterisks (*) are tapes that I have put back in after they have become recyclable.

What am I doing wrong? I want Networker to use these tapes and label them as needed and not bug me to be doing it.

Thanks!

Code:
bash-2.03$ nsrjb

Jukebox Qualstar_Prod:
  slot  volume         pool            barcode   volume id        recyclable
     1: 000002L1       Default         000002L1  2204525793       no        
     2: 000031L1       Local Backup    000031L1  125633203        no        
     3: 000025L1       Local Backup    000025L1  91198351         no        
     4: 000004L1       Manual Backups  000004L1  1011144449       no        
     5: 000029L1       Local Backup    000029L1  107975407        no        
     6: 000048L1       Manual Backups  000048L1  4217871127       no        
     7: 000017L1*                                2143415809                 
     8: 000018L1*                                3711902465                 
     9: 000006L1*                                2145492225                 
    10:                                                                     
    11: 000026L1       Local Backup    000026L1  74421300         no        
    12: 000057L1*                                3135950337                 
    13: 000053L1*                                3999447809                 
    14: 000033L1       Offsite Clone   000033L1  712962956        no        
    15: 000046L1*                                2145518337                 
    16: 000010L1*                                3627012097                 
    17: 000041L1       Default         000041L1  2824693546       no        
    18: 000003L1*                                2914502657                 
    19: 000052L1       Test Clone      000052L1  1936255471       no        
    20: 000015L1       Local Backup    000015L1  24624525         no        
    21: 000058L1*                                3135926529                 
    22: 000059L1*                                3135979521                 
        *not registered in the NetWorker media data base

drive 1 (/dev/rmt/0cbn) slot 14: 000033L1 (mounted)  
drive 2 (/dev/rmt/1cbn) slot  2: 000031L1 (mounted)
 
What you say is obviously not completely true:

"Not registered in the media db" simply means that NW does not
know the media any longer.

This means that some process did not recycle/relabel the media
(in this case he would create a new entry in the media db)
but removed the entry from the media db (for instance using
nsrmm -d volume).

By default, NW will not do this. So either you found a bug or somebody
stated such operation.

NW can still read the media but as long as you do not scan it, such
tapes will not be re-added.

 
This scenario results when adding tapes from a particular group back into the jukebox via a 'web front end for operators' that I wrote.

I'm working with Legato support to figure out what might be going wrong (read: I've setup tons of debug stuff in my code and am writing all commands and data out to a logfile to catch where the problem is occuring)

Thanks for the info!
 
I am embarrassed.

Turns out the tape volumes in question came from our development server and accidentally got put into the
tapes that were expired for our production server (someone
took off the tape dots used to segregate the tapes!!),
so it is no wonder the system is treating them as 'foreign'.

Maybe this will help someone in the future...

Thanks!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top