Quantcast
Channel: Backup – Windows and Windows Server forum
Viewing all articles
Browse latest Browse all 3921

Windows Server 2008 R2 Ent - Windows Server Backup, VSS, SPP, ASR Writer errors while trying to run Bare metal recovery backup

$
0
0

My Bare metal recovery protection started failing this week on a Windows Server 2008 R2 Ent. SP1 machine.  The machine in question is an Exchange 2010 SP2 Enterprise UR 4 v2 database server.  This server is protected by Microsoft System Center Data Protection Manager 2010 ver 3.0.7707.0.  I don't believe the problem is DPM 2010 related as I get the same errors when using Windows Server Backup.  I have rebooted the server and disabled the antivirus software but still had the same errors.  Here are the relative alerts, event viewer logs and list writer details:

 Affected area: Computer\System Protection

Occurred since: 9/11/2013 9:24:21 AM

Description: The replica of System Protection Computer\System Protection on [Server Name] is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check. You can recover data from existing recovery points, but new recovery points cannot be created until the replica is consistent.

For SharePoint farm, recovery points will continue getting created with the databases that are consistent. To backup inconsistent databases, run a consistency check on the farm. (ID 3106)

DPM cannot create a backup because Windows Server Backup (WSB) on the protected computer encountered an error (WSB Event ID: 521, WSB Error Code: 0x807800A1). (ID 30229 Details: Internal error code: 0x809909FB)

More information

Recommended action: For resolution actions and more information on the WSB error, go to http://technet.microsoft.com/en-us/library/cc734488(WS.10).aspx.

Synchronize with consistency check.

Run a synchronization job with consistency check...

Resolution: To dismiss the alert, click below

Inactivate alert

__________________________

Log Name: Application

Source: GroupShield for Exchange

Date: 9/10/2013 4:01:43 PM

Event ID: 2053

Task Category: None

Level: Error

Keywords: Classic

User: N/A

Computer: [Server Name]

Description:

An update failed with error 80004005:Unspecified error

.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name="GroupShield for Exchange" />

<EventID Qualifiers="49152">2053</EventID>

<Level>2</Level>

<Task>0</Task>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2013-09-10T23:01:43.000000000Z" />

<EventRecordID>1887171</EventRecordID>

<Channel>Application</Channel>

<Computer>[server name]</Computer>

<Security />

</System>

<EventData>

<Data>An update failed with error 80004005:Unspecified error

.</Data>

</EventData>

</Event>

 

_______________________________________

Log Name: Application

Source: VSS

Date: 9/10/2013 8:03:51 PM

Event ID: 8193

Task Category: None

Level: Error

Keywords: Classic

User: N/A

Computer: [Server Name]

Description:

Volume Shadow Copy Service error: Unexpected error calling routine IVssAsrWriterBackup::GetAsrMetadata. hr = 0x80042411, A critical volume selected for backup exists on a disk which cannot be backed up by ASR.

.

Operation:

PrepareForBackup event

Context:

Execution Context: ASR Writer

Execution Context: Writer

Writer Class Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}

Writer Name: ASR Writer

Writer Instance ID: {1cff496d-41d5-400d-ae3e-ef06d16f8f3a}

Error-specific details:

ASR Writer: A critical volume selected for backup exists on a disk which cannot be backed up by ASR. (0x80042411)

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="2013-09-11T03:03:51.000000000Z" />

<EventRecordID>1887528</EventRecordID>

<Channel>Application</Channel>

<Computer>[server name]</Computer>

<Security />

</System>

<EventData>

<Data>IVssAsrWriterBackup::GetAsrMetadata</Data>

<Data>0x80042411, A critical volume selected for backup exists on a disk which cannot be backed up by ASR.

</Data>

<Data>

Operation:

PrepareForBackup event

Context:

Execution Context: ASR Writer

Execution Context: Writer

Writer Class Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}

Writer Name: ASR Writer

Writer Instance ID: {1cff496d-41d5-400d-ae3e-ef06d16f8f3a}

Error-specific details:

ASR Writer: A critical volume selected for backup exists on a disk which cannot be backed up by ASR. (0x80042411)</Data>

<Binary>2D20436F64653A20575254415352574330303030303439312D2043616C6C3A20575254415352574330303030303336362D205049443A202030303030373431322D205449443A202030303031303935322D20434D443A2020433A5C57696E646F77735C73797374656D33325C76737376632E6578652020202D20557365723A204E616D653A204E5420415554484F524954595C53595354454D2C205349443A532D312D352D313820</Binary>

</EventData>

</Event>

_________________________________________________

Log Name: Application

Source: VSS

Date: 9/10/2013 8:03:51 PM

Event ID: 12290

Task Category: None

Level: Warning

Keywords: Classic

User: N/A

Computer: [Server Name]

Description:

Volume Shadow Copy Service warning: ASR writer Error 0x80042411. hr = 0x00000000, The operation completed successfully.

.

Operation:

PrepareForBackup event

Context:

Execution Context: ASR Writer

Execution Context: Writer

Writer Class Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}

Writer Name: ASR Writer

Writer Instance ID: {1cff496d-41d5-400d-ae3e-ef06d16f8f3a}

Error-specific details:

ASR Writer: A critical volume selected for backup exists on a disk which cannot be backed up by ASR. (0x80042411)

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name="VSS" />

<EventID Qualifiers="0">12290</EventID>

<Level>3</Level>

<Task>0</Task>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2013-09-11T03:03:51.000000000Z" />

<EventRecordID>1887529</EventRecordID>

<Channel>Application</Channel>

<Computer>[server name]</Computer>

<Security />

</System>

<EventData>

<Data>ASR writer Error 0x80042411</Data>

<Data>0x00000000, The operation completed successfully.

</Data>

<Data>

Operation:

PrepareForBackup event

Context:

Execution Context: ASR Writer

Execution Context: Writer

Writer Class Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}

Writer Name: ASR Writer

Writer Instance ID: {1cff496d-41d5-400d-ae3e-ef06d16f8f3a}

Error-specific details:

ASR Writer: A critical volume selected for backup exists on a disk which cannot be backed up by ASR. (0x80042411)</Data>

<Binary>2D20436F64653A20575254415352574330303030303530372D2043616C6C3A20575254415352574330303030303632372D205049443A202030303030373431322D205449443A202030303031303935322D20434D443A2020433A5C57696E646F77735C73797374656D33325C76737376632E6578652020202D20557365723A204E616D653A204E5420415554484F524954595C53595354454D2C205349443A532D312D352D313820</Binary>

</EventData>

</Event>

____________________________________________________________________

Log Name: Application

Source: SPP

Date: 9/10/2013 8:03:52 PM

Event ID: 16387

Task Category: None

Level: Error

Keywords: Classic

User: N/A

Computer: [Server Name]

Description:

Shadow copy creation failed because of error reported by ASR Writer. More info: A critical volume selected for backup exists on a disk which cannot be backed up by ASR. (0x80042411).

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name="SPP" />

<EventID Qualifiers="0">16387</EventID>

<Level>2</Level>

<Task>0</Task>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2013-09-11T03:03:52.000000000Z" />

<EventRecordID>1887530</EventRecordID>

<Channel>Application</Channel>

<Computer>[server name]</Computer>

<Security />

</System>

<EventData>

<Data>ASR Writer</Data>

<Data>A critical volume selected for backup exists on a disk which cannot be backed up by ASR. (0x80042411)</Data>

<Binary>01000000C70F0000B60F00000000000042BEB7C511CAC619E59C92030000000000000000</Binary>

</EventData>

</Event>

____________________________________________________________

Log Name: Application

Source: Microsoft-Windows-Backup

Date: 9/10/2013 8:03:52 PM

Event ID: 521

Task Category: None

Level: Error

Keywords:

User: SYSTEM

Computer: [Server Name]

Description:

The backup operation that started at '2013-09-11T03:03:47.135000000Z' has failed because the Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed with following error code '2155348129'. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name="Microsoft-Windows-Backup" Guid="{1DB28F2E-8F80-4027-8C5A-A11F7F10F62D}" />

<EventID>521</EventID>

<Version>0</Version>

<Level>2</Level>

<Task>0</Task>

<Opcode>0</Opcode>

<Keywords>0x8000000000000000</Keywords>

<TimeCreated SystemTime="2013-09-11T03:03:52.127320700Z" />

<EventRecordID>1887531</EventRecordID>

<Correlation />

<Execution ProcessID="13604" ThreadID="13740" />

<Channel>Application</Channel>

<Computer>[server name]</Computer>

<Security UserID="S-1-5-18" />

</System>

<EventData>

<Data Name="BackupTime">2013-09-11T03:03:47.135000000Z</Data>

<Data Name="ErrorCode">2155348129</Data>

<Data Name="ErrorMessage">%%2155348129</Data>

</EventData>

</Event>

__________________________________________________________

 

C:\Windows\system32>vssadmin list writers

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool

(C) Copyright 2001-2005 Microsoft Corp.

Writer name: 'Task Scheduler Writer'

Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}

Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}

State: [1] Stable

Last error: No error

Writer name: 'VSS Metadata Store Writer'

Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}

Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}

State: [1] Stable

Last error: No error

Writer name: 'Performance Counters Writer'

Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}

Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}

State: [1] Stable

Last error: No error

Writer name: 'System Writer'

Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}

Writer Instance Id: {ed950359-2cad-461a-873b-bdd046000966}

State: [7] Failed

Last error: Timed out

Writer name: 'Microsoft Exchange Replica Writer'

Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}

Writer Instance Id: {b5559414-7331-4a89-8d17-89871a63a453}

State: [1] Stable

Last error: No error

Writer name: 'ASR Writer'

Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}

Writer Instance Id: {a5f6a80f-f22b-49a5-a08d-072da184fea1}

State: [1] Stable

Last error: No error

Writer name: 'IIS Config Writer'

Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}

Writer Instance Id: {76b64d25-a9df-4e14-b6d0-b0274b8ff1e1}

State: [7] Failed

Last error: Timed out

Writer name: 'Shadow Copy Optimization Writer'

Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}

Writer Instance Id: {42553c30-0cc9-4e1b-a831-859e897acd2c}

State: [1] Stable

Last error: No error

Writer name: 'COM+ REGDB Writer'

Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}

Writer Instance Id: {bf27a9f0-7582-40d7-a719-644489f527e6}

State: [1] Stable

Last error: No error

Writer name: 'Registry Writer'

Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}

Writer Instance Id: {bda99211-4a64-44e1-99b6-18c8254915e2}

State: [1] Stable

Last error: No error

Writer name: 'Microsoft Exchange Writer'

Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}

Writer Instance Id: {8332ce01-9e39-4ed1-85b9-478b21f72406}

State: [1] Stable

Last error: No error

Writer name: 'WMI Writer'

Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}

Writer Instance Id: {09cc108f-ae08-4a0c-baac-5c173e6257b4}

State: [7] Failed

Last error: Timed out

Writer name: 'IIS Metabase Writer'

Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}

Writer Instance Id: {32ce72f0-7a03-490b-a934-53e90309ffb7}

State: [7] Failed

Last error: Timed out

Writer name: 'BITS Writer'

Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}

Writer Instance Id: {850c2165-9b09-4057-b3c1-31bca9b882e6}

State: [1] Stable

Last error: No error

Writer name: 'Cluster Database'

Writer Id: {41e12264-35d8-479b-8e5c-9b23d1dad37e}

Writer Instance Id: {2935b6c1-6e2a-410c-b75f-5511cd67d6be}

State: [7] Failed

Last error: Timed out



Viewing all articles
Browse latest Browse all 3921

Trending Articles



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