On Thu, Sep 23, 2010 at 2:20 PM, Stefan G. Weichinger wrote:
> I would like to see it in my smaller installations as well, where there
> is no changer ...
Well, there's always a changer, but some of them (like chg-manual and
chg-single) do not support ejecting. That might be a good thing to
fix.
Am 23.09.2010 21:16, schrieb Dustin J. Mitchell:
> On Thu, Sep 23, 2010 at 1:28 PM, Stefan G. Weichinger wrote:
>> A flag to set in amanda.conf to force an "mt -f $tapedev offl" after
>> successful amdump/amflush ...
>
> This has been a standing bug in Zmanda's bugzilla for a while, but
> it's ne
On Thu, Sep 23, 2010 at 1:28 PM, Stefan G. Weichinger wrote:
> A flag to set in amanda.conf to force an "mt -f $tapedev offl" after
> successful amdump/amflush ...
This has been a standing bug in Zmanda's bugzilla for a while, but
it's never become clear where this should happen. Changers alread
Am 09.09.2010 17:55, schrieb Dustin J. Mitchell:
> I bet most of you have some small nitpick with Amanda that you've
> never felt warranted an email. Well, now's your chance! I'd like to
> put some polish on Amanda, and it's hard for me to see the areas that
> need burnishing, since I work on Ama
This may be a little late, but it would be nice to have a switch on
most status, etc. utils to format the output for texting to a mobile
device rather than email.
According to Verizon's website, the 160 char limit on text messages is
as follows:
The 160 character limit includes the sender's email
On 9/21/10 2:42 PM, Dustin J. Mitchell wrote:
On Tue, Sep 21, 2010 at 1:26 PM, Chris Nighswonger
wrote:
This may be a little late, but it would be nice to have a switch on
most status, etc. utils to format the output for texting to a mobile
device rather than email.
Almost the exact same th
On Tue, Sep 21, 2010 at 1:26 PM, Chris Nighswonger
wrote:
> This may be a little late, but it would be nice to have a switch on
> most status, etc. utils to format the output for texting to a mobile
> device rather than email.
Almost the exact same thing was requested earlier by Douglas K. Rand.
On 9/17/10 4:40 PM, Dustin J. Mitchell wrote:
On Fri, Sep 17, 2010 at 2:59 PM, Stefan G. Weichinger wrote:
And as a bonus: the possibility to get these warnings to another
mail-address than the usual reports.
There have been a number of notification-related nitpicks so far.
While they&#x
On Fri, Sep 17, 2010 at 2:59 PM, Stefan G. Weichinger wrote:
> And as a bonus: the possibility to get these warnings to another
> mail-address than the usual reports.
There have been a number of notification-related nitpicks so far.
While they're good ideas, I don't want
Am 09.09.2010 17:55, schrieb Dustin J. Mitchell:
> I bet most of you have some small nitpick with Amanda that you've
> never felt warranted an email. Well, now's your chance! I'd like to
> put some polish on Amanda, and it's hard for me to see the areas that
> need burnishing, since I work on Ama
JL,
On Tue, Sep 14, 2010 at 05:20:05PM -0400, Jon LaBadie wrote:
> On Tue, Sep 14, 2010 at 12:30:19PM -0500, Dustin J. Mitchell wrote:
> >
> > One note: we already have "diskname" and "device" in a DLE, where
> > "device" is what's actually backed up, and "diskname" is the name used
> > to refer
On Tue, Sep 14, 2010 at 12:30:19PM -0500, Dustin J. Mitchell wrote:
>
> One note: we already have "diskname" and "device" in a DLE, where
> "device" is what's actually backed up, and "diskname" is the name used
> to refer to it. So, for example, a disklist
>
> foohost /home
>
> could be renamed
On Tue, Sep 14, 2010 at 10:32:55AM -0600, Charles Curley wrote:
> On Tue, 14 Sep 2010 09:21:47 -0400
> Brian Cuttler wrote:
>
> > On Mon, Sep 13, 2010 at 07:37:52PM -0600, John Hein wrote:
> > > Chris Lee wrote at 22:23 +0100 on Sep 13, 2010:
> > > > The way I see it the DLE is for the admin t
These are some exciting ideas, so far!
I'd love to see some of this fleshed out in code, even if that's not
Amanda code -- an example of a catalog with fake dump and recover
operations that demonstrates how all of this would fit together. With
that in place, we can settle on a particular structur
On Tue, 14 Sep 2010 09:21:47 -0400
Brian Cuttler wrote:
> On Mon, Sep 13, 2010 at 07:37:52PM -0600, John Hein wrote:
> > Chris Lee wrote at 22:23 +0100 on Sep 13, 2010:
> > > The way I see it the DLE is for the admin to make sub divisions
> > > in the backup to make backing up easier to manage.
On Mon, Sep 13, 2010 at 07:37:52PM -0600, John Hein wrote:
> Chris Lee wrote at 22:23 +0100 on Sep 13, 2010:
> > The way I see it the DLE is for the admin to make sub divisions in
> > the backup to make backing up easier to manage. The software should
> > store the file object with path and host
Am 13.09.2010 21:09, schrieb Dustin J. Mitchell:
> As you can see, complicated. But a consistent approach to storing the
> DLE and path of a particular "user object" over time would be a useful
> first step. Do you have any thoughts on how that might be
> implemented?
Remember my script generat
Dustin J. Mitchell wrote at 14:56 -0500 on Sep 13, 2010:
> On Mon, Sep 13, 2010 at 2:43 PM, Brian Cuttler wrote:
> > Virtual DLEs !?!
> >
> > That is EXACTLY what we need !
> >
> > I know you warned us, but I'm REALLY Excited about this !
> >
> > That would _so_ fix my Terrabyte sized DLE
Chris Lee wrote at 22:23 +0100 on Sep 13, 2010:
> The way I see it the DLE is for the admin to make sub divisions in
> the backup to make backing up easier to manage. The software should
> store the file object with path and hostname, with the DLE as an
> after thought; that way for the other d
Dustin J. Mitchell wrote at 14:09 -0500 on Sep 13, 2010:
> On Sun, Sep 12, 2010 at 9:36 PM, John Hein wrote:
> > This may not be considered a nitpick but more of a feature request.
> >
> > If I move a disk or rename a host or move the host to a different
> > domain, it'd be nice to be able to
Dustin J. Mitchell wrote:
On Sun, Sep 12, 2010 at 9:36 PM, John Hein wrote:
This may not be considered a nitpick but more of a feature request.
If I move a disk or rename a host or move the host to a different
domain, it'd be nice to be able to rename the disklist entry (DLE) and
have his
On Mon, Sep 13, 2010 at 02:56:28PM -0500, Dustin J. Mitchell wrote:
> On Mon, Sep 13, 2010 at 2:43 PM, Brian Cuttler wrote:
> > Virtual DLEs !?!
> >
> > That is EXACTLY what we need !
> >
> > I know you warned us, but I'm REALLY Excited about this !
> >
> > That would _so_ fix my Terrabyte sized D
Virtual DLEs !?!
That is EXACTLY what we need !
I know you warned us, but I'm REALLY Excited about this !
That would _so_ fix my Terrabyte sized DLE problem...
On Mon, Sep 13, 2010 at 02:09:16PM -0500, Dustin J. Mitchell wrote:
> On Sun, Sep 12, 2010 at 9:36 PM, John Hein wrote:
> > This may
I'm sorry to sound pedantic here, but I think this is a case where we
can only fix it by looking at specific problems. Amcheck is pretty
careful to give as many error messages as possible in each run, rather
than simply bailing out after the first, so if there's a case where
this does not happen,
On Mon, Sep 13, 2010 at 2:43 PM, Brian Cuttler wrote:
> Virtual DLEs !?!
>
> That is EXACTLY what we need !
>
> I know you warned us, but I'm REALLY Excited about this !
>
> That would _so_ fix my Terrabyte sized DLE problem...
Yes, yes it would. It would fix a lot of problems!
I don't think it
On Mon, Sep 13, 2010 at 8:15 AM, Stefan G. Weichinger wrote:
> As mentioned some time ago I would luv a separate
> "mailto-human-tape-changer" ;-)
So Douglas is describing a "mobile-friendly" amcheck mail, while
you're requesting a "next-tape-only" amreport mail. I imagine you'd
also like a more
On Sun, Sep 12, 2010 at 9:36 PM, John Hein wrote:
> This may not be considered a nitpick but more of a feature request.
>
> If I move a disk or rename a host or move the host to a different
> domain, it'd be nice to be able to rename the disklist entry (DLE) and
> have history tracking, incrementa
On Sat, Sep 11, 2010 at 7:56 PM, Jon LaBadie wrote:
> So, I wonder if there is any way to backup a COD (Client On Demand)?
> I envision a request from the client would start a dump to holding
> disk which would require 'autoflush' for the taping to occur later.
> Consideration would also have to b
Hi Dustin,
A script-tool application for running script taking parameters such as path to
script, PFEXEC or SUDO and when to run etc
define script-tool amplugin-script {
plugin "amplugin-script"
property "script" "path to script to run"
property PFEXEC" "YES"
property "SUDO" "no"
execute-on pre
Am 12.09.2010 22:17, schrieb Douglas K. Rand:
> We send the result of "amcheck -m" to our pagers, and I've always
> wanted a problem only option for amcheck so that all of the output was
> related to the problems, and everything that was OK would be
> quiet.
As mentioned some time ago I would luv
> On Sat, Sep 11, 2010 at 10:42 PM, Lisa Seelye wrote:
>
>> Disk permissions and file permissions are always a nightmare. Some
>> things aren't right and amcheck complains about each one in turn. It
>> would be useful to have some kind of thorough "lint" mode, perhaps with
>> a --fix-permissions
On 2010-09-12 17:25, Dustin J. Mitchell wrote:
On Sat, Sep 11, 2010 at 10:42 PM, Lisa Seelye wrote:
Disk permissions and file permissions are always a nightmare. Some things
aren't right and amcheck complains about each one in turn. It would be
useful to have some kind of thorough "lint" mode,
Dustin J. Mitchell wrote at 10:55 -0500 on Sep 9, 2010:
> I bet most of you have some small nitpick with Amanda that you've
> never felt warranted an email. Well, now's your chance! I'd like to
> put some polish on Amanda, and it's hard for me to see the areas that
> need burnishing, since I
We send the result of "amcheck -m" to our pagers, and I've always
wanted a problem only option for amcheck so that all of the output was
related to the problems, and everything that was OK would be
quiet. And, of course, if there are no problems it is completely
silent like -m does. The pages get t
On Sat, Sep 11, 2010 at 10:42 PM, Lisa Seelye wrote:
> Disk permissions and file permissions are always a nightmare. Some things
> aren't right and amcheck complains about each one in turn. It would be
> useful to have some kind of thorough "lint" mode, perhaps with a
> --fix-permissions to repair
> I bet most of you have some small nitpick with Amanda that you've
> never felt warranted an email. Well, now's your chance! I'd like to put
> some polish on Amanda, and it's hard for me to see the areas that need
> burnishing, since I work on Amanda all day, every day.
>
> - typo in a manpage?
On Thu, Sep 09, 2010 at 10:55:55AM -0500, Dustin J. Mitchell wrote:
> I bet most of you have some small nitpick with Amanda that you've
> never felt warranted an email. Well, now's your chance! I'd like to
> put some polish on Amanda, and it's hard for me to see the areas that
> need burnishing,
I bet most of you have some small nitpick with Amanda that you've
never felt warranted an email. Well, now's your chance! I'd like to
put some polish on Amanda, and it's hard for me to see the areas that
need burnishing, since I work on Amanda all day, every day.
- typo in a manpage?
- command
rote:
> >Hello,
> >
> >I've been testing 2.5.1 for a few days now and I have 2 nitpicks:
> >
> >With 2.4.5 'amtoc -a' produces outputfile with names
> >.toc as per the man page. This doesn't seem to be the
> >case anymore with 2.5.1 where I
Jean-Francois,
Could you try this patch?
Jean-Louis
Jean-Francois Malouin wrote:
Hello,
I've been testing 2.5.1 for a few days now and I have 2 nitpicks:
With 2.4.5 'amtoc -a' produces outputfile with names
.toc as per the man page. This doesn't seem to be the
case anym
Hello,
I've been testing 2.5.1 for a few days now and I have 2 nitpicks:
With 2.4.5 'amtoc -a' produces outputfile with names
.toc as per the man page. This doesn't seem to be the
case anymore with 2.5.1 where I just get a file called "tape.toc". And
in the situ
41 matches
Mail list logo
