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

Windows 2008 R2 Ent x64 Web server - backup fails with error 0x800423F3

$
0
0

Windows Server 2008 R2 with SP1 x64, running as IIS server. Not a domain member.

I am trying to do a System State backup to a local D: drive. The backups fail as follows:

Windows Server Backup error:

The operation was stopped. Detailed error: The volume shadow copy operation failed
with error 0x800423F3. View the event log for more information.


In Event Viewer, the following error shows:

Log Name:      Application
Source:        Microsoft-Windows-Backup
Date:          7/22/2015 3:14:32 PM
Event ID:      521
Task Category: None
Level:         Error
Keywords:
User:          SYSTEM
Computer:      MYSERVER
Description:
The backup operation that started at '?2015?-?07?-?22T19:08:21.380000000Z' 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="2015-07-22T19:14:32.255126300Z" /><EventRecordID>1624</EventRecordID><Correlation /><Execution ProcessID="7544" ThreadID="5216" /><Channel>Application</Channel><Computer>MYSERVER</Computer><Security UserID="S-1-5-18" /></System><EventData><Data Name="BackupTime">2015-07-22T19:08:21.380000000Z</Data><Data Name="ErrorCode">2155348129</Data><Data Name="ErrorMessage">%%2155348129</Data></EventData></Event>

Running 'vssadmin list writers' after the backup failure shows the following:

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: {9176b774-b7e5-4497-855e-5e0bcee6e87c}
   State: [9] Failed
   Last error: Timed out

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {1ba0828b-6441-48b5-bf6d-112d93b2d0b1}
   State: [9] Failed
   Last error: Timed out

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {0bfd75f8-5da2-4fcf-b8af-9bf9796a145c}
   State: [9] Failed
   Last error: Timed out

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {10d13dd9-e5fd-4e47-8471-08df1ae46b04}
   State: [9] Failed
   Last error: Timed out

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {92cb5b23-aab6-4b5f-987c-a62a296b178e}
   State: [9] Failed
   Last error: Timed out

Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {e13a0edc-6597-455e-ba69-d2140c55ef73}
   State: [9] Failed
   Last error: Timed out

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {9a066e74-5011-40d5-ae32-57688d0b099e}
   State: [9] Failed
   Last error: Timed out

Restarting the appropriate services or the server resets all of the writers to stable, but the issue reoccurs on the next backup.

The only thing that has helped has been to stop the website (using 'appcmd stop site mysite'), running the backup, and then restarting the site. Then the backup succeeds.

Any suggestions?




Viewing all articles
Browse latest Browse all 3323

Trending Articles



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