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??

This is a question from a new IT student... bare with me please...

I am trying to transfer data from a Windows Server 2003, so that I can remake the server.  I do not have admin rights to the server.  

Am I able to remove the disk drives and copy from another computer?  Any information as basic as it maybe is very helpful here... Thanks!!!

I am backing up the System State of a Domain Controller running Server 2012 R2 to a Synology NAS running Samba 3.6.9 (out of date, but it comes with the distribution).

When using SMB1 on the Synology NAS, the backup succeeds and authenticates as the user performing the backup (either the configured Domain User account with appropriate rights, or interactively with my account as a Domain Admin). However, when SMB2 is enabled on the Synology NAS, it appears as if the Computer Account, rather than the interactive Domain Admin account is attempting to read/write to the Samba share on the NAS.

From my understanding, Samba does not support adding Computer Accounts (COMPUTER$) to share security.

Why am I seeing this behavior difference from Windows Server? This also existed with Server 2012.

Trevor Seward

This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

In my lab I run a Hyper-V Server 2012 Core to run multiple test-systems virtualy. To backup my system I want to use the "Windows Server Backup" role/feature. This role/feature works fine on other systems (include Windows 2012 Server Core) but not with my Hyper-V Server 2012 Core Edition with TrueCrypt.

Problem: Starting a Backup on the Hyper-V Core over the Wbadmin command works fine (testet with c:). But if I want to schedule the backup over "Remote Computer Management" over the GUI, I receive the following error: "The parameter is incorrect" and I can't find any future information in e.g. in the EventViewer. The only thing, which I can use from the GUI-Menu is "Recover"<- this works. "Backup Schedule..." and "Backup Once..." rises the same error.

see Printscreen: http://i.stack.imgur.com/GPf47.png

System:

• Hyper-V Server 2012 6.2 (9200)
• Roles: File and Storage Service, Hyper-V
• Features: .NET Framework 3.5, .NET Framework 4.0, Windows Power Shell, Windows Server Backup, WoW64 Support
• TrueCrypt: Systempartition and all other Harddisks are encrypted

Any idea?

Creating a new backup job on my server, it will fail when trying the first run. I checked the Event Viewer, ran some online searches that suggested trying to disable the SQL VSS Writer. I did that, and now the initial backup completes.

Now the problem is, the next time the backup is scheduled to run, it fails. I checked the Event Viewer, and found this, 17 minutes after the backup kicked off:

Application Error Event ID 1000

"Faulting application wbengine.exe, version 6.0.6002.18005, time stamp 0x49e023c7, faulting module wbengine.exe, version 6.0.6002.18005, time stamp 0x49e023c7, exception code 0xc0000005, fault offset 0x00000000000d37fc, process id 0x2008, application start time 0x01cf0871f8ed12aa."

I've tried deleting the job, deleting the catalog, reregistering the VSS Writers, but no matter what, the above happens like clockwork when I start back over from scratch. Create job, disable SQL VSS Writer, backup succeeds. Next day (or next manual run), backup fails. 

Any information anyone can provide (preferably on the second issue) would be much appreciated. Thanks in advance!

VSS writers inside virtual machine 'CONTOSO' failed to perform BackupComplete to its shadow copy (VSS snapshot) set: Catastrophic failure (0x8000FFFF). (Virtual machine ID 9851BE14-F276-459D-8D60-DF73B67EB658)

What does it mean? Writers on virtual machine are OK and all backups are successfull. Every day I have one 10172 event for one backup in Hyper-V-VMMS event log.

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.

Writer name: 'Task Scheduler Writer'
   Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
   Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
   State: [1] Stable
   Last error: No error

Writer name: 'VSS Metadata Store Writer'
   Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
   Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
   State: [1] Stable
   Last error: No error

Writer name: 'Performance Counters Writer'
   Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
   Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
   State: [1] Stable
   Last error: No error

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {17daa546-f2b5-44a8-b88f-31fae0650076}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {75f7fecf-4696-4f0e-8d09-19809d5f35da}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {204ef83b-d168-4179-a6aa-ef01e93dae7d}
   State: [1] Stable
   Last error: No error

Writer name: 'WIDWriter'
   Writer Id: {8d5194e1-e455-434a-b2e5-51296cce67df}
   Writer Instance Id: {b45a4a13-60a4-4f38-bdc0-c4cc748f3513}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {aca59bd3-2f19-4c76-b54a-28f2c2d95f73}
   State: [1] Stable
   Last error: No error

Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {41ef02d7-38b9-424a-b35b-a4b1cf79bd17}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {7a6ef84a-4fff-46ed-8921-da0d12fb5028}
   State: [1] Stable
   Last error: No error

Writer name: 'MSSearch Service Writer'
   Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
   Writer Instance Id: {6d28a625-90a9-47a4-bf9f-fd8a6c76e770}
   State: [1] Stable
   Last error: No error

Writer name: 'MSMQ Writer (MSMQ)'
   Writer Id: {7e47b561-971a-46e6-96b9-696eeaa53b2a}
   Writer Instance Id: {5bca99fe-6db6-4994-a744-e4149ba54364}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {d8249c2a-530f-48e9-92c3-179762ed0064}
   State: [1] Stable
   Last error: No error

Writer name: 'TermServLicensing'
   Writer Id: {5382579c-98df-47a7-ac6c-98a6d7106e09}
   Writer Instance Id: {51f5c94d-514b-4ca7-b5dd-2f11047d6a54}
   State: [1] Stable
   Last error: No error

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {ce748865-451a-4189-8276-f2cb177629da}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {207fe098-42ab-430b-9285-c0b902729ade}
   State: [1] Stable
   Last error: No error

Hello all,

I am trying to use Windows Server Backup to run scheduled backups of my Hyper-V VMs. I am using the following configuration:

- Hyper-V Server 2012

- Backup volume attached via iSCSI from SNAPSERVER NAS

- Entire volume dedicated for use of full server backup.

I access the Backup GUI via a remote mmc connection. The GUI summary page suggests that the backups appear to have been running over the christmas period:

However, Hyper-V manager reports that the guest VMs are "Status: Backing Up" and I am unable to perform any operations on them (e.g. revert snapshot).

If I click on the detail menu (i.e. local backup in above image), the MMC will hang with a marquee box saying "Please Wait". I have left this run for over an hour without it changing. I am then forced to kill the MMC in task manager.

Running wbadmin from a remote PS session, I can see that the backup job is stuck at 76% on the first VM. Using the stop job command, seems successful (i.e get status shows job has stopped before completion) but the machines still show as "backing up" in Hyper-V manager, and the command prompt does not return to the 'prompt'

The only resolution I have found to this is to restart the physical hyper-v host. As this is a production server, this is something that I REALLY want to avoid.

The error logs on the hyper-v server are filled with vhdmp error 129 "Reset to device .. was issued". This error is created every 30 seconds.

I think I am slowly coming to the realisation that I have to pay out for thrid party software :-(. Any help would be appreciated..

Additional Info:

I had a similar issue trying to run the same process, only within a 2012 Guest VM.

I ran through the Backup Wizard, selected the System, OS, and my Data drives to backup. total output is probably about 400-500GB of data to be snapshot and backed up. It's set to automatically backup daily at 9:00pm, but upon the first backup it just sits there. I figured I'd let it ride until the next day since I've seen backups take a couple hours before.

Well, It's more than 12 hours since it started the process, and I cannot access my server. It doesn't wake the screen, CTRL-Alt-Del doesn't do anything, and I can't remote in with RDP.

Any advice? I haven't shut it down or forced a reboot yet. 

Hi all,After upgrading from 2003 to exchange 2013 we are facing outlook disconnects and immediately restores but this happens after every 20 minutes. Outlook client is outlook 2007 sp3. There is no issues in the networks. Is there is outlook version issue or network issue. I will check again in the network if u all say it. Please help me in this. Thanks

Hi!

Windows Server 2008 Standard x86, full patched, after changing failed disk (one in RAID-1) doesn't correctly create system state backup.

Backup started and after copy some data i.e. 1,49 GB stopped with message "device is not ready". In Application log is write message

Log Name:      Application
Source:        Microsoft-Windows-Backup
Date:          2013-08-26 00:03:36
Event ID:      517
Task Category: None
Level:         Error
Keywords:      
User:          SYSTEM
Computer:      HOSTNAME.DOMAIN.NAME
Description:
The description for Event ID 517 from source Microsoft-Windows-Backup cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

EV_RenderedValue_0,00
2147942421
%%2147942421

The resource loader failed to find MUI file

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>517</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2013-08-25T22:03:36.552Z" />
    <EventRecordID>154664</EventRecordID>
    <Correlation />
    <Execution ProcessID="4036" ThreadID="4192" />
    <Channel>Application</Channel>
    <Computer>HOSTNAME.DOMAIN.NAME</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="BackupTime">2013-08-25T22:02:05.905Z</Data>
    <Data Name="ErrorCode">2147942421</Data>
    <Data Name="ErrorMessage">%%2147942421</Data>
  </EventData>
</Event>

I've checked system partition with chkdsk /f /r  - without errors.

How I can correct this situation.

Regards

Wojciech Sciesinski

I have the similar Problem such as many other users with the backup programm but:

- i have a Windows 7 System as Backup-Target (No NAS !!!!)

- i cannot backup over VPN but when i do it local to the same Windows 7 machine, everything is OK

The VPN runs perfectly. I can copy big files without Problems (bandwith is 10 MBit/s). I can do the Backup per Windows Server Backup or per wbadmin - the result is the same. I will make a Bare Metal Recovery Image.

Where is the problem ? The only differences between local backup and VPN-backup is the smaller bandwith and the higher latency.

Hello All,

I have a HP server that I have just installed Server 2012 standard, SQL Server 2012 and Sharepoint 2013.

When I try to take bare metal backup I get the error: "The system writer is missing", I have tried the backup as the local admin and domain admin.

The backup will only work if I decide to back up C:, once I select "Bare Metal" or "System State" the backup fails.

I have tried this solution: http://technet.microsoft.com/en-us/library/cc734021.aspx but have not had any luck yet.

When I run the command "vssadmin list writers" I can not see "System Writer" listed.

How can I add/turn on the System Writer?

Hi everybody,

on our SBS 2008 EventViewer says Backup Succeeded, no further errors shown.
But when I try to recover files or Volumes, data Partition "D" is not shown. Server-Manager -> Storage -> Windows-Server-Backup says "Completed with Warnings", and Details show:

"D:The request could not be performed because of an I/O device error"

But in WindowsImageBackup there is a vhd of the appropriate size.

ChkDsk says no errors on both backup and destination drive. What now?

Thanks,
Thilo

I have an error when i launch a backup with this command wbadmin start systemstatebackup -backuptarget:h:.

Nom du journal :Application
Source :       Application Error
Date :         10/01/2014 11:55:00
ID de l'événement :1000
Catégorie de la tâche :(100)
Niveau :       Erreur
Mots clés :    Classique
Utilisateur :  N/A
Ordinateur :   srv-logiciel.raimu.local
Description :
Application défaillante wbengine.exe, version 6.0.6002.18005, horodatage 0x49e023c7, module défaillant wbengine.exe, version 6.0.6002.18005, horodatage 0x49e023c7, code d’exception 0xc0000005, décalage d’erreur 0x00000000000362ba, ID du processus 0x19cc, heure de début de l’application 0x01cf0df1b1726c06.
XML de l’événement :
<Event xmlns="
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-01-10T10:55:00.000Z" />
    <EventRecordID>5496897</EventRecordID>
    <Channel>Application</Channel>
    <Computer>srv-logiciel.raimu.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>wbengine.exe</Data>
    <Data>6.0.6002.18005</Data>
    <Data>49e023c7</Data>
    <Data>wbengine.exe</Data>
    <Data>6.0.6002.18005</Data>
    <Data>49e023c7</Data>
    <Data>c0000005</Data>
    <Data>00000000000362ba</Data>
    <Data>19cc</Data>
    <Data>01cf0df1b1726c06</Data>
  </EventData>
</Event>

Result of vssadmin list writers

vssadmin 1.1 - Outil ligne de commande d'administration du service
de cliché instantané de volume
(C) Copyright 2001-2005 Microsoft Corp.

Nom du rédacteur : 'ASR Writer'
   ID du rédacteur : {be000cbe-11fe-4426-9c58-531aa6355fc4}
   ID de l'instance du rédacteur : {3f47a346-a58f-4dfc-bae3-d609f3ac27b2}
   État : [1] Écurie
   Dernière erreur : Aucune erreur

Nom du rédacteur : 'System Writer'
   ID du rédacteur : {e8132975-6f93-4464-a53e-1050253ae220}
   ID de l'instance du rédacteur : {978d43f5-b096-4567-aed2-2a024eac9c7d}
   État : [1] Écurie
   Dernière erreur : Aucune erreur

Nom du rédacteur : 'WMI Writer'
   ID du rédacteur : {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   ID de l'instance du rédacteur : {abd4b941-489d-4709-91da-3f4f3ed72b66}
   État : [1] Écurie
   Dernière erreur : Aucune erreur

Nom du rédacteur : 'Shadow Copy Optimization Writer'
   ID du rédacteur : {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   ID de l'instance du rédacteur : {eb44e074-6fdc-446a-ac5e-65b69163f30c}
   État : [1] Écurie
   Dernière erreur : Aucune erreur

Nom du rédacteur : 'Registry Writer'
   ID du rédacteur : {afbab4a2-367d-4d15-a586-71dbb18f8485}
   ID de l'instance du rédacteur : {fd72df2e-e98f-4895-8973-2a2fced4ec59}
   État : [1] Écurie
   Dernière erreur : Aucune erreur

Nom du rédacteur : 'COM+ REGDB Writer'
   ID du rédacteur : {542da469-d3e1-473c-9f4f-7847f01fc64f}
   ID de l'instance du rédacteur : {088d0edf-ee27-490d-a1df-6d6410309d7e}
   État : [1] Écurie
   Dernière erreur : Aucune erreur

Nom du rédacteur : 'Dhcp Jet Writer'
   ID du rédacteur : {be9ac81e-3619-421f-920f-4c6fea9e93ad}
   ID de l'instance du rédacteur : {98503db9-91f3-4926-8858-663eea6a961d}
   État : [1] Écurie
   Dernière erreur : Aucune erreur

Nom du rédacteur : 'IIS Config Writer'
   ID du rédacteur : {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   ID de l'instance du rédacteur : {e86af11c-3c01-4169-b755-41e1617b43f8}
   État : [1] Écurie
   Dernière erreur : Aucune erreur

Nom du rédacteur : 'BITS Writer'
   ID du rédacteur : {4969d978-be47-48b0-b100-f328f07ac1e0}
   ID de l'instance du rédacteur : {248646da-e186-4b44-b5a9-d3d4709b7ed2}
   État : [1] Écurie
   Dernière erreur : Aucune erreur

PS: I search in the forum and I don't found any solution.

Could you help me, please?

In our site office we have Windows Server 2003 installed on DELL Power Edge 1900 having three hard disks of 250 gb each and RAID 5 configured

 In this server we had Folders which were shared in office network. One of the hdd went faulty and also the OS crashed with Nt kernel file corrupted.

 Data recovery utility was run and after the completion of the process Windows Server 2008 was loaded to view the folders.  The entire data is not seen in the folders.

 Is this because the file system of two Server OS ( 2003 and 2008) is different and so the folders are  not available?

Hi,

I am trying activate to windows server 12 Standard edition but it is not being success and show error code 0x8007232B and DNS name does not exit, Please give me solution ASAP.

Thanks

Waish Khan

I'm administering a network system which I built and installed for a local company.

I set up wbadmin to backup the server (Windows Server 2012) to a local computer and then move the files to a NAS drive. (wbadmin would not store the backup on the NAS).

All was working well until I installed another 2 hard drives (E:) on a raid controller to supplement the raid boot drives (C:).  I moved the server folders over to the E: drive and edited my batch program to include drive E: in the backup.

Since then the system generates an error stating that the operation has stopped. The parameter is incorrect.

I have Google'd this error for over a month now but to no avail.

I've shrunk the E: drive from 2Tb to less than 1Tb but no change.

I've rewritten the batch file to backup C: and then after the files have been moved onto the NAS to backup E:.  The C: drive backs up but then the error appears again when E: tries to back up.

Batch File: -

@echo off
setlocal
set currentdate=%date:/=-%
set target=\\Shop-PC\ServerBackup\
set log=%target%backup log %computername% %currentdate%.txt
set errorlog=%target%backup error log %computername% %currentdate%.txt
set backuptarget=%target%WindowsImageBackup\%computername%
set desiredtarget=%target%%computername% - %currentdate%
set nastarget=\\NAS\ServerBackup\Saturday

(
 wbadmin start backup -backupTarget:%target% -include:c:\,e:\ -allCritical -systemState -user:CardrossAdmin -password:Cardros1895s -vssFull -quiet 
) 1>>"%log%" 2>>"%errorlog%"

RMDIR "%nastarget%" /S /Q 

MD "%nastarget%"

move "%backuptarget%" "%desiredtarget%"

xcopy %target% %nastarget% /E /C /H /Y

RMDIR "%desiredtarget%" /S /Q 

DEL "%target%\*.TXT"

endlocal

Any assistance in resolving this issue would be greatly appreciated.