Quantcast
Channel: Data Protection Manager - Exchange protection forum
Viewing all articles
Browse latest Browse all 442

Exchange 2007 - DPM2010 Encoutered a retryable VSS Error (ID 30112)

$
0
0

Hello Everybody,

On one of our servers were DPM in installed we receive the following errors while synchronizing recovery points for the First & Second storage group.
Every 15 minutes we do a synchronization, and every 15 minutes only the First & Second storage group errors when trying create the recovery points.
The exchange 2007 server is part of an Windows 2008 SBS server which is virtualized with Hyper-V.

In DPM 2010 we receive the following error when start creating recovery points:

Type: Recovery point
Status: Failed
Description: DPM encountered a retryable VSS error. (ID 30112 Details: VssError:The writer experienced a transient error.  If the backup process is retried,
the error may not reoccur.
 (0x800423F3))
 More information
End time: 24-11-2011 12:30:19
Start time: 24-11-2011 12:30:05
Time elapsed: 00:00:13
Data transferred: 0 MB
Cluster node -
Recovery Point Type Incremental Sync
Source details: First Storage Group
Protection group: XXX Share System en SQL

If I check the Application Log of the SBS server, then following events occur every 15 minutes:
The same events occur also for the Second Storage Group

EventID 9706
Exchange VSS Writer (instance f133cb57-2338-4ff9-b5f4-a7358459627f) failed with error code 1296 when collecting private metadata information for storage group 'First Storage Group' in preparation for backup.

EventID 9705
Exchange VSS Writer (instance f133cb57-2338-4ff9-b5f4-a7358459627f) failed with error code 1296 when preparing components (storage groups) for backup.

EventID 9607
Exchange VSS Writer (instance f133cb57-2338-4ff9-b5f4-a7358459627f) failed with error code 1296 when preparing for backup.

EventID 12289
Volume Shadow Copy Service error: Unexpected error VSS_E_WRITER_STATUS_NOT_AVAILABLE. An older active writer session state is being overwritten by a newer session. The most common cause is that the number of parallel backups has exceeded the maximum supported limit.  hr = 0x80042409.

Operation:
   Aborting Writer

Context:
   Maximum supported sessions: 64
   Completed sessions: 8
   Active sessions: 64
   Aborted sessions: 0
   Writer failed sessions: 64
   New snaphot set: {f133cb57-2338-4ff9-b5f4-a7358459627f}
   Old snapshot set: {2934751a-3bc9-4d03-80c4-bc36bed60394}
   Old operation: 1001
   Old state: 7
   Old failure: 0x800423f3
   Writer Class Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Name: Microsoft Exchange Writer
   Writer Instance Name: Exchange Information Store
   Writer Instance ID: {51fdfbe0-2b30-40cb-ae81-85be13de9928}

I discovered that when I run a full backup, the First & Second Storage Group are running and succeed. When I do an Incremental Backup it fails.
If I do a; vssadmin list writers is see that the Exchange Writer is stable, but has a retryable error, state 7 failed.

Could anyone help me with this problem!
Thanks in advance!



Viewing all articles
Browse latest Browse all 442

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>