For AI agents: the complete documentation index is available at https://docs.ovhcloud.com/en/llms.txt, the full documentation bundle is available at https://docs.ovhcloud.com/en/llms-full.txt, and this page is available as Markdown at https://docs.ovhcloud.com/en/guides/storage-and-backup/managed-backup-for-vmware/migrate.md.

Managed Backup for VMware - Migrating from Veeam Managed Backup

View as Markdown

Learn what changes when you move from Veeam Managed Backup to Managed Backup for VMware, how the migration works and what happens to your old backups.

Objective

If you currently use Veeam Managed Backup on your infrastructure, you can move to Managed Backup for VMware. The order picks up the protection already in place on each of your virtual machines.

This guide explains what changes, how the migration works and what happens to your old backups.

Requirements

OVHcloud Console Access

  • Direct link:
  • Navigation path: Private Cloud > Backup > Managed Backup for VMware

Instructions

What the migration brings you

You keep the Veeam backup engine, with less to manage yourself. Your machines keep an equivalent level of protection, and each one gets its own Backup plan, systematic encryption and self-service restore from your VBR. The details are in the table What changes between the two services.

How your current protection is matched

The order detects the protection in place on each machine and suggests an equivalent Backup plan:

Your current protectionSuggested Backup plan
Legacy offer, no tierStandard
StandardStandard
AdvancedAdvanced
PremiumPremium

You can change each suggestion before you confirm. A machine that is not protected today has no suggestion: you can give it a plan if you wish.

What changes between the two services

FeatureVeeam Managed BackupManaged Backup for VMware
Protection levelOne level for the whole virtual datacenterOne Backup plan per machine, which you can change at any time
Maximum machine size2 TBUnder 8 TB
Retention14 points (legacy offer, Standard)
35 points (Advanced, Premium)
One point per day		14 days (Standard)
35 days (Advanced, Premium)
Backup encryptionStandard, Advanced, Premium
Legacy offer not encrypted		Systematic, on all three plans
Copy to a secondary siteAdvanced, PremiumAdvanced and Premium, on the site of your choice
ImmutabilityNo14 days, on Advanced and Premium
Long-term GFS retentionPremiumPremium, 12 months of coverage
Self-service file-level restore (FLR)NoYes, from your VBR

With Managed Backup for VMware, you also get:

  • on-demand backup from your VBR
  • Instant Recovery to temporarily start a machine from its backup (see the guide Backing up and restoring from the VBR console)
  • monitoring of each machine in the OVHcloud Console
  • storage included in the price, with nothing to provision

Before you order

Warning

Your old server keeps backing up until the new service is delivered

Your old backup server keeps backing up your machines until the new service is successfully delivered (usually within 2 hours, indicative time). At that point, all its backup jobs are deleted and its proxies are deactivated, all at once. No machine is backed up twice, and no machine with a Backup plan is left unprotected. If the delivery fails, nothing changes on your old server. In all cases, the old service has an end date (see What happens to your old backups).

  • Check your list of machines: give a plan to each machine you want to protect with the new service.
  • The switch is final: once the new service is delivered, the backups of the old server are not restarted.
  • Order in time: Veeam Managed Backup runs up to and including 28 February 2027. If no new service is delivered by then, your machines are no longer protected.

Placing the order

  1. Click Order on the product home page if you do not have a Managed Backup for VMware service yet, or Add an infrastructure on the dashboard otherwise.
  2. Choose the infrastructure to migrate. The order recognises your Veeam Managed Backup service.
  3. Choose the secondary site and the datacenter of the new backup server.
  4. Check the list of machines: each one comes with the suggested Backup plan. Change the suggestions if needed.
  5. Deal with the flagged machines: a machine that is protected today and left without a plan is flagged. The summary tells you how many machines are in this case, and which ones. You can go back and give them a plan, or leave them unprotected knowingly.
  6. Read the estimated monthly amount, accept the terms and conditions and click Confirm the order.
Warning

Machines of 8 TB or more

Virtual machines of 8 TB or more are not supported: they stay visible in the order list, but they cannot receive a Backup plan, even if they are protected today. If you tag one in vSphere, it is backed up anyway, but in degraded mode, without full support, and it can delay the backups of your other machines. Do not put a tag on them in vSphere. If one of them has a tag, remove it (a weekly email reminds you).

What happens before, during and after delivery

  • Before delivery, your old service keeps backing up all your virtual machines.
  • During delivery, the machines to which you gave a Backup plan are tagged by OVHcloud in vSphere. They are protected by the new service from the first backup run.
  • After delivery, you receive your login details for the new VBR by email, as for any new order (see Getting started with Managed Backup for VMware). Your new backups are created on Managed Backup for VMware. Your old backups are not transferred.
  • Give a plan to each machine you want to protect. Without a plan, a machine is no longer backed up. Its old backups can still be restored (see What happens to your old backups).
  • A machine of 8 TB or more is not supported (see Machines of 8 TB or more).
  • Afterwards, you adjust protection with tags in vSphere. The tag in vSphere is the reference: the OVHcloud Console no longer adds any tag after the order. The procedure is in the guide Protecting your virtual machines.

What happens to your old backups

  • No new backup is created on your old server after the new service is delivered.
  • Veeam Managed Backup runs up to and including 28 February 2027. Your old backups can be restored until then. Remember to restore what you need before that date.

To protect your machines with the new service, see Protecting your virtual machines.

Billing during the migration

  • Your new service is billed under the usual rules: per protected machine, over a billing period from the 28th of the previous month to the 27th of the current month (see Understanding your billing).
  • Veeam Managed Backup billing stops automatically in the cycle where your new service starts to be billed. You have nothing to do.
  • You are never billed for both offers over the same period.
  • Billing of the old service ends when it stops (see What happens to your old backups).

Go further

Getting started with Managed Backup for VMware: resources, order and first login.

Protecting your virtual machines: adjust protection after the migration.

Understanding your billing: price per machine and the billing period rule.

Join our community of users.

Was this page helpful?