---
title: "Running Restore"
description: "The Run action causes machines in a plan to recover from their backup files. For more information on the data recovery process, see the Veeam Backup & Replication User Guide, section Data Recovery."
canonical: "https://helpcenter.veeam.com/docs/vro/userguide/running_restore.html"
breadcrumb: "User Guide > Working with Recovery Plans > Working with Restore Plans > Running and Scheduling Restore Plans > Running Restore"
dateModified: "2026-08-26"
---

# Running Restore

The **Run** action causes machines in a plan to recover from their backup files. For more information on the data recovery process, see the Veeam Backup & Replication User Guide, section [Data Recovery](https://helpcenter.veeam.com/docs/vbr/userguide/data_recovery.html?ver=13).

::: important

For Orchestrator to be able to perform restore in a [clean room](infrastructure_clean_room.md) in case the production Veeam Backup & Replication server becomes unavailable, you must do the following before running a restore plan:

1. Add the production backup repository to the embedded Veeam Backup & Replication server as described in the Veeam Backup & Replication User Guide, section [Backup Repositories](https://helpcenter.veeam.com/docs/vbr/userguide/backup_repository.html?ver=13).
2. Rescan the backup repository as described in the Veeam Backup & Replication User Guide, section [Rescanning Backup Repositories](https://helpcenter.veeam.com/docs/vbr/userguide/rescanning_backup_repositories.html?ver=13). Note that this process may take several minutes to complete.
3. Run the restore plan.

:::

To run a restore plan:

 1. Navigate to **Recovery Plans**.
 2. Select the plan and click **Run**.
 3. In the **Run Plan** window, do the following:

     1. For security purposes, retype your password and click **Next**. 

        You must also select the **Force-enable the plan** check box if you have not enabled the plan yet.

     2. <a id="recoverylocation"></a>In the **Recovery location** section, click the link and select a location to which inventory groups included in the plan will be restored. For a recovery location to be displayed in the list of available locations, it must be created and added to the list of inventory items available for the scope, as described in section [Managing Recovery Locations](managing_recovery_locations.md).

        If the selected recovery location includes multiple hosts, datastores and networks, Orchestrator will use the round-robin algorithm to restore machines added to the plan. For more information, see [How Orchestrator Places VMs During Restore](understanding_resource_usage_restore.md).

        ::: important

        If you select a Hyper-V recovery location and the restore plan contains a VM that already exists in this location, Orchestrator will make an attempt to replace the existing VM with the restored one. However, if the existing VM is powered on, the restore operation will complete with an error. To work around the issue, power all the plan VMs off — and then try running the plan again.

        :::

     3. <a id="restorepoint"></a>In the **Restore point** section, choose a restore point that will be used to recover machines. 

        Keep in mind that recovering data from the archive tier is not supported. If you select the **Most recent** option, make sure to choose a restore point that is stored in either the capacity or the performance tier. For more information on Veeam Backup & Replication tiering options, see the Veeam Backup & Replication User Guide, section [Scale-Out Backup Repository](https://helpcenter.veeam.com/docs/vbr/userguide/backup_repository_sobr.html?ver=13).

     4. <a id="ransomware_restore"></a>In the **Malware detection** section, choose whether you want to check restore points created for machines included in the plan for malware flags. When restoring to a VMware vSphere environment, you can also decide whether you want to scan these restore points with antivirus software, YARA rules or both.

        By default, Orchestrator checks the most recent restore point on each machine. If no clean restore point is found, Orchestrator restores the machine to the selected recovery location without connecting it to any network. However, you can instruct Orchestrator to halt the plan and cancel the restore operation if no clean restore point is found.

        For more information on how Orchestrator performs malware scan, see [Overview](malware_scan_overview.md).

        ::: note

        -   If you choose to perform malware scan while running the plan, Orchestrator will scan only one disk per mount server at a time. This process may take a while, affecting the [plan RTO](restore_plan_rto_rpo.md).
        -   To scan a restore plan for possible malware without running the plan, follow the instructions provided in section [Scanning Recovery Plans](scanning_recovery_plans.md).

        :::

     5. Review configuration information and click **Run**.

[![Running Restore](images/run_restore.png "Running Restore")](images/run_restore.png){.toggle scale=65}

The plan goal is to reach the *RESTORED* state. If any critical error is encountered, the plan will stop with the *HALTED* state. To learn how to work with *HALTED* restore plans, see [Managing Halted Plans](managing_halted_restore_plans.md).