It was the client code that was previously fixed, more than once, in the 3.1
and 3.7 timeframe --- sounds like the DST code for Windows got broken,
again. 4.1.x is downlevel, for support contract purposes -- unless things
are different for you.
Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:don_france AT ayett DOT net (change aye to a, for replies)
Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Bill Dourado
Sent: Saturday, November 02, 2002 7:03 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Daylight saving Disaster
Importance: High
Hi there
I am in big trouble after daylight saving when clocks went backup one
hour.
All the clients(50) are attempting to do full backups !
My TSM Server version is 4.1.4.1
The clients(Windows 2000 & NT) are mostly 4.1.1.0 , a few are 3.1.07 &
3.1.0.6.
I have temporarily suspended all backup schedules except for the business
critical clients.
I have upgraded one of clients to 4.2.3.1 and intend to upgrade the rest
of the clients.
Will I run into any problems bearing in mind my TSM Server version is
4.1.4.1 ?
T.I.A
Bill Dourado
|