When I upgraded one of my servers to Amanda 3.5.1, I had to run amdump from a script (out of cron),
because . . .
Now it doesn't send out an email report when it is finished.
What is my workaround? I've looked through the amdump and amanda man pages. I don't see an option to
tell it, "please DO send an email report." I also did check all the various places that might hint
at an email getting hung up, but didn't find any evidence in any of the logs or spool directories
that any had ever been sent.
The reason I'm running it out of a script instead just a straight call from the crontab line is that
3.5.1 will now run more than one instance of amanda in parallel, and this server can't handle that.
So, I have a script now that checks to see if amanda is already running before launching a new run.
That script is called from cron. I have another server that manages just fine with Amanda 3.5.1's
behavior, because it has a tape library with two LTO7 drives and also with a pair of 4TB server
grade SSDs for holding disk space.
--
---------------
Chris Hoogendyk
-
O__ ---- Systems Administrator
c/ /'_ --- Biology & Geosciences Departments
(*) \(*) -- 315 Morrill Science Center
~~~~~~~~~~ - University of Massachusetts, Amherst
<[email protected]>
---------------
Erdös 4
