- Thread Author
- #1
This is a long message, beware.
I recently installed build 7000 on my machine, but I've been having trouble with the built-in backup software.
The short version of the issue is that backups of C:\ no longer work.
The long version:
Windows successfully creates a shadow copy, but then fails at 6% with the error message "Backup failed. Windows Backup had to skip all drives included in backup. Make sure that the drives are plugged in and working correctly. (0x810000FF)." Yes, the drives are plugged in and working correctly.
In Event Viewer, there is a somewhat more useful error message: "Drive C:\ was not backed up. The error is: The filename, directory name, or volume label syntax is incorrect. (0x8007007B)."
I have my backup configured to backup the entire C:\ drive only. If I configure it to backup D:\ and not C:\, and make no other configuration changes, it works. However, when I switch it back to C:\, it doesn't. I think there is either some corruption or confusion within my system. I've tried deleting the <systemname> directory from the backup location, so it has no knowledge of having ever done another backup.
After initially installing, I used gparted under Ubuntu to resize the primary C:\ partiiton and increase its size. Part of this resize involved moving the partition "left" on the disk, which caused my system to be unable to boot. However, I used the repair feature on the DVD to get it to boot again. The system ran a chkdsk as well and fixed some things. But a chkdsk now comes back clean.
I think somewhere in the Windows Backup configuration or in the partition table somewhere, it's looking at the old start location for the partition and getting confused. But it should be able to be fixed because everything else works fine.
So, if you've read this far, here's my two questions:
1) Does anyone know where Windows Backup stores it configuration so I can let it clear it out and restart?
2) Perhaps more importantly, does anyone know how to get Windows Backup to increase its logging or somehow give me more details about what it's doing when it fails at 6%?
Thanks.
I recently installed build 7000 on my machine, but I've been having trouble with the built-in backup software.
The short version of the issue is that backups of C:\ no longer work.
The long version:
Windows successfully creates a shadow copy, but then fails at 6% with the error message "Backup failed. Windows Backup had to skip all drives included in backup. Make sure that the drives are plugged in and working correctly. (0x810000FF)." Yes, the drives are plugged in and working correctly.
In Event Viewer, there is a somewhat more useful error message: "Drive C:\ was not backed up. The error is: The filename, directory name, or volume label syntax is incorrect. (0x8007007B)."
I have my backup configured to backup the entire C:\ drive only. If I configure it to backup D:\ and not C:\, and make no other configuration changes, it works. However, when I switch it back to C:\, it doesn't. I think there is either some corruption or confusion within my system. I've tried deleting the <systemname> directory from the backup location, so it has no knowledge of having ever done another backup.
After initially installing, I used gparted under Ubuntu to resize the primary C:\ partiiton and increase its size. Part of this resize involved moving the partition "left" on the disk, which caused my system to be unable to boot. However, I used the repair feature on the DVD to get it to boot again. The system ran a chkdsk as well and fixed some things. But a chkdsk now comes back clean.
I think somewhere in the Windows Backup configuration or in the partition table somewhere, it's looking at the old start location for the partition and getting confused. But it should be able to be fixed because everything else works fine.
So, if you've read this far, here's my two questions:
1) Does anyone know where Windows Backup stores it configuration so I can let it clear it out and restart?
2) Perhaps more importantly, does anyone know how to get Windows Backup to increase its logging or somehow give me more details about what it's doing when it fails at 6%?
Thanks.