>Can anyone tell me what log/debug files to look in to find out why I >keep getting the MISSING errors below, and what I should be looking for?
Start with amdump.1 (the most recent amdump log file). It has a very detailed log of everything that went on during the run. Pick one of your clients and disks to look for (I'd use "idebigger" since it's unique). For the following I just grep'd amdump.1 for "[/_]data", which happens to be a unique file system in one of my configs (I also left out a couple of lines of no interest). In general you should see a sequence of events something like this (mixed in with all the other activity): # grep '[/_]data' amdump.1 setting up estimates for fortress.cc.purdue.edu:/data got result for host fortress.cc.purdue.edu disk /data: 0 -> 3349550K, 5 -> 2722448K, 6 -> 2717312K fortress.cc.purdue.edu /data 1 5 2002:4:6:7:59:19 2722448 1995 driver: send-cmd time 1261.520 to dumper4: FILE-DUMP 04-00005 /amanda/RCD/20020409/fortress.cc.purdue.edu._data.5 fortress.cc.purdue.edu /data 5 2002:4:6:7:59:19 2048000 DUMP 2722560 |;bsd-auth;index; driver: finished-cmd time 4526.310 dumper4 dumped fortress.cc.purdue.edu:/data driver: send-cmd time 8077.002 to taper: FILE-WRITE 00-00689 /amanda/RCD/20020409/fortress.cc.purdue.edu._data.5 fortress.cc.purdue.edu /data 5 20020409 driver: finished-cmd time 8953.699 taper wrote fortress.cc.purdue.edu:/data The first two lines are planner getting the estimate. The next line is the schedule for driver. The next two lines are driver telling dumper4 to do the backup into the holding disk (FILE-DUMP). The last two lines are taper writing it to tape. The sequence is slightly different if the file system goes direct to tape. >Dick John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
