The primary guide on dual boot can be found here.

There are instances where an ongoing sync is interrupted when a user switches OSes. It could either be an incomplete sync or an incomplete modification (i.e. not all changes have been synced). We’ll walk you through the process, some examples, and expected results for some common cases.

We've included two main sections in this article, mainly Local to Cloud sync and Cloud to Local sync.

Precondition:

  1. OS A: Externally sync a folder to a shared partition/drive

  2. OS B: Externally sync the same folder in OS A to the same shared partition/drive

LOCAL TO CLOUD

Case 1: Local to cloud (L2C) incomplete sync:

  1. OS A: Externally sync a folder to a shared partition/drive

  2. A 500MB file (File A) is created locally and completely uploaded in OS A.

  3. In the same OS A, another 500MB file is created locally. Let’s call this File B.

  4. The user quits Insync after 100MB of File B has been uploaded.

  5. User switches to OS B.

  6. In OS B, user externally syncs the same folder in Step 2 of the precondition.

  7. File A in OS B should be completely synced. File B should start to upload completely.

  8. If the user switches to OS A, File B should be uploaded already, and the folder it is in should be synced.

Case 2: L2C renames while Insync is offline

  1. OS A: Sync a folder containing a subfolder with multiple files

  2. Switch to OS B.

  3. The subfolder should be synced on OS B.

  4. User renames the subfolder on OS B, then switches to OS A again.

  5. On OS A, the folder should be renamed and synced.

  6. For whatever reason, the user quits Insync on OS A, then renames the subfolder again.

  7. User restarts Insync on OS A.

Case 3: L2C modifications with sync interruptions

  1. User syncs a 500MB file in the folder under OS A. We’ll call it File A.

  2. User switches to OS B.

  3. File A should be completely synced on OS B.

  4. User modifies File A on OS B and quits after 100MB has been uploaded.

  5. User switches to OS A again.

  6. On OS A, File A should start to upload completely.

  7. If the user switches to OS B once more, File A should be synced without re-uploading or downloading. No duplicates should appear

Case 3a: no sync is interrupted

  1. In OS B, File A is modified and completely uploaded

  2. User switches to OS A

  3. File A should be completely synced

CLOUD TO LOCAL

Case 1: Cloud to Local (C2L) incomplete sync:

  1. Insync is running on OS A

  2. Via web browser, the user adds a new 500MB item (File A) to the cloud and it completely syncs down to OS A.

  3. Via web, the user adds another 500MB item (File B) but quits Insync after 100MB has been synced.

  1. User switches to OS B

  2. File A should be synced without re-downloading on OS B.

  3. File B should download, then completely sync afterwards on OS B.

  4. If the user switches to OS A again, File B should be synced.

Case 2: C2L renames while Insync is offline

  1. On OS A, sync a folder containing a subfolder with multiple files

  2. Switch to OS B

  3. The subfolder should be completely synced on OS B.

  4. On a web browser, user renames the subfolder in Step 1.

  5. User switches back to OS A.

  6. The subfolder on OS A should be renamed.

  7. User quits Insync on OS A, then opens a web browser.

  8. User renames the subfolder on the web browser.

  9. Insync on OS A is restarted.

  10. The subfolder should be renamed on OS A with no duplicates. `OS: B` The subfolder should be synced

Case 3: C2L modifications with sync interruption

  1. Sync a 500MB file on OS A, then switch to OS B.

  2. File should be synced on OS B.

  3. On a web browser, user uploads a modified version of the 500MB file.

  4. On OS B, the file should start downloading.

  5. User quits Insync after 100MB has been downloaded, then switches back to OS A.

  6. On OS A, the file should start downloading and be completely synced afterwards.

  7. User switches to OS B again

  8. The 500MB file should be synced without redownloading or uploading.

Case 4: Unsyncing files

  1. Sync a file in the folder under OS A

  2. Switch to OS B

  3. File should be synced on OS B

  4. User unsyncs the file on OS B

  5. User switches back to OS A.

  6. The file should also be unsynced on OS A.

Did this answer your question?