>> When you run amdump, are you seeing a new amandad*debug file? What
>> about a sendsize*debug file or sendbackup*debug? What's in them?
>
>hrm. on teh server side, i'm not seeing any. ...
Sorry. I should have been clearer. These files are only on the client.
>i'm wondering if i should destroy the various databases and start this
>over.
I don't think that's necessary (at least yet).
The amandad*debug file you sent is for a "selfcheck":
SERVICE selfcheck
In other words, it is related to an amcheck run (and looks normal).
The sendsize*debug file is from the estimate (planner) part of an
amdump run. It looks perfectly normal, although it would be useful to
see the corresponding amandad*debug file (the file names are date/time
stamps so it should be pretty easy to match them up).
So what happened when you ran the amdump around Thu Aug 16 21:38:02 2001?
The next place to go digging around is the amdump.<NN> file in the logdir
directory (amgetconf <config> logdir). It has a datestamp line at the
top and bottom so you can find the one that brackets the sendsize.
Skimming through it you should see planner asking the client for
estimates, getting the estimates back, deciding what to do and generating
the schedule.
After that should be driver, dumper and taper messages that do the work
(e.g. FILE-DUMP). Although it's possible that if your tape is not yet
online and the estimate is larger than a tape planner would bail out.
>-------/ f. johan beisser /--------------------------------------+
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
