Rclone Sync Vs: Copy !!hot!!

| Pitfall | Consequence | Prevention | |---------|-------------|-------------| | Swapping source/destination in sync | Deletes source data | Use --dry-run ; double-check order ( rclone sync source dest ) | | Running sync without --checksum | Modtime changes might cause unnecessary updates | Add --checksum for critical data | | Assuming copy never overwrites | It does overwrite if destination file is older/different | Use --update or --ignore-existing | | Using sync on shared destination folders | Deletes files created by others | Use copy instead or add explicit --exclude rules |

This behavior makes copy ideal for incremental backups or "pooling" data from multiple sources into one location. It is an additive process; the destination only grows or updates, never shrinks. If you are worried about human error—such as accidentally deleting a local folder and wanting to ensure the cloud version remains intact— copy is the correct choice. rclone sync vs copy

Use if you want to add to your collection without ever losing a file. Use Sync if you want your cloud storage to be a carbon copy of your local drive and don't mind (or specifically want) files to be deleted to stay in sync. Use if you want to add to your

The sync command is designed to make the Destination an of the Source. It is powerful but inherently "destructive." It is powerful but inherently "destructive