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?

Hi

I am using DPM 2012 SP1 on Windows Server 2012. Trying to backup a Windows Server 2008 that hosts our Windows Deployment Services. We have a number of Images on the D drive of that server using 162GB of space on the hard drive.

There is more space available on the D: drive than the C drive so I have edited the psdatasourceconfig.xml file so that the SystemStateBackup by WBS is backed up to D:\WindowsImageBackup\*. Then the DPM part of the backup can take over and backup to the disks on our backup server.

IF I stop the Windows Deployment Services Service - the backup runs like a dream, takes about 10GB of space on the D drive and then moves over to the Backup Server.

If the Windows Deployment Services Service is running - the D:\RemoteInstall\Images\ folder is included as part of the SystemStateBackup and the extra 162GB of files means that the D: drive runs out of space and the SystemStateBackup fails.

There is a section in the psdatasourceconfig.xml file called <FilesToExclude/> but I cannot work out the syntax for this or if this is the right place.

Can you please help.

Thanks

Debbie

Windows 2008 R2 Standard SP1

Using a Power Shell script on this server to backup this server and the script is launched via Task Scheduler.

Task launch looks like this:
Program/Script: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
Add Arguments: -nologo -noninteractive –Command "& {F:\Scripts\Backup\Backup.ps1}"
Start in: C:\Windows\System32\WindowsPowerShell\v1.0\

It is set to run as an administrative account.

Here is the contents of the PS1 script:

Wbadmin start backup -backupTarget:\\BackupServer\backups$\ -include:'c:,F:\Data,F:\homedirs,F:\Inventory,F:\Production,F:\Share' -allCritical -systemState -vssFull -quiet

$date = get-date -uFormat "%Y-%m-%d"

ren \\BackupServer\backups$\WindowsImageBackup\Server \\BackupServer\backups$\WindowsImageBackup\Server-$date

The backup appears to run successfully. There are no errors in the error logs. According to the logs for that backup date all files were successfully backed up, INCLUDING the data in homedirs.

Despite that when I go to restore data for someone's homedir I cannot do so. When I look through the catalog using Windows Server Backup I cannot see anything in any homedir unless I previously had permission to that directory.

Why is this and how do I resolve this? I need to be able to see individual files within the catalog if I want to restore them for users. I have Enterprise/Domain Admin permissions so adding in permissions isn't a problem but it's something I would prefer not to do.

Hello!

I need to move/migrate a Windows Server 2008 R2 (Domain controller, alone) to new hardware.

So to do this i have:

* Maked a full backup of the old server, with Windows Server Backup
* Restored the backup on the new server, using a Windows Server 2008 R2 install disc.

But when i start the new server this is happening: http://goo.gl/2TcaUQ (Skip to 1:30)
Here you see at the last second that the server is rebooting.

* I tried to start the server with boot logging, but the log file is empty.
* I tried startup repair, but i did not find any tool (used a tool to remove local password) See here: http://goo.gl/NOg7Yb

But if i do a new install of Windows Server 2008 R2 the server it starting just fine.

But I needall applications,SQLServer,domainsetupetc. onthe old server.

What to do?

Symptom One

You attempt toschedule 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 isno 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 resizeshadowstorage /for=<ForVolumeSpec> /on=<OnVolumeSpec> [/maxsize=<MaxSizeSpec>]

More Information

Vssadmin resize shadowstorage

http://technet.microsoft.com/en-us/library/cc788050.aspx

Symptom Two

When you addanother 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 theOriginal 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 attachOriginal 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.

Hi, trying to backup system image using SCDPM 2010 RTM.Most of the server are getting healthy backups except for this one server which is giving error:

Affected area:	Computer\System Protection
Occurred since:	1/27/2014 2:43:27 PM
Description:	The replica of System Protection Computer\System Protection on server.DOMAIN.COM 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:  0x80070057). (ID 30229 Details: Internal error code: 0x809909FB)
	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...
Resolution:	To dismiss the alert, click below
	Inactivate alert

On the server, event viewer show the following events:

1. Backup Log:

Backup started at '2014-01-27T11:26:21.356950100Z' failed with following error code '2147942487'.

2. Application Log:

The description for Event ID 517 from source Microsoft-Windows-Backup cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

27-Jan-14 11:26:21 AM
2147942487
%%2147942487

The resource loader failed to find MUI file

However, when I observe the backup process using "wbadmin get status", it reaches 99% then stops.

Running backup of volume Local Disk(C:), copied (97%).
Running backup of volume Local Disk(C:), copied (98%).
Running backup of volume Local Disk(C:), copied (99%).

Backup stopped before completing.

Summary of backup:
------------------


Backup stopped before completing.
The parameter is incorrect.

