On Tue, 7 May 2002 at 10:17am, Martinez, Michael - CSREES/ISTM wrote
> Yes, all the files are listed, both using "restore -tf" and amrecover.
> Another thing I discovered is that the backup is not entirely good, on the
> server as well as the client. I can restore some files, but not others, even
> though these others may be listed in the index.
Uh oh.
> I'm getting checksum errors, as for example:
*snip*
The *first* thing I'd do is make sure that your hardware is OK. Do a dump
by hand on the tape server to the tape drive, read it back, and confirm
that it's OK. If it doesn't work, then troubleshoot the hardware -- tape
drive, tapes, SCSI cables, SCSI chain, termination, color of goat. Are
you getting any errors in the logs?
Remember that amanda is, really, "just" a backup organizer. All backups
are actually done by system utilities (dump or tar) and the various device
drivers.
> 1. /sbin/dump is making mistakes. I'm currently testing Gnu Tar with a clean
> slate.
Possibly, but my first suspicion is hardware -- probably the tape drive
since backups from both clients are failing (otherwise I'd also suspect a
hard drive).
> 2. My tape definition is incorrect for my drive? Maybe. I'm using a Sony
> DDS-3 125 m (12 gig uncompresseD) tape, and I'm using hte following
> definition which I took from the mailing list
>
> define tapetype SDT-9000 {
> comment "Sony SDT-9000 DDS-3 DAT drive"
> length 12288 mbytes # 12GB native for 125 m tapes
> filemark 0 kbytes
> speed 1200 kbytes # kb/s sustained rate, compression disabled
> }
No -- that's fine. About the only thing amanda really uses there is the
length parameter, in order to do estimates.
> 3. Maybe the permissions on /var/lib/DailySet1/curinfo and index, are
> incorrect? Don't know. I've got amanda.amanda drwxr-sr-x for both dirs
I don't have the setgid bit. But this wouldn't cause the errors above.
> 4. amcheck was complaining that subdirectories in those two above (like
> _var, _home) didn't exist. But it said it would create them, so I figured
> I'd let it
Good choice.
Check your hardware.
--
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University
