And, for what it's worth, the stated "Local Fix" (aka, circumvention) DOES
NOT WORK!!!
I tested both 3.1.7 and 3.7.2, on NT and W2k. The problem is definitely
there on NT with 3.7.2 (and not with 3.1.7); also, we did not see it fail
with 3.7.2 on Win2k (FAT32 & NTFS)... but I didn't try every combination
(with & without SP1, etc.). The failure observed on Win2k was for the files
that were changed between 1am & 2am on 10/29... Also, don't know if the
"accept date" will work any miracles, since it's the client working with the
local filesystem API that seems to be the source of the problem.
For our environment, there are no huge consequences for the NT/W2k clients
using 3.7.2, if we just let things happen (we'll increase the version
count); we'd prefer that over a rush-to-fix install, not having tested the
new, 3.7.2.17 fixtest level.
Don France
Technical Architect - Unix Engineering
EDS Ph: (707) 226-0640
Bus-Ph: (408) 257-3037
> -----Original Message-----
> From: Barth, Terry (MBS) [mailto:[EMAIL PROTECTED]]
> Sent: Friday, October 27, 2000 6:30 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Warning - Windows NT/2000 Sev1 Flash
>
>
> I was watching this thread of conversation and I am not sure
> what version
> everyone is using - but in the below message at the end, it does state
>
> " *This does not affect 3.1.x and 3.7.0 clients. "
>
> Therefore, that may be why many have had different results.
>
>
> -----Original Message-----
> From: Dave Canan [mailto:[EMAIL PROTECTED]]
> Sent: Friday, October 27, 2000 11:13 AM
> To: [EMAIL PROTECTED]
> Subject: Warning - Windows NT/2000 Sev1 Flash
>
>
> This APAR was just opened this morning. I wanted to get ti
> distributed to
> the LISTSERV as quickly as I could.
>
>
>
> PMR NO: 08519,000,866
> OSs INVOLVED: NT
> COMPID: 5697TSMNT and 5698TSMNT
> APAR SEV: 1
> RELESE: 3.7.2 - 4.1.1
> KEYWORD: Daylight Savings incremental
> ABSTRACT:
> "Automatically adjust clock for daylight savings changes"
> causes incremental to do full backup
> ERROR DESCRIPTION:
> When NT is set to automatically adjust the clock for Daylight
> Savings NT modifies ALL files' time attribute by setting
> it back 1 hour thus causing incremental backups to perform full
> backups.
>
> RECREATE DIRECTIONS:
> 1) Create a subset of files
> 2) Change the time zone on NT to one that has daylight savings
> changes ( if applicable)
> 3) Change the time to a few minutes prior to daylight savings
> time (0200 October 29, 2000).
> ex: 0155
> 4) Check the box next to
> "Automatically adjust clock for daylight savings changes"
> 5) Do an incremental backup
> 6) Watch the time stamps change when the clock goes from 0159
> to 0200 back to 0100.
> 7) Do another incremental backup
> All files will be backed up as if it were a full backup.
>
> LOCAL FIX
> Uncheck the "Automatically adjust clock for daylight savings
> changes" in the time/date control panel and manually adjust
> the time for daylight savings.
> Additional Notes:
> *This does not affect 3.1.x and 3.7.0 clients. Microsoft
> Searchable Knowledge base reference number Q129574.
> * Old APAR IC13012 (v2.105 closed 1996) is the same problem for
> FAT file systems
>
>
> Money is not the root of all evil - full backups are.
>
