I have been running backups on a Windows 2012 R2 Server (Dell PowerEdge T420) for a few months with no problems.  We backup to a rotation of 3 RDX 1TB Cartridges but found out that Windows Backup does not support removable RDX media.  To get around this problem, we use BackupAssist which still uses Windows Server Backup in the background to complete the backups.

BackupAssist uses a single .vhd container file on the RDX and it is mounted asdrive G:

Again, this worked for a few months with no problems.

Then I ran Windows Update and about 30 updates were applied to the server.  Since then we cannot seem to keep multiple backups on the RDX Cartridge.  Before the Windows Updates, I was able to keep previous backups, sometimes as many as 98 copies.  We are backing up about 30GB of data each night.

Now, since the Windows Updates, I cannot get past 2 or 3 perhaps, and then lose all backup copies and end up with a completed backup, but only 1 backup copy and no previous backups.

We see in the error log the following error, which I believe is the cause of the problem.  Backups run at 8pm nightly.

I have 3 sites setup the same.  2 of the sites had all the Windows Updates applied and then started having this problem.  The above error was never seen until the Windows Updates.  The third site has not had any Windows Updates applied, and we currently have 42 previous backups on the loaded RDX Cartridge.

I have been working with BackupAssist support, but they state that it is simply Windows Server Backup that runs the back end and it is probably a Windows Server issue.  I have been fighting this for 2 months now.

Just wondering if anyone has any idea on the above error.

Thanks in advance to any that can shed some light on this problem.

We are using DPM 2012 to protect several servers.  Periodically (one to two times per week), VSS writers will get in a failed state.  Rebooting the server always clears up the issues but it seems to me that there should be a way to restart services or processes to re-initialize the writers.  For example, when the SQL Server writer is in a failed state, you simply restart the SQL Server VSS Writer service and the issue is fixed most times.  Rebooting production servers two to three times per week just to clear up VSS issues doesn't make sense.  The ones I can't figure out how to fix without a reboot are these:

1. NPS VSS Writer
2. IIS Config Writer (IIS is not currently installed and iisreset doesn't fix it)

All the other writers are pretty easy to figure out, although I'm not sure why "System Writer" is really the Cryptographic service.

Anyone provide some clarification on what service to restart to clear up these VSS writers?

Rob

I have my servers set up to do local backups to external hard drives with a goal of 7 to 14 days of backups using command line scripting.  Each Sunday the scripts rename the external drive WindowsServerBackukp folder to WindowsServerBackupOld before starting the current day's backup. 

On several servers, the backup to the new WindowsServerBackup folder fails.  Typically the new WindowsServerBackup folder is only 5Mb to 10Mb.  Attempts to rerun the backup fail almost immediately:

No other errors are recorded in event logs.  Deleting the WindowsImageBackup folder and rerunning the backup always succeeds. 

I would appreciate any thoughts on what may be causing these failures.

Thanks!

Leon

Hi,

I'm facing backup failure issue in Windows server 2008 R2 Enterprise. VSS writers are went to timed out state and backup failed. 

I've restarted the respective services belongs to VSS writers and still backup failing. Tivoli backup software is doing backup jobs.

Can anyone provide the solution at the earliest.

- Vicky

vicky

Hello,

At this moment we are using a server 2008 R2 SP1 cluster with 2 nodes, using an application clusterdisk (E:).
Both cluster nodes have services wich are pointing towards an E: path.
Unfortunately, our systemstate backup fails on the node where the E: volume (clusterdisk) is not online.

If I make an systemstate backup with "windows backup" it fails and generates an 519 ID :
‘The backup operation that started at '‎2016‎-‎01‎-‎18T20:00:51.247109700Z' has failed to back up volume(s)’

If I make an systemstate backup with "wbadmin" it fails and generates an 517 ID:
The backup operation that started at '‎2016‎-‎01‎-‎18T16:58:44.437751000Z' has failed with following error code '2155347997' 

The hotfix from https://support.microsoft.com/nl-nl/kb/2182466 can't be installed.

I also read in this article (https://social.technet.microsoft.com/Forums/windowsserver/en-US/19ed7bbb-1e6f-4074-bbda-d01411280e8c/wbadmin-failing-system-state-error-517?forum=windowsbackup) the following text :

"i think i figured out an issue with one of the services was poitning towards an incorrect path..the servcie is removed although the system state has started to work but untill system is rebooted will not be able to confirm..."

I would like to know if someone experienced the same issue, and if they know a solution for this problem.

Kind regards,

Johan

Windows Server 2008 R2 edition with Hyper V installed and running two virtual Servers. Using Windows Server Backup to backup systems. On trying to do a test restore and using file and folder I see the server name and then the tree to Local Disk (C:) but when I try to expand the C drive after ten minutes get the error message:

"The open instance of Recovery Wizard was inactive for more than ten minutes. The wizard was automatically canceled to allow other backup or recovery tasks to proceed."

The backup history all shows as successful.

Don't know if this means the backups are useless or something else is preventing the recovery of individual files?

Hope there is a simple explanation for this and all the backups are still salvageable if needed.

Thanks

Chris



Chris P

I have three Gen 2 VM, all running Windows Server 2012 R2 Std, performing scheduled Windows backup to NAS via iSCSI and all are reporting the following event during backup:

Log Name:      Microsoft-Windows-Backup
Source:        Microsoft-Windows-Backup
Date:          2/07/2014 7:01:31 AM
Event ID:      24
Task Category: None
Level:         Information
Keywords:      
User:          SYSTEM
Computer:      SVR03.server.local
Description:
Backup started a fresh backup for volume '{00000000-0000-0000-0000-000000000000}' ('Esp') : [Reason: 'Volume size changed']. This may cause loss of older backup versions when backup completes.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Backup" Guid="{1DB28F2E-8F80-4027-8C5A-A11F7F10F62D}" />
    <EventID>24</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="2014-07-01T21:01:31.237292800Z" />
    <EventRecordID>18</EventRecordID>
    <Correlation />
    <Execution ProcessID="64584" ThreadID="59024" />
    <Channel>Microsoft-Windows-Backup</Channel>
    <Computer>SVR03.server.local</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="VolumeGUID">{00000000-0000-0000-0000-000000000000}</Data>
    <Data Name="VolumeFriendlyName">Esp</Data>
    <Data Name="VhdDeleteReason">Volume size changed</Data>
  </EventData>
</Event>

There has been no explicit volume size change, however these VM all use Dynamically expanding virtual hard disk (VDHX).

A forth VM (Gen 1) running Windows 7 Pro, also provisioned with a Dynamically expanding virtual hard disk does not exhibit this behaviour when it performs a Windows backup.

How can I rectify this situation?

TIA

Troy

Hi guys,

I seem to be having an issue with our Windows Server Backup running on Windows Server 2012 R2. The backup appears to be completing with warnings and some VM's are being skipped. There are 3VM's in total being backed up but 2 are being skipped during the snapshot phase.

The errors in wbadmin are:

• The component [VM Name] was skipped during the snapshot and will not be available for recovery. Error: The writer experienced a non-transient error. If the backup is retried, the error is likely to reoccur.

I get the same warning for both VM's. 

In event viewer I get the following warning:

XML version:

Has anybody seen this before. Could any-one offer any insight as to what may be causing the issue?

Regards

J

I have arcserver backup software and it is failing on the system state so I ran a windows backup just for system state and it failed also with only 2 informational events as follows:

=============================event 1=====================================

Event ID 1001 / Source Windows Error Reporting / Log Name: Application

Fault bucket , type 0
Event Name: Windows Server Backup Error
Response: Not available
Cab Id: 0

Problem signature:
P1: 2
P2: 1
P3: 0x80780102
P4: 0x8078001d
P5: 0x00000000
P6: 0x8078001d
P7: 0x80780064
P8: 0x00000000
P9:
P10:

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_2_eb4095c0d039d80764d38dbbea8fdad2a78b745_00000000_2e4eb9ec <SEE FILE CONTENTS BELOW>

Analysis symbol:
Rechecking for solution: 0
Report Id: ade020c0-b5be-11e5-813a-fc15b421aaed
Report Status: 4100
Hashed bucket:

=================================event 2===============================

Event ID: 517 / Source: Backup / Log Name: Application

XML DATA

Thanks in advance for the help.  I have a Windows Server 2012 R2 Essentials Server that has been running flawlessly for almost six months, including daily backups to a USB-attached 1.8 TB hard drive.  Total internal disk space is 900 GB of which only about 30% is used.

Three days ago, backups started failing with the 0x807800C5 error and "specified backup disk cannot be found" error.  I've tried deleting all of the backups, reformatting the the USB drive, deleting the entire backup configuration and re-initializing, SFC on the backup drive and C drive (no errors)...

No updates or software changes were installed between the time backups were working and when the process began failing.

I have tried backing up via WBADMIN to other locations, including a new/different USB-attached hard drive and the C drive and they respond with the same error.

VSSAdmin List Writers shows all writers stable - no errors.

There are no virtual machines involved on the server.

There are no other errors in the event log other than the backup error.  Below is a listing of the error message details.

Thanks again.

 BackupTemplateID {CBDEBB8E-EADB-4B32-8314-44E8EE942B22}
  HRESULT 0x807800c5
  DetailedHRESULT 0x80780081
  ErrorMessage %%2155348165
  BackupState 12
  BackupTime 2016-01-10T17:48:01.451355100Z
  BackupTarget Hartman200 Backup Drive
  NumOfVolumes 2
  VolumesInfo <VolumeInfo><VolumeInfoItem Name="Esp" OriginalAccessPath="" State="12" HResult="-2139619199" DetailedHResult="0" PreviousState="9" IsCritical="1" IsIncremental="0" BlockLevel="1" HasFiles="0" HasSystemState="0" IsCompacted="0" IsPruned="0" IsRecreateVhd="2" FullBackupReason="2" DataTransferred="0" NumUnreadableBytes="0" TotalSize="0" TotalNoOfFiles="0" Flags="523" BackupTypeDetermined="1" SSBTotalNoOfFiles="0" SSBTotalSizeOnDisk="0" /><VolumeInfoItem Name="C:" OriginalAccessPath="C:" State="15" HResult="-2139619228" DetailedHResult="0" PreviousState="0" IsCritical="1" IsIncremental="0" BlockLevel="1" HasFiles="0" HasSystemState="1" IsCompacted="0" IsPruned="0" IsRecreateVhd="0" FullBackupReason="2" DataTransferred="0" NumUnreadableBytes="0" TotalSize="0" TotalNoOfFiles="0" Flags="1576" BackupTypeDetermined="1" SSBTotalNoOfFiles="0" SSBTotalSizeOnDisk="0" /></VolumeInfo>
  SourceSnapStartTime 2016-01-10T17:48:01.451355100Z
  SourceSnapEndTime 2016-01-10T17:48:57.809252500Z
  PrepareBackupStartTime <TimesList><Time Time="2016-01-10T17:49:13.484Z" /><Time Time="1601-01-01T00:00:00.000Z" /></TimesList>
  PrepareBackupEndTime <TimesList><Time Time="2016-01-10T17:49:13.500Z" /><Time Time="1601-01-01T00:00:00.000Z" /></TimesList>
  BackupWriteStartTime <TimesList><Time Time="2016-01-10T17:49:13.500Z" /><Time Time="1601-01-01T00:00:00.000Z" /></TimesList>
  BackupWriteEndTime <TimesList><Time Time="1601-01-01T00:00:00.000Z" /><Time Time="1601-01-01T00:00:00.000Z" /></TimesList>
  TargetSnapStartTime 1601-01-01T00:00:00.000000000Z
  TargetSnapEndTime 1601-01-01T00:00:00.000000000Z
  DVDFormatStartTime <TimesList></TimesList>
  DVDFormatEndTime <TimesList></TimesList>
  MediaVerifyStartTime <TimesList></TimesList>
  MediaVerifyEndTime <TimesList></TimesList>
  BackupPreviousState 9
  ComponentStatus <ComponentStatus></ComponentStatus>
  ComponentInfo <ComponentInfo></ComponentInfo>
  SSBEnumerateStartTime 1601-01-01T00:00:00.000000000Z
  SSBEnumerateEndTime 1601-01-01T00:00:00.000000000Z
  SSBVhdCreationStartTime 1601-01-01T00:00:00.000000000Z
  SSBVhdCreationEndTime 1601-01-01T00:00:00.000000000Z
  SSBBackupStartTime 1601-01-01T00:00:00.000000000Z
  SSBBackupEndTime 1601-01-01T00:00:00.000000000Z
  SystemStateBackup <SystemState IsPresent="0" HResult="0" DetailedHResult="0" />
  BMR <BMR IsPresent="1" HResult="-2139619199" DetailedHResult="0" />
  VssFullBackup false
  UserInputBMR true
  UserInputSSB false
  BackupSuccessLogPath C:\Windows\Logs\WindowsServerBackup\Backup-10-01-2016_17-48-01.log
  BackupFailureLogPath C:\Windows\Logs\WindowsServerBackup\Backup_Error-10-01-2016_17-48-01.log
  EnumerateBackupStartTime <TimesList><Time Time="1601-01-01T00:00:00.000Z" /><Time Time="1601-01-01T00:00:00.000Z" /></TimesList>
  EnumerateBackupEndTime <TimesList><Time Time="1601-01-01T00:00:00.000Z" /><Time Time="1601-01-01T00:00:00.000Z" /></TimesList>
  PruneBackupStartTime <TimesList><Time Time="1601-01-01T00:00:00.000Z" /><Time Time="1601-01-01T00:00:00.000Z" /></TimesList>
  PruneBackupEndTime <TimesList><Time Time="1601-01-01T00:00:00.000Z" /><Time Time="1601-01-01T00:00:00.000Z" /></TimesList>
  BackupFlags 0x1
  ComponentInfoSummary <ComponentInfoSummary ComponentInfoArrayPresent="1" TotalComponents="0" SucceededComponents="0" />

Jim

This seems to be a problem that has come up before in these forums - I have been through several threads and none of the suggestions have helped fix server backup.

I am trying to perform a System State and C: backup (for Bare Metal Recovery) - backup is to a local drive (so not a NAS or a Network Share). Server Backup used to work but stopped sometime around the time I switched the backup drive (which was running out of space).

Backup fails both from the scheduled Server Essentials Dashboard and also manually using wbadmin. For example:

wbadmin start backup -backuptarget:P: -include:c: -allcritical -vssfull -quiet > "c:\Temp\Server Backup.log"

Gives the following output:

I have a server running Windows Server 2012 R2. I had two non-RAID 2TB hard drives; C drive had the OS and D drive was empty. I did a full system backup with Windows Server Backup and created a system image, WITHOUT including D drive. The size of backup image was approximately 1.2TB. 

I created RAID 1 for the same two drives. I have about 1.8TB free on the C drive. I wanted to restore the system from backup image so I did a boot from Windows installation disc, went to Repair computer -> Troubleshoot -> Restore from system image. I get the error the disk that's active in BIOS is too small! 

It is the same drive that had the OS before I took a backup. I have 1.8TB free on the hard drive after RAID and the backup image size is 1.2TB. How is this error possible?!

Any help on fixing this will be great. Thanks!

Hello,

I have a 2 virtual Windows servers (one SBS2011 and one 2008) that I would like to backup on two Qnap NAS. (one is located in the room than the servers and teh other one is in another building)

I have created and setup two iScsi targets on each NAS and mounted them on both servers (each servers has now a disk mounted on each NAS)

I then configured Windows server backup with multiple target and I was hoping the backup will rotate from one backup disk to the other.

The backup run fine, but it always goes to the same disk.

Is there  way to configure windows server backup so that he use both target disk?

Thanks in advance for your help,

We're deploying Win7 to 100's of machines, need a way to remotely reset/wipe the backup catalog.  This would be the equivalent of doing at the computer console:

  Control Panel
  Back up your computer
  (The last backup did not complete successfully)More Information
  Delete catalog and try to run Backup again

but done remotely/programmatically.

Newly deployed machines that haven't had their backup configured yet occasionally get into this state, we need to remotely reset/wipe the catalog so they can start fresh.  I've tried deleting the sysvol\Windows Backup\Catalogs files and folders, have tried fooling with the entries in hklm\soft\ms\cv\WindowsBackup, no joy.  Have hunted thru registry and hard disk, can't see where this info is kept.  Clients haven't yet created folders at the remote backup target location, so there's no catalog there to delete.  If we do the steps mentioned above at the gui, all is well, but I need to know how to do this remotely without having to visit the client.

Thanks for any info.

HI

Recently I have moved to this new server environment, I am using windows backup 2012 for taking the backup of my exchange 2013.

1. every week I use to take full backup of exchange ( Apps folder, Logs & Database).  around 400Gb size of backup on 2TB hard disk (external USB).

2. today I notice that my hard disk size remain same after the first full backup & there is slight difference in the server backup size and the backup available on hard disk.

3. I also noticed that I cannot find the old full backups that I took before, only I can see today's backup.

4. i tired to see the log history of backup it's showing the old backups date and time with successful option

How can i get the old backups, did i do something wrong in taking the backups,  or how can i set weekly full backup.

so that i can have each week 400Gb backups for each week.

Thank you

I have been running backups on a Windows 2012 R2 Server (Dell PowerEdge T420) for a few months with no problems.  We backup to a rotation of 3 RDX 1TB Cartridges but found out that Windows Backup does not support removable RDX media.  To get around this problem, we use BackupAssist which still uses Windows Server Backup in the background to complete the backups.

BackupAssist uses a single .vhd container file on the RDX and it is mounted asdrive G:

Again, this worked for a few months with no problems.

Then I ran Windows Update and about 30 updates were applied to the server.  Since then we cannot seem to keep multiple backups on the RDX Cartridge.  Before the Windows Updates, I was able to keep previous backups, sometimes as many as 98 copies.  We are backing up about 30GB of data each night.

Now, since the Windows Updates, I cannot get past 2 or 3 perhaps, and then lose all backup copies and end up with a completed backup, but only 1 backup copy and no previous backups.

We see in the error log the following error, which I believe is the cause of the problem.  Backups run at 8pm nightly.

I have 3 sites setup the same.  2 of the sites had all the Windows Updates applied and then started having this problem.  The above error was never seen until the Windows Updates.  The third site has not had any Windows Updates applied, and we currently have 42 previous backups on the loaded RDX Cartridge.

I have been working with BackupAssist support, but they state that it is simply Windows Server Backup that runs the back end and it is probably a Windows Server issue.  I have been fighting this for 2 months now.

Just wondering if anyone has any idea on the above error.

Thanks in advance to any that can shed some light on this problem.