ADSM-L

Re: [ADSM-L] VSS Hotfix list for Windows 2008

2009-10-15 17:15:07
Subject: Re: [ADSM-L] VSS Hotfix list for Windows 2008
From: Cory Heikel <cheikel AT HMC.PSU DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 15 Oct 2009 17:13:23 -0400
Sergio,

Let me know how you make out with this. We are experiencing similar
problems which my gut kept telling me had to do with the vss. We have an
open ticket with IBM, but no real answers yet. One thing we did find was
that if you add -systemstate to the opt file thei system doesn't hang or
crash.  Good luck!

Cory

Cory Heikel
Tivoli Systems Administrator
Hershey Medical Center
(717) 531-7972

>>> "Sergio O. Fuentes" <sfuentes AT UMD DOT EDU> 10/15/2009 5:09 PM >>>
The only indication that it's a VSS issue is the fact that the crash or
hang happens during or immediately after the System state backup.
There's nothing in the logs because the crash occurs abruptly.  Even
Window event logs don't show any sort of error message or STOP event.
The hotfixes I listed previously fix issues that cause crashes or hangs,
so I'm going to recommend installing those for the sake of eliminating
that potential cause.

vssadmin list writers shows no errors or failed writers but this is on
a system that has recovered from a crash.  I'd have to have some amount
of clairvoyance to run this command right before a crash since it
happens at such random times.  First, I'll apply these hotfixes.  Are
they any others to apply?

Thanks!

Sergio

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
Of Tchuise, Bertaut
Sent: Thursday, October 15, 2009 1:19 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] VSS Hotfix list for Windows 2008

Sergio,

What specific error messages pertaining to TSM do you see in the
dsmerror.log file? While running vssadmin list writers, are there any
writers that show state of failure?

Thanks.

BERTAUT TCHUISE
TSM/NetApp Storage Administrator
Legg Mason Technology Services
*410-580-7032
BTchuise AT leggmason DOT com


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
Of
Sergio O. Fuentes
Sent: Thursday, October 15, 2009 1:05 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] VSS Hotfix list for Windows 2008

Hi all,

We're running Windows 2008 to serve Exchange in a clustered
environment.
Nodes on the cluster have intermittently crashed during the TSM 5.5.2
client backup run (or immediately after).  This run backs up the C:
drive and system state.  I have suspicions that VSS is the culprit
(and
not necessarily TSM).  Does IBM or MS have any comprehensive VSS
hotfix
list that should address some of these issues?

I see this page for MS: http://support.microsoft.com/kb/940349
I see this page on IBM's site:
http://www-01.ibm.com/support/docview.wss?uid=swg21242128&loc=en_US&lang

=en

Problem is that these are only for Windows 2003.  I'm looking for
something similar but for Windows 2008.  Workarounds aren't really an
option here since I don't have admin rights to these machines, so a
hotfix is really what I'm looking for.

I have this list from my own research.  The first one seems to be
indicative of what we're seeing:

http://support.microsoft.com/kb/953531
http://support.microsoft.com/kb/950267
http://support.microsoft.com/kb/957522

Does anyone have any additional hotfixes that may apply here?  I
appreciate your help.

Thanks!

Sergio

IMPORTANT:  E-mail sent through the Internet is not secure. Legg Mason
therefore recommends that you do not send any confidential or sensitive
information to us via electronic mail, including social security
numbers, account numbers, or personal identification numbers. Delivery,
and or timely delivery of Internet mail is not guaranteed. Legg Mason
therefore recommends that you do not send time sensitive
or action-oriented messages to us via electronic mail.

This message is intended for the addressee only and may contain
privileged or confidential information. Unless you are the intended
recipient, you may not use, copy or disclose to anyone any information
contained in this message. If you have received this message in error,
please notify the author by replying to this message and then kindly
delete the message. Thank you.