ADSM-L

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

2013-02-26 16:14:32
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:12:38 +0000
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.


-----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:07 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] TSM TDP EXCHANGE INCREMENTAL BACKUP

Hi Jeannie,

Did the problem still happen after restarting the Microsoft Exchange 
Replication service?
... or are you waiting for the next schedule to run?

How about the DSMERROR.LOG file in the "baclient" directory?
What's in there? This file will have the best chance to contain the error. Keep 
in mind that DP/Exchange VSS backups utilize the BA Client "DSMAGENT" for the 
snapshots and data movement, therefore you need to look in the DSMERROR.LOG 
file for related DSMAGENT logging.

Thanks,

Del

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

"ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu> wrote on 02/26/2013
03:56:22 PM:

> From: Jeanne Bruno <JBruno AT CENHUD DOT COM>
> To: ADSM-L AT vm.marist DOT edu,
> Date: 02/26/2013 03:57 PM
> Subject: Re: TSM TDP EXCHANGE INCREMENTAL BACKUP Sent by: "ADSM: Dist 
> Stor Manager" <ADSM-L AT vm.marist DOT edu>
>
> Hello.  We are not using hardware for VSS.
> I did a 'vssadmin list writer' and noticed there was a 'replication 
> error', so I restarted the Microsoft Exchange Replication service.
> Vssadmis list writers showed no errors after that.
>
> Errors from logs:
> 02/25/2013 15:09:01 ANS1909E The scheduled command failed.
> 02/25/2013 15:09:01 ANS1512E Scheduled event 'TDP_WKD_EXCHDB1'
> failed.  Return code = 418.
>
> Current date is:
> Mon 02/25/2013
> Current time is:
> 03:01 PM
> ---------------------
> Return code was 418
> =====================
>
> 02/25/2013 15:00:16 --- SCHEDULEREC QUERY BEGIN
> 02/25/2013 15:00:16 --- SCHEDULEREC QUERY END
> 02/25/2013 15:00:16 Next operation scheduled:
> 02/25/2013 15:00:16
> ------------------------------------------------------------
> 02/25/2013 15:00:16 Schedule Name:         TDP_WKD_EXCHDB1
> 02/25/2013 15:00:16 Action:                Command
> 02/25/2013 15:00:16 Objects:               "c:\Program Files\Tivoli
> \TSM\TDPExchange\excincr.cmd"
> 02/25/2013 15:00:16 Options:
> 02/25/2013 15:00:16 Server Window Start:   15:00:00 on 02/25/2013
> 02/25/2013 15:00:16
> ------------------------------------------------------------
> 02/25/2013 15:00:16
> Executing scheduled command now.
> 02/25/2013 15:01:23
> Executing Operating System command or script:
>    "c:\Program Files\Tivoli\TSM\TDPExchange\excincr.cmd"
> 02/25/2013 15:09:01 Finished command.  Return code is: 418
> 02/25/2013 15:09:01 ANS1909E The scheduled command failed.
> 02/25/2013 15:09:01 ANS1512E Scheduled event 'TDP_WKD_EXCHDB1'
> failed.  Return code = 418.
>
>
> Event log:
> VSS shadow copy set ID '{33c33fc0-1f5f-4643-9be8-77ed210bb828}' has 
> been started.
> Signaling VSS writers to prepare for a backup operation.
> VSS writers have prepared for a backup operation.
> Failure Executing Schedule TDP_WKD_EXCHDB1, RC=418.