I upgraded my main computer to Windows 7 Home Premium which has a C drive (500 GB) and a Raid 5 SATA array (2.7 TB) on drive D:. I tried to backup the install as an image on the D: drive and I get the following error code 0x8078002A and a comment about an I/O error and one of the backup files could not be created.
I plugged in a USB external hard drive in and it works.
This computer is part of a gigabit switched home network (the main file server), so I tried to back up one of the home computers (running W7 Professional) through the network onto a shared folder on drive D: and I get the same error. The backup gets 27% of the way through on both computers and then fails.
I have updated the Raid driver (I had to as part of the W7 install).
Any ideas or solutions on this one?
Secondly, can I copy the backup off the USB drive onto the D: drive and have a reliable backup, or will that corrupt the backup?
Thanks for your help
I get the same error code only in case of activating the box for creating an image for C (I am using an external disc via an USB connection for the back-up). Not activating this box allows normal back-up. I was not able to find a solution for this problem (image creation) in web. But I found a lot of some complaints. Maybe this is an unresolved problem?
I am having the same issue.
Were either of you able to resolve your problems?
I have a feeling this may be related to the default "Power Options". Shutting down drives, devices after some time, etc. So I am changing power plans and running the same utility for research on it.
I have this issue. Backing up creating a system disk of C: and E:. C: is a Solid State Disk. Backing up the image to a WD 3T USB3.0 notebook.
Tried turning off and deleting system restore points, disabled virus checkers, running check disk. All partitions by the way are NTFS.
I was having this same issue on Windows 7 Ultimate with a new Western Digital My Book Essential 3TB. I formatted the drive right after I got it with NTFS. After looking around, finding this thread, and then looking some more, I found a solution on the WD Knowledge Base that worked. It is answer ID 6618 and is titled Error: 0x8078002A occurs when backing up to a 2.5 or 3.0 TB drive in Windows 7 Backup and Restore.Immediately after running the WD Quick Formatter tool and using the Factory Default configuration I attempted a backup with only the system image selected and it worked without error. I then ran another backup with the system image as well as some user data files selected and that, too, completed successfully.FWIW, here are the results of running
fsutil fsinfo ntfsinfo f:on my drive (which is loaded as F:)
NTFS Volume Serial Number : 0x4610ce4610ce3ca5 Version : 3.1 Number Sectors : 0x000000015d4b97de Total Clusters : 0x000000002ba972fb Free Clusters : 0x0000000027cd46f6 Total Reserved : 0x0000000000000000 Bytes Per Sector : 512 Bytes Per Physical Sector : 4096 Bytes Per Cluster : 4096 Bytes Per FileRecord Segment : 1024 Clusters Per FileRecord Segment : 0 Mft Valid Data Length : 0x0000000000040000 Mft Start Lcn : 0x00000000000c0000 Mft2 Start Lcn : 0x0000000000000002 Mft Zone Start : 0x00000000000c0040 Mft Zone End : 0x00000000000cc840 RM Identifier : F3F52DD1-A72B-11E0-8FC2-005056C00008If you're using a WD external drive and getting this error with backups, I recommend trying this solution and posting your results here.
However, is anyone aware if Microsoft is building a fix so that drives with 4K logical sector sizes are not an issue? This error is going to effect more people over time with the increasing number of 2.5 TB and larger hard drives on the market.
Thanks RayD for the tip. I unfortunately can not implement the fix as suggested by RayD as I have too much data and can not reformat my backup external hard drive.
Have tried all means of undertaking a full back up in Windows 7 using an Omega 1TB and the same error message 0x8078002A using MS Backup. However by backing up separate files not exceeding 500 MB all found entirely satisfactory. Omega say they will advise me when the solution is resolved, but it is now almost two years and no answer has been forthcoming. Can I say that it is not possible to resolve this problem, which will get worse with the increase of large backup drives. Surely somebody must have an answer or must we all go back to a larger number of smaller backup hard drives.
I await with interest if a solution can be found.