Windows NT/2000 Daylight Savings Time Problem
Hello did I had to install the fix IP22088_17 on the NT/2000 servers, before next week'end, where we are going to summertime??? Sincerely, Bo Nielsen FDB dataPhone: +45 4386 4671 Roskildevej 65 Fax: +45 4386 4990 DK-2620 AlbertslundE-mail: [EMAIL PROTECTED] Denmark -- Fra: Andy Raibeck[SMTP:[EMAIL PROTECTED]] Svar til: ADSM: Dist Stor Manager Sendt:28. oktober 2000 08:44 Til: [EMAIL PROTECTED] Emne: Re: ATTN ALL TSM USERS: Windows NT/2000 Daylight Savings Time Problem Hello, The fixtests for this problem are now available for download from the FTP site. Please note that the original note I sent out earlier erroneously stated that the version 4.1 fixtest was 4.1.1.17 and the file names to download begin wtih IP22088_17. In fact, the fixtest version is 4.1.1.16 and the file names begin with IP22088_16. The 3.7 fixtest was reported correctly as being version 3.7.2.17 and the file names beginning with IP21933_17. I have included the corrected version of the original note below for your reference. The files are located on our anonymous ftp site, ftp.software.ibm.com: Version 4.1.1.16: Directory /storage/tivoli-storage-management/patches/client/v4r1/Windows/v411/single Please review the IP22088_16_readme.ftp file for information on downloading and installing the fixtest. Version 3.7.2.17: Directory /storage/tivoli-storage-management/patches/client/v3r7/Windows/v372/i386/s ingle Please review the IP21933_17_readme.ftp file for information on downloading and installing the fixtest. Andy Andy Raibeck IBM/Tivoli Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." IMPORTANT - PLEASE READ THE FOLLOWING: A problem with the switch between Daylight Savings Time (DST) and Standard Time (STD) has just been discovered for the Windows TSM clients. BACKGROUND When Windows NT and 2000 systems automatically switch between DST and STD, the time attributes for files stored on NTFS file systems will be shifted by one hour. This is because NTFS displays time information as an offset from Greenwich Mean Time (GMT). Thus when the DST change is made, the offset from GMT is changed, causing the timestamps on your NTFS files to also change. (Note: Time information for Event Viewer events is affected in the same manner, but that is not pertinent to this discussion.) Further information on this subject is available in the Microsoft Knowledge Base, item Q129574. If you point your web browser to Microsoft's MSDN site, http://msdn.microsoft.com, and search on "Q129574" (without the quotes), you will find the information. THE PROBLEM When the system automatically adjusts between DST and STD, the TSM 3.7.2 (and higher) clients will see that the modification time has changed for all files on NTFS systems, and will proceed to back everything up accordingly, even if the file has not really changed. This will occur only once after the time change, and thereafter incremental backups will proceed as normal. However, this will almost certainly affect the amount of data backed up by each client, effectively causing a full backup on all NTFS file systems. This could have a large impact on network and TSM server resources. The following bullets summarize the conditions under which this problem can occur: - TSM client is running on Windows NT 4.0 or Windows 2000. TSM clients running on Windows 9x-based operating systems (Windows 95, 98) are not affected. - The TSM client level is 3.7.2.x or higher (including all 4.1.x levels). TSM client levels below 3.7.2.x are not affected, as the problem was introduced in the 3.7.2.x code. - The file systems are formatted for NTFS. FAT and FAT32 file systems are unaffected by this problem. - The operating system's time zone settings are configured to automatically adjust for DST. You can check this by right-clicking on the Windows task bar and selecting the "Adjust Date/Time" item in the pop-up menu. (Alternatively, you can double-click on the clock display in the task bar.) Either of these actions will bring up the "Date/Time Properties" dialog. Click on the "Time Zone" tab and you should see the "Automatically adjust clock for daylight saving changes" checkbox. If the box is checked (the default installation setting), then your system is configured to automatically adjust for DST. Users in regions that do not observe DST (such as Arizona) will be unaffected by this problem, provided that the system's time zone settings are similarly configured to not observe DST. WHAT IBM/TIVOLI IS DOING ABOUT THIS Here are the actions that we are taking or have taken to date: 1) We have opened a severity 1 APAR, IC28544, to address this problem. 2)
Re: Windows NT/2000 Daylight Savings Time Problem
I believe we go to DST the last Sunday in April. I hope we get clear on this on this change and don't have a notice 3 days before telling us there is a problem. NO way I can update 100 clients with that notice. David B. Longo System Administrator Health First, Inc. 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax:321.434.5525 [EMAIL PROTECTED] [EMAIL PROTECTED] 03/16/01 04:38AM Hello did I had to install the fix IP22088_17 on the NT/2000 servers, before next week'end, where we are going to summertime??? Sincerely, Bo Nielsen FDB dataPhone: +45 4386 4671 Roskildevej 65 Fax: +45 4386 4990 DK-2620 AlbertslundE-mail: [EMAIL PROTECTED] Denmark -- Fra: Andy Raibeck[SMTP:[EMAIL PROTECTED]] Svar til: ADSM: Dist Stor Manager Sendt:28. oktober 2000 08:44 Til: [EMAIL PROTECTED] Emne: Re: ATTN ALL TSM USERS: Windows NT/2000 Daylight Savings Time Problem Hello, The fixtests for this problem are now available for download from the FTP site. Please note that the original note I sent out earlier erroneously stated that the version 4.1 fixtest was 4.1.1.17 and the file names to download begin wtih IP22088_17. In fact, the fixtest version is 4.1.1.16 and the file names begin with IP22088_16. The 3.7 fixtest was reported correctly as being version 3.7.2.17 and the file names beginning with IP21933_17. I have included the corrected version of the original note below for your reference. The files are located on our anonymous ftp site, ftp.software.ibm.com: Version 4.1.1.16: Directory /storage/tivoli-storage-management/patches/client/v4r1/Windows/v411/single Please review the IP22088_16_readme.ftp file for information on downloading and installing the fixtest. Version 3.7.2.17: Directory /storage/tivoli-storage-management/patches/client/v3r7/Windows/v372/i386/s ingle Please review the IP21933_17_readme.ftp file for information on downloading and installing the fixtest. Andy Andy Raibeck IBM/Tivoli Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." IMPORTANT - PLEASE READ THE FOLLOWING: A problem with the switch between Daylight Savings Time (DST) and Standard Time (STD) has just been discovered for the Windows TSM clients. BACKGROUND When Windows NT and 2000 systems automatically switch between DST and STD, the time attributes for files stored on NTFS file systems will be shifted by one hour. This is because NTFS displays time information as an offset from Greenwich Mean Time (GMT). Thus when the DST change is made, the offset from GMT is changed, causing the timestamps on your NTFS files to also change. (Note: Time information for Event Viewer events is affected in the same manner, but that is not pertinent to this discussion.) Further information on this subject is available in the Microsoft Knowledge Base, item Q129574. If you point your web browser to Microsoft's MSDN site, http://msdn.microsoft.com, and search on "Q129574" (without the quotes), you will find the information. THE PROBLEM When the system automatically adjusts between DST and STD, the TSM 3.7.2 (and higher) clients will see that the modification time has changed for all files on NTFS systems, and will proceed to back everything up accordingly, even if the file has not really changed. This will occur only once after the time change, and thereafter incremental backups will proceed as normal. However, this will almost certainly affect the amount of data backed up by each client, effectively causing a full backup on all NTFS file systems. This could have a large impact on network and TSM server resources. The following bullets summarize the conditions under which this problem can occur: - TSM client is running on Windows NT 4.0 or Windows 2000. TSM clients running on Windows 9x-based operating systems (Windows 95, 98) are not affected. - The TSM client level is 3.7.2.x or higher (including all 4.1.x levels). TSM client levels below 3.7.2.x are not affected, as the problem was introduced in the 3.7.2.x code. - The file systems are formatted for NTFS. FAT and FAT32 file systems are unaffected by this problem. - The operating system's time zone settings are configured to automatically adjust for DST. You can check this by right-clicking on the Windows task bar and selecting the "Adjust Date/Time" item in the pop-up menu. (Alternatively, you can double-click on the clock display in the task bar.) Either of these actions will bring up the "Date/Time Properties" dialog. Click on the "Time Zone" tab and you should see the "Automatically adjust clock for daylight saving changes" checkbox. If the box is checked (the default installation setti
Re: Windows NT/2000 Daylight Savings Time Problem
No such luck! DST starts the FIRST Sunday in April. (perhaps appropriately, this year, it's April 1) -Original Message- From: David Longo [mailto:[EMAIL PROTECTED]] Sent: Friday, March 16, 2001 10:17 AM To: [EMAIL PROTECTED] Subject: Re: Windows NT/2000 Daylight Savings Time Problem I believe we go to DST the last Sunday in April. I hope we get clear on this on this change and don't have a notice 3 days before telling us there is a problem. NO way I can update 100 clients with that notice. David B. Longo System Administrator Health First, Inc. 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax:321.434.5525 [EMAIL PROTECTED] [EMAIL PROTECTED] 03/16/01 04:38AM Hello did I had to install the fix IP22088_17 on the NT/2000 servers, before next week'end, where we are going to summertime??? Sincerely, Bo Nielsen FDB dataPhone: +45 4386 4671 Roskildevej 65 Fax: +45 4386 4990 DK-2620 AlbertslundE-mail: [EMAIL PROTECTED] Denmark -- Fra: Andy Raibeck[SMTP:[EMAIL PROTECTED]] Svar til: ADSM: Dist Stor Manager Sendt:28. oktober 2000 08:44 Til: [EMAIL PROTECTED] Emne: Re: ATTN ALL TSM USERS: Windows NT/2000 Daylight Savings Time Problem Hello, The fixtests for this problem are now available for download from the FTP site. Please note that the original note I sent out earlier erroneously stated that the version 4.1 fixtest was 4.1.1.17 and the file names to download begin wtih IP22088_17. In fact, the fixtest version is 4.1.1.16 and the file names begin with IP22088_16. The 3.7 fixtest was reported correctly as being version 3.7.2.17 and the file names beginning with IP21933_17. I have included the corrected version of the original note below for your reference. The files are located on our anonymous ftp site, ftp.software.ibm.com: Version 4.1.1.16: Directory /storage/tivoli-storage-management/patches/client/v4r1/Windows/v411/single Please review the IP22088_16_readme.ftp file for information on downloading and installing the fixtest. Version 3.7.2.17: Directory /storage/tivoli-storage-management/patches/client/v3r7/Windows/v372/i386/s ingle Please review the IP21933_17_readme.ftp file for information on downloading and installing the fixtest. Andy Andy Raibeck IBM/Tivoli Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." IMPORTANT - PLEASE READ THE FOLLOWING: A problem with the switch between Daylight Savings Time (DST) and Standard Time (STD) has just been discovered for the Windows TSM clients. BACKGROUND When Windows NT and 2000 systems automatically switch between DST and STD, the time attributes for files stored on NTFS file systems will be shifted by one hour. This is because NTFS displays time information as an offset from Greenwich Mean Time (GMT). Thus when the DST change is made, the offset from GMT is changed, causing the timestamps on your NTFS files to also change. (Note: Time information for Event Viewer events is affected in the same manner, but that is not pertinent to this discussion.) Further information on this subject is available in the Microsoft Knowledge Base, item Q129574. If you point your web browser to Microsoft's MSDN site, http://msdn.microsoft.com, and search on "Q129574" (without the quotes), you will find the information. THE PROBLEM When the system automatically adjusts between DST and STD, the TSM 3.7.2 (and higher) clients will see that the modification time has changed for all files on NTFS systems, and will proceed to back everything up accordingly, even if the file has not really changed. This will occur only once after the time change, and thereafter incremental backups will proceed as normal. However, this will almost certainly affect the amount of data backed up by each client, effectively causing a full backup on all NTFS file systems. This could have a large impact on network and TSM server resources. The following bullets summarize the conditions under which this problem can occur: - TSM client is running on Windows NT 4.0 or Windows 2000. TSM clients running on Windows 9x-based operating systems (Windows 95, 98) are not affected. - The TSM client level is 3.7.2.x or higher (including all 4.1.x levels). TSM client levels below 3.7.2.x are not affected, as the problem was introduced in the 3.7.2.x code. - The file systems are formatted for NTFS. FAT and FAT32 file systems are unaffected by this problem. - The operating system's time zone settings are configured to automatically adjust for DST. You can check this by right-clicking on the Windows task bar and selecting the "Adjust Date/Time" item in the pop-up menu. (Alternatively, you can double-click on the clock disp
Re: Windows NT/2000 Daylight Savings Time Problem
What are the implications of not having these versions? Are they the same as back in October 2000 or is there some diference? David B. Longo System Administrator Health First, Inc. 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax:321.434.5525 [EMAIL PROTECTED] [EMAIL PROTECTED] 03/16/01 10:49AM Have we reverted back to the last Sunday in April? I know that at one time, the change to DST used to occur on the last Sunday in April, but it was changed to the first Sunday in April back in the 1980's (at least in the US). If you are running the 3.7.x client, I recommend using 3.7.2.19. If you are running the 4.1.1.x client, you need to use IP22088_16 (there is no IP22088_17 as far as I know), which corresponds to version 4.1.1.16. If you are running the 4.1.2.x client, you need to use IP22151_12, which corresponds to version 4.1.2.12. We also verified that the DST fix stayed fixed in this level. Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." David Longo [EMAIL PROTECTED]@VM.MARIST.EDU on 03/16/2001 08:17:26 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: Windows NT/2000 Daylight Savings Time Problem I believe we go to DST the last Sunday in April. I hope we get clear on this on this change and don't have a notice 3 days before telling us there is a problem. NO way I can update 100 clients with that notice. David B. Longo System Administrator Health First, Inc. 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax:321.434.5525 [EMAIL PROTECTED] [EMAIL PROTECTED] 03/16/01 04:38AM Hello did I had to install the fix IP22088_17 on the NT/2000 servers, before next week'end, where we are going to summertime??? Sincerely, Bo Nielsen FDB dataPhone: +45 4386 4671 Roskildevej 65 Fax: +45 4386 4990 DK-2620 AlbertslundE-mail: [EMAIL PROTECTED] Denmark -- Fra: Andy Raibeck[SMTP:[EMAIL PROTECTED]] Svar til: ADSM: Dist Stor Manager Sendt:28. oktober 2000 08:44 Til: [EMAIL PROTECTED] Emne: Re: ATTN ALL TSM USERS: Windows NT/2000 Daylight Savings Time Problem Hello, The fixtests for this problem are now available for download from the FTP site. Please note that the original note I sent out earlier erroneously stated that the version 4.1 fixtest was 4.1.1.17 and the file names to download begin wtih IP22088_17. In fact, the fixtest version is 4.1.1.16 and the file names begin with IP22088_16. The 3.7 fixtest was reported correctly as being version 3.7.2.17 and the file names beginning with IP21933_17. I have included the corrected version of the original note below for your reference. The files are located on our anonymous ftp site, ftp.software.ibm.com: Version 4.1.1.16: Directory /storage/tivoli-storage-management/patches/client/v4r1/Windows/v411/single Please review the IP22088_16_readme.ftp file for information on downloading and installing the fixtest. Version 3.7.2.17: Directory /storage/tivoli-storage-management/patches/client/v3r7/Windows/v372/i386/s ingle Please review the IP21933_17_readme.ftp file for information on downloading and installing the fixtest. Andy Andy Raibeck IBM/Tivoli Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." IMPORTANT - PLEASE READ THE FOLLOWING: A problem with the switch between Daylight Savings Time (DST) and Standard Time (STD) has just been discovered for the Windows TSM clients. BACKGROUND When Windows NT and 2000 systems automatically switch between DST and STD, the time attributes for files stored on NTFS file systems will be shifted by one hour. This is because NTFS displays time information as an offset from Greenwich Mean Time (GMT). Thus when the DST change is made, the offset from GMT is changed, causing the timestamps on your NTFS files to also change. (Note: Time information for Event Viewer events is affected in the same manner, but that is not pertinent to this discussion.) Further information on this subject is available in the Microsoft Knowledge Base, item Q129574. If you point your web browser to Microsoft's MSDN site, http://msdn.microsoft.com, and search on "Q129574" (without the quotes), you will find the information. THE PROBLEM When the system automatically adjusts between DST and STD, the TSM 3.7.2 (and higher) clients will see that the modification time has changed for all files on NTFS systems, and will proceed to back everything up accordingly, even if the file has not really changed
Re: Windows NT/2000 Daylight Savings Time Problem
If you are not on a version of the client that includes the fix for IC28544 (the DST problem), then you will experience the problem. The version numbers I recommend all inlcude that fix, plus a number of other fixes as well. You can check the README files for those versions to see what is fixed in them. Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." David Longo [EMAIL PROTECTED]@VM.MARIST.EDU on 03/16/2001 09:23:40 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: Windows NT/2000 Daylight Savings Time Problem What are the implications of not having these versions? Are they the same as back in October 2000 or is there some diference? David B. Longo System Administrator Health First, Inc. 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax:321.434.5525 [EMAIL PROTECTED] [EMAIL PROTECTED] 03/16/01 10:49AM Have we reverted back to the last Sunday in April? I know that at one time, the change to DST used to occur on the last Sunday in April, but it was changed to the first Sunday in April back in the 1980's (at least in the US). If you are running the 3.7.x client, I recommend using 3.7.2.19. If you are running the 4.1.1.x client, you need to use IP22088_16 (there is no IP22088_17 as far as I know), which corresponds to version 4.1.1.16. If you are running the 4.1.2.x client, you need to use IP22151_12, which corresponds to version 4.1.2.12. We also verified that the DST fix stayed fixed in this level. Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." David Longo [EMAIL PROTECTED]@VM.MARIST.EDU on 03/16/2001 08:17:26 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: Windows NT/2000 Daylight Savings Time Problem I believe we go to DST the last Sunday in April. I hope we get clear on this on this change and don't have a notice 3 days before telling us there is a problem. NO way I can update 100 clients with that notice. David B. Longo System Administrator Health First, Inc. 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax:321.434.5525 [EMAIL PROTECTED] [EMAIL PROTECTED] 03/16/01 04:38AM Hello did I had to install the fix IP22088_17 on the NT/2000 servers, before next week'end, where we are going to summertime??? Sincerely, Bo Nielsen FDB dataPhone: +45 4386 4671 Roskildevej 65 Fax: +45 4386 4990 DK-2620 AlbertslundE-mail: [EMAIL PROTECTED] Denmark -- Fra: Andy Raibeck[SMTP:[EMAIL PROTECTED]] Svar til: ADSM: Dist Stor Manager Sendt:28. oktober 2000 08:44 Til: [EMAIL PROTECTED] Emne: Re: ATTN ALL TSM USERS: Windows NT/2000 Daylight Savings Time Problem Hello, The fixtests for this problem are now available for download from the FTP site. Please note that the original note I sent out earlier erroneously stated that the version 4.1 fixtest was 4.1.1.17 and the file names to download begin wtih IP22088_17. In fact, the fixtest version is 4.1.1.16 and the file names begin with IP22088_16. The 3.7 fixtest was reported correctly as being version 3.7.2.17 and the file names beginning with IP21933_17. I have included the corrected version of the original note below for your reference. The files are located on our anonymous ftp site, ftp.software.ibm.com: Version 4.1.1.16: Directory /storage/tivoli-storage-management/patches/client/v4r1/Windows/v411/single Please review the IP22088_16_readme.ftp file for information on downloading and installing the fixtest. Version 3.7.2.17: Directory /storage/tivoli-storage-management/patches/client/v3r7/Windows/v372/i386/s ingle Please review the IP21933_17_readme.ftp file for information on downloading and installing the fixtest. Andy Andy Raibeck IBM/Tivoli Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." IMPORTANT - PLEASE READ THE FOLLOWING: A problem with the switch between Daylight Savings Time (DST) and Standard Time (STD) has just been discovered for the Windows TSM clients. BACKGROUND When Windows NT and 2000 systems automatically switch between DST and STD, the time attributes for files stored on NTFS file systems will be shifted by one hour. This is because NTFS displays time information as an offset from Greenwich Mean Time (GMT). Thus when the DST change is made, the
Re: Windows NT/2000 Daylight Savings Time Problem
I Just downloaded the 3.7.2.19 from: ftp://index.storsys.ibm.com/tivoli-storage-management/patches/client/v3r7/Wi ndows/v372/i386/single/ IP21933 19 FULL.EXE When I expanded the file, I kept getting the message _Setup.dll already exits. I renamed each instance and wound up with 10 versions 6 were 34K and 4 were 35K I don't think I want to run this one. On Friday, March 16, 2001 7:49 AM, Andy Raibeck [SMTP:[EMAIL PROTECTED]] wrote: Have we reverted back to the last Sunday in April? I know that at one time, the change to DST used to occur on the last Sunday in April, but it was changed to the first Sunday in April back in the 1980's (at least in the US). If you are running the 3.7.x client, I recommend using 3.7.2.19. If you are running the 4.1.1.x client, you need to use IP22088_16 (there is no IP22088_17 as far as I know), which corresponds to version 4.1.1.16. If you are running the 4.1.2.x client, you need to use IP22151_12, which corresponds to version 4.1.2.12. We also verified that the DST fix stayed fixed in this level. Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked."
Re: Windows NT/2000 Daylight Savings Time Problem
Hi Nancy, There is no 4.1.0.x fix for this; you will need to go to 4.1.1.16 or 4.1.2.12. Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." Nancy Reeves [EMAIL PROTECTED]@VM.MARIST.EDU on 03/16/2001 02:30:16 PM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: Windows NT/2000 Daylight Savings Time Problem Andy, What version of 4.1.0.x for Windows NT has the fix? Or should I upgrade to 4.1.1.16 or 4.1.2.12? I only have a couple dozen NT/2000 clients. Nancy Reeves Technical Support, Wichita State University [EMAIL PROTECTED] 316-978-3860 If you are not on a version of the client that includes the fix for IC28544 (the DST problem), then you will experience the problem. The version numbers I recommend all inlcude that fix, plus a number of other fixes as well. You can check the README files for those versions to see what is fixed in them. Regards, Andy --- If you are running the 3.7.x client, I recommend using 3.7.2.19. If you are running the 4.1.1.x client, you need to use IP22088_16 (there is no IP22088_17 as far as I know), which corresponds to version 4.1.1.16. If you are running the 4.1.2.x client, you need to use IP22151_12, which corresponds to version 4.1.2.12. We also verified that the DST fix stayed fixed in this level. Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." IMPORTANT - PLEASE READ THE FOLLOWING: A problem with the switch between Daylight Savings Time (DST) and Standard Time (STD) has just been discovered for the Windows TSM clients. BACKGROUND When Windows NT and 2000 systems automatically switch between DST and STD, the time attributes for files stored on NTFS file systems will be shifted by one hour. This is because NTFS displays time information as an offset from Greenwich Mean Time (GMT). Thus when the DST change is made, the offset from GMT is changed, causing the timestamps on your NTFS files to also change. (Note: Time information for Event Viewer events is affected in the same manner, but that is not pertinent to this discussion.) Further information on this subject is available in the Microsoft Knowledge Base, item Q129574. If you point your web browser to Microsoft's MSDN site, http://msdn.microsoft.com, and search on "Q129574" (without the quotes), you will find the information. THE PROBLEM When the system automatically adjusts between DST and STD, the TSM 3.7.2 (and higher) clients will see that the modification time has changed for all files on NTFS systems, and will proceed to back everything up accordingly, even if the file has not really changed. This will occur only once after the time change, and thereafter incremental backups will proceed as normal. However, this will almost certainly affect the amount of data backed up by each client, effectively causing a full backup on all NTFS file systems. This could have a large impact on network and TSM server resources. The following bullets summarize the conditions under which this problem can occur: - TSM client is running on Windows NT 4.0 or Windows 2000. TSM clients running on Windows 9x-based operating systems (Windows 95, 98) are not affected. - The TSM client level is 3.7.2.x or higher (including all 4.1.x levels). TSM client levels below 3.7.2.x are not affected, as the problem was introduced in the 3.7.2.x code. - The file systems are formatted for NTFS. FAT and FAT32 file systems are unaffected by this problem. - The operating system's time zone settings are configured to automatically adjust for DST. You can check this by right-clicking on the Windows task bar and selecting the "Adjust Date/Time" item in the pop-up menu. (Alternatively, you can double-click on the clock display in the task bar.) Either of these actions will bring up the "Date/Time Properties" dialog. Click on the "Time Zone" tab and you should see the "Automatically adjust clock for daylight saving changes" checkbox. If the box is checked (the default installation setting), then your system is configured to automatically adjust for DST. Users in regions that do not observe DST (such as Arizona) will be unaffected by this problem, provided that the system's time zone settings are similarly configured to not observe DST. WHAT IBM/TIVOLI IS DOING ABOUT THIS Here are the actions that we are taking or have taken to date: 1) We have opened a severity 1 APAR, IC28544, to address this problem. 2) We have designed and built fixtests for the 3.7.2 and 4.1.1 Windows clients. The fixtest vers
Re: ATTN ALL TSM USERS: Windows NT/2000 Daylight Savings Time Problem
At 04:44 PM 10/27/2000 -0700, you wrote: IMPORTANT - PLEASE READ THE FOLLOWING: A problem with the switch between Daylight Savings Time (DST) and Standard Time (STD) has just been discovered for the Windows TSM clients. Andy, thank you for the detailed note on Friday afternoon. An open note to TSM product managers: A problem very similar to this one got into the ADSM Windows client a few years ago, and caused significant grief to ADSM sites. I find it distressing to see a similar problem show up again. Sure, it is probably a different bug, but what it indicates is that insufficient quality control was added following the last occurrence of this bug. If a test for this had been added to the quality control process, this bug would have been detected before the code had been distributed. This does make me wonder what, if any, testing is done before the code is made available for distribution. If you cannot learn from the past, you (and all of us) will be forever condemned to repeat the same experiences again and again.
Re: ATTN ALL TSM USERS: Windows NT/2000 Daylight Savings Time Problem
I have installed fixtest 3.7.2.17 that appeared on the ftp site this weekend on two clients. Unfortunately, even with this code installed, the first incremental backup after the end of DST began backing up all files. Is this fix only a partial fix due to the previous client version storing an incorrect timestamp for the file? The new version reads the correct timestamp, compares is with the incorrectly stored one and decides to back up the files? Or is it not a fix at all? Neil The information in this e-mail is confidential and may also be legally privileged. The contents are intended for recipient only and are subject to the legal notice available at http://www.keldagroup.com/email.htm Yorkshire Water Services Limited Registered Office 2 The Embankment Sovereign Street Leeds LS1 4BG Registered in England and Wales No 2366682
