I did Google the error code and got lots of information about shadow
volumes and reparse etc, but very little that actually helped isolate
the real cause of the error.
I find it rather amazing that I should get any this type of system error
with a newly installed system - it's only just over a month old.
"It" (meaning Win7) created the shadow copy and then can't read it,
can't suggest possible causes, and can't even tell me what partition was
being processed when the error was encountered. How "user friendly" is that?
"It" implies that taking backups is really simple and straightforward,
but when it goes wrong gives absolutely no assistance in fixing it.
I've now started using Acronis True Image Home V11, which is apparently
working fine.
If I figure out what was wrong I'll post back, but it's pretty
impenetrable stuff.
(Yes, I know that some people despise "top posting", but I hate
ploughing down through stuff I've already read in order to find the most
recent addition.)
--
Regards, Gary Wooding
(To reply by email, change gug to goog in my address)
On 23/12/2011 09:47, Jeff Layman wrote:
> On 22/12/2011 16:24, Paul wrote:
>> Jeff Layman wrote:
>>> On 22/12/2011 08:13, lemel_man wrote:
>>>> I've recently installed Win7 Ultimate X64 which I dual boot with, but
>>>> seldom use, my old XP Pro+SP3 system.
>>>> I have a single 1TB HDD which is divided into 4 NTFS partitions; W7 on
>>>> one, XP on another, and two for common data.
>>>> I've tried to use Win7 Backup (to an external 1TB drive) twice, but
>>>> both
>>>> times it has failed with the following error message...
>>>>
>>>> "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."
>>>> The error code is 0x81000037
>>>>
>>>> I've checked the event logs, but they only repeat the above info. I
>>>> have
>>>> no idea what volume is causing the error, or how to fix it.
>>>> Any ideas please?
>>>>
>>>
>>> Might be worthwhile seeing if the free backups (such as EaseUs and
>>> Macrium) give you the same message. If they work ok, forget W7 backup.
>>> If they don't work either, just uninstall them (but you'll have to
>>> solve the W7 problem).
>>>
>>> Also, have you tried backing up each partition separately to see which
>>> is/are causing the problem?
>>>
>>
>> Isn't Macrium also VSS based ? If so, it should fail the same way.
>>
>> Don't know about EaseUs. The thing is, to back up C:, you either
>> need to "do the backup from DOS" (to avoid the busy file problem),
>> or use VSS to aid the backup process while Windows is still running.
>> I haven't heard of any, third solutions.
>>
>> Backing up data only partitions, is a lot easier, with lots more
>> choices of solutions.
>>
>> The fact that VSS exists, has made backup program designers pretty
>> lazy. If they all glom onto VSS as a solution, and your VSS is
>> broken for some reason, then you can find a lot of trialware
>> doesn't work either.
>>
>> http://en.wikipedia.org/wiki/Shadow_Copy
>>
>
> Yes, EaseUs also uses VSS.
>
> I assume you've googled the error code. There are many causes/solutions
> for error code 0x81000037 discussed here:
> http://social.technet.microsoft.com/...3-5882dc73a383
>
>
> Hope one of them sorts out your problem.
>