amrecover woes, continued


Howdy!

I had posted this before but never got a good resolution as to what'sgoing on.. Later, Galen Johnson seemed to post something that soundedidentical to what's been going on with my amrecover, but that threadalso kinda faded out so I wanted to see if anyone has a resolution forthis nagging problem.

Simply put, amrecover doesn't seem to work when I'm restoring from SMBbackups.


If I have a directory on my W2K machine:

docs/
docs/file1.txt
docs/file2.txt
docs/new/file3.txt
docs/new/test.txt

All of which is backed up on a level 0 on, say, Tuesday. Then, a level 1is done on Wednesday, and the following file is added:


docs/file4.txt

So now Amanda has two backups, level 0 on Tuesday (tape1), and a level 1on Wednesday (tape2).

If I do an amrecover into a temporary directory (/tmp/test-restore),amrecover will correctly ask for tape1 first and restore the level0:


docs/
docs/file1.txt
docs/file2.txt
docs/new/file3.txt
docs/new/test.txt

Then it proceeds to do the level 1 on top of the level 0 (which iscorrect behavior so far), but when it starts the level 1, it will DELETEanything that is not included in the level 1:


tar: Deleting `./docs/'
tar: Deleting `./docs/new'

The end result? The directory will contain ONLY:

docs/
docs/new/
docs/file4.txt

It will have DELETED all the files that are in the Level 0 and not inthe Level 1.

I, too, suspect the G flag passed to GnuTar in the restore, but am notsure what the fix would be..

Can someone else run an SMB restore to verify this behavior? If you geta successful restore, could you please pass along your config and howyou did it?


Thanks very much in advance!

\marc