GENERAL GUIDE • ENCRYPTED BACKUPS

Recover your files on a new device

Prepare for recovery if your old device is replaced or the application's data is lost. This guide applies to any encrypted BackUP job, rather than a particular account or backup.

Save an offline copy

Keep an offline copy for recovery without access to this application. You can also print this guide or save it as PDF.

1. Understand your password and keys

Encryption password

The password you chose in the Encryption step unlocks that job's backups. It is separate from your sign-in password. Changing your account password does not change it.

Recovery file

This file contains a decryption key and is an alternative to the encryption password. It belongs to the job you downloaded it from, not every job in your workspace. Anyone with this file and the backups can decrypt them.

Local key

The application keeps a protected key in its private data folder for automatic backups and restore. Do not rely on it alone: it can be lost with the device or an operating system reinstall.

The recovery file does not contain your backed-up files. You need the complete backup data, plus either the encryption password or the matching recovery file.

2. Prepare your recovery materials

For each encrypted job, use Job details → Download recovery file. Keep the file somewhere secure, separate from your backup drive. Record which file belongs to which job.
Keep your encryption password safely. Do not confuse it with your account password.
Keep the entire job repository folder, including encryption.json, the .objects folder, and the dated backup folders. Do not delete or edit their internal files.
Keep a copy of the complete Recovery tool folder and this guide, so they are available even if the old device stops working.

Copying one dated folder is not enough: incremental versions share content stored in .objects. Enable your operating system's option to show hidden files if that folder is not visible.

3. Choose your situation

Your jobs still appear in the application

Open the job details and select Restore.
If the application reports that the local key is unavailable, select Unlock encryption. Enter the encryption password or choose the matching recovery file. Wait for any active operation to finish before unlocking.
Choose the backup version and files, then select a separate restore destination.

Unlocking makes the local key available for automatic operation again.

You have a new device or lost the database

On Windows, locally saved keys are protected for the original Windows account and its profile. For an installed service, this is the BackUP service account. Copying the application database and vault to a new device is not enough. Keep your backup encryption password or recovery file. Configure AWS credentials again if cloud access is needed.

Reinstalling the application does not automatically add your old jobs. Unlock encryption alone does not import an existing backup repository.

Use the standalone recovery tool described below. It does not need your old account or the application database.

Go to the new-device instructions ↓

4. Restore on a new device

Prepare the backups and destination
Connect the backup drive or copy the entire job repository to the new device. Choose a completed dated version, not a folder ending in .partial. Create an empty restore folder outside the backup repository and make sure it has enough space for the decrypted files.
Prepare the recovery tool
In a default Windows installation, the tool is located in:
```
C:\Program Files\BackUP System\Recovery
```
You can copy the entire Recovery folder from another device. Keep the .dll, .deps.json, and .runtimeconfig.json files together.
The standalone tool requires .NET Runtime 10 for the device's operating system and architecture. If needed, download it from Microsoft's official website; the SDK is not required. Open a new terminal after installing it. The regular Windows BackUP application does not require this additional installation.
The encryption format and recovery tool do not depend on Windows, but current runtime tests were performed on Windows. Full Linux and macOS support has not been announced. Filename and permission compatibility across operating systems has limitations.
Run with a password or recovery file
Open PowerShell on Windows. The following paths are examples: replace the tool path, dated version folder, and restore destination with your actual paths. Keep quotation marks around the paths.
Option A: Use your encryption password
```
dotnet "C:\Program Files\BackUP System\Recovery\BackUP.Recovery.dll" --version "E:\Backups\JobName\2026-01-01_02-00-00" --destination "D:\RestoredFiles"
```
The tool prompts for the encryption password in the terminal. Your typing is hidden. Enter the password and press Enter. Do not include the password in the command itself.
Option B: Use your recovery file
```
dotnet "C:\Program Files\BackUP System\Recovery\BackUP.Recovery.dll" --version "E:\Backups\JobName\2026-01-01_02-00-00" --destination "D:\RestoredFiles" --recovery-file "F:\SafeKeys\BackUP-recovery.json"
```
The matching recovery file replaces the need for the encryption password. The standalone tool currently restores the entire selected version. Selective file restore is available in the application when the job is registered there.

5. Verify that recovery completed

Wait for Verified restore: followed by the output path. The tool may take time without displaying a progress percentage.
The restored files appear in a new folder named after the backup date and time, using the recovery device's local time zone. If the name already exists, a numeric suffix is added. Existing files are not overwritten.
Open a sample of your photos and documents. Check that important files are present and that you selected the correct version before relying on the recovery.
A folder ending in .partial is incomplete and must not be treated as a successful restore.

Restored files are readable normally. The tool restores content and folder structure, not every operating-system permission or attribute. Recreating jobs and schedules on the new device is a separate step.

6. Troubleshooting

The application cannot start because its local vault is missing or damaged: Preserve the existing application data. Restore an intact matching vault on the original Windows installation, or use the standalone recovery tool with your backup password or recovery file. Do not delete the vault to bypass this error.
Incorrect password or mismatched recovery file: Use the job's encryption password, not your sign-in password. Check that the recovery file belongs to the same job and that your keyboard layout is correct.
Missing encryption.json or .objects: Check that you copied the whole repository. The --version argument must point to a dated version folder inside it, not the repository root. A password or key cannot replace missing backup data.
Verification or damaged-content error: Do not edit repository files to bypass the error. Preserve the original and check another intact copy of the repository, if available.
The dotnet command is not recognized: Install the appropriate .NET Runtime 10 and open a new terminal. Also check that all Recovery tool files are present.
You lost both the password and recovery file: If the old application can still unlock the job, download a new recovery file from its details. Without the password, a matching recovery file, or a working local key, the application cannot bypass encryption.