Amanda-Users

Re: incomplete backups

2002-11-13 22:31:23
Subject: Re: incomplete backups
From: Gene Heskett <gene_heskett AT iolinc DOT net>
To: Frank Smith <fsmith AT hoovers DOT com>, amanda-users AT amanda DOT org
Date: Wed, 13 Nov 2002 22:05:06 -0500
On Wednesday 13 November 2002 13:14, Frank Smith wrote:
>--On Wednesday, November 13, 2002 09:49:56 -0700 "Carl D. Blake" 
<carl AT boeckeler DOT com> wrote:
>> On Tue, 2002-11-12 at 18:02, Gene Heskett wrote:
>>> Greets folks;
>>>
>>> I now have recovered as much as I can, but a couple of things
>>> need to be said.
>>>
>>> Not enough emphasis is placed on the fact that tar won't access
>>> a file with any kind of a lock on it, and in the case of
>>> amanda, its certainly a fixable problem.  I recovered all the
>>> indexes and curfiles and such but absolutely nothing else that
>>> could be construed as a configuration file.
>>>
>>> So chg-scsi.conf, amanda.conf, disklist, tapelist & the rest of
>>> the configuration stuff in /usr/local/etc/amanda/DailySet1 is
>>> gone and I'm going to have to re-invent a goodly number of
>>> wheels before amanda is back up and running.
>>
>> I'm a little puzzled.  When I look at the files that amanda says
>> it backed up it looks like it backed up the above files you
>> mentioned on my system.  My system is a RedHat Linux 6.0 system
>> using GNU tar V1.12.  Is your system and/or tar different?
>
>I don't think it is a universal problem, although I'm sure it can
> be painful for those that discover it.  My system (Debian 3.0,
> tar 1.13.19) backs them up fine.  I even get occasional 'file
> changed as we read it' messages backing up changing index files,
> so tar isn't even skipping files with active write locks on my
> system.

I wonder if thats one of the diffs between tar-1.13-25 which I'm 
running, and tar-1.13-19.  In which case it might be smart to 
back-pedal one minor version.

One of those things that makes one 'hummmm'.

>  If there are certain versions, filesystems, etc. that can cause
> this problem then something needs to be added to the docs so the
> people impacted can work around it.

I agree, but first we need to define if we can, just why it didn't, 
and if possible, fix that.  Recoveries are relatively few and far 
between, as they should be, so this might take a while to draw a 
bead on.

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

<Prev in Thread] Current Thread [Next in Thread>