On Sunday 02 April 2006 12:14, stan wrote:
I put this back on the list Stan, I hope you don't mind.
>On Sun, Apr 02, 2006 at 10:53:01AM -0500, Gene Heskett wrote:
>> On Sunday 02 April 2006 10:46, stan wrote:
>> >On Sun, Apr 02, 2006 at 10:05:11AM -0400, Jon LaBadie wrote:
>> >> On Sat, Apr 01, 2006 at 03:51:59PM -0500, stan wrote:
>> >> > I'm in the (hopefully) final stages of setting up my new
>> >> > Amanda machine.
>> >>
>> >> Never tried, submitted for your consideration and comments (you
>> >> == list).
>> >>
>> >> All three configs identical (actually links) except for a file
>> >> listing the device for that config (RAIT, FILE, or /dev) which
>> >> as you suggest is sourced (included) into amanda.conf.
>> >>
>> >> Same tape list suggests also 25 vtapes, which you create and
>> >> label.
>> >
>> >One more thought.
>> >
>> >The only thing I don't rally like about this is the amount of
>> > "wrapper" functionality that I need to set up around the Amanda
>> > system. EG the script taht I presently have to copy disk labels to
>> > vtapes, and one to keep the vtape disk space under control.
>>
>> To which I'd have to reply, that the wrapper script thats big enough
>> to do the job isn't too big. I currently have the amdump wrapped in
>> another script of about 3.5kb, and it calls another script when
>> amdump is finished thats about 6.5kb. I could probably clean up the
>> trash & make the comments more concise & cut the whole thing by 30%,
>> but it works, and I have a strong inclination to leave whats working
>> well alone. And it is working well for me.
>
>Well, I wasn't really complaining, just pointing out that if what
>I am tryign to do is of general interst, perhaps it, or some hooks
>to help support it, could be added in future versions of Amanda.
>
>I suspect that more and more people will want to integrate _some_
>vtape functionality into thier Amanda systems as time goes on, but
>I can't see people wanting to give up the security of physical tapes
>either, gievn the choice.
>
>BTW, what (in broad general concept) do your wrapper scripts do?
>Just curios, maybe they do something that I would find interesting.
The amdump wrapper isn't terribly complex, it runs amcheck once to force
the 'loading' of the correct (v)tape & then fires off the amdump run.
When thats finished and amdump has quit, releasing all the file locks,
it then runs a sub-script that does some housekeeping of its own
temporary files, then generates a tarball of the $config directory, and
a tarball of the indices & data directory such that the indices so
captured are fully complete and uptodate as of this backup, reflecting
the complete history of the backup for the last tapecycle days, and
appends that to the (v)tape.
Then it falls back to the first script and does a run of amverify. It
doesn't see the last 2 files of course but does its checking over the
amdump generated files. I get 3 emails from it per session, one from
the 2 scripts, one from amdump and one from amverify.
If I was still running tapes, I'd disable the amverify run as that would
double the wear rate, and tape drives & tapes have a short enough life
as it is. I was running this back when I was using tapes, and have
added the amverify run since switching to vtapes since in terms of hard
drive life, its virtually free. The HD is a WD 200GB pata drive, now
about 2 years old, spinning 24/7/365, and smartd has found nothing to
complain about yet.
That knocking sound in the background? Me, knocking on wood of
course :)
--
Cheers, Gene
People having trouble with vz bouncing email to me should add the word
'online' between the 'verizon', and the dot which bypasses vz's
stupid bounce rules. I do use spamassassin too. :-)
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2006 by Maurice Eugene Heskett, all rights reserved.
|
