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.

Similar Messages

  • Lost Windows Server Backup, historical backups. Backup seems to have restarted from a fresh full backup. How can I get to those old backups?

    Scenario with very bad outlook:
    Friday-16th, early AM.  Win2008 SBS Server crashes due to RAID5 issues, bad disk.  Found that server was NOT configured with hot spare and for some reason the controller had marked a 2nd disk bad..which turned out not to be the case.
    Had a single external USB backup drive being fed by Windows Server Backup.  Obtained support from vendor and was able to regain the RAID and start the server. 
    Soon became apparent that Exchange was having serious issues - edb was corrupt and not mountable.  Restore edb from backup, repaired and was eventually able to mount.  Then found it had Hub Transport issues.  Researching that when it was noticed
    NTFS events being logged at a high rate.  Restarted system to repair the filesystem, which was successful.
    After the FS repair, found the Exchange edb, new edb I had created to migrate mailboxes to, and public edb all 0k in size.
    Restored the edb again and commenced repair, which eventually read Clean Shutdown again...but could not get it to mount.  Exchange was having various issues seemingly with AD.
    Changed backup time to avoid a backup that day, as did not want to back up while RAID was rebuilding - had inserted a replacement for the failed drive.
    Monday/19th, was advised that much of the data was corrupt.  This is an accounting firm and relies heavily on their data, especially since the last time their ext USB was rotated was Nov6 2013.  They now have no year end backup, nor a backup from
    post tax season 2014.
    Is it possible to recover any of the historical backups prior to the full backup/restart?
    Oh, and all Shadow Copies for the impacted volume/drive are gone.
    Thank you.

    Hi,
    Please use the “Wbadmin get versions” command to check the backup versions on the server. If there is only latest shadow copy, you may not recover any of the historical backups prior to the full backup.
    Backup Version and Space Management in Windows Server Backup
    http://blogs.technet.com/b/filecab/archive/2009/06/22/backup-version-and-space-management-in-windows-server-backup.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.

  • 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.

  • [Windows Server 2008 R2] [Windows Server Backup] How to remove an old backup set

    Hello,
        long time ago I made a backup of some files of a server on a network location running manually a command like this one:
    "wbadmin start backup -backupTarget:\\Server1\Backup\MyServer\wbadmin_Effe -include:F: -user:DOMAIN\myself -password:******** -quiet"
    Now this network location is no more available because that machine is definitely broken.
    I have no problems to run and create backups on a local drive or on other network locations.
    My only problem is that now, in the main window of Windows Server Backup, when i click "View details" under "All Backups", I can still see that backup as the oldest available... that's a bit annoying.
    It appears also if I run the command "wbadmin GET VERSIONS".
    Does anybody know how can I remove this backup version set from my server?
    Thanks,
        Alex.

    Hi Alex,
    The command will remove all backups existed on your server. If you cannot get Shadow Copy ID and there are "good" backups existed on you server, you could not remove the old backup versions.
    How to completely delete the backup file from network share and clean up the backup version for the server?
    http://social.technet.microsoft.com/Forums/windowsserver/en-US/2ecc1c25-9308-4c50-be37-9762913cab61/how-to-completely-delete-the-backup-file-from-network-share-and-clean-up-the-backup-version-for-the?forum=windowsbackup
    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.

  • How to schedule multiple backup job through windows server backup in windows server 2008 R2

    hi expert,
    need your help, In my small  environment I am using windows 2008 R2 as a domain controller. and installed windows server feature for backup.
    Now i want to create backup at a different time.
    1. System state backup at 5.00 PM on saturday only
    2.  finance and hr data backup on daily basis at 5.00 PM.
    so how i create different job schedule through windows server backup.
    Regards,
    Triyambak
    Regards, Triyambak

    Scenario #1
    The following command will create a Task Scheduler task named
    DailyFolder1Backup with the start time of 23:00.
    This task will run DAILY with the HIGHESTprivileges. It will run the Windows Server Backup CLI to backup
    g:\folder1 to target volume
    F:.
    SCHTASKS /Create /SC DAILY /TN
    DailyFolder1Backup /RL HIGHEST /ST 23:00/TR
    "wbadmin start backup –backupTarget:F: -include:g\folder1
    -vsscopy -quiet"
    Scenario #2
    The following command will create a Task Scheduler task named
    DailyFolder2Backup with the start time of 24:00.
    This task will run DAILY with the HIGHESTprivileges. It will run the Windows Server Backup CLI to backup
    h:\folder2 to target volume
    F:.
    SCHTASKS /Create /SC DAILY /TN
    DailyFolder2Backup/RL HIGHEST /ST 24:00/TR
    "wbadmin start backup –backupTarget:F: -include:h:\folder2
    -vsscopy -quiet"
    Please feel free to let us know if you have any question or concern.
    Please VOTE as HELPFUL if the post helps you and remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading
    the thread.

  • Can Windows Server Backup spread a single backup job across multiple disks if they are not set up as a virtual disk?

    This may be a dumb question, but I can't seem to find any definitive information after having done many, many searches.  Short question is - can Windows Server Backup spread a single backup job across multiple disks if they are not in a storage
    pool or some other RAID/JBOD structure?
    Background:
    I'm running Server 2012 Essentials with all Windows Updates installed.  I have been backing up approx 2.8TB of data (Bare Metal Recovery, C:, S: (shared folders), and system reserved) for the past year+ onto a storage pool made up of two-2TB external
    USB drives.  Backup is slow (takes approx 1.5 days to complete), but generally works.  Not surprisingly I was constantly getting capacity low messages so I decided to increase my backup storage pool by adding a 3TB drive and another spare 750GB drive
    for a total of 7.75TB.  Instead of having four separate external USB enclosures, I bot a 4-bay enclosure - Startech.com model #S3540BU33E to simplify this (or so I thought!).
    The first problem I had was adding the two new drives to the existing storage pool. I think that is because the Startech uses a JMicron USB controller that reports identical uniqueid's for all drives so only one shows up in the GUI interface for creating storage
    pools. After doing research on this, I set up a new storage pool and virtual disk using all four drives via Powershell and thought I was good. However, when the backup ran, it failed after filling the first drive, saying there was no remaining capacity. In
    reality there were three remaining empty drives and there storage pool reported almost 5TB of avail capacity. I assumed this was due to the identical uniqueid issue so I decided to try a different tactic.
    Instead of using a storage pool that combines all four disks into one virtual disk, I just added each of them to Windows Server Backup as individual drives thinking it would manage them collectively. I.e., when a drive filled up during a particular backup,
    it would just start using the next drive and so on. Apparently this was a foolish assumption because the backup failed again as soon as the first disk filled up.
    So now I don't know if this is still an issue with the identical uniqueid's or if Server Backup actually can't spread a single backup across multiple individual drives that aren't in a pool or other virtual disk implementation. Hence, my original question.
    My guess is that it does *not* spread them across individual disks, but I just wanted to get confirmation.
    Thanks

    Mandy,
    Thank you for following up on my question.
    Unfortunately the article you referenced doesn't address what I am trying to accomplish.
    The article focuses on saving the same backup job to multiple disks and rotating the disks between on and offsite for enhanced protection.  However, it still requires that an individual backup job fits on a single disk.
    What I am trying to determine is if a single backup job can span across more than one physical disk (during the backup process) without those physical disks being in some type of virtual disk implementation (e.g., storage pool, RAID, etc.).
    Thanks,
    Gerry

  • 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

  • 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

  • How are Windows Server Backup and Command Line Tools used in vCSHB installation?

    How are Windows Server Backup and Command Line Tools used during the installation of vCSHB?  Is it required in all types of deployments (PtoV, VtoV, PtoP)? Is it used to create the files that are put in the file share for the second node to use during vCSHB installation or is it only used during a vCSHB clone operation of a Physical to Physical deployment?  Are these tools not used in some deployments?

    You need Windows Server Backup installed on source and destination, and during the installation of vCSHB the installer will invoke the wbadmin (Windows Server Backup Utility) and will backup configuration and application data (application data is optimal but can decrease the sync time after installation of secondary node). On the secondary node you will need only run the vCSHB installer and everything will be restored.
    Check this blog entry for some more info about some problems in P2P deployment: http://www.vcoportal.de/2013/12/vmware-vcenter-server-heartbeat-restore-on-a-second-node-a-journey/

  • 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] .

  • 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]

  • 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.

  • Windows Server Backup won't progress

    Hello,
    Recently, wbadmin on our Windows2008 std. can’t complete its backup (seems breezed at the 30% ….). I tried to start wbadmin  by command line but breezed (at 30%) .  I also checked if there are any bad sectors on the volumes. I ran the chkdsk  but
    no bad sectors.  I looked logs at C:\Windows\Logs\WindowsServerBackup ,but there are no “Critical”, “Warning”,” Error” types logs.
    I am taking two volumes backup (D (160Gb) and F(150GB)) from this server.  It usually finish it about 6 hours but not now.  
    Can you please help me ? 

    Hello Frank,
    Last two days, I tested Windows Server Backup from Wizard.
    When I chose only one volume (F drive), it was successful.
    However, I started three volumes(C: D, F), the backup stopped with error code 2155348001.
    Today, I am going to test this procedure below:
    - Run regedit.exe and navigate to "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\SPP"
    - Create a new Registry value of type DWORD with name "CreateTimeout"
    - Change value to 12000000(2*10*60*1000 = 20 mins) in decimal
    I will give you update when backup finishes. 
    Thank you,

  • 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

Maybe you are looking for