I've installed a DPM 2010 and pushed the agents to two Exchange 2010 mailbox servers.  I'm getting "Replica is inconsistent" on both servers when I create a protection group and attempt to create teh first copy.  I've tried to perform a "Consisteny check" but it quickly fails.

Firewalls are off on both servers and DPM server

Below are the errors from the servers that are failing. 

Volume Shadow Copy Service error: Error creating the Shadow Copy Provider COM class with CLSID {65ee1dba-8ff4-4a58-ac1c-3470ee2f376a} [0x80070422, The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
].

Operation:
   Obtain a callable interface for this provider
   Check If Volume Is Supported by Provider
   Add a Volume to a Shadow Copy Set

Context:
   Provider ID: {b5946137-7b9f-4925-af80-51abd60b20d5}
   Class ID: {00000000-0000-0000-0000-000000000000}
   Snapshot Context: 0
   Execution Context: Coordinator
   Provider ID: {b5946137-7b9f-4925-af80-51abd60b20d5}
   Volume Name: \\?\Volume{9ea6bf62-de8c-11df-94bf-806e6f6e6963}\
   Execution Context: Coordinator

Volume Shadow Copy Service information: The COM Server with CLSID {65ee1dba-8ff4-4a58-ac1c-3470ee2f376a} and name SW_PROV cannot be started. [0x80070422, The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
]

Operation:
   Obtain a callable interface for this provider
   Check If Volume Is Supported by Provider
   Add a Volume to a Shadow Copy Set

Context:
   Provider ID: {b5946137-7b9f-4925-af80-51abd60b20d5}
   Class ID: {00000000-0000-0000-0000-000000000000}
   Snapshot Context: 0
   Execution Context: Coordinator
   Provider ID: {b5946137-7b9f-4925-af80-51abd60b20d5}
   Volume Name: \\?\Volume{9ea6bf62-de8c-11df-94bf-806e6f6e6963}\
   Execution Context: Coordinator

This has been an ongoing issue for quite awhile now.  IT seems that after I reboot the Exchange Server, I can get a good systems state backup for a couple of days.  Then it starts failing.  Looking on the Mail server, vss admin list writers; shows that some of the writers are stuck in " waiting for completion" :

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\profilename>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative comman
(C) Copyright 2001 Microsoft Corp.

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {949796fd-40d3-4bfb-98bc-a5bf39c9a708}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'Microsoft Exchange Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {4d56c16d-8ea9-47df-94b7-8df2402fb08c}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {be44aa15-6b03-497a-af1d-713f3504345d}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'Event Log Writer'
   Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
   Writer Instance Id: {da56c48d-c1f2-46cb-b1b5-70ae1f0e12f0}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {2dd0c117-fb84-4e19-9305-7fcb2a342a16}
   State: [1] Stable
   Last error: No error

Writer name: 'MSDEWriter'
   Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
   Writer Instance Id: {fbf3e4e0-19fd-4f94-b74a-711ed4209fed}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {f235096c-5015-4bf9-9fbb-7bb16aea01bb}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {f93cd428-f9b5-4088-be43-a86fa4e55ce6}
   State: [5] Waiting for completion
   Last error: No error

After a restart, these clear up, and I am able grab the system state; however rebooting the mail server every night is not a viable option.

Anybody have any ideas ?

Greetings,

i had DPM 2007 and it worked with Exchange 2003. I even had DPM 2010 RC running for a year and the Exchange 2010 backup worked.

Now i moved to DPM 2010 and the backup is failing.

