Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Files not backing up & Calling DoSnapshotSet stall #22

Open
SINEKT opened this issue Mar 1, 2011 · 2 comments
Open

Files not backing up & Calling DoSnapshotSet stall #22

SINEKT opened this issue Mar 1, 2011 · 2 comments

Comments

@SINEKT
Copy link

SINEKT commented Mar 1, 2011

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!

@candera
Copy link
Owner

candera commented Apr 19, 2011

Did we ever make any progress on resolving this question?

@SINEKT
Copy link
Author

SINEKT commented Apr 19, 2011

I am sorry, but I currently don't have access to the computers in question more often than a couple of hours a month. Unfortunately, these are the computers of one of our customers and we only perform maintenance there once a month, so that is the only moment when I can test stuff. If one of the systems were at home or at the office, the problem would have been gone by now. Annoying, I know.

But thanks anyway for your help ! ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants