I would like you to separate the backup file creation function for deletion and updates.
I want to backup only changed files, not deleted ones.
Additionally, when creating backup files by version, I would like it to indicate whether the file is a deletion or an update.
I would prefer to avoid cross-checking with logs as much as possible during the process.
Please if possible
I would like you to separate the backup file creation function for deletion and updates
- Posts: 2
- Joined: 13 Jun 2026
-
- Posts: 4879
- Joined: 11 Jun 2019
Your first request can be achieved by using a custom sync, where you define the rules.
Your second request is irrelevant if you don't sync deletions anyway, but could still be a nice quality-of-life update.
Your second request is irrelevant if you don't sync deletions anyway, but could still be a nice quality-of-life update.
-
- Posts: 2960
- Joined: 22 Aug 2012
What do you mean by "backup file"?
Do you mean
a) a file created or updated by a sync in a (left or right) base-location or any of its subfolders, or
b) a file created via Versioning, as a previous version of a file updated in or deleted from a (left or right) base location or any of its subfolders
In case a),
• if you now run a Mirror sync (which deletes right-side items that have been deleted from your left-side), you can use the Update sync instead (which retains right-side items that have been deleted from your left-side)
• if you now run a Two-way sync (which deletes items that have been deleted from the opposite side), as xCSxXenon replied, you can use a Custom sync instead, in which you replace the two bottom (Delete) action icons by two minus-icons (Do nothing), by clicking on the respective icons.
In case b)
it is not a smart idea to not (at least temporarily) create/retain a copy in your Versioning location of files deleted by your sync from a base-location or any of its subfolders.
What if your deletion (that caused the sync to delete files from a base-location or any of its subfolders) was accidental?
Do you mean
a) a file created or updated by a sync in a (left or right) base-location or any of its subfolders, or
b) a file created via Versioning, as a previous version of a file updated in or deleted from a (left or right) base location or any of its subfolders
In case a),
• if you now run a Mirror sync (which deletes right-side items that have been deleted from your left-side), you can use the Update sync instead (which retains right-side items that have been deleted from your left-side)
• if you now run a Two-way sync (which deletes items that have been deleted from the opposite side), as xCSxXenon replied, you can use a Custom sync instead, in which you replace the two bottom (Delete) action icons by two minus-icons (Do nothing), by clicking on the respective icons.
In case b)
it is not a smart idea to not (at least temporarily) create/retain a copy in your Versioning location of files deleted by your sync from a base-location or any of its subfolders.
What if your deletion (that caused the sync to delete files from a base-location or any of its subfolders) was accidental?
- Posts: 2
- Joined: 13 Jun 2026
I am currently using unidirectional mirroring from the server to the device, with the device configured to allow only updates.
In other words, the device has no permissions to create, delete, move, or copy files, only update permissions.
Since file management on the server side is handled separately, there is no reason for the synchronization program to back up files deleted from the server. During synchronization, I only need to back up files that are modified during the synchronization process.
In short, I want to back up only the files that are being updated.
That is why I requested that you allow me to select whether to back up changes and deletions separately.
I confirmed that regardless of how I configure the delete settings in Custom Synchronization, files deleted from the server are uploaded from the device to the server and backed up.
Please let me know if there is another way to configure this.
In other words, the device has no permissions to create, delete, move, or copy files, only update permissions.
Since file management on the server side is handled separately, there is no reason for the synchronization program to back up files deleted from the server. During synchronization, I only need to back up files that are modified during the synchronization process.
In short, I want to back up only the files that are being updated.
That is why I requested that you allow me to select whether to back up changes and deletions separately.
I confirmed that regardless of how I configure the delete settings in Custom Synchronization, files deleted from the server are uploaded from the device to the server and backed up.
Please let me know if there is another way to configure this.
-
- Posts: 2960
- Joined: 22 Aug 2012
> I want to back up only the files that are being updated.
Again, it is unclear what you mean, and that unclarity concerns two aspects in above quote.
• As asked before, but not replied to: what do you mean by "back up"
• What do you mean by "are being updated"
If you want to create a sync that leaves your left-side unaffected, and that only updates right-side files (that then must pre-exist the sync), but does not create right-side files that (pre-sync) exist left-side only, nor deletes right-side files that left-side do not or no longer exist, you can create the following custom sync:Note that "Use database file to detect changes" is not checkmarked.
Because you have no create or delete rights in your right-side "update only" location, you must also disable the creation of lock files by setting the LockDirectoriesDuringSync flag to false.
If instead you want to create a backup (here in terms of: a further copy) of the files just updated in your "update only" right-side location during a sync you ran, simply create a Mirror sync from your now left-side "update only" location to your backup location, which is now your right-side location.
Again, because you have no create or delete rights in your now left-side "update only" location, you must disable the creation of lock files by setting theLockDirectoriesDuringSync flag to false.
Again, it is unclear what you mean, and that unclarity concerns two aspects in above quote.
• As asked before, but not replied to: what do you mean by "back up"
• What do you mean by "are being updated"
If you want to create a sync that leaves your left-side unaffected, and that only updates right-side files (that then must pre-exist the sync), but does not create right-side files that (pre-sync) exist left-side only, nor deletes right-side files that left-side do not or no longer exist, you can create the following custom sync:Note that "Use database file to detect changes" is not checkmarked.
Because you have no create or delete rights in your right-side "update only" location, you must also disable the creation of lock files by setting the LockDirectoriesDuringSync flag to false.
If instead you want to create a backup (here in terms of: a further copy) of the files just updated in your "update only" right-side location during a sync you ran, simply create a Mirror sync from your now left-side "update only" location to your backup location, which is now your right-side location.
Again, because you have no create or delete rights in your now left-side "update only" location, you must disable the creation of lock files by setting theLockDirectoriesDuringSync flag to false.