===== part 1 =====
We all have to tell TSM how to do its daily housekeeping.
In 3.1 we used admin schedules;
in 3.7 maybe we supplemented that with server scripts;
in 4.1 the scripts became a little more programmable;
But they're not great. The problems I see:
1. A second admin schedule won't start if an earlier admin schedule is still
running. The earlier schedule has to complete, or the second one says
"missed" and won't even start. And you don't always know how long the first
one's going to take.
2. You can't say "migrate stgpool xxxx wait=yes". All you can do is lower
the highwater mark to kick off migration. But if you want to WAIT for
migration to complete, you just have to guess how long it's going to take.
3. It's hard to cancel a script. Cancel the currently running process, and
the NEXT thing takes off.
If you use the OS (crontab, for instance) to schedule administrative jobs,
you have more flexibility.
-you can schedule, say, database backup, and it will run whether another
job is running or not (see point 1 above).
-you can test whether job A is running before kicking off job B (point 2
above).
-you can stop a macro all at once.
(NOTE: I'm only talking about ADMIN schedules here - CLIENT schedules are
better done with the TSM scheduler.)
So, over time, I've gotten more partial to crontab-base scheduling. Even
though it's nice to have all the scheduling done by TSM, it just doesn't
work as well.
Who agrees? Disagrees?
===== part 2 =====
I'm trying to figure out a general solution to this. So tell me please:
what scheduling requirements do you have? For instance:
-- run migration as soon as no nodes are in session. But if a node
session starts, turn off migration.
-- wait until migration finishes before running DB backup
-- run "move drm" to eject vault tapes as soon as DB backup is done, but
be sure the tape list has been emailed to vault service first.
-- and yours?
I don't think anybody's compiled a list of scheduling requirements before.
I'll share what I get. (or just mail the list.)
Thanks in advance.
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Tab Trepagnier
Sent: Friday, May 18, 2001 1:01 PM
To: [EMAIL PROTECTED]
Subject: Script logic
I'm just beginning to use TSM server scripts.
What is the best way to implement a "while do" loop?
For example:
While "node" sessions are present:
"sleep" for 10 minutes
End While
Launch the next TSM process...
That will allow building condition / prerequisite testing into the scripts.
Thanks.
Tab Trepagnier
TSM Administrator
Laitram Corporation
