Hi everyone,
I’m setting up a synchronization workflow using Cryptomator, FreeFileSync (FFS), and Google Drive. I want to ensure my logic is sound and won’t result in a corrupted vault, especially when handling sync conflicts.
Here is my folder architecture:
-
GDrive: Remote encrypted cloud files.
-
Encrypted Local: Local copy of GDrive.
-
Decrypted Local: The mounted Cryptomator virtual drive.
-
Working Folder: Where all my actual local edits happen.
My Golden Rule: I never use Two-Way sync between GDrive and the “Encrypted Local” folder. I only use Mirror (Pull or Push) to prevent encrypted file conflicts.
My workflow for handling conflicts (edits made in both the Cloud and the local Working Folder):
-
Mirror (Pull): GDrive → Encrypted Local.
-
Unlock the vault to mount the Decrypted Local drive (which now reflects the cloud’s state).
-
Two-Way Sync: Working Folder ↔ Decrypted Local. I resolve any file conflicts manually here on the unencrypted files using FFS.
-
Mirror (Push): Encrypted Local → GDrive. This pushes the safely resolved, newly encrypted state back to the cloud.
Can anyone confirm if this workflow safely prevents vault corruption? Are there any hidden risks with resolving conflicts on the mounted drive before mirroring the encrypted vault back to the cloud?
Thanks in advance!