To take this discussion back to the whole list:
Stefan has a small untested  script to make use of a feature which I 
 think is not active currently.     He may have seen references in the code.
    amadmin  <config>  tapes  —days  N
which apparently would tell you what tapes will be required for N days to come.

      amadmin  <config>  tapes
tells  about  RUNTAPES  number  of tapes,  where RUNTAPES is
the number  configured to be used each day.    The  dash-dash-days  flag
would multiply  N days times  RUNTAPES,  I imagine.

You would still have to grep  through your tape library to see if the tapes 
were present.


If that  —days  flag  worked,  it could be very useful.    The flags aren’t
in my man pages,   and they don’t work for me  (though nothing complains about 
the flag).



Currently,   one could increase the RUNTAPES parameter arbitrarily,    then
      amadmin  <config>  tapes
      mtx  -f  /dev/changer   status
  and  some  grepping  to see if all those tapes were present.    But Stefan 
says he needs the
RUNTAPES param and can’t change it.


Or, Stefan suggests that maybe  AMCHECK  might be expected to  do the work for 
us, rather than us
having to write a script to check the library.

Comments, thoughts, from anybody else?   Discussion …..

Deb Baddorf
Fermilab


(please forgive capitalized words — that’s so spell checker will stop changing 
them into OTHER words)



On Feb 17, 2015, at 3:08 PM, Stefan G. Weichinger <[email protected]> wrote:

> On 17.02.2015 20:51, Debra S Baddorf wrote:
> 
>>> When I run it on a server with  amadmin-3.3.6 .. the help tells me so, yes.
>> 
>> Hmmm — I’m at 3.3.7   and I don’t see that.
>> Only for OTHER  amadmin  commands,  such as  bump.
> 
> maybe that got changed, yes!
> Sophisticated users do a code-view .. others ask JLM on the list ;-)
> 
> 
>>> I don't like fiddling with $runtapes, no, I need that parameter to be
>>> exactly defined at the customer in case.
>>> 
>>> And it wouldn't be an elegant solution IMO (I wouldn't understand it in
>>> a year and screw it up by "correcting" the value of $runtapes).
>> 
>> Well, if I changed it,  I would put a large paragraph of comments about WHY
>> I had changed the value!
> 
> I prefer doing things in a way that does not bend things.
> As seen above, upstream code changes ...
> 
> 
>>>> Maybe this makes it worth putting the amanda-users back into the email 
>>>> address
>>>> and sharing the concept with the list?   And then re-sharing your script 
>>>> (since I’ve
>>>> obliterated it from this email)
>>> 
>>> Feel free to share it there if you want ... I am running out of time
>>> here right now and got to leave now. Maybe we wait with sharing it .. ->
>> 
>> I’ll put together both your script,  and my questions about  —days
>> and about the   RUNTAPES   param   and post them to the list.
>> Just to get some conversation flowing.
>> Catch ya later.
> 
> Thanks, looking fwd.
> 
> To me that looks like a nice feature request for amcheck!
> 
> Stefan
> 


Reply via email to