I'm having trouble backing up one of our servers.

I've tried to take a manual shadow copy, but that fails too.

This is the output from the diskshadow:

DISKSHADOW> set context persistent

DISKSHADOW> set verbose on
istent
DISKSHADOW> add volume C:

istent
DISKSHADOW> add volume \\?\Volume{21d0911e-a727-11e2-8124-806e6f6e6963}\

DISKSHADOW> create
me \\?\Volume{21d0911e-a727-11e2-8124-806e6f6e6963}\Excluding writer "Shadow Copy Optimization Writer", because all of its components have been excluded.

* Including writer "Task Scheduler Writer":+ Adding component: \TasksStore

* Including writer "VSS Metadata Store Writer":+ Adding component: \WriterMetadataStore

* Including writer "Performance Counters Writer":+ Adding component: \PerformanceCounters

* Including writer "SqlServerWriter":+ Adding component: \ASTAREG-APP01\ASTAREG\master
--removed several lines to keep it readable. (approx 1400 lines)+ Adding component: \ASTAREG-APP01\ASTAREG\unit_450

* Including writer "System Writer":+ Adding component: \System Files

* Including writer "ASR Writer":+ Adding component: \ASR\ASR+ Adding component: \Volumes\Volume{21d0911e-a727-11e2-8124-806e6f6e6963}+ Adding component: \Volumes\Volume{21d0911f-a727-11e2-8124-806e6f6e6963}+ Adding component: \Disks\harddisk0+ Adding component: \BCD\BCD

* Including writer "Registry Writer":+ Adding component: \Registry

* Including writer "COM+ REGDB Writer":+ Adding component: \COM+ REGDB

* Including writer "WMI Writer":+ Adding component: \WMI

The last operation failed.
	- Returned HRESULT: 80042302
	- Error text: VSS_E_UNEXPECTED

Output from vssadmin list writers:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\administrator.LOCAL>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Waiting for responses.
These may be delayed if a shadow copy is being prepared.

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: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {1642a445-03f7-47aa-8c2a-026970ffe2a5}
   State: [11] Failed
   Last error: Retryable error

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {c7f14ce1-862d-469c-a0f6-4d04f40a6154}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {8b7f6ee8-caec-426f-9bb8-a4604676be94}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {31e7e45c-a2d2-444a-9658-08f51e1223c5}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {03f58120-3f0f-4388-8d79-b18780dac432}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {33d15e4b-bf9e-4fd5-a85c-491b55cda09e}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {b048fc99-96a3-4c76-8077-a5e85f34c768}
   State: [1] Stable
   Last error: No error

I have a brand new 2008R2 SP1 server (Domain Controller) where I try to make SystemState backup. Backup seems to work fine, but I can not delete oldest.
I'm uncertain if I do have a valid SS backup.

I take backup with this command:

C:\>wbadmin start systemstatebackup -backuptarget:D:
wbadmin 1.0 - Backup command-line tool
(C) Copyright 2004 Microsoft Corp.

Starting to back up the system state [04-08-2011 08:45]...
Retrieving volume information...
This will back up the system state from volume(s) Local Disk(EFI System Partitio
n) (200.00 MB),C-OS(C:) to D:.
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...
Windows Server Backup is updating the backup for deleted items.
This might take a few minutes.
Found (96) files.
Found (13207) files.
Found (29482) files.
Found (39566) files.
Found (78588) files.
Found (79088) files.
The search for system state files is complete.
Starting to back up files...
The backup of files reported by 'Task Scheduler Writer' is complete.
The backup of files reported by 'VSS Metadata Store Writer' is complete.
The backup of files reported by 'Performance Counters Writer' is complete.
Overall progress: 1%.
Currently backing up files reported by 'System Writer'...
 - continuing to 100% -

Summary of the backup operation:
------------------

The backup of the system state successfully completed [04-08-2011 08:59].
Log of files successfully backed up:

--------------------------------------------------------------------------------------------

If I check the backup with "Get Versions", I get this:

--------------------------------------------------------------------------------------------

C:\>wbadmin get versions
wbadmin 1.0 - Backup command-line tool
(C) Copyright 2004 Microsoft Corp.

