You can simulate having an EVENT driven scheduler by changing the database
backup event from a straight command to a script. See, for example, the
Tivoli-supplied script BKUP_STG_DB that is shipped with the product. In the
supplied sample, they show doing a storage pool backup, followed by a
database backup, with logic to defer the whole event if there is a node in
session with the server. A few deft modifications should suit your purposes.
For example, their script starts out with
select * from sessions where -
upper(session_type)='NODE'
if (rc_ok) goto reschedule
The reschedule label then deletes a "temporary" schedule (if one exists) and
creates a onetime schedule that runs the script again, specifying a start
time of NOW+0:20. If you were to use this for "inspiration", you could
schedule the storage pool backup commands to run in the background, schedule
the database backup command / script to run at a reasonable time after they
normally complete and start the script out with something along the lines of
the following
select * from processes where -
upper(process)='BACKUP STGPOOL'
if (rc_ok) goto reschedule
Then, at the reschedule label, play the same game with rescheduling the
database backup in a temporary schedule at "some point" in the future.
(Reader beware! The syntax may not be 100% accurate. I am assuming that the
process name that is returned will indeed match the command name executed to
back up the storage pool.) I believe this should work, but, as always, I
reserve the right to be wrong.
Jack Coyle
> ----------
> From: Talafous, John G.[SMTP:Talafous AT TIMKEN DOT COM]
> Reply To: ADSM: Dist Stor Manager
> Sent: Saturday, March 24, 2001 4:39 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Admin schedule to Backup DB does not start
>
> Yes, the compelling reason is to have the backups of storage pools
> complete,
> hopefully, by 9:00AM. Then the scheduled launch of a database backup at
> 10:00AM would coincide nicely with DRM processing and the resultant
> ejection
> of tapes from an ATL.
>
> But, if clients send more data than anticipated..... Oh my! I run into
> the
> situation that the earlier ADMIN schedule does not complete soon enough.
> (I
> have changed the BACKUP_DB schedule to have an eight (8) hour startup
> window). This should help.
>
> Another reason is an attempt to keep the number of tape drives utilized by
> administrative schedules and migration tasks at an
> INSTALLATION_MAX_DRIVES-1
> to permit random client restores to have at least one drive available.
> (Note: INSTALLATION_MAX_DRIVES is a variable applicable to any situation.)
>
> Is the problem not having an EVENT driven scheduler available to TSM? (ie:
> When storage pool X drains to zero, why can't I launch a backup of storage
> pool x-tape to x-copy?) Or, can I?
>
> Thanks in advance,
> John G. Talafous IS Technical Principal
> The Timken Company Global Software Support
> P.O. Box 6927 Data Management
> 1835 Dueber Ave. S.W. Phone: (330)-471-3390
> Canton, Ohio USA 44706-0927 Fax : (330)-471-4034
> talafous AT timken DOT com http://www.timken.com
>
>
>
>
>
>
>
> -----Original Message-----
> From: Coyle, Jack [mailto:jack.coyle AT REXHEALTH DOT COM]
> Sent: Saturday, March 24, 2001 12:37 PM
> To: ADSM-L AT vm.marist DOT edu
> Subject: Re: Admin schedule to Backup DB does not start
>
>
> The issue here would seem to be the "wait=yes" option you have specified
> for
> the backup command. Doing so causes the server to process the command in
> the
> foreground. This, in turn, requires that you must wait for the command to
> complete before performing any other tasks. Indeed, in such an
> environment,
> you can only run one scheduled command at a time. Is there a compelling
> reason why "wait=yes" is specified (other than the obvious one of not
> wanting the database backup to occur before the backups of the storage
> pools
> complete)?
>
> Jack Coyle
>
> > ----------
> > From: Talafous, John G.[SMTP:Talafous AT TIMKEN DOT COM]
> > Reply To: ADSM: Dist Stor Manager
> > Sent: Saturday, March 24, 2001 12:07 PM
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: Re: Admin schedule to Backup DB does not start
> >
> > The ADMIN schedule that processing storage pools contained a "backup stg
> > blahpool blahpool wait=yes". When the wait completed, another backup
> stg
> > command was issued and the ADMIN schedule ended. Then, the ADMIN
> schedule
> > to
> > do the database backup kicked off.
> >
> > Does this mean only one ADMIN schedule at a time?
> > jt
> >
> > -----Original Message-----
> > From: Cook, Dwight E [mailto:cookde AT BP DOT COM]
> > Sent: Saturday, March 24, 2001 11:33 AM
> > To: ADSM-L AT vm.marist DOT edu
> > Subject: Re: Admin schedule to Backup DB does not start
> >
> >
> > did they have the same start time ? ? ?
> > That might cause that... but the actual scheduled event should initiate
> > and
> > be gone in seconds...
> > For all admin activity that I can think of, tsm simply spawns off a
> > process
> > and the scheduled event is complete, unless it is something really short
> > like an "update stg diskpool high=1 low=0" type thing...
> > What was your other schedule that actually tied things up for a while...
> > Like with the dbbackup schedule, it will start a process and then the
> > schedule/event is complete...
> >
> > Dwight
> >
> > -----Original Message-----
> > From: Talafous, John G. [mailto:Talafous AT TIMKEN DOT COM]
> > Sent: Saturday, March 24, 2001 9:38 AM
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: Re: Admin schedule to Backup DB does not start
> >
> >
> > Well what do you know?!? Another ADMIN schedule to manage storage pools
> > was
> > running. When it finished, the BACKUP_DB admin schedule started. But,
> does
> > this mean that only one (1) admin schedule can be active at any given
> > time?
> >
> > TIA,
> > John G. Talafous IS Technical Principal
> > The Timken Company Global Software Support
> > P.O. Box 6927 Data Management
> > 1835 Dueber Ave. S.W. Phone: (330)-471-3390
> > Canton, Ohio USA 44706-0927 Fax : (330)-471-4034
> > talafous AT timken DOT com http://www.timken.com
> >
>
|
