Volume Shadow Copy Service (VSS) - Windows 7x64

[bolgasolgamolga]

At first I really want to Thank all people who work on FreeFileSync. This tool is just amazing!

I found a few topics already with the same subject but they didn’t solve my problem:

If a file is in use (in my special case a .exe file) on a network share, FreeFilesync cannot copy it. With Win XP x86 and FreeFileSync 6.3 it worked, with Windows 7 x64 it don’t work.

What I tried so far:
Start Free File Sync as Administrator.
“Reregister” the VSS as described in the HelpFile of FreeFileSync

It still don’t work. So I gave hobocopy a try https://sourceforge.net/projects/hobocopy/
Actually somehow it worked with this one. So I assume that copy locked files with VSS should work correctly with my configuration.

On the server (network share) I think Windows Server 2003 is running (actually I don’t know).

Are there any hints? Bug? Had someone success with a similar setup?

Thanks in advance
Mathias

[Zenju]

VSS on a 64 bit OS requires a 64 bit executable to work correctly and a 32 bit executable on a 32 bit OS. It's possible this restriction applies to a network share hosted by a 32-bit OS as well, in that it does not support 64 bit clients.
You could try out `<FFS install dir>\bin\FreeFileSync_Win32.exe` to start the 32 bit FFS executable on a 64 bit OS; maybe this does the trick.

[bolgasolgamolga]

Sorry for my late resonpse.

The 32-bit version failed to run on my machine. I found another workaround (rename files before coping).

1.Compare the directories
2.Copy the file(names) on right side to clipboard
3.Paste to excel -> generate "rename" command for DOS-shell
4.Execute Rename on cmd.exe
5.Compare again (renamed files will be deleted, updated files will be added)

Maybe this could be an Option to avoid deleting (or moving) files before overwrite. (=FEATURE REQUEST) ;-)

Thanks for your help
Mathias

[Zenju]

> FreeFilesync cannot copy it.

What are the symptoms, do you see an error message?

> somehow it worked with this one [hobocopy]

Maybe we should dig deeper into this one. If it works for hobocopy there's no reason it should not work with FFS since both are just clients of the same VSS function provided by Windows. Is this still reproducible?

> The 32-bit version failed to run on my machine

You mean, FFS failed to start or VSS failed to copy? What error message are you seeing?

> I found another workaround (rename files before coping).

This is a workaround for what? For the failure to use VSS on the source side for files in use? How can this be? Or are you talking about a different problem? Please be as precise as possible when describing what you are doing.