Migrating Veeam Backup & Replication to Linux-Based Backup Server

If you need to migrate Veeam Backup & Replication from Windows-based backup server to Linux-based backup server, you can back up its configuration database, install Veeam Backup & Replication on the target server and restore the configuration data from the backup. As a result, you will have new Veeam Backup & Replication server with settings, jobs and backup infrastructure from the old server.

Important

This feature is available only in queue mode. To join the queue, please sign up here.

Registration is required because the migration process is complex and platform conversion requires professional assistance. The queue works on a first-come, first-served basis to ensure that all requests are handled efficiently and with the best possible customer experience.

Before you begin

Before you migrate the Veeam Backup & Replication configuration database to Linux-based backup server, check the following prerequisites:

  • Install Veeam Backup & Replication on the Linux machine where you plan to move your source backup server. The machine must meet system requirements for a backup server. For instructions on how to install Veeam Backup & Replication, see Deployment.
  • Stop all running jobs and disable all scheduled jobs on the source backup server before you create the configuration backup. Do not start or enable any jobs until the migration of Veeam Backup & Replication is finished. If you start a job before migration is completed, Veeam Backup & Replication will produce a new restore point in the chain and update the chain metadata. The created configuration backup will not contain information about this new restore point. When you migrate data from the configuration backup to the database and start the job again, Veeam Backup & Replication will fail to synchronize the chain metadata with data in the database. As a result, the job will fail.
  • Manually create an encrypted configuration backup of the source Veeam Backup & Replication database as described in the Running Configuration Backups Manually section. Unencrypted configuration backup files are not supported.

Migrating Veeam Backup & Replication

Perform the following steps:

Step 1. Launch Configuration Restore Wizard

  1. Log in to the Veeam Host Management web UI.

In the browser address bar, enter the following URL, replacing <VBR-Host-IP> with the hostname or IP address of your target Veeam Backup & Replication server:

https://<VBR-Host-IP>:10443/

  1. In the Configuration Restore section, click Submit Request to acquire permissions:
  1. In the Configuration Restore section, click Start configuration restore.

Migrating Veeam Backup & Replication to Linux-Based Backup Server 

Step 2. Select Restore Mode

At the Restore Mode step of the wizard, select Migrate.

Migrating Veeam Backup & Replication to Linux-Based Backup Server 

Step 3. Select Configuration Backup

At the Configuration Backup step of the wizard, click Browse to select a configuration backup file to restore and specify the backup encryption password.

Migrating Veeam Backup & Replication to Linux-Based Backup Server 

Step 4. Specify Source Backup Server

At the Source Server step of the wizard, specify the source backup server and service account.

After the migration, this server will be added to managed servers on the target software appliance. This ensures that its local backup repository and backup proxies remain a part of the backup infrastructure.

Migrating Veeam Backup & Replication to Linux-Based Backup Server 

Step 5. Specify the Authorization Key

At the Authorization Key step of the wizard, specify the authorization key you received from the Veeam Support.

Migrating Veeam Backup & Replication to Linux-Based Backup Server 

Step 6. Finish The Migration

After you migrate the configuration backup, finalize the configuration:

Note

If the Veeam Backup & Replication server was added to the Veeam Backup Enterprise Manager or Veeam ONE infrastructure, you must add the new backup server and delete the old one after the migration.

Page updated 11/19/2025

Page content applies to build 13.0.1.180