Thanks, Alex - brilliant idea - and that's how Servergraph already does it.
We give the TSM admins visibility into the status, checked daily, fo how old
the backups are.
So they need not care about schedules - just whether things are current or
not.

The really great side benefit from this is finding wasted space.
That is, if a filespace ahs not backed up in 90 days, does it still exist?
Probably not, except on TSM tapes.  Delete it.

We had one customer free up 4 TB of defunct filespaces.  Anybody who's short
on library space
should check for that one way or another.
(IMHO)

-----------------------------
Mr. Lindsay Morris
Lead Architect
www.servergraph.com
512-482-6138 ext 105

> -----Original Message-----
> From: Alex Paschal [mailto:AlexPaschal AT Freightliner DOT com]
> Sent: Friday, June 20, 2003 12:25 PM
> To: 'adsm-l AT vm.marist DOT edu'; 'lmorris AT servergraph DOT com'
> Subject: RE: Schedule for the last day of the month...every month
>
>
> Hi, Lindsay.
>
> I would suggest also monitoring backup status using a select statement to
> pull out filespaces that didn't complete backup within x amount of time,
> even if you use the TSM scheduler.  This is useable with autosys.  Also,
> autosys scripts can report based on RC, and since we now have meaningful
> RC's from the client, that probably provides autosys reasonable
> success/failure notification.  My autosys controlled backups email me on
> failure, but I'm using scripts to parse the dsmc output for some weird
> things, rather than using the dsmc RC.
>
> The problem we run into is that our TSM admins don't have visibility into
> the Autosys schedules for load balancing purposes.  I'm still trying to
> figure that one out.  Maybe a weekly autosys report?  Hmm...
>
> Alex Paschal
> Freightliner, LLC
> (503) 745-6850 phone/vmail
>
>
> -----Original Message-----
> From: Mr. Lindsay Morris [mailto:lmorris AT SERVERGRAPH DOT COM]
> Sent: Friday, June 20, 2003 12:25 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Schedule for the last day of the month...every month
>
>
> Curtis, if I may ask: how can you monitor backup status (ie success or
> failure of all your nodes) if you use autosys?
>
> -----------------------------
> Mr. Lindsay Morris
> Lead Architect
> www.servergraph.com
> 512-482-6138 ext 105
>
> > -----Original Message-----
> > From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf 
> > Of
> > Curtis Stewart
> > Sent: Thursday, June 19, 2003 11:10 PM
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: Re: Schedule for the last day of the month...every month
> >
> >
> > We've just decided to get rid of the whole TSM scheduler for the most
> > part and go with an external schedular for TSM backups (AutoSys). It
> > fixes the whole "last day of the month, or quarter or whatever" problem
> > easily. It also lets us quit using the TSM scheduler on our clients.
> > This may not be the right answer for you, but it looks like it's going
> > to work fine for us.
> >
> > curtis stewart
> >
> > Kent Monthei wrote:
> >
> > >You might be able to develop & schedule a little script which
> > >        a) does a 'delete schedule'
> > >        b) goes through a loop that performs a 'define
> schedule' for the
> > >31st/30th/29th/28th (in that order)
> > >        c) after each 'define schedule' attempt, checks the Return Code
> > >(or output of 'q sched')
> > >        d) exit if/when the 'define schedule' is successful.
> > >
> > >Then schedule the script to run on any of the 1st through 28th
> day of the
> > >month.
> > >
> > >Kent Monthei
> > >GlaxoSmithKline
> > >
> > >
> > >
> > >
> > >
> > >"Bill Boyer" <bill.boyer AT VERIZON DOT NET>
> > >
> > >Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> > >19-Jun-2003 13:14
> > >Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> > >
> > >
> > >
> > >
> > >        To:     ADSM-L
> > >
> > >        cc:
> > >        Subject:        Schedule for the last day of the
> > month...every month
> > >
> > >I have a client that wants to do monthly backups on the last day of the
> > >month. A co-worker did some testing and creating a schedule for say
> > >5/31/3002 with PERU=MONTH. The June event gets scheduled for 6/30, but
> > >then
> > >remains the 30th day from then on. Until Feb next year when it moves to
> > >the
> > >29th.
> > >
> > >Outside of creating a schedule for each month with a PERU=YEAR,
> > is there a
> > >way to do a schedule on the last day of every month??
> > >
> > >TIA,
> > >Bill Boyer
> > >"Some days you are the bug, some days you are the windshield." - ??
> > >
> > >
> > >
> >
>
>