Backup time: 30-07-2011 21:00
Backup target: Fixed Disk labeled D:
Version identifier: 07/30/2011-19:00
Can recover: Volume(s), File(s), Application(s), System State
Snapshot ID: {6f4f38c8-3d3c-4e9f-87fb-d7cdb9c13c59}
 - several other backups-

Backup time: 04-08-2011 08:45
Backup target: Fixed Disk labeled D:
Version identifier: 08/04/2011-06:45
Can recover: Volume(s), File(s), Application(s), System State
Snapshot ID: {ae749899-447f-4c6d-b2d3-06c2f1816541}

--------------------------------------------------------------------------------------------

So far everything seems ok.
But when I try to delete the oldest backup, things look weired:

--------------------------------------------------------------------------------------------

C:\wbadmin delete systemstatebackup -deleteOldest
wbadmin 1.0 - Backup command-line tool
(C) Copyright 2004 Microsoft Corp.

Enumerating system state backups...
ERROR - No system state backups were found.
This command can be used to delete backups that only contain the system state.

--------------------------------------------------------------------------------------------

If I try with -keepversions, I get same result:

--------------------------------------------------------------------------------------------

C:\>wbadmin delete systemstatebackup -keepversions:1
wbadmin 1.0 - Backup command-line tool
(C) Copyright 2004 Microsoft Corp.

Enumerating system state backups...
ERROR - No system state backups were found.
This command can be used to delete backups that only contain the system state.

-------------------------------------------------------------------------------------------- 

So do I have a valid Systemstate backup ?
And can I trust I can use it to recover if needed, since it says "No system state backups were found" ?
And why can't I delete the oldest backup ?

- Duelund

This is on Windows Server 2012R2 Essentials specifically. But I saw the same behavior on 2012 Essentials before switching.

Both on the Dashboard's alerts and daily health reports, it indicates that one or more drives are unhealthy and need to be fixed. However, it does not list any disk specifically. This occurs several minutes after the backups are scheduled, and will change when it happens if I change the time for the backups. 

This happens EVERY DAY. Deleting or ignoring the reports just cause it to come back. Disabling backups, or disconnecting the drive they're stored on doesn't fix it. Neither does formatting the drive and setting up backups again.

I've not found any specific errors, and I've scanned the system partitions using their volume ID, and that hasn't helped.

No virus scanner nor disk tools are installed. There are no 3rd party file system filters installed either.

The Event Viewer doesn't indicate any issues specifically either.

This is frustrating and annoying.

Hi all.

Why do we non-authoritative restore? Much easier to promote new server and replicate it.

Hi,

I have read through for forum to see any previous posts that can apply to the problem I have. There are a few but none of those are answered with solution. If anyone knows the answer for fixing my backup problem below, I will send a million thanks :)

I have a Windows server 2012 R2 standard running as a file server. It has drives as below:

C drive: O/S

D drive: DVD rom

E drive: data. Shared folder. Users map to shared folder in E drive

F drive: Backups drive. Use it to backup the "E\share" folder

E drive has a folder called "share". This folder has about 2TB

F drive has 4.5TB. It's a set of raided drives, Raid 5 using Dell Powervault MD 1000

I'm using the built-in Windows server backup utility(wbadmin) to backup E\share to F drive. The problem is that the backup utility can only keep 1(one) backup file. The properties of F drive shows it has plenty of space. However, if I run 5 backups within one day, it does NOT delete previous backups. The problem is it delete all backups when next day the backup runs. Question is:

Why doesn't it delete other backups ran within the same day?

Why does it delete all backups on the next day it runs the backup?

It appears that it's not the hardware or F drive issues in my case. It's something with configuration or setting under Windows registry and it flags to delete all backups on the next day the wbadmin backup runs. I already formatted and re-installed Windows server 2012 on this machine and it does the same. Did anyone in here ever have this weir situation like this before? I also replaced all the drives in MD1000 to make a new F drive but the backup still does the same.  It's weirder than weird. I have spent my time for last 3 weeks but could not find a solution to fix this issue. Please help...

Hi! 

I have a following error while doing scheduled backups: "Failure while compacting the virtual disk on the backup location"OS is Server 2012 R2 Essential 

I use a dedicated HDD for backups. Its a WD GREEN 3TB. 

Any suggestions? 

LOGS:

• EROOR: The backup operation that started at '‎2014‎-‎06‎-‎27T00:57:25.744931200Z' has failed with 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.
• WARNING: The backup operation that started at '‎2014‎-‎06‎-‎26T16:30:31.944377600Z' has completed with errors. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.

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 regards

Hi, 

I have a script running the below 

Wbadmin start backup -backupTarget:\\192.*.*.*\Jupitor\serverBackup\%dd%%mm%\CDrive -include:C: -vssFull -quiet > cDrive_log.txt
Wbadmin start backup -backupTarget:\\192.*.*.*\jupitor\serverBackup\%dd%%mm%\DDrive -include:D: -vssFull -quiet > dDrive_log.txt

I run this command wbadmin start recovery -version: ***********-** -itemtype:file -items:d:\bkup\monday\**.dbf  it shows me "invalid specific path"

Thanks and Regards Cityuser

I am having trouble restoring an existing backup using windows server backup. The backup is stored on a network share. 

I goto recovery wizard > a backup stored on another location > remote shared folder > and then I enter my shared folder: 

\\share-pc\SERVERNAME\WindowsImageBackup\SERVERNAME\Backup 2014-12-05 013008

I then get this message:

"The specified remote share does not contain any backups. Provide a path to a remote shared folder that contains backups."

 I have confirmed that all of the following paths fail:

\\share-pc\SERVERNAME\WindowsImageBackup\SERVERNAME\Backup 2014-12-05 013008

\\share-pc\SERVERNAME\WindowsImageBackup\SERVERNAME\

\\share-pc\SERVERNAME\WindowsImageBackup\

\\share-pc\SERVERNAME\

I can ping the machine and mount the shares on the server as well.

Any thoughts?

Dear Sir,

I was keeping all my in and out emails in Microsoft outlook.

Suddenly i had a Virus in my laptop, and all my sent/received emails were lost and i do not have any backup.

Could you please see if you have my emails in your server, send them to me to my email account:

m.nasr@ipglebanon.com

Will appreciate very much

Thank you

Mohammad Abou El Nasr

Hey community,

i`m reading these topics since years. All issues could be resolved so far. But since yesterday i`m really afraid. I think i can`t solve this issue without you specialists.

I´m running a Hyper V (Server 2012 R2 Core) with currently three VM`s on it.
I like to initiate a host based backup with "wbadmin".

The used command ist: wbadmin start backup -backupTarget:B:\ -hyperv:"VMS030"

The VM has three disks: Fast Storage 400gb, Slow Storage 500 GB, Paging on SSD`s 15 gb.
I assigned 30.720 megabytes of RAM to this VM.

The other VM`s are much smaller. The Backup is working on these VM`s without any errors.
Now... what`s special about this VM? The VM is a SBS2011 with Exchange, SQL Server and AD on it.

The wbadmin command fails with

Detaillierter Fehler: FEHLER - Vorgangsfehler im Volumeschattenkopie-Dienst (0x8
00423f4)
Für den Generator wurde ein nicht vorübergehender Fehler festgestellt. Wenn der
Sicherungsvorgang wiederholt wird,
tritt der Fehler höchstwahrscheinlich erneut auf.

I´m looking for a workaround or a fix since hours on different error-ids. But cannot resolve it.
There WindowsServerBackup-Log tells me this:

Fehler des Writers
Writer-ID: "{66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}"
Instanz-ID: "{02FFB0A1-6658-4EBF-A79E-ACD7C00038BB}"
Name des Writers: "Microsoft Hyper-V VSS Writer"
Status des Writers: "8"
Fehlerergebnis: "800423F4"
Anwendungsergebnis: "80004005"
Anwendungsmeldung: "(null)"
   Komponente: "1415E5AA-E823-4586-A84D-CF3DB849E8B4"
   Logischer Pfad: "(null)"
   Komponentenergebnis: "800423F4"
   Komponentenmeldung: (null)
       Dateiangabe: "A:\Virtual Machines\\1415E5AA-E823-4586-A84D-CF3DB849E8B4.xml", rekursiv: "0"
       Dateiangabe: "A:\\vms030.vhdx", rekursiv: "0"
       Dateiangabe: "P:\\vms030-pagin.vhdx", rekursiv: "0"
       Dateiangabe: "R:\\vms030-ressources.vhdx", rekursiv: "0"
       Dateiangabe: "A:\Snapshots\F60A2B69-C801-4656-AF69-6C4643FCA18D.xml", rekursiv: "0"
       Dateiangabe: "A:\Snapshots\F60A2B69-C801-4656-AF69-6C4643FCA18D\*", rekursiv: "0"
       Dateiangabe: "A:\\vms030_F60A2B69-C801-4656-AF69-6C4643FCA18D.avhdx", rekursiv: "0"
       Dateiangabe: "P:\\vms030-pagin_F60A2B69-C801-4656-AF69-6C4643FCA18D.avhdx", rekursiv: "0"
       Dateiangabe: "R:\\vms030-ressources_F60A2B69-C801-4656-AF69-6C4643FCA18D.avhdx", rekursiv: "0"
*-----------------------------*


Anwendungssicherung
Writer-ID: "{66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}"
   Komponente: "1415E5AA-E823-4586-A84D-CF3DB849E8B4"
   Beschreibung     : Offline\VMS030
   Logischer Pfad: ""
   Fehler           : 80780175
   Fehlermeldung   : Eine Komponente wurde bei der Schattenkopie des Volumes übersprungen.

   Detaillierter Fehler  : 800423F4
   Detaillierte Fehlermeldung : Für den Generator wurde ein nicht vorübergehender Fehler festgestellt. Wenn der Sicherungsvorgang wiederholt wird,
tritt der Fehler höchstwahrscheinlich erneut auf.

This is the output of Backup Logs in Event Viewer

Die Beschreibung für die Ereignis-ID "5" aus der Quelle "Microsoft-Windows-Backup" wurde nicht gefunden. Entweder ist die Komponente, die dieses Ereignis auslöst, nicht auf dem lokalen Computer installiert, oder die Installation ist beschädigt. Sie können die Komponente auf dem lokalen Computer installieren oder reparieren.

Falls das Ereignis auf einem anderen Computer aufgetreten ist, mussten die Anzeigeinformationen mit dem Ereignis gespeichert werden.

Die folgenden Informationen wurden mit dem Ereignis gespeichert:

EV_RenderedValue_0,00
2155348041
0
%%2155348041
12
06.12.2014 09:58:00
B:
0
<VolumeInfo></VolumeInfo>
06.12.2014 09:58:00
06.12.2014 09:58:28<TimesList></TimesList><TimesList></TimesList><TimesList></TimesList><TimesList></TimesList>
01.01.1601 00:00:00
01.01.1601 00:00:00<TimesList></TimesList><TimesList></TimesList><TimesList></TimesList><TimesList></TimesList>
19<ComponentStatus><ComponentStatusItem Name="1415E5AA-E823-4586-A84D-CF3DB849E8B4" LogicalPath="" Caption="Offline\VMS030" AppId="HyperV" WriterId="{66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}" InstanceId="{02ffb0a1-6658-4ebf-a79e-acd7c00038bb}" ConsistencyCheckResult="-2139618955" ConsistencyCheckResultDetailed="-2147212300"/></ComponentStatus><ComponentInfo><ComponentInfoItem WriterId="{66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}" InstanceId="{02ffb0a1-6658-4ebf-a79e-acd7c00038bb}" Name="1415E5AA-E823-4586-A84D-CF3DB849E8B4" LogicalPath="" Caption="Offline\VMS030" AppName="HyperV" hResult="-2139618955" hDetailedResult="-2147212300" IsFullBackup="1" FullBackupReason="0" Size="0" DataTransferred="0" TotalNoOfFiles="0" /></ComponentInfo>
01.01.1601 00:00:00
01.01.1601 00:00:00
01.01.1601 00:00:00
01.01.1601 00:00:00
01.01.1601 00:00:00
01.01.1601 00:00:00<SystemState IsPresent="0" HResult="0" DetailedHResult="0" /><BMR IsPresent="0" HResult="0" DetailedHResult="0" />
False
False
False
C:\Windows\Logs\WindowsServerBackup\Backup-06-12-2014_09-58-00.log
C:\Windows\Logs\WindowsServerBackup\Backup_Error-06-12-2014_09-58-00.log<TimesList></TimesList><TimesList></TimesList><TimesList></TimesList><TimesList></TimesList>
5<ComponentInfoSummary ComponentInfoArrayPresent="1" TotalComponents="1" SucceededComponents="0" />

Das Handle ist ungültig

And finally the Apps Errorlog from Eventviewer:

Die Beschreibung für die Ereignis-ID "1001" aus der Quelle "Windows Error Reporting" wurde nicht gefunden. Entweder ist die Komponente, die dieses Ereignis auslöst, nicht auf dem lokalen Computer installiert, oder die Installation ist beschädigt. Sie können die Komponente auf dem lokalen Computer installieren oder reparieren.

Falls das Ereignis auf einem anderen Computer aufgetreten ist, mussten die Anzeigeinformationen mit dem Ereignis gespeichert werden.

Die folgenden Informationen wurden mit dem Ereignis gespeichert:

0
Windows Server Backup Error
Nicht verfügbar
0
2
1
0x80780049
0x00000000
0x00000000
0x00000000
0x00000000
0x800423f4
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_2_13a53d7aa8e7829769665e4df6f1cf697e2cbfe_00000000_17a9bb93
0
6f6092af-7d2e-11e4-8144-c860008e5417
4100

Das Handle ist ungültig

Die Beschreibung für die Ereignis-ID "517" aus der Quelle "Microsoft-Windows-Backup" wurde nicht gefunden. Entweder ist die Komponente, die dieses Ereignis auslöst, nicht auf dem lokalen Computer installiert, oder die Installation ist beschädigt. Sie können die Komponente auf dem lokalen Computer installieren oder reparieren.

Falls das Ereignis auf einem anderen Computer aufgetreten ist, mussten die Anzeigeinformationen mit dem Ereignis gespeichert werden.

Die folgenden Informationen wurden mit dem Ereignis gespeichert:

06.12.2014 09:58:00
2155348041
%%2155348041

Das Handle ist ungültig

Die Beschreibung für die Ereignis-ID "8224" aus der Quelle "VSS" wurde nicht gefunden. Entweder ist die Komponente, die dieses Ereignis auslöst, nicht auf dem lokalen Computer installiert, oder die Installation ist beschädigt. Sie können die Komponente auf dem lokalen Computer installieren oder reparieren.

Falls das Ereignis auf einem anderen Computer aufgetreten ist, mussten die Anzeigeinformationen mit dem Ereignis gespeichert werden.

Die folgenden Informationen wurden mit dem Ereignis gespeichert:


Das Handle ist ungültig

Die Beschreibung für die Ereignis-ID "517" aus der Quelle "Microsoft-Windows-Backup" wurde nicht gefunden. Entweder ist die Komponente, die dieses Ereignis auslöst, nicht auf dem lokalen Computer installiert, oder die Installation ist beschädigt. Sie können die Komponente auf dem lokalen Computer installieren oder reparieren.

Falls das Ereignis auf einem anderen Computer aufgetreten ist, mussten die Anzeigeinformationen mit dem Ereignis gespeichert werden.

Die folgenden Informationen wurden mit dem Ereignis gespeichert:

06.12.2014 09:58:00
2155348041
%%2155348041

Das Handle ist ungültig

Die Beschreibung für die Ereignis-ID "1001" aus der Quelle "Windows Error Reporting" wurde nicht gefunden. Entweder ist die Komponente, die dieses Ereignis auslöst, nicht auf dem lokalen Computer installiert, oder die Installation ist beschädigt. Sie können die Komponente auf dem lokalen Computer installieren oder reparieren.

Falls das Ereignis auf einem anderen Computer aufgetreten ist, mussten die Anzeigeinformationen mit dem Ereignis gespeichert werden.

Die folgenden Informationen wurden mit dem Ereignis gespeichert:

0
Windows Server Backup Error
Nicht verfügbar
0
2
1
0x80780049
0x00000000
0x00000000
0x00000000
0x00000000
0x800423f4
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_2_13a53d7aa8e7829769665e4df6f1cf697e2cbfe_00000000_17a9bb93
0
6f6092af-7d2e-11e4-8144-c860008e5417
4100

Das Handle ist ungültig

Die Beschreibung für die Ereignis-ID "16387" aus der Quelle "SPP" wurde nicht gefunden. Entweder ist die Komponente, die dieses Ereignis auslöst, nicht auf dem lokalen Computer installiert, oder die Installation ist beschädigt. Sie können die Komponente auf dem lokalen Computer installieren oder reparieren.

Falls das Ereignis auf einem anderen Computer aufgetreten ist, mussten die Anzeigeinformationen mit dem Ereignis gespeichert werden.

Die folgenden Informationen wurden mit dem Ereignis gespeichert:

Microsoft Hyper-V VSS Writer
Für den Generator wurde ein nicht vorübergehender Fehler festgestellt. Wenn der Sicherungsvorgang wiederholt wird, tritt der Fehler höchstwahrscheinlich erneut auf. (0x800423F4)
Unbekannter Fehler (0x80004005)

Das Handle ist ungültig

Die Beschreibung für die Ereignis-ID "8229" aus der Quelle "VSS" wurde nicht gefunden. Entweder ist die Komponente, die dieses Ereignis auslöst, nicht auf dem lokalen Computer installiert, oder die Installation ist beschädigt. Sie können die Komponente auf dem lokalen Computer installieren oder reparieren.

Falls das Ereignis auf einem anderen Computer aufgetreten ist, mussten die Anzeigeinformationen mit dem Ereignis gespeichert werden.

Die folgenden Informationen wurden mit dem Ereignis gespeichert:

0x800423f4, Für den Generator wurde ein nicht vorübergehender Fehler festgestellt. Wenn der Sicherungsvorgang wiederholt wird,
tritt der Fehler höchstwahrscheinlich erneut auf.



Vorgang:
   PrepareForSnapshot-Ereignis

Kontext:
   Ausführungskontext: Writer
   Generatorklassen-ID: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
   Generatorname: Microsoft Hyper-V VSS Writer
   Generatorinstanz-ID: {02ffb0a1-6658-4ebf-a79e-acd7c00038bb}
   Befehlszeile: C:\Windows\system32\vmms.exe
   Prozess-ID: 1852

Das Handle ist ungültig

Do you guy`s have any clue how i can resolve this?

As i said ... i can backup a few smaller VM`s. Only the "Big one" fails.
I already thought about a disk space issue ... But there is at least 30 % of free space on each disk.

Thank you all!

Hello

i have HP server ( Windows server 2012 r2 )
some problems in my systems and i want to make format to the server and i have 6 Hyper -v Licenses
but if i make format and install the windows server a gain how can i get my windows server Licenses ?

thanks 

Host and VMs:  Server 2012 (Fully patched and unfortunatey not R2).

When this occurs the VM becomes unresponsive for a period of time and then this error is generated on host.  The other VM remains responsive w/o error at any point.  No backups or shadow copies should be taking place at this time and I've confirmed as much.  Backups are always successful when they run.  Have a bit of a strange setup here (Not designed by me).  Have two RAID arrays.  One is the C: partition at 275GB w/ 79GB free and the other is 557GB and it is offline and passed through to the VM as the SQL data drive.  This is how it was done and unfortunately how it needs to remain.  I do not get the below error daily but it does happen a few times a month but the time/day is never consistent.  Oddly though the VM isn't always unresponsive (At least the customer doesn't contact me if it is) when this error is generated.  Other day errors are exact except the VolumeShadowCopy number is different (See error below and you'll understand what I mean).  I have a sneaking suspicion that the issues is due to the lack of enough space to create a shadow copy of the VM on Host C: but I don't know why this wouldn't occur every day if that was in fact the issue.

The error I feel is causing the VM to become unresponsive: (Checking  Details|XML view in Event viewer for this error does point to the problematic VM)

The description for Event ID 36 from source volsnap 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:

\Device\HarddiskVolumeShadowCopy133
C:

The locale specific resource for the desired message is not present

Any help would be appreciated, the vendor of this POS server doesn't seem to have much insight and I'm left to try to resolve this myself it feels.

Dave

Hi

I have recently added 2 SAS HDD on my server and extend the array and volume to the logical disk. But somehow when it not showing the correct volume size as what the array is showing.

Please help.

On windows server 2012 R2 am able to create NFS share.

But when i look at the version i could see Mounted version 3 where i would like to use version 4.

can somebody help me to configure the NFS v4 on the windows server 2012 r2

We're having an issue where every other day the system state fails. We use a 3rd party piece of software that uses WSB for the system state. We get the following in the eevnt logs:

Faulting application name: wbengine.exe, version: 6.1.7601.17514, time stamp: 0x4ce79951
Faulting module name: ntdll.dll, version: 6.1.7601.18229, time stamp: 0x51fb164a
Exception code: 0xc0000005
Fault offset: 0x0000000000055384
Faulting process id: 0x3560
Faulting application start time: 0x01d01197a2bdc7a1
Faulting application path: C:\Windows\system32\wbengine.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: d6f0610d-7d8f-11e4-a8f7-5cf3fc557333

and the following when running vssadmin list writers:

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: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {7655da00-923b-441b-bc40-d64e3d44aaa9}
   State: [1] Stable
   Last error: No error

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {0e9c9681-5e67-4748-900c-b32ff7ebd072}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'FRS Writer'
   Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
   Writer Instance Id: {3e4d034d-b955-428e-952b-0581f8e05203}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {3ee8ab83-468c-4cfe-8613-6946976820fb}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'FSRM Writer'
   Writer Id: {12ce4370-5bb7-4c58-a76a-e5d5097e3674}
   Writer Instance Id: {2975a331-2068-4a6e-a16f-4635f5ce2856}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {43188986-6573-45a8-b871-4be3d189a45f}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {a9632f02-31e3-424c-8c87-69395dbf04e2}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {180f4d03-93aa-4947-b874-c2d0d7546ca0}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {231ceb2e-3b8c-40f1-8d02-22a4f263802d}
   State: [1] Stable
   Last error: No error

Writer name: 'TS Gateway Writer'
   Writer Id: {368753ec-572e-4fc7-b4b9-ccd9bdc624cb}
   Writer Instance Id: {60237974-e116-454e-b29c-6ffeffd1bd9d}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {440c5208-9d3a-4c84-884c-f9a3d8ad2c1e}
   State: [1] Stable
   Last error: No error

Writer name: 'NPS VSS Writer'
   Writer Id: {35e81631-13e1-48db-97fc-d5bc721bb18a}
   Writer Instance Id: {d6ae39a4-2c8b-4e48-9f79-12247b9fac5b}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'Dhcp Jet Writer'
   Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
   Writer Instance Id: {c616d312-5e21-47df-9e59-100cf6ac6f0e}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {8f945f3b-d50b-47b8-9085-1416d0b094e1}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {50c005a1-35e8-4bc1-a0c1-1bcdc9351322}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'MSSearch Service Writer'
   Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
   Writer Instance Id: {2bcebf65-9243-4ccd-bae2-6ae12efd9a51}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'Certificate Authority'
   Writer Id: {6f5b15b5-da24-4d88-b737-63063e3a1f86}
   Writer Instance Id: {4101713c-f207-431f-be52-1171f1227c0b}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'NTDS'
   Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
   Writer Instance Id: {aa053355-2571-4e37-ba1d-501127ab2846}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'Microsoft Exchange Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {7645b18a-8aa4-49d3-abd1-5d7debd4b3f3}
   State: [1] Stable
   Last error: No error

as i said - this happens every other day, the 3rd party software provider say this is a microsoft issue but this doesnt happen when running a system state directly from WSB

We recently implement a new Windows 2012 R2 domain controller but have been unable to take a system state backup using Windows Backup.  We get the following error?

There was a failure in updating the backup for deleted items.  Error code 0x8078014D

We have other Windows 2012 R2 domain controllers that we can backup the system state on using Windows Backup without any issues.

I need to perform a bare metal recovery, and restore the backup from "network location". I am using Server 2012R2 for Hyper-V host, and the VM is a Generation 2 VM. I am booting to Windows Server 2012R2 with Update Media, but I can't get any network Connection to the windows Setup. Suggestions?

Hello!

I have HP ProLiant DL320e Gen8 v2 Server and Windows Server 2012 R2. 
Currently I have Raid 1 configured with HP's Dynamic Smart array.

I need more free space to server. Currently there is 2x 1TB hdd's and new ones are 3TB.

I think that I have to:

1. backup current system. (with what?)
2. Remove current HDD's
3. Insert new HDD's
4. Create a new Raid 1 for new HDD's 
5. Restore from backup.

When I try to make backup with Windows Server Backup, I get an error: "Backup of volume C: has failed. The drive cannot find the sector requested.

Any tips for how to do this? Any help would be greatly appreciated.