Hi Adrian,

It appears that there is a problem with the
Windows VSS setup on the system.

I recommend calling IBM support. They will direct you to
perform the "DISKSHADOW Prereq Test".


http://www-01.ibm.com/support/docview.wss?uid=swg21403456&myns=swgtiv&mynp=OCSSTG2D&mync=R


This will remove TSM from the equation and make sure valid snapshots
can be created with the VSS subsystem and Exchange Server.
In the VSS world, this should be done before running TSM VSS snapshots,
to validate that the system is ready.

Thanks,

Del

----------------------------------------------------


"ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu> wrote on 09/30/2010
10:14:50 AM:

>> From: Adrian Compton <acompton AT ASPENPHARMA DOT COM>
>> To: ADSM-L AT vm.marist DOT edu
>> Date: 09/30/2010 10:15 AM
>> Subject: Re: TDP for Exchange 6.1.2
>> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu>
>>
>> Hi Del,
>>
>> Thanks for that. It fixed my problem, but now opened another.
>> Not being a Windows expert or never having used VSS I am a bit stumped.
>>
>> 30-09-2010 15:58:56 ANS5271E A Microsoft Volume Shadow Copy
>> Services writer is in an invalid state before snapshot initialization.
>> 30-09-2010 15:58:56 ANS5258E Microsoft volume shadow copy snapshot
>> initialization failed.
>> 30-09-2010 15:58:56 ANS1327W The snapshot operation for 'PLZVXMB01
>> \Microsoft Exchange Writer\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
>> \PLZXDB01\c6f3502e-7c4f-445e-a698-5a4fe1ebcd37' failed with error code:
4353.
>> 30-09-2010 15:58:56 ANS5258E Microsoft volume shadow copy snapshot
>> initialization failed.
>>
>> Any ideas? This happens even if I stop and start the Volume shadow
>> Copy Service
>>