Revised post 02/06/01 Below is a compilation of info that has been posted to this list about the TSM Win32 client. All available versions of the Win32 client have SUPPORT ISSUES that you must address carefully to preserve data integrity in your Win2K backups. Some of these problems also affect WinNT, noted below. Thanks to everyone who has contributed. If you find errors or have additional information, please post it and I will update this list regularly. Most of the problems below only affect those who are backing up via the scheduler. Where search keywords are included you can search for the original postings at: www.adsm.org. ++++++++++++++ Level 3.7.2.01 -- Win2K: Some clients get "export of RSM data base fails" error during scheduled backup. The scheduler stops and no backups are done, but it REPORTS SUCCESS BACK TO THE SERVER. YOU CAN"T BE SURE whether you are getting backups of your Win2K machines or not without checking the scheduler log. This should be posted as a HIPER problem on the Tivoli web site as it is a MAJOR INTEGRITY problem to report failed backups as OK. Search keywords: "EXPORT RSM". If you don't need registry backups, avoid the problem by using the BACKUPREG NO option. One person reported correcting it by setting the RSM service to MANUAL start. --Win2K: APAR IC27196 There are other cases where scheduled backups fail but are reported as COMPLETED successfully back to the server. This is fixed in 4.1.2. --Win2K, WinNT: Our old favorite the Daylight Savings time bug has returned, it does a full backup when it should not. --Win2K, WinNT: APAR IC27249 If the setup wizard is used to configure an existing dsm.opt file for web client or scheduler, the include/exclude statements are removed. Fixed in 4.1.2. +++++++++++++++ Level 3.7.2.17 --Win2K, WinNT: This level has fix for the Daylight Savings Time bug. +++++++++++++++ Level 4.1.1 --Win2K: One person reported RSM EXPORT error as in the 3.7.2.01 above. --Win2K: At Level 4.1.1, the scheduler does not give you backups of the system objects, you must create your own .bat files to back them up with commands. --Win2K, WinNT: Level 4.1.1 also has the Daylight Savings Time bug. --WinNT, WIN2K: Reports of unusually slow archiving times with TSM 4.1.1 client. Search: "archiving problems with TSM". --Win2K: APAR IC27728 - if backing up with compression=yes and compressalways=no, the backup of system ojbects is not complete. Bypass - use compressalways=no if using compression. --Win2K, WinNT: APAR IC27249 If the setup wizard is used to configure an existing dsm.opt file for web client or scheduler, the include/exclude statements are removed. Fixed in 4.1.2. ++++++++++++++++ Level 4.1.1.16 -- Win2K, WinNT: This level has the fix for the Daylight Savings Time bug. ++++++++++++++++ Level 4.1.2 -- Win2K: One person has reported the EXPORT RSM bug as in 3.7.2.01. In this case the RSM error did NOT prevent the backup of other data, although it still reported SUCCESS back to the server. --Win2K: At 4.1.2 the scheduler DOES back up the system objects automatically as part of a normal incremental backup. --Win2K: Your server must be at 3.7.3 at least, or the client will not back up the registry, even though earlier versions of the client did so. --Win2K, WinNT: The 4.1.2 client has changed the structure for registry backups so now a system32\config subdirectory is created in \adsm.sys as part of registry backup. However, the 4.1.2 client has an EXCLUDE statement that prevents these files in system32\config from being sent to the server. Current older TSM clients that you plan to upgrade in place also, in MANY INSTALLATIONS, have this EXCLUDE statement and will prevent registry backups from being saved. So you must NOT USE the exclude list provided with the client for new installs, and for existing clients you must ALTER your include/exclude lists to add: include *:\adsm.sys\...\*. You must PREVENT YOUR USERS from installing the 4.1.2 clients until you have taken care of this problem. FOR TIVOLI TO DISTRIBUTE THE CLIENT IN THIS FASHION IS APPALLING. This should be flagged as a HIPER problem on the Tivoli Web site, as having someone simply install the 4.1.2 client over an older client will CREATE AN INTEGRITY PROBLEM that they will never be aware of until they try to do a restore. Search keyword: "REGISTRY EXCLUDED". From www.redbooks.ibm.com you can download a new document, SG24-6141-00, that has a tested EXCLUDE list suitable for Win2K. Win2K: APAR IC29368 - User Abort on Backup. Client displays User Abort when error detected instead of displaying proper error message, it is sometimes easy to determine what the real error is, sometimes not so easy. --Win2K: APAR IC29356 - Different number of system objects backed up via web client than GUI or cmd line, pretty minor but make sure you don't rely on a backup of the System Objects made with the Web Client. --Win2K: Bare Metal Restore, on person reports error importing the RSM data base files --Win2K, WinNT: APAR IC29440, silent installs do not distribute the custom dsm.opt file. Search: "custom dsm.opt" --Win2K, WinNT: IC28963 - bogus error in dsmerror.log after reboot - "error killing thread" --Win2K: IC29403 - Install using MSINSTALLER or W2K Group Policy does not work
