Hello

We have a Windows Server 2012 machine that runs a VSS full backup daily using Windows Server Backup to a dedicated partition.

It's been running fine for close to 2 years now and was automatically clearing old backups when space was needed.

We used to have about 250 backups available but for some reason even though there was space available it deleted all of them about 3 weeks ago.

I now have about 15 backups available and again even though there is enough free space it doesn't seem to retain all the backups it should.

I can't find anything useful in the logs and as far as I understand it there is no way for me to specify the backup retention period.

I would appreciate any help you can give me in troubleshooting this issue.

Thank you

Hey,

I cant start my Windows Server Backup tool on my Windows Server 2008 R2. It gives me error:

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

"A fatal error occured during a Windows Server Backup snap-in (Wbadmin.msc) operation. Error details: 

The Windows Server Backup service has stopped.. 

Close Wbadmin.msc and then restart it. 

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

Event Viewer:

The following process dump file was generated:
 C:\Program Files\DebugDiag\Logs\Crash rule for all instances of wbengine.exe\wbengine__PID__1144__Date__05_06_2015__Time_11_03_07AM__639__Second_Chance_Exception_C0000005.dmp

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 read on some topic, that I should re-create the Backup folder in task scheduler. I did that but it didnt help. That folder is also empty. 

Here is the dump file.

I'd like to create an automated rotating schedule of backups using wbadmin and task scheduler, which would backup Bare Metal Recovery; System State; Drive C: and D: to a Network Share in a pattern like this:

• Monday - Incremental, overwrite last Monday's
• Tuesday - Incremental, overwrite last Tuesday's
• Wednesday - Incremental, overwrite last Wednesday's
• Thursday - Incremental, overwrite last Thursday's
• Friday - Incremental overwrite last Friday's
• Saturday - Full, overwrite last Saturday's

I need to use the wbadmin commands within the Task Scheduler and do not know any of the required Syntax to make sure everything goes smoothly, I do not want to do this through the CMD.

Sir,

We are using Windows Storage Server 2008 OS for our Storage Server. In this We ae trying to take backup using Windows Server Backup utility.

In Select Backup Items option, not able to select the sub folders and files. It shows only the drives. But, In windows Server 2008 R2 Enterprise OS, We are able to select the sub folder and files.

What are the setting to be change to select sub folders and files in Windows Storage Server 2008?

We are running Exchange 2010 on a 2008R2 server.

The servers System Reserved partition is listed as only having 6% available space.

We assigned a drive letter and looked around the drive and see nothing that can be deleted.

This lack of space is causing the vss writers to fail according to Veeam our backup provider.

Is there a "safe" way to expand this 100MB volume so I can renable my application aware backups again?

Hi

I am doing some lab testing and when I try to restore some active directory object I go to Directory services restore mode type .\administrator and password for Directory services mode and when I try to run the command wbadmin get versions I get this error

The Specified service does not exist as an installed service

Dont understand what specified service does not exist as an installed service

Anyone has an idea

Dalibor Bosic

Hello all,

We have a Windows Server 2012 R2 VM running on a Xenserver and it is our main Domain Controller. I just added the Windows Server Backup feature and attached a new Virtual Drive and assigned the letter B: to store the backups. After I went through the Wizard to create a schedule (I chose to do a full bare metal backup), I got the message:

This disk will no longer be visible in Windows Explorer—to prevent data from accidentally being stored on the drive and then overwritten, and to prevent accidental loss of backups.

Up to there it is all fine, but how do I make this drive visible so I can copy the backups to another computer and an off-site location. I tried to browser to the drive path like b:\Windowsserverbackup\<server name> and it did not work. Any help would be very appreciated. Thanks. 

From Microsoft Technet

Dear all,

I am really  frustrated with Windows server backup, i took Bare metal, system state and complete backup of My Domain controller Multiple times and it went successfully.

When i try to restore the backup it is failing, due to this i lost my Domain controller and promoted additional domain controller by seizing the roles. Please some one help me by providing steps to backup and restore.

Thanks in Advance.

Hi Guys,

Do we have GPO Settings for restricting users for creating files and folders on the desktop. If so Could you please share the details.

Thanks.

Tanooj

This problem was first encountered on an IBM x3650 in a cluster with an IBM x3550 for failover, however this problem is reproducible on a server running HyperV not part of a cluster.

When I try to run a VM based backup from inside the VM using the server backup utility to E: drive(which is an attached vhdx file). It fails with this error

Backup failed to complete. There is not enough disk space to create the volume shadow copy on the storage location. make sure that, for all volumes to be backup up, the minimum required disk space

for shadow copy creation is available. This applies to both the backup storage destination and volumes included in the backup. Minimum requirements: For Volume less than 500 megabytes, the minimum is 50 megabytes of free space. For volumes more than 500 megabytes, the minimum is 320 megabytes of free space. Recommended: At least 1 gigabyte of free disk space for each volume if the volume size is more than 1 gigabyte.

Detailed Error: Insufficient storage available to create either the shadow copy storage file or other shadow copy data.

In the event viewer I see this error

EventID: 521 The backup operation that started at '‎TIME’ has failed because the Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed with following error code '0x80780119'. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.

This problem was not happening in our test setup using Server 2012 R2 MSDN copy, before rolling out to production  using ourVolume license copy of server.So as a test I installed two VMs on a Host(MSDN), one VM using our MSDN copy of server and one with our  Volume license copy of server,very simple install, install Windows backup, attach VHDx file and attempt bare metal backup. The MSDN copy is able to perform the bare metal backup. TheVolume license copy fails with the above errors.

Has anyone else run into this problem? Or any ideas on where to look to see the differences between the two VMs that is stopping the backup from completing?

I am running server 2012r2 standard with Hyper-V installed and im backing up three VMs (2 windows, 1 CentOS)

The backups run with no issue using the standard default options (full backup etc.). After the backup completes the CentOS VM for some reason remounts the filesystem Read Only. When i reboot the VM it comes back up with no issue. I have confirmed that it must be something with windows server backup since the logs on the vm rergarding the remounting of the filesystem coordinate with the backup schedule. When i take this vm out of the backup pool i have no issue. I cant find a whole lot about this online. Can anyone shed some light on this? What information would you need from me?

I have a Windows 2008 R2 server where Windows Server Backup has started failing.

WSB error says "there is not enough space on the disk". This doesn't make sense to me. The backup is a full backup of system state, C: and E: (D: is the DVD drive). C: is using 91GB out of 120GB. E: is using 159GB out of 810GB. Together this is 250GB plus the system state to back up. The backup drive is a 500GB drive in a removable cage. There are 3 swappable disks but I started over from scratch and deleted the job. I then recreated the job and told it to use just the disk that's currently in place and had it format the drive.

The only other clue is in the Event log the error code given is 2155348010. So far I haven't found anything useful about that code.

The backup completes its backup of System State, Bare Metal Recovery, System Reserved partition, and C:. Then it fails when it starts to backup E:.

I hope someone can provide an answer so I can get this backup working again. What I'm seeing doesn't make any sense.

Jonathan

Hi

We are looking for a way to safely install all windows & application updates and restore / recover the servers in case of any failure with these updates. As we know, with client OS we have the recovery points, with HV we have the snapshots etc. We found a useful KB article (http://www.techrepublic.com/blog/data-center/how-to-restore-a-system-image-in-windows-server-2012/), but not sure about Windows backup solution and it's not practical to backup all production servers before applying the patches.   

Please let us know is there any tool or workaround for this

Thanks in advance

LMS

I've got a server running Server 2012 R2 Standard with a 21TB volume that I need to backup. Unfortunately it appears that WSB isn't capable of backing up a volume of this size. I've searched and have not been able to find any definite volume limit in the documentation.

Has anyone else run into this?

Thanks,

Dewayne

Fellows,

I have a server running 3 VM's with Hyper-V, the VM's are always up and running.

I installed an external HD and I'm backing up to it all the data: System Data, C:(OS) and D:(VM disks).

The backup is been running fine for the last couple months, without failure, and I can see ALL the data that is getting backed up, as VSS copy backup.

My question is this, if ONE day I need to recover a specific file (lets say a file from the File Server VM, that was accidentally deleted), or something else more catastrophic happens, CAN I count on these backups for data retrieval? Or because the VM's are running they are not getting backed up?

I recently created a disk pool of 2.5gb via 2 sata HDD's and when I try to assign it to Server Backup duties the process fails. The message I get is that the server backup services are not running so try starting them manualy via services.msc. The services concerned are:Addininfrastructure.svc, Clientfilebackupprovider.svc, Identity.svc and Serverbackup.svc.

However after starting the services (all were set to Auto) via services.msc the problem still remains. The pool is visible via Storage/Hard disks on the dashboard.Has anybody had/solved this problem before?

TIA, Colin

VSS writers inside virtual machine 'CONTOSO' failed to perform BackupComplete to its shadow copy (VSS snapshot) set: Catastrophic failure (0x8000FFFF). (Virtual machine ID 9851BE14-F276-459D-8D60-DF73B67EB658)

What does it mean? Writers on virtual machine are OK and all backups are successfull. Every day I have one 10172 event for one backup in Hyper-V-VMMS event log.

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 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: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {17daa546-f2b5-44a8-b88f-31fae0650076}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {75f7fecf-4696-4f0e-8d09-19809d5f35da}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {204ef83b-d168-4179-a6aa-ef01e93dae7d}
   State: [1] Stable
   Last error: No error

Writer name: 'WIDWriter'
   Writer Id: {8d5194e1-e455-434a-b2e5-51296cce67df}
   Writer Instance Id: {b45a4a13-60a4-4f38-bdc0-c4cc748f3513}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {aca59bd3-2f19-4c76-b54a-28f2c2d95f73}
   State: [1] Stable
   Last error: No error

Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {41ef02d7-38b9-424a-b35b-a4b1cf79bd17}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {7a6ef84a-4fff-46ed-8921-da0d12fb5028}
   State: [1] Stable
   Last error: No error

Writer name: 'MSSearch Service Writer'
   Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
   Writer Instance Id: {6d28a625-90a9-47a4-bf9f-fd8a6c76e770}
   State: [1] Stable
   Last error: No error

Writer name: 'MSMQ Writer (MSMQ)'
   Writer Id: {7e47b561-971a-46e6-96b9-696eeaa53b2a}
   Writer Instance Id: {5bca99fe-6db6-4994-a744-e4149ba54364}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {d8249c2a-530f-48e9-92c3-179762ed0064}
   State: [1] Stable
   Last error: No error

Writer name: 'TermServLicensing'
   Writer Id: {5382579c-98df-47a7-ac6c-98a6d7106e09}
   Writer Instance Id: {51f5c94d-514b-4ca7-b5dd-2f11047d6a54}
   State: [1] Stable
   Last error: No error

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {ce748865-451a-4189-8276-f2cb177629da}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {207fe098-42ab-430b-9285-c0b902729ade}
   State: [1] Stable
   Last error: No error

Hi Everybody,

I have on my hyper-v failover cluster hosts the same error (server 2012 datac).
All my writers are stable and no error.
All updates and hotfixes I have found are installed (I think :P).
When selecting the backup (volume snapshot) in settings of the vm's the backup fails.
Settings of the VM under “management” select “Intergration Services“. Deselect “Backup (volume snapshot)“.

When deselecting the box the backup will run and complete succesfully.
However I still want to fix the issue and want to backup the vm's without the downtime.

The error appears when running Windows server backup (WSB) and the 3rd party arcserve backup software.
Also when going to properties of C:, shadowcopies, settings and pressing on the Details button.

Error box:

Failed to initialize the Details dialog for Volume C:\
Error 0x80042306: The shadow copy provider had an error. Check the System and Application event logs for mote information.

Does somebody have a fix for me?

A while ago I posted another question but that down not work anymore:
https://social.technet.microsoft.com/Forums/en-US/e00123c7-44a3-4f53-a726-8abca7e4542b/vss-error-server-2012-datacenter-application-12289-12297-12340-8194-system-9?forum=windowsbackup

EVENTVIEWER LOCAL DISK:

Volume Shadow Copy Service error: Unexpected error DeviceIoControl(\\?\Volume{fc58b624-75ef-47bb-aea2-8ae71d91a50b} - 00000000000001B4,0x00530024,0000000000000000,0,0000004E554EA530,4096,[0]).  hr = 0x80070001, Incorrect function.
.

Operation:
   Query diff areas on this volume

Context:
   Volume Name: C:\

EVENTVIEWER CSV DISK:

Volume Shadow Copy Service error: Unexpected error DeviceIoControl(\\?\Volume{fc58b624-75ef-47bb-aea2-8ae71d91a50b} - 00000000000000D0,0x00530024,0000000000000000,0,00000089AC199A00,4096,[0]).  hr = 0x80070001, Incorrect function.
.

Operation:
   Query diff areas on this volume

Context:
   Volume Name: F:\

EVENT ID 8193:

Volume Shadow Copy Service error: Unexpected error calling routine RegSetValueExW(0x0000061c,(null),0,REG_BINARY,000000B66E25C850.72).  hr = 0x800703fa, Illegal operation attempted on a registry key that has been marked for deletion.
.

Operation:
   Gather writers' status

Context:
   Writer Class Id: {41e12264-35d8-479b-8e5c-9b23d1dad37e}
   Writer Name: Cluster Database
   Writer Instance ID: {19c284da-7542-41a7-a5d0-84956ca53e61}

Hi Team,

I just installed two brand-new servers with the brand-new OS Windows Server 2012 R2. I didn't install any other 3rd party applications. I also didn't change any system settings. I just followed the Microsoft recommendation and installed OS. Then I enabled the Window Server Backup feature. But somehow the backup failed with the error messages in the below screenshots.

Regards,
Jun Gao

I am experiencing a problem with Windows Server Backup where previous backup versions (copies) are lost if the connection to the iSCSI target, where the backups are stored, is dropped and remains disconnected for a short time.  

I have configured the Windows Server 2008 server to connect to a QNAP iSCSI NAS device using the built in iSCSI Initiator.  I have also configured Windows Server Backup to use the iSCSI volume as the backup target disk.  Periodically, for reasons not yet understood, the server loses connectivity with the iSCSI device.  When this happens I often find that the backup copies that had existed on the target volume are no longer there and the backups have to start again.

Today I discovered that the volume ID of the target disk seems to change, without manual intervention, when the iSCSI initiator reconnects to the target and Windows Server Backup is refreshed.  This is demonstrated by the output of the WBADMIN GET VERSIONS command, e.g.:

Backup time: 18/05/2011 23:30 

Backup target: Fixed Disk labeled ATEGO-M 2010_03_17 08:29 DISK_01(\\?\Volume{a79ff0ae-2cbb-11df-8798-005056bb11b1})

Version identifier: 05/18/2011-23:30

Can Recover: Volume(s), File(s), Application(s), Bare Metal Recovery, System State

Backup time: 19/05/2011 23:30 

Backup target: Fixed Disk labeled ATEGO-M 2010_03_17 08:29 DISK_01(\\?\Volume{a79ff0ae-2cbb-11df-8798-005056bb11b1})

Version identifier: 05/19/2011-23:30

Can Recover: Volume(s), File(s), Application(s), Bare Metal Recovery, System State

Backup time: 20/05/2011 23:30 

Backup target: Fixed Disk labeled ATEGO-M 2010_03_17 08:29 DISK_01(\\?\Volume{a79ff0ae-2cbb-11df-8798-005056bb11b1})

Version identifier: 05/20/2011-23:30

Can Recover: Volume(s), File(s), Application(s), Bare Metal Recovery, System State

Backup time: 14/11/2011 10:53 

Backup target: Fixed Disk labeled ATEGO-M 2011_05_22 13:08 DISK_01(\\?\Volume{32077493-83cc-11e0-931b-005056bb11b1})

Version identifier: 11/14/2011-10:53

Can Recover: Volume(s), File(s), Application(s), Bare Metal Recovery, System State

Backup time: 23/12/2011 20:34 

Backup target: Fixed Disk labeled ATEGO-M 2011_11_14 17:43 DISK_01(\\?\Volume{c253b27d-0dd8-11e1-bab4-005056bb11b1})

Version identifier: 12/23/2011-20:34

Can Recover: Volume(s), File(s), Application(s), Bare Metal Recovery, System State

Backup time: 30/01/2012 09:20 

Backup target: Fixed Disk labeled ATEGO-M 2011_12_24 10:41 DISK_01(\\?\Volume{62330671-2d51-11e1-b23e-005056bb11b1})

Version identifier: 01/30/2012-09:20

Can Recover: Volume(s), File(s), Application(s), Bare Metal Recovery, System State

You can see that the label (ATEGO-M 2011_12_24 10:41 DISK_01) remains constant throughout, but the volume GUID changes.  I suspect that this causes Windows Server Backup to lose its backup history as it no longer recognises the volume as being the same - although it quite clearly is.

The question is:  Is this behaviour to be expected?  

Should the volume GUID change each time the volume is disconnected and reconnected?

I suspect that it shouldn't.  So, is there a way to fix the GUID so that it remains constant even if the volume becomes disconnected for a short while?

Thanks