) to use different versioning locations for each of your syncs. There are also a few shortcut options to choose from. This allows you to carry the software around with you, on a flash drive for example, and run it as needed without installation. There is both a local installation and a portable version available. The file-name is then simply the same as the original file-name. FreeFileSync FreeFileSync has a few more options during setup, including which version to use. If you select the default (?) method of versioning, your versioning location will contain the last previous version (if any) of files included in your sync, each file in its applicable location in the folder-tree. The individual previous versions of any file can be identified by the date/time-stamp, as added to the original file-name. If you select the YYYY-MM-DD method of versioning, your versioning location will contain all previous versions (if any) of files included in your sync, each previous version in its applicable location in the folder-tree. if FFS will "move" one or more previous-version-files into that sub-tree. If a new(er) version of a file is synced, FFS will now "move" the previous version of that file (if any) to the specified versioning location, while preserving the tree structure, relative to the "root" of your sync.Į.g., if you sync *E:\FolderA\SubFolderB* with *\\\FolderC*, the folder-tree structure as within SubFolderB and FolderC will be preserved.įFS will not "copy" the tree structure to your versioning location, but will only create relevant (sub)folders according to need, i.e. The versioning location can even be the root of a drive (useful when using mapped drives). Preferably that folder is initially empty. That can be any existing folder on any local- or networklocation to which you have write access. I do not know whether or not FreeFileSync includes code written by anyone other than the publisher, so this may not be the case.If you select "Versioning", you have to tell FFS where to store the previous version(s). GPL code can not be compiled into a binary with code that is not GPL compatible and distributed. FreeFileSync 7.9 appears to be the last properly open source release.įollowing from that, if FreeFileSync is using any code from third parties or patches submitted by other developers under the GPL and the publisher has not gotten their express consent to license it under a proprietary license, then FreeFileSync is in violation of the GPL and, thus, the copyright of the third parties. Instead of doing this manually you can import a ffsbatch file via Menu Program Open. Example: Real time synchronization - in combination with FreeFileSync Start RealtimeSync.exe located in FreeFileSync's installation directory and enter all folders you want to monitor. So, while the source for the majority of the app is available under the GPL, any claims that the 8.x binaries being distributed are licensed under the GPL are factually false. Usually this command line will trigger a FreeFileSync batch job. This means that FreeFileSync 8.0 and up is no longer a fully GPLed app and the binary must be considered freeware only. It is designed to save your time setting up and running data backups while having nice visual feedback along the way. FreeFileSync is a free Open Source software that helps you synchronize files and synchronize folders for Windows, Linux and macOS. I attempted to compile the FreeFileSync code myself but as there are no build environment instructions, I wound up hitting a wall.Īlso of note, I took a look at the FreeFileSync 8.x code and it does not appear to contain the requisite code to interpret the install.dat file that causes issues with moving FreeFileSync between relative paths (DropBox, etc). Free data backup software to synchronize files and folders. You can download FreeFileSync Portable 7.9 Dev Test 4 from the forum topic on here if you're curious: All source code is included if you'd like to check it out as well. Unfortunately, though it worked on some PCs, it did not work on others. Error Code 32" issue that occurs on many PCs whenever launching FreeFileSync 6.3 and up from other processes (menus, third party file managers, schedulers, etc) so that everyone could use FreeFileSync 7.9 on every PC. So folks here know as well, I attempted to standardize the technique of using a process breakout, either command line or otherwise, to get around the dreaded "Cannot open file GlobalSettings.xml.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |