From 32d6e973a814fae6cbf4e8f1c3ab39983aee8a95 Mon Sep 17 00:00:00 2001 From: Nicole Rappe Date: Thu, 20 Feb 2025 16:26:20 -0700 Subject: [PATCH] Update Scripts/Powershell/General Purpose/rClone.md --- Scripts/Powershell/General Purpose/rClone.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Scripts/Powershell/General Purpose/rClone.md b/Scripts/Powershell/General Purpose/rClone.md index 9c75653..e03fddb 100644 --- a/Scripts/Powershell/General Purpose/rClone.md +++ b/Scripts/Powershell/General Purpose/rClone.md @@ -39,6 +39,8 @@ The following commands illustrate how to use bisync to synchronize a local folde === "Repairing a Broken BiSync" If you find your bisync has somehow gone awry, and you need to re-create the differencing databases that are used by rclone to determine which files are local and which are remote, you can run the following command to (non-destructively) re-build the databases to restore bisync functionality. + + The only core difference between this command and the "Subsequent Sync" command, is the addition of `--resync` to the argument list. ```powershell .\rclone.exe bisync "Local" "Remote" --create-empty-src-dirs --conflict-resolve newer --conflict-loser delete --compare size,modtime,checksum --resilient --log-level ERROR --drive-skip-gdocs --fix-case --force --progress --resync