On Wednesday 13 November 2002 13:20, Jon LaBadie wrote:
>On Wed, Nov 13, 2002 at 04:59:19PM +0000, Niall O Broin wrote:
>> On Wed, Nov 13, 2002 at 11:14:40AM -0500, Gene Heskett wrote:
>> > >This is exactly why my nightly backup script, after running
>> > > the amdumps and rewinding/ejecting the tapes, tars up all
>> > > the amanda config files and directories.  That tar ball then
>> > > gets put two places (on two separate machines), each of
>> > > which are backed up. So, if my amanda server completely
>> > > dies, I'll still have my complete config and set up as of
>> > > last night.
>> >
>> > So it looks as if I'm going to have to reinvent that wheel
>> > too. I take it that must depend on the system, Jon L. tells me
>> > his backups do contain all that.  I *think* he's doing
>> > solaris.
>>
>> Nothing to do with the system at all. It's just a little
>> something added into the script which runs amanda each day - I
>> presume at least 95% of amanda users run amanda from a cron
>> driven script. A couple of lines in that /those (if you run more
>> than one config) script(s) and bingo - indices safely squirelled
>> away.
>
>I think Gene was refering to his backup on Linux missing things
> like amanda.conf, tapelist, disklist, ...  He attributed this to
> tar "honoring" locks on these files during backup.  I noted to
> him that my backups on Solaris do not seem to lack these files.

Thats it precisely, Jon.  Once I get the majority of this thing 
running again, I'll see if amrecover can find those files in the 
indices I do have.  Its disabled in manda's crontab ATM for obvious 
reasons.

-- 
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz  512M
99.19% setiathome rank, not too shabby for a WV hillbilly