Lester Lai21 downloadsMirror a source folder to a target folder using Windows robocopy.
Full Vault Mirror Sync is a Windows-only Obsidian Community Plugin that performs one-way mirror sync from a source folder to a target folder by using Windows robocopy.
Traditional Chinese documentation: README.zh-TW.md
This plugin performs mirror sync with robocopy /MIR. The target folder is forced to match the source folder. Extra files in the target folder can be deleted. If a file is deleted from the source, it can also be deleted from the target on the next sync. This plugin is not a backup tool and is not a versioned backup system.
Use this plugin when you want one folder to stay aligned with another folder on the same Windows machine, such as:
robocopy mirror sync with /MIR /COPY:DAT /DCOPY:DAT /R:3 /W:1 /FFT /XJ1.5.0 or laterrobocopyCommunity Plugin submission support is prepared in this repository, but availability inside the public Obsidian Community Plugins catalog depends on the official review and merge process.
If you are installing from a GitHub release, download these assets from the matching release tag:
main.jsmanifest.jsonstyles.css<YourVault>\.obsidian\plugins\full-vault-mirror-sync\
main.jsmanifest.jsonstyles.cssSettings -> Community plugins.Full Vault Mirror Sync.Source folder path: full Windows path for the source folder. Defaults to the current vault root.Target folder path: full Windows path for the mirror target.Sync interval: timer interval in minutes for automatic sync.Enable automatic sync: starts timer-based sync only after you enable it.Sync once on Obsidian startup: runs one sync shortly after Obsidian starts. This only works when automatic sync is enabled.Manual sync: runs the real robocopy mirror flow.Verify after sync: runs metadata-based post-sync validation.Retry automatically on verification failure: retries sync up to 3 more times when validation fails.C:\ or D:\ as either source or target.More details: docs/SAFETY.md
This plugin does not upload your data, does not call cloud APIs, and does not collect telemetry. Sync and validation run locally on your Windows machine.
No API key is required.
When Verify after sync is enabled, the plugin checks:
The current release does not perform checksum validation.
The plugin excludes its own runtime state file from post-sync validation to avoid false failures caused by status updates after sync.
If sync cannot start or cannot finish before validation, post-sync validation is marked as skipped.
When the target drive or destination folder is unavailable, the sync status becomes Failed.
The plugin shows a clear destination-path error such as:
Destination path is not available: P:\ObsidianMirror
Robocopy exit codes are not traditional success/failure codes.
0 through 7 are treated as successful or acceptable.0 usually means no files needed to be copied.1 means files were copied successfully.3 can mean files were copied and additional differences were handled.8 or higher means failure.robocopyInstall dependencies:
npm install
Build once:
npm run build
Watch mode:
npm run dev
Main source files:
src/main.tsmanifest.jsonstyles.cssSupporting docs:
manifest.json version, for example 0.1.0vmain.js, manifest.json, and styles.css to the GitHub releasesource.zip or source.tar.gzDetailed release notes: docs/RELEASE.md
MIT. See LICENSE.