DUMPed /home trumps TARred /home/tim in index (fwd)

[Tape Backup]

I'm still tinkering with AMANDA.
I've pretty much committed to GNUTAR, because I'm on an HP
with logical volumes and can't get dump to work on the clients.

At one point, I tried dump on /home on the server and it worked.
Since then, I've been using TAR on /home/tim.  

Today I deleted a file and tried to restore it, but
according to amrecover, it had not been backed up,
as it was insisting  setdisk be /home, which hadn't been
backed up lately.  The file ~had~ been backed up in the normal tar run.


Do I need to wipe out my past flirtations with DUMP
from the index before I can get TAR to work? 
Is fidelity critical?  
Can I get that DUMP expunged from my record?






BTW
What was the final verdict on
the "--listed-incremental" and "--incremental"
flurry recently?

Re: DUMPed /home trumps TARred /home/tim in index (fwd)

[John R. Jackson]

>... it was insisting  setdisk be /home ...

Huh?  What was your current working directory when you started amrecover?
Did you try "setdisk /home/tim" and if so and it failed, what did it say?

>Do I need to wipe out my past flirtations with DUMP
>from the index before I can get TAR to work? 

It's possible you'll need to wipe out the memory of /home, but DUMP vs
tar has nothing to do with it.  The index files are identical.

John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]