Tobi & Andy,
Thanks for your interest and your reply.
I followed your instructions, step by step (very clear, I might add). Everything on
the server side looks as I would expect it.
The problem appears to be on the client side. In response to the q sched, on the
client, I don't see the backup policy that I have just created. I only see the "old"
one that I am to be phasing out.
This is confirmed when looking in the dsmsched.log file. Only the "old" job appears
here.
The only thing that shows up in the dsmerror.log file is, "Error starting listen
thread", which has been there for some time before I started my activities.
Ken
[EMAIL PROTECTED]
>>> [EMAIL PROTECTED] 07/16/2002 4:15:38 AM >>>
I would also add, make sure the scheduler daemon/service is running on
each client machine.
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: [EMAIL PROTECTED] (change eye to i to reply)
The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
Tobias Hofmann <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
07/16/2002 02:07
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject: Re: Scheduled TSM Policy Will Not Run
Hi Ken,
At 20:03 15.07.2002, you wrote:
>Hi,
>I'm new to TSM & AIX (so new that, last month I could not spell TSM nor
AIX).
I am as new to this as you are, even though on Win2K, but that shouldn,t
make too much a difference. Here is what I would do:
> So here's my dilemma.
[...]
> The new policy does not run and I receive the following message on the
> TSM server.
>
>ANR2578W Schedule DAVINCI_BACKUP_DAILY in domain
> UNIX_SERVER_DAVINCI_DAILY for node
> BACKUP_DAVINCI_DAILY
> has missed its scheduled start up window.
on the server, run
"q sched" to see what schedules are planned.
run "q assoc" to see if the nodes you want to have are associated (even
though to me it seems like that davinci was scheduled, hence the "missed"
notification).
run "q event *domain* *schedule*" to see if the events are scheduled as
intended.
on the client, run (in dsmc) "q sched" to see if the node has picked up
the
schedule provided by the server.
if i got this correctly, running this command on the client should update
the schedule for the node (here it did, iirc).
if no schedule shows up, in a next step i would check the schedmode
setting
for both the client and the server - see "set schedmode" in the admin-ref
and the schedmode-line in the dsm.sys-file on the client.
on a further node, the files dsmsched.log and dsmerror.log (which have to
be defined in the dsm.sys of the client as well) might help you along.
after a succesfull connection with the server, i find the next scheduled
backup at the end of the dsmsched.log.
take all this with a grain of salt - newbie-alert! :)
hoping that this helps, and please do correct me if i went wrong
somewhere,
regards, tobi
>
>What did I miss? Where did I go wrong?
>
>Thanks in advance to anyone who wants to lead me through the process, or
>just clear up the error of my ways.
>
>Ken
>[EMAIL PROTECTED]
----------------------------------------------------------------------
Dipl.-Ing. Tobias Hofmann Bauhaus-Universitaet Weimar D99423 Weimar
Professur fuer Graphische Datenverarbeitung Projekt medienquadrat
SnailMail: Bauhaus-Universitaet Weimar, Fak. Medien, D99421 Weimar
Location: D99423 Weimar Karl-Haussknechtstr. 7 Zimmer 111
Fon: ++49-(0)3643-58-3780 Fax : -3701
e-mail: mailto:[EMAIL PROTECTED]
----------------------------------------------------------------------
