Hi Del
Thanks so much. I followed all your suggestions, and it is working.
It has now been running for ages how ever doing a "Exchange integrity Check for
component 'JNBXDB01'"
Is this normal to take so long? Brand new Exchange server on 2008 R2 with only
20 odd users?
Regards
Adrian Compton
Group IT Infrastructure
Aspen Pharmacare
8 Gibaud Street, Korsten, Port Elizabeth, 6014
P O Box 4002
Korsten
Port Elizabeth
6014
Switchboard Tel No: +27 (0) 41 407 2111 Direct Tel No: +27 (0) 41 407 2855
Fax:+27 (0) 41 453 7452 Cell:+27 (0) 82 861 7745
This email is solely for the named addressee. Any unauthorized use or
interception of this email, or the review, retransmission, dissemination or
other use of, or taking of any action in reliance upon the contents of this
email, by persons or entities other than the intended recipient, is prohibited.
If you are not the named addressee please notify us immediately by way of a
reply e-mail, and also delete this email and any attached files.
Disclaimer: You must scan this email and any attached files for viruses and/or
any other defects. Aspen accepts no liability for any loss, damages or
consequence, whether direct, indirect, consequential or economic, however
caused, and whether by negligence or otherwise, which may result directly or
indirectly from this communication or of any attached files.
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Del Hoobler
Sent: Thursday, September 30, 2010 16:35
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] TDP for Exchange 6.1.2
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
>>
|
