ADSM-L

Re: [ADSM-L] TSM TDP EXCHANGE INCREMENTAL BACKUP

2013-02-26 16:38:28
Subject: Re: [ADSM-L] TSM TDP EXCHANGE INCREMENTAL BACKUP
From: Jeanne Bruno <JBruno AT CENHUD DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 26 Feb 2013 21:36:24 +0000
Do you happen to know what the recommended sp level of exchange is?
And also the Recommended level of tdp?


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Del Hoobler
Sent: Tuesday, February 26, 2013 4:18 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] TSM TDP EXCHANGE INCREMENTAL BACKUP

VSS_E_WRITERERROR means that the Exchange Server is having an issue.
I recommend opening a PMR to take this to the next step.


Thanks,

Del

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

"ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu> wrote on 02/26/2013
04:12:38 PM:

> From: Jeanne Bruno <JBruno AT CENHUD DOT COM>
> To: ADSM-L AT vm.marist DOT edu,
> Date: 02/26/2013 04:13 PM
> Subject: Re: TSM TDP EXCHANGE INCREMENTAL BACKUP Sent by: "ADSM: Dist 
> Stor Manager" <ADSM-L AT vm.marist DOT edu>
>
> Sorry, I meant to include the DSMerror.log.
>
> I restarted Exchange Replication service first and then the schedule 
> kicked off.  Still failed.
>
> Dsmerror:
> 02/25/2013 15:07:21 ANS0361I DIAG: VssRequestor::checkWriterStatus:
> VssRequestor::checkWriterStatus failed with
hr=VSS_E_WRITERERROR_RETRYABLE
> 02/25/2013 15:07:21 ANS5268W The Microsoft Volume Shadow Copy Services 
> writer 'Microsoft Exchange Replica Writer' current state
> (VSS_WS_STABLE) is not valid for the current operation.
> 02/25/2013 15:07:51 ANS0361I DIAG: VssRequestor::checkWriterStatus:
> VssRequestor::checkWriterStatus failed with
hr=VSS_E_WRITERERROR_RETRYABLE
> 02/25/2013 15:07:51 ANS5268W The Microsoft Volume Shadow Copy Services 
> writer 'Microsoft Exchange Replica Writer' current state
> (VSS_WS_STABLE) is not valid for the current operation.
> 02/25/2013 15:08:21 ANS0361I DIAG: VssRequestor::checkWriterStatus:
> VssRequestor::checkWriterStatus failed with
hr=VSS_E_WRITERERROR_RETRYABLE
> 02/25/2013 15:08:21 ANS5268W The Microsoft Volume Shadow Copy Services 
> writer 'Microsoft Exchange Replica Writer' current state
> (VSS_WS_STABLE) is not valid for the current operation.
> 02/25/2013 15:08:52 ANS0361I DIAG: VssRequestor::checkWriterStatus:
> VssRequestor::checkWriterStatus failed with
hr=VSS_E_WRITERERROR_RETRYABLE
> 02/25/2013 15:08:52 ANS5268W The Microsoft Volume Shadow Copy Services 
> writer 'Microsoft Exchange Replica Writer' current state
> (VSS_WS_STABLE) is not valid for the current operation.
> 02/25/2013 15:08:52 ANS5272E A Microsoft Volume Shadow Copy Services 
> writer is in an invalid state after snapshot initialization.
> 02/25/2013 15:08:52 ANS5258E Microsoft volume shadow copy snapshot 
> initialization failed.
> 02/25/2013 15:08:52 ANS1327W The snapshot operation for 'EXCHANGE1 
> \Microsoft Exchange Writer\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
> \DB2\178dbfd6-f84e-4749-b9f3-332304166a9a' failed with error code: 4353.
> 02/25/2013 15:08:52 ANS1327W The snapshot operation for 'EXCHANGE1 
> \Microsoft Exchange Writer\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
> \DB3\596ceca2-f9f1-463f-babb-3a76eb4f2011' failed with error code: -1.
> 02/25/2013 15:08:52 ANS5258E Microsoft volume shadow copy snapshot 
> initialization failed.
> 02/25/2013 15:08:52 ANS5283E The operation was unsuccessful.