We have seen very strange behavior in the reports given by TSM for past scheduled
backups.
In particular, some node names repeatedly show that the actual start date is BEFORE
the scheduled start date. All clients are in polling mode. We have no randomization
(set to 0).
Other node names never show this (actual start date is past scheduled start date).
Samples of sql query of the EVENTS table are below.
We have TSM Server 4.1 on AIX, clients are Windows NT or 98, version 4.1.2.0 or
4.1.2.12.
Has anyone out there experienced such things ?
Gilles Danan
-----------------------------------------------------------------------------------------------------------------
SCHEDULED_START: 2001-07-29 04:00:00.000000
ACTUAL_START: 2001-07-29 02:00:20.000000
DOMAIN_NAME: BK20_ARCH_DOM
SCHEDULE_NAME: 4H_DAILY
NODE_NAME: vers_008
STATUS: Missed
RESULT:
REASON:
SCHEDULED_START: 2001-08-16 20:00:00.000000
ACTUAL_START: 2001-08-16 09:57:53.000000
DOMAIN_NAME: BK10_ARCH_DOM
SCHEDULE_NAME: 20H_DAILY_C
NODE_NAME: vers_014
STATUS: Completed
RESULT: 0
REASON:
SCHEDULED_START: 2001-08-12 06:00:00.000000
ACTUAL_START: 2001-08-12 05:00:18.000000
DOMAIN_NAME: BK20_ARCH_DOM
SCHEDULE_NAME: 6H_DAILY
NODE_NAME: vers_001
STATUS: Missed
RESULT:
REASON:
