So, you're right: not having errors like this is sort of the point of
hobocopy. So we should fix this!
Looking at the code, it seems to me that the copy should proceed even
if it encounters this error - file sizes are used only to print out
statistics, to a failure to compute file size is not fatal. Are you
seeing the copy terminate when you get this error?
I also have a half-baked theory that version 1.0 does not properly
wait for the snapshot to complete before starting the backup, which
might result in this the problem. Is it feasible for you to try the
unstable version? The one that's on GitHub isn't the very latest code,
but I could probably find some time today to push a build of the very
latest stuff if you'd like to give it a try.
Sorry about that: the new home of hobocopy is
http://github.com/candera/hobocopy. You can go straight to the
downloads page at https://github.com/candera/hobocopy/downloads. I did
make an attempt to point people to the new site from the SF one, but
apparently didn't do so good a job.
Can you add the /verbosity=4 switch and see if the additional info
tells us anything about where it's stopping?
Also, do you have TrueCrypt installed?
OK. Can you share the last few lines of the output at verbosity 4?
> I'm not using TrueCrypt or any form of encryption.
Sometimes even having it installed can cause issues with the Volume
Shadow Service. I'd also be interested to see the output of running
"vssadmin list providers", "vssadmin list shadows", "vssadmin list
shadowstorage", "vssadmin list volumes" and "vssadmin list writers".
Hmm. No real help there.
>
> Here's the other output you requested:
> [C:\]vssadmin list writers
> vssadmin 1.1 - Volume Shadow Copy Service administrative command-line
> tool
> (C) Copyright 2001-2005 Microsoft Corp.
So, these bits here look interesting:
> Writer name: 'System Writer'
> Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
> Writer Instance Id: {2850eaae-45f7-4e9f-8365-02618a57239f}
> State: [5] Waiting for completion
> Last error: No error
>
> Writer name: 'MSSearch Service Writer'
> Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
> Writer Instance Id: {8a85cdcd-dbda-4773-8f8f-e6705272767c}
> State: [5] Waiting for completion
> Last error: No error
>
> Writer name: 'WMI Writer'
> Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
> Writer Instance Id: {309ca2a6-64db-46f8-8eac-4f1a412034d1}
> State: [5] Waiting for completion
> Last error: No error
The "waiting for completion" part is what catches my eye. Did you run
'vssadmin list writers' while hobocopy was running?
I'll admit I'm a bit puzzled by this one: VSS is pretty complicated
and I still don't understand it that well. But I'm happy to keep
working on it until we find you a solution; just bear with me.
One thing I'd like to know is what process has that file open. It's a
shadow copy, so nothing should. You can download the handle utility
from http://technet.microsoft.com/en-us/sysinternals/bb896655, then
fire up hobocopy and run something like this:
handle Thunderbird
That should give us a list of processes that are accessing files with
Thunderbird in their names. We're particularly interested in anything
that isn't hobocopy.exe.
If that doesn't turn up any smoking gun, I have a few other questions
and things to try:
* Does this only happen with incremental backups, or do you see it
with full backups, too?
* Do you have antivirus software installed?
* If so, does this still happen if you disable it?
* If you reboot, does the problem go away?
* If you run chkdsk /r c: and reboot, does the problem go away?
Huh. That's a little weird - with hobocopy not running, I don't see
why those writers would be doing anything. Do you know if there is any
other backup software running on the machine? Something else your
company mandates, perhaps?
>> That should give us a list of processes that are accessing files with
>> Thunderbird in their names. We're particularly interested in anything
>> that isn't hobocopy.exe.
>
> Just thunderbird.exe and hobocopy.exe. If hobocopy isn't running, then
> it's just Thunderbird.
And does Thunderbird have files open with paths that look like
\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy4\Documents and
Settings\gperrow\ApplicationData\Thunderbird\Profiles\yz85hgzm.default\abook.mab?
Or does Thunderbird have them open on C:\ ? I would assume the latter.
If it's the former, then that's rather puzzling - only hobocopy should
have files in the shadow copy open.
>> * Does this only happen with incremental backups, or do you see it
>> with full backups, too?
>
> Only incremental backups.
Hmm. I've had a sneaking suspicion for some time that I'm not handling
incremental backups correctly. I find the documentation around the API
almost totally impenetrable, though.
I've gone ahead and built two new versions of hobocopy. You can find them here:
http://dl.dropbox.com/u/451150/hobocopy-master.zip
http://dl.dropbox.com/u/451150/hobocopy-29.zip
If you don't mind, I'd love to have you try each of them. The master
one is the latest code, including all the bugfixes I've made to date.
So it's newer than the unstable one on github. The -29 one is one I
just created that changes the code to always use the VSS_BT_FULL flag,
even for incremental backups. You'll still get an incremental backup,
since I filter by file modification times, but VSS will act like it's
a full backup.
>> * Do you have antivirus software installed?
>
> Yes, McAfee VirusScan Enterprise, which I cannot disable due to stupid
> company IT policies. I can uninstall it, which I plan to do on Monday,
> so if you think that's part of the problem, I can wait until then and
> try again.
I always suspect antivirus when there are weird file problems. But I
don't have any specific reason to think that's it, no.
>> * If you reboot, does the problem go away?
>> * If you run chkdsk /r c: and reboot, does the problem go away?
>
> No and no. Actually, I just ran chkdsk /f C:, so I'll try /r.
/f versus /r shouldn't make any difference as far as I know. I'm
grasping at straws a bit, and was wondering whether it might not be a
disk corruption issue. The fact that it only fails during incremental
copies suggests to me that this is a hobocopy bug, though. We'll know
more if you get a chance to try those two versions I just posted.
Thanks for your patience!
OK. Long shot anyway.
> Nope, Thunderbird only has C:\ files.
OK. Would have been puzzling if it did.
> Tried 'em both, same result.
Wow - that's *really* confusing. Other than selecting which files to
copy, there shouldn't be any difference between full and incremental
in the 29 branch. But I wrote this code almost five years ago, and
have only recently started actively maintaining it, so it's entirely
possible I'm missing something.
> If I get bored this afternoon or tomorrow, I may try downloading the
> hobocopy code and see if I can build and debug it.
That would be really helpful, so I hope you get bored. :)
It should be as easy as cloning the repo and then running the
build.cmd from within a VS2010 command prompt. Then just add a /debug
switch to hobocopy and it will trigger a breakpoint at startup, which
should let you attach a VS2010 instance. The only caveat is that
build.cmd creates the release builds, so you might want to use a
VS2010 build instead.
The change I made to use VSS_BT_FULL is on the
29-always-use-full-backup branch if you want to check that out.
Let me know what you find: I'm not giving up on this one yet.
Here's [1] the updated version. I pushed the code on the
29-always-use-full-backup branch, too. Again, I really appreciate you
taking the time to give this a try.
[1] http://dl.dropbox.com/u/451150/hobocopy-29-20110503-01.zip
On Tue, May 3, 2011 at 10:15 PM, Craig Andera <can...@wangdera.com> wrote:
>>> Right, that makes sense. Nice call. I can make that change.
>>
>> Does that mean I get a cut of all the hobocopy profits? :-)
>
> Haha. You can have 50% of the *revenue*, even. :)
>
>>> Huh. Again, very strange: the only process that should have a handle
>>> open is hobocopy. But AFAIK, processes don't block themselves. I'll
>>> take a look at that and see if I can figure anything out. Maybe we can
>>> add some sort of retry functionality.
>>
>> All I can think of is that Windows 7 does things slightly differently
>> than Vista, but I assume you've done testing on Windows 7 already.
>>
>> Let me know if I can help further.
>
> From your description (since I can't repro), it looks like the failure
> comes during a call to CreateFile. At a guess, *something* is grabbing
> that file for a brief time. Not sure what, though: it makes no sense
> that a piece of software would consistently lock a file in a
> newly-created shadow copy.
>
> I've got a few minutes to hack tonight. I'll try throwing together
> something on a branch that retries the CreateFile five times on some
> interval. If you can give it a try when I'm done, I'd appreciate it.
>
> Thanks again for your assistance in tracking this down. I'm not sure
> whether anyone else knows this, but hobocopy has been downloaded over
> 100,000 times over the last few years. And those are just the ones I
> know about - it's hosted on some websites that have higher Google
> juice than the project home. So your assistance has the potential to
> help a lot of people!
>
It's been a few months now, but as near as I can recall we never
resolved this issue.
I'm guessing that you're on a 64-bit machine that's not running
Windows XP: only one of those builds should actually work for you at
all. Have you tried the version that is at
http://dl.dropbox.com/u/451150/hobocopy-29-20110503-01.zip?
On Sat, Nov 12, 2011 at 4:49 AM, ahmetgns <ahme...@hotmail.com> wrote:
> I have the same problem with original poster of this thread with
> Windows 7 64-bit Home Premium version. I have tried three versions and
> for
> Release XP version > Hobocopy always stops running
> Release W2K3 , x86 > "There was a COM Failure" error appears.
> Release W2K3, x64 > "(Error number 32)." which makes me find this
> thread.
>
> If you have a new version I can give it a try also :) Thanks for the
> program.
>
> On 13 Mayıs, 18:25, Craig Andera <cand...@wangdera.com> wrote:
>> Have you had any time to follow up on this? It's been pretty busy the
>> last week, but I found some time today to work on hobocopy, so I
>> thought I'd see if there was any way I could help out.
>>
>>
>>
>> On Tue, May 3, 2011 at 10:32 PM, Craig Andera <cand...@wangdera.com> wrote:
>> > Whoops, realized I forgot to cc the group on the last few messages.
>> > Hopefully they'll forgive me.:)
>>
>> > Here's [1] the updated version. I pushed the code on the
>> > 29-always-use-full-backup branch, too. Again, I really appreciate you
>> > taking the time to give this a try.
>>
>> > [1]http://dl.dropbox.com/u/451150/hobocopy-29-20110503-01.zip
>>
"c:\Documents and Settings\user_name\AppData\Local\Microsoft\Windows
\Temporary Internet Files\Low\"
"c:\Users\user_name\Local Settings\Application Data\Microsoft\Windows
\Temporary Internet Files\Low\"
...and many more just for the same file.
I suspect this problem causes this error (Error number 32) and I don't
know which path is the original path for the file and others are just
the mirror paths. I will be glad if I can help you to solve this
problem.
On 17 Kasım, 16:00, Craig Andera <cand...@wangdera.com> wrote:
> Sorry for the delay in responding. I was travelling and am only now catching up.
>
> It's been a few months now, but as near as I can recall we never
> resolved this issue.
>
> I'm guessing that you're on a 64-bit machine that's not running
> Windows XP: only one of those builds should actually work for you at
> all. Have you tried the version that is athttp://dl.dropbox.com/u/451150/hobocopy-29-20110503-01.zip?
If there is a file with a name FILE.JPG, for instance, under
C:\Users\user\AppData\Local\Microsoft\Windows\Temporary Internet Files
\Low
then you can also find this file under
"C:\Users\user\AppData\Local\Application Data\Microsoft\Windows
\Temporary Internet Files\Low" or
"C:\Users\user\AppData\Local\Application Data\Application Data
\Microsoft\Windows\Temporary Internet Files\Low" or
"C:\Documents and Settings\user\AppData\Local\Microsoft\Windows
\Temporary Internet Files\Low" or
"C:\Documents and Settings\user\Local Settings\Microsoft\Windows
\Temporary Internet Files\Low" etc.
The real path for the file is, as I could determine" is the first one.
The others are shortcuts to those paths (and normally you cannot
access the contents of them by clicking on those shortcuts due to NTFS
permissions which Windows 7 sets the "List folder/Run file" permission
to "Not Allow" for Everyone by default) therefore HoboCopy cannot copy
content from those paths and gives the error number 32. See the
original poster's first post of this topic and notice that Graeme
Perrow wants to copy something in his personal account folder by
typing the path as "\Documents and Settings\" which is actually not a
path but just a shortcut for his "\Users\" folder.
For short, paths including "Documents and Settings", "Local Settings",
"Application Data" or similar are shortcuts to Windows 7's real paths
like "Users", "Appdata" etc. and HoboCopy can copy content only by
typing these real paths, if I could determine it correct.
When (if - ugh) I get back to hobocopy work, I'll have to verify this
and see if there's anything I can do about somehow handling this.