Back upwardly Hyper-V virtual machines

  • Article
  • 29 minutes to read

Important

This version of Data Protection Director (DPM) has reached the end of support, we recommend you to upgrade to DPM 2019.

System Center Data Protection Manager (DPM) protects Hyper-5 virtual machines by bankroll upwardly virtual machine'south information. You tin can dorsum data up at the Hyper-V host level to enable VM-level and file-level data recovery, or back up at the guest-level to enable awarding-level recovery.

Supported scenarios

DPM can back up virtual machines running on Hyper-V host servers in the following scenarios:

  • Virtual machines with local or direct storage - Support virtual machines hosted on Hyper-Five host standalone servers that have local or straight attached storage. For example a hard drive, a storage area network (SAN) device, or a network attached storage (NAS) device. The DPM protection agent must be installed on all hosts.

  • Virtual machines in a cluster with CSV storage - Back up virtual machines hosted on a Hyper-Five cluster with Cluster Shared Volume (CSV) storage. DPM 2012 SP1 introduced express total fill-in, parallel backups, and cluster query improvements for CSV fill-in. The DPM protection agent is installed on each cluster node.

  • Virtual machines with SMB storage - Back up virtual machines hosted on a Hyper-Five standalone server or cluster with SMB 3.0 file server storage. SMB shares are supported on a standalone file server or on a file server cluster. If you're using an external SMB 3.0 file server the DPM protection agent should be installed on it. If the storage server is amassed, the agent should exist installed on each cluster node. Yous'll need full-share and folder-level permissions for the machine$ account of the application server on the SMB share.

  • Support virtual machines configured for live migration - Live migration allows yous to move virtual machines from one location to while providing uninterrupted access. Y'all can migrate virtual machines betwixt two standalone servers, within a single cluster, or between standalone and cluster nodes. Multiple live migrations tin run concurrently. Yous can also perform a live migration of virtual motorcar storage so that virtual machines tin can exist moved to new storage locations while they go along to run. DPM tin support virtual machines that are configured for live migration. Read more.

  • Back up replica virtual machines - Back up replica virtual machines running on a secondary server (DPM 2012 R2 only)

Learn most supported DPM and Hyper-5 versions in What tin can DPM back up? .

Host vs Invitee backup

DPM can perform a host or guest-level fill-in of Hyper-Five VMs. At the host level the DPM protection agent is installed on the Hyper-V host server or cluster and protects the unabridged VMs and data files running on that host. At the invitee level the agent is installed on each virtual machine and protects the workload present on that machine.

Both methods take pros and cons:

  • Host-level backups are flexible because they piece of work regardless of the type of Os running on the guest machines and don't crave the installation of the DPM protection amanuensis on each VM. If yous deploy host level dorsum you'll be able to recover an entire virtual auto, or files and folders (detail-level recovery).

  • Invitee-level dorsum is useful if y'all want to protect specific workloads running on a virtual motorcar. At host-level you tin can recover an entire VM or specific files, but information technology won't provide recover in the context of a specific application. For example to be able to recover specific SharePoint items from a backed up VM then you should exercise guest-level backup of that VM. Notation that you must use guest-level backup if you want to protect data stored on passthrough disks. Passthrough allow the virtual machine to straight access the storage device and don't store virtual volume data in a VHD file.

Online and offline backup

Important

Depending on your DPM configuration, and what y'all are protecting, DPM's online and offline backup behavior differs. If you lot apply DPM 2012 R2 with UR3 (or afterwards) to protect Hyper-V on Windows Server 2012 R2 (or subsequently), the VMs go along running during the fill-in process. In this case, the rest of this department does not utilize.

If you protect a Hyper-V server on Windows Server 2012, or if you employ DPM 2012 R2 with UR1 or UR2, the following section applies to your configuration:

DPM works seamlessly with the Hyper-5 Volume Shadow Copy Services (VSS) writer to ensure that consistent versions of virtual machines are captured and protected without affecting virtual motorcar access. The ability to back upward open files is disquisitional for business organisation continuity. By default, DPM performs online backups that don't affect the availability of virtual machines. To perform an online backup the following is required:

  • The Fill-in integration service must be enabled, so the operating system running on the virtual machine running must support Hyper-V integration services.

  • The guest operating arrangement must support VSS (Windows 2003 server or later). Online backup isn't supported if virtual machines are running Linux.

  • There should exist no dynamic disks on the virtual machine.

  • All volumes can be either NTFS or ReFS

  • The VSS storage consignment for the volumes shouldn't be modified.

  • The virtual auto must exist running, and if the virtual machine is in a cluster the cluster resource grouping should be online. A Shadow Storage assignment of a volume within the virtual automobile mustn't be explicitly set to a different book other than itself.

If these weather aren't met DPM will perform an offline backup where the virtual motorcar is paused and placed in a saved state while the snapshot is taken, and so the virtual machine is resumed. This means the virtual motorcar is unavailable during the backup, commonly a brusque period of less than a minute for many environments.

Protect VMs on SOFS clusters

DPM tin can dorsum upward VMs deployed on both NTFS and ReFS-based SOFS clusters. To protect VMs on SOFS clusters, do the following procedures:

Add the post-obit machine accounts to the backup operator groups and share permissions:

  • If protecting a highly bachelor (HA) VM, provide the auto account name of the host cluster and cluster nodes, and DPM server.
  • If protecting a non-HA VM, provide the auto name of the Hyper-V host and the DPM server.

To add the auto accounts to the backup operator groups, run the following steps for each node in the SOFS cluster:

  1. Open the command prompt, and blazon, lusrmgr.msc to open up Local Users and Groups.

  2. In the Local Users and Groups dialog, click Groups.

  3. In the list of groups, correct-click Backup Operators and select Backdrop.

    The Backup Operators Properties dialog opens.

  4. In the Backup Operators Properties dialog, click Add.

  5. In the Select Users, Computers, Services Accounts, or Groups dialog, click Object Types. The Object Types dialog opens.

  6. In the Object Types dialog, select Computers and click OK. The Object Types dialog closes.

  7. In the Select Users, Computers, Service Accounts, or Groups dialog, enter the proper name of the server or cluster, and click Cheque Names.

  8. One time y'all have identified the computers, restart the node.

To give permissions to the share, do the following:

  1. On a server where the SOFS/SMB share is hosted, open up Server Manager > File and Storage Services > Shares.

  2. Right click the VM storage share, then click Properties.

  3. In the Properties dialog, on the left navigation carte du jour, click Permissions.

  4. Click Customize permissions to open the Avant-garde Security Settings dialog.

  5. On the Permissions tab, click Add.

  6. Click Select a Main.

  7. In the Select User, Computer, Services Account, or Group dialog, click Object Types.

  8. In the Object Types dialog, select Computers, and click OK.

  9. In the Select User, Computer, Service Account, or Grouping dialog, enter the name of the Hyper-5 node or cluster name you want to accept permission.

  10. Click Cheque Names to resolve the name, and click OK.

  11. In the Permission Entry for Share dialog, select Total Control, and click OK.

  12. In the Avant-garde Security Settings for Share dialog, click the Share tab and echo steps 6-11 for the Share tab instead of the Permissions tab.

  13. When yous are finished calculation permissions for the servers, click Apply.

    This prepares the VMs on SOFS shares for the backup process.

How the Backup process works

