Ref TSM Win2003 Clients 5.3.2.1, 5.3.2.4 I've just been through this on Windows 2003 Server since TSM version 5.3.2.1. I just installed TSM 5.3.2.4, but I am still getting an occasional Win2003 Service crash.
To avoid the C:\tsmlvsacache directory from taking all the free space on C:\ (and you have to reboot to clear it out), I first added to dsm.opt the snapshotcachesize option, then I added the following options to turn off Open File Support, to make them "dynamic", as documented in the readme... DOMAIN E: F: L: * --- OFS (Open File Supt) goes to C:\tsmlvsa\tsmlvsacache. Blowing 9 GIGs on C: snapshotcachesize 4 * --- Don't snapshot (OFS) these disks include.fs e: fileleveltype=dynamic *** Added f: and l: Oct 17-04 CH include.fs f: fileleveltype=dynamic include.fs l: fileleveltype=dynamic Not a terrible show stopper, but I'm almost tempted to go back to WinClient 5.2 for awhile. Pioneers always get arrows in the back. Charlie Hurtubise Tecsys Inc. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Zoltan Forray/AC/VCU Sent: Monday, October 18, 2004 2:38 PM To: [EMAIL PROTECTED] Subject: TSMLVSACACHE files When building a recent Windows 2003 server, the TSM LVSA (Open File Support) was installed. I just found a document on IBM.COM that says that this configuration is NOT SUPPORTED but due to Shadow Copy services, the LVSA may "negatively interact with the TSM LVSA ". Well, it has. It has sucked-up every bit of free space (80GB) in 500MB chunks in the TSMLVSACACHE directory. Since we need to reboot the box to disable LVSA, it might be an issue due to this being a Domino service. In the meantime, can I delete the contents of the TSMLVSACACHE directory ?
