On Tue, 18 Feb 2003 at 4:00pm, rwong AT mrs.mni.mcgill DOT ca wrote

> When I ran 2.4.3b4, I was able to read from the tapes via amadmin, mt, and 
> dd piped to gtar.  Amrestore was not able to read the tapes, it kept
> complaining about "error reading file header".
> 
> So, I thought moving up to the current stable 2.4.3 version would fix the 
> amrestore problems.  It didn't.  And this time, the manual process of 
> using the unix cmd line tools didn't even get me the content *supposedly* 
> on the tapes as reported by amadmin.

I'd be interested in any debug files left in /tmp/amanda/ corresponding to 
your amrestore problems.  I've used amrecover with 2.4.2p2, 2.4.3, and 
2.4.4b1 (this morning) with no problems -- it can work.

> The last version I used which worked well was 2.4.3b3.  So I put that 
> version back in and now it doesn't get the estimates from it's own local 
> disks 
> but it can get the estimates from all the other remote clients.
> 
> log.1 has lines for each of the failed filesystems:
> FAIL planner hostname /disk/blah/restore 20030218 0 [missing result for 
> /disk/blah/restore in hostname response]

And what's in /tmp/amanda/sendsize*debug or /tmp/amanda/amandad*debug for 
those backups?

-- 
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University