deblan-mirror/abraunegg-onedrive
deblan-mirror/abraunegg-onedrive
1
0
Fork 0
mirror of https://github.com/abraunegg/onedrive synced 2026-03-14 14:35:46 +01:00
Code Issues Projects Releases Wiki Activity

Update PR

Browse source 
* Update PR
This commit is contained in:
abraunegg 2025-12-12 11:28:41 +11:00
commit 0f94f4c209
1 changed files with 5 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

9
docs/usage.md
View file

@ -1088,11 +1088,12 @@ Are you sure you wish to proceed with --resync? [Y/N]
You must press `Y` or `y` to continue with `--resync` action. Any other entry will exit the application.
#### Understanding the --resync risks and behaviour
A `--resync` **does not delete local-only files**.
If an item exists locally but not in OneDrive, and is not excluded via a `sync_list` rule, it will be treated as **new local content** and uploaded during the resynchronisation.
A `--resync` **does not delete local-only files**. When a file exists locally but not in OneDrive, and is not excluded via a `sync_list` rule, it is treated as new local content and will be uploaded during the resynchronisation process.
The risks when using `--resync` come from the loss of historic state:
* The client no longer knows which side previously held the authoritative version.
Local deletion of such files when using `--resync` only occurs when using the explicit local data destructive modes such as `--download-only --cleanup-local-files`.
The risks when using `--resync` come from the loss of the historic state:
* The client no longer knows which side previously held the authoritative version of your data.
* Conflict handling still preserves data via safe backup mechanisms, but may result in renamed or duplicated files.
* Upload and download volumes may spike significantly.
* Increased calls to the Graph API can lead to temporary throttling (HTTP 429).