The server hardware is HP blade with two disk which are mirrored, and has 12 GB free space. below is the output from systeminfo command:

Host Name:                 server
OS Name:                   Microsoftr Windows Serverr 2008 Enterprise 
OS Version:                6.0.6002 Service Pack 2 Build 6002
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Member Server
OS Build Type:             Multiprocessor Free
Registered Owner:          Admin
Registered Organization:   -
Product ID:                55041-339-7818202-76771
Original Install Date:     04-Aug-08, 3:15:18 PM
System Boot Time:          21-Jan-14, 3:58:47 PM
System Manufacturer:       HP
System Model:              ProLiant BL460c G1
System Type:               x64-based PC
Processor(s):              2 Processor(s) Installed.
                           [01]: Intel64 Family 6 Model 23 Stepping 6 GenuineIntel ~3000 Mhz
                           [02]: Intel64 Family 6 Model 23 Stepping 6 GenuineIntel ~3000 Mhz
BIOS Version:              HP I15, 02-May-11
Windows Directory:         C:\Windows
System Directory:          C:\Windows\system32
Boot Device:               \Device\HarddiskVolume1
System Locale:             en-us;English (United States)
Input Locale:              en-us;English (United States)
Time Zone:                 (GMT+03:00) Kuwait, Riyadh
Total Physical Memory:     16,381 MB
Available Physical Memory: 8,320 MB
Virtual Memory: Max Size:  21,821 MB
Virtual Memory: Available: 13,722 MB
Virtual Memory: In Use:    8,099 MB
Page File Location(s):     C:\pagefile.sys
Domain:                    DOMAIN.COM
Logon Server:              N/A
Hotfix(s):                 157 Hotfix(s) Installed.
                           [01]: {47740627-D81D-4A45-A215-03B075A18EC7}
                           [02]: {3D019598-7B59-447A-80AE-815B703B84FF}
                           [03]: {A8E86480-A9C1-4414-8AA2-B05A485C82F0}
                           [04]: {C444285D-5E4F-48A4-91DD-47AAAA68E92D}
                           [05]: {DB33A524-845E-4855-9E90-A5619BCDD527}
                           [06]: {ECC3A660-90E3-4A89-9FE8-F8B3C633B12E}
                           [07]: {65AFCB03-3111-47E2-B1ED-198D6B0BC96E}
                           [08]: {F5E29D9D-519A-36C7-87E3-9A22A8180B1B}
                           [09]: KB971513
                           [10]: KB971512
                           [11]: 944036
                           [12]: 982861
                           [13]: KB960362
                           [14]: KB2079403
                           [15]: KB2117917
                           [16]: KB2141007
                           [17]: KB2160329
                           [18]: KB2183461
                           [19]: KB2207566
                           [20]: KB2286198
                           [21]: KB2296011
                           [22]: KB2296199
                           [23]: KB2305420
                           [24]: KB2345886
                           [25]: KB2347290
                           [26]: KB2387149
                           [27]: KB2388210
                           [28]: KB2416400
                           [29]: KB2416470
                           [30]: KB2419640
                           [31]: KB2423089
                           [32]: KB2436673
                           [33]: KB2442962
                           [34]: KB2443685
                           [35]: KB2447568
                           [36]: KB2467659
                           [37]: KB938464
                           [38]: KB942288
                           [39]: KB948609
                           [40]: KB948610
                           [41]: KB949189
                           [42]: KB950762
                           [43]: KB950974
                           [44]: KB951066
                           [45]: KB951698
                           [46]: KB951978
                           [47]: KB952004
                           [48]: KB952287
                           [49]: KB953733
                           [50]: KB954155
                           [51]: KB954459
                           [52]: KB955020
                           [53]: KB955069
                           [54]: KB955302
                           [55]: KB955430
                           [56]: KB955839
                           [57]: KB956250
                           [58]: KB956572
                           [59]: KB956744
                           [60]: KB956802
                           [61]: KB957097
                           [62]: KB957200
                           [63]: KB957321
                           [64]: KB957388
                           [65]: KB958481
                           [66]: KB958483
                           [67]: KB958623
                           [68]: KB958624
                           [69]: KB958644
                           [70]: KB958687
                           [71]: KB959130
                           [72]: KB959426
                           [73]: KB960225
                           [74]: KB960803
                           [75]: KB961371
                           [76]: KB961501
                           [77]: KB967190
                           [78]: KB967723
                           [79]: KB968389
                           [80]: KB968537
                           [81]: KB969058
                           [82]: KB969897
                           [83]: KB969897
                           [84]: KB969947
                           [85]: KB970238
                           [86]: KB970430
                           [87]: KB970653
                           [88]: KB971468
                           [89]: KB971486
                           [90]: KB971557
                           [91]: KB971657
                           [92]: KB971737
                           [93]: KB971930
                           [94]: KB971961
                           [95]: KB972036
                           [96]: KB972270
                           [97]: KB972636
                           [98]: KB973346
                           [99]: KB973507
                           [100]: KB973525
                           [101]: KB973565
                           [102]: KB973687
                           [103]: KB973917
                           [104]: KB974145
                           [105]: KB974318
                           [106]: KB974455
                           [107]: KB974470
                           [108]: KB974571
                           [109]: KB975364
                           [110]: KB975467
                           [111]: KB975517
                           [112]: KB975560
                           [113]: KB975759
                           [114]: KB975929
                           [115]: KB976098
                           [116]: KB976264
                           [117]: KB976470
                           [118]: KB976662
                           [119]: KB976749
                           [120]: KB976768
                           [121]: KB976772
                           [122]: KB977165
                           [123]: KB978251
                           [124]: KB978262
                           [125]: KB978542
                           [126]: KB978601
                           [127]: KB978886
                           [128]: KB979099
                           [129]: KB979306
                           [130]: KB979309
                           [131]: KB979482
                           [132]: KB979687
                           [133]: KB979688
                           [134]: KB979899
                           [135]: KB979910
                           [136]: KB980182
                           [137]: KB980195
                           [138]: KB980218
                           [139]: KB980232
                           [140]: KB980248
                           [141]: KB980302
                           [142]: KB980436
                           [143]: KB980842
                           [144]: KB981322
                           [145]: KB981332
                           [146]: KB981793
                           [147]: KB981852
                           [148]: KB982132
                           [149]: KB982214
                           [150]: KB982519
                           [151]: KB982664
                           [152]: KB982666
                           [153]: KB982799
                           [154]: KB983589
                           [155]: KB948465
                           [156]: KB960568
                           [157]: KB968930
Network Card(s):           1 NIC(s) Installed.
                           [01]: HP NC373i Multifunction Gigabit Server Adapter
                                 Connection Name: Local Area Connection 2
                                 DHCP Enabled:    No
                                 IP address(es)
                                 [01]: x.x.x.x
                                 [02]: fe80::f494:43c2:7d90:e774
Hyper-V Requirements:      VM Monitor Mode Extensions: No
                           Virtualization Enabled In Firmware: No
                           Second Level Address Translation: No
                           Data Execution Prevention Available: No

Things I have tried:

1. I tried to backup manually to external HDD using wsb snap-in, but it has failed in the same way.

2. Stop and re-add protection.

3. I have researched the error, some results suggest that some bad sectors might exist, however, when I run the command, it forces me to schedule the command on next boot. when I reboot, it loads windows after that gives a message "Cannot open the volume for direct access"

How to end this loop? please help. Thanks for considering my question ...

Environment:

Windows Server 2012 R2 Essentials running in VirtualBox in a Windows 7 host. Networking is configured and works fine.

Background:

My only backup needs are to copy the contents of two folders to a NAS folder every day at 2 AM.

I configured a backup schedule in Windows Server Backup (wbadmin) to a network location which is hosted as a Samba share on a Synology NAS.

For authentication, I created a backup user which has the same username and password as a user on the Samba share, with permission to read and write the backup folder. I added this user to the Backup Operators group.

Problem:

When I try to run the Backup Once operation to test my backup, I get the following error message:

"Windows Backup cannot read the backup destination."

What I've tried:

I verified that the location is directly accessible in Windows by copying and pasting the address from the Windows Server Backup destination into explorer. Providing the backup user credentials opened the location and creating/reading files worked fine.

Adding the backup user to the Administrators group did not have an effect.

Update 2014-02-18

I checked the backup destination and was surprised to find that the scheduled backup actually completes successfully.However, Backup Once always results in the above error message. So the problem is confined to the "Backup Once" operation.

Win Srv 2012 Essentails backup runs fine for several days, then hangs and adds "new virtual drives # 6 and #7 or similar". At the same time the server manager hangs with loading storage pool and further disk/drive - information.

Completely disconnecting / shut off and reconnecting the external USB-backup drive stops the error with an unsuccessful backup. 

Hi

We are having issues on one of our Windows 2008 servers with Windows Backup. The backups are failing on Sunday night through to Thursday night with the error "The system cannot find the file specified". However, the backup on a Friday and Saturday night run fine.

The backup starts at 10pm and the last member of staff leaves site at 6pm so there is no-one on the system using the files. I have also ran a chkdsk on each volume and they do not have any errors. I have also recreated the backup jobs without success.

I've about ran out of ideas and I'm hoping someone may be able to offer some ideas.

Thanks in advance

Rob

Hello,
        We are taking wbadmin backup in local drive using the network share (i.e. sharing a folder in the local drive) and using "wbadmin start backup -backupTarget:\\%computername%\wbadminbackup -allcritical -quiet"

But the backup had failed. Following errors was in Wbadmin GUI.

The specified network name is no longer availabe.
The backup of the volume was stopped before the backup started running

The event viwer has following entry
 "Backup Started $$$$  failed with following error code '2147942464' "

I checked Wbadmin had created the WindowsImageBackup folder and some VHD file inside the  the network share


Any idea ?

Thanks
With Regards
Hemant.

I set up a backup on my Windows 2012R2 Essentials server using the dashboard and this has been running (logs show so) for a couple of months. I thought I'd try to check out what I'd set to back u, maybe try a restore and maybe change the external disk.

However, when I go to the dashboard, devices select the server and the click on "Restore files or Folders" or "Customise Backup for this server" the "Set Up Server Backup" window pops up with "Loading Data. This can take a few minutes" and the ... just stays there. For ever.

I've rebooted, run chkdsk, but cannot get past this point (I have to shut down the Dashboard to clear it)

I have a service pack from HP to apply but I don't want to do anything until I know I have  agood backup.

Hello.

I am trying to create a powershell script that will check the last 3 backups taken om my domain controllers and send the result of that to chosen recipients with e-mail.

 The main problem i have noticed is that when i run get-wbjob -previous 3 command it will only generate the result on the local server. Is there any way to query cross server or will i have to create a scheduled task for each DC?

Thanks

/Lee

I have taken over in a new role and found that while backups were being conducted on a regular basis, the backup solution was not VSS aware and almost 1TB of log files had accrued since Exchange was installed in 2011!

I have implemented the use of the Windows Server Backup utility on the Windows 2008 R2 server that hosts Exchange 2010.

After verifying that I had achieved consistency within the mail databases, I scheduled a Full VSS Backup to run every night to a series of externally attached USB hard drives, and was happy to see that each days Exchange log files are now being flushed after each back up.

However, when reviewing the backup reports within Windows Server backup utility, I note that each backup following the initial FULL backup to each hard drive is referred to as Incremental? I was under the impression that in specifying a VSS FULL Backup, any existing backup found within the WindowsImageBackup folder on the backup media would be overwritten in it's entirety but it seems that the existing Full backup is instead being 'modified' by each subsequent backup?

Also, the collective size of the .vhd files created on the backup media is significantly larger than the space shown within Windows Explorer as 'used' on each of the volumes backed up?

Could someone please explain these apparent anomalies? - Thanks

      Our company uses Windows Server Backup to back up our Windows 2012 Server.  We back up the host component and the two virtual machines on the server.  Every time I install windows updates on our server my backup jobs stop working and I get a VSS error.  In order to get backup working again, I have to recreate my backup job.  In order to do this I have to attach all the backup drives to the computer at the same time.  This has been an issue all the way back to when the server was first installed.  At that time the person who installed Windows Server talked to Microsoft.  Microsoft said the problem would be fixed in the first service pack which they ended up never releasing.  I have looked online, but haven’t found any information on these issues.  Are there any fixes for these two problems?

I'm having the following problem. Our backups are failing with the following error:

In the backup logs, I find:

Error in backup of D:\ during write: Error [0x800700a1] The specified path is invalid.
Error in backup of D:\Perforce\ during write: Error [0x800700a1] The specified path is invalid.
Error in backup of D:\Perforce\Database\ during write: Error [0x800700a1] The specified path is invalid.
Error in backup of D:\Perforce\Database\p4s.exe during write: Error [0x800700a1] The specified path is invalid.

In the event viewer, I find:

And on the command line, wbadmin returns:

...
Found (41) files.
The backup operation stopped before completing.
Summary of the backup operation:
------------------
The backup operation stopped before completing.
Detailed error: Element not found.
The backup of the system state failed [5/24/2010 5:23 PM].
Log of files successfully backed up:
C:\Windows\Logs\WindowsServerBackup\Backup-24-05-2010_14-51-56.log

Log of files for which backup failed:
C:\Windows\Logs\WindowsServerBackup\Backup_Error-24-05-2010_14-51-56.log

The operation ended before completion.
Element not found.
ERROR(-3): Backup failed!

This is very frustrating. The more I use Windows built-in backup the more fragile it seems to be. The D drive is a local drive and the path is valid.  Running check disk finds no problems.  The drive is mostly empty. I tried with and without the anti-virus software, same problem.  There are no other server errors to indicate a problem with the drive or the path. I ran vssadmin list writers, and none of them returned any errors.  Why would the backup return an invalid path error, for a path that is valid? Any help would be greatly appreciated.

Thanks much,
James.