The error i am seeing is : Dtaa consistency verifcation check failed on LOGS of Storage Group on server.companydomainname (ID: 30146 Details: Unknown error (0xffffffc01) (0xFFFFFFC01)

The recommendation is to get the right version of ESE and ESEUTIL, which i have done. i mean it was working before.

Thanks for the help.

I am using exchange 2003 SP2 and DPM 2012 and need to recover a users mailbox from a tape backup.  I set up the recovery and select to bring the database to a clean shutdown and save it to a network folder.  The problem is that the backup restore completes in DPM but all that is saved int he folder is the LOG files and the STM file, no EDB file so I can try and restore it with eseutil etc.   Any ideas why this is happening?  On the DPM options on the clean shutdown it says the exchange version is 6.5.7638.2 but if I look on my ESM console it says 6.5.7638.1   is this the issue?  I just do not see why it completes the backup and the EDB file is actually there the whole time right up until when its about to complete the EDB file is then removed.  I cannot copy the file at any point either as it says it is in use. 

Any ideas?

Hi,

I have a DPM 2007 server which is protecting Exchange cluster. There are a total of 15 storage groups. Recovery point is getting created for all storage groups except for one (SG07), which says "Can not perform creation of a recovery point because the replica is not idle. (ID : 141) Wait for the ongoing job to complete or cancel the job in the Monitoring task area."

However when I go to jobs tab, I do not see any ongoing job for that particular data storage group.

I checked the application logs on Exchange server, there was this VSS error:

Log Name:      Application
Source:        VSS
Date:          6/18/2012 8:32:29 AM
Event ID:      8193
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      exchange.corporateroot.net
Description:
Volume Shadow Copy Service error: Unexpected error calling routine ConvertStringSidToSid.  hr = 0x80070539.

Operation:
   OnIdentify event
   Gathering Writer Data

Context:
   Execution Context: Shadow Copy Optimization Writer
   Writer Class Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Name: Shadow Copy Optimization Writer
   Writer Instance ID: {24b48334-ea3f-4d88-af89-711f4ac3f9fa}
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="VSS" />
    <EventID Qualifiers="0">8193</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-06-18T06:32:29.000Z" />
    <EventRecordID>280389158</EventRecordID>
    <Channel>Application</Channel>
    <Computer>exchange.corporateroot.net</Computer>
    <Security />
  </System>
  <EventData>
    <Data>ConvertStringSidToSid</Data>
    <Data>0x80070539</Data>
    <Data>

Operation:
   OnIdentify event
   Gathering Writer Data

Context:
   Execution Context: Shadow Copy Optimization Writer
   Writer Class Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Name: Shadow Copy Optimization Writer
   Writer Instance ID: {24b48334-ea3f-4d88-af89-711f4ac3f9fa}</Data>
    <Binary>2D20436F64653A20534543534543524330303030303838322D2043616C6C3A20534543534543524330303030303837352D205049443A202030303031353436382D205449443A202030303031353836302D20434D443A2020433A5C57696E646F77735C73797374656D33325C76737376632E6578652020202D20557365723A204E5420415554484F524954595C53595354454D20202020202D205369643A2020532D312D352D3138</Binary>
  </EventData>
</Event>

On the Exchange server, all writers are stable, except this one :

Writer name: 'Microsoft Exchange Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {58fb8dc1-5d47-4733-9d04-6aad0d070e67}
   State: [5] Waiting for completion
   Last error: No error

Are these related by any chance? If yes, why is only SG07 not getting backed up while all other storage groups are? Please help.

Regards,

Pavit

Hi All,

I am busy moving esx virtual exchange servers to hyperv. I want to be able to do host and guest level backups  of the exchange vm. My concern is that on the host level backup of the virtual exchange servers that it will truncate the log files and I will have problems when the giuest level exchange backups run due to the "missing" log files.

I have looked at http://support.microsoft.com/kb/975354 but the hotfix apparently does not apply to my host server 2008 r2 datacentre. Also the registry entry does not exist.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Virtualization\VssRequestor
Name: BackupType
Type: REG_DWORD
Value: 0 or 1

It tells me to create the entry, but I think it refers to the entry BackupType but I do not even have Virtualization\VssRequestor. Must I create the whole entry or am I missing something here.

Would also like to hear how other people combine the host and guest level backup of exchange virtual servers (2003\2007\2010) and what schedules they run.

Please advise.

DPM 2010  server 2008r2 x64 with latest hotfixes and Exchange 2010 sp2 On 2008r2 x64.  DPM server shows Agent not reachable and Exchange server shows "The DPMRA service terminated unexpectedly.  It has done this 42 time(s)".  Exchange server also has SCOM.  I've removed/reinstalled SCOM and DPM agent on machine and the problem reappears.  It works for a day or so, then the problem returns.  This is a 3 node cluster.

Relevant part of the dpm logs:

38E8    1DBC    06/29    08:00:58.071    31    vssbaserequestor.cpp(946)    [0000000003424EE0]        NORMAL    QueryStatus returned 0x4230a, Releasing VssAsync [0000000000543210]
38E8    1DBC    06/29    08:00:58.071    31    vsssnapshotrequestor.cpp(236)    [0000000003424EE0]        NORMAL    CVssSnapshotRequestor::AddComponentForSnapshot [0000000003424EE0]
38E8    1DBC    06/29    08:00:58.087    31    vsssnapshotrequestor.cpp(347)    [0000000003424EE0]        NORMAL    CVssSnapshotRequestor::AddVolumeForSnapshot [0000000003424EE0]
38E8    1DBC    06/29    08:00:58.087    03    clusterutil.cpp(1758)            WARNING    ClusterResourceTypeOpenEnum failed for resource type Volume Manager Disk Group with windows error 5078
38E8    1DBC    06/29    08:00:58.087    03    clusterutil.cpp(1758)            WARNING    ClusterResourceTypeOpenEnum failed for resource type GeoCluster Replicated Disk with windows error 5078
38E8    1DBC    06/29    08:00:58.087    03    clusterutil.cpp(2145)    [0000000003BCED50]        WARNING    Failed: Hr: = [0x8007001f] Either the volume \\?\Volume{4a99e7db-b66b-49ff-a06c-027ddb29d26a}\ is offline or the volume is not a clustered disk.

38E8    1DBC    06/29    08:00:58.087    31    vsssnapshotrequestor.cpp(379)            NORMAL    ssLocalVolumeGuid = [\\?\Volume{4a99e7db-b66b-49ff-a06c-027ddb29d26a}\], ssClusterVolGuid=[\\?\Volume{4a99e7db-b66b-49ff-a06c-027ddb29d26a}\]
38E8    1DBC    06/29    08:00:58.087    31    vsssnapshotrequestor.cpp(390)    [0000000003424EE0]        NORMAL    CVssSnapshotRequestor: AddVolumeForSnapshot - Marked volume E:\ to be snapshot
38E8    1DBC    06/29    08:00:58.087    31    vsssnapshotrequestor.cpp(424)    [0000000003424EE0]        NORMAL    CVssSnapshotRequestor::StartPrepareForBackup [0000000003424EE0]

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!

Hy.

I have one question regarding DPM 2010 protection of Exchange in DAG environment. Can someone please explain what is the proper way to do a backup. Should i backup only passive databases, only active or both? I suppose that by backing up passive copy logs will be truncated properly on all other databases? If I am only using one DPM server, what are the benefits of backing up all active and passive Exchange databases?

Thnx.

Gurmeet Singh

Im wondering about the different between when you run Sync and Full backup in Exchange.

Does the VSS act the same? Does the essential check for data integrity runs even when you run Sync?

What is the different in Exchange DBs when you run Sync vs Full backup?

Some detail information about what is actually happenning in the background will be appreciate it.

Thanks in advance!

ITLAAL

Hi,

We are planning to use DPM 2010 to backup all our servers.

We have an Exchange 2003 cluster and we are having some difficulties backing up the databases. It fails with the following error:

DPM encountered an error while performing an operation for
\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy629\Program Files\Microsoft\
Exchange Server\Mailbox\First Storage Group\mdb01.edb on mailserver.domain.local
(ID 2033 Details: The system cannot find the file specified (0x80070002))

If we try to run a manual Consistency Check, it fails again, but with another mdb.

Does anyone have an idea, what's going wrong?

Thanks in advance!

/Michael

When configuring the protection group for an Exchange 2010 DAG all recommendations I've seen point to selecting the Exchange DB which selects all DAG members. When this is done say for a 2 node DAG there is a section to have one member be the Full Backup and the other to be the Copy Backup.

So once the protection begtins working I am seeing both DAG members in the protection group which have backed up the data. My question is:

Is DPM essentially backing up both members therefore I have 2 copies of the same data using up twice the space?

Running EX2010 with DPM and for the past month been getting 9782 errors on my Mailbox server. In DPM, however, the backup looks fine for both the MB and the PF. Prior all backups and log truncations worked fine..nothing has changed otehr than the normal windows updates for servers (no exchange patches).

Hi,

Have a single Exchange 2010 server with single database. When I go to protect with DPM 2010 I get error message

The selected datasource(s) cannot be configured for copy backup because it is either a standalone mailbox db or a dr replica (ID: 32528)

The Full button is greyed out.

Thanks in advance

Gurmeet Singh

Hi Guys,

We are running DPM 2010 on a Windows Server 2008 R2 Standard edtion. We are backing up our Exchange 2007 storage group through DPM 2010. However for these past few days, it's not backing up one of our storage group and we're getting this error below. 

Creation of recovery points for MSG1 on exchange2007.domain.com have failed.
The last recovery point creation failed for the following reason: (ID: 3114) DPM has detected a discontinuity in the log chain for MSG1 on exchange2007.domain.com since the last synchronization. (ID: 30216)
  
   3114
   a95cf972-a37d-4ef6-9630-e1eb47c234d2
   dpm2010.domain.com
   exchange2007.domain.com
   a95cf972-a37d-4ef6-9630-e1eb47c234d2
     
   Recovery point creation failures
   678994be-5e20-47a4-ab7c-95bcd5e7d817
   Creation of recovery points for MSG1 on exchange2007.domain.com have failed. The last recovery point creation failed for the following reason: (ID: 3114) DPM has detected a discontinuity in the log chain for MSG1 on exchange2007.domain.com since the last synchronization. (ID: 30216)
   30216
   1
   86600.0068916

Below are the steps we did to try to resolve issue:

1. Confirmed that Circular Logging is Disabled on the specified storage group.

2. In DPM Administrator Console, in the Protection task area, select the volume, click Create recovery point, and then, in the Actions pane, click Express full backup.

3. Run a consistency check (Currently the protected storage now shows that the "Replica is Inconsistent")

4. Stopped the protection for the specified storage group and deleted all the replica from the disk.

5. Add the specified storage group again to the protection group and run consistency check but it still appears as "Replica Inconsistent"

6. Restart Exchange Information Store and run consistency check again as what this link (http://www.buchatech.com/category/microsoft/data_protection_manager/) suggested but it didn't work.

All these steps that we did didn't solve the issue. The specified storage group still appear "Replica Inconsisten" on the protection tab of our DPM 2010 console. Your help will be much appreciated. Thanks in advance!

Hi,

Short question.

Is there already support for the Exchange 2013 Preview version in DPM 2012 (SP1).

Many Thanks,

Matthijs