Sync solves consistency; backup solves recovery
A sync service keeps files on several devices in a similar state. Renames, edits and deletions usually propagate, which is convenient but does not create an independent historical copy.
A backup is designed to recover from accidental deletion, corruption, ransomware or account problems. A synced folder can be a source for backup, but it should not be the only backup.
Check version and trash retention rules
Retention varies by service, account plan and organization policy. A visible version-history interface should not be treated as a promise of permanent retention.
Before cleanup, confirm whether you can restore one file, an entire folder and a large batch. Record the retention window and test a small restore before an incident forces you to use it for the first time.
Recognize online-only files, local copies and shortcuts
Space-saving modes may store only names and previews locally. A scanner that needs complete content can trigger large downloads, unexpectedly consuming bandwidth and disk capacity.
A shortcut is not an independent copy, and a shared folder may affect another person's workflow. Identify the object type and owner before reorganizing it.
- Confirm that content is available offline
- Separate shortcuts from real copies
- Check ownership and collaborators
- Avoid bulk cleanup while sync is active
Keep copies with different failure modes
Copy count alone is not enough. Copies in the same account, sync folder or permanently connected device can fail together.
Keep a convenient synchronized set and another backup with version history or offline isolation. Test restores periodically so the backup is more than a reassuring file count.