Questions about this warning I have been unable to verify...
#1 What constitutes a "significant difference", more precisely?
#2 This is a "warning", so if my batch job is supposed to stop on the first "error", is this counted?
Search found 3 matches
- 01 Feb 2025, 17:26
- Forum: Help
- Topic: Any way to limit the "size" of a synchonization job?
- Replies: 3
- Views: 2141
- 27 Jan 2025, 23:26
- Forum: Help
- Topic: Any way to limit the "size" of a synchonization job?
- Replies: 3
- Views: 2141
Re: Any way to limit the "size" of a synchonization job?
So I believe I found the option in the GlobalSettings.xml that governs the warning you speak about.
<OptionalDialogs><WarnSignificantDifference Show="true"/>
This looks promising.
I guess I need to look up whether this will STOP the sync, because that's what I want.
And also how does this work when ...
<OptionalDialogs><WarnSignificantDifference Show="true"/>
This looks promising.
I guess I need to look up whether this will STOP the sync, because that's what I want.
And also how does this work when ...
- 27 Jan 2025, 00:31
- Forum: Help
- Topic: Any way to limit the "size" of a synchonization job?
- Replies: 3
- Views: 2141
Any way to limit the "size" of a synchonization job?
I've been using FreeFileSync for years to backup my fileserver to another backup fileserver.
I use the Mirror (with versioning) Sync type, and it's been working nicely.
An automated script runs a sync at 3AM every day.
However, there was once a time when a ransomware virus invaded the main ...
I use the Mirror (with versioning) Sync type, and it's been working nicely.
An automated script runs a sync at 3AM every day.
However, there was once a time when a ransomware virus invaded the main ...