DPM performs backup with VSS as follows. The steps in this description are numbered to help with clarity.

  1. The DPM cake-based synchronization engine makes an initial copy of the protected virtual auto and ensures that the re-create of the virtual motorcar is complete and consistent.

  2. After the initial copy is fabricated and verified, DPM uses the Hyper-V VSS writer to capture backups. The VSS author provides a information-consistent gear up of disk blocks that are synchronized with the DPM server. This approach provides the do good of a "full backup" with the DPM server, while minimizing the fill-in data that must be transferred across the network.

  3. The DPM protection agent on a server that is running Hyper-Five, uses the existing Hyper-5 APIs to determine whether a protected virtual automobile also supports VSS.

    • If a virtual car complies with the requirements for online backup and has the Hyper-V integration services component installed, so the Hyper-V VSS writer recursively frontward the VSS request through to all VSS-enlightened processes on the virtual machine. This functioning occurs without the DPM protection amanuensis being installed on the virtual machine. The recursive VSS request allows the Hyper-V VSS writer to ensure that disk- write operations are synchronized so that a VSS snapshot is captured without the loss of information.

      The Hyper-V integration services component invokes the Hyper-Five VSS writer in Book Shadow Copy Services (VSS) on virtual machines to ensure that their application information is in a consequent state.

    • If the virtual machine doesn't comply with online backup requirements, DPM automatically uses the Hyper-5 APIs to pause the virtual machine earlier they capture information files.

  4. Later the initial baseline copy of the virtual auto synchronizes with the DPM server, all changes that are fabricated to the virtual auto resources are captured in a new recovery point. The recovery point represents the consistent state of the virtual machine at a specific fourth dimension. Recovery point captures can occur at least one fourth dimension a solar day. When a new recovery betoken is created, DPM uses block-level replication in conjunction with the Hyper-Five VSS writer to determine which blocks take been altered on the server that is running Hyper-Five afterwards the last recovery point was created. These data blocks are and then transferred to the DPM server and are applied to the replica of the protected information.

  5. The DPM server uses VSS on the volumes that host recovery information so that multiple shadow copies are bachelor. Each of these shadow copies provides a separate recovery. VSS recovery points are stored on the DPM server. The temporary re-create that is made on the server running Hyper-V, is only stored for the duration of the DPM synchronization.

Backup prerequisites

These are the prerequisites for backing upwards Hyper-5 virtual machines with DPM.

Prerequisite Details
DPM prerequisites - If you desire to perform item-level recovery for virtual machines (recover files, folders, volumes) and so you'll demand to install the Hyper-Five role on the DPM server. If you lot merely want to recover the virtual car and not item-level and then the role isn't required.
- You tin protect upward to 800 virtual machines of 100 GB each on one DPM server and allows multiple DPM servers that support larger clusters.
- DPM excludes the page file from incremental backups to improve virtual machine backup functioning.
- DPM tin can backup a Hyper-V server or cluster in the same domain equally the DPM server, or in a child or trusted domain. If you want to backup Hyper-V in a workgroup or an untrusted domain y'all'll need to set up up hallmark. For a single Hyper-V server you tin can use NTLM or document hallmark. For a cluster yous can utilize certificate authentication only.
- Using host-level backup to back up virtual machine data on passthrough disks isn't supported. In this scenario nosotros recommend y'all use host-level dorsum to backup VHD files and guest-level back to back up the other data that isn't visible on the host.
- When protecting a Hyper-V cluster using scaled-out DPM protection (multiple DPM server protecting a big Hyper-V cluster) you lot can't add together secondary protection for the protected Hyper-Five workloads.
- You tin only fill-in replica virtual machines if DPM is running Arrangement Heart 2012 R2 and the Hyper-V host is running on Windows Server 2012 R2.
- You can back up deduplicated volumes.
Hyper-5 VM prerequisites - The version of Integration Components that is running on the virtual machine should be the same every bit the version of Hyper-Five on the server that is running Hyper-V.
- For each virtual machine backup you lot'll need gratuitous space on the volume hosting the virtual hard disk files to allow Hyper-V enough room for differencing disks (AVHD's) during fill-in. The space must be at least equal to the adding Initial disk size*Churn charge per unit*Backup window fourth dimension. If you're running multiple backups on a cluster, you'll need enough storage chapters to suit the AVHDs for each of the virtual machines using this adding.
- If you want to backup virtual machines located on a Hyper-5 host servers running Windows Server 2012 R2, the virtual car should take a SCSI controller specified, even if information technology'due south non connected to anything. This is considering for online fill-in in Windows Server 2012 R2 the Hyper-V host mounts a new VHD in the VM then dismounts it subsequently. Only the SCSI controller can support this and thus is required for online backup of the virtual automobile. The SCSI controller doesn't information technology became articulate why we need this SCSI controller. Without this setting, event ID 10103 will exist issued when you endeavor to back up the virtual machine.
Linux prerequisites - You tin can backup Linux virtual machines using DPM 2012 R2. Only file-consequent snapshots are supported.
Back up VMs with CSV storage - For CSV storage, install the Volume Shadow Copy Services (VSS) hardware provider on the Hyper-V server. Contact your storage surface area network (SAN) vendor for the VSS hardware provider.
- If a single node shuts downward unexpectedly in a CSV cluster, DPM volition perform a consistency cheque confronting the virtual machines that were running on that node.
- If you need to restart a Hyper-V server that has BitLocker Bulldoze Encryption enabled on the CSV cluster, you lot must run a consistency bank check for Hyper-V virtual machines.
Support VMs with SMB storage - Turn on auto-mount on the server that is running Hyper-Five to enable virtual machine protection.
- Disable TCP Chimney Offload.
- Ensure that all Hyper-V machine$ accounts have full permissions on the specific remote SMB file shares.
- Ensure that the file path for all virtual machine components during recovery to alternate location is less than 260 characters. If not, recovery might succeed, but Hyper-V cannot mount the virtual machine.
- The following scenarios are non supported:
Deployments where some components of the virtual automobile are on local volumes and some components are on remote volumes; an IPv4 or IPv6 address for storage location file server., and recovery of a virtual machine to a computer that uses remote SMB shares.
- You'll need to enable the File Server VSS Agent service on each SMB server - Add it in Add roles and features > Select server roles > File and Storage Services > File Services > File Service > File Server VSS Agent Service.

