Veeam v13: Migrating to Linux Appliance & Copy Job Evolution
With the release of Veeam v13, it is now possible to deploy the backup appliance on a Linux base. This saves on Windows licensing and antivirus overhead.
[!IMPORTANT] Pre-upgrade Warning: If you have Backup Copy Jobs running in Legacy mode, you cannot proceed directly with the upgrade. Migrating these jobs is a mandatory “pre-work” step to ensure a smooth transition to version 13.
- The Pre-work: Migrating Legacy Jobs
Before touching the upgrade button, you must transform your legacy chains into Per-Machine chains:
Disable the legacy backup copy job.
Create a new identical job: Veeam v13 (and the later builds of v12) will default to the new per-machine mode.
Map the Backup: Point the new job to the same repository and backup chain.
Acknowledge the Warning: Veeam will notify you that the old chain will be disconnected. You’ll find these old points under Orphaned in the Disk section.
Clean up: Note that per-machine backups create individual files for each VM. Keep an eye on the old restore points; I’ve found that Veeam doesn’t always prune them automatically once expired, so manual cleanup might be necessary.
- Moving to the Linux Appliance
Once your jobs are modernized, you can proceed with the migration:
Step 1: Update your current Windows-based installation from v12 to v13.
Step 2: Perform a Full Configuration Backup export.
Step 3: Deploy the new Veeam Linux Appliance.
Step 4: Import the configuration backup.
Important Update on Migration Strategy: Veeam now requires a specific Migration Key to move the configuration from a Windows-based VBR to the new Linux Appliance via the standard import/export method. To obtain this, you must register on their dedicated portal and wait for approval.
Warning: As of my current experience, this process is not instantaneous. I have been waiting for a response for over a month. If you are on a tight schedule, do not rely on the “Configuration Backup” method alone.
The Alternative: Manual Job Reconstruction Since the official migration path is currently gated by human approval, the most reliable alternative is the manual approach:
Deploy the new Linux Appliance as a fresh install. Attach the existing repositories to the new appliance. Rescan the repositories to populate the “Imported Backups” section. Recreate the Backup Jobs manually, pointing them to the same repository. Map Backups: Use the “Map Backup” function to link the new jobs to the existing backup chains. This ensures no data loss and maintains the continuity of your incremental chains.
Management Interface: Keep in mind that the Web UI does not yet expose 100% of the advanced settings. To gain full control over the infrastructure, you should install the Veeam Backup & Replication Console. You can easily find the download link for the console directly on the appliance login page when accessing it via browser.