Here's a little more info from the report.

FAILURE AND STRANGE DUMP SUMMARY:
  planner: ERROR BS1NAK :  amandad busy
  BS1        //ADS1/AMRightFax RESULTS MISSING

NOTES:
  planner: Adding new disk hsp-db:/db/backup/hsp.
  planner: Adding new disk BS1://ADS1/AMRightFax.

DUMP SUMMARY:
                                     DUMPER STATS            TAPER STATS
HOSTNAME     DISK        L ORIG-KB OUT-KB COMP% MMM:SS  KB/s MMM:SS  KB/s
-------------------------- --------------------------------- ------------
BS1          -AMRightFax   MISSING --------------------------------------
data         /db/backup  1 10915001069824  98.0   3:045822.0   9:131934.0
fs1          /data       2   82130  37312  45.4   0:45 827.0   0:211798.9
fs1          /home       4   17120   4000  23.4   0:08 494.2   0:04 929.3
hope         /db/backup  1  699530 691232  98.8   2:404313.4   5:571937.8
hsp-db       -backup/hsp 0  392710 392768   --    0:3610988.9   3:241929.9
localhost    /dev/hdb3   1   75640  38016  50.3   0:241573.8   0:211838.1
localhost    /etc        1     360    416   --    0:003704.5   0:05  87.4

Is Amanda confused about the server name? There is a note about NAKs when a
host is referred to by different names. I'm backing up the local machine
using the "localhost" name. I'll try changing that to BS1.

-----Original Message-----
From: Joshua Baker-LePain [mailto:jlb17 AT duke DOT edu]
Sent: Wednesday, February 12, 2003 11:06 AM
To: Bill Hults
Cc: Amanda List
Subject: Re: Backing up Windows shares


On Wed, 12 Feb 2003 at 10:10am, Bill Hults wrote

> planner: time 0.113: setting up estimates for BS1://ADS1/AMRightFax
> BS1://ADS1/AMRightFax overdue 12095 days for level 0
> setup_estimate: BS1://ADS1/AMRightFax: command 0, options:
>     last_level -1 next_level0 -12095 level_days 0
>     getting estimates 0 (0) -1 (-1) -1 (-1)

That's obviously a bad estimate.

> INFO planner Adding new disk hsp-db:/db/backup/hsp.
> INFO planner Adding new disk BS1://ADS1/AMRightFax.
> ERROR planner BS1NAK :  amandad busy

That's bad as well.

> There is a line in /tmp/amanda/amtrmidx about not being able to open the
> directory the index was in. The directory wasn't created presumable since
it
> didn't do a backup of the share.
> That seems to be the only pertinent message in /tmp/amanda.
> Anyone have any ideas as to what might be causing this behavior?

What does amcheck have to say about your config?  On BS1 (which I'm
assuming is the Linux samba host), do you see stale, leftover amanda
processes?

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

This e-mail was scanned by RAV Antivirus. (www.ravantivirus.com)

This e-mail was scanned by RAV Antivirus. (www.ravantivirus.com)