--On Friday, November 01, 2002 19:21:50 -0500 Galen Johnson <[EMAIL PROTECTED]> wrote:
hmmm...it seems I sent my last reply only to Joshua..anywho...anyone have any clue as to which maillist one needs to be on for tar issues? I had responded to Joshua that I'm beginning to believe that tar is at issue here (tar 1.13.25). It's either
tar or the options fed to it but I can't find where in the code the options are fed to tar for the backup so I can try to give it a -g instead of -G (it was easy to find for amrecover).
GNU tar bug reports should go to [EMAIL PROTECTED], but see below..
=G=
Joshua Baker-LePain wrote:
On Fri, 1 Nov 2002 at 4:59pm, Galen Johnson wrote
I also have an issue with recover in that it deletes files when the
incremental is restored. I can almost understand why. It seems that
if the files aren't included in the incremental (and they won't be if
they haven't changed) the tar command seems to assume that the files
have been removed and deletes them to have the directory appear to be
in the "same state" as it thinks it was. Anyone else run into this?
Is there some subtle configuration I'm missing?
What exactly is the problem? The purpose of doing a restore (to most people)
is to make the filesystem after the restore be just like it was at the time
of the backup. This means that files deleted between backup levels need to
be deleted by the corresponding restore level.
If you need a file that was deleted before the incremental, restore it from
the next lower level backup.
On filesystems with limited space and a fair amount of churn, restoring all
the files ever deleted could also cause you to fill up your filesystem.
Frank
Sorry, I didn't quite understand this the first time. This seems like a
tar bug. What version are you running? If it's recent, I'd report it to
the tar maintainers. If not, try the latest.
I need an answer for this...if amrecover is gonna botch the restores I'm
gonna have to find a different solution which I would prefer not to do
since I like relative ease of Amanda. I'm using 2.4.3 with tar...which
I suspect may be part of the problem since the arguments ot restore are
'xpGvf' but I'm not familiar enough with how the old gnu style used to work.
You could always just 'amrestore' the tar images off the tape(s) and
fiddle with the tar options to see if you can get it do what you
want/what it should...
--
Frank Smith [EMAIL PROTECTED]
Systems Administrator Voice: 512-374-4673
Hoover's Online Fax: 512-374-4501
