FreeFileSync Forum

Thank you very much Zenju for implementing this and for listening to the wishes of your users/customers. I really appreciate that.

I would also appreciate an extraction of the data from the "GlobalSettings.xml".

My problem in this context is the following:

I have a folder "D:\Tools" on machine1, where FreeFileSync is also located in its own folder ("D:\Tools\FreeFileSync") as a portable 'installation'.

The folder "D:\Tools ...

I would also like to have the possibility to add some notes to a job. These could be very informative and displayed when hovering over a job in the job list.

Sometimes it's just too hard to fit all the descriptive information into the job name.

@Zenju: Would be nice, if you could clarify this.

Or am I wrong here?

Thank you @xCSxXenen

As far as I understand so far, the GUID, which is the unique ID of each database file, is created when a database file is first created and not every time the base folder is synchronized, right?

Just to clarify a spontaneous backup idea:

Assuming I have the scenario outlined above, i.e. a PC, a notebook and a USB stick(#1) via which I synchronize the two computers via Two Way Sync.

Can I simply include another device, e.g. an external HDD/SSD or also another USB stick(#2), into the ...

Thank you @Zenju

Thank you @Zenju.

According to this, @charliebrown's assumption is wrong and I can use FFS as I described?

PROBLEM: When ffs is run, to sync machine A and machine C, using portable usb disk B as a middle man, the .sync.ffs_db file on B is useless as it is machine specific to the last machine that used the external hdd B.

This means ffs cannot move/delete files properly amongst other errors noted. The ...

Ok, I understand that and I am convinced that it makes sense.

If only so that FFS can judge whether a file that exists only on D when syncing D with E was added to D, or possibly deleted by a sync of E with F on E.

BTW: All these formulations alone twist your brain.... :-)

Thx. in advance Plerry!

Hi all,

after years I'm going to use FreeFileSync again and for long term and surely I will donate then.

Edit:
I already decided to donate and did this right now (e-mail: mr*l@web.de)

Currently I try to understand the concept of the 'sync.ffs_db' files for two way syncs.

I found some statements ...

My suggestion:
Leave your current price model as it is.

But add a second model where one just buys the current version.
So new features are not included at all, but bugfixes are included for a (much) longer time period.

I would have to try this myself with FreeFileSync, because I never used it in that manner.
Usually I use standard OS tools/command line commands like copy/xcopy for such stuff.
Robocopy also is worth a view.

So you want the file from location A alway being copied to location B regardless of the timestamp or content?

Thats odd, because especially Microsoft Access databases immediately get a new timestamp after opening, even if you don't change anything.

So I maybe it is important to know the following:
- Are the Access databases at the time when you want to sync them via FreeFileSync still open, maybe?
- Are it ...

Maybe it is also important, on what kind of device this VeraCrypt container is located?
Is it a SSD, HDD, thumb- or card drive or maybe a network drive?

There is a blank in the folder/path between "Program" and "Files".
You then would have to Quote it because of the blank:
"C:\Program Files\FreeFileSync\FreeFileSync.exe"

USBDLM can do this:
http://www.uwe-sieber.de/usbdlm_e.html

But you would have to read a bit yourself...

Yep, you're right, that's also a possible solution.

So the facts of this discussion seem to be:
- FFS detects a conflict for example, if a file on both sides has been changed.
- 4worlds suggestion is, as far as I understood, that the situation, when a newer file would be overwritten by an older one, should also be rated as a conflict.

Am I right ...

No problem, back to topic. ;-)

I absolutely see it the same way was as Plerry does.

@4world:
In the matter of a 2 way sync tool, FreeFileSync absolutely behaves correct.
If the user replaces a newer file by an older one, it is his own decision to do that.

Your point seems to be, that FFS should be able to protect the user from ...

For me this Looks like a side effect of an anti virus software or similar.

Do you call the batch job via an automated task and so maybe with different user privileges?

You could also think about PaySafeCard for anonymous payments.

Ok, so this is more clear now. 2008 R2 is the server equivalent to Windows 7.
And there also exists a Service Pack 1 for Windows Server 2008 R2.
Is that alread installed?

Reference: https://en.wikipedia.org/wiki/Windows_Server_2008_R2

I would guess that installing (minimum) Service Pack 1 for your Windows Server 2008 (or R2) could help.