I have a server running 2012 Essentials. Windows Server Backup is set to run twice a day. The backups are being saved to a VHD file that is mounted just prior to the job and then dismounted after the job via scheduled tasks.

Some of the jobs are completing without error but others are failing saying they completed but have warnings. Here is an example.

Under the Data Transferred column for System Reserved it says 960 KB of 960 KB but under the Status column is says 1% of backup done. 960 KB of 960 KB is 100% so I don't understand why it says 1%. The C: and D: drives and System State have status of Completed but the Bare metal recovery says Backup failed to complete.

When I look on the Errors tab, for both System Reserved and Bare metal recovery the message is the same, "There was a failure while compacting the virtual hard disk on the backup location. Detailed error: The process cannot access the file because it is being used by another file."

I don't understand how this error is occurring. I'm sure it's not a case of the backup drive getting dismounted too early as the backups are incremental and take less than 1/2 hour to run but the time between mount and dismount is 3 hours.

I don't know what other process could be using the "file" nor what "file" it is referring to.

The Windows Event Logs contain even less information than the WSB details so they are of no help.

Anyone have an idea what might be going on? This is not a consistent problem as some backups run just fine including both scheduled times.

Jonathan

I took back of my windows 2012 physical server and the file it created is in VHDX format. I have the backup file copied to another location. Now i completely wiped off the array on this server, re-created the arrays in the same form like before. Now how do i get my bare metal server restored to previous state using VHDX file? This is very confusing , there is no proper documentation on how to back and restore physical servers. Any help is appreciated.

Hello,

I have a question about Hyper - V replica.

I have configured Hyper - V replica for one virtual machine with Windows Server 2008 R2 (hypervisors are using Windows server 2012R2). I have created also backup with windows backup in recovery site. I have the following issue:

Second server has stopped to be replicated before a month and there is no working backup either.

I have a problem with the primary Virtual machine and it is not working now. I checked the log in primary hipervisor and it looks that there some data that should be replicated. 

I was wondering whether if i start the secondary virtual machine the replication will be resumed to the last available snapshot?

 Thank you in advance!

Hi,

I am tring to restore a Server 2008 R2 Standard Ed (full installation) RTM to a virtual machine, from a full Windows Server Backup image taken of a physical machine (Dell PE 2970).  All restores fine, and looks good until it tries to boot, when a Stop Error occurs, with the following error:

*** STOP: 0x0000007B (0xFFFFF880009A9928, 0xFFFFFFFFC0000034, 0x0000000000000000, 0x0000000000000000)

I believe the non-bracketed portion means "INACCESSABLE_BOOT_DEVICE".

There is only the System Reserved volume + a C: volume (system volume) + F: volume (DVD drive) on the original server.  It has had other volumes in it before, which are correctly listed in the MountedDevices registry key, but they have not been physically present for a while.

The virtual disk I'm trying to restore to is several GBs larger than the original virtual disk on the RAID controller (2 disks in RAID 1).

I can't figure out why the server isn't booting.  I've successfully restored Server 2008 machines from physical machines to VMs before, including servers using hardware RAID cards (e.g. Dell SAS 6/iR).  The only difference I can think of is that this is Server 2008 R2, this is a 2 proc server (I've tried several virtual proc numbers on the VM to no avail), and the RAID controller is PERC 6/i, and this is the first server I've tried with that particular RAID card.

Any help would be greatly appreciated, even if it's to point out that I'm looking in the wrong direction.

Many thanks,

Chris

Hello, I have a WD Sentinel DX4000 12TB unit and it’s recently been locking up.

After talking to WD Help they recommended I ‘Perform a Recovery’.

However every time I get to the last stage I get the error message ‘Error Code: 0x8007000d’

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

Recover your server

Could not reset the server to factory default settings

Your server was not reset to the factory default settings. Resolve the issue, and then restart the server recovery process.

Error Code: 0x8007000d

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

On the drive its says 'Recovery Started' but no progress number.

This drive has 9 years of my life on it and I am just a bit panicked.

Any help much appreciated,

Thor

I'm looking for notes/documents if the following can be achieve.

I want two identical machines running the same software and configuration so that if one goes down i can just bring up the other one on our LAN.  I will also need the primary to update the secondary on a predetermined schedule. 

I'm having a hard time cloning a RAID configure hard drive.

I am using a 2TB usb 3.0 drive to backup my data drive and keep getting eh error "Failed" "Volume is too small to accommodate restore point metadata. Please ensure that on volume included in backup is at least 512mb in size".

The data drive has over 22gb of data on it.

I have no idea what the problem is, can anyone help

I'm trying to restore a server running Windows 2008 R2 Standard. The server is an IBM x3250 M3 with EFI.

I did a complete image backup of the two drives to a network share.  Then I try to restore to the same server, (with no hardware changes).  When I run the restore, I get this message:

"The system image restore failed.

Windows cannot restore a system a system image to a computer that has different firmware. The system image was created on a computer using BIOS and the computer is using EFI."

Any help would be greatly appreciated.

Ok so here is my situation.

I have a Server 2008 R2 Enterprise and I have performed a Full System backup using the Server Backup feature. Originally the drives were on a 72GB hard drives RAID 1 and I want to upgrade them to 300GB Hard Drive.  So I decided that I would just backup and restore onto the 300GB Hard Drive.  But when I try to perform the server 2008 recovery, it will not recognize the backup on the external hard drive at all.  It wont even show up in the list.  But if I go searching for drivers it shows up just fine in the drive list.  So what am I missing?

Hi All,

I'm currently experiencing problems with my Windows 2012 Server Backup (Windows 2012 Essentials). I backup my data to a dedicated Iscsi drive (on a Synology box) using the build-in Windows Server Backup tool. Everything was running fine with at one moment 20 backups available. After that the diskspace was nearing it's limit of 2.5 TB. 

As described by Microsoft the windows backup tool should, when nearing it's limit, delete the oldest snapshot and as a result keep e.g. 20 backups but moving the oldest backup-day consequently. 

My problem is that this did not happen. It instead deleted all the current copies and started over fresh! So only ONE copy available (clearing all the 20 stored backups!!). This is very unwanted and basically eliminates the entire use of the backup software!

When looking at the windows logfile I saw that a lot of vhdmp warnings were present with a message like:

Reset to device, \Device\RaidPort3, was issued.

Eventueally I also saw a eventID 33 followed by and error on eventID 33

The shadow copies of volume \\?\Volume{93896cfc-d904-11dd-8cb5-001ec9ef572e} were deleted because the shadow copy storage could not grow in time.  Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadow copied

It seems that because the drive is somehow to slow to respond (maybe iscsi isn't getting enough IO throughput) and Windows thinks the snapshots are unavailable and deletes ALL the snapshows and starts over fresh.

Some People suggest to set a limit on the shadow copies. But others have reported this does not work. A thread about this exists but no answer from Microsoft until now :(. Relevant discussions here and here

Does anyone have an answer to mitigating these problems? It basically destroys my backup plan! Surely others will be doing the same things (backing up to a dedicated media with limited space ?)

Regards, Martin

Hi,

The system state is constantly failing on our Windows server 2012.
We get the error "Backup failed to complete. The system writer is not found in the backup." when trying to take the backup locally on our server.
The server contains 3 drives, Does not matter what drive I chose, The C: (Windows drive) has 96GB free out of 130 GB.

Information regarding the server:
OS: Windows Server 2012 Standard 64-bits (6.2 Build 9200)
Microsoft SharePoint Server 2013
Microsoft SQL Server 2012
Antivirus: System Center Endpoint Protection
It is a virtual machine with 16384 MB RAM and a page file with 18686 MB

We are using DPM 2012 Service pack 1.
It lists the following error when trying to take the backup/check inconsistency:

"Affected area: Computer\System Protection

Occurred since: 2014-07-11 08:14:29

Description: The replica of System Protection Computer\System Protection on SERVERNAME is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check. You can recover data from existing recovery points, but new recovery points cannot be created until the replica is consistent.

For SharePoint farm, recovery points will continue getting created with the databases that are consistent. To backup inconsistent databases, run a consistency check on the farm. (ID 3106)
 DPM cannot create a backup because Windows Server Backup (WSB) on the protected computer encountered an error (WSB Event ID: 517, WSB Error Code:  0x1D34BA0). (ID 30229 Details: Internal error code: 0x80990ED0)
 More information
Recommended action: For resolution actions and more information on the WSB error, go to http://technet.microsoft.com/en-us/library/cc734488(WS.10).aspx.
 Synchronize with consistency check.
 Run a synchronization job with consistency check..."

EventIDs listed on the server:
Source: CAPI2, EventID 513
With the error message

Troubleshooting performed:

Performed backup locally using Windows Server Backup (It fails after a few seconds saying "Backup failed to complete. The system writer is not found in the backup." )
When using the vssadmin list writers, It lists the following:

Microsoft Windows [Version 6.2.9200]                                            (c) 2012 Microsoft Corporation. All rights reserved.   
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool      (C) Copyright 2001-2012 Microsoft Corp.

Writer name: 'Task Scheduler Writer'                                              
Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}                              
Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}                     
State: [1] Stable                                                              
Last error: No error 
                                                                                                                                      
Writer name: 'VSS Metadata Store Writer'                                          
Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}                              
Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}                     
State: [1] Stable                                                              
Last error: No error  
                                                                                                                                     
Writer name: 'Performance Counters Writer'                                        
Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}                              
Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}                     
State: [1] Stable                                                              
Last error: No error
                                                                                                                                       
Writer name: 'SqlServerWriter'                                                    
Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}                              
Writer Instance Id: {5f0a641e-7fb4-422b-bbc5-d60ecf688d75}                     
State: [1] Stable                                                              
Last error: No error
                                                                                                                                        
Writer name: 'ASR Writer'                                                         
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}                             
Writer Instance Id: {1bb12ddb-a7fd-424e-87fa-48e3f245a6c7}                     
State: [1] Stable                                                              
Last error: No error 
                                                                                                                                     
Writer name: 'Shadow Copy Optimization Writer'                                    
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}                              
Writer Instance Id: {c5bce6a4-2bbc-4df7-9938-580b2dbba292}                     
State: [1] Stable                                                              
Last error: No error  
                                                                                                                                     
Writer name: 'Registry Writer'                                                    
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}                              
Writer Instance Id: {bbcf0fd9-e505-4fa1-b83c-1734d4c249ac}                     
State: [1] Stable                                                              
Last error: No error    
                                                                                                                                   
Writer name: 'WMI Writer'                                                         
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}                              
Writer Instance Id: {a96beab3-2709-48c6-b48a-e730159c3a1a}                     
State: [1] Stable                                                              
Last error: No error 
                                                                                                                                      
Writer name: 'IIS Metabase Writer'                                                
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}                              
Writer Instance Id: {cd1daf6a-79e8-411c-a1a7-1459fe2eb952}                     
State: [1] Stable                                                              
Last error: No error 
                                                                                                                                      
Writer name: 'COM+ REGDB Writer'                                                  
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}                              
Writer Instance Id: {4527bf6a-c5b9-42dd-8320-21705ccd8dff}                     
State: [1] Stable                                                              
Last error: No error 
                                                                                                                                      
Writer name: 'BITS Writer'                                                        
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}                              
Writer Instance Id: {761ff855-d6cc-4e0d-a831-efa50e798192}                     
State: [1] Stable                                                              
Last error: No error
                                                                                                                                       
Writer name: 'IIS Config Writer'                                                  
Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}                              
Writer Instance Id: {279dc9c7-5727-4ee1-bdfd-52f058b3e9b5}                     
State: [1] Stable                                                              
Last error: No error  "

- Tried the KB2009272 (http://support.microsoft.com/kb/2009272/sv)
- Shadow copies are NOT enabled on the server.
- There is enough space on the server itself and where we store the backup.
- Removed the server from the protection Group and all backed up system states of it that was stored (It has not successfully ran in a long while but somehow there was data being taken up) then added it again. It is OK until i run a inconsistency check.
- Backup of C:, D:, L: and SQL databases works fine.
- We have this occuring on several Windows server 2012 that has the same configuration as this one (SharePoint and SQL) so we have found the following article that describes that the SharePoint 2013 breaks the VSS writer and therefor the backup cannot be run.Article: http://blogs.technet.com/b/dpm/archive/2011/10/31/troubleshooting-data-protection-manager-system-state-and-bare-metal-backup.aspx

Best regards,
Sebastian

Hello

We have been running a Windows Server 2008 Standard on an old HP ML350 server for many years.  The old server finally kicked the bucket so we performed a bare-metal restore (using the Windows built-in restore from backup function) to a new (used) HP DL380 G6 server...  the restore worked perfectly.  The new server came right up and everything is working just as it was on the old server except for one major problem.  The new server won't activate.

We used the Automated phone line activation utility but after putting in the zillion character installation id, the phone activation voice says the product is invalid and hangs up on me.  We tried the "buy a new product key" option that the Windows Activation utility on the server offers as an option but when we get to the website it says the product is no longer available.

We have the original case and media that we purchased many years ago and the Product Key is on the card that came with the disk (actually 2 discs  32 and 64 bit versions).

What can we do at this point?  We don't want to purchase another copy of Windows Server 2008 for fear we will just run into the same problem.  The product we have is valid and has been running on our old server for many years.  We can't upgrade to Server 2012 because we believe that 2012 only supports 64 bit versions and we must stay on a 32 bit platform so that existing (and irreplaceable) applications will continue to run. 

Any suggestions? 

Event Log:The backup operation that started at '‎2015‎-‎01‎-‎18T06:28:26.580441900Z' has failed with following error code '2155347997' (The operation ended before completion.). Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.

Issue :System State Backup Failed on windows server 2008 R2. This is not a VM and Virtual Box and SQL is not present on the system . This is a Physical machine.

I referred to the thread and didn't find the solution. That was also bit similar kind of issue .Can anyone please help me to get it resolved.

Thanks in Advance !!

I am using Server 2008 r2 Std.  Last three days I have been facing this Problem(Backup fail)

"""""""""The operation to backup the volume was stopped before it started running""""""""""   This the error massage

we are having Domain controller with windows 2008 Core. this has been hosted in vmware. during the time of initiating the

time of initiating the systemstate backup the OS get hung and need a reboot for the same. Please find the command below

wbadmin start systembackup –backupTarget:<target drive location>:

Please help on troubleshooting this

Thanks

hariharan

I have an issue with windows taking forever to boot after setting up Windows backup.

PC Setup:

2 Samsung SSD Mirrored for Hardware raid on (MOBO OS/Programs)

2 Seagate 4TB Mirrored for Hardware raid (Data storage)

1 Seagate 4tb HD used solely for Windows backup.  (Have also tried with multiple other drives with same outcome.)

If I have all drives connected without setting up the Windows Backup, system will boot up in 37 seconds.  As soon as I enable the backup to the additional drive, it kills the boot time.  Brings boot time to over 2.5 mins.  Brand new PC, clean installation, no antivirus or any other software that could be slowing it down.  If drive is just in PC as an extra drive there seems to be no issue, just as soon as I enable the Windows Backup to additional drive. Never noticed this issue on any other PC