CLOUD BACKUP & PHOTO LIBRARIES
rclone sync makes a destination match a source. That is useful for a controlled mirror, but it also means files present only at the destination can disappear.
Quick answer
Confirm direction and filters, run a dry run and inspect proposed deletions. Use copy when you want transfers without removing extra destination files.
Steps to follow
-
Before you start
Keep the original data available while following this procedure. Record the application version, account, source path and destination you are actually using. If an error is involved, save its exact wording. Use a small, non-sensitive sample first so that an unexpected result is easy to inspect without disturbing your working library.
-
Set up the right scope
Configure the remote and identify a small source and an isolated destination prefix. List both locations first. Reversing source and destination changes which files are authoritative.
-
Apply the relevant settings
Preview with rclone sync /path/source remote:test –dry-run –verbose. Read the proposed changes, including excluded files and deletions. Replace example paths only after identifying the actual locations.
-
Complete the first run
Run the reviewed command without –dry-run, then inspect logs and compare the destination. Add automation only once the same task behaves correctly on an unchanged second run.
Decisions and checks
The limitation that matters
Sync is one-way matching, not versioned backup or two-way conflict resolution. A mistaken deletion at the source can propagate. Use a separate versioned backup or a deliberately configured backup directory if recovery is required.
How to verify the result
Create a disposable extra file in the test destination and observe its treatment in a dry run. Confirm your filters and recovery policy before using the command on important data.
Keep the result reliable
After the first successful check, repeat the process with an ordinary working session or scheduled run. Record the date and the recovery location. Revisit the setup after changing devices, accounts, storage paths or software versions; yesterday’s successful job does not prove that a new configuration is covered.
Compare the options
| Situation / component | Purpose / action | What to check |
|---|---|---|
| Input | Preserve an unchanged sample | Know which account and location contain the original |
| Operation | Follow the procedure for your installed version | Review errors and skipped items, not only the completion message |
| Result | Open the resulting file or test the documented recovery route | Confirm that the content, version and access rights are correct |
Frequently asked questions
Can I remove the original immediately?
Keep it until you have verified the intended result and have an independent recovery copy where the data matters. A visible file name, a green icon or a completed task alone does not show that every needed item is recoverable.
What information helps if this fails?
Record the version, exact error, affected file type, available space and whether the same small sample works elsewhere. Share sanitized details through the official support route; passwords, recovery keys and private documents are not needed for an initial diagnosis.
Official documentation
This guide combines current official documentation with practical recovery checks. It does not claim hands-on testing of your installation. Menu labels and supported procedures can vary by release; follow the documentation for your installed version.