Re: amanda overwrites level0 without warning
Hello, Dave Sherohman <[EMAIL PROTECTED]> writes: > Sending an advance notice ok for this. >> [interactive prompt] > IMO, no. I thougth of an interactive prompt with a timeout (after posting to be honest). Imagine a scenario like this: i am an admin or a cron job . In 3 dumps the unique level0 of the tapecycle will be overwriten. I do this amdump ( 2 dumps before overwrite) Admin receive a warning AND a level0 is planned for the next dump ( 1 dump before overwrite). should it be implemented like this ? I wonder if detecting abnormal operation (with a "max_runs_per_day" in amanda.conf for example) should be usefull and, if yes, what kind of action(s) amanda should take. Anyway, time for me to look at this planner. May the source be with me :o) Bye.
Re: amanda overwrites level0 without warning
--On Thursday, April 11, 2002 03:37:15 +0200 Frederic Saincy <[EMAIL PROTECTED]> wrote: > Hi, > > Frank Smith <[EMAIL PROTECTED]> writes: > >> The planner logic might not be set >> up to handle this extreme case. > > I don't know very well amanda's internal and this is the occasion for > me to look at the sources. If the planner can't, amdump must wonder: > "If i do this, can admin restore the system ?". > > If not, there is 2 solutions in an environment without tape changer: > > 1) do nothing > 2) do a level0. > > I imagine all prefers the second solution. > > I gonna look at this "extreme case" further: i did it as a test, but > imagine, for example, a bad written /etc/cronttab and the > The_Big_Problem (r) once level0 was overwritten. Too bad. > > Bye. Even if it gave the warning it would do no good if it ran enough times before you read the daily reports, as the warnings won't stop it from overwriting the tape. If you aren't using a changer just append an mt offline command to your amdump command in cron and then Amanda can't overwrite a tape without your assistance. Once you get Amanda doing some real work it will probably become impossible to run through your entire set of tapes in a day, since Amanda won't run again if it is still running from the run before, and all the planners and dumpers take some time to complete. Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: amanda overwrites level0 without warning
Hello, Dave Sherohman <[EMAIL PROTECTED]> writes: > Sending an advance notice ok for this. >> [interactive prompt] > IMO, no. I thougth of an interactive prompt with a timeout (after posting to be honest). Imagine a scenario like this: i am an admin or a cron job . In 3 dumps the unique level0 of the tapecycle will be overwriten. I do this amdump ( 2 dumps before overwrite) Admin receive a warning AND a level0 is planned for the next dump ( 1 dump before overwrite). should it be implemented like this ? I wonder if detecting abnormal operation (with a "max_runs_per_day" in amanda.conf for example) should be usefull and, if yes, what kind of action(s) amanda should take. Anyway, time for me to look at this planner. May the source be with me :o) Bye.
Re: amanda overwrites level0 without warning
On Thu, Apr 11, 2002 at 01:05:38PM +0200, Frederic Saincy wrote: > Detect the first abnormal dump, then mail a warning and stop to back > up this tapecycle ? I don't know that amanda can reasonably do much more than sending an advance notice[1] (Warning: Last level 0 dump of /dev/foo will be overwritten in 2 runs) and trying to shoehorn in a fresh level 0 before the old one gets overwritten. > Does the second dump for a tapecycle in a day can be considered as > "abnormal" ? Not necessarily. If, for example, runspercycle > dumpcycle, then there has to be at least one day per cycle when multiple runs are normal. It's even normal if runspercycle = dumpcycle, but dumps aren't run on weekends. > Does an interactive prompt for amdump would fit for this case ? > > for example: > > "Amanda detects an abnormal dumps [big warning] do you *really* know > what your are doing [y/n]?" IMO, no. Interactive prompts as a part of normal operation (i.e., other than in amflush or amlabel) would be Bad, as they require manual intervention to continue. Not good in a cron job, plus it contradicts the software's apparent intent (the second A in amAnda stands for Automatic). If you really want to do this, it should be controlled by a switch in amanda.conf (userisanidiot yes) so that those who do know what they're doing don't have to worry about 42 filesystems not getting backed up by cron just because one machine's purely-vendor-supplied /usr is about to lose its last level 0. [1] ISTR that it already does this
Re: amanda overwrites level0 without warning
Hi, Was sleepy yesterday. Doing a level0 does not fit, so, for all case, with or without tape changer / holdingdisk / tape drive (tapeio) what can be "the" good solution ? Detect the first abnormal dump, then mail a warning and stop to back up this tapecycle ? Does the second dump for a tapecycle in a day can be considered as "abnormal" ? Does an interactive prompt for amdump would fit for this case ? for example: "Amanda detects an abnormal dumps [big warning] do you *really* know what your are doing [y/n]?" Bye.
Re: amanda overwrites level0 without warning
--On Thursday, April 11, 2002 03:37:15 +0200 Frederic Saincy <[EMAIL PROTECTED]> wrote: > Hi, > > Frank Smith <[EMAIL PROTECTED]> writes: > >> The planner logic might not be set >> up to handle this extreme case. > > I don't know very well amanda's internal and this is the occasion for > me to look at the sources. If the planner can't, amdump must wonder: > "If i do this, can admin restore the system ?". > > If not, there is 2 solutions in an environment without tape changer: > > 1) do nothing > 2) do a level0. > > I imagine all prefers the second solution. > > I gonna look at this "extreme case" further: i did it as a test, but > imagine, for example, a bad written /etc/cronttab and the > The_Big_Problem (r) once level0 was overwritten. Too bad. > > Bye. Even if it gave the warning it would do no good if it ran enough times before you read the daily reports, as the warnings won't stop it from overwriting the tape. If you aren't using a changer just append an mt offline command to your amdump command in cron and then Amanda can't overwrite a tape without your assistance. Once you get Amanda doing some real work it will probably become impossible to run through your entire set of tapes in a day, since Amanda won't run again if it is still running from the run before, and all the planners and dumpers take some time to complete. Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: amanda overwrites level0 without warning
Hi, Frank Smith <[EMAIL PROTECTED]> writes: > The planner logic might not be set > up to handle this extreme case. I don't know very well amanda's internal and this is the occasion for me to look at the sources. If the planner can't, amdump must wonder: "If i do this, can admin restore the system ?". If not, there is 2 solutions in an environment without tape changer: 1) do nothing 2) do a level0. I imagine all prefers the second solution. I gonna look at this "extreme case" further: i did it as a test, but imagine, for example, a bad written /etc/cronttab and the The_Big_Problem (r) once level0 was overwritten. Too bad. Bye.