Back up virtual machines

  1. Fix up your DPM server and your storage. When setting upwardly your storage, utilise these storage chapters guidelines.

    • Boilerplate virtual automobile size - 100 GB
    • Number of virtual machines per DPM server - 800
    • Total size of 800 VMs - 80 TB
    • Required space for backup storage - 80 TB

  2. Set up the DPM protection agent on the Hyper-V server or Hyper-Five cluster nodes. If you lot're doing guest-level fill-in you'll install the agent on the VMs yous want to support at the guest-level.

  3. In the DPM Administrator console click Protection > Create protection group to open the Create New Protection Grouping wizard.

  4. On the Select Group Members page, select the VMs yous desire to protect from the Hyper-Five host servers on which they're located. We recommend you put all VMs that will have the aforementioned protection policy into one protection group. To make efficient apply of space, enable colocation. Colocation allows y'all to locate data from unlike protection groups on the aforementioned disk or tape storage, so that multiple information sources take a single replica and recovery point volume.

  5. On the Select Information Protection Method folio, specify a protection group name. Select I want short-term protection using Deejay and select I desire online protection if you want to support data to Azure using the Azure Backup service. If this pick isn't available complete the wizard to create the grouping and so change the protection group settings to select this selection. Yous can store data in Azure for up to 3360 days.

    If you accept a standalone tape or tape library connected to the DPM server yous'll be able to select I want long-term protection using tape.

  6. In Specify Curt-Term Goals > Retentivity range, specify how long you want to retain deejay data. In Synchronization frequency specify how often incremental backups of the data should run. Alternatively, instead of selecting an interval for incremental backups you can enable Just before a recovery indicate. With this setting enabled DPM will run an express total back just earlier each scheduled recovery bespeak.

    • If you're protecting application workloads, recovery points are created in accordance with Synchronization frequency, provided the awarding supports incremental backups. If it doesn't then DPM runs an express total fill-in, instead of an incremental fill-in, and creates recovery points in accordance with the limited backup schedule.

    • If you lot enable long-term storage to tape, in Specify Long-Term Goals > Retentivity range, specify how long you want to continue your tape data (one-99 years). In Frequency of backup select the backup frequency that you want.

    • The fill-in frequency is based on the specified retentivity range. When the retention range is i-99 years, you can select backups to occur daily, weekly, bi-weekly, monthly, quarterly, one-half-yearly, or yearly.

    • When the retention range is 1-11 months, you can select backups to occur daily, weekly, bi-weekly, or monthly. When the retention range is one-iv weeks, you can select backups to occur daily or weekly.

    • On a stand-alone tape bulldoze, for a unmarried protection group, DPM uses the same tape for daily backups until there is insufficient space on the record. If yous enabled colocation, data resources are colocated on the tape.

    • If you lot configured long-term storage to tape, on the Select Tape and Library Details page specify the tape and library that'll be used for support of this protection group. Yous can also specify whether to shrink or encrypt the backup data.

  7. In the Review disk allocation folio review the storage pool disk space allocated for the protection grouping.

    Total Information size is the size of the data you want to back up, and Disk space to be provisioned on DPM is the infinite that DPM recommends for the protection grouping. DPM chooses the platonic fill-in book, based on the settings. Withal, you can edit the fill-in book choices in the Disk resource allotment details. For the workloads, select the preferred storage in the dropdown bill of fare. Your edits modify the values for Total Storage and Free Storage in the Available Disk Storage pane. Underprovisioned space is the amount of storage DPM suggests y'all add to the volume, to go along with backups smoothly in the hereafter.

  8. On the Choose Replica Creation Method page, specify how the initial replication of data in the protection group will be performed. If yous select to replicate over the network nosotros recommended you choose an off-superlative time. For large amounts of information or less than optimal network conditions, consider replicating the data offline using removable media.

  9. On the Consistency Cheque Options page, select how you desire to automate consistency checks. You can enable a bank check to run only when replica data becomes inconsistent, or co-ordinate to a schedule. If you don't want to configure automatic consistency checking, you can run a manual check at whatsoever fourth dimension by right-clicking the protection grouping and selecting Perform Consistency Check.

    Later you create the protection grouping, initial replication of the information occurs in accordance with the method you selected. After initial replication, each backup takes place in line with the protection group settings. If you demand to recover backed up data note the following:

Back up virtual machines configured for alive migration

When virtual machines are involved in live migration, DPM continues to protect the virtual machines as long as the DPM protection agent is installed on the Hyper-5 host. The way in which DPM protects the virtual machines depends on the type of live migration involved.

Live migration within a cluster - When a virtual car is migrated within a cluster DPM detects the migration, and backs upward the virtual motorcar from the new cluster node without any requirement for user intervention. Because the storage location hasn't changed, DPM continues with express full backups. In a scaled scenario with two DPM servers to protect the cluster, a virtual machine that is protected by DPM1 continues to be protected by DPM1, no matter where the virtual machine is migrated.

Live migration outside the cluster - When a virtual machine is migrated between stand-alone servers, different clusters, or betwixt a stand-solitary server and a cluster, DPM detects the migration, and tin can back upwards the virtual machine without user intervention.

Requirements for maintaining protection

The following are requirements for maintaining protection during live migration:

  • The Hyper-5 hosts for the virtual machines must be located in a System Center VMM cloud on a VMM server running at least System Centre 2012 with SP1.

  • The DPM protection amanuensis must be installed on all Hyper-V hosts.

  • DPM servers must be continued to the VMM server. All Hyper-V host servers in the VMM cloud must too be connected to the DPM servers. This allows DPM to communicate with the VMM server so DPM can find out on which Hyper-V host server the virtual machine is currently running, and to create a new backup from that Hyper-V server. If a connectedness can't exist established to the Hyper-V server, the dorsum up fails with a message that the DPM protection agent is unreachable.

  • All DPM servers, VMM servers, and Hyper-5 host servers must be in the aforementioned domain.

Details well-nigh live migration

Note the post-obit for backup during live migration:

  • Live migration protection doesn't back up backup to record.

  • If a live migration transfers storage, DPM performs a full consistency check of the virtual machine, and so continues with express full backups. When live migration of storage occurs, Hyper-V reorganizes the virtual hd (VHD) or VHDX which causes a one-time spike in the size of the DPM backup data.

  • On the virtual machine host, turn on auto-mount to enable virtual protection, and disable TCP Chimney Offload.

  • DPM uses port 6070 as the default port for hosting the DPM-VMM Helper Service. To alter the registry:

    1. Navigate to HKLM\Software\Microsoft\Microsoft Data Protection Manager\Configuration.
    2. Create a 32-bit DWORD value: DpmVmmHelperServicePort, and write the updated port number as function of the registry key.
    3. Open <Install directory>\Microsoft System Centre 2012\DPM\DPM\VmmHelperService\VmmHelperServiceHost.exe.config, and change the port number from 6070 to the new port. For example: <add baseAddress="net.tcp://localhost:6080/VmmHelperService/" />
    4. Restart the DPM-VMM Helper service, and restart the DPM service.

Set up protection for live migration

To set up up protection for live migration:

  1. Fix the DPM server and its storage, and install the DPM protection agent on every Hyper-V host server or cluster node in the VMM cloud. If you're using SMB storage in a cluster, install the DPM protection amanuensis on all cluster nodes.

  2. Install the VMM console as a client component on the DPM server then that DPM tin can communicate with the VMM server. The console should be the aforementioned version as the one running on the VMM server.

  3. Assign the DPMMachineName$ account as a read-merely administrator account on the VMM management server.

  4. Connect all Hyper-V host servers to all DPM servers with the Gear up-DPMGlobalProperty PowerShell cmdlet. The cmdlet accepts multiple DPM server names. Employ the format: Set-DPMGlobalProperty -dpmservername <dpmservername> -knownvmmservers <vmmservername>. For more data see Ready-DPMGlobalProperty.

  5. After all virtual machines running on the Hyper-V hosts in the VMM clouds are discovered in VMM, fix a protection group and add the virtual machines you want to protect. Note that automatic consistency checks should exist enabled at the protection grouping level for protection under virtual car mobility scenarios.

  6. After the settings are configured, when a virtual machine migrates from i cluster to some other, all backups continue as expected. Y'all can verify alive migration is enabled as expected as follows:

    1. Cheque the DPM-VMM Helper Service is running. If it isn't start it.

    2. Open Microsoft SQL Server Management Studio and connect to the instance that hosts the DPM database (DPMDB). On DPMDB run the following query: SELECT Superlative 1000 [PropertyName] ,[PropertyValue] FROM[DPMDB].[dbo].[tbl_DLS_GlobalSetting].

      This query contains a property, called KnownVMMServer. This value should be the same value you provided with the Set up-DPMGlobalProperty cmdlet.

    3. Run the following query to validate the VMMIdentifier parameter in the PhysicalPathXML for a particular virtual machine. Replace VMName with the proper name of the virtual machine.

      select cast(PhysicalPath equally XML) from tbl_IM_ProtectedObject where DataSourceId in (select datasourceid from tbl_IM_DataSource where DataSourceName like '%<VMName>%')

    4. Open the .xml file that this query returns and validate that the VMMIdentifier field has a value.

Run manual migration

Later y'all consummate the steps in the previous sections, and the DPM Summary Manager job completes, migration is enabled. By default, this job starts at midnight and runs every forenoon. If y'all want to run a manual migration, to cheque everything is working as expected, do the following:

  1. Open up SQL Server Management Studio and connect to the instance that hosts the DPM database.

  2. Run the following query: select * from tbl_SCH_ScheduleDefinition where JobDefinitionID='9B30D213-B836-4B9E-97C2-DB03C3EB39D7'. This query returns the ScheduleID. Note this ID every bit you volition utilize information technology in the next step.

  3. In the SQL Server Management Studio, aggrandize SQL Server Agent, and so aggrandize Jobs. Right-click ScheduleID that y'all noted, and select Start Job at Step.

Note that backup performance is afflicted when the job runs. The size and scale of your deployment determines how much time the job takes to finish.

Support replica virtual machines

If DPM is running on Windows Server 2012 R2 or greater, then yous tin support replica virtual machines on a secondary server. This is useful for several reasons:

Reduces the impact of backups on the running workload - Taking a backup of a virtual machine incurs some overhead as a snapshot is created. Past offloading the fill-in procedure to a secondary remote site, the running workload is no longer impacted past the backup performance. This is applicable merely to deployments where the backup copy is stored on a remote site. For example, you lot might take daily backups and store data locally to ensure quick restore times, simply have monthly or quarterly backups from replica virtual machines stored remotely for long-term retention.

Saves bandwidth - In a typical remote branch role/headquarters deployment you need an appropriate amount of provisioned bandwidth to transfer backup data betwixt sites. If you create a replication and failover strategy, in addition to your data fill-in strategy, you can reduce the amount of redundant data sent over the network. Past backing upward the replica virtual machine data rather than the primary, you relieve the overhead of sending the backed upwardly data over the network.

Enables hoster backup - You can use a hosted datacenter as a replica site, with no need for a secondary datacenter. In this case the hoster SLA requires consequent backup of replica virtual machines.

A replica virtual machine is turned off until a failover is initiated, and VSS can't guarantee an awarding-consistent backup for a replica virtual car. Thus the backup of a replica virtual machine will be crash-consistent only. If crash-consistency can't exist guaranteed, then the backup will fail and this might occur in a number of atmospheric condition:

  • The replica virtual auto isn't healthy and is in a critical country.

  • The replica virtual car is resynchronizing (in the Resynchronization in Progress or Resynchronization Required state).

  • Initial replication between the primary and secondary site is in progress or awaiting for the virtual machine.

  • .hrl logs are existence applied to the replica virtual motorcar, or a previous action to apply the .hrl logs on the virtual deejay failed, or was canceled or interrupted.

  • Migration or failover of the replica virtual auto is in progress

Recover backed up virtual machines

When you can recover a backed upward virtual machine, yous utilize the Recovery magician to select the virtual machine and the specific recovery point. To open up the Recovery Wizard and recover a virtual machine:

  1. In the DPM Administrator panel, blazon the proper noun of the VM, or expand the listing of protected items and select the VM you desire to recover.

  2. In the Recovery points for pane, on the calendar, click any appointment to see the recovery points available. Then in the Path pane, select the recovery point you want to use in the Recovery wizard.

  3. From the Actions menu, click Recover to open the Recovery Wizard.

    The VM and recovery point yous selected announced in the Review Recovery Selection screen. Click Next.

  4. On the Select Recovery Blazon screen, select where you desire to restore the data and then click Side by side.

    • Recover to original instance: When you recover to the original instance, the original VHD is deleted. DPM recovers the VHD and other configuration files to the original location using Hyper-Five VSS writer. At the end of the recovery procedure, virtual machines are nonetheless highly available. The resource group must be present for recovery. If it isn't bachelor, recover to an alternate location and and then make the virtual machine highly available.

    • Recover as virtual auto to whatever host: DPM supports alternate location recovery (ALR), which provides a seamless recovery of a protected Hyper-V virtual machine to a unlike Hyper-5 host, contained of processor architecture. Hyper-5 virtual machines that are recovered to a cluster node will not be highly available. If y'all choose this pick, the Recovery Magician presents you with an additional screen for identifying the destination and destination path.

    • Copy to a network folder: DPM supports item-level recovery (ILR), which allows you to do detail-level recovery of files, folders, volumes, and virtual difficult disks (VHDs) from a host-level backup of Hyper-Five virtual machines to a network share or a volume on a DPM protected server. The DPM protection agent doesn't accept to be installed inside the guest to perform item-level recovery. If you cull this option, the Recovery Magician presents y'all with an additional screen for identifying the destination and destination path.

    Notation

    DPM does not support detail level recovery of a Dynamic Disk within a Guest VM. For this the Guest VM should have a Basic Disk.

  5. In Specify Recovery Options configure the recovery options and click Adjacent:

    • If you are recovering a VM over low bandwidth, click Modify to enable Network bandwidth usage throttling. After turning on the throttling option, you lot can specify the corporeality of bandwidth you want to make available and the time when that bandwidth is available.
    • Select Enable SAN based recovery using hardware snapshots if you have configured your network.
    • Select Transport an e-mail when the recovery completes and then provide the electronic mail addresses, if you desire email notifications sent one time the recovery process completes.

  6. In the Summary screen, make sure all details are right. If the details aren't correct, or you desire to make a change, click Back. If you are satisfied with the settings, click Recover to beginning the recovery process.

  7. The Recovery Status screen provides data about the recovery task.

Annotation

By default, eight parallel recoveries are supported. You tin increase the number of parallel restore jobs by calculation the below registry key:

  • Primal Path: HKLM\Software\Microsoft\Microsoft Information Protection Director\Configuration\ MaxParallelRecoveryJobs
  • 32 Bit DWORD: HyperV
  • Data: <number>

Restore an individual file from a Hyper-Five VM

You can restore individual files from a protected Hyper-Five VM recovery point. This feature is only available for Windows Server VMs. Restoring individual files is similar to restoring the entire VM, except you browse into the VMDK and find the file(s) yous want, earlier starting the recovery process. To recover an individual file or select files from a Windows Server VM:

Note

Restoring an individual file from a Hyper-V VM is available only for Windows VM and Disk Recovery Points.

  1. In the DPM Administrator Console, select Recovery view.

  2. Using the Browse pane, scan or filter to find the VM y'all want to recover. Once yous select a Hyper-V VM or binder, the Recovery points for pane displays the available recovery points.

    "Recovery points for" pane to recover files from Hyper-v VM

  3. In the Recovery Points for pane, use the calendar to select the date that contains the desired recovery bespeak(south). Depending on how the backup policy has been configured, dates can take more one recovery point. In one case you've selected the day when the recovery bespeak was taken, brand sure you've chosen the correct Recovery time. If the selected date has multiple recovery points, cull your recovery bespeak past selecting information technology in the Recovery fourth dimension drop-downwardly menu. Once you chose the recovery signal, the list of recoverable items appears in the Path pane.

  4. To find the files you want to recover, in the Path pane, double-click the particular in the Recoverable particular cavalcade to open it. Select the file, files, or folders you want to recover. To select multiple items, press the Ctrl key while selecting each particular. Utilise the Path pane to search the list of files or folders appearing in the Recoverable Detail column.Search listing below doesn't search into subfolders. To search through subfolders, double-click the folder. Employ the Upwards push to move from a child folder into the parent folder. You can select multiple items (files and folders), but they must exist in the same parent binder. You tin't recover items from multiple folders in the same recovery job.

    Review Recovery Selection in Hyper-v VM

  5. Once yous've selected the item(s) for recovery, in the Administrator Console tool ribbon, select Recover to open the Recovery Sorcerer. In the Recovery Magician, the Review Recovery Selection screen shows the selected items to exist recovered.

  6. On the Specify Recovery Options screen, if you desire to enable network bandwidth throttling, select Change. To exit network throttling disabled, select Next. No other options on this sorcerer screen are bachelor for VMware VMs. If you choose to modify the network bandwidth throttle, in the Throttle dialog, select Enable network bandwidth usage throttling to turn information technology on. Once enabled, configure the Settings and Piece of work Schedule.

  7. On the Select Recovery Type screen, select Next. You can just recover your file(due south) or folder(s) to a network folder.

  8. On the Specify Destination screen, select Browse to find a network location for your files or folders. DPM creates a folder where all recovered items are copied. The folder name has the prefix, DPM_day-calendar month-twelvemonth. When y'all select a location for the recovered files or binder, the details for that location (Destination, Destination path, and available space) are provided.

    Specify location to recover files from Hyper-v VM

  9. On the Specify Recovery Options screen, choose which security setting to apply. You can opt to modify the network bandwidth usage throttling, but throttling is disabled by default. Likewise, SAN Recovery and Notification aren't enabled.

  10. On the Summary screen, review your settings and select Recover to commencement the recovery process. The Recovery status screen shows the progression of the recovery operation.