* Chris Miller <[email protected]> [20181119 12:15]:
> Hi Folks,
>
> Last week I created a set of vtapes {slot0..slot21}, (because I didn't know
> if zero was used). I labeled each of them with a unique label. I ran amdump
> for each of three clients and I got semi-successful results, meaning two
> completed and one left artifacts on the holding disk but never got written to
> vtape. Later that day, I ran a second amdump on all three clients, but this
> time all three clients failed. amcheck reports: "Taper scan algorithm did not
> find an acceptable volume."
>
> Clearly I don't understand how to manage vtapes. Or maybe my configuration is
> wrong. How do I know that AMANDA realizes that there are 21 vtapes available?
> How do I ask why none of these is acceptable?
>
> I ran amoverview, which tells me what I already knew, meaning that I
> completed one level 0 backup for each client. I ran amreport with much more
> detailed description of what I already knew.
>
> I understand that AMANDA takes great pride managing the tape library to avoid
> operational catastrophes like re-using a tape which happens to be the only
> backup. I have zero experience with real tapes, and the tape library model is
> not helpful for someone like me with no tape library experience trying to use
> vtape. For example, do I have to label my vtapes, or can I tell AMANDA to
> label them for me since I don't think I really care what the label says. And
> then how do I tell AMANDA that it is acceptable to re-use the oldest vtape in
> the collection? How do I take a vtape out of the rotation and how do I add a
> new tape to the rotation?
>
> Please don't be afraid to answer my questions with a short and sweet
> reference to an article. There is little point explaining the subtleties to
> me in e-mail, when a perfectly good explanation already exists.
What taperscan algorithm are you using? By default, it is set to 'traditional'
if it is not specified, which might be not what you want.
I've always used the 'oldest' taperscan algorithm:
define taperscan "my-taperscan" {
plugin "oldest"
}
taperscan "my-taperscan"
Read 'man amanda-taperscan' for the details.
You can check which 'tapes' amanda expects for the next run with the command
'amadmin <CONFIG> tape', running it as the amanda user.
Also, 'amtape <CONFIG> inventory' will tell you what amanda is aware of.
This info is based on the cached meta-info for the changers, and might
not be accurate (stale). 'amtape <CONFIG> update' will force a rescan
of the (virtual) changer.
Hope this makes sense,
jf
>
> Thanks for the help,
> --
> Chris.
>
> V:916.974.0424
> F:916.974.0428
