Going forward, when you use SD (or CCC for that matter) to perform the backup, either product will first erase the destination you choose whether the copy/clone will be made to, and then perform the backup.
I've never used SD and can't comment, but CCC does not "first erase the destination"; its default behavior is "Modified and deleted files will be cached as space allows on the destination."
Actually, CCC doesn't erase the destination under any circumstances.
When CCC copies files to the destination, it has to do something with files that already exist on the destination — files that are within the scope of the backup task, and items that aren't on the source at all. By default, CCC uses a feature called the SafetyNet to protect files and folders that fall into three categories:
Older versions of files that have been modified since a previous backup task Files that have been deleted from the source since a previous backup task Files and folders that are unique to the root level of the destination
....
When CCC's SafetyNet is disabled, older versions of modified files will be deleted once the updated replacement file has been successfully copied to the destination, and files that only exist on the destination will be deleted permanently.
Last edited by artie505; 05/15/1609:02 PM. Reason: Clarify
The new Great Equalizer is the SEND button.
In Memory of Harv: Those who can make you believe absurdities can make you commit atrocities. ~Voltaire
