Cross-Instance Backup & Restore

This guide explains how to move (restore) backups between JetAdmin Cloud and JetAdmin On‑Premise environments in both directions.

Restore Backup from On‑Prem → Cloud

Use this flow when you want to migrate or copy your On‑Prem data into JetAdmin Cloud.

In this case, you first download or export a backup from your On‑Prem system, then upload it into the Cloud instance.

Before starting, make sure you have the JET_BRIDGE_CLOUD_TOKEN from your On‑Prem server (jet-onpremise/.env).

Note: Before restoring into Cloud, it is strongly recommended to create a backup of your current Cloud environment. Restore operations overwrite existing data, and having a Cloud backup allows you to roll back if needed.

Steps in Cloud App (Restore Backup)

Go to App Settings

Click on Restore Backup

Upload your backup file

Click on Advanced

Enter your JET_BRIDGE_CLOUD_TOKEN (the same token from the On‑Prem .env file)

Click on Restore Backup

Restore Backup from Cloud → On‑Prem

Use this flow when you want to bring Cloud data into your On‑Prem installation.

Before starting, make sure you have the JET_BRIDGE_CLOUD_TOKEN from your On‑Prem server.

Open this file and copy the value of JET_BRIDGE_CLOUD_TOKEN. You do not need to generate or configure this token manually.

Steps in Cloud App (Download Backup)

Go to Download Backup

Click on Advanced Settings

Enter your JET_BRIDGE_CLOUD_TOKEN (from the On‑Prem .env file)

Click on Download Backup

Wait until the backup file is downloaded.

Steps in On‑Prem App (Restore Backup)

Go to App Settings

Go to Restore Backup

Upload the downloaded backup file

Click on Advanced Settings

Leave the token field empty (the system will use the token from .env automatically)

Click on Restore Backup

After the process finishes, the On‑Prem instance will contain the restored Cloud data.

Important: JET_BRIDGE_CLOUD_TOKEN

When JetAdmin On‑Prem is deployed, a bridge token is automatically generated and stored in the environment file:

jet-onpremise/.env

Example:

JET_BRIDGE_CLOUD_TOKEN=jet_bridge_xxxxx

You do not need to create this token manually. The same token is used for:

• Downloading backups from Cloud to On‑Prem

• Restoring On‑Prem backups into Cloud

Always keep this token private and do not share it outside your organization.

Useful Tips and Best Practices

Before any restore, always create a backup of the target system (Cloud or On‑Prem). Restore operations overwrite existing data.

If a restore fails, first check:

• That the token in the UI matches the token in jet-onpremise/.env

• That the On‑Prem service was restarted after any .env change