Skip to content

SafeVault v1.1.4

Choose a tag to compare

@Justin-147 Justin-147 released this 13 Jul 10:03

SafeVault v1.1.4

SafeVault v1.1.4 makes protected-folder and external-backup cleanup available
directly in Recovery Home. It does not change the object-store format or delete
original files from protected folders.

Highlights

  • Protect Folders now shows Stop Protection and Delete History actions directly
    in each folder row.
  • Delete History presents the number of file records, versions, and recovery
    points that will be removed, followed by a normal confirmation dialog. Users
    no longer need to type a root ID or full path.
  • Backup Management lists SafeVault-created external backup archives, including
    file size and modification time.
  • Individual external backup archives can be deleted from the UI.
  • Automatic backup can be stopped while keeping existing archives.

Safety

  • Stopping protection preserves all existing recovery history.
  • Deleting history removes SafeVault metadata for the selected root but never
    modifies or deletes the original protected folder.
  • Backup deletion is restricted to regular SafeVault archive files directly
    inside the configured external backup directory. Path traversal, symlinks,
    missing files, and unrelated files are rejected.
  • Unreferenced object-store content is not silently removed. It remains subject
    to the separate, explicit cleanup workflow.

Upgrade Notes

Windows users can install the new SafeVaultSetup.exe over an existing version.
Protected folders, recovery history, backup configuration, storage location,
Startup choice, and storage budget remain unchanged.

After upgrading, open Recovery Home and use Protect Folders to stop protection
or preview history removal. Open Backup Management to review external archives.
Every destructive action still requires an explicit confirmation.

Known Limits

  • Smart retention remains planning/dry-run only and does not automatically
    delete referenced version history.
  • Removing a root's history makes that history unavailable for recovery, but
    physical object-store space is reclaimed only by the separate cleanup action.