Backup import fails or closes sessions

Use this article when a VaultPilot backup import fails, returns an archive error, rejects an oversized upload, or succeeds and closes active sessions.

Identify the backup type first

  • Quick Recovery uses a .vpr.json file and a separate recovery key. It excludes file records, revision history, license, server settings and logs.
  • A full Backup Tool backup is a ZIP archive produced by the Backup Tool. The ZIP is not password protected; never send it to anyone, including support.
  • A maintenance backup contains only Audit, Discovery or Executions records and cannot restore a server profile.

Do not upload one type into another type’s import control. If the Quick Recovery key is lost, the file cannot be decrypted; do not try to recover it from logs or the server.

First checks

CheckHealthy result
Operator roleImport is started by an Owner.
File sourceThe file is a VaultPilot Backup Tool ZIP archive or an encrypted JSON export.
Upload sizeThe file is no larger than 512 MB.
Upload pathThe file is uploaded through the VaultPilot screen, not a script or another tool.
Archive contentThe ZIP is exactly as the Backup Tool produced it, not repacked or edited.

What the errors usually mean

ErrorMeaningOperator action
File too largeThe upload is over the size limit.Confirm the file source and size; do not split or edit the archive manually.
Upload size missingThe upload did not come through the normal browser path.Retry from the VaultPilot screen in a supported browser.
Archive invalidThe archive is damaged, empty, repacked or too large to process.Stop and verify the backup was produced by the Backup Tool.
Archive not supportedThe archive contains no VaultPilot backup.Use the correct backup export or Backup Tool archive.
Quick Recovery decrypt errorThe .vpr.json file and the key do not match.Match the file to the correct key; do not guess the value or edit the file.

Successful import side effect

A successful full-backup or Quick Recovery import rebuilds the server profile and closes all active sessions. Users then sign in again through the usual VaultPilot address. Quick Recovery restores only its limited scope; missing file records, history, license or server settings are expected, not an import failure.

Safe evidence

Send privately after redaction:

  • VaultPilot version.
  • Backup file type: ZIP archive or encrypted JSON export.
  • File size rounded to the nearest MB.
  • The exact error message shown on screen.
  • Whether the import finished and closed sessions.
  • Timestamp and the role of the operator.

Do not send backup archives, encrypted JSON exports, database files, certificate packages, private keys, master passwords, logs with secrets or screenshots showing real vault records.

Still stuck?

Check the troubleshooting guide, then write to support@vaultpilot.io with the version, the steps you took and the exact redacted error. Never attach passwords, vault exports or private keys.

Open the troubleshooting guide

Back to Knowledge base