VaultSync Development diary

VaultSync 1.7 — Sentinel is out

VaultSync 1.7 ( Sentinel ) is now officially released. This update focuses on one thing: If you’re backing up to NAS, external drives, or across machines, this release is for you. What Sentinel actually changes Backups don’t usually fail instantly — they drift…

VaultSync 1.7 — Sentinel is out

VaultSync 1.7 (Sentinel) is now officially released.

This update focuses on one thing:

If you’re backing up to NAS, external drives, or across machines, this release is for you.

What Sentinel actually changes

Backups don’t usually fail instantly — they drift into failure:

  • indexes go out of sync
  • destinations get renamed or re-mounted
  • retention deletes something critical
  • chains silently break

Sentinel introduces systems to detect, explain, and repair that.

Backup integrity & repair

VaultSync now actively monitors your backup structure:

  • Startup non-blocking integrity scans
  • Deterministic orphan-backup repair planning
  • Manual repair tools (Settings → Advanced)
  • Retention safeguards to protect the last valid restore point
  • Early Doctor workflow for guided fixes

Backups are no longer “fire and forget” — they are continuously verified

Transfers that don’t restart from 0

A big real-world improvement:

  • Archive uploads now resume from verified checkpoints
  • Interrupted transfers don’t restart entirely
  • rsync / robocopy keep native restart behavior
  • Full diagnostics for resume / fallback outcomes

This removes one of the most painful failure cases for large backups

Smarter storage awareness

Sentinel makes storage behavior predictable:

  • Stable destination fingerprinting (handles rename / re-add cleanly)
  • Per-destination soft quotas
  • Cleanup suggestions before issues happen
  • Clear storage risk explanations

You see problems before they break your backups

Restore readiness (new core signal)

This is one of the biggest conceptual additions:

  • New restore-readiness scorecard
  • Shows:
    • which projects are at risk
    • why they are at risk
  • One-click review → direct fixes

Backups are now judged by “can I restore?”, not just “did it run”

Dashboard (the only major visual change)

The Dashboard has been fully reworked:

https://preview.redd.it/ehi9verad9qg1.png?width=3514&format=png&auto=webp&s=fe78a6d61bea8a8a25b0d7d8097e5cbb8cf0936a

  • Stable responsive KPI layout (no more awkward spacing)
  • Dedicated restore-readiness section
  • Storage cards now explain why capacity is risky
  • Cleaner hierarchy, less duplicated information

Power-user & system upgrades

  • Cross-machine metadata conflict detection
  • Maintenance window for health tasks
  • Retention simulation preview
  • Improved support bundles with deeper diagnostics
  • Smarter updater:
    • preflight checks
    • patch validation
    • multi-version upgrade paths

UI polish (non-invasive, but noticeable)

No major redesign — but everything is tighter:

  • Better spacing, alignment, and consistency
  • Improved tag color system (now managed in Projects)
  • New custom themes (OLED Black, Deep Blue, editor-style)
  • Cleaner theme editor with proper swatches

Stability fixes

A lot of reliability work under the hood:

  • Fixed font + localization issues
  • Fixed restore UI inconsistencies
  • Fixed startup config race conditions
  • Reduced logging overhead (batched writer)
  • Improved project discovery fallbacks

Download

👉 https://github.com/ATAC-Helicopter/VaultSync/releases

Feedback

If something feels off, confusing, or missing — tell me.

A lot of 1.7 came directly from user feedback, and I want to keep that loop tight.

[link] [comments]