Remember this a few days ago...
Charlie H - Tecsys Inc.
-----Original Message-----
From: Charlie Hurtubise
Sent: Monday, October 18, 2004 2:55 PM
To: 'ADSM: Dist Stor Manager'
Subject: RE: TSMLVSACACHE files & Win2003
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:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Zoltan Forray/AC/VCU
Sent: Monday, October 18, 2004 2:38 PM
To: ADSM-L AT VM.MARIST DOT EDU
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 ?
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
PAC Brion Arnaud
Sent: Thursday, October 21, 2004 10:52 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: RC=12
Andrew,
We faced the same problem in our shop and found out that there was a
patch from microsoft we needed to get everything working OK. Take a look
here : http://support.microsoft.com/default.aspx?scid=kb;en-us;833167
and you'll be saved !
Cheers.
Arnaud
************************************************************************
******
Panalpina Management Ltd., Basle, Switzerland, CIT Department
Viadukstrasse 42, P.O. Box 4002 Basel/CH
Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 01
Direct: +41 (61) 226 19 78
e-mail: arnaud.brion AT panalpina DOT com
************************************************************************
******
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Meadows, Andrew
Sent: Thursday, 21 October, 2004 16:30
To: ADSM-L AT VM.MARIST DOT EDU
Subject: RC=12
I was wondering if anyone else has had this problem.
I have multiple windows 2003 servers that have TSM clients on them
ranging from 5.2.1.1 to 5.2.3.0 backing up to a AIX 5.1 server with TSM
server version 5.2.1.1. When the incremental backup starts the first
thing that it starts with is the System State. When TSM attempts to use
Virtual Shadow Copy in Windows it fails with a error message and
ultimately causes the backup to show as failed. Will attach error
message below received in dsmerror.log. I have checked on IBM's website
and all that is mentioned is that if Open File support is installed that
you may have problems.
http://www-1.ibm.com/support/docview.wss?rs=663&context=SSGSG7&q=windows
+server+2003&uid=swg21121552&loc=en_US&cs=utf-8&lang=en
Open file support is not on these machines and never has been. Has
anyone else seen this problem and if so how have you fixed it?
DSMerror.log ---
10/20/2004 23:15:35
fioGetAttrib(\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy27\WINDOWS\sy
stem32\CatRoot\{127D0A1D-4EF2-11D1-8608-00C04FC295EE}) failed.
********************************************
This message is intended only for the use of the Addressee and may
contain information that is PRIVILEGED and CONFIDENTIAL.
If you are not the intended recipient, you are hereby notified that any
dissemination of this communication is strictly prohibited.
If you have received this communication in error, please erase all
copies of the message and its attachments and notify us immediately.
Thank you.
********************************************
|
