PDA

View Full Version : Windows backup error help



SXRguyinMA
12-19-2010, 10:40 AM
Ok, the last few times I've tried to run backup I've had this issue:


Log Name: Application
Source: Windows Backup
Date: 12/18/2010 11:59:24 PM
Event ID: 4104
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Tempest-SXR
Description:
The backup was not successful. The error is: Windows Backup failed while trying to read from the shadow copy on one of the volumes being backed up. Please check in the event logs for any relevant errors. (0x81000037).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Windows Backup" />
<EventID Qualifiers="0">4104</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2010-12-19T04:59:24.000000000Z" />
<EventRecordID>7222</EventRecordID>
<Channel>Application</Channel>
<Computer>Tempest-SXR</Computer>
<Security />
</System>
<EventData>
<Data>Windows Backup failed while trying to read from the shadow copy on one of the volumes being backed up. Please check in the event logs for any relevant errors. (0x81000037)</Data>
<Binary>37000081E30500003F0900005B090000420ED1665C2BEE174B 64529CB14610EA71000000</Binary>
</EventData>
</Event>

Now everything I've read on MS online says it's a reparse issue. Now I've no NFI what that means or is lol :?

From MS Online:


Issue 2: Error code 0x81000037

If the reparse point points to a location that contains any compressed file format (multimedia files, .zip files, and so on), you receive an error message that resembles the following:0x81000037: Windows Backup failed while trying to read from the shadow copy on one of the volumes being backed up


To work around this problem, remove this reparse point from the library, and then run the backup wizard again. To back up content for this reparse point, select the absolute path of this location from the Windows Backup configuration user interface.

Note This error may also occur if Microsoft Forefront Client Security reports a file as malware, and this file will be included in backups by Windows Backup. In this case, use Forefront Client Security to remove malware from your computer.

It's always ran fine. The only thing I can think of is I added a 4GB flash drive that's dedicated to readyboost. Think this might be it if it's trying to backup off this drive?

NightrainSrt4
12-19-2010, 11:03 AM
Sounds like you've got a/some symlinks or something. I don't think windows goes down through those links when you try to backup.

It could be the readyboost if windows is making links to what is on the flash drive, and it hits that link on the C:/ side and can't trace down to it. Try it without the flash drive. If you've got other symlinks you'd probably have to track them down if you aren't trying to back up the entire volume.

Just my initial thoughts, haven't looked things up yet, so someone might come along with better ideas.

SXRguyinMA
12-19-2010, 11:04 AM
I'm just doing a standard backup, where it backs up the libraries and then makes an image of c:

I can't find anywhere where it says what it includes, so I can't tell if it's reading from the readyboost drive

Konrad
12-19-2010, 11:05 PM
I think Windows UAC is interfering; ad-hoc USB devices and removable drives may not have the same read/write/access administrative settings as fixed drives. Not sure how you'd fix that, if it's the problem.

Or are you running any crazy third-party partition software or seeing any SMART failure warnings? I can't think of any other reasons for mismatched volumes.

You could always try different backup software.

SXRguyinMA
12-19-2010, 11:41 PM
well I've got UAC disabled, so I'm not sure. I'm going to pull the readyboost USB stick tomorrow and give it another shot

NightrainSrt4
12-20-2010, 01:12 AM
It very well could be that. Windows is probably making links between the original file and the version on the readyboost drive. When its backing up it hits the link pointing to the flash drive, but doesn't hunt down where the file on the other side of the link and instead just tosses that error. That's my theory anyway, haha.