Error in backup 0x807800C5

Es ist so typisch von Microschrott, dass sie es selbst nach Jahren NICHT schaffen, eine funktionierende Imagesicherung ihres eigenen Systems hinzubekommen :(

Der Abbruch bei 57% erfolgt nur, wenn auch ein Systemabbild erstellt wird, die Sicherung der Dateien und des Windows-Verzeichnisses funktioniert dagegen (meist) zuverlässig.

Ich empfehle zur Imagesicherung der Systempartition Software von Drittanbietern, konkret "Drive Snapshot", das genial einfach und absolut zuverlässig funktioniert!!!

www.drivesnapshot.com

I also received this error.

finally found the following solution:

http://superuser.com/questions/508932/windows-backup-failed-with-error-0x807800c5

--

FYI, instead of adding EVERYONE permissions, try adding SYSTEM permissions. I was getting error 80070005 when I was trying to backup to a network share on a local drive (the only way to backup to a subfolder). Although giving full access to EVERYONE on both the folder and the share was sufficient to stop the error, such access was unacceptable. I started to narrow down the accounts, and it turns out that giving the SYSTEM account full access is sufficient to allow the backup to proceed, along with the actual user account you want to use for the backup. – Triynko Dec 15 '14 at 23:26

--

by adding system with full permissions it looks like the issue is solved.

I have found another work around that may work with some NAS.  Instead of pointing the backup folder to a network share, I created a VHD on the network share and mount the VHD as a local drive.  Here is what I did:

1. Start Windows 8 Disk Management, under Action, select create VHD.   Put the VHD in the NAS folder where the backup will be stored.   Select either VHD or VHDX (usable only under Windows 8 or Windows Server 2012).   Select Dynamically Expanding type and the appropriate size.  For mine, I created a 300GB VHDX.
2. A new disk will be available under Disk Management and requires initialization, formatting and letter assignment.  After this, you can perform a backup pointing to this drive and see if it works.

To mount the VHD every time the system starts up, create a scheduled task that runs the following windows command script:

1. START "Diskpart" /WAIT %SystemRoot%\System32\Diskpart.exe /s %SystemRoot%\CMD\AttachBackupVHD.script
2. The AttachBackupVHD.script contains the following DISKPART command:

SELECT VDISK FILE="NAS location\Backup.vhdx"

ATTACH VDISK

EXIT

I tested this on an Iomega/Lenovo NASix201 and Western Digital DX4000 (Windows Storage Server 2008 Essential) and the backup worked on both devices.  Backup to ReadyNas devices did not work as the connection to the VHD was lost during backup.  Your mileage may vary.

My tests indicated that it is not just any Linux or Unix based NAS devices that are having problems.  Prior to adding a new Windows 8 Pro computer, I have four other Windows 7 computers being backed up to a share on a Western Digital Sentinel DX4000, which is a Windows Server 2008 Storage device.  All the Windows 7 computers can be backed up without any issues, including the system images.  On my new Windows 8 computer, the back up will fail when the destination is on that share.  It will work if I point the destination to locally attached USB hard drive.

To make matter worse, once I configured Windows 7 backup on my Windows 8 computer, I would have to disable Windows 7 backup before I could use the File History feature.   I don't understand why we cannot have two types of backups for redundancy.

DER LINK zur Frage an Windows:

http://answers.microsoft.com/de-de/windows/forum/windows\_8-networking/windowsdateisicherung-im-netzwerk-speichen/1dac24cb-0422-4a0f-bd30-d893be9322fe

THE LINK on the issue of Windows:

http://answers.microsoft.com/de-de/windows/forum/windows\_8-networking/windowsdateisicherung-im-netzwerk-speichen/1dac24cb-0422-4a0f-bd30-d893be9322fe

LG

Thanks for posting this. I was pulling my hair out. Hard to understand why they don't support NAS servers.