Re: FW: History report?

2010-01-28 Thread stan
On Thu, Jan 28, 2010 at 10:45:35AM -0800, Paul Yeatman wrote:
> On Thu, 2010-01-28 at 12:03 -0500, stan wrote:
> > On Thu, Jan 28, 2010 at 08:17:50AM -0500, Jean-Louis Martineau wrote:
> > > Parse the output of: amadmin  find
> > > Not exactly what you want: amanda  due
> > > 
> > Jmm, this got me looking at the amadmin, so I started tryiing varios
> > options to it. When I got to balance the last line of the output told me:
> > 
> > (7 filesystems overdue. The most being overdue 34 days.)
> > 
> > Which is pretty scarey. How can I list the ones that are overdue?
> > 
> 
> That's what the "amanda  due" should show you.  You should find in
> the output 7 lines that say "Overdue ## days: :"
> 
Thanks, I was being buried in data. now I used my friend grep, and I see
it.


-- 
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?


Re: FW: History report?

2010-01-28 Thread Paul Yeatman
On Thu, 2010-01-28 at 12:03 -0500, stan wrote:
> On Thu, Jan 28, 2010 at 08:17:50AM -0500, Jean-Louis Martineau wrote:
> > Parse the output of: amadmin  find
> > Not exactly what you want: amanda  due
> > 
> Jmm, this got me looking at the amadmin, so I started tryiing varios
> options to it. When I got to balance the last line of the output told me:
> 
> (7 filesystems overdue. The most being overdue 34 days.)
> 
> Which is pretty scarey. How can I list the ones that are overdue?
> 

That's what the "amanda  due" should show you.  You should find in
the output 7 lines that say "Overdue ## days: :"

Paul




Re: FW: History report?

2010-01-28 Thread stan
On Thu, Jan 28, 2010 at 08:17:50AM -0500, Jean-Louis Martineau wrote:
> Parse the output of: amadmin  find
> Not exactly what you want: amanda  due
> 
Jmm, this got me looking at the amadmin, so I started tryiing varios
options to it. When I got to balance the last line of the output told me:

(7 filesystems overdue. The most being overdue 34 days.)

Which is pretty scarey. How can I list the ones that are overdue?

-- 
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?


Re: FW: History report?

2010-01-28 Thread stan
On Thu, Jan 28, 2010 at 08:17:50AM -0500, Jean-Louis Martineau wrote:
> Parse the output of: amadmin  find
> Not exactly what you want: amanda  due
> 
The 2nd one is really not far from what I really need. I assume it would
tell me if somethig was past due?

> 

-- 
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?


Re: FW: History report?

2010-01-28 Thread stan
On Thu, Jan 28, 2010 at 02:12:05PM +0100, Gerhard den Hollander wrote:
> * stan  (Thu, Jan 28, 2010 at 01:53:12PM +0100)
> > On Thu, Jan 28, 2010 at 10:13:08AM +0100, Uwe Menges wrote:
> > > stan wrote:
> > > > Beacuse of the ongoing problems we ar having with getting reliable 
> > > > Amanda
> > > > backups here, it has dawned on me that it would be nice to have a report
> > > > showing how old the newest level zero is for each DLE, and so on for 
> > > > wach
> > > > existant level.
> > > > 
> > > > Is there an easy way to generate this report?
> > > > 
> > > 
> > > I use "amoverview uwe -diskwidth 28 -skipmissed -num0" to get such info.
> > 
> > Hmm, well, that certainly oes presnt a lot of data :-)
> > 
> > I was hoping for a more management freindly looking repport.
> > 
> > I realize that with a day or so's effort I could probably cobble together
> > something using perl, but i was hoping to "stand on the shoulders of
> > giants". 
> 
> I use the following scripts
> 
> the first script just runs
> 
> amadmin  find 
> for all our amanda configs
> and just prints all of that to stdout
> 
> (its called amstatusall and looks like this
> 
Thaks, taht does looke useful. I will play with it.



-- 
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?


Re: FW: History report?

2010-01-28 Thread Jean-Louis Martineau

Parse the output of: amadmin  find
Not exactly what you want: amanda  due

Jean-Louis

stan wrote:

Beacuse of the ongoing problems we ar having with getting reliable Amanda
backups here, it has dawned on me that it would be nice to have a report
showing how old the newest level zero is for each DLE, and so on for wach
existant level.

Is there an easy way to generate this report?

  




Re: FW: History report?

2010-01-28 Thread stan
On Thu, Jan 28, 2010 at 10:13:08AM +0100, Uwe Menges wrote:
> stan wrote:
> > Beacuse of the ongoing problems we ar having with getting reliable Amanda
> > backups here, it has dawned on me that it would be nice to have a report
> > showing how old the newest level zero is for each DLE, and so on for wach
> > existant level.
> > 
> > Is there an easy way to generate this report?
> > 
> 
> I use "amoverview uwe -diskwidth 28 -skipmissed -num0" to get such info.

Hmm, well, that certainly oes presnt a lot of data :-)

I was hoping for a more management freindly looking repport.

I realize that with a day or so's effort I could probably cobble together
something using perl, but i was hoping to "stand on the shoulders of
giants". 

-- 
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?


Re: FW: History report?

2010-01-28 Thread Uwe Menges
stan wrote:
> Beacuse of the ongoing problems we ar having with getting reliable Amanda
> backups here, it has dawned on me that it would be nice to have a report
> showing how old the newest level zero is for each DLE, and so on for wach
> existant level.
> 
> Is there an easy way to generate this report?
> 

I use "amoverview uwe -diskwidth 28 -skipmissed -num0" to get such info.

Yours, Uwe