Skip to main content

Sync Recovery and Integrity Checks

Sync plans do not currently run automated recovery tests or scheduled integrity jobs. Verification for sync plans is an on-demand workflow.

This page explains how to test a sync plan, how to check whether source and destination still match, and what to do when differences appear.

What You Should Validate​

For an important sync plan, verify all of the following:

  • the destination contains the expected current files
  • source edits appear after the next sync
  • source deletions are reflected at the destination
  • revisions are created before overwrites or deletions if revisions are enabled
  • the source and destination still match when you run an integrity check

Running a Manual Integrity Check​

In Pluton PRO, sync plans expose Check Integrity from the plan actions.

What the check does:

  • compares the configured source path against the synced destination
  • ignores Pluton's internal .pluton revision area
  • reports matches, missing files, and differences
  • stores the result on the plan so you can review it in the sync integrity view

What it does not do:

  • it does not automatically repair differences
  • it does not run on a recurring schedule for sync plans

Interpreting the Result​

Everything matches

  • The source and destination are aligned based on the completed check

Differences found

  • Some files differ or are missing
  • Review the result first
  • If the source is authoritative, run Sync Now to reconcile the destination

Check failed

  • The comparison itself could not complete
  • Usual causes are source access issues, destination connectivity problems, or permission errors

Practical Test Procedure​

Use a small test folder before relying on a new sync plan in production.

1. Validate the Initial Mirror​

  • Create the plan
  • Let the first sync finish
  • Confirm the destination contains the same files and structure as the source

2. Test an Update​

  • Edit a non-critical file in the source
  • Wait for the next scheduled sync or trigger Sync Now
  • Confirm the updated content appears at the destination

3. Test a Deletion​

  • Delete a disposable test file from the source
  • Run or wait for the next sync
  • Confirm the destination reflects that deletion

4. Test Revisions​

If revisions are enabled:

  • modify or delete a test file
  • complete a sync
  • confirm an older copy was moved into the revision area before the mirror changed

5. Run an Integrity Check​

  • Use Check Integrity
  • Review whether Pluton reports a clean match or differences
  • If differences appear unexpectedly, inspect the destination before syncing again

Recovery Expectations for Sync Plans​

Recovery with sync plans is different from recovery with snapshot backups.

Current File Recovery​

  • The destination already contains the current mirrored copy
  • For many incidents, recovery is simply reading or copying the file back from the destination

Previous Version Recovery​

  • Available only if revisions were enabled before the file changed
  • Older copies are kept in the revisions area and can be used for recovery workflows

When Sync Alone Is Not Enough​

Use an incremental backup plan alongside sync if you need:

  • long-term history
  • point-in-time restores
  • stronger protection against accidental mass deletion or corruption

For critical sync plans:

  1. validate the initial sync when the plan is created
  2. run a manual integrity check after major storage or path changes
  3. re-test revisions after changing retention settings
  4. perform a small recovery drill periodically using a disposable test file

This keeps the verification realistic without relying on features that sync plans do not currently automate.