Windows 10, Samsung S6
We use a backup program named "SyncBackSE" to back up our Documents folder from one computer to another, and also to an Android phone. In the Android case, it's a one-way operation: copying from the computer to the phone. The files are never altered on the phone itself, and never transferred back to the computer.
The SyncBack program keeps a log of which files have already been transferred to the phone, and when. Any that have been changed since the last backup are copied to the phone. That much works.
The problem: When SyncBack copies a file to the phone, the phone will not simply replace an existing file with the new version; it makes a duplicate, adding an extension like ".dup0". So frequently-modified files (modified on the computer) end up with multiple duplicates (.dup0, .dup1, .dup2 etc.)
We are not using Kies, or at least not intentionally. SyncBack recognizes the S6 as a drive, using "Media Transfer Protocol". The SyncBack people say that their program will not make ".dup0" copies; it must be the phone.
Any ideas?
We use a backup program named "SyncBackSE" to back up our Documents folder from one computer to another, and also to an Android phone. In the Android case, it's a one-way operation: copying from the computer to the phone. The files are never altered on the phone itself, and never transferred back to the computer.
The SyncBack program keeps a log of which files have already been transferred to the phone, and when. Any that have been changed since the last backup are copied to the phone. That much works.
The problem: When SyncBack copies a file to the phone, the phone will not simply replace an existing file with the new version; it makes a duplicate, adding an extension like ".dup0". So frequently-modified files (modified on the computer) end up with multiple duplicates (.dup0, .dup1, .dup2 etc.)
We are not using Kies, or at least not intentionally. SyncBack recognizes the S6 as a drive, using "Media Transfer Protocol". The SyncBack people say that their program will not make ".dup0" copies; it must be the phone.
Any ideas?
Facebook
Twitter
Instagram