Thanks for giving me a good insight. I'm attaching the actlog from
00:00.(I'm sorry if it's too long). We have client polling every 12
hours. It looks like the client started and couldn't connect with the
server and ended inmmediately.
Today I did a test on one of client node. I rebooted the client node
and ran its schedule and it went OK. I suspect all other nodes need to
be restarted or rebooted to able to connect to the server with new time.
If that's the case, there are too many nodes that need to be rebooted.
Please correct me if I'm wrong. Thanks again.


05/15/02 00:00:12     ANR0403I Session 414 ended for node COMPAQ2
(Win95).
05/15/02 00:00:15     ANR0407I Session 422 started for administrator
JBAECHI
                       (WebBrowser) (HTTP 10.2.11.119(1251)).

05/15/02 00:00:15     ANR2017I Administrator JBAECHI issued command:
QUERY
                       ACTLOG

05/15/02 00:00:15     ANR0405I Session 422 ended for administrator
JBAECHI
                       (WebBrowser).

05/15/02 00:01:22     ANR0406I Session 434 started for node COMPAQ2
(Win95)
                       (Tcp/Ip 10.2.11.119(1263)).

05/15/02 00:01:24     ANR0406I Session 435 started for node COMPAQ2
(Win95)
                       (Tcp/Ip 10.2.11.119(1264)).

05/15/02 00:01:30     ANR2562I Automatic event record deletion started.

05/15/02 00:01:30     ANR2565I 0 schedules for immediate client actions
have
                       been deleted.

05/15/02 00:01:30     ANR2563I Removing event records dated prior to
05/08/02
                       00:00:00.

05/15/02 00:01:30     ANR2564I Automatic event record deletion ended -
40
                       records deleted.

05/15/02 00:02:32     ANR0403I Session 434 ended for node COMPAQ2
(Win95).
05/15/02 00:02:33     ANR0403I Session 435 ended for node COMPAQ2
(Win95).
05/15/02 00:02:47     ANR0406I Session 436 started for node COMPAQ2
(Win95)
                       (Tcp/Ip 10.2.11.119(1265)).

05/15/02 00:02:51     ANR0403I Session 436 ended for node COMPAQ2
(Win95).
05/15/02 00:05:33     ANR0406I Session 437 started for node DUBLIN
(NetWare)
                       (Tcp/Ip 10.15.1.5(3003)).

05/15/02 00:05:33     ANR0403I Session 437 ended for node DUBLIN
(NetWare).
05/15/02 00:05:33     ANR0406I Session 438 started for node DUBLIN
(NetWare)
                       (Tcp/Ip 10.15.1.5(3004)).

05/15/02 00:05:33     ANR0403I Session 438 ended for node DUBLIN
(NetWare).
05/15/02 00:06:38     ANR0406I Session 439 started for node COMPAQ2
(Win95)
                       (Tcp/Ip 10.2.11.119(1266)).

05/15/02 00:06:40     ANR0403I Session 439 ended for node COMPAQ2
(Win95).
05/15/02 00:10:59     ANR0406I Session 440 started for node BOLTON
(NetWare)
                       (Tcp/Ip 10.13.1.5(1842)).

05/15/02 00:11:00     ANR0403I Session 440 ended for node BOLTON
(NetWare).
05/15/02 00:11:00     ANR0406I Session 441 started for node BOLTON
(NetWare)
                       (Tcp/Ip 10.13.1.5(1843)).

05/15/02 00:11:00     ANR0403I Session 441 ended for node BOLTON
(NetWare).
05/15/02 00:17:45     ANR0406I Session 442 started for node GLOBAL
(WinNT)
                       (Tcp/Ip 10.51.1.5(1619)).

05/15/02 00:17:45     ANR0403I Session 442 ended for node GLOBAL
(WinNT).
05/15/02 00:17:45     ANR0406I Session 443 started for node GLOBAL
(WinNT)
                       (Tcp/Ip 10.51.1.5(1620)).

05/15/02 00:17:45     ANR0403I Session 443 ended for node GLOBAL
(WinNT).

>>> gwichman AT ZANTAZ DOT COM 05/15/02 07:02PM >>>
I would recommend doing basic troubleshooting.. check the TSM server
activity log around the time the backup window occurred (e.g. -> q act
startt=01:00). What was the TSM server doing if not backing anyone up?
Was
it trying to contact the clients and failing to (there would be
repeated
"contacting client blahblah" msgs if it was). Is there nothing there
except
a "client XX missed backup window" at the end of the window?

Ditto check the dsmsched.log on some of the clients. What were they
doing
around the supposed backup time? It should say clearly when they got
their
last schedule and what it was.

Are your clients in prompted or polling mode? The reason for the
missed
backups could vary depending on what mode you use. If polling, what was
the
interval the clients poll at (default is 12 hours)?

By looking at the logs you should be easily able to determine if it was
a
connectivity problem or if the clients simply missed their schedules
due to
an error in timing. You should also be able to see if the clients are
receiving the schedules and what time they individually think they're
supposed to being their backups. Some basic troubleshooting goes a
long
way..

Regards,

Gerald Wichmann
Senior Systems Development Engineer
Zantaz, Inc.
925.598.3099 (w)