ADSM-L

Re: [ADSM-L] Windows server patches screw things up (I know....what else is new....)

2008-08-18 11:47:14
Subject: Re: [ADSM-L] Windows server patches screw things up (I know....what else is new....)
From: Len Boyle <Len.Boyle AT SAS DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 18 Aug 2008 11:45:48 -0400
Zoltan,


Can you give a little more detail about the disk subsystem. What is the make 
and model?
San or local?, raid?, special firmware features? Etc.?

What service pack is Windows 2003 at? Have you installed the vss patches from 
last 2007?

len

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Zoltan Forray/AC/VCU
Sent: Monday, August 18, 2008 11:37 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Windows server patches screw things up (I know....what else 
is new....)

We are seeing new errors on various Windows 2003 servers, which we think
are related to recent M$ patches (so, what else is new).  The client
confirms that updates were applied on the same day the first failures
started.

The symptoms/error messages are:

08/15/2008 05:57:38 ANS1009W An error occurred processing the operating
system include/exclude statements.
The error was detected while processing:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToBackup\DRM.
RC = 13.
08/18/2008 02:04:34 ANS5250E An unexpected error was encountered.
   TSM function name : isVolumeSupported
   TSM function      : IsVolumeSupported() returned
'VSS_E_UNEXPECTED_PROVIDER_ERROR' for volume 'c:\'
   TSM return code   : 4353
   TSM file          : vssreq.cpp (5491)
08/18/2008 02:04:35 ANS5250E An unexpected error was encountered.
   TSM function name : vssCheckVolumeSupport
   TSM function      : isVolumeSupported() returned unexpected error for
volume '\\den3print\c$'
   TSM return code   : 4353
   TSM file          : vssback.cpp (3075)
08/18/2008 02:04:35 ANS5258E An error occurred initializing a VSS request.
For more information, see the TSM client error log.

Going back in the log for 2+ weeks does not show any of these errors.

This client is a 5.5.0.2 and I suggested upgrading to 5.5.1.1 as a
minimum.  I haven't been able to find anything definitive when searching
IBM.COM.


Any thoughts?