On Wed, Dec 27, 2017 at 05:26:04PM -0500, Jean-Louis Martineau wrote:
> Jon,
> 
> 'amadmin tape' list the oldest reusable label, it doesn't use the 
> taperscan algorithm and it doesn't check what is currently loaded in the 
> changer.
> 'amcheck' and 'amtape' run the taperscan algorithm and verify they are 
> in the changer.
> 
> Which taperscan are you using?
> 

Just a bit more info (I already posted "lexical" is my algorithm.

I did an "amtape DS1 inventory".  It lists all 240 tapes.

The output has two values in the last column, "[retention-tapes]"
and "[retention-no]".  However these do not match the in-use vs.
skipped tapes.

  DS1-000 to DS1-009 [retention-no]     # recreated after crash
                                        # currently being skipped
  DS1-010 to DS1-018 [retention-tapes]  # most recently used
                                        # after looping from 207
  DS1-019 to DS1-077 [retention-no]     # oldest used and I assume
                                        # will be used next
  DS1-078 to DS1-207 [retention-tapes]  # used after 077 and
                                        # looped to 010
  DS1-208 to DS1-239 [retention-no]     # newly created, never used
                                        # skipped over

Jon
> Jean-Louis
> 
> 
> On 27/12/17 05:12 PM, Jon LaBadie wrote:
> > A while back one of my small older drives containing
> > vtapes failed.  I replaced it and its twin with larger
> > drives.  I moved the still good vtapes from the good
> > twin to the new drives, created empty vtapes for the
> > lost backups from the crashed drive, and added a good
> > number of new vtapes.
> >
> > However, none of the previously unused vtapes are
> > being used by amanda and I can not figure out why.
> >
> > Here are relevant entries from my current tape list.
> >
> > 20171227025501 DS1-018 reuse BLOCKSIZE:32 POOL:DS1 STORAGE:DS1 CONFIG:DS1
> > ...
> > 20170705025501 DS1-019 reuse BLOCKSIZE:32 POOL:DS1 STORAGE:DS1 CONFIG:DS1
> > 20170627205502 DS1-009 reuse BLOCKSIZE:32 POOL:DS1 STORAGE:DS1 CONFIG:DS1
> > ...
> > 20170618085502 DS1-209 reuse BLOCKSIZE:32 POOL:DS1 STORAGE:DS1 CONFIG:DS1
> > 20170618025502 DS1-208 reuse BLOCKSIZE:32 POOL:DS1 STORAGE:DS1 CONFIG:DS1
> >
> > DS1-018 is the vtape it used last night, 019 will be
> > used tonight.  DS1-208 is at the bottom of the list
> > and amanda is skipping all 40 tapes between it and
> > DS1-009.
> >
> >
> > There are 3 ways to check what tapes will be used.
> > However their results differ.
> >
> > $ amanda amadmin DS1 tape
> > The next Amanda should go onto tape DS1-208 or a new tape.
> >                                 tape DS1-209 or a new tape.
> >                                 tape DS1-210 or a new tape.
> >
> > $ amanda amtape DS1 taper
> > slot 19: volume 'DS1-019'
> > Will write to volume 'DS1-019' in slot 19.
> >
> > $ amcheck DS1
> > Amanda Tape Server Host Check
> > -----------------------------
> > NOTE: Holding disk '/amanda/Holding': 293752 MB disk space available, using 
> > 293652 MB
> > slot 19: volume 'DS1-019'
> > Will write to volume 'DS1-019' in slot 19.
> >
> > [ looks the same as amtape ]
> >
> >
> > Any clues as to why the 40+ tapes are not being used?
> >
> > Why do amadmin and amtape/amcheck use different
> > algorithms when looking up the next tape(s) to be used?
> >
> > Jon
> This message is the property of CARBONITE, INC. and may contain confidential 
> or privileged information.
> If this message has been delivered to you by mistake, then do not copy or 
> deliver this message to anyone.  Instead, destroy it and notify me by reply 
> e-mail
>>> End of included message <<<

-- 
Jon H. LaBadie                 j...@jgcomp.com
 11226 South Shore Rd.          (703) 787-0688 (H)
 Reston, VA  20190              (703) 935-6720 (C)

Reply via email to