Windows backup fails
We are trying to backup server 2008, hyper v host, with 2 vms. Windows backup fails: the system writer is not found in the backup.
Event log error:
Log Name: Application
Source: Microsoft-Windows-Backup
Date: 11/22/2014 9:10:26 PM
Event ID: 521
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: VM01
Description:
The backup operation that started at '2014-11-23T02:00:25.981000000Z' 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 '2155348001'. Please review the event
details for a solution, and then rerun the backup operation once the issue is resolved.
Nothing we seem to try fixes this any idea's would be appreciated
Hi David,
The problem can occur due to the following reasons:
Not enough space inside the virtual machine's VHD.
The Integration services installed is not installed.
The OS is unable to auto-mount the snapshotted VHDs during the backup process.
Also have a look at the following link and see if the symptom matches your problem:
http://blogs.technet.com/b/asiasupp/archive/2011/08/01/windows-server-backup-failed-to-backup-with-error-0x81000101.aspx
Regards
Markus
Similar Messages
-
Windows 7: Windows Backup failed 0x81000031
Windows backup ran, and my once-pristine and empty backup drive now has something filling its space, so I assume some files were successfully backed up. Thing is, the Action Center icon has the red x on it and it comes up with one issue: Check, your backup (Important). Clicking this issue produces the following dialog:
Windows Backup: Troubleshooting Options
Check your backup
Windows Backup failed while determining libraries location of one of the users included in the backup.
Details: BitLocker Drive Encryption cannot be used because critical BitLocker system files are missing or corrupted. Use Windows Startup Repair to restore these files to your computer.
Options:
*Try to run backup again
*Change backup settings
Error code: 0x81000031
Thing is, I'm using home premium. I don't see bitlocker as an option and I'm not terribly enthused about having to repair bitlocker when I can't use it to begin with. (Primarily, because I use Windows 7 Home Premium. Even if I used a version which supported bit locker, I'd never use it to begin with - I lack a TPM chip which means that anybody who has physical access to my machine could compromise my security regardless of bitlocker, it'd just take slightly longer for them if bitlocker were present.)
I'm digressing, the point is I don't use bitlocker and I don't know how not having bitlocker prevents Windows 7 from copying files from one drive to another and making a note in a logfile that the files were backed up. I realize I simplify the method of backing files up but it doesn't get much more complex than copying them to a separate location and timestamping them.
tl;dr: Windows Backup produced error code 0x81000031 because bitlocker drive encryption cannot be used. I don't want to use bit locker drive encryption I just want to back my files up to an external drive. Suggestions? Preferably ones that don't make me run Windows Startup Repair.Well 4 years later same problem simple fix, did every thing else as suggested by microsoft sys repair start up repair etc etc and just removing the drive that was included in library fixed the issue i have spent hours on
now have to reinstall all that sys restore removed...SO EVERYBODY do what Sneha said first..
Clicked "Start", then "Computer".
Right clicked on the "Library" I wanted to modify, and selected "properties".
Immediately saw that my DVD drive was an included folder in the library.
Clicked on the drive in the list, and the Remove Button became active.
Clicked on "Remove" and it removed the drive from the list.
Clicked on "Incude Folder" and added in my real backup folder location (not required, I just want a libray connection to
it).
Clicked on "Ok". thanks ath1234 for the process..Cheers -
The Volume Shadow Copy service initially was running under the context of System, so we thought that ‘System’ doesn’t have permissions to access network shares.
When the Volume Shadow Copy service was running under the context of System, this was the error logged:
“failed with following error code '0x8078014B' (There was a failure in creating a directory on the backup storage location.).”
Which is likely due to not having permissions to write to the network location.
This is a scheduled backup trying to write to a network location, so we changes the service to run under the context of an account that does have permissions to write to the network share.
Then the error changed to this:
“failed with following error code '0x8078006B' (Windows Backup failed to create the shared protection point on the source volumes.).”
HRESULT 0x8078006b
DetailedHRESULT 0x8004230f
ErrorMessage %%2155348075
BackupState 12
VolumesInfo <VolumeInfo><VolumeInfoItem Name="C:" OriginalAccessPath="C:" State="15" HResult="-2139619228" DetailedHResult="0" PreviousState="0" IsCritical="1" IsIncremental="0"
BlockLevel="0" HasFiles="1" HasSystemState="0" IsCompacted="0" IsPruned="0" IsRecreateVhd="0" FullBackupReason="0" DataTransferred="0" NumUnreadableBytes="0" TotalSize="0"
TotalNoOfFiles="0" Flags="1604" BackupTypeDetermined="0" SSBTotalNoOfFiles="0" SSBTotalSizeOnDisk="0" /><VolumeInfoItem Name="D:" OriginalAccessPath="D:" State="15" HResult="-2139619228"
DetailedHResult="0" PreviousState="0" IsCritical="0" IsIncremental="0" BlockLevel="0" HasFiles="1" HasSystemState="0" IsCompacted="0" IsPruned="0" IsRecreateVhd="0"
FullBackupReason="0" DataTransferred="0" NumUnreadableBytes="0" TotalSize="0" TotalNoOfFiles="0" Flags="68" BackupTypeDetermined="0" SSBTotalNoOfFiles="0" SSBTotalSizeOnDisk="0"
/></VolumeInfo>
We aren’t really seeing anything that gives any hint on what the issue is.
Any ideas? Thanks in advance!We are trying to back up folders/files from 2 local drives (C: & D:), both of which have only 10% space used, and 100 GB free.
We are attempting to back the files up to a Remote Shared File (and there is 100+ GB free space out there).
If we try another network location, we receive the exact same error.
This is Windows Server 2012, not running Hyper-V and is a physical server not a VM.
Thank you for the link.
Looking in:
Event Viewer / Application and Service Logs / Microsoft / Windows / Backup / Operational
But it doesn’t seem to give any more details:
Log Name:
Microsoft-Windows-Backup
Source:
Microsoft-Windows-Backup
Date:
7/8/2013 8:00:12 PM
Event ID:
5
Task Category: None
Level:
Error
Keywords:
User:
SYSTEM
Computer:
servername.edu
Description:
The backup operation that started at '2013-07-09T02:00:06.273000000Z' has failed with following error code '0x8078006B' (Windows Backup failed to create the shared protection point on the source volumes.).
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>5</EventID>
<Version>3</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000000000000</Keywords>
<TimeCreated SystemTime="2013-07-09T02:00:12.872602100Z" />
<EventRecordID>30</EventRecordID>
<Correlation />
<Execution ProcessID="3028" ThreadID="3996" />
<Channel>Microsoft-Windows-Backup</Channel>
<Computer>servername.edu</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BackupTemplateID">{A421E864-A115-4288-8D12-F4878CF8A248}</Data>
<Data Name="HRESULT">0x8078006b</Data>
<Data Name="DetailedHRESULT">0x8004230f</Data>
<Data Name="ErrorMessage">%%2155348075</Data>
<Data Name="BackupState">12</Data>
<Data Name="BackupTime">2013-07-09T02:00:06.273000000Z</Data>
<Data Name="BackupTarget">\\servername\BACKUP</Data>
<Data Name="NumOfVolumes">2</Data>
<Data Name="VolumesInfo"><VolumeInfo><VolumeInfoItem Name="C:" OriginalAccessPath="C:" State="15" HResult="-2139619228" DetailedHResult="0" PreviousState="0" IsCritical="1" IsIncremental="0" BlockLevel="0" HasFiles="1" HasSystemState="0"
IsCompacted="0" IsPruned="0" IsRecreateVhd="0" FullBackupReason="0" DataTransferred="0" NumUnreadableBytes="0" TotalSize="0" TotalNoOfFiles="0" Flags="1604" BackupTypeDetermined="0" SSBTotalNoOfFiles="0" SSBTotalSizeOnDisk="0" /><VolumeInfoItem
Name="D:" OriginalAccessPath="D:" State="15" HResult="-2139619228" DetailedHResult="0" PreviousState="0" IsCritical="0" IsIncremental="0" BlockLevel="0" HasFiles="1" HasSystemState="0" IsCompacted="0" IsPruned="0" IsRecreateVhd="0" FullBackupReason="0" DataTransferred="0"
NumUnreadableBytes="0" TotalSize="0" TotalNoOfFiles="0" Flags="68" BackupTypeDetermined="0" SSBTotalNoOfFiles="0" SSBTotalSizeOnDisk="0" /></VolumeInfo></Data>
<Data Name="SourceSnapStartTime">2013-07-09T02:00:06.289250300Z</Data>
<Data Name="SourceSnapEndTime">1601-01-01T00:00:00.000000000Z</Data>
<Data Name="PrepareBackupStartTime"><TimesList><Time Time="1601-01-01T00:00:00.000Z" /><Time Time="1601-01-01T00:00:00.000Z" /></TimesList></Data>
<Data Name="PrepareBackupEndTime"><TimesList><Time Time="1601-01-01T00:00:00.000Z" /><Time Time="1601-01-01T00:00:00.000Z" /></TimesList></Data>
<Data Name="BackupWriteStartTime"><TimesList><Time Time="1601-01-01T00:00:00.000Z" /><Time Time="1601-01-01T00:00:00.000Z" /></TimesList></Data>
<Data Name="BackupWriteEndTime"><TimesList><Time Time="1601-01-01T00:00:00.000Z" /><Time Time="1601-01-01T00:00:00.000Z" /></TimesList></Data>
<Data Name="TargetSnapStartTime">1601-01-01T00:00:00.000000000Z</Data>
<Data Name="TargetSnapEndTime">1601-01-01T00:00:00.000000000Z</Data>
<Data Name="DVDFormatStartTime"><TimesList></TimesList></Data>
<Data Name="DVDFormatEndTime"><TimesList></TimesList></Data>
<Data Name="MediaVerifyStartTime"><TimesList></TimesList></Data>
<Data Name="MediaVerifyEndTime"><TimesList></TimesList></Data>
<Data Name="BackupPreviousState">2</Data>
<Data Name="ComponentStatus"><ComponentStatus></ComponentStatus></Data>
<Data Name="ComponentInfo"><ComponentInfo></ComponentInfo></Data>
<Data Name="SSBEnumerateStartTime">1601-01-01T00:00:00.000000000Z</Data>
<Data Name="SSBEnumerateEndTime">1601-01-01T00:00:00.000000000Z</Data>
<Data Name="SSBVhdCreationStartTime">1601-01-01T00:00:00.000000000Z</Data>
<Data Name="SSBVhdCreationEndTime">1601-01-01T00:00:00.000000000Z</Data>
<Data Name="SSBBackupStartTime">1601-01-01T00:00:00.000000000Z</Data>
<Data Name="SSBBackupEndTime">1601-01-01T00:00:00.000000000Z</Data>
<Data Name="SystemStateBackup"><SystemState IsPresent="0" HResult="0" DetailedHResult="0" /></Data>
<Data Name="BMR"><BMR IsPresent="0" HResult="0" DetailedHResult="0" /></Data>
<Data Name="VssFullBackup">false</Data>
<Data Name="UserInputBMR">false</Data>
<Data Name="UserInputSSB">false</Data>
<Data Name="BackupSuccessLogPath">
</Data>
<Data Name="BackupFailureLogPath">
</Data>
<Data Name="EnumerateBackupStartTime"><TimesList><Time Time="1601-01-01T00:00:00.000Z" /><Time Time="1601-01-01T00:00:00.000Z" /></TimesList></Data>
<Data Name="EnumerateBackupEndTime"><TimesList><Time Time="1601-01-01T00:00:00.000Z" /><Time Time="1601-01-01T00:00:00.000Z" /></TimesList></Data>
<Data Name="PruneBackupStartTime"><TimesList><Time Time="1601-01-01T00:00:00.000Z" /><Time Time="1601-01-01T00:00:00.000Z" /></TimesList></Data>
<Data Name="PruneBackupEndTime"><TimesList><Time Time="1601-01-01T00:00:00.000Z" /><Time Time="1601-01-01T00:00:00.000Z" /></TimesList></Data>
<Data Name="BackupFlags">0x9</Data>
<Data Name="ComponentInfoSummary"><ComponentInfoSummary ComponentInfoArrayPresent="1" TotalComponents="0" SucceededComponents="0" /></Data>
</EventData>
</Event> -
Hello,
When I try to run a system state backup with this command: wbadmin start systemstatebackup -backuptarget:<drive letter>
I get the error
"Failed to create the shared protection point on the source volumes.
ERROR - Volume Shadow Copy Service operation error (0x8004230f)
The shadow copy provider had an unexpected error while trying to process the specified operation."
I'm not sure how to fix this. I'm logged into the machine as an Administrator.
Windows Server Enterprise 2008 SP2 64-bit
Any suggestions??After I re-registered the dll, I'm still getting the same error in the command window. The DLL registers successfully and the "MS Software Shadow Copy Provider" starts fine.
Two errors in the Event Viewer:
1.)
Log Name: Application
Source: Microsoft-Windows-Backup
Date: 1/21/2014 10:11:25 AM
Event ID: 521
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: mfacs-server-7.gs.umt.edu
Description:
Backup started at '1/21/2014 5:11:11 PM' failed as Volume Shadow copy operation failed for backup volumes with following error code '2155348075'. Please rerun backup once 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="2014-01-21T17:11:25.287Z" />
<EventRecordID>11410</EventRecordID>
<Correlation />
<Execution ProcessID="4964" ThreadID="3528" />
<Channel>Application</Channel>
<Computer>mfacs-server-7.gs.umt.edu</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BackupTime">2014-01-21T17:11:11.920Z</Data>
<Data Name="ErrorCode">2155348075</Data>
<Data Name="ErrorMessage">%%2155348075</Data>
</EventData>
</Event>
2.)
Log Name: Application
Source: VSS
Date: 1/21/2014 10:11:24 AM
Event ID: 12293
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: mfacs-server-7.gs.umt.edu
Description:
Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details EndPrepareSnapshots({40d86592-3a48-4d38-afab-0e4a7b8bb8f1}) [hr = 0x8000ffff].
Operation:
Executing Asynchronous Operation
Context:
Current State: DoSnapshotSet
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="VSS" />
<EventID Qualifiers="0">12293</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-01-21T17:11:24.000Z" />
<EventRecordID>11409</EventRecordID>
<Channel>Application</Channel>
<Computer>mfacs-server-7.gs.umt.edu</Computer>
<Security />
</System>
<EventData>
<Data>{b5946137-7b9f-4925-af80-51abd60b20d5}</Data>
<Data>EndPrepareSnapshots({40d86592-3a48-4d38-afab-0e4a7b8bb8f1})</Data>
<Data>0x8000ffff</Data>
<Data>
Operation:
Executing Asynchronous Operation
Context:
Current State: DoSnapshotSet</Data>
<Binary>2D20436F64653A20434F52534E50534330303030313630392D2043616C6C3A20434F52534E50534330303030313539302D205049443A202030303030323732302D205449443A202030303030343139322D20434D443A2020433A5C57696E646F77735C73797374656D33325C76737376632E6578652020202D20557365723A204E5420415554484F524954595C53595354454D20202020202D205369643A2020532D312D352D3138</Binary>
</EventData>
</Event>
Results of vssadmin list writers:
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: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {f3c10044-4938-4d49-9f2d-789c571a6428}
State: [7] Failed
Last error: No error
Writer name: 'SqlServerWriter'
Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Instance Id: {aaa19109-d447-40ec-b71e-2a8fbaed55ad}
State: [7] Failed
Last error: No error
Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {f64b2bfa-fd68-4729-bebb-7e281b144fc5}
State: [7] Failed
Last error: No error
Writer name: 'DPM Writer'
Writer Id: {0074a271-4f24-43e0-9ec7-28a44189cb80}
Writer Instance Id: {38646851-4a56-4499-b90c-181a839cae95}
State: [1] Stable
Last error: No error
Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {7ae6130c-b116-44a9-87a4-4b8bee461131}
State: [7] Failed
Last error: No error
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {62a5b392-a50f-4703-8c23-acb5590efcd1}
State: [7] Failed
Last error: No error
Writer name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
Writer Instance Id: {1615a920-5ec9-43d0-b6ff-a5b767430623}
State: [1] Stable
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {f22b72f6-940b-42c9-a824-80858e6f5f5c}
State: [7] Failed
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {4c603239-dd36-4343-aba7-73858e574e39}
State: [7] Failed
Last error: No error
C:\Windows\system32>
Thanks! -
SBS 2008 Standard - Windows Backup fails first time after every reboot
Backup runs successfully every night.
Once server is rebooted first backup fails, then subsequent backups succeed OK.
So much so that we run the backup manually and let it error (pretty much straight away) then let it run again successfully at 10pm.
Backs up to external hard drive on rotation.
I think it's a VSS issue - has anyone else had this? What did you do to resolve?
Thanks,
J.Hi,
According to the Event ID 521, please refer to the following article. you will get detailed explains.
Event ID 521 — Backup Operations
http://technet.microsoft.com/en-us/library/cc734453(v=WS.10).aspx
Based on all error messages that you provided, it seems that backup issue caused by sqlwriter.exe. So, please
temporarily disable SQL Server related services and then check if this issue can be solved. It will help us to confirm if this issue was related to SQL Server.
Meanwhile, would you please let me know if you have installed available update rollup for your SBS 2008 Standard?
Hope this helps.
Best regards,
Justin Gu -
Time Machine not working since Yosemite was installed.
I had this issue too and went through all the great suggestion found on this site, but finally was able to resolve it after looking at the system.log to see the reason it was failing. By using terminal and entering:
sudo grep backupd /var/log/system.log
I saw "Backup failed with error:11". Then looking above, I saw many "Error: (-36) SrcErr:YES /Applications/" messages. After "Applications" I saw the culprit files that were causing Time Machine to fail. I deleted some Apps that I didn't need and found Time Machine would get farther than before. I then looked at the system.log again and saw it failing on the remaining Apps. I was able to use Time Machine to restore these App directories from a couple months ago before the Time Machine was failing. Now the problem is resolved. Whew! It seemed to be choking on corrupt files and these can be corrected by restoring earlier ones that were not corrupted.
Well, I thought I should share this with others that may have run into the same issue so they can save time. Hope it helps! -
Problems both seemed to appear about the same time and may be related.
Had backups on an external drive prior to the problem and appeared to be working. I have since cleaned the external drive in an attempt to start a new backup series but it continues to stop and report backup has failed.
The System restore was working fine and one day it had changed all the existing Restore Points to "System Image restore point"
but still showed all the different dates. In the System Properties window it indicates that there are 0 bytes in "current usages",
which I assume they are all empty but I can't create any new ones. I get Error code 0x80042308.
I have tried the Clean Boot with no results. I use MS Security Essentials for virus protection.
I have no other symptoms or problems on the PC.
About ready for a Recovery and start all over.
George M1Hi,
Your first step should be to run chkdsk /r /f on all the drives in that computer. Shadow copy errors are often caused by disk problems (usually minor) which chkdsk will find and correct.
Also, this issue can be caused that VSS dlls are corrupted.
Re-install the VSS dlls by following these steps:
a. Using command prompt, CD to the WINDOWS\system32 directory
b. Stop the Volume Shadow Copy service by executing the command "net stop vss"
c. Register the following DLLs and services by executing these commands:
regsvr32 ole32.dll
regsvr32 vss_ps.dll
Vssvc /Register
regsvr32 /i swprv.dll
regsvr32 /i eventcls.dll
regsvr32 es.dll
regsvr32 stdprov.dll
regsvr32 vssui.dll
regsvr32 msxml.dll
regsvr32 msxml3.dll
regsvr32 msxml4.dll
Hope these could be helpful.
Kate Li
TechNet Community Support -
Setting up of Windows backup failing
I've added a 2TB USB drive (Western Digital MyBook) to a new 2012 Essentials server to allow Server Backup to perform a secondary (non-cloud) backup. The setup routine is failing during (or immediately after) formatting with the message "The system
cannot find the file specified". Sometimes, when I try to repeat the process, I get an error in a snap-in of the MMC (blbmmc.dll). Where should I be looking to troubleshoot this please?Hello Milos
Thank you for replying. Looking at this more closely, the error occurs when the summary status of the Backup Schedule Wizard changes from "Formatting" to "Modifying existing schedule", which would suggest the wizard can't find the existing
config.
I can't find any error codes because this error is not being reported in Event Viewer. I have no other backup configured.
Best - Anthony -
System State Backup fail. Writer name: 'NTDS' : State: [11] Failed : Last error: Non-retryable error
Hello!!! Everybody,
I have Win Server 2008 R2 contain Domain controller (No Hyper-V). I have to take "SYSTEM STATE DATA BACKUP". I have ran following command on this Server.
c:\>wbadmin start systemstatebackup -backuptarget:d:
but backup was not successful & I got following error in command prompt.
" A VOLUME SHADOW COPY SERVICE OPERATION HAS OCCURRED : <0X800423f4>. THE WRITER EXPERIENCED A NON-TRANSIENT ERROR. IF THE BACKUP PROCESS IS RETRIED,THE ERROR IS LIKELY TO REOCCUR."
I also ran following command to know exact problem.
c:\>vssadmin list writers
I got following error
Writer name: 'NTDS'
Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
Writer Instance Id: {21c57902-5037-467b-b9a3-72ed41c9723e}
State: [11] Failed
Last error: Non-retryable error
I also checked Event Viewer & got following 3 noserror.
(1) Event ID : 8229, Source : VSS
A VSS writer has rejected an event with error 0x800423f4, The writer experienced a non-transient error. If the backup process is retried, the error is likely reoccur.
Process ID : 608
(2) Event Id : 412, Source : ESENT. Task Category: Logging/Recovery
lsass (636) Unable to read the header of log file "\\?\Globalroot\device\harddiskvolumeshadowcopy2\Windows\NTDS\edb.log".Error:546
(3)Event Id : 521 Source : Backup
The backup operation that started at '2014-05-13T01:44:31.444000000Z' 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.
I have also restart the server but problem is not resolved. I have no SQL in my Server.
I also re-register the VSS components with the help of following website.
Website Link : https://kb.acronis.com/content/45776
You are requested please solve my problem on very urgent basis.You can refer below link for your issue
http://waynestorey.com/blog/2012/01/18/windows-backup-fails-with-event-id-521-error-code-2155348129/
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Mai Ali | My blog: Technical | Twitter:
Mai Ali -
Windows Backup creates "locked" directory on SMB share
I'm trying to back up my Windows 7 laptop to my Mac Mini over SMB.
Normal non-backup file operations work okay, from the desktop: I can create folders, drag files, delete files, etc.
But Windows Backup fails, because it creates a directory on the SMB share that--despite ACLs--OS X won't let anyone create files within, or change the security settings. The only option is to rm -rf the directory.
The ACLs look like this (the directory Windows Backup creates is called 'MEGALITH'. I tried creating a parent directory (called 'Megalith') with inherited ACLs, but to no avail:
sarsen:Megalith root# ls -le .
total 0
drwx------+ 2 windowsbackupuser staff 68 Jan 8 12:49 MEGALITH
0: user:root inherited allow list,add_file,search,delete,add_subdirectory,delete_child,readattr,writeattr,re adextattr,writeextattr,readsecurity,writesecurity,chown,file_inherit,directory_i nherit
1: group:admin inherited allow list,add_file,search,delete,add_subdirectory,delete_child,readattr,writeattr,re adextattr,writeextattr,readsecurity,writesecurity,chown,file_inherit,directory_i nherit
2: user:_spotlight inherited allow list,search,file_inherit,directory_inherit
Even with these ACLs, I cannot chown the MEGALITH directory. Nor can I edit its ACLs in the Server window.
My SMB config is:
sarsen$ defaults read /Library/Preferences/SystemConfiguration/com.apple.smb.serve r
AclsEnabled = 1;
AllowGuestAccess = 0;
AllowNTLM2Auth = 1;
DOSCodePage = 437;
EnabledServices = (
disk
LocalKerberosRealm = "LKDC:SHA1.C5D430A59786EE0CC0515EEF37A77A538C6D612A";
NetBIOSName = sarsen;
ServerDescription = sarsen;
Workgroup = WORKGROUP;
"wins server" = (
And the error log says:
Jan 8 12:49:27 sarsen.nerdgod.com digest-service[711]: digest-request: init request
Jan 8 12:49:27 sarsen.nerdgod.com digest-service[711]: digest-request: init return domain: SARSEN server: SARSEN
Jan 8 12:49:27 sarsen.nerdgod.com digest-service[711]: digest-request: uid=0
Jan 8 12:49:27 sarsen.nerdgod.com digest-service[711]: digest-request: od failed with 2 proto=ntlmv1-with-v2-session
Jan 8 12:49:27 sarsen.nerdgod.com digest-service[711]: digest-request: user=SARSEN\\windowsbackupuser
Jan 8 12:49:27 sarsen.nerdgod.com digest-service[711]: digest-request kdc: ok user=SARSEN\\windowsbackupuser proto=ntlmv1 flags: NEG_KEYEX, ENC_128, NEG_VERSION, NEG_TARGET_INFO, NEG_NTLM2, NEG_ALWAYS_SIGN, NEG_NTLM, NEG_SIGN, NEG_TARGET, NEG_UNICODEFor interoperability with Windows clients, this is absolutely 100% bad behavior:
http://support.microsoft.com/kb/326549
Note Unlike the Read-only attribute for a file, the Read-only attribute for a folder is typically ignored by Windows, Windows components and accessories, and other programs. For example, you can delete, rename, and change a folder with the Read-only attribute by using Windows Explorer.
The Read-only and System attributes is only used by Windows Explorer to determine whether the folder is a special folder, such as a system folder that has its view customized by Windows (for example, My Documents, Favorites, Fonts, Downloaded Program Files), or a folder that you customized by using the Customize tab of the folder's Properties dialog box. As a result, Windows Explorer does not allow you to view or change the Read-only or System attributes of folders. When a folder has the Read-Only attribute set it causes Explorer to request the Desktop.ini of that folder to see if any special folder settings need to be set. It has been seen where if a network share that has a large amount of folders set to Read-only, it can cause Explorer to take longer then what is expected to render the contents of that share while it waits on the retrieval of the Desktop.ini files. The slower the network connectivity to the share the longer this process can take to the point where Explorer may timeout waiting for the data and render nothing or appear to hang.
Note In some previous versions of Windows, you can change the Read-only attribute for folders by using the Properties dialog box for the folder, but no versions of Windows permit you to change the System attribute by using Windows Explorer. -
Windows Server 2008 R2 Backup failing with error - 0x8004231F
Hi,
I have Windows Server 2008 R2 Web Edition. Everything was working fine until recently. I tried checking for the log files, but I see that there are no log files that are created now in the location C:\Windows\Logs\WindowsServerBackup. The only files that
are being created recently are of the type mentioned below.
Wbadmin.1.etl
WbadminUI.0.etl
etc.
I tried removing the old backup and starting a new backup. But, even now it is failing with the same error.
When running the backup from the PowerShell, the output is as below.
PS C:\Users\administrator> Wbadmin start backup -backupTarget:\\localhost\E$\WindowsImageBackup\Server01 -systemState -vss
Copy
wbadmin 1.0 - Backup command-line tool
(C) Copyright 2004 Microsoft Corp.
Note: The backed up data cannot be securely protected at this destination.
Backups stored on a remote shared folder might be accessible by other
people on the network. You should only save your backups to a location
where you trust the other users who have access to the location or on a
network that has additional security precautions in place.
Retrieving volume information...
This will back up volume System Reserved (100.00 MB) (Selected Files),SAN(I:) (Selected Files),Local Disk(C:) (Selected
Files) to \\localhost\E$\WindowsImageBackup\Server01.
Do you want to start the backup operation?
[Y] Yes [N] No y
The backup operation to \\localhost\E$\WindowsImageBackup\Server01 is starting.
Starting to back up the system state [12/8/2013 9:29 AM]...
Creating a shadow copy of the volumes specified for backup...
Creating a shadow copy of the volumes specified for backup...
Creating a shadow copy of the volumes specified for backup...
Summary of the backup operation:
The backup of the system state failed [12/8/2013 9:30 AM].
Log of files successfully backed up:
C:\Windows\Logs\WindowsServerBackup\Backup-08-12-2013_09-29-49.log
Log of files for which backup failed:
C:\Windows\Logs\WindowsServerBackup\Backup_Error-08-12-2013_09-29-49.log
There is not enough disk space to create the volume shadow copy on the storage location. Make sure that, for all volumes
to be backup up, the minimum required disk space for shadow copy creation is available. This applies to both the backup
storage destination and volumes included in the backup.
Minimum requirement: For volumes less than 500 megabytes, the minimum is 50 megabytes of free space. For volumes more th
an 500 megabytes, the minimum is 320 megabytes of free space.
Recommended: At least 1 gigabyte of free disk space on each volume if volume size is more than 1 gigabyte.
ERROR - A Volume Shadow Copy Service operation error has
occurred: (0x8004231f)
Insufficient storage available to create either the shadow copy storage file or other shadow copy data.
If you see the free space available in each of the drives, they are in plenty.
C:\ 7.5 GB free of 70 GB
E:\ 250 GB free of 499 GB
I:\ 86.7 GB free of 350 GB
I am out of any hints on how I can proceed now. Has any one had similar issues? Can any one give any hint on this? Thanks.
Thanks.Some Additional info.
Shadow Copy Storage association
For volume: (\\?\Volume{a9fb0474-f1bd-11e0-b235-806e6f6e6963}\)\\?\Volume{a9f
b0474-f1bd-11e0-b235-806e6f6e6963}\
Shadow Copy Storage volume: (\\?\Volume{a9fb0474-f1bd-11e0-b235-806e6f6e6963}
\)\\?\Volume{a9fb0474-f1bd-11e0-b235-806e6f6e6963}\
Used Shadow Copy Storage space: 0 B (0%)
Allocated Shadow Copy Storage space: 0 B (0%)
Maximum Shadow Copy Storage space: 32 MB (32%)
Shadow Copy Storage association
For volume: (I:)\\?\Volume{ddf6a51c-1282-11e3-b291-000c293b01d1}\
Shadow Copy Storage volume: (I:)\\?\Volume{ddf6a51c-1282-11e3-b291-000c293b01
d1}\
Used Shadow Copy Storage space: 0 B (0%)
Allocated Shadow Copy Storage space: 0 B (0%)
Maximum Shadow Copy Storage space: 35 GB (10%)
Shadow Copy Storage association
For volume: (E:)\\?\Volume{0e3bf713-125d-11e3-b2dd-000c293b01bd}\
Shadow Copy Storage volume: (E:)\\?\Volume{0e3bf713-125d-11e3-b2dd-000c293b01
bd}\
Used Shadow Copy Storage space: 0 B (0%)
Allocated Shadow Copy Storage space: 0 B (0%)
Maximum Shadow Copy Storage space: 149.999 GB (30%)
Shadow Copy Storage association
For volume: (C:)\\?\Volume{a9fb0475-f1bd-11e0-b235-806e6f6e6963}\
Shadow Copy Storage volume: (C:)\\?\Volume{a9fb0475-f1bd-11e0-b235-806e6f6e69
63}\
Used Shadow Copy Storage space: 0 B (0%)
Allocated Shadow Copy Storage space: 0 B (0%)
Maximum Shadow Copy Storage space: 4.99 GB (7%)
Hope this might also help you experts to get a little more information. -
Windows 2008 R2 backup fails with event 521 error code 2155348001
Windows Server 2008 R2 SP1. Hyper-V role installed.
OS on drive C. All VMs stored on Drive D.
I am attempting to run a Bare Metal backup of the host system to a network share.
Drive D is not included in the backup job. I am getting the following error:
Log Name: Application
Source: Microsoft-Windows-Backup
Date: 1/10/2014 11:28:52 PM
Event ID: 521
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: SHAQTUS.scdl.local
Description:
The backup operation that started at '2014-01-11T04:08:50.683000000Z' 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 '2155348001'. Please review the event
details for a solution, and then rerun the backup operation once the issue is resolved.
Reviewing event details, as suggested, does not offer any solution.
I have tried the suggested solutions in other similar threads of increasing the timeout value with the registry entry.
This does not work.
I have not tried reregistering the VSS writers manually, as the only links I have found are for server 2003/2008 (not R2) and explicitly state that they won’t work on higher versions of the OS, since they now utilize manifests and the manual procedure could
cause problems for those servers. Haven't found similar procedures for 2008 R2.
I have been able to narrow this down a bit.
A Windows 2008 R2 SP1 server with Hyper-V installed – backup to a network share is successful;
Install the DPM 2012 agent – same backup fails with the 2155348001 error.
We use DPM 2012 to backup VMs, but DPM cannot perform a bare metal backup/restore of server and the 2012 version no longer has the DPMSRT feature.
I prefer to run Bare Metal Backup to a file server share.
Stuck on this one.
RickHi,
The issue is related to DPM, I would suggest you ask for help from DPM forums:
http://social.technet.microsoft.com/Forums/en-US/home?forum=dataprotectionmanager
Regards,
Mandy
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
Exchange 2013 Window Backup failure - fails to clean up log files - error FFFFFFFC
Hello,
We currently have an Exchange 2013 - Exchange 2007 coexistence setup.
1x Windows Server 2008 R2 with Exchange 2007 CAS/HUB
1x Windows Server 2008 R2 with Exchange 2007 MBX
1x Windows Server 2008 R2 with Exchange 2013 CU 3 (all roles)
Since our current backup solution (Symantec Backup Exec 2010 R3) does not support backing up Exchange 2013 CU3 databases, we are using the builtin Windows Backup feature to backup the Exchange 2013 CU3 databases.
This has functioned for a while, until all of a sudden, the log files are not cleared anymore, causing our log disk to fill up.
Our Exchange 2013 server looks like this:
C: Windows + Exchange installation
D: Databases
E: Database Log Files
F: Archive Databases
G: Archive Database Log Files
S: Dedicated backup volume
The backup is scheduled to run every day at 21:00 hours, performing a full VSS backup of D:,E:,F: and G: to the volume S:
Windows backup log says the backup completed with exceptions, leaving the Exchange logs untouched and filling the drive.
The Windows Backup Command Line tools are NOT installed since they are not compatible with Exchange 2013.
In the eventvwr we can see the following error:
The Microsoft Exchange Replication service VSS Writer (Instance a33ec440-7f12-4c50-806b-1bc5ceaf8aad) failed with error FFFFFFFC when processing the backup completion event.
The command VSSADMIN LIST WRITERS displays the following:
Writer name: 'Microsoft Exchange Writer'
Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
Writer Instance Id: {cf84a907-76dc-428c-90e0-c18a3f9db493}
State: [1] Stable
Last error: Retryable error
Restarting the Microsoft Exchange Replication (MSExchangeRepl) clears the writer error, same with a reboot, however the error comes backup after the next backup.
Any thoughts on how to resolve this issue?
Thanks.Hello,
Here is a blog for your reference.
http://blogs.technet.com/b/timmcmic/archive/2012/03/11/exchange-and-vss-my-exchange-writer-is-in-a-failed-retryable-state.aspx
If there is any useful information after you change the logging to expert, please free let me know.
Cara Chen
TechNet Community Support -
Hi
We have a Windows 2012 server with Exchange 2013, all is working fine except now i am getting issues with the backup.
'Exchange - The application will not be available for recovery from this backup. the consistency check failed for the component Microsoft Exchange Server'
I have checked the database all is fine, i have created a new db and move all mailbox;s over and then removed the old db, i have enabled circular logging and then disabled it, it seems no matter what i do i cannot get a full backup!
i did have to restore the server once and the backups still worked for about 4 days after that and then stopped, i have also tried to remove and re add the backup role!
i am stumped, any advice would be great!Hi
Ok, i created a test db and tried to back it up right away, it failed, i did not add any mailbox's to it either. i got quite a few events in the windows logs, as well as the same event above i got the following:
Log Name: Application
Source: MSExchangeRepl
Date: 21/01/2013 10:16:30
Event ID: 2038
Task Category: Exchange VSS Writer
Level: Warning
Keywords: Classic
User: N/A
Computer: NERDS-DC01.nerds.local
Description:
Microsoft Exchange VSS Writer backup failed. No log files were truncated. Instance 75754d0d-8dfe-4909-8beb-5a4f824254a9. Database 4843b37c-7b3c-42b2-8b57-1393615c2c15.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MSExchangeRepl" />
<EventID Qualifiers="32772">2038</EventID>
<Level>3</Level>
<Task>2</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-01-21T10:16:30.000000000Z" />
<EventRecordID>261645</EventRecordID>
<Channel>Application</Channel>
<Computer>NERDS-DC01.nerds.local</Computer>
<Security />
</System>
<EventData>
<Data>75754d0d-8dfe-4909-8beb-5a4f824254a9</Data>
<Data>4843b37c-7b3c-42b2-8b57-1393615c2c15</Data>
</EventData>
</Event>
AND
Log Name: Application
Source: MSExchangeRepl
Date: 21/01/2013 10:16:30
Event ID: 2038
Task Category: Exchange VSS Writer
Level: Warning
Keywords: Classic
User: N/A
Computer: NERDS-DC01.nerds.local
Description:
Microsoft Exchange VSS Writer backup failed. No log files were truncated. Instance 75754d0d-8dfe-4909-8beb-5a4f824254a9. Database db5826f3-1029-4219-ad80-441a0e94537a.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MSExchangeRepl" />
<EventID Qualifiers="32772">2038</EventID>
<Level>3</Level>
<Task>2</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-01-21T10:16:30.000000000Z" />
<EventRecordID>261646</EventRecordID>
<Channel>Application</Channel>
<Computer>NERDS-DC01.nerds.local</Computer>
<Security />
</System>
<EventData>
<Data>75754d0d-8dfe-4909-8beb-5a4f824254a9</Data>
<Data>db5826f3-1029-4219-ad80-441a0e94537a</Data>
</EventData>
</Event>
and
Log Name: Application
Source: MSExchangeRepl
Date: 21/01/2013 10:16:30
Event ID: 2034
Task Category: Exchange VSS Writer
Level: Error
Keywords: Classic
User: N/A
Computer: NERDS-DC01.nerds.local
Description:
The Microsoft Exchange Replication service VSS Writer (Instance 75754d0d-8dfe-4909-8beb-5a4f824254a9) failed with error FFFFFFFC when processing the backup completion event.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MSExchangeRepl" />
<EventID Qualifiers="49156">2034</EventID>
<Level>2</Level>
<Task>2</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-01-21T10:16:30.000000000Z" />
<EventRecordID>261649</EventRecordID>
<Channel>Application</Channel>
<Computer>NERDS-DC01.nerds.local</Computer>
<Security />
</System>
<EventData>
<Data>75754d0d-8dfe-4909-8beb-5a4f824254a9</Data>
<Data>FFFFFFFC</Data>
</EventData>
</Event>
and
Log Name: Application
Source: SPP
Date: 21/01/2013 10:16:30
Event ID: 16389
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: NERDS-DC01.nerds.local
Description:
Writer Microsoft Exchange Writer experienced retryable error during shadow copy creation. Retrying... More info: .
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="SPP" />
<EventID Qualifiers="0">16389</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-01-21T10:16:30.000000000Z" />
<EventRecordID>261650</EventRecordID>
<Channel>Application</Channel>
<Computer>NERDS-DC01.nerds.local</Computer>
<Security />
</System>
<EventData>
<Data>Microsoft Exchange Writer</Data>
<Data>
</Data>
<Data>The writer experienced a transient error. If the backup process is retried, the error may not reoccur. (0x800423F3)</Data>
<Data>
</Data>
<Binary>00000000A5120000981200000000000042BEB7C511CAC619E59C92030000000000000000</Binary>
</EventData>
</Event> -
Windows Storage Server 2008 backup fail to UEFI based computers
Hai All
I have got Windows Storage Server 2008 running on a WD Sentinel DX4000. Recently my company bought a couple of new Dell laptops all running windows 8.1 64bit OS. Only three older laptops were left. Now for the fun part...I installed the connectors pointing
to the Sentinel on the laptops, and as expected the pc's show on the dashboard of the Storage Server, but all of the backups fail on the newer laptops. I installed the connectors on the older laptops as well and they go through no problem
The only difference between the older laptops and the new ones are the GPT partition drives and laptops running on UEFI, the older laptops, although running the same OS, do not have GPT and UEFI. I looked at the Event Viewer and found three errors to do
with the backup: Event 514 pointing to a ClientVSSProblem, Event 8194 pointing to Volume Shadow Copy Service error: Unexpected error querrying for the VSSWriterCallback interface, hr=0x80070005,Access Denied and the last one is Event 513 CAPI2, Cryptographic
Service failed while processing onIdentity() call in the System Writerobject Details: AddLegacyDriverFiles: Unable to back up image of binary Microsoft Link-Layer Discovery Protocol. I did as most articles suggested but with no change. From changing registries
to taking ownership of the %windir% and adding the NT AUTHORITY, the NT Service and BUILTIN\Users. No change.
Help is much appreciated before i make a boat anchor out of the WD Sentinel.
Kind regardsWell looks like there is a change or two to be made on the client computer, granting some access to the NT Services and NT Authority. To automate this fix I wrote a batch file to be run on the client pc:
takeown /f %windir%\winsxs\temp\PendingRenames /a
pause
icacls %windir%\winsxs\temp\PendingRenames /grant "NT AUTHORITY\SYSTEM":(RX)
pause
icacls %windir%\winsxs\temp\PendingRenames /grant "NT Service\trustedinstaller":(F)
pause
icacls %windir%\winsxs\temp\PendingRenames /grant "BUILTIN\Users":(RX)
pause
takeown /f %windir%\winsxs\filemaps\* /a
pause
icacls %windir%\winsxs\filemaps\*.* /grant "NT AUTHORITY\SYSTEM":(RX)
pause
icacls %windir%\winsxs\filemaps\*.* /grant "NT Service\trustedinstaller":(F)
pause
icacls %windir%\winsxs\filemaps\*.* /grant "BUILTIN\Users":(RX)
net stop cryptsvc
pause
net start cryptsvc
pause
The backup now starts on the Sentinel
Kind Regards
Maybe you are looking for
-
How to use RAID 0 on Qosmio x300-11w?
Hi, I have a Qosmio x300-11w with 2 320GB HDD and I would like to use them in RAID 0 for a bit more speed, I cant see any RAID options in BIOS. Is there another way to enable it? My BIOS version up to date version 1-30 I think. Anyone know if it is p
-
Image on pc not rendering fast
i have created and posted a starter site on my own domain. when i view on a mac the images render real quick. on a pc the images with drop shadows take up to 10 seconds. i have tried it on many different pc's with the same results. question is: is th
-
Relatively slow display of pdf files?
Hi: I've got an Oracle Text application that indexes and queries various file types fine, but the actual display of pdf files is pretty slow. On a 2.4GHz P4 w/1G Ram it took about 20 seconds to display it's version of a 2.5M pdf file. It takes < 10 s
-
my younger brother has disabled his i phone and it doesnt say try again in so many minutes it says connect to itunes when i do it never seems to work when i restore and update how do i get past this?
-
OWB 11.2.0.1 SAP LOCATION: Problem with separate FTP Server connection
Hello, hope somebody can help me. We are working on a BI Project by our Customer with a Exadata Machine. The Goal of this project is to have the DWH on the Oracle Exadata machine. At the Moment we have the Development System on a separate Server with