4 4 3:Hyper-V Restore

From SEPsesam

Template:Copyright SEP AG en

This is not the latest version of SEP sesam documentation and, as such, does not provide information on features introduced in the latest release. For more information on SEP sesam releases, see SEP sesam Release Versions. For the latest documentation, check Hyper-V documentation.


SEP sesam enables you to restore individual VMs that were backed up from a Hyper-V single server or a Hyper-V cluster. Only one VM can be restored at a time, regardless of whether you are using a Hyper-V single server or a Hyper-V cluster backup.

Restore options

The following options are available when restoring Hyper-V:

  • Select an alternative location to restore your data:
    • restore a VM to the original or a different location (including CSV and SMB 3.0) with the same or a different VM name using relocation
    • restore a VM to the same or a different single Hyper-V server and to the same or a different Hyper-V cluster
    • perform a simple path restore of your selected Hyper-V data directly to a directory on any system instead of restoring and importing the VM to the Hyper-V manager
  • Select a specific Hyper-V version for restore.
  • Restore a complete backup task (ONLY Hyper-V virtual machines that have been backed up separately in a single backup task).
  • Schedule a restore task.

Restoring a Hyper-V virtual machine

Create a new restore task for the VM you want to restore. Note that you cannot perform a Complete restore of selected taskwhen restoring VMs residing on a Hyper-V single server.

  1. From the SEP sesam GUI menu bar, select Activities -> Restore. The New restore task window opens.
  2. Select what you want to restore. You can search save sets by task name or by filename or path.
    • When searching by task name, use the drop-down list of available tasks and select the one you want to restore from. This option is selected by default.
    • If you are searching by filename/path, select the option Filename or path in save set and enter your search expression in the search pattern field.
  3. Under the Saved in period drop-down lists, specify the time frame for which you want to conduct the search. Click Next.

  4. The search results are displayed. From the list of save sets matching your query, click the version you want to select.
    • If you are restoring a save set related to the Hyper-V single server or Hyper-V node backup type all, do not check the option complete restore of selected task. This option is not applicable to a Hyper-V single server VM restore or a node VM restore even though it is shown as available. Because you can only restore a single virtual machine at a time even though you may have backed up several VMs in a single backup task, a complete restore of the selected task is not possible.
    • Select the option complete restore of selected task ONLY if you are restoring a Hyper-V virtual machine that has been backed up separately in a single backup task, i.e., for which a special backup task has been created for the sole purpose of backing up an individual VM. There are no restrictions to restoring the complete task only in the event that you have backed up a single VM in a single task. If more than one VM is included in the backup, do not use this option.
    Click Next.

  5. Data from the selected save set is displayed in a hierarchical tree structure. Select your Hyper-V single server then select the VM you want to restore. Click Next.

  6. Review your restore task configuration and set additional options if necessary.
    • Details of the selected save set are displayed at the top of the window. The name of the restore task is automatically generated in the Name field. You can edit the name and insert a comment below.
    • The Drive field shows the drive with backed up data.
    • The Interface field shows the server (RDS server or Sesam server) with the attached data storage containing the selected save set.
    • The Target node drop-down list shows the target server to which the data will be restored. To restore a task from a cluster to a different single server, select the appropriate Hyper-V target node.
    • Under the Target Path, check the Restore to new VM option. You can enter the target path or browse for it. If no target path is defined, the VM is restored to the default location.
    Make sure that the target host can support the VM type you want to restore. For details, see Known issues.

    SMB3 restore with relocation. Check the Restore to new VM option. You can enter the target path by using UNC notation \\smbshare\Hyper-V\newVM. If no target path is defined, the VM is restored to the Hyper-V server default location.

    • Under the Execution options drop-down list, select one of the following options:
      • do not overwrite existing files (set by default): the VM will not be restored if it already exists on the target server
      • overwrite existing files: if a VM exists on the target server, it will be replaced by the restored version
      • create a new version: if a VM exists on the target server, the restored VM will be restored under a different name
    • You can specify additional restore settings by clicking the Expert options button. In the pop-up windows that opens, you can modify the log level settings, define the pre/post script for restore, etc. For details, see the Restore Wizard.
    If you want to restore the host components from a Hyper-V server/node backup with the source set asall, or from a Hyper-V backup that includes the host components item, click the Expert options button, then the Backup type tab and select the As path backup option. The host components include the virtual server application configuration settings and are needed to recover the Hyper-V server. With the As path backup option, the selected data can be restored to the file system without additional action instead of having to restore and import the VM to the Hyper-V manager (default).

  7. If you want to start your VM restore immediately, click Start. If you want to save the restore task, click Save.

A restore task can be scheduled like any other task. If you want to add a restore task to the schedule, see Scheduling Restore.

Known issues

When attempting to restore a Hyper-V VM into a different Hyper-V environment, the restore might fail with one of the following errors:

Unable to import virtual machine due to configuration errors

or something like

The virtual machine <VM_name> is currently using an AMD processor, but physical computer <host_name> has an Intel processor. A running or saved virtual machine cannot be migrated to a physical computer that has a processor from a different vendor. However, you can move the virtual machine to this node if you shut down the virtual machine.

The configuration error could be caused if a VM you want to restore is not compatible with destination Hyper-V host. Restoring can fail for the following reasons:

  • Hyper-V VMs are using advanced CPU features and fail if the CPUs are too different (different generation, type ...), when restoring VMs between servers with different processor types, e.g., Intel VT or AMD-V, or when the destination server is lacking virtualization extensions or has them disabled.
  • Restoring a VM that is fully configured with virtual switches and network definitions into a different Hyper-V environment could result in a failure to find the original switch definitions.

Possible solutions

Check VM and Hyper-V host compatibility
Before restoring a VM to a different Hyper-V host, check whether the host can support the VM type you want to restore. Use the Compare-VM cmdlet to check a VM and a Hyper-V host compatibility. Run the following commands to first record the compatibility report in a PowerShell variable $Report and then display the compatibility report:
$report = Compare-VM -Path $Source
$report.Incompatibilities | FT -AutoSize

Use the report to fix any compatibility or configuration issues. For details, see MS article Compare-VM.

Enable processor compatibility mode for a virtual machine
According to Microsoft: "Hyper-V performs pre-flight checks whenever a virtual machine live migration or save/restore operation is initiated. These checks compare the set of processor features that are available to the virtual machine on the source host against the set of features that are available on the target host. If these feature sets don’t match, the migration or restore operation is cancelled." For more information, see the whole MS article Processor Compatibility Mode in Hyper-V. To enable processor compatibility mode for a virtual machine, proceed as follows:
    The Processor Compatibility Mode is only applicable to processor types within the same vendor processor family. It does not enable migrations between AMD- and Intel-based hosts. For more information, check TechNet Magazine Tip: When to Use Processor Compatibility Mode to Migrate Virtual Machines.
  1. Open Hyper-V Manager and shut down the VM which you want to configure for CPU compatibility mode.
  2. Right-click the powered off VM. In the Action pane, click Settings, and then click Processor.
  3. Expand Processor, and click Compatibility.
  4. Click Migrate to a physical computer with a different processor, and then click OK.
Shut down VM, back up, and restore
If you are restoring a VM from a Hyper-V host with one processor type (e.g., AMD) to the host with another processor type (e.g., Intel), you might try to move a Hyper-V VM by shutting it down, backing it up, and then restoring on the new host. For more details, see the Redmond Magazine article How To Move a Hyper-V Virtual Machine to New Hardware.

See also

Hyper-V Backup