A fatal error with Windows Server Backup

Hey,
I'm trying to backup my Windows Server 2008 R2 (physical server). Windows Server Backup tool crashes when I start to start it. It gives me error "A fatal error occurred during a Windows Server Backup snap-in (Wbadmin.msc) operation. Error details: The
Windows Server Backup service has stopped.
Errors I get to event viewer:
ASR Warning: Failed to collect disk information for ASR Backup. Reason: Unable to obtain disk information for device 14 (Win32 error code 0x1).
ASR Warning: Failed to collect disk information for ASR Backup. Reason: Unable to obtain disk information for device 10 (Win32 error code 0x1).
ASR Warning: Failed to collect disk information for ASR Backup. Reason: Unable to obtain disk information for device 3 (Win32 error code 0x1).
ASR Warning: Failed to collect disk information for ASR Backup. Reason: Unable to obtain disk information for device 1 (Win32 error code 0x1).
The following process dump file was generated:
C:\Program Files\DebugDiag\Logs\Crash rule for all instances of wbengine.exe\wbengine__PID__9716__Date__07_04_2014__Time_03_08_24PM__911__First chance exception 0XE06D7363.dmp
These devices (disks) that are showing in warnings arent initialized from Disk Management. If I open Disk Management, it always pops up prompt to initialize disks. I havent initialized these disks cause I already have them in use, but Windows regonizes those
disks twice cause I'm using multipath. I shouldnt initialize one physical disk twice.
I think seeing these disks twice is crashing my Windows Server Backup. Is there a way to disable specific disks for Windows Server Backup? Can I disable those disks somehow, so Windows Server Backup wouldnt see those disks twice? Or can I somehow tell Windows
that its seeing my disks twice, and there is actually only one disk instead of two.
Greetings,
Niko Turunen
Finland

Hi,
How did you configure the disks by using multipath? The ASR component is a system-critical component that is reported by the ASR writer. Every fixed disk on the computer is exposed as a component in ASR. During backup, the requester should include all fixed
disks.
For more detailed information, please refer to the articles below:
Using VSS Automated System Recovery for Disaster Recovery
http://technet.microsoft.com/en-ca/aa384630(v=vs.80).aspx
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.

Similar Messages

Backup Problem with Windows Server Backup

Hello,
we have problems with Windows Server Backup Feature.
Our system is a Windows Server 2008 Standard. On the computer runs a SQL Server 2005.
Since several days no backup can be carried out. We get the error message:
- Error during a Volume Shadow Copy service operation. Detailed error: Failed to process the volume shadow copy: "0x800423F0".
- Errors in the event log: For the started backup an error occured. The volume shadow copy operation was not successful. Error code: "2155348129". Run the backup again after the problem was fixed.
We have already tried to restart the services, uninstalled the Windows Server Backup Feature and reinstalled it, also we rebootet the server several times. Unfortunately, so far without success.
What else can we do respectively where could be the problem?
Kind regards
Sven Otto
KRK ComputerSysteme GmbH (Germany)

Hi Sven,
Please check if there a system partition that is created on the server. If so, assign a drive letter on the partition to check the results.
For more detailed information, please refer to the article below:
Volume Shadow Copy Error 0x800423f0 - writer error: inconsistent snapshot
http://kb.backupassist.com/articles.php?aid=2995
Please Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
Best 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.

Fatal Errors with Windows Integrated Server

Every once in a while - 3 or 4 times in the last 3 hours I get a fatal error on the server. The last part of the server log looks like this:
08/03/13 14:27:59 WARNING: ExecutorService.inform Unknown event state3 Ignored
08/03/13 14:27:59 WARNING: ExecutorService.inform Unknown event state4 Ignored
08/03/13 14:28:12 WARNING: ExecutorService.inform Unknown event state3 Ignored
08/03/13 14:28:12 WARNING: ExecutorService.inform Unknown event state4 Ignored
08/03/13 14:28:13 WARNING: ExecutorService.inform Unknown event state3 Ignored
08/03/13 14:28:13 WARNING: ExecutorService.inform Unknown event state4 Ignored
08/03/13 14:28:15 BASE URL IS: /SOAConsole/faces
08/03/13 14:28:16 BASE URL IS: /SOAConsole/faces
# An unexpected error has been detected by HotSpot Virtual Machine:
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x6d80f244, pid=5376, tid=2388
# Java VM: Java HotSpot(TM) Client VM (1.5.0_11-b03 mixed mode)
# Problematic frame:
# V [jvm.dll+0xcf244]
# An error report file with more information is saved as hs_err_pid5376.log
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
Process exited.
I'll be happy to include the error report file if that is helpful

I'm sorry I have not been able to determine what caused the errors. In many cases I didn't actually notice it until I went to try to use the console or worklist and found the server was down. I then looked at the log to find the error. There was at least once when I was just navigating the console and it died, but I don't ermember exactly where. Nothing I hadn't done before. I'll try to pay more attention.
I just restart the server to recover.

Error using Window Server Backup on 2012R2 Hyper-V to network share

Hi
I have a Windows 2012 R2 Hyper-V server. It runs a Windows 2012 R2 VM (called
server-1).
I want to backup the VM to a network location (\\network-1\server-1_backup$). To do this, I installed Windows Server Backup from the command line and configured a backup to look like this:
C:\Users\admin>wbadmin enable backup
wbadmin 1.0 - Backup command-line tool
(C) Copyright 2013 Microsoft Corporation. All rights reserved.
The scheduled backup settings:
Bare metal recovery : Not Included
System state backup: Not Included
Volumes in backup: (null)
Components in backup: HyperV\server-1
Files excluded: (null)
Advanced settings: VSS Backup Option (FULL)
Location to store backup: \\network-1\server-1_backup$\
Times of day to run backup: 04:00
But when I run this backup manually, I get the following error:
C:\Users\admin>wbadmin start backup
wbadmin 1.0 - Backup command-line tool
(C) Copyright 2013 Microsoft Corporation. All rights reserved.
Do you want to create a backup using the same configuration that you use for
scheduled backups?
[Y] Yes [N] No y
The backup operation to Scheduled backup target is starting.
Creating a shadow copy of the volumes specified for backup...
Summary of the backup operation:
The backup operation stopped before completing.
The backup operation stopped before completing.
Detailed error: A component critical volume failed to snapshot.
Log of files successfully backed up:
C:\Windows\Logs\WindowsServerBackup\Backup-23-02-2015_08-49-55.log
Log of files for which backup failed:
C:\Windows\Logs\WindowsServerBackup\Backup_Error-23-02-2015_08-49-55.log
ERROR - The shared restore point operation failed with error (0x8100010c)
No valid component or volume to snapshot.
A component critical volume failed to snapshot.
The log file then looks like this:
Writer Failures
Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
Instance Id: {3976D373-854E-4527-B85D-7B61924C8597}
Writer Name: Microsoft Hyper-V VSS Writer
Writer State: 0
Failure Result: 81000112
Application Result: 0
Application Message: (null)
   Component: 1DAF1C56-0635-4043-A933-E97A62EBC139
   Logical Path:
   Component Result: 8100010D
   Component Message: Component reports path on network share which cannot be snapshotted. (0x8100010D)
   Component: 30144C93-56A2-4259-B276-86D59AC767E9
Application backup
Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
   Component: 1DAF1C56-0635-4043-A933-E97A62EBC139
   Caption     : Offline\server-1
   Logical Path:
   Error           : 8078001D
   Error Message   : The operation ended before completion.
The odd thing is that if I set this up from a Windows 2012 Server using the GUI to exactly the same network destination, the backup works no problem. It just doesn't work when using Server 2012 R2 Hyper-V configured through a command line.
Any help appreciated,
Andrew

Hi Andrew,
I tested this in my lab server 2012R2 , but there's no error .
I would suggest you to create a new share folder on other server then check if the issue persists .
Writer Name: Microsoft Hyper-V VSS Writer
Writer State: 0
Failure Result: 81000112
Application Result: 0
Application Message: (null)
   Component: 1DAF1C56-0635-4043-A933-E97A62EBC139
   Logical Path:
   Component Result: 8100010D
   Component Message: Component reports path on network share which cannot be snapshotted. (0x8100010D)"
According to this error , please check if the VM's resource (such as VHD file) was restored on network share .
I also searched the error "ERROR - The shared restore point operation failed with error (0x8100010c)" , but I can not find it within following article :
http://blogs.technet.com/b/filecab/archive/2009/09/16/diagnosing-failures-in-windows-server-backup-part-1-vss-spp-errors.aspx
Any further information please feel free to let us know .
Best Regards,
Elton Ji
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] .

Backing up Exchange Server 2013 CU3 with Windows Server Backup Program

Looking at configuring Windows Server Backup Program to backup Exchange Server 2013 CU3 which is a member a DAG Group using a specific Backup Domain Account.
From my understanding from the following technet Article" Using Windows Server Backup to Backup and Restore Exchange Data" at http://technet.microsoft.com/en-us/library/dd876851(v=exchg.150).aspx I cannot use wbadmin.exe has it uses an older
unsupported version of Powershell.
My question is what are the minimum AD rights required for an AD account needed to be able to backup/restore Exchange Datastore using Windows Server Backup Program in Windows Server 2012?
Thanks,
NIck

Hi Sathish,
After looking at your response, it all make sense except when I look at what exchange right assigned via RBAC. I understand that the backup service account will require access to the exchange databases
to be able to backing and restoring them. After looking at the different roles
I'm wondering if I require to assign both the Databases roles for Backing up the databases and the Disaster Recovery Role as well to be able to restore the databases has well as having a mailbox on the exchange
server for the backup service account?
Below is explanation of the roles via the ECP
Database Role
This role enables administrators to create, manage, mount and dismount mailbox and public folder databases on individual servers.
Disaster Recovery
This role enables administrators to restore mailboxes and database availability groups in an organization.
Thanks,
Nick

Problem: VSS error with 'SQL Server Backup to Windows Azure Tool' installed

When 'SQL Server Backup to Windows Azure Tool' is installed, shadow copies cannot be enable and backups fail. When attempting to enable shadow copies, we get a "volsnap" error: "The shadow copies of volume X were aborted because
of a failed free space computation". After uninstalling the "Tool", VSS works. Reinstalling "Tool" causes the problem to return.
While the error suggests a space issue, there is plenty of space on the server's two volumes. Additionally, another 100GB volume was added and VSS storage was allocated to it; still received the error.
Issue seems to point to 'SQL Server Backup to Windows Azure Tool'.
Environment: Hyper-V guest: "Windows Server 2012 R2 Standard" with "SQL Server 2008 R2 Standard". Using "Azure Storage" for SQL backups.
Suggestions?

Hello,
Yes, we have a confirmed interference between the tool and the VSS Framework. This was identified very recently and is under investigation by the product group. Since the issue is within the filter driver shipped by the tool, that unfortunately means that
you currently need to choose between the tool and a working VSS Framework. If the latter is more important, then uninstall the tool (that will require a restart).
We apolologize for the inconvenience. I'm going to try to get the home page of the tool updated to avoid other situations like yours. Hopefully we should see a new version of the tool soon.
As a side note, recent versions of SQL Server can directly use Azure Storage as backup target, see
http://msdn.microsoft.com/en-us/library/jj919148(v=sql.110).aspx.
Regards,
Guillaume Fourrat - Microsoft France

Windows Server Backup - 0x80042407, seriously?

I installed server 2008 on a test server with 4x250GB drives in a RAID5 array.
Windows was installed on a 60GB partition, the rest of the array was left as free space.
After installing updates and drivers, I decided that I wanted a RAID10 array.
This would give me a chance to test the restore functionality of Windows Server Backup.
I did a full backup with Windows Server Backup to a network location.
After reconfiguring the RAID array I started the recovery process.
Here is the issue. right when the restore should start, I get an error....
The Windows Complete PC Restore operation failed.
Error details: The disk that is set as active in BIOS is too small to recover the original system disk. Replace the disk with a larger one and retry the restore operation. (0x80042407)
I've tried creating partitions of all sizes and leaving the disk blank, same error.
I even set the disk as the first boot device in BIOS.
I've read elsewhere that the disk must be the same size or larger. That just seems like a bad April fools joke to me.
Can anyone give me some insight on this issue?

Hello Jason,
Thank you for your reply.
For your further concern, this same or bigger disk size requirement is by design for Windows Server 2008 and Windows Vista. As a suggestion, we recommend you use a bigger disk for Bare Metal Restore.
Currently we cannot edit the backup size. However, to fulfill your demand, there is a possible given workaround to restore the backup to smaller disk size.
Workaround: To recover the System manually using Volume recovery
By using this workaround, at minimum the OS critical partitions should be of the same size for the volume recovery.
To recovery the System manually from Windows Recovery Environment (when BMR – Complete PC Restore is not working), user has to recover all the partitions individually and then set the BCD boot entries.
Please follow the below mentioned steps:
1)    Get the backup version from the backup target.
2)    From version, get the size of partitions at the time of backup.
3)    Recreate the partitions manually with same or more size.
4)    Perform volume recovery of Individual volumes.
5)    Set the Active bit for System volume.
6)    Fix the Boot entries.
Please replace anything marked under <> with actual values. The yellow marked entries are for sample only. We have to pick the actual values from his system. Also assuming the Boot disk is disk 0 in this case.
Open Command prompt:
1)    Do wbadmin get versions –backuptarget:<X:>.
a.    Select the version id from. E.g. Version identifier: 02/11/2009-09:14
Note: If the backup target is network share, then run “start /w wpeinit” to enable networking.
2)    Do wbadmin get items –version:<versioned> -backuptarget:<X:>
a.    This will give the list of volumes that were backed up and their sizes.
3)    Using Diskpart, recreate your volumes of the same or more size. Assume that the Boot disk is Disk 0 and is empty. Disk 0 is the boot disk and is the first disk in BIOS boot order.
If the required partitions are already present then skip the steps below.
a.    Diskpart.exe
b.    List disk
c.    Select disk 0.
d.    Create par primary size=<size>
e.    Format fs=ntfs quick label=”OS”               (Format the OS partition with NTFS)
f.     Assign letter=D                 (assign drive letter D: to OS volume)
g.    Do the same for all the volumes you want to recover.
h.    Detail disk
i.      It lists the newly created partitions.
4)    To recover the volumes one by one,
a.    Do wbadmin get items –version:<versionid> -backuptarget:<X:> .
b.    Select the volume id or drive letter for OS volume that was backed up.
E.g. C: corresponds to the OS volume at backup time.
c.    Wbadmin start recovery –version:<versionid> -backuptarget:<x:> -itemType:Volume –items:C: -recoverytarget:D:
d.    Do the same for all the other volumes. Make sure that minimum space requirement is met.
e.    Set the active bit of System volume from Diskpart.
f.     Diskpart.exe ->
                                          i.    Select volume D:
                                         ii.    active
5)    Reboot the OS and boot back into WinRE as OS is not yet bootable.
6)    Select Startup-Repair option to fix the BCD boot entries.
7)    Reboot and OS should be in a bootable state.
8)    If OS is still not bootable, use bcdedit.exe/bootrec.exe in WinRE to fix the BCD boot options.
I understand that it will be reasonable to edit the backup so that the bare metal restore process can accept the smaller disk size, our product team are aware of this desired functionality and will definitely keep this in mind as future product development continues.
Thanks for your understandings.
This posting is provided "AS IS" with no warranties, and confers no rights.

Using multiple drives with Windows 7 Backup

I have a customer with a new PC running Windows 7 Pro. He has 3 Seagate 1TB USB drives that he swaps out nightly for backups. Currently, backups are being done using the built-in Windows 7 Backup.
His previous PC ran XP and used the program which is pre-loaded onto Seagate drives to install onto PCs. He used this with the 3 drives and had no problems.
However, this software on the drives would not install on his Windows 7 PC because I presume it to not be compatible, even in compatibility mode.
The problem now is that each time he swaps in a different drive, the backups fail because it's a different drive and the backup software can't seem to handle multiple drives. With Windows Server Backup, you can add multiple drives so that when you swap them,
backups still run. I can't seem to do that with Windows 7 Backup.
Does anyone know how to get multiple drives to work with the built-in Windows 7 Backup?
Jonathan

In addition to the above persons' solution, you can choose a third software instead of the built-in Windows 7 Backup tool, the backup software can make up for the deficiency of the backup tool of Windows. You can search in Google, and
will find many kinds of software, Genie backup and AOMEI Backupper: http://www.backup-utility.com/ can be ok. Hope the freeware can give you suggestion.
AOMEI turned out to be the answer. It works well with multiple drives and provides an easy way the user can see if the backup succeeded or not. Thanks!
Jonathan

A fatal error occurred during a windows server backup snap-in operation;

Unable to get windows server backup to work, I believe it was running fine not too long ago.
getting the following errors in the event log;
Faulting application name: wbengine.exe, version: 6.3.9600.17415, time stamp: 0x54504543
Faulting module name: wbengine.exe, version: 6.3.9600.17415, time stamp: 0x54504543
Exception code: 0xc0000005
Fault offset: 0x000000000011e4d7
Faulting process id: 0x1a20
Faulting application start time: 0x01d01a1b546c5049
Faulting application path: C:\Windows\system32\wbengine.exe
Faulting module path: C:\Windows\system32\wbengine.exe
Report Id: 99e58796-860e-11e4-80c4-40167e73010e
Faulting package full name:
Faulting package-relative application ID:
and
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: wbengine.exe
P2: 6.3.9600.17415
P3: 54504543
P4: wbengine.exe
P5: 6.3.9600.17415
P6: 54504543
P7: c0000005
P8: 000000000011e4d7
P9:
P10:
Attached files:
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_wbengine.exe_a2f5333556c4387ec0eb41803df32b5ef88b1de_6e4602a0_1b3ef3fb
Analysis symbol:
Rechecking for solution: 0
Report Id: 8a7a7549-860e-11e4-80c4-40167e73010e
Report Status: 0
Hashed bucket:

Hi,
It seems that there is an error accessing the catalog. You could run the "wbadmin delete catalog" to delete the catalog to resolve the issue.
For more detailed information, please refer to the thread below:
Windows Server 2k8 Backup Errors
https://social.technet.microsoft.com/Forums/windowsserver/en-US/9051f767-2e25-44f9-a4cf-d49f75513da6/windows-server-2k8-backup-errors?forum=winservergen
Please note: The command "wbadmin delete catalog" will remove all backups existed on your server.
Best Regards,
Mandy
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Server 2008 R2 Windows Server Backup. "Error in backup of Hyper-V.vhd during read: Error [0x80070001] Incorrect function.

Hello,
We are currently using Windows Server Backup to backup three Hyper-V guests running on a Windows 2008 R2 host. Two guests are running Server 2008 R2 and one is running Windows 7. I have the backups going to a dedicated external disk drive.
WSB backs up the two 2008 R2 Hyper-V guests just fine. However, when attempting to backup the Windows 7 Hyper-V guest, I receive the following error:
Error in backup of <Windows 7.vhd> during read: Error [0x80070001] Incorrect function.
I ran a "vssadmin list writers" and all the VSS writers showed "Stable" with no errors. I have plenty of space on the external drive as well. I've read this article:
https://support.microsoft.com/kb/973455?wa=wsignin1.0#workaroundissue12 except that doesn't seem to be what I'm experiencing here.
Anyone have any suggestions?

Hi,
As the other 2 guests could be backed up correctly, the issue should not be the Windows Server Backup feature.
First please refer to this article:
Backing Up and Restoring Virtual Machines
http://msdn.microsoft.com/en-us/library/dd405549(v=vs.85).aspx
Please check if all following requirements are met. Specifically please check if Integration Service is installed.
Backup (volume snapshot) Integration Service is installed and running in the child VM. The service name is "Hyper-V Volume Shadow Copy Requestor".
Windows 2000: Backup Integration Service is not supported.
The child VM must be in the running state.
The Snapshot File Location for the VM is set to be the same volume in the host operating system as the VHD files for the VM.
All volumes in the child VM are basic disks and there are no dynamic disks.
All disks in the child VM must use a file system that supports snapshots (for example, NTFS).
If you have any feedback on our support, please send to [email protected]

[Forum FAQ] Cannot perform a backup schedule via Windows Server Backup and receive "The system cannot find the path specified." Error

Symptom One
You attempt to
schedule a backup every day via Windows Server Backup on Windows Server 2008 R2. At the beginning, the backup works without issue. But after a few days it failed and you receive the error “Windows Server Backup:
The system cannot find the path specified.”
Cause
The issue may occur if there is
no shadow copy storage space available on the backup volume.
Verify
You can use the List ShadowStorage command to check if you have enough storage space to store the newly created shadow copy. If you've reviewed the size of the backup snapshot and discovered
that there is no allocated space for the storage association, you need to resize shadowstorage.
Solution
You could run the command below to create shadow copy storage space on the backup volume:
vssadmin resize
shadowstorage /for=<ForVolumeSpec> /on=<OnVolumeSpec> [/maxsize=<MaxSizeSpec>]
More Information
Vssadmin resize shadowstorage
http://technet.microsoft.com/en-us/library/cc788050.aspx
Symptom Two
When you add
another external hard drive to backup schedule via Windows Server Backup on Windows Server 2012, it fails and you receive the error “The System cannot find the path specified.”
Cause
The issue is due to the
Original Destination Disk was not attached to the server.
Verify
You could check the disk status in Disk Management to see if the Original Destination Disk is offline or removed.
Solution
You need to attach
Original Destination Disk to the Server then choose another external hard drive as backup target. After that, you could remove the Original Destination Disk.
Workaround
To work around this issue, please use the WBADMIN command line tool to add disk.
WBADMIN ENABLE BACKUP -addtarget :{ DiskID}
The AddTarget parameter takes disk ID as parameter. It can be retrieved by running "WBADMIN GET DISKS" command.
Example:
WBADMIN ENABLE BACKUP
-addtarget :{ aa123d14-bba0-1dd9-0d93-80aaaa6bbb63}
More Information
Wbadmin enable backup
http://technet.microsoft.com/en-us/library/cc742130.aspx
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

good

Restore bkf Backup Files on Tape with Windows Server 2008 R2

We have to migrate an application from a legacy server (OS Windows Server 2003) to a new server (OS Windows Server 2008 R2).
Due to legal obligations we have to keep backups for 10 years. Until now NTBACKUP was used to store the data on tape.
We must be able to restore data from tapes of the last 10 years for audit purposes.
We installed Update für Windows Server 2008 R2 x64 Edition (KB974674) containing NTBackup-RestoreUtility on the new server.
It seems that this tool is not able to restore from tapes.
How can we fullfil the legal requirements to restore backuped data from tape on Windows Server 8 R2 (and in future with Windows Server 2012 R2)?

Hi,
This is Exchange server forum. Actually, we have a dedicated support team regarding the Microsoft Windows Server. I recommend you ask your question on our Windows Server forum which is staffed by more experts specializing in this kind of problems. Thanks
for your understanding.
For your convenience:
http://social.technet.microsoft.com/Forums/windowsserver/en-US/home?category=windowsserver
Hope it helps.
If you have any problem with Exchange server, welcome to our Exchange server forum.
Best regards,
Amy Wang
TechNet Community Support

Windows Server Backup - wbengine.exe Crashing

Hi,
When running either a scheduled back or a once off backup, I receive the following error around 30 seconds into the backup:
"The Windows Server Backup service has stopped"
"A fatal error occurred during a Windows Server Backup snap-in (Wbadmin.msc) operation. Error details: The Windows server Backup service has stopped"
In event viewer the following two events were logged:
Faulting application name: wbengine.exe, version: 6.1.7601.17514, time stamp: 0x4ce79951
Faulting module name: ntdll.dll, version: 6.1.7601.18247, time stamp: 0x521eaf24
Exception code: 0xc0000374
Fault offset: 0x00000000000c4102
Faulting process id: 0x13e8
Faulting application start time: 0x01cfa9f0936b235a
Faulting application path: C:\Windows\system32\wbengine.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: e99a55c8-15e4-11e4-9ab5-a01d48c77640
The Block Level Backup Engine Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service.
I have tired restarting the Block Level Backup Engine Service service, deleting the backup catalogue, removing and re adding Window Server Backup feature. None of these fixed the problem.
I used Debug Diagnostic Tool v2.0 and capturing all instances of wbengine.exe process:
Loading control script C:\Program Files\DebugDiag\scripts\CrashRule_Process_wbengine.exe.vbs
DumpPath set to C:\Users\administrator\Desktop\wbengineLogs
[8/20/2014 9:23:48 AM] Process created. BaseModule - C:\Windows\system32\wbengine.exe. BaseThread System ID - System ID: 7940
[8/20/2014 9:23:48 AM] C:\Windows\SYSTEM32\ntdll.dll loaded at 0x77780000
[8/20/2014 9:23:48 AM] Thread created. New thread system id - System ID: 1912
[8/20/2014 9:23:48 AM] Thread created. New thread system id - System ID: 7756
[8/20/2014 9:23:48 AM] Thread created. New thread system id - System ID: 4920
[8/20/2014 9:23:48 AM] Thread created. New thread system id - System ID: 6964
[8/20/2014 9:23:48 AM] Thread created. New thread system id - System ID: 6100
[8/20/2014 9:23:48 AM] Thread created. New thread system id - System ID: 6524
[8/20/2014 9:23:48 AM] Thread created. New thread system id - System ID: 6824
[8/20/2014 9:23:48 AM] C:\Windows\system32\kernel32.dll loaded at 0x77560000
[8/20/2014 9:23:48 AM] C:\Windows\system32\KERNELBASE.dll loaded at 0xfd5e0000
[8/20/2014 9:23:48 AM] C:\Windows\system32\ADVAPI32.dll loaded at 0xfe030000
[8/20/2014 9:23:48 AM] C:\Windows\system32\msvcrt.dll loaded at 0xff5d0000
[8/20/2014 9:23:48 AM] C:\Windows\SYSTEM32\sechost.dll loaded at 0xff530000
[8/20/2014 9:23:48 AM] C:\Windows\system32\RPCRT4.dll loaded at 0xfeed0000
[8/20/2014 9:23:48 AM] C:\Windows\system32\USER32.dll loaded at 0x77680000
[8/20/2014 9:23:48 AM] C:\Windows\system32\GDI32.dll loaded at 0xffa20000
[8/20/2014 9:23:48 AM] C:\Windows\system32\LPK.dll loaded at 0xff6c0000
[8/20/2014 9:23:48 AM] C:\Windows\system32\USP10.dll loaded at 0xff130000
[8/20/2014 9:23:48 AM] C:\Windows\system32\ole32.dll loaded at 0xff320000
[8/20/2014 9:23:48 AM] C:\Windows\system32\OLEAUT32.dll loaded at 0xfdf40000
[8/20/2014 9:23:48 AM] C:\Windows\system32\VSSAPI.DLL loaded at 0xfc1e0000
[8/20/2014 9:23:48 AM] C:\Windows\system32\ATL.DLL loaded at 0xfc1c0000
[8/20/2014 9:23:48 AM] C:\Windows\system32\VssTrace.DLL loaded at 0xfc1a0000
[8/20/2014 9:23:48 AM] C:\Windows\system32\SETUPAPI.dll loaded at 0xff6d0000
[8/20/2014 9:23:48 AM] C:\Windows\system32\CFGMGR32.dll loaded at 0xfd910000
[8/20/2014 9:23:48 AM] C:\Windows\system32\DEVOBJ.dll loaded at 0xfd8f0000
[8/20/2014 9:23:48 AM] C:\Windows\system32\NETAPI32.dll loaded at 0xfa190000
[8/20/2014 9:23:48 AM] C:\Windows\system32\netutils.dll loaded at 0xfc9f0000
[8/20/2014 9:23:48 AM] C:\Windows\system32\srvcli.dll loaded at 0xfd130000
[8/20/2014 9:23:48 AM] C:\Windows\system32\wkscli.dll loaded at 0xfa170000
[8/20/2014 9:23:48 AM] C:\Windows\system32\XmlLite.dll loaded at 0xfa9e0000
[8/20/2014 9:23:48 AM] C:\Windows\system32\bcrypt.dll loaded at 0xfcf10000
[8/20/2014 9:23:48 AM] C:\Windows\system32\VirtDisk.dll loaded at 0xf5740000
[8/20/2014 9:23:48 AM] C:\Windows\system32\FLTLIB.DLL loaded at 0xf8de0000
[8/20/2014 9:23:48 AM] C:\Windows\system32\CLUSAPI.dll loaded at 0xf9c60000
[8/20/2014 9:23:48 AM] C:\Windows\system32\cryptdll.dll loaded at 0xfd040000
[8/20/2014 9:23:48 AM] C:\Windows\system32\IMM32.DLL loaded at 0xfe110000
[8/20/2014 9:23:48 AM] C:\Windows\system32\MSCTF.dll loaded at 0xff020000
[8/20/2014 9:23:48 AM] C:\Windows\system32\CRYPTBASE.dll loaded at 0xfd420000
[8/20/2014 9:23:48 AM] C:\Windows\system32\bcryptprimitives.dll loaded at 0xfca00000
[8/20/2014 9:23:48 AM] C:\Windows\system32\cscapi.dll loaded at 0xf9bd0000
[8/20/2014 9:23:48 AM] C:\Windows\system32\CLBCatQ.DLL loaded at 0xfdc70000
[8/20/2014 9:23:48 AM] C:\Windows\system32\CRYPTSP.dll loaded at 0xfcdc0000
[8/20/2014 9:23:48 AM] C:\Windows\system32\rsaenh.dll loaded at 0xfcac0000
[8/20/2014 9:23:48 AM] C:\Windows\system32\RpcRtRemote.dll loaded at 0xfd510000
[8/20/2014 9:23:48 AM] C:\Windows\system32\blb_ps.dll loaded at 0xf7520000
[8/20/2014 9:23:48 AM] C:\Windows\System32\vds_ps.dll loaded at 0xf8310000
[8/20/2014 9:23:48 AM] C:\Windows\system32\WINTRUST.dll loaded at 0xfd720000
[8/20/2014 9:23:48 AM] C:\Windows\system32\CRYPT32.dll loaded at 0xfd760000
[8/20/2014 9:23:48 AM] C:\Windows\system32\MSASN1.dll loaded at 0xfd5d0000
[8/20/2014 9:23:48 AM] C:\Windows\system32\vss_ps.dll loaded at 0xfa2f0000
[8/20/2014 9:23:48 AM] C:\Windows\system32\taskschd.dll loaded at 0xf4b20000
[8/20/2014 9:23:48 AM] C:\Windows\system32\SspiCli.dll loaded at 0xfd390000
[8/20/2014 9:23:48 AM] C:\Windows\system32\spp.dll loaded at 0xeec40000
[8/20/2014 9:23:48 AM] C:\Windows\system32\dsrole.dll loaded at 0xfb630000
[8/20/2014 9:23:48 AM] C:\Windows\System32\msxml3.dll loaded at 0xf89b0000
[8/20/2014 9:23:48 AM] C:\Windows\system32\SHLWAPI.dll loaded at 0xff200000
[8/20/2014 9:23:48 AM] C:\Windows\System32\ES.DLL loaded at 0xfb5b0000
[8/20/2014 9:23:48 AM] C:\Windows\system32\SXS.DLL loaded at 0xfd430000
[8/20/2014 9:23:48 AM] C:\Windows\system32\PROPSYS.dll loaded at 0xfad60000
[8/20/2014 9:23:48 AM] C:\Windows\system32\samcli.dll loaded at 0xfa670000
[8/20/2014 9:23:48 AM] C:\Windows\system32\SAMLIB.dll loaded at 0xfa650000
[8/20/2014 9:23:48 AM] C:\Windows\System32\msxml6.dll loaded at 0xf6ab0000
[8/20/2014 9:23:48 AM] Thread created. New thread system id - System ID: 7428
[8/20/2014 9:23:48 AM] Initializing control script
[8/20/2014 9:23:48 AM] Clearing any existing breakpoints
[8/20/2014 9:23:48 AM]
[8/20/2014 9:23:48 AM] Current Breakpoint List(BL)
[8/20/2014 9:23:49 AM] Thread exited. Exiting thread system id - System ID: 7428. Exit code - 0x00000000
[8/20/2014 9:23:54 AM] Thread created. New thread system id - System ID: 5848
[8/20/2014 9:23:55 AM] C:\Windows\system32\blbres.dll loaded at 0x73050000
[8/20/2014 9:23:55 AM] C:\Windows\system32\blbres.dll Unloaded from 0x73050000
[8/20/2014 9:23:55 AM] C:\Windows\system32\blbres.dll loaded at 0x73050000
[8/20/2014 9:23:55 AM] C:\Windows\system32\blbres.dll Unloaded from 0x73050000
[8/20/2014 9:23:55 AM] C:\Windows\system32\blbres.dll loaded at 0x73050000
[8/20/2014 9:23:55 AM] C:\Windows\system32\blbres.dll Unloaded from 0x73050000
[8/20/2014 9:23:55 AM] C:\Windows\system32\blbres.dll loaded at 0x73050000
[8/20/2014 9:23:55 AM] C:\Windows\system32\blbres.dll Unloaded from 0x73050000
[8/20/2014 9:23:55 AM] C:\Windows\system32\blbres.dll loaded at 0x73050000
[8/20/2014 9:23:55 AM] C:\Windows\system32\blbres.dll Unloaded from 0x73050000
[8/20/2014 9:23:55 AM] C:\Windows\system32\blbres.dll loaded at 0x73050000
[8/20/2014 9:23:55 AM] C:\Windows\system32\blbres.dll Unloaded from 0x73050000
[8/20/2014 9:23:55 AM] Thread created. New thread system id - System ID: 7188
[8/20/2014 9:24:02 AM] Thread created. New thread system id - System ID: 6160
[8/20/2014 9:24:02 AM] Thread created. New thread system id - System ID: 7640
[8/20/2014 9:24:02 AM] Thread created. New thread system id - System ID: 8148
[8/20/2014 9:24:02 AM] Thread created. New thread system id - System ID: 5348
[8/20/2014 9:24:02 AM] Thread created. New thread system id - System ID: 2964
[8/20/2014 9:24:02 AM] Thread created. New thread system id - System ID: 5320
[8/20/2014 9:24:02 AM] Thread created. New thread system id - System ID: 4164
[8/20/2014 9:24:02 AM] Thread created. New thread system id - System ID: 7916
[8/20/2014 9:24:02 AM] Thread created. New thread system id - System ID: 6244
[8/20/2014 9:24:02 AM] Thread created. New thread system id - System ID: 7908
[8/20/2014 9:24:02 AM] Thread created. New thread system id - System ID: 6200
[8/20/2014 9:24:02 AM] Thread created. New thread system id - System ID: 5028
[8/20/2014 9:24:02 AM] Thread created. New thread system id - System ID: 7804
[8/20/2014 9:24:03 AM] First chance exception - 0XE06D7363 caused by thread with System ID: 7640. DetailID = 1
[8/20/2014 9:24:03 AM] Thread exited. Exiting thread system id - System ID: 7640. Exit code - 0x00000000
[8/20/2014 9:24:07 AM] Thread exited. Exiting thread system id - System ID: 6160. Exit code - 0x00000000
[8/20/2014 9:24:08 AM] Thread created. New thread system id - System ID: 1108
[8/20/2014 9:24:08 AM] Thread created. New thread system id - System ID: 992
[8/20/2014 9:24:08 AM] Thread created. New thread system id - System ID: 7784
[8/20/2014 9:24:08 AM] Thread created. New thread system id - System ID: 4432
[8/20/2014 9:24:08 AM] Thread created. New thread system id - System ID: 5304
[8/20/2014 9:24:09 AM] First chance exception - 0XE06D7363 caused by thread with System ID: 7784. DetailID = 2
[8/20/2014 9:24:09 AM] Thread exited. Exiting thread system id - System ID: 7784. Exit code - 0x00000000
[8/20/2014 9:24:13 AM] Thread created. New thread system id - System ID: 2780
[8/20/2014 9:24:13 AM] Thread created. New thread system id - System ID: 8012
[8/20/2014 9:24:13 AM] Thread created. New thread system id - System ID: 7552
[8/20/2014 9:24:13 AM] Thread created. New thread system id - System ID: 6812
[8/20/2014 9:24:13 AM] Thread created. New thread system id - System ID: 5368
[8/20/2014 9:24:13 AM] Thread created. New thread system id - System ID: 1388
[8/20/2014 9:24:13 AM] Thread exited. Exiting thread system id - System ID: 2780. Exit code - 0x00000000
[8/20/2014 9:24:13 AM] Thread created. New thread system id - System ID: 7404
[8/20/2014 9:24:14 AM] Thread exited. Exiting thread system id - System ID: 7404. Exit code - 0x00000000
[8/20/2014 9:24:14 AM] Thread created. New thread system id - System ID: 2284
[8/20/2014 9:24:47 AM] Thread exited. Exiting thread system id - System ID: 6524. Exit code - 0x00000000
[8/20/2014 9:25:12 AM] Thread exited. Exiting thread system id - System ID: 2284. Exit code - 0x00000000
[8/20/2014 9:25:12 AM] Thread created. New thread system id - System ID: 6188
[8/20/2014 9:25:12 AM] Thread exited. Exiting thread system id - System ID: 6188. Exit code - 0x00000000
[8/20/2014 9:25:12 AM] Thread created. New thread system id - System ID: 7120
[8/20/2014 9:25:12 AM] Thread exited. Exiting thread system id - System ID: 7120. Exit code - 0x00000000
[8/20/2014 9:25:13 AM] Thread created. New thread system id - System ID: 7428
[8/20/2014 9:25:20 AM] Thread exited. Exiting thread system id - System ID: 7428. Exit code - 0x00000000
[8/20/2014 9:25:20 AM] Thread created. New thread system id - System ID: 1280
[8/20/2014 9:25:21 AM] Thread exited. Exiting thread system id - System ID: 7552. Exit code - 0x00000000
[8/20/2014 9:25:21 AM] Thread exited. Exiting thread system id - System ID: 5368. Exit code - 0x00000000
[8/20/2014 9:25:21 AM] Thread exited. Exiting thread system id - System ID: 1280. Exit code - 0x00000000
[8/20/2014 9:25:21 AM] Thread created. New thread system id - System ID: 8108
[8/20/2014 9:25:21 AM] Thread exited. Exiting thread system id - System ID: 8108. Exit code - 0x00000000
[8/20/2014 9:25:21 AM] C:\Windows\system32\blbsrv.dll loaded at 0xe6240000
[8/20/2014 9:25:25 AM] First chance exception - 0X80000003 caused by thread with System ID: 992. DetailID = 3
[8/20/2014 9:25:25 AM] First chance exception - 0XC0000374 caused by thread with System ID: 992. DetailID = 4
[8/20/2014 9:25:25 AM] Second chance exception - 0XC0000374 caused by thread with System ID: 992
[8/20/2014 9:25:25 AM] Thread exited. Exiting thread system id - System ID: 5028. Exit code - 0xffffffff
[8/20/2014 9:25:25 AM] Thread exited. Exiting thread system id - System ID: 4432. Exit code - 0xffffffff
[8/20/2014 9:25:25 AM] Thread exited. Exiting thread system id - System ID: 992. Exit code - 0xffffffff
[8/20/2014 9:25:25 AM] Thread exited. Exiting thread system id - System ID: 7804. Exit code - 0xffffffff
[8/20/2014 9:25:25 AM] Thread exited. Exiting thread system id - System ID: 7908. Exit code - 0xffffffff
[8/20/2014 9:25:25 AM] Thread exited. Exiting thread system id - System ID: 4164. Exit code - 0xffffffff
[8/20/2014 9:25:25 AM] Thread exited. Exiting thread system id - System ID: 2964. Exit code - 0xffffffff
[8/20/2014 9:25:25 AM] Thread exited. Exiting thread system id - System ID: 8148. Exit code - 0xffffffff
[8/20/2014 9:25:25 AM] Thread exited. Exiting thread system id - System ID: 5848. Exit code - 0xffffffff
[8/20/2014 9:25:25 AM] Thread exited. Exiting thread system id - System ID: 6824. Exit code - 0xffffffff
[8/20/2014 9:25:25 AM] Thread exited. Exiting thread system id - System ID: 6100. Exit code - 0xffffffff
[8/20/2014 9:25:25 AM] Thread exited. Exiting thread system id - System ID: 6964. Exit code - 0xffffffff
[8/20/2014 9:25:25 AM] Thread exited. Exiting thread system id - System ID: 7756. Exit code - 0xffffffff
[8/20/2014 9:25:25 AM] Thread exited. Exiting thread system id - System ID: 7940. Exit code - 0xffffffff
[8/20/2014 9:25:25 AM] Thread exited. Exiting thread system id - System ID: 6812. Exit code - 0xffffffff
[8/20/2014 9:25:25 AM] Thread exited. Exiting thread system id - System ID: 8012. Exit code - 0xffffffff
[8/20/2014 9:25:25 AM] Thread exited. Exiting thread system id - System ID: 5304. Exit code - 0xffffffff
[8/20/2014 9:25:25 AM] Thread exited. Exiting thread system id - System ID: 6200. Exit code - 0xffffffff
[8/20/2014 9:25:25 AM] Thread exited. Exiting thread system id - System ID: 6244. Exit code - 0xffffffff
[8/20/2014 9:25:25 AM] Thread exited. Exiting thread system id - System ID: 7916. Exit code - 0xffffffff
[8/20/2014 9:25:25 AM] Thread exited. Exiting thread system id - System ID: 5320. Exit code - 0xffffffff
[8/20/2014 9:25:25 AM] Thread exited. Exiting thread system id - System ID: 5348. Exit code - 0xffffffff
[8/20/2014 9:25:25 AM] Thread exited. Exiting thread system id - System ID: 7188. Exit code - 0xffffffff
[8/20/2014 9:25:25 AM] Thread exited. Exiting thread system id - System ID: 4920. Exit code - 0xffffffff
[8/20/2014 9:25:25 AM] Thread exited. Exiting thread system id - System ID: 1912. Exit code - 0xffffffff
[8/20/2014 9:25:25 AM] Thread exited. Exiting thread system id - System ID: 1388. Exit code - 0xffffffff
[8/20/2014 9:25:25 AM] Process exited. Exit code - 0xffffffff
* EXCEPTION DETAILS *
DetailID = 1
Count: 1
Exception #: 0XE06D7363
Stack:
Call Site
KERNELBASE!RaiseException
msvcrt!CxxThrowException
VSSAPI!CVssJetWriter::SetWriterFailure
VSSAPI!CVssJetWriter::SetWriterFailure
VSSAPI!CVssJetWriter::SetWriterFailure
VSSAPI!CVssJetWriter::SetWriterFailure
VSSAPI!CVssJetWriter::SetWriterFailure
VSSAPI!CVssJetWriter::SetWriterFailure
msvcrt!srand
msvcrt!ftime64_s
kernel32!BaseThreadInitThunk
ntdll!RtlUserThreadStart
DetailID = 2
Count: 1
Exception #: 0XE06D7363
Stack:
KERNELBASE!RaiseException
msvcrt!CxxThrowException
VSSAPI!CVssJetWriter::SetWriterFailure
VSSAPI!CVssJetWriter::SetWriterFailure
VSSAPI!CVssJetWriter::SetWriterFailure
VSSAPI!CVssJetWriter::SetWriterFailure
VSSAPI!CVssJetWriter::SetWriterFailure
VSSAPI!CVssJetWriter::SetWriterFailure
msvcrt!srand
msvcrt!ftime64_s
kernel32!BaseThreadInitThunk
ntdll!RtlUserThreadStart
DetailID = 3
Count: 1
Exception #: 0X80000003
Stack:
ntdll!RtlUnhandledExceptionFilter
ntdll!EtwEnumerateProcessRegGuids
ntdll!RtlQueryProcessLockInformation
ntdll!RtlLogStackBackTrace
ntdll!RtlIsDosDeviceName_U
ole32!CoTaskMemFree
wbengine
wbengine
wbengine
wbengine
wbengine
wbengine
wbengine
kernel32!BaseThreadInitThunk
ntdll!RtlUserThreadStart
DetailID = 4
Count: 1
Exception #: 0XC0000374
Stack:
ntdll!RtlUnhandledExceptionFilter
ntdll!EtwEnumerateProcessRegGuids
ntdll!RtlQueryProcessLockInformation
ntdll!RtlLogStackBackTrace
ntdll!RtlIsDosDeviceName_U
ole32!CoTaskMemFree
wbengine
wbengine
wbengine
wbengine
wbengine
wbengine
wbengine
kernel32!BaseThreadInitThunk
ntdll!RtlUserThreadStart
* EXCEPTION SUMMARY *
|--------------------|
| Count | Exception |
|--------------------|
| 2 | 0XE06D7363 |
| 1 | 0X80000003 |
| 1 | 0XC0000374 |
|--------------------|
Any help would be greatly appreciated.

Hi
Similar post:
http://social.technet.microsoft.com/Forums/windowsserver/en-US/4d87c9a1-8f1b-4bb3-8b13-ee37bc3c014b/windows-server-backup-failing-to-start-error-a-fatal-error-occurred-during-a-windows-server-backup?forum=windowsbackup

Mount vhdx file from Windows Server Backup 2012

We have a 2012 server with a network share that other servers backup to using Windows Server Backup. To view the files from a windows 2008 r2 backup .vhd file all I have to do is open it in windows explorer and it mounts as a drive and opens. When
I try to do the same with a 2012 backup (.vhdx) it tells me "you don't have permission to mount the file" but if I open disk management I can see the volume, and if I right click on it and select "Change Drive Letter and Paths" and add
a drive letter, then I can browse it. I get the same issue using mount-vhd in powershell.

Hi Adm1nMikeW,
Please try to use disk management --> action --> attach VHD (this way will avoid the error message).
The root cause is the attribute "nodefaultdriveletter" of the backup vhd was not set to "no".
You can try following setps :
1. in cmd prompt type diskpart
2. recognize the problematic volume you want to set via list volume
3. run command select volume "volume number"
4. run command attributes volume clear nodefaultdriveletter
then detach it and reattach the disk again .
Hope this helps
Best Regards
Elton Ji
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.

Backed up files partially disappear after restore (Windows Server 2008 R2 - Windows Server Backup)

Dear all,
I am experiencing a problem with "Windows Server 2008 R2", using Windows Server Backup.
Here's my setup:
Server: RAID 5 Disk setup
Backup:
By using Windows Server Backup (within Windows Server 2008 R2), C: and D: were fully backed up, with "System State" and "Baremetal Recovery" options selected. Backup went okay without any errors.
Restore:
By using Windows Recovery Environment (booted from Windows Server DVD), C: and D: were fully restored to the original partitions with "System Recovery" option found within Windows RE (without re-formatting partitions during restore). Restore
went OK without any errors. Rebooted, and system has been running fine.
Problem:
After the restore, the system itself seems running OK; no BSOD, no crash, no visible errors.
However, our client insisted some files (around 6 to 7) which are related to the propriety software has "disappeared" right after System Recovery.
Question:
Since Windows Server Backup is using "Volume Shadow Copy" technology which enables "live backup" of the running system, is it possible that some files will disappear (=restore error) after
System Recovery?
I cannot really find any errors or warnings related to Windows Server Backup in the event log, through. No Windows-backup errors. No VSS errors, too.
Do anybody have experienced this kind of problem in the past? Any suggestion will be greatly appreciated.

Thank you for your reply, Ms. Mandy.
To make things clear, let me explain to you briefly:
1. The "missing data" was backed up with "full system backup".
2. After a system restore from the above backup image, as you mentioned, partitions has been overwritten with the partions' backup data in the Backup Data Set taken by Windows Server Backup. No error with backup. No error after restore, and reboot - system
has been running fine.
3. Although there was a report that the affected files(about 7 java exectables) were missing after the above restore operation, other aspect of system was running fine at the time of the report.
4. I have checked the original backup data set - and voila, there ARE files which seems to gone after restore.
5. When I used Windows Server Backup "on" Windows Server 2008 R2 normal environment (= NOT Recovery environment from DVD) and selectd ONLY these affected files to restore, these files could be RESTORED successfully, without any errors. SO... data
was property backed up.
> The recovery will overwrite the partitions so files created after the backup point will be missing.
I understand, and this is not the case this time, because the affected files are already present in the backup data set (= I have mounted the backup data as VHD, and I could clearly see them present in the mounted VHD file)
Plus, these files are completely restoreable via "selective file restore" in Windows Server Backup.
Things I want to know/confirm:
> The recovery will overwrite the partitions
If I understand this correctly, in case that the files in question are already present in the backup data set, these files SHOULD be restored after full system restore, right? (If these files could not be restored, Windows Server Backup SHOULD show some errors.)
What do you think, Ms. Mandy? :)
Jo

A fatal error with Windows Server Backup

Similar Messages

Maybe you are looking for