System State Backup - 2008R2 - Volume Shadow Copy Error

I am attempting to do system state backup in my Test environment. I am running Hyper-V on a standalone "sandbox" server. I have configured a semi-duplicate environment.
We are updating the schema soon, and I would like to do a System State restore for practice and I haven't actually had to do one in about 10 years.
I am running 2008R2 DC as a VM in my Hyper-V environment. It has a C: and E: volume, VSS is enabled on e: and set to Unlimited. I set my set "BackupLocation=e:\adbackups" and attempt to run wbadmin.exe start systemstatebackup -backupTarget:"E:"
(with quotes or without it still fails.
My error from command is Error - Volume Shadow Copy Service operation error (0x800423f4) which appears to be a generic error. In the Backup Event Viewer it shows as Event ID 9, another generic error.
I am running as Domain Admin, and I checked that I have Backup Operator rights. Volume Shadow Copy service is running.

Hello Chris,
This issue occurs if any of the virtual disks attached to the guest VM was created by using the option to copy the contents of a physical disk. Please refer the below mentioned MS KB..
Backup of a Hyper-V virtual machine fails with error 0x800423f4 if the disk signature on a virtual hard disk is the same as a physical disk on the Hyper-V host
http://support.microsoft.com/kb/975695
Sincerely, Asifkhan -- Please mark my post helpful if it was really helpful to you.

Similar Messages

Win2008 R2 Backup Failure: Volume Shadow copy operation failed for backup volumes with following error code "2155348254"

Failed to get exclusive lock on the Extensible Firmware Interface (EFI) system partition.
[ Name] Microsoft-Windows-Backup
   [ Guid] {1DB28F2E-8F80-4027-8C5A-A11F7F10F62D}
   EventID 517
   Version 0
   Level 2
   Task 0
   Opcode 0
   Keywords 0x8000000000000000
- TimeCreated
   [ SystemTime] 2012-09-13T02:01:26.193377500Z
   EventRecordID 134130
   Correlation
- Execution
   [ ProcessID] 13508
   [ ThreadID] 552
   Channel Application
   Computer SERVER.srv.local
- Security
   [ UserID] S-1-5-17
- EventData
BackupTime 2012-09-13T02:00:15.711673900Z
ErrorCode 2155348254
ErrorMessage %%2155348254

Shaon,
I am receiving an identical error message as the original poster.
Let me give you some information on my setup and what I have already tried.
I am running a Windows Server 2008 R2 domain controller with SP1 installed. The system also runs MS SQL 2008 and IIS. All critical and recommended updates are installed.
The server backs up to a set of one of two external hard drives over USB 2.0 every night using Windows Backup. The external hard drives are encrypted using BitLocker and rotated offsite every week. We had no problems until 27 November 2013. On
that date I installed the November Windows updates and rebooted. Backups have not worked correctly since that time.
The server has two hard drives. The first one contains an 100 MB EFI partition (created for the IBM System x3200 M3 server EFI hardware although it appears to be entirely empty). The second partition contains the OS and the SQL databases. The
second hard drive contains shared data files. None of the partitions are close to being full.
The backup fails with the following error in the Windows Backup interface:
EFI System Partition: Windows Server Backup failed to get an exclusive lock on the EFI system partition. Detailed error: Access is denied.
The event viewer contains the error listed by the original poster (in the detailed view). The general view has this description:
The backup operation that started at <time> has failed with the following error code '2155348254' (Windows Backup failed to get an exclusive lock on the EFI system partition (ESP). This may happen if another application is using files on the
ESP. Please retry the operation.). Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.
This error is thrown about 1 minute after the backup begins. After encountering the error with the EFI partition the backup exits and does not attempt to backup the other partitions.
The most interesting detail about the problem is that if I reboot the server and immediately perform a backup it completes successfully. If I reboot the server and wait approximately an hour before starting the backup it will fail. The backups
will continue to fail until the server is rebooted, at which point I if a backup is started immediately it will succeed but all future backups will fail. Therefore, it seems that Windows Backup has access to the EFI partition immediately after a reboot
but loses access for some reason close to the hour mark (this is an estimate based on a little experimentation but not an exact number).
Reading the little bit of information available online for this error message I have tried disabling our antivirus (Kaspersky) with no effect. I have also replaced the first hard drive in the server that contains the EFI partition with not effect (the
old hard drive imaged to the new hard drive with no errors, but backups still fail with the new hard drive). Backups fail with either external hard drive connected, so it is unlikely that the external hard drive is the problem. I have erased all
the Windows Backup settings including wiping all data on the external backup drive and created a new backup with no effect. I attempted to not backing up the EFI partition but it is required for the system state. I have reviewed all the Windows
updates installed in 27 November 2013 but none of the KB articles reference anything that I could possibly see related to the backup except for possibly the installation of .NET 4.5.1. However, I do not believe that Windows Backup uses .NET. 'Vssadmin
list writers' does not list any obvious errors.
At this point I am stymied except to think that I have some esoteric hardware failure. I have contacted IBM support who ran an extensive hardware diagnostic which showed no hardware issues.
I run several other similar Windows Server 2008 R2 systems, but none of them are on this model of hardware and none of them have an EFI partition. They all installed the same November Windows Updates. All of them are able to backup to external
hard drives without issue.
Any support you can provide would be greatly appreciated.

Domain Controller System State backup script *not working*

Hello I am trying to get an automated backup for my domain controller to a network share using a script and windows task scheduler - our domain controller is windows server 2008r2
this is the code for the script i have written as seen below, however when i run the scrip it does create the folder on the network share but fails to initiate the system state backup power shell returns this error when i run the script.
any suggestions on what i can do to resolve this issue? i am also rather new to powershell so there many be a much easier way of going about it.
many thanks
Gordon
wbadmin 1.0 - Backup command-line tool
(C) Copyright 2004 Microsoft Corp.
ERROR - One of the parameters or options specified is invalid: [quiet].
See the syntax below.
Syntax: WBADMIN START SYSTEMSTATEBACKUP
-backupTarget:<VolumeName>
[-quiet]
Description: Creates a system state backup of the local computer and stores
it on the location specified.
To use this command, you must be a member of the Backup Operators group
or Administrators group.
Parameters:
-backupTarget Specifies the location where you want to store the backup.
The storage location requires a drive letter or a GUID-based
volume of the format: \\?\Volume{GUID}.
-quiet Runs the command with no prompts to the user.
Example:
WBADMIN START SYSTEMSTATEBACKUP -backupTarget:f:
#adds windows server backup powershell snapin
Add-Pssnapin windows.serverbackup
#gets date
$date = Get-Date -Format dd.MM.yyyy
#declares backup location and adds date
$backdir = ("\\backupserver\bpdbackups\DC\$date")
#makes backup directory on network share
mkdir $backdir | out-null
#runs system statebackup
wbadmin start systemstatebackup -backupTarget:$backdir -[quiet]
#sends and email at the nd of the process
$smtp = "192.168.xxx.xxx"
$from = "Domain Controller <[email protected]>"
$to = "Network Admin <[email protected]>"
$body = "The backup operation has been successfully done! Date: $date"
$subject = "Backup on $date"
#Send an Email to User
send-MailMessage -SmtpServer $smtp -From $from -To $to -Subject $subject -Body $body - BodyAsHtml
write-host "Backup Successful"

wbadmin start systemstatebackup -backupTarget:$backdir -[quiet]"[quiet]"? I guess you should remove the bracketswbadmin start systemstatebackup -backupTarget:$backdir -quiet

Backup Fail with Volume Shadow Copy Service error: Error calling a routine on the Shadow Copy Provider, Event ID 12293, error returned while creating the volume shadow copy 0x8004230f,

We are using TINA backup solution and windows 2003 backup is failling with VSS error.
For testing purpose we initiate a system state backup (or any file backup) with the help of windows 2003 ntbackup.exe and found it is failing with below error.
Backup error report.
Backup Status
Operation: Backup
Active backup destination: File
Media name: "Backup.bkf created 28/05/2014 at 06:34"
Volume shadow copy creation: Attempt 1.
Error returned while creating the volume shadow copy:0x8004230f.
Error returned while creating the volume shadow copy:8004230f
Aborting Backup.
The operation did not successfully complete.
We check event viewer and found below error event.
Event Type:
Error
Event Source:
VSS
Event Category:
None
Event ID:
12293
Date:
28/05/2014
Time:
05:48:10
User:
N/A
Computer:
CQ329TOS
Description:
Volume Shadow Copy Service error: Error calling a routine on the Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details Cannot ask provider {b5946137-7b9f-4925-af80-51abd60b20d5} if
volume is supported. [0x8000ffff] [hr = 0x8000ffff].

Resolution:
After getting this error we check Shadow Copy provider and writer health and fond it is fine.
To get shadow copy providers details use below command.
Command: vssadmin list providers
Command output
C:\>vssadmin list providers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.
Provider name: 'Microsoft Software Shadow Copy provider 1.0'
   Provider type: System
   Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
   Version: 1.0.0.7
To get shadow copy writers health
Command: vssadmin list writers
Command Output.
C:\>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.
Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {333e02cd-d9ec-43c8-9b45-39691ad1b351}
   State: [1] Stable
   Last error: No error
Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {800877a5-e13d-47a3-8f99-ebd4d3b3fd12}
   State: [1] Stable
   Last error: No error
Writer name: 'MSDEWriter'
   Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
   Writer Instance Id: {63400aa0-a17f-4121-9483-1cd226f03238}
   State: [1] Stable
   Last error: No error
Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {e13cb72b-84fa-4c86-86d8-48f523aafc9a}
   State: [1] Stable
   Last error: No error
Writer name: 'Event Log Writer'
   Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
   Writer Instance Id: {ce63b3a0-e038-4e56-9d07-929f256639de}
   State: [1] Stable
   Last error: No error
Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {008e8714-ed6d-4288-81ce-4b0b1ec41294}
   State: [1] Stable
   Last error: No error
Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {e22a8953-a52c-4a76-bec0-8773122cbff8}
   State: [1] Stable
   Last error: No error
Next I check Shadow Copies details from volume properties (right click on C or other drive then select properties then click on Shadow Copies Tab) and found it is showing the same error code..
From this error it is clear that the issue is inside the registry hive and due to junk hive shadow copies services not able to working properly.
For me the server have two disk we check disk signature at MBR and found the disk signature was.
Signature disk 0 : 9351912b
Signature disk 0 : FDFBE035
But at registry we found lot of nonexistance signature. Which indicate lot of junk valu inside registry.
Now how can we resolve this issue?
It is very simple just delete the registry key “volume” (registry key “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\STORAGE\Volume”) and reboot the server it will “Volume” registry hive automatically.
Note:
When you remove registry key it is showing error unable to delete, then please right click on it select permission then take ownership and assign full permission to your login account.
Please be careful when you delete registry key because system can fully crashed if you delete or modify wrong registry key.
Your can take a backup of the registry key by exporting.

The creation of the shadow copy on the backup destination has failed. Detailed Error: The Volume Shadow Copy operation failed with the error 0x80042316

When using Microsoft Backup on a Windows Server 2008 SP2 (not R2 - [Microsoft version 6.0.6002]) I get the error "The creation of the shadow copy on the backup destination has failed. Detailed Error: The Volume Shadow Copy operation failed with the
error 0x80042316"
The odd thing is that when I start the backup manually, it works fine. When it runs automatically the error appears.
When doing a SFC /scannow I do get errors that can't be corrected.
Is there anything short of rebuilding this machine (It's a DC and the only one this office has) I can do to fix this?

Hi,
0x80042316 means "Another shadow copy creation is already in progress". This error could occur when another VSS instance is running.
Is there any third party backup application installed? Try to uninstall it to see the result. And please also check if there is another backup schedule which causes the conflict.
Meanwhile please provide the result of:
vssadmin list providers
vssadmin list writers
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Support, contact [email protected].
Hi,
I do have Crashplan ProE running. It started at 1900 and the Windows Backup starts at 2000. I have modified Crashplan not to start until 2300 to see if that helps.
Also:
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Provider name: 'Microsoft Software Shadow Copy provider 1.0'
Provider type: System
Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
Version: 1.0.0.7
AND:
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: {f0c7ee55-5885-4894-8dd3-14fffbdd4d2e}
State: [1] Stable
Last error: No error
Writer name: 'SqlServerWriter'
Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Instance Id: {017a0133-7577-4322-b513-04f72404b70a}
State: [1] Stable
Last error: No error
Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {6b17d670-9ea8-4ff1-a59e-b474f4b893db}
State: [1] Stable
Last error: No error
Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {56aad1bf-9bf1-4fde-b2f4-a706577c632d}
State: [1] Stable
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {e942d09d-276e-450a-9bf4-b1d5abe6af8a}
State: [1] Stable
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {3737164b-61ac-454c-b1f7-42f2620f10db}
State: [1] Stable
Last error: No error
Writer name: 'DFS Replication service writer'
Writer Id: {2707761b-2324-473d-88eb-eb007a359533}
Writer Instance Id: {39458257-aca4-481e-a302-994f3eb1e9a3}
State: [1] Stable
Last error: No error
Writer name: 'Dhcp Jet Writer'
Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
Writer Instance Id: {6a8ab4aa-760c-4102-a27f-58f570c9c572}
State: [1] Stable
Last error: No error
Writer name: 'NTDS'
Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
Writer Instance Id: {53577013-8397-448e-9a25-c7cac08aa0a8}
State: [1] Stable
Last error: No error
Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
Writer Instance Id: {ee2c9173-92e7-455c-8f73-601647c0ddb2}
State: [1] Stable
Last error: No error
Writer name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
Writer Instance Id: {b1f60392-9dfd-4e3a-bda6-3dc2cb622ba4}
State: [1] Stable
Last error: No error
Writer name: 'IIS Config Writer'
Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
Writer Instance Id: {a328aede-78f0-448e-9c36-e8379e9fe2a8}
State: [1] Stable
Last error: No error
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {c39fa334-5c9d-4906-a3b5-33c3444948e6}
State: [1] Stable
Last error: No error
Writer name: 'NPS VSS Writer'
Writer Id: {35e81631-13e1-48db-97fc-d5bc721bb18a}
Writer Instance Id: {3c9c5584-b5fd-48cf-8541-0c8bfa585ca0}
State: [1] Stable
Last error: No error

How to Delete Non-System State Backups in Windows 2008R2

Hello,
I am running a Windows 2008R2 server which uses Windows Server Backup to do the backups. We are using the backup-tool to create non-system state backups of the data-directories on this machine. The backup is done on a dedicated disk connected through iscsi
(to a Synology box). This backup disk has become too small and we have now replaced the Synology box with a bigger one. Here i created a new LUN again for the backup purposes.
Now for my question; The wbadmin.exe tool supplied with W2008R2 does not offer a way to delete the old backups. I know that in Win2012 (which we we also have running) I could add the new iscsi location and then (when enough backups are available on the new
target) use wbadmin.exe delete backup to delete the old non-system state backups; e.g.
wbadmin delete backup -version:08/07/2013-21:00
This (very undocumented) feature of Windows 2012 and higher works quite nice and is exactly what i am searching for on the W2008R2 machine; a way to delete the old backups (and under the hood delete the corresponding snapshots)
I've done quite a bit of research and it should be possible to do something similar in 2008 but then manually, The howto is described in the following link: http://blogs.technet.com/b/filecab/archive/2009/06/22/backup-version-and-space-management-in-windows-server-backup.aspx .
Basically it describes that you should use DiskShadow.exe to remove e.g. the oldest snapshot with a command like :
Delete shadows OLDEST \\?\Volume{7fc1871b-2e1f-11dd-a339-001e4fb7af35}
Windows Server backup (wbadmin) should then on the next run 'see' this deletion and update its list of available backups:
"You can perform the same steps manually to delete backups on demand. However, the backup catalog update cannot be done manually and it will happen instead during
the next backup."
I've done this on our box and it indeed removes the shadows from the list. However, in the Windows Backup 'dashboard' it still lists the backups as available. Also after a new backup has finished (according the the article this is when it should 'update'
its backup catalog). When I try to restore a backup from a date that i just removed it gives a nice message that this is impossible because the snapshot is not available (duh :)) ;
Unable to browse Local disk. The shadow copy of the backup stored on the backup destination cannot be found.
So it seems that the aforementioned method works; it removes the snapshot and frees diskspace, but it doesn't update the Windows Backup catalog. As a result the management tool (GUI) still lists the backups which are no longer available! How can i change
this? Is there any way to do this? I found one article which mentions that the Dashboard bases its screen on the Windows Logs and not on the actual VSS snapshots available:
http://forum.wegotserved.com/index.php/topic/23757-start-afresh-with-server-backup/ (WHS) In my situation however this seems unlikely because i don't have any logs that date back as far as my backups go.
In my opinion this is a real bug and it leaves us with a in-consequent backup schema. Does anyone have similar situations or even a solution to my problem?
Kind Regard, Martin

Hi Mandy,
Yes! I think i got my answer and I now get how windows backup works in Windows 2008 :-) It turns out that I dismissed some suggestions a bit too soon. The answer lies in the command mentioned earlier :
Wbadmin delete catalog
This command does delete all the backups from a perspective of the Windows Backup UI, but leaves the VSS snapshots intact. This means that the backups are still available, but you just can't restore them with the User Interface. In order to 'update' the
UI with the current available snapshots (which you can list with diskshadows list shadows all), you have to re-add the existing media on which the backups took place using the Wizard of the UI. It will then inform you that existing backups are available and
if you want to keep these for restore purposes. If you click 'yes', and THEN perform a backup ... All the current available backups will be shown in the User Interface :-)
So for my steps taken to change from one iscsi (iscsi1) to another (iscsi2):
- Add the 2nd iscsi target with the Windows Backup UI
using Backup schedule , Modify backup -> [desired options] => Add more backup destinations -> iscsi2
- Remove the 1st iscsi target with the Windows Backup UI
using Backup schedule , Modify backup -> [desired options] => Remove current backup destinations -> iscsi1
- Run some backups on the new destination. Old restore points are now still available. When enough restore points are available on the new volume iscsi2 start deleting old data from iscsi1 as follows:
- Run diskshadow
diskshadow
- list all the current snapshots
list shadows all
- remove all the snapshots of iscsi1 (repeat until all shadows are gone of iscsi1)
delete shadows oldest \\?\volume{yourvolumeid}\
- delete the windows backup catalog
wbadmin delete catalog
- Restart the windows backup UI and re-add your schedule on the new volume iscsi2. It will now ask if you want the keep the existing data for restore purposes; click yes.
- After the next backup only the backups of volume iscsi2 will be listed and everything is fine !
I Hope my post will help others with similar questions. It was quite a search before I understood the way it works. Basically as long as your VSS snapshots are still available and listed by diskshadow you still have the backups and you will be able to get
this in sync with the steps above (delete schedule and re-add originating targets containing the snapshots). After the next backup the UI will update itself.
(In my case someway along the way I lost my originating snapshots, but because I already had my new backup set it didn't bother me; It kept me from having to delete all 510 old backups :) with diskshadow)
Regard, Martin

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

SBS 2003 SP2: VSS errors; unable to create system state backup (NTBACKUP)

NTBACKUP system state on W2k3 server fails after "thinking" for ~10 mins and "creating" shadow copy; almost no disk activity, almost no CPU load. Errors in the Application
log:
Source: SQLVDI EventID: 1
Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=3392. Thread=29348. Client. Instance=. VD=Global\{9B35142B-C687-4766-9707-BC387534BA38}1_SQLVDIMemoryName_0.
Several of them.
Then:
EventID: 8019
Source: NTBackup
End Operation: Warnings or errors were encountered.
Consult the backup report for more details.
Then:
Source: VSS
EventID: 12305
Volume Shadow Copy Service error: Volume/disk not connected or not found. Error context: CreateFileW(\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy9,0xc0000000,0x00000003,...).
And finally:
EventID: 12293
Source: VSS
Volume Shadow Copy Service error: Error calling a routine on the Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details PostFinalCommitSnapshots({de0d580b-68ce-4eae-a046-b5b5b7a80235}, 1) [hr = 0x80042308].
When creating shadow copy on the system volume, the operation may take ~40-90 mins. On the data volume -- <1 min.
"vssadmin list writers" shows:
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.
Writer name: 'System Writer'
State: [10] Failed
Last error: Retryable error
Writer name: 'SqlServerWriter'
State: [10] Failed
Last error: Retryable error
Writer name: 'MSDEWriter'
State: [1] Stable
Last error: No error
Writer name: 'FRS Writer'
State: [10] Failed
Last error: Retryable error
Writer name: 'NTDS'
State: [1] Stable
Last error: No error
Writer name: 'IIS Metabase Writer'
State: [10] Failed
Last error: Retryable error
Writer name: 'Event Log Writer'
State: [1] Stable
Last error: No error
Writer name: 'COM+ REGDB Writer'
State: [1] Stable
Last error: No error
Writer name: 'Dhcp Jet Writer'
State: [10] Failed
Last error: Retryable error
Writer name: 'Certificate Authority'
State: [10] Failed
Last error: Retryable error
Writer name: 'WINS Jet Writer'
State: [10] Failed
Last error: Retryable error
Writer name: 'Registry Writer'
State: [1] Stable
Last error: No error
Writer name: 'Microsoft Exchange Writer'
State: [1] Stable
Last error: No error
Writer name: 'TermServLicensing'
State: [10] Failed
Last error: Retryable error
Writer name: 'WMI Writer'
State: [10] Failed
Last error: Retryable error
Here is what I tried to do:
1. Restarted that thing.
2. Cleaned the security log.
3. Installed Windows Server 2003 Hotfix rollup KB940349-v3.
4. Stopped both SBSMONITORING and SHAREPOINT instances of MSDE, SQL 2005, SQL 2005 VSS and tried to perform the system state backup then. Stopped Exchange 2003 before launching NTBACKUP as well.
5. "regsvr32 sqlvdi.dll" in MSDE directory.
6. Renamed "System Volume Information" on all volumes and VSS has re-created them.
7. chkdsk /f was fun on all volumes, no major issues found.
8. Installed Hotfixes KB967551, KB975928-v2 (someone recommended).
9. Disabled SQL Server VSS Writer (SQLVDI errors disappeared from the application event log, VSS and NTBACKUP errors stayed).
10. Re-registered the DLLs as per Shaon Shan's post at http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/346fa42c-a476-457f-bcf3-59f87e444b55
The above had no effect on the issue whatsoever, except a little change at item 9 as mentioned.

Hi there.
I just had that problem. I saw friday my backup from my sbs 2003, was not completing becasuse it said it couldn´t creat a shadow copy in the external drive... It kept giving me errors os VSS and Volsnap... But strange thing is, i have VSS turned off in all
drives, and from months no problems with backups... So i went in Event viewer and look at it with attention, i saw a error that keep coming up from time to time (because we change the external drive form week to week). And i realize that there's a disk error
event...
Couldn´t run checkdisk from server, dont now why.. So i disconnected the drive, connected to my laptop, and ran a CheckDisk /F /X. ... It had BAD SECTORS! So i ran check disk... waited like 10-20 minutes. And then i ran it again just in case, and the 2nd
time was much more faster, like 3-6 minutes.
I disconnected from laptop, and connected to server. I went to the Backup wizard (in server managment), and press Backup now...
It hang 5-10 second in Creating Shadow copy..... And it started making the Backup :_D
I've seen all errors that were reported exactly as mine. I ran the Hotfix, all stayed the same, i followed all manual steps and still the same... and the problem was always in the external drive, which had bad sectors.
Hope it will help the next person that needs this info!

Wbadmin System State Backup "Parameter is incorrect"

Hello,
We have two physical Windows Server 2008 R2 x64 Standard Domain Controllers and the system state backup on both fails with the same error.
We issue the command:
wbadmin start systemstatebackup -backuptarget:c:
(NOTE: We did the REG fix to allow backups to the system volume)
and we get this as the output:
C:\Windows\system32>wbadmin start systemstatebackup -backuptarget:c:
wbadmin 1.0 - Backup command-line tool
(C) Copyright 2004 Microsoft Corp.
Starting to back up the system state [28/02/2010 21:26]...
Retrieving volume information...
This will back up the system state from volume(s) System(C:) to c:.
Do you want to start the backup operation?
[Y] Yes [N] No y
Creating a shadow copy of the volumes specified for backup...
Creating a shadow copy of the volumes specified for backup...
Please wait while system state files to back up are identified.
This might take several minutes...
Summary of the backup operation:
The backup of the system state failed [28/02/2010 21:27].
Log of files successfully backed up:
C:\Windows\Logs\WindowsServerBackup\Backup-28-02-2010_21-26-31.log
Log of files for which backup failed:
C:\Windows\Logs\WindowsServerBackup\Backup_Error-28-02-2010_21-26-31.log
The operation ended before completion.
The parameter is incorrect.
C:\Windows\system32>
This happens on both servers and the two backup log files mentioned in the output are both empty.
There's no other information that I can find so I don't know what the "parameter" is or why it is incorrect.
Has anyne come across this problem and know what the error is referring to?
Thanks
Sunil

I received a PowerShell script from Suhas and ran it on the affected server, the script output gave:
1.
     Service Name    : RMAGENT
     Service Caption : RMAGENT
     Registry key    : HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\RMAGENT\ImagePath
     Value           : \\PRIMARY\admin$\Microsoft DPM SRT\RFCAgent.exe
     Reason          : The service path contains a double slash. Network paths or paths containing a double slash are not supported.
2.
     Service Name    : RMAGENT
     Service Caption : RMAGENT
     Registry key    : HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\RMAGENT\ImagePath
     Value           : \\PRIMARY\admin$\Microsoft DPM SRT\RFCAgent.exe
     Reason          : The service path does not have a proper path format. Only paths beginning with [<Drive>]:\ format are supported.
The "RMAgent" is from Microsoft Data Protection Manager 2007 System Recovery Tool (DPM-SRT) and I think is the remote agent that DPM-SRT uses to backup the remote system.
The DPM-SRT RMAgent isn't supported and doesn't work on Windows Server 2008 R2 systems and I am not sure how it ended up installed on the server. Removing this service should solve the problem and allow the System State Backups to work. The DPM-SRT agent wasn't listed in the "Programs and Features" and so couldn't be installed from there (if it was I would have spotted this a long time ago and probably solved the problem). Instead, I used the information at:
http://www.howtogeek.com/howto/windows-vista/how-to-delete-a-windows-service-in-vista-or-xp/
To delete the RMAgent service: sc delete "RMAgent" in an Administrator CMD prompt. This removed the registry entries shown in the script output above. When this was done, I ran the script again just to be sure there was nothing else and indeed the RMAgent entries had gone and there were no other items that needed attention.
Finally, I tried "webadmin start systemstatebackup -backuptarget:C:" again in an administrator CMD prompt and it completed successfully.
I would like to thank Abhinav Mathur and Suhas Rao in particular for their very helpful script.
Sunil

Windows Server 2008 R2 - System State Backup - Application Log: CAPI2 513

When performing a system state backup from wbadmin, I get...
Creating a shadow copy of the volumes specified for backup...
Creating a shadow copy of the volumes specified for backup...
Please wait while system state files to back up are identified.
This might take several minutes...
Summary of the backup operation:
The backup of the system state failed [12/15/2011 6:38 PM].
Log of files successfully backed up:
C:\windows\Logs\WindowsServerBackup\Backup-15-12-2011_18-38-05.log
Log of files for which backup failed:
C:\windows\Logs\WindowsServerBackup\Backup_Error-15-12-2011_18-38-05.log
The operation ended before completion.
The system writer is not found in the backup.
In the event log, I get...
Log Name: Application
Source: Microsoft-Windows-CAPI2
Date: 12/15/2011 6:38:24 PM
Event ID: 513
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Server1.domain.com
Description:
Cryptographic Services failed while processing the OnIdentity() call in the System Writer Object.
Details:
AddCoreCsiFiles : GetNextFileMapContent() failed.
System Error:
The parameter is incorrect.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-CAPI2" Guid="{5bbca4a8-b209-48dc-a8c7-b23d3e5216fb}" EventSourceName="Microsoft-Windows-CAPI2" />
<EventID Qualifiers="0">513</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2011-12-15T23:38:24.430498600Z" />
<EventRecordID>144157</EventRecordID>
<Correlation ActivityID="{0450BC50-F800-0002-8457-553A80BBCC01}" />
<Execution ProcessID="1240" ThreadID="4360" />
<Channel>Application</Channel>
<Computer>Server1.domain.com</Computer>
<Security />
</System>
<EventData>
<Data>
Details:
AddCoreCsiFiles : GetNextFileMapContent() failed.
System Error:
The parameter is incorrect.
</Data>
</EventData>
</Event>
The System Writer is not showing up when I view vssadmin list writers.
I have already tried every tip in the following links:
http://technet.microsoft.com/en-us/library/cc734021(WS.10).aspx
http://social.technet.microsoft.com/Forums/en-US/windowsbackup/thread/bb760434-de80-4cb6-ae9e-bd253e4b037c/
I have also run sfc /scannow and rebooted. No luck.
I think the reason none of the tips at the above links work for me is that the System Error is NOT access denied like many others are getting, but is instead
The parameter is incorrect. I think that's the key.
Any ideas why I am getting this error and why my System Writer is nowhere to be found?

Hi,
You mentioned that “The System Writer is not showing up when I view vssadmin list writers.”
you may reboot the related services or re-register the writers, please refer to:
How to Re-register Volume Shadow Copy Service (VSS) Components on Windows 2008/Windows 2003.
http://www.symantec.com/business/support/index?page=content&id=TECH70486
Best regards,
Jeff Ren
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Windows 2012 System State Backup Fails

We have a Windows 2012 Domain Controller VM that we would like to backup the System State using DPM. Agent has been installed and the Windows Backup has been added.
When the backup runs in DPM, the job fails. Here is the error code:
DPM cannot create a backup because Windows Server Backup (WSB) on the protected computer encountered an error (WSB Event ID: 517, WSB Error Code: 0x12363C0). (ID 30229 Details: Internal error code: 0x80990ED0)
When we try and create the backup using Windows Backup, the following error is in the log file:
following error code '0x807800C5' (There was a failure in preparing the backup image of one of the volumes in the backup set.). Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.
We have tried attaching a separate drive and backup to a shared location. Both fail.
We have tried backup of just a few files on the DC instead of the System State, this fails as well.
All VSS Writers show as Stable with no errors
Server has the latest updates
Server has been rebooted, same issue
VM is Windows 2012 on a Windows 2008 R2 clustered host and is using Dynamic Disks (not fixed disks).
Anyone have any thoughts on what could be going on?

Hi,
If any of the following are true, you will not be able to backup a system state to that volume.
• Make sure that the target volume has no shadow copy before the backup starts.
• If a system state backup is stored on a source volume, backup settings should be configured for full backups. By default, settings are configured for full backups.
• Periodically check that no other user or program maintains a shadow copy on the target volume.
• Do not keep volume level backups and system state backups in the same location.
• The volume used to store the system state backup needs twice the amount of free space as the size of the system state backup until the backup completes
Meanwhile please check if it is caused that you are backing up to a critical drive. Try modify the following key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\wbengine\SystemStateBackup\
Set the value of this entry as follows:
Name: AllowSSBToAnyVolume
Data type: DWORD
Value data: 1
If you have any feedback on our support, please send to [email protected]

Failed to create the volume shadow copy inside of virtual machine 'SBS-SVR'

Hi there,
Currently only partial backups are being completed.
I receive the following error:
Writer Failures
Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
Instance Id: {B8818795-2E27-44A3-85AB-D4C3DDBD288E}
Writer Name: Microsoft Hyper-V VSS Writer
Writer State: 5
Failure Result: 80042336
Application Result: 80004005
Application Message: (null)
Component: 9E70CA9C-B992-425D-B091-95B76763BE39
Logical Path: (null)
Component Result: 800423F3
Component Message: Failed to create the volume shadow copy inside of virtual machine 'SBS-SVR'. (Virtual machine ID 9E70CA9C-B992-425D-B091-95B76763BE39)
File Spec: C:\ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines\\9E70CA9C-B992-425D-B091-95B76763BE39.xml Recursive: 0
File Spec: C:\Users\Public\Documents\Hyper-V\Virtual hard disks\\SBS-SVR-SYSTEM_404D40C1-A532-4272-AE8B-251C4A03B4F3.avhdx Recursive: 0
File Spec: C:\Users\Public\Documents\Hyper-V\Virtual hard disks\\SBS-SVR-SYSTEM.vhdx Recursive: 0
Application backup
Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
Component: 9E70CA9C-B992-425D-B091-95B76763BE39
Caption : Backup Using Child Partition Snapshot\SBS-SVR
Logical Path:
Error : 80780175
Error Message : Component was skipped from volume shadow copy.
Detailed Error : 800423F3
Detailed Error Message : The writer experienced a transient error. If the backup process is retried,
the error may not reoccur.
The success file is as follows:
Backup of volume \\?\Volume{72ec559c-60ca-11e2-93e8-806e6f6e6963}\ succeeded.
Backup of volume C: succeeded.
Application backup
Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
Component: Host Component
Caption : Host Component
Logical Path:
In the event logs: application, i found this:
The backup operation that started at '‎2014‎-‎05‎-‎18T11:00:22.221374600Z' has failed to back up volume(s) ''. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.
Some errors that are occuring that may be linked are:
Event Viewer, Application and Service Logs, Microsoft, Windows, Hyper-V-VMMS (the below is occuring every 2 minutes)
Failed to register the service principal name 'Hyper-V Replica Service'.
Failed to register the service principal name 'Microsoft Virtual System Migration Service'.
Failed to register the service principal name 'Microsoft Virtual Console Service'.
Upon some research I tried the following without much luck:
http://support.microsoft.com/kb/2761899
http://social.technet.microsoft.com/wiki/contents/articles/1340.hyper-v-troubleshooting-event-id-14050-vmms.aspx
Specs:
Microsoft Windows Server 2012 Standard x64
6.2.9200
ProLiant ML350e Gen8
VM: Microsoft® Windows Server® 2008 Standard FE x64
6.0.6002 Service Pack 2
Look forward to any help.
John

Hi John,
Please run “vssadmin list writers” command to check the VSS writer status. There is a similar thread, please go through it to help troubleshoot this issue:
Windows 2012 Backup for HyperV failed with error code '0x80780049'
http://social.technet.microsoft.com/Forums/windowsserver/en-US/f1a0c9c6-7b4c-409c-b4da-c145b8b59eb1/windows-2012-backup-for-hyperv-failed-with-error-code-0x80780049?forum=winserverhyperv
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.

Audio buzz and video cut-out caused by volume shadow service errors during updates and other services that create shadow copies

I have this issue and see throughout the Internet that my problem is shared by large numbers of other Windows 7 users, and a few Windows 8 users.
I also see that Microsoft has not addressed the issue.
I've been troubleshooting the problem for 13 months and across 3 separate hard drives on 2 separate computers, with the help of tech escalation from both Carbonite and Dell (whom I wanted to eliminate as causes, and who have been kind enough to assist even
after being eliminated as causes because they evidently care about customer service).
Over 13 months we have run system diagnostics, reinstalls and repairs to no avail. We have been able to reproduce the event in the absence of every attached device, every installed program, every subscribed service, and every hardware type and configuration.
We have visited chat rooms showing that this is a widespread problem (e.g., http://superuser.com/questions/630033/audio-video-glitch-when-shadow-copy-service-starts), and that even professional server administrators simply consign themselves to VSS being "the
bane of backup software" (http://community.spiceworks.com/topic/229743-problem-with-vss-writer-system-writer-timed-out).
Yet regardless of the computer or the configuration, the problem persists. It causes characteristic and alarming disk write error and memory spikes on the Resource Monitor that can be traced to huge numbers on the System 4 and VSSVC.exe processes, occurring
every time the Volume Shadow Copy Service and Application Experience create a restore point during an automatic update of Adobe, antivirus, etc.; and one can even provoke an event simply by manually creating a restore point, which has the bonus of triggering
an 8220 notice that the Volume Shadow Service has run out of time while deleting files. And the only advice I've seen from MS is that this is a "normal condition."
It is not normal to be unable to enjoy audio and video. And it is certainly not normal for one's PC to continually degrade with every update until it becomes unable to update and must be replaced.
I am on my 3rd computer with this problem (different type and configuration each time), and Dell has offered me an upgrade to Windows 8 in the hopes that the problem will not recur there. But I see from Microsoft's tech chat that Windows 8 users are reporting
the problem as well (http://answers.microsoft.com/en-us/windows/forum/windows_8-pictures/after-upgrading-to-windows-8-pro-there-is-an/813432c2-14f1-463f-bba3-ad322ceb6e00).
Please, please post a real answer to this problem. Thank you.

Hi,
Above all I understand the frustration as a same issue persists for a very long time.
At first I'm thinking if it is directly related to the application CrashPlan some customers mentioned in one of the threads you provided. However I then noticed that you said it could be also reproduced by creating a System Restore point.
Currently I cannot find a Windows 7 system so I used a Windows 8.1 laptop (also Dell) for testing.
I tried to play an online video and also a local video with creating a restore point in the middle. However I failed to reproduce the same behavior.
The following screenshot was captured in second test (play a local video):
I cannot confirm if it is because we have a large physical memory (8GB), or Windows 8.1 resolved this issue. From the screenshot, memory is not spiked (actually it is almost not changed).
So in current situation you can test to enlarge the size of physical memory (and virtual memory) for test if available. And as Dell provided a Windows 8 system, you can try it before and after installing Windows 8.1.
As a support engineer I also hope to help fix the issue or at least find out the cause. Later I will try to find a Windows 7 system for testing as well.
In addition, please understand that as the issue occurs mostly in Windows 7, though it seems related to VSS, it is still a Windows client system issue. So you can post the question to Windows 7 forum for further information. Here is the link:
http://social.technet.microsoft.com/Forums/en-US/category/w7itpro/
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Windows Server 2008 R2 System State Backup fails "the parameter is incorrect"

Hi,
I'm having the same problem as I've found in a few other threads.
http://social.technet.microsoft.com/forums/en-us/windowsbackup/thread/C633B2E6-1161-4146-BC09-C2712231F0EE
and
http://social.technet.microsoft.com/Forums/en-US/windowsbackup/thread/0b0f2d9c-e3b1-4f85-a6d2-2e15e5a15bc1
I've tried running the vshadow.exe -wm2 > out.txt command and searching the output for invalid paths, but I can't seem to find any paths that looks incorrect.
I've also done a registry search under HKLM\CurrentControlSet\Services for the / character and didn't come up with any in any paths either.
The server is a pretty new install. DC, DNS, DHCP, File and Print services. It has been running in production for about a week for a small business. Their previous server desperately needed changing over, so it got pushed in fairly quick. I never assumed
I would have had trouble with the system state backing up!. It would be nice to get it working so I can sleep at night :). The old DC is still running, so all is not lost in a failure, but still... I guess also once I've demoted the old DC, I can restore AD
just by restoring the entire system image (Don't have to worry about USN sync if only single DC), but I would still like a system state backup.
Thanks, Ryan

Hi,
Try to apply the following hotfix.
System state backup error in Windows Server 2008, in Windows Vista, in Windows 7 and in Windows Server 2008 R2: "Enumeration of the files failed"
http://support.microsoft.com/kb/980794
You may have to restart the computer after you apply this hotfix.
Jeff Ren TechNet Community Support beneficial to other community members reading the thread.

MSDN article KB955078 - System state backups failing in MSCS environment

Hello,
We have a an MSCS cluster running on Windows 2008 with SQL server 2008.
When we run a system state backup on the Passive node we get the error mentioned in Microsoft article KB955078 because of the SAP executables installed onto one of the shared disks.
Has anyone else encountered this and if so what did you do to resolve it?
Symantec have suggested we install the SAP executables on a local disk but if we do that then the cluster won't really work smoothly because the ASCS instance willl have to shut down. I'm not even convinced SAP would support this kind of install.
Any suggestions welcomed.
Regards
Garry Bayford

Hi Garry!
Possibly, as SAPinst installs the binaries on the shared drive in the cluster, those binaries will be listed as protected binaries.
The fact is that, neither in Windows Server 2003 nor in 2008 you can access a shared drive that is attached in one node from any other node in the same cluster, in a similar way that you cannot access a local drive of a computer from another computer. So the message is obvious: "the files (and the path) do not exist", as the drive indicated "do not exist" in the passive node.
In any case, if you want to access the SAP folders from the passive node you can do it without any troubles through the virtual network address associated to the SAP cluster group by means of the SAPMNT resource, i.e.
sapmnt.
This is what you should do if you want to backup any files. However I do not think that it is necessary to constantly back up the SAP binaries, as these do not change at all, until the moment that you update the kernel (and so, you can take a backup of the binaries just at that moment).
I hope that this sheds some light into your concern. Cheers!
-Jesú

System State Backup - 2008R2 - Volume Shadow Copy Error

Similar Messages

Maybe you are looking for