Author: Richard Mochnaczewski <Richard.Mochnaczewski AT STANDARDLIFE DOT CA>
Date: Tue, 12 Jul 2005 13:54:41 -0400
Hi Everybody, I have a Windows 2003 server running a 5.2.2 client ( TSM server is at 5.1 Level 1.6 ). Why am I getting the following reconnection/session lost errors in the log ? It only occurs for t
Author: "George, Jason" <Jason.George AT VALERO DOT COM>
Date: Tue, 12 Jul 2005 13:26:28 -0500
Exclude it. -JG Hi Everybody, I have a Windows 2003 server running a 5.2.2 client ( TSM server is at 5.1 Level 1.6 ). Why am I getting the following reconnection/session lost errors in the log ? It o
Author: "Stapleton, Mark" <mark.stapleton AT BERBEE DOT COM>
Date: Tue, 12 Jul 2005 13:30:10 -0500
This is not necessary. c:\adsm.sys is automatically excluded from file-level backups; it is backed up as part of the systemstate/systemobject backups. -- Mark Stapleton (stapleton AT berbee DOT com)
Author: "George, Jason" <Jason.George AT VALERO DOT COM>
Date: Tue, 12 Jul 2005 13:38:13 -0500
I understand. I'd still add the following to your global exclusions list: exclude.dr "c:\adsm.sys" Our reporting software, Bocada was showing all these files in that c:\adsm.sys as missing. IBM told
Author: William Jean <wjean AT GLASSHOUSE DOT COM>
Date: Tue, 12 Jul 2005 14:36:25 -0400
You are getting the errors because the TSM server is running at 5.1. You will need to upgrade it to 5.2 before the errors will go away. Alternatively you can exclude the systemstate and systemservies
Author: David W Litten <dlitten AT DUKE-ENERGY DOT COM>
Date: Tue, 12 Jul 2005 14:46:53 -0400
Pull up the following link and do a find for string adsm.sys. You'll see that there was a bug where certain client versions included the adsm.sys folder even when explicitly excluded. http://www-1.ib
Author: "Mark D. Rodriguez" <mark AT MDRCONSULT DOT COM>
Date: Tue, 12 Jul 2005 13:57:28 -0500
Richard, I read th other replies that you got and some of them are good ideas like upgrading your TSM server code is definitely a good idea. Don't know if it is the cause of your problem though. If y
Author: Andrew Raibeck <storman AT US.IBM DOT COM>
Date: Tue, 12 Jul 2005 12:32:46 -0700
This was fixed in client level 5.3.0.0. In brief, the older client levels had a built-in EXCLUDE ?:\adsm.sys\...\*. Starting in 5.3, this was changed to an EXCLUDE.DIR for the adsm.sys directory in o