amrecover woes, continued

[Marc N. Cannava]

Howdy!

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

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

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 1 is 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 1 on 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 is correct behavior so far), but when it starts the level 1, it will DELETE anything 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 in the Level 1.

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

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

Thanks very much in advance!

\marc