---
title: "Managed Backup for VMware - Backing up and restoring from the VBR console"
description: "Learn how to start an on-demand backup and how to restore a full virtual machine, files or folders from the web console of your Veeam Backup & Replication server"
url: https://docs.ovhcloud.com/es/guides/storage-and-backup/managed-backup-for-vmware/backup-restore
lang: en
lastUpdated: 2026-11-03
---
> For AI agents: the complete documentation index is available at https://docs.ovhcloud.com/es/llms.txt, the full documentation bundle is available at https://docs.ovhcloud.com/es/llms-full.txt.

# Managed Backup for VMware - Backing up and restoring from the VBR console

## Objective

Your Veeam Backup & Replication (VBR) backup server is dedicated to your infrastructure. You access it through its web console to start backups and restore your data, without opening a ticket.

**This guide explains how to start an on-demand backup and how to restore a full virtual machine, files, or start a machine directly from its backup.**

## Requirements

- Have an active Managed Backup for VMware service.
- Have the login of your VBR account and its password (see [Getting started with Managed Backup for VMware](https://docs.ovhcloud.com/es/guides/storage-and-backup/managed-backup-for-vmware/getting-started.md)).
- Have at least one virtual machine that is tagged and backed up.

## Instructions

### What your account allows

| You can                                                                                                                                                                                                                           | Managed by OVHcloud                                                                                                                                              |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| • Start an on-demand backup.<br />• Restore a full virtual machine.<br />• Restore files or folders.<br />• Start a machine from its backup (Instant Recovery).<br />• Check the status of your backups and their restore points. | • The backup jobs: creation, editing and deletion.<br />• The configuration of the VBR, its proxies and the storage.<br />• The deletion of an immutable backup. |

To choose what is backed up, use the vSphere tags (see [Protecting your virtual machines](https://docs.ovhcloud.com/es/guides/storage-and-backup/managed-backup-for-vmware/tag-vm.md)).

### How your backups are scheduled

- **Three backup jobs** are created on your VBR at delivery, one per Backup plan: Standard, Advanced and Premium. Each machine joins the job of its tag.
- **The jobs start every evening at 10 pm,** in the local time of your infrastructure.
- **An on-demand backup** runs immediately, including outside this schedule.

### Signing in to the VBR console

The VBR interface is in English. The labels below are the ones shown on screen.

1. On your dashboard, click "Open the VBR console", choose your infrastructure, then click "Open the VBR web interface". The **Veeam Backup & Replication** sign-in page opens in a new tab.
2. In **Username**, enter the login given in your delivery email. In **Password**, enter the initial password. Click "Sign in". Tick "Remember me" only on a personal computer.
3. At first sign-in, the **Change password** screen asks you to choose a new password. Fill in the two fields, check the "Password requirements" link if needed, which describes the rules to follow, then click "Confirm". OVHcloud does not keep this password, so write it down in a safe place.
4. The **Overview** page appears. The left menu gives you access to "Jobs" and "Backups" (under **Home**), then to "Logs & Events" (under **Audit**).

### Starting an on-demand backup

This is useful right after you tag a machine, or before a sensitive operation (update, application migration).

1. Sign in to the console (see [Signing in to the VBR console](#signing-in-to-the-vbr-console)).

2. In the left menu, under **Home**, click "Jobs", then open the "Backup Jobs" tab. You see one job per Backup plan. The job name ends with `standard`, `advanced` or `premium`.

3. Tick the box of the job for the Backup plan you want.

4. In the action bar, click "Start". The job backs up all the machines that have this tag.

   _The **Jobs** page, **Backup Jobs** tab. In the screenshot, the three jobs are ticked. For a single backup, tick only the job you want._

5. Follow the result in the columns of the list:
   - **Status** shows the state of the job. **Stopped** means it is not running at that moment.
   - **Last Run** shows how long ago the job last ran.
   - **Last Result** shows the result: **Success** for a successful backup, **Warning** for a warning to read in the job details.

6. Open the job details to read its sessions. The history at the top of the page shows the latest runs. The **Session Details** area lists the actions of the session in **Job View**, and **Workload View** shows the result machine by machine.

7. Check that a new restore point appears (see [Checking the status of your backups](#checking-the-status-of-your-backups)).

### Restoring a full virtual machine

Restoring a whole machine uses the **Entire VM Restore** wizard.

1. From the "Backups" page, select the machine to restore and its restore point, then start the full machine restore.

2. The wizard shows its steps on the left: **Virtual Machines**, **Restore Mode**, **Host**, **Datastore**, **Folder**, **Network**, **Reason** and **Summary**. Click "Next" to move forward, "Previous" to go back, "Cancel" to quit.

3. At the **Restore Mode** step, choose:
   - **Restore to the original location**, to replace the existing machine.
   - **Restore to a new location, or with different settings**, under another name, to keep the current machine.

4. At the **Host** and **Datastore** steps, choose the host and the datastore for the restored machine.

5. At the **Folder** step, the original folder of the machine is selected by default. To change it, select the machine then click "Folder". To restore the machine under another name, click "Name". The **Change VM Settings** panel opens. It offers **Set name to**, **Add prefix** and **Add suffix**. Confirm with "OK".

   _The **Entire VM Restore** wizard, **Folder** step, with the **Change VM Settings** panel open._

6. At the **Network**, **Reason** and **Summary** steps, check the network, enter the reason for the restore if needed, then review the summary before you start the restore.

7. Follow the restore until its final report.

**Warning:** **Check the tag after a restore**

After a restore, check the tag of the restored machine in vSphere and add it again if needed. A machine without a tag is neither backed up nor billed.

A restore always goes to the original infrastructure of the machine. Restoring to another infrastructure is not available.

### Restoring files or folders

1. From the "Backups" page, select the machine then start a guest file restore (_Guest File Restore_). The **Browse** page of the machine opens.

2. Next to **Restore Point**, click "Select restore point". The **Select Restore Point** dialog shows a calendar. The days that have restore points are active. The **Available restore points** list shows the time of each point and its type: **Full** for a full backup, **Increment** for an incremental backup. Choose a point, or click "Select latest restore point" to take the most recent one. The **Mount server** field stays on **Automatic**. Click "Select".

3. Browse the tree of the restore point. The left tree shows the machine, and the right list shows the folders and files with their type, size, dates and owner. The **Search** field helps you find a name. Tick the files or folders you want.

   _Browsing the files of the mounted restore point._

4. Click "Restore" to restore the selection to the original machine, or "Download" to download it.

5. When you are done, click "Exit File-level Restore", at the top left, to close the file restore session.

The console gives you an operation report, which you can keep to document the incident.

### Starting a machine from its backup (Instant Recovery)

Instant Recovery starts a machine directly from a restore point, without waiting for its data to be copied. It is the fastest way to bring a service back online.

1. From the "Backups" page, select the machine and start an instant restore. The **Instant Recovery to VMware vSphere** wizard opens. Its steps are **Machines**, **Restore Mode**, **Reason** and **Summary**.

2. At the **Machines** step, tick the machine to restore. The **Restore Point** column shows the selected point. "Add" adds other machines and "Remove" removes some.

3. To change the restore point, click "Restore Point". The **Restore Points** panel lists the available points with their type (**Increment** or **Full**). Select one and click "OK".

4. Click "Next". At the **Restore Mode** step, choose **Restore to the original location** for an identical restore, or **Restore to a new location or with different settings** to customise the location and settings.

5. Click "Next". At the **Reason** step, you can enter the reason for the restore. The **Summary** step recaps your choices. Review them then start the restore.

6. Once the machine has started, it appears in the left menu, under **Action Required** > "Instant Recovery". The list shows its state (**Mounted**) and the restore point used. Check that the machine works as expected.

7. To finish the restore, select the machine then click "Migrate to Production". If you do not need the machine, click "Stop Publishing" to end the session without migrating it.

   _The **Instant Recovery** list under **Action Required**._

8. The **Quick Migration** wizard opens. Its steps are **Virtual Machines**, **Destination**, **Datastore**, **Transfer** and **Summary**. At the **Destination** step, choose the host or cluster (**Host or cluster**), the resource pool (**Resource Pool**) and the folder (**VM folder**) with the "Choose" buttons.

9. At the **Transfer** step, the source and target proxies (**Source proxy** and **Target proxy**) are selected automatically by default. The **Force Veeam transport usage** box forces the disks to be moved by the Veeam transfer engine, even if VMware Storage vMotion is available. Finish with "Next", then confirm the summary.

**Warning:** **Instant Recovery is a temporary solution, not a lasting way to run**

During the session, the machine runs from the backup storage, not from your production storage. Its performance is reduced. It cannot be moved (vMotion). It is not covered by the automatic maintenance of the platform.

Do not leave a machine running in Instant Recovery: as soon as it is checked, migrate it to the production storage and end the session. If you do not need the machine, end the session without migrating it. The duration of the session is not monitored, so remember to end it yourself.

### Restoring from the secondary site

Advanced and Premium backups are copied to the secondary site chosen at order time, where they stay restorable. If the primary site is unavailable, contact support, who will guide you: OVHcloud rebuilds the backup server (see [Security and guarantees](https://docs.ovhcloud.com/es/guides/storage-and-backup/managed-backup-for-vmware/security.md#platform-recovery)).

### How long your restore points stay available

| Backup plan | Retention | Immutability | Monthly points                    |
| ----------- | --------- | ------------ | --------------------------------- |
| Standard    | 14 days   | None         | No                                |
| Advanced    | 35 days   | 14 days      | No                                |
| Premium     | 35 days   | 14 days      | 11 monthly points, about one year |

A restore point keeps the Backup plan under which it was written: if you change the tag of a machine, its old points keep their original retention.

### Checking the status of your backups

Three pages of the console give you the status of your backups.

- **Overview** summarises the activity. The **Protection Overview** card counts the sessions of the last 24 hours (**Total Sessions**) and splits them into **Success**, **Warning** and **Failed**.

- **Backups** lists the backups present on your VBR, by job. Expand a job with the arrow to the left of its name to see one line per machine. The **Restore Points** column (header truncated on screen) shows the number of restore points of each machine.

  _The **Backups** page, jobs expanded. The columns show, among other things, the creation date and the number of restore points._

- **Logs & Events**, **Session Logs** tab, lists the sessions of the last 24 hours (**Last 24 Hours**) with the job name, the session type, its status (**Success** or **Warning**) and its start and end times. The **Type in a name** and **Status** fields let you filter the list.

Your VBR sends you its backup notifications by email, to the address of the OVHcloud account that ordered the service. The last backup date shown in the OVHcloud Console remains the signal to watch: a date older than that of the other machines, or no date, flags a machine to check. The details of a failure are available in the console of your VBR.

## Go further

[Protecting your virtual machines](https://docs.ovhcloud.com/es/guides/storage-and-backup/managed-backup-for-vmware/tag-vm.md): choose what is backed up.

[Security and guarantees of your backups](https://docs.ovhcloud.com/es/guides/storage-and-backup/managed-backup-for-vmware/security.md): encryption, immutability, replication.

[FAQ and troubleshooting](https://docs.ovhcloud.com/es/guides/storage-and-backup/managed-backup-for-vmware/faq.md): lost password, machine not backed up.

Vendor documentation: [Veeam Help Center](https://helpcenter.veeam.com/).

Join our [community of users](https://community.ovhcloud.com/).