VaultPilot provides two different recovery artifacts: a browser-encrypted Quick Recovery package and a full Backup Tool backup collected on the Windows server. Their scope, key handling, and restore purpose are not interchangeable.
Recommended workflow
- Take a full Backup Tool backup before updates; do not use Quick Recovery as the only backup.
- Store the backup outside the VaultPilot server disk.
- Restrict access; backup metadata is sensitive.
- Test restore in a controlled environment.
Encrypted Quick Recovery
An Owner creates the .vpr.json package under Server Settings > General. It contains the profile, the vaults that Owner can open, and their records except files. The browser encrypts the package with a separate key that is shown once and cleared from the screen after five minutes, so copy it right away. Keep file and key in separate, access-controlled locations.
Quick Recovery leaves out files, record history, audit history, license, server settings, and logs. Its purpose is to rebuild an empty server profile; a successful import closes every session. It is not a full-system or routine disaster-recovery backup.
VaultPilot Backup Tool
Run backup collection on the Windows server as Administrator with VaultPilotBackupTool.exe.
Record where the archive is saved and keep it private. It can contain encrypted vault data, configuration, and certificate material. The ZIP itself is not password protected; store it offline with restricted access. Do not attach it to tickets or support email.
The download identifies VaultPilot Backup Tool version 3.0.0. The adjacent VaultPilotLogCollector.exe has its own 3.0.2 version. These tool versions do not follow the VaultPilot server version.
The server-backup import panel accepts a VaultPilot Backup Tool ZIP archive or an encrypted JSON export. Import rebuilds the server profile from the backup and closes active sessions. Run it only as an administrator recovery action, after you confirm the file source and backup purpose.
If the ZIP contains a database archive, it must also contain the Backup Tool manifest, or the import stops. Do not send raw database files with a support case.
If import fails because the file is too large, the upload is incomplete, or the archive is invalid or unsupported, use Backup import fails or closes sessions before retrying.
For uninstall, data retention, rollback and purge boundaries, use Uninstall, data retention and rollback. Normal uninstall should preserve the data directory unless an explicit private purge approval exists.
Integrity
Encrypted JSON import checks the SHA-256 integrity manifest and item counts. ZIP import rejects damaged, unsafe or unsupported archives before restore. If any value does not match or the source is unclear, stop the import and write privately to support@vaultpilot.io.