HoboCopy problems

[Alexe Emil]

 Hi there,


 I am using Hobocopy on a few computers and quite frankly it's a good piece
 of software, it's simple, small and does a lot, and it's certainly on my
 goodies list.

 The problem is that it acts funny on some computers, and I wonder if you
 could help me with this. Actually, it seems more of a VSC service problem,
 but I figured since you wrote the code you should know a bit more about
 Volume Shadow Copy than I currently do.

 This is what happens on one of the PCs:

 First issue, it seems not to be able to back up some MSSQL database files
 and folders. I get something like this, with Verbose set to 4:

 Component X is named XXXXXXXX, has a path of COMPUTER-NAME, and is not
 selectable for backup. 0 files, 0 databases, 2 log files.

 Also:

 Component X has name XXXXXXXXXX, path COMPUTER NAME, is not selectable for
 backup, and has parent (no parent).

 Then, after a few dozen lines, it stalls at Calling DoSnapshotSet forever,
 goes no further.

 I have noticed that when requested to stop, manually, or via command or
 batch file, the VSC service hangs in a "stopping" state, making it
 impossible to be accessed until the computer is restarted.


 I will be glad to provide more info if you can help me with this.


 Thanks!

[Craig Andera]

>  I am using Hobocopy on a few computers and quite frankly it's a good piece
>  of software, it's simple, small and does a lot, and it's certainly on my
>  goodies list.

Thank you! I wrote it for myself, and I'm constantly surprised by how
many people also find it useful. But that's cool.

>  The problem is that it acts funny on some computers, and I wonder if you
>  could help me with this. Actually, it seems more of a VSC service problem,
>  but I figured since you wrote the code you should know a bit more about
>  Volume Shadow Copy than I currently do.

Heh. That may not be a safe assumption. But I'll try.

>  This is what happens on one of the PCs:
>
>  First issue, it seems not to be able to back up some MSSQL database files
>  and folders. I get something like this, with Verbose set to 4:
>
>  Component X is named XXXXXXXX, has a path of COMPUTER-NAME, and is not
>  selectable for backup. 0 files, 0 databases, 2 log files.
>
>  Also:
>
>  Component X has name XXXXXXXXXX, path COMPUTER NAME, is not selectable for
>  backup, and has parent (no parent).
>
>  Then, after a few dozen lines, it stalls at Calling DoSnapshotSet forever,
>  goes no further.
>
>  I have noticed that when requested to stop, manually, or via command or
>  batch file, the VSC service hangs in a "stopping" state, making it
>  impossible to be accessed until the computer is restarted.

Very strange. Have you tried the interim version of hobocopy that I
posted on the github site last week, or are you using 1.0? I ask
because that version contains some fixes around how I interact with
asynchronous VSS API calls. I'm not sure that it would address your
problem, but it might be worth a try. Note that you'll need the
updated vcredist to run the newer version.

[sin...@yahoo.com]

I will give it a try, though it might take a couple of weeks until I
get to those computers, 'cause they're at one of my customers. The
only XP machine I could test stuff on is at the office, where HoboCopy
work just fine.

[Craig Andera]

No hurry from my perspective. :) As you can tell from how much I
charge for it, hobocopy is sort of a spare-time thing for me.

[tord.b...@gmail.com]

Hi Craig.

I use your Hobocopy utility at a customer of mine and it seems to do the job perfectly.

However, I use the Hobocopy x64  and x86 versions from 2008  as they are both considered to be stable ("last modified" info on the .exe file says 23.06.2008 09:27).

Can you tell me the difference between these and the latest "unstable" version found here?

https://github.com/candera/hobocopy/downloads

Should I be using the latest 64bit and 32bit versions from 2011?

Thanks,

Tord Bergset

[Craig Andera]

Hi Tord. I'm glad you find the tool useful. To be 100% honest, I don't
remember all the differences between the stable and unstable versions.
I seem to recall chasing a few bugs that were giving some people
trouble, and introducing some fixes into the unstable version. Really,
it wasn't meant to mean "unstable" in the sense of "broken", but more
along the lines of "not as fully tested".

FWIW, I ran the "unstable" version myself until I stopped using
hobocopy altogether.

> --
> You received this message because you are subscribed to the Google Groups
> "hobocopy" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to hobocopy+u...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

[tord.b...@gmail.com]

Craig,

Interesting...so what made you stop using the program? You wouldn't believe all the things I am using it for .-)

Any other free and better/newer command line tools out there you can recommend as a substitute?

/Tord

[Craig Andera]

I stopped using it because I realized hobocopy does two things: make a
shadow copy and then copy files out of it. The copying part is pretty
crappy compared to alternatives like rsync or robocopy (hobocopy's
incremental copy, for example, is pretty broken), so I tossed that bit
and kept the shadow copy bit. That's ShadowSpawn
(https://github.com/candera/shadowspawn). So now I run rsync under
shadowspawn instead.

Another reason is that I find myself moving away from Windows and
towards other operating systems.