From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] 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 (mark.stapleton AT cdw DOT com)
CDW Berbee
System engineer
7145 Boone Avenue North, Suite 140
Brooklyn Park MN 55428-1511
763-592-5963
www.berbee.com