Do the following: Obtain hotfixes from Microsoft KB articles
KB934016, KB940349, KB951568 Apply these hotfixes - applicable for Windows 2003 SP2 and above. In windows dsm.opt files, put in a line TESTFLAGS VSSSYSTEMPROVIDER So dsm.opt may look like: PASSWORDACCESS GENERATE TCPSERVERADDRESS servername managedservices webclient schedule schedmode prompted tcpwindowsize 63 tcpbuffsize 32 txnbytelimit 25600 tcpnodelay yes resourceutilization 4 TESTFLAGS VSSSYSTEMPROVIDER DATEFORMAT 2 That seem to fix the system state backup issues very well. Dont forget, Microsoft best practice is also to do a system state backup to file as well via ntbackup. This can be scheduled as a task to run daily via a batch file (which is what we do here) . Let me know if you have issues with doing this but your windows engineers should be able to figure it out. The most important thing to do for a windows backup is to have the system state available, whether via ntbackup, or TSM, or preferably both. With the new fixes, ASR information can also be backed up by TSM for more efficient bare metal restores. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Mark Stapleton Sent: Saturday, 18 October 2008 1:34 AM To: [email protected] Subject: Re: [ADSM-L] WIndows2003 VSS errors From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Crosskey, Adam - Corporate Core - ICT Services > I have a solution it seems. > Microsoft KB940184 details repairing corruption to a registry key > concerned with the vss writes. > If you are suffering from VSS errors during TSM backups (and when the > Scheduler starts), and get no output from the VSSADMIN LIST WRITERS > command at the windows cmd line, follow the instructions in KB940184. > I only had to complete the first step (although the COM+ service hung > and I needed to reboot) to resolve the issue. ...and herein lies a lesson that we learn when we work with TSM. Because TSM uses naught but vendor APIs when working with an OS, the vast majority of problems we have with backups (though not all, certainly) lay with issues within the OS or hardware--not TSM itself. -- Mark Stapleton ([EMAIL PROTECTED]) CDW Berbee System engineer 7145 Boone Avenue North, Suite 140 Brooklyn Park MN 55428-1511 763-592-5963 www.berbee.com <html> <body> <font face="arial" color=#808080 size="-2"><img alt="Santos Logo" src="http://www.santos.com/library/logo.gif";> <br>Santos Ltd A.B.N. 80 007 550 923<br> Disclaimer: The information contained in this email is intended only for the use of the person(s) to whom it is addressed and may be confidential or contain privileged information. If you are not the intended recipient you are hereby notified that any perusal, use, distribution, copying or disclosure is strictly prohibited. If you have received this email in error please immediately advise us by return email and delete the email without making a copy.</font> <font face="arial" color=#008000 size="-2">Please consider the environment before printing this email</font> </body> </html>
![http://www.santos.com/library/logo.gif"](http://www.santos.com/library/logo.gif"){kind=link}