>Ok I will do this and if I remember correctly we can't run 2 amdumps in
>one day - right - it isn't recommended right? ...
It's a problem for you because you're not flushing to tape. Amanda would
overwrite the images it has already saved in the holding disk.
>And I do run it a
>second time the amdump.xx log numbers will increment.
Correct. So will the log.YYYYMMDD.nn files.
>So I will unset this force flag on sda10 and let her run again tomorrow
>am? Anyway I can dump 'only' sda10 right now?
Temporarily edit the disklist to comment everything but that entry out,
make the run then put things back to normal. As long as you are certain
it's the only entry in disklist, and there is no holding disk entry for
today for this disk, you can do the run now since it won't overwrite
anything.
>I also noticed that there was
>no .log file generated this time around and amanda didn't tell me to run
>amcleanup.
That's good. Something really bad happened on the 9th. The first thing
I'd do is run "uptime" and see how long the system has been up. If it
wasn't rebooted, I'd start looking at system log files, in particular
for a full file system or quota problem.
>Denise E. Ives
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
