I use FFS to backup all data files and sub-directories from my user directory to a drive attached to my router.
Currently it is set to mirror variant, but this isn't the safest method to backup data as it deletes stuff from the target if/when it is deleted from the source.
If I set delete and overwrite to versioning this will probably make it much safer, but I'm thinking for my purpose (backups) would it be better to change variant from mirror to update.
Question is, if using update variant, I assume files just keep being added to the backup and are never deleted even when they are deleted from the source, so the backup just keeps growing bigger. Looking at the icons on the sync settings screen when update variant is selected, other than create and update left side, all other action icons say "do nothing".
In this instance, if files are never deleted how does versioning work? Are the updated files still moved into the revision backup?
Or if using versioning, is it better to stick with the mirror variant?
versioning with update?
- Posts: 7
- Joined: 25 Feb 2023
-
- Posts: 2456
- Joined: 22 Aug 2012
> if using update variant, I assume files just keep being added to the backup and are never deleted even when they are deleted from the source
True, but only new (differently named) files that are added to the source will be added to the target.
If you (at the source side) you modify a file that exists on both sides, an update sync will update the existing to target-side file.
> In this instance, if files are never deleted how does versioning work? Are the updated files still moved into the revision backup?
Versioning will only "move" pre-existing files to the Versioning location if they will be deleted or updated (in your case: from/in the target location).
As, when using Update, a deletion in the source does not result in a deletion in the target, those files will remain in the target and will not be moved to the versioning location.
> Or if using versioning, is it better to stick with the mirror variant?
That's up to you.
If you prefer that files deleted from the source are moved to the Versioning location instead of staying in the target location, you need to use Mirror.
True, but only new (differently named) files that are added to the source will be added to the target.
If you (at the source side) you modify a file that exists on both sides, an update sync will update the existing to target-side file.
> In this instance, if files are never deleted how does versioning work? Are the updated files still moved into the revision backup?
Versioning will only "move" pre-existing files to the Versioning location if they will be deleted or updated (in your case: from/in the target location).
As, when using Update, a deletion in the source does not result in a deletion in the target, those files will remain in the target and will not be moved to the versioning location.
> Or if using versioning, is it better to stick with the mirror variant?
That's up to you.
If you prefer that files deleted from the source are moved to the Versioning location instead of staying in the target location, you need to use Mirror.
- Posts: 7
- Joined: 25 Feb 2023
@Plerry Thank you for clarifying this, much appreciated.
