Hi John -
gtar version:
/usr/local/bin/tar --version
tar (GNU tar) 1.13
Oh well, I'm currently doing a 'gtar -xvf' on the entire image, and there
is that large number in front of everything, but it seems to be restoring
files properly. However I just noticed that it is restoring files I
thought were being excluded, so perhaps that's due to this version of
tar?
07247144107/./logs/smalltest (from current job process)
As for the duplicate partitions, that's not working, here's my entries
from amanda.conf and disklist:
define dumptype comp-user {
comment "Non-root partitions on reasonably fast machines"
options compress-fast
priority medium
index yes
program "GNUTAR"
exclude "./logs/"
}
define dumptype comp-logs {
comment "Amanda dump partition"
options compress-fast
priority low
index yes
program "GNUTAR"
exclude "./home"
and in disklist:
lou /dev/sd0g comp-user #/export exclude ./logs
lou /dev/sd0g comp-logs #/export just ./logs
daily[47]# amcheck -c daily
"disklist", line 21: duplicate disk record, previous on line 20
amcheck-clients: could not load "disklist"
(brought to you by Amanda 2.4.1p1)
I'll update gtar -- I had previously read not to update, but it sounds
like gtar+Amanda is now fixed in the current versions. Do I need to
update Amanda too (I know, loaded question!).
Thanks for the quick reply!
-doug
On Tue, 27 Mar 2001, John R. Jackson wrote:
> >I'm trying to do a full level 0 restore of a directory on our largest
> >backed up partition. ...
> >I successfully used the amrecover technique to have Amanda restore off of
> >the level 0 and all of the subsequent days, however I could tell that not
> >everything got restored. ...
>
> Amrecover is not really set up for full restores. Those often (as you
> discovered) need other options to the restore program.
>
> >... However, after reading the gtar info pages, it seems that
> >their interactive mechanism is not very easy to manipulate.
>
> This came up here recently. Because I don't know much about GNU tar,
> it did not get covered well enough in "the chapter". I'm reviewing that
> at the moment and will try to improve the text.
>
> Not that it helps you at the moment ... :-)
>
> >restore[25]# amrestore -p /dev/nrst0 lou /dev/sd0g | /usr/local/bin/tar xwvf -
> >...
> >amrestore: 11: restoring lou_dev_sd0g.20010313.0
> >extract 07253617211/./?q
>
> Uh, oh. That big number on the front may spell serious trouble.
>
> What version of GNU tar are you using? Pretty much everything up to
> 1.13.17 had bad problems (as has been discussed on this list numerous
> times).
>
> Do you have indexing turned on? Do the index files look like the above,
> i.e. have a big number at the front of every line?
>
> I don't know that there is any way out of this either. I don't recall
> what the problem was with GNU tar or whether it was something that could
> be "reversed".
>
> Sorry. I'm sure that's not exactly going to be the bright point of
> your day.
>
> If you gather some more information, such as poking around in the index
> files or generating new catalogues (gtar -t) of the dumps, we might be
> able to come up with a solution.
>
> >As an aside, is there a way to force Amanda to accept two disklist entries
> >for the same partition, but with different options? ...
>
> Since you're using GNU tar, you can use "logs" for one and "logs/."
> for the other.
>
> >Doug Silver
>
> John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
>
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Doug Silver
619 235-2665
Quantified Systems, Inc
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
