Re: feature request: overdue-warning in reports

> On Sep 20, 2016, at 3:57 PM, Stefan G. Weichinger wrote: > > Am 2016-09-20 um 18:27 schrieb Debra S Baddorf: >> In the meanwhile, you could have a cron job on each server do the line listed >> below …. rather than you logging in each day. >> >> Just a suggestion! You may

Re: feature request: overdue-warning in reports

Am 2016-09-20 um 18:27 schrieb Debra S Baddorf: > In the meanwhile, you could have a cron job on each server do the line listed > below …. rather than you logging in each day. > > Just a suggestion! You may already be doing that. Thanks, Deb, sure, a possible workaround for now. But this

feature request: overdue-warning in reports

To be able to monitor my multiple amanda-installations more quickly I would like to have an extra line in the email reports: each DLE that is overdue for more than X days (this could become a parameter in amanda.conf) should be listed something like: WARNING: DLE some_data is overdue for X days

Re: Another feature request

Am 24.07.2014 um 09:44 schrieb Stefan G. Weichinger: It would be great to have amanda test for DLEs being overdue more than X days and email/warn me. Might be scripted with amadamin conf due, right, but I assume it would be better to add it as a feature either to amcheck (run at a specific

Another feature request

It would be great to have amanda test for DLEs being overdue more than X days and email/warn me. Might be scripted with amadamin conf due, right, but I assume it would be better to add it as a feature either to amcheck (run at a specific time via cron) or amdump (run after the backups). This

Re: feature request: mt offl after amdump

Am 03.07.2014 14:33, schrieb Stefan G. Weichinger: Am 03.07.2014 14:27, schrieb Jean-Louis Martineau: Stefan, If you have 3.3.5 $ man amanda.conf eject-volume bool Default: no. Set to yes if you want the volume to be ejected after Amanda wrote data to it. It

Re: feature request: mt offl after amdump

Am 03.07.2014 14:52, schrieb Jean-Louis Martineau: Read download.php, it tell how to use svn or git. Follow the link for the development branch in the table, it tell you how to checkout. ... sorry, my fault, didn't scroll enough. Thanks, Stefan

Re: feature request: mt offl after amdump

Am 02.07.2014 22:12, schrieb Stefan G. Weichinger: Am 02.07.2014 22:10, schrieb Jean-Louis Martineau: Better news, it's already in 3.3.1 Check for the eject-volume setting. pardon? I have 3.3.5 here already. Looking fwd! JL, pls provide me what to checkout with svn. I can't find latest

Re: feature request: mt offl after amdump

Stefan, If you have 3.3.5 $ man amanda.conf eject-volume bool Default: no. Set to yes if you want the volume to be ejected after Amanda wrote data to it. It works only with some changer and device. Add the following to amanda.conf: eject-volume yes

Re: feature request: mt offl after amdump

Am 03.07.2014 14:27, schrieb Jean-Louis Martineau: Stefan, If you have 3.3.5 $ man amanda.conf eject-volume bool Default: no. Set to yes if you want the volume to be ejected after Amanda wrote data to it. It works only with some changer and

Re: feature request: mt offl after amdump

On 07/03/2014 08:33 AM, Stefan G. Weichinger wrote: Am 03.07.2014 14:27, schrieb Jean-Louis Martineau: Stefan, If you have 3.3.5 $ man amanda.conf eject-volume bool Default: no. Set to yes if you want the volume to be ejected after Amanda wrote data to it. It

Re: feature request: mt offl after amdump

Am 29.06.2014 23:27, schrieb Stefan G. Weichinger: I am currently rewriting my cronjobs to systemd-units and -timers ... and I do that as well for the daily run of amdump. Works fine so far. my question: It is rather easy to do a mt -f /dev/st0 offl after a successful amdump, if

Re: feature request: mt offl after amdump

Stefan, This feature is already committed for the next major release (3.4). Jean-Louis On 06/29/2014 05:27 PM, Stefan G. Weichinger wrote: I am currently rewriting my cronjobs to systemd-units and -timers ... and I do that as well for the daily run of amdump. Works fine so far. my question:

Re: feature request: mt offl after amdump

Am 02.07.2014 21:56, schrieb Jean-Louis Martineau: Stefan, This feature is already committed for the next major release (3.4). Wow, I love to hear that! I assume you could provide a link to the commit? I'd like to see what you implemented (and maybe comment on that :-) ). Thanks, regards,

Re: feature request: mt offl after amdump

Better news, it's already in 3.3.1 Check for the eject-volume setting. Jean-Louis On 07/02/2014 03:58 PM, Stefan G. Weichinger wrote: Am 02.07.2014 21:56, schrieb Jean-Louis Martineau: Stefan, This feature is already committed for the next major release (3.4). Wow, I love to hear that! I

Re: feature request: mt offl after amdump

Am 02.07.2014 22:10, schrieb Jean-Louis Martineau: Better news, it's already in 3.3.1 Check for the eject-volume setting. pardon? I have 3.3.5 here already. Looking fwd!

feature request: mt offl after amdump

I am currently rewriting my cronjobs to systemd-units and -timers ... and I do that as well for the daily run of amdump. Works fine so far. my question: It is rather easy to do a mt -f /dev/st0 offl after a successful amdump, if there is only one tape-device. I currently use 2 LTO-2 drives

feature request

My version of amanda is a little older, but I don't believe I've seen anything on rejecting a DLE because of size. I have a user that just grew their directory/files and is now sitting on close to 2 TBytes of data. Amanda discovered this, determined it didn't have sufficient work area and began

another wish / feature request

What about some integration of amcleanup and amdump ? I imagine a parameter definining the time of day the amdump should be finished (= the servers are available and idle for users ...). When amdump is running and somehow noticing that the current dumps will take more time than until XX:YYam it

Another nitpick / feature request

When a large DLE doesn't tape all the split parts before running out of tapes, could the subsequent flush (amflush or autoflush) pick up where the original taping left off? I just had a large DLE (23 3GB parts) fail on the last part by just 800MB. On the subsequent amdump the DLE autoflushed the

Re: Another nitpick / feature request

On Sat, Sep 18, 2010 at 9:44 AM, Jon LaBadie j...@jgcomp.com wrote: When a large DLE doesn't tape all the split parts before running out of tapes, could the subsequent flush (amflush or autoflush) pick up where the original taping left off? I just had a large DLE (23 3GB parts) fail on the

Re: Another nitpick / feature request

On Sat, Sep 18, 2010 at 10:37:48AM -0500, Dustin J. Mitchell wrote: On Sat, Sep 18, 2010 at 9:44 AM, Jon LaBadie j...@jgcomp.com wrote: When a large DLE doesn't tape all the split parts before running out of tapes, could the subsequent flush (amflush or autoflush) pick up where the

Re: Another nitpick / feature request

On Sat, Sep 18, 2010 at 2:17 PM, Jon LaBadie j...@jgcomp.com wrote: I'll certainly defer to you knowledge of the difficulty.  I was thinking that the logic is already there for the split disk feature.  The added code would be for saving its state and recreating it on the next flush. Yes, that

Re: feature request : infos about holdingdisk-content

Dustin J. Mitchell schrieb: On Wed, May 30, 2007 at 12:54:51AM +0200, Stefan G. Weichinger wrote: Is that documented somewhere? Only in the manpages at the moment. It's on my wiki todo list. Ok, just checked that ... IMO there should be a special howto related to the topic holdingdisk in

Re: feature request : infos about holdingdisk-content

Stefan G. Weichinger schrieb: -- Stefan G. Weichinger amanda core team member mailto: [EMAIL PROTECTED] pgp: 3C64175D -- Stefan G. Weichinger amanda core team member mailto: [EMAIL PROTECTED] pgp: 3C64175D -- [..] I apologize again for using this *stupid*

feature request : infos about holdingdisk-content

Greets, another wish ... Could we have (amanda.conf-parameter-switchable) informations about the holdingdisk-content in the amanda-reports? For example: Instead of: Some dumps may have been left in the holding disk. Run amflush again to flush them to tape. there could be: Dumps left in

Re: feature request : infos about holdingdisk-content

Stefan -- The new 'amadmin holding list' command gives that sort of result. If you run, e.g., amadmin DailySet1 holding list -l It will give you a detailed listing; an example from my development box: size (kB) lv dump specification 1720 knuth /tmp/amanda/prefix/etc 20070529 62

Re: feature request : infos about holdingdisk-content

Dustin J. Mitchell schrieb: Stefan -- The new 'amadmin holding list' command gives that sort of result. If you run, e.g., amadmin DailySet1 holding list -l It will give you a detailed listing; an example from my development box: size (kB) lv dump specification 1720

Re: feature request : infos about holdingdisk-content

On Wed, May 30, 2007 at 12:54:51AM +0200, Stefan G. Weichinger wrote: Is that documented somewhere? Only in the manpages at the moment. It's on my wiki todo list. When was it added? 2.5.2. Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc.

Re: feature request : slots into reports

Stefan G. Weichinger schrieb: Greets, amanda-users, Quite a stupid signature-function used sorry for the multiple sigs and the noise generated -- Stefan

feature request : slots into reports

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Greets, amanda-users, I'd like to suggest a small addition which I think might be helpful, not only for me. I would like to have the slots of my changer listed in the amanda-report-mail. Right now it is: USAGE BY TAPE: Label Time Size

Feature request: Timeouts for amverify

Hi, Coming back to work after Easter holidays I found a small annoyance with amverify: Our cron backup skript basically does amdump; mt status; amverify; mt offline; After inserting the last tape on thursday all backups went to holding disk as planned. Inserting the next tape for amflush