Hyper-V Cloud Practice Builder. Disaster Recovery Using DPM 2010

Transcription

1 Hyper-V Cloud Practice Builder Disaster Recovery Using DPM 2010

2 The Hyper-V Cloud Practice Builder from Microsoft Enterprise Services can help Microsoft partners by: Accelerating practice development by providing best practices for planning and delivering a Private Cloud solution based on Microsoft Virtualization technologies. Reducing training costs by providing methodologies for delivering Server Virtualization scenarios. Lowering risk by providing real-world examples of problems and solutions encountered by Microsoft architects and consultants. The Hyper-V Cloud Practice Builder is for: Consulting Services management, sales, and delivery roles. Software and Hardware vendors looking to understand how Private Cloud is delivered. Licensing and resellers interested in sizing and scoping Private Cloud engagements. Introduction Microsoft System Center Data Protection Manager 2010 is a server software application that enables disk-based and tape-based data protection and recovery for computers in and across Active Directory directory service domains. Data Protection Manager performs replication, synchronization, and recovery point creation to provide reliable protection and rapid recovery of data both by system administrators and by end-users. This Guide discusses the use of Microsoft System Center Data Protection Manager 2010 to backup and restore the virtualized environment in a Private Cloud. This Guide is part of the Hyper-V Cloud Practice Builder that is based on the framework that Microsoft Consulting Services has leveraged to deliver Server Virtualization for several years in over 82 countries. 2

3 Contents System Center Data Protection Manager and the Virtualized Environment... Prerequisites for protecting Hyper-V using Data Protection Manager Data Protection Manager Supported Scenarios 5 Data Protection Manager Unsupported Scenarios 5 Application Awareness 6 Planning Protection of Virtualized Workloads 8 Protection Groups 8 Planning Protection Groups 10 Planning Protection Group Storage 11 Planning Disaster Recovery 12 Installing and Configuring Data Protection Manager Hardware Requirements 14 Component 14 Minimum Requirement 14 System volume: 1 GB 14 Software Requirements 14 Installing Data Protection Manager Deploying Data Protection Manager Agents 18 Creating Protection Groups and Protecting VMs 20 Recovering Virtual Machines 23 Supported Scenarios 23 Recovering a Virtual Machine to Its Original Location 23 Recovering a Virtual Machine to an Alternate Location 23 Item-Level Recovery for Hyper-V 29 3

4 System Center Data Protection Manager and the Virtualized Environment Microsoft System Center Data Protection Manager 2010 (DPM) has extended the protection of Microsoft Hyper-V and now supports these configurations: Cluster Shared Volumes (CSV) Highly available virtual machines on a failover cluster Stand-alone hosts Windows Server/Server Core and Microsoft Hyper-V Server & Local Data Source Protection When recovering a virtual machine, Data Protection Manager 2010 supports the following options: Recovery to the original location Recovery to an alternate location Item-level recovery from a host-based virtual machine backup Recovery to network folder Copy to tape Before you install Data Protection Manager 2010, you need to ensure that the Data Protection Manager server and the computers and applications it is going to protect meet network and security requirements. You must also ensure that they are running on supported operating systems and that they meet the minimum hardware requirements and software prerequisites. The Data Protection Manager 2010 installation requires Windows Server 2008 R2 or the x64-bit version of Windows Server Data Protection Manager is designed to run on a dedicated, single-purpose server that cannot be an application server, a computer with cluster services enabled, or a management server for Microsoft System Center Operations Manager. You can, however, monitor the Data Protection Manager server and the computers that it protects using Operations Manager. 4

5 Data Protection Manager Supported Scenarios Data Protection Manager 2010 supports the following scenarios for Hyper-V: Online backup. Data Protection Manager 2010 supports online backups for guests running Windows Server 2008, Windows Server 2008 R2, and Windows Server Online backups ensure that Data Protection Manager does not bring down the protected virtual machine. By default, Data Protection Manager tries to protect virtual servers in the online mode. Offline backup. Data Protection Manager 2010 supports offline protection for guests running older operating systems such as Windows NT 4.0 and Windows Server 2000, and Linux. Offline backup requires Data Protection Manager to pause a virtual machine, take a snapshot of the virtual machine, bring the virtual machine online again, and then back up the snapshot. Failover Clustering. Data Protection Manager 2010 supports protection for clustered Hyper-V host servers, with full install or Server Core-based Hyper-V hosts. Data Protection Manager also supports Quick Migration and Live Migration. Data Protection Manager Unsupported Scenarios Data Protection Manager 2010 does not support the backup of virtual machines that do not have their storage on the host. However, if you have at least one virtual hard disk (VHD) of the virtual server on the local machine, Data Protection Manager protects the local VHD. Storage not on host means you either use iscsi to present volumes to the virtual machine or use a remote VHD. For such machines, we recommend that customers perform host-level backup of the VHD files using Data Protection Manager and install an agent into the virtual machine to back up data that is not visible on the host. Data Protection Manager 2010 does not support host-based backup of virtual machine pass-through disks. To backup pass-through disks, the Data Protection Manager agent must be installed in the virtual machine and the backup of pass-through disks must be performed from within the virtual machine. 5

6 Application Awareness Many existing backup solutions offer generic backup functionality that can sometimes be adapted to various applications. Instead of conforming to this model, Data Protection Manager was designed to leverage three fully supported Microsoft technologies to provide continuous data protection specifically for Hyper-V. The Data Protection Manager block-based synchronization engine is used to make the initial copy of a protected virtual machine, ensuring that a complete and consistent copy is made. The Data Protection Manager network transport ensures that the copied data is delivered intact to the Data Protection Manager server. After the initial copy is made, Data Protection Manager captures express full backups using the Hyper-V Volume Shadow Copy Service (VSS) writer. The Data Protection Manager agent monitors which disk blocks have changed in the protected virtual machines. The VSS writer, under Data Protection Manager instruction, provides a data-consistent set of disk-blocks to synchronize to the Data Protection Manager server. This provides the benefit of a full backup with the Data Protection Manager server having a complete and up-to-date copy of the data, without the penalty of transmitting everything across the network like a normal full. The Data Protection Manager agent on the Hyper-V host machine uses the existing Hyper-V APIs to determine whether a protected virtual machine is also capable of supporting VSS. By combining the Windows Server VSS functionality with block-level synchronization, Data Protection Manager can protect virtual machines while they are active. After the initial baseline copy of the virtual machines resources is synchronized to the Data Protection Manager server, any changes to the virtual machine can be continuously synchronized as often as every 30 minutes. The express full backup technology of Data Protection Manager identifies which blocks have changed on the host storage volumes. Those blocks, and only those blocks, are copied to the Data Protection Manager server, where they are applied to an active replica of the data, with previous iterations stored as a set of differences within the preceding backup. Data Protection Manager can maintain up to 512 of these differential backups. 6

7 The entire express full backup process usually takes only a few minutes to complete, depending on how much data has changed. After the express full backup is completed, the Data Protection Manager server has captured an exact duplicate of the virtual machine from the original Hyper-V host. To provide multiple recovery points, Data Protection Manager maintains a shadow copy of the changed blocks between the current express full backup and the previous one. These block level differences are stored; Data Protection Manager uses them to reconstitute the previous recovery point. In this manner, Data Protection Manager can maintain up to 512 recovery points per data source. If the virtual machine is running Windows Server 2003 or later and has the Hyper-V Integration Components installed, then the Hyper-V VSS writer will pass the VSS request through to all VSS-aware processes on the virtual machine without requiring the virtual machine to be running the Data Protection Manager agent. This recursive VSS request allows the VSS writer to ensure that all disk write operations are paused both for the workloads within the virtual machine as well as for the various files that comprise the virtual machine data set and permits the VSS snapshot to be captured with no data outage. This unique combination of features between Data Protection Manager and Hyper-V usually equals or surpasses all other backup methods for virtual environments. Data Protection Manager calls the Hyper-V VSS writer. The Hyper-V VSS writer determines that the virtual machine is VSScapable and calls the VSS writers within the virtual machine. Any VSS-capable applications such as Microsoft SQL Server 2005 invoke their VSS writers to ensure that their application data is in a consistent state. The Windows Server VSS functionality ensures that the NTFS volumes inside the virtual machine are also consistent. When these steps are complete and the internal contents of the virtual machine are known to be data consistent, the Data Protection Manager agent tracks changed blocks and transfers those to the Data Protection Manager server. 7

8 This process ensures that the virtual machine is internally consistent before securing the virtual machine files on the host, without requiring downtime. If the virtual machine does not support VSS, then the Hyper-V VSS writer will automatically use the Hyper-V APIs to put the virtual machine into hibernation before capturing the various data files. Once they have been protected, the machine is automatically restarted. This integration permits the seamless capture of any supported virtual machine configuration or operating system with as little downtime as possible between three to five minutes in most cases. Data Protection Manager also uses VSS to maintain shadow copies on the Data Protection Manager server between one express full and the next one. By storing only the differences between individual express full backups, Data Protection Manager is able to maintain up to 512 shadow copies of the complete virtual machine data set without requiring 512 times the space. Planning Protection of Virtualized Workloads Planning the backup and recovery of virtualized workloads requires careful consideration of a number of variables including all of the virtual machines, storage, and configuration data that comprise the workload as well as the Recovery Point and Recovery Time objectives described in previous sections. Data Protection Manager uses a concept called protection groups to manage the protection of related resources. Protection Groups A protection group is a collection of data sources, such as volumes, shares, or Virtual Machines, that have a common protection configuration. Data sources within a protection group are referred to as protection group members. The protection group configuration specifies the performance options that you want to enable, such as on-the-wire compression and daily consistency checks. The protection policy specifies how often to synchronize the replica with the live data on the protected computer and when to create recovery points of the replica. Some of the factors you should consider when deciding how to organize your data into protection groups are the business requirements of the organization, network performance, and the characteristics of the data. 8

9 Consider, for example, how often the data changes, how rapidly the data size increases, and how critical it is to be able to recover a very recent copy of lost data. You might also want to consider how frequently you need to back up the data to tape, which data needs to be encrypted or compressed, and the number of backup copies you need available. In most cases, you will want to group data with similar characteristics together. To efficiently make use of your storage and bandwidth, you must design a set of recovery goals that takes into account the nature of each protected data source. To define these goals, you must first determine your desired synchronization frequency, recovery point schedule, and retention range. The synchronization frequency determines how often the Data Protection Manager agent will capture snapshots of your data and transmit the changes to the Data Protection Manager server. This value reflects how much data you are willing to lose from this data source if there is an outage or disaster. Think of your synchronization frequency as how often you wish incremental backups of your data to happen. The recovery point schedule determines how often Data Protection Manager creates discrete recovery points for the protected data. The Data Protection Manager recovery point schedule determines the opportunities you have to recover your data. If you perform a weekly full backup and daily incremental backup in a traditional backup application, you have seven unique points of recovery. Data Protection Manager creates recovery points at every express full backup as well as when data is synchronized. A fifteen minute synchronization schedule provides 96 recovery points per day. The retention range determines how long you need Data Protection Manager to keep the protected data available for recovery. You may define both short-term and long-term protection policies to control recovery from both disk and tape. Short-term policies may use either disk or tape, while long-term policies are intended to provide control over your extended tape retention. o o Defining a short term to tape scenario implies using Data Protection Manager as a traditional tape backup solution, intending to replace one s existing backup solution. Defining short term to disk (only) is often used to provide a 9

10 robust backup and recovery solution for Hyper-V and other workloads through Data Protection Manager, and then allow a third party heterogeneous enterprise tape solution to back up the Data Protection Manager server for long term compliance. o Most Data Protection Manager users, however, will choose short term to disk plus long term to tape, enabling a complete solution that offers rapid and reliable disk-based protection and recovery, with a seamlessly integrated tape component for long-term retention of data. With the Data Protection Manager agents installed on all Hyper-V hosts, Data Protection Manager will be aware of all the Hyper-V hosts and the virtual machines running on them and they can be added to a protection group. Planning Protection Groups Protection Groups can be designed in multiple ways to achieve the desired Recovery Time Objective (RTO) and Recovery Point Objective (RPO). Examples include: Create protection groups for all VMs comprising a particular workload (i.e. all the VMs that comprise a virtualized Microsoft Office SharePoint Services farm Create protection groups for all VMs comprising a particular enterprise service such as Web servers Create protection groups mapped to data priority (i.e. all VMs holding financial data) Create protection groups for only the application data inside the VM and not the entire VM itself by placing Data Protection Manager agents inside the VMs and backing up only the application data o o The entire guest can be protected as a VM, using the VSS Writer in the virtualization host Application data within the guest can be separately protected, using each application s VSS Writer For each workload that runs within a VM, determine whether it will be protected as part of the VM using a Data Protection Manager agent installed 10

11 on the host machine, or whether its data will be protected separately by a Data Protection Manager agent on the guest OS within the VM. If the data will be protected as part of a VM, there is no need to also separately protect it: VM Protection Options Data Protection Manager Agent Placement What Is Protected What Is Not Protected Recovery Granularity Protect entire VM On VM host Entire system: all applications, files, system state, and OS; VM configuration Pass-through disks that are attached to guest VMs; deploy a Data Protection Manager agent into the VM to protect these Entire VM can be recovered, or individual files, folders or volumes using ILR Protect application data within the VM On VM host and on each guest with data that requires protection Data types that Data Protection Manager supports. Data types that are not supported by Data Protection Manager Discrete application data may be separately recovered With the above decisions made per workload and VM, protection groups can be designed along the dimensions outlined above (workload, service, priority, etc.). Planning Protection Group Storage Once the decisions are made in terms of what aspects of the virtualized workload will be backed up and the design concept for storage groups has been selected, planning for the storage and protection policies for each protection group can begin. Planning for the storage required to protect virtual workloads is a challenging topic and is impacted by the decision of whether to protection the entire VM or just the data within the VM. Calculating storage requirements for protecting virtual workloads is challenging due the fact that the data is stored on VHD files and in cases where the entire VM is being backed up, the calculations must include the OS volumes and changes that may occur on the VM system volume VHD and thus backed up. Very early on in the Proof of Concept (PoC) or Pilot phases it is recommended 11

12 to start protecting a subset of the planned virtual workloads to gather real world metrics for the rate of data change to be used in planning the overall storage requirements. Due to the ease with which virtual machines can be commissioned as compared to physical servers, a higher storage growth rate assumption should be utilized that would otherwise be the case, particularly if the strategy of backing up the entire VM is being widely utilized. As an example, an administrator could very easily instantiate 10 new virtual machines, each with an OS volume of 20 GB which could result in a requirement for 400 GB (10*20*2) of Data Protection Manager storage. Planning Disaster Recovery A Data Protection Manager server can back up other Data Protection Manager servers. A Data Protection Manager server that protects data sources directly is called the primary Data Protection Manager server. A Data Protection Manager server that protects other Data Protection Manager servers is called the secondary Data Protection Manager server. In Data Protection Manager 2007 SP1, you can protect only the primary Data Protection Manager server with a secondary Data Protection Manager server. The Data Protection Manager 2010 allows more complex and cost-effective disaster recovery scenarios through cyclic protection and chaining. Cyclic protection enables two Data Protection Manager servers to protect each other, and is typically aimed at smaller architectures, such as in a branch office. Chaining allows you to create a chain of Data Protection Manager servers in 12

13 which each server protects the next server in the chain. In Data Protection Manager 2010, a secondary Data Protection Manager server can be used to protect the following: The databases in the instance of SQL Server on the primary Data Protection Manager server. All local volumes and application data on the primary Data Protection Manager server. All replicas on the primary Data Protection Manager server that are directly protected by primary Data Protection Manager server. Before you configure secondary protection for your servers, you must ensure that the Data Protection Manager server or selected Data Protection Manager servers are not being protected by other Data Protection Manager servers. Before you can protect the replicas and database of the primary Data Protection Manager server, you must start the Data Protection Manager Writer and SQL Server VSS Writer services on the primary Data Protection Manager server. Installing and Configuring Data Protection Manager 2010 A Data Protection Manager 2010 Beta installation comprises two primary tasks: 1. Installing the Data Protection Manager pre-requisite software 13

14 2. Installing the Data Protection Manager application. Hardware Requirements The following table shows the minimum recommended hardware requirements for a Data Protection Manager 2007 installation. In a production environment, greater hardware requirements might be required for your servers. Component Minimum Requirement Processor Memory Disk space for Data Protection Manager installation Disk space for storage pool 1 GHz or faster; 2.33 GHz quad-core CPU recommended Minimum 521 MB; 4 GB recommended System volume: 1 GB Data Protection Manager installation location: GB Database files drive: 900 MB 1.5 times the size of the protected data Software Requirements Operating System Requirements Windows Server 2008 (Standard and Enterprise x64-bit editions) Windows Server 2008 R2 (Standard and Enterprise editions) SQL Server Requirements SQL Server version SQL Server 2008 (Standard or Enterprise Edition) Software Prerequisites The Data Protection Manager 2010 installation will guide you through the installation of the following prerequisites: Windows PowerShell 2.0 Note Versions of PowerShell 1.0 and 2.0 cannot coexist on the same computer. You must remove PowerShell 1.0 before installing Data Protection Manager. The Data Protection Manager installation wizard will prompt you to install PowerShell 2.0. Microsoft.NET Framework 3.5 with Service Pack 1 (SP1) Windows Installer (MSI)

15 Windows Single Instance Store (SIS) Note: You must restart the computer to complete the installation of the prerequisite software. After restarting the computer, restart Data Protection Manager Setup. Installing Data Protection Manager 2010 Log on to the Data Protection Manager server using a domain user account that is a member of the local administrators group. If you are installing Data Protection Manager from a network share, browse to the installation share, and then double-click Setup.exe in the root folder of the share. 1. On the Microsoft System Center Data Protection Manager 2010 screen, click Install Data Protection Manager. 2. On the Microsoft Software License Terms page, review the license agreement. If you accept the terms, click I accept the license terms and conditions, and then click OK. After you click OK, Data Protection Manager installs the Visual C++ Redistributable 2008 package and Microsoft.NET Framework 3.5 SP1 if they have not already been installed. 3. On the Welcome page, click Next. Data Protection Manager begins a prerequisites check for all required hardware and software. 4. On the Prerequisites Check page, wait while Data Protection Manager Setup checks the system to verify that it meets the software and hardware requirements. If all required components are present, Data Protection Manager Setup displays a confirmation. Click Next to continue. If one or more required or recommended components are missing or noncompliant, Setup displays a warning or error message. On the Prerequisites Installation page, Data 15

16 Protection Manager setup installs any prerequisite software required for setup. The Data Protection Manager Setup Wizard will indicate if a restart is required to complete the installation. If a restart is required, restart the Data Protection Manager server and start Data Protection Manager Setup again. 5. On the Product Registration page, enter your registration information. 6. On the Installation Settings page, in the DPM Program Files section, accept the default folder, or click Change to browse to the folder to which you want to install Data Protection Manager. You can install Data Protection Manager only on a local drive, and you cannot install it in read-only folders, hidden folders, or directly to local Windows folders such as Documents and Settings or Program Files. (Data Protection Manager can, however, be installed to a subfolder of the Program Files folder.) 7. On the Installation Settings page, in the SQL Server settings section, specify whether you want to install the MSDPMV3Beta1Eval instance of SQL Server 8. On the Security Settings page, specify and confirm a strong password for the restricted MICROSOFT$DPM$Acct and DPMR$<computer name> local user accounts, and then click Next. For security purposes, Data Protection Manager runs SQL Server and the SQL Server Agent service under the MICROSOFT$DPM$Acct account, which Data Protection Manager Setup creates during the Data Protection Manager installation. To securely generate reports, Data Protection Manager creates the DPMR$<computer name> account. 9. On the Microsoft Update Opt-In page, specify if you want to sign up for the Microsoft Update service, and then click Next. 10. On the Summary of Settings page, review the summary of installation settings. To install Data Protection Manager using the specified settings, click Install. To change the settings, click Back. After the installation is complete, the Installation page displays the installation 16

17 status. 11. Click Close, and then restart the computer to incorporate all of the Data Protection Manager Setup changes. 12. Restart the Data Protection Manager Server. After you install Data Protection Manager 2010, you must perform the following tasks before you can start protecting your data. 1. Add a Disk to the Storage Pool. For information about installing disks to the Storage Pool, see Adding Disks to the Storage Pool ( 2. Install protection agents on the computers you want to protect. a. On the protected computer, if the firewall is turned on, click Attach Agents, and then install the agent manually. For information about installing the agent manually, see To install the protection agent manually on a target computer in this topic. b. On the protected computer, if the firewall is turned off, click Install Agents to install the agent on the protected computer. c. Create the protection groups. d. Upgrading an agent from Data Protection Manager 2007 SP1 to Data Protection Manager 2010 may show that a restart is required. Prerequisites for protecting Hyper-V using Data Protection Manager 2010 Before protecting Hyper-V virtual machines with Data Protection Manager, ensure that you have met the following prerequisites before protecting Windows Hyper-V: 1. On the Data Protection Manager server, you must do the following to enable item-level recovery (ILR): Install Windows 2008 Server SP2 or Windows Server 2008 R2 with the RTM version of Hyper-V 17

18 Install the Hyper-V role on the DPM server ( Note Data Protection Manager continues to protect Hyper-V virtual machines even if the Hyper-V role is not installed on the Data Protection Manager server. However, you cannot do an ILR unless the Hyper-V role is enabled. 2. On the Hyper-V host: Install the Microsoft Hyper-V prerequisites ( or Microsoft Windows Server 2008 SP2 or Windows Server 2008 R2. Install the Hyper-V updates ( These updates are cumulatively available in Hotfixes and Security Updates in Windows Server 2008 SP2 and Windows Vista SP2 ( For CSV deployment, install the VSS hardware provider on the host computer Install the integration components on the guests. For more information, see Install a Guest Operating System ( Deploying Data Protection Manager Agents Before you can start protecting data, you must install a protection agent on each computer that contains data that you want to protect. After the protection agent is installed on the computer, the computer is referred to as a protected computer in the Management task area. However, the data sources on the computer are not protected until you add them to a protection group. Agents can be deployed several different ways: Deploying protection agents behind a firewall Deploying directly from the Data Protection Manager Administrator Console 18

19 Deploying via standard software distribution methods (Microsoft Systems Management Server, System Center Configuration Manager, etc.) Deploying manually Deploying Data Protection Manager Agents Behind a Firewall If you want to install protection agents on computers that reside behind a firewall, such as servers with the Windows Firewall enabled, Data Protection Manager provides an executable file named DPMAgentInstaller.exe that performs the following: Installs the protection agent prerequisites and the Data Protection Manager protection agent. Configures the target computer to receive commands from the specified Data Protection Manager server name. Configures the firewall to allow communication to come in. To install a protection agent on a server behind a firewall: 1. On the computer on which you want to install the protection agent, from the Windows command prompt, from the Agents folder, type DpmAgentInstaller.exe <Data Protection Manager server name> 2. On the Data Protection Manager server, from the Data Protection Manager Management Shell prompt, type Attach- ProductionServer.ps1 <Data Protection Manager server name> <production server name> <user name> <password> <domain> The password parameter is not required and we recommend that you do not provide it. Data Protection Manager will prompt you for a password, which will not appear on the screen. However, you can provide the password if you want to use the script to install a protection agent on a large number of computers. Note If you are attaching the protected computer on a different domain, you must specify the fully qualified domain name. For example, Computer1.Domain1.corp.microsoft.com, where Computer1 is the name of the protected computer, and Domain1.corp.microsoft.com is the domain to 19

20 which you are attaching the computer. The required configurations to protect the server are created. Data Protection Manager Administrator Console will now display the protected server. To display the correct protection agent status, in the Monitoring task area, on the Jobs tab, click Refresh Job. Installing the protection agent manually To install a protection agent manually: 1. On the computer on which you want to install the protection agent, we recommend that you map a network drive to the Data Protection Manager server. For example, at the command prompt type net use Z:\\DPM1\c$. 2. On the protected computer, at the command prompt, perform the following steps: a. Change the directory to <drive letter>:\program Files\Microsoft DPM\DPM\ProtectionAgents\RA\3.0.<build number>.0\i386 If you have a 64-bit computer, replace i386 with AM64. b. Run DpmAgentInstaller.exe <Data Protection Manager server name>. For example, type: DPMAgentInstaller.exe DPM1.Fully.qualified.domain OR On a 64-bit computer, type: DPMAgentInstaller_x64.exe <DPM server name>. Creating Protection Groups and Protecting VMs This section illustrates how to create protection groups in Data Protection Manager 2010 and set the protection options for all of the resources included in the protection group. The procedure to protect virtual machines deployed on a CSV and regular shared disk in a failover cluster are the same. Screenshot Procedure 20

21 In Data Protection Manager Administrator Console, click Protection on the navigation bar. In the Actions pane, click Create protection group. The Create New Protection Group Wizard appears. Review the Welcome page, and then click Next. Expand the cluster node to see the virtual machines that are hosted on the failover cluster. Select the virtual machines that you want to include and then click Next. Enter a name for the protection group and select whether to protect the group on disk, tape, or both. Click Next. Select the retention range and set the application recovery points. Click Next. 21

22 Review the disk space allocations. Click Next. Choose the replica creation method. Click Next. Review the summary page then click Create Group. If you elected to have Data Protection Manager immediately create a replica, you can monitor the status of the replica creation by selecting the Monitoring tab and locating the running job. Upon completion, if you select the Protection tab, you should see the newly created protection group as well as the replicas that were created. If you elected not to immediately create replicas, you will see the protection group only until the replicas are created, according to the schedule you specified. 22

23 Recovering Virtual Machines Supported Scenarios Data Protection Manager 2010 supports the following recovery scenarios: Scenario Description Recovering a virtual machine to its original location. Recovering a virtual machine to an alternate location Item-level recovery (ILR) of Hyper-V virtual machines The original VHD is deleted. Data Protection Manager will recover the VHD and other configuration files on the original location by using the Hyper-V VSS writer. At the end of the recovery process, virtual machines will still be highly available. The resource group must be present for recovery to happen. If the resource group is not available, recover to an alternate location and then make the virtual machine highly available. Data Protection Manager supports alternate location recovery (ALR), which provides a seamless recovery of a protected Hyper-V virtual machine to a different Hyper-V host, independent of processor architecture. Hyper-V virtual machines that are recovered to a cluster node will not be highly available. For more information about how to make a virtual machine highly available, see Make the virtual machine highly available ( Data Protection Manager supports item-level recovery (ILR), which allows you to do granular recovery of files, folders, volumes, and virtual hard disks (VHDs) from a host-level backup of Hyper-V virtual machines to a network share or a volume on a Data Protection Manager protected server. The Data Protection Manager protection agent does not have to be installed inside the guest to perform item-level recovery. Recovering a Virtual Machine to Its Original Location The procedure to recover a virtual machine to its original location is the same as with any other data source. For more information, see Recovery Wizard ( Recovering a Virtual Machine to an Alternate Location In the event of disaster recovery, Data Protection Manager 2007 allows you to recover virtual machines as files to a network folder. You can then copy those 23

24 files to an alternate Hyper-V host server. However, to start a virtual machine on an alternate Hyper-V host server, you have to manually create and configure the virtual machine using the recovered files. Now, Data Protection Manager 2010 supports alternate location recovery (ALR), which allows you to recover a Hyper-V virtual machine to an alternate stand-alone Hyper-V host or to a cluster. The recovered virtual machine is already registered and configured on an alternate Hyper-V host server. Note When you recover to an alternate clustered host, Data Protection Manager will not make the virtual machine highly available. You must do that using the Failover Cluster Manager. Data Protection Manager 2010 also supports alternate location recovery of Hyper-V virtual machines to a cluster both in a Cluster Share Volume (CSV) and Non-CSV environment. Recovering a Hyper-V virtual machine in a Cluster Shared Volumes (CSV) environment 1. In Data Protection Manager Administrator Console, click Recovery on the navigation bar. 2. Browse or search for the virtual machine listed under the cluster node that you want to recover. 3. Available recovery points are indicated in bold on the calendar in the recovery points section. Select the bold date for the recovery point that you want to recover. 24

25 4. On the Recoverable Items pane, click to select the virtual machine item that you want to recover. 5. In the Actions pane, click Recover. Data Protection Manager starts the Recovery Wizard. Review your recovery selection, and then click Next. 6. Select the type of recovery you would like to perform: Recover to original instance. Recover to network folder. Recover to an alternate location. Type the alternate location, or click Browse and, in the Specify Alternate Recovery Destination dialog box, select a recovery location. Click OK. In this type of recovery, Hyper-V virtual machines recovered to a cluster will not be highly available. To make it highly available, do the following: 1. Ensure that you are recovering a virtual machine to a specific folder in a CSV. The folder should have the following path: %SystemDrive%\ClusterStorage\Volume<Number> 2. Make the Hyper-V virtual machines highly available. For more information about how to make a virtual machine highly available, see Make the virtual machine highly available 25

26 ( Copy to tape. 7. Specify your recovery options, and then click Next. 8. The summary section of the recovery wizard lists the virtual machine to be recovered. Review your recovery settings, and then click Recover. Recovering a Hyper-V virtual machine in a non-csv environment 1. In Data Protection Manager Administrator Console, click Recovery on the navigation bar. 2. Expand the cluster node to see the virtual machines that are hosted on the failover cluster. Select the virtual machines that you want to recover. 3. Available recovery points are indicated in bold on the calendar in the recovery points section. Select the bold date for the recovery point you want to recover. 26

27 4. In the Recoverable item pane, click to select the recoverable item you want to recover. a. If you select the virtual machine on the left pane, the Recoverable Item list will show you the list of VHDs. If you do a recovery at this point, you are recovering a VHD and not the virtual machine. 5. In the Actions pane, click Recover. Data Protection Manager starts the Recovery Wizard. For more information about the Recovery wizard, see Recovery Wizard ( a. In a non-csv environment, the destination will be a volume on available storage in the cluster. 6. Make the Hyper-V virtual machines recovered to a cluster highly available. For more information about how to make a virtual machine highly available, see Make the virtual machine highly available ( Recovering to an alternate stand-alone Hyper-V host Data Protection Manager 2010 allows you to recover a Hyper-V virtual machine to an alternate stand-alone Hyper-V host: 1. In Data Protection Manager Administrator Console, click Recovery on the navigation bar. 2. Browse or search for the Hyper-V virtual machine that you want to recover from the list of Hyper-V computers. 3. Available recovery points are indicated in bold on the calendar in the recovery points section. 27

28 4. Select the bold date, and then the time from the drop-down list, for the recovery point you want to recover. 5. In the Recoverable item pane, click to select the recoverable item you want to recover. a. If you select the virtual machine on the left pane, the Recoverable Item list will show you the list of VHDs. If you do a recovery at this point, you are recovering a VHD and not the virtual machine. 6. In the Actions pane, click Recover. Data Protection Manager starts the Recovery Wizard. For more information about the Recovery wizard, see Recovery Wizard ( 28

29 7. You can now close the Recovery Wizard and view the recovery status in the Monitoring task area. a. If the recovered virtual machine was backed up in an online state, and it is saved state after recovery, delete the saved state of that virtual machine from the Hyper-V Manager Console and start it. b. After alternate location recovery always check whether the virtual machine s network configuration is correct. Item-Level Recovery for Hyper-V Data Protection Manager 2007 provides both host-based and guest-based protection for Hyper-V virtual machines. Data Protection Manager 2010 supports item-level recovery (ILR), which allows you to do granular recovery of files, folders, volumes, and virtual hard disks (VHDs) from a host-level backup of Hyper-V virtual machines to a network share or a volume on a Data Protection Manager protected server. You must have the Hyper-V role enabled on the Data Protection Manager server to perform item-level recoveries. During item-level recovery, Data Protection Manager has to mount the VHDs of the protected virtual machines. 29

30 Note Item-level recovery does not support recovery of an item to its original location. The following table lists supported and unsupported scenarios when recovering files, folders, volumes, and VHDs using ILR in a Hyper-V virtual machine. Scenario Volumes or files/folders recovery Virtual Hard Disk (VHD) recovery From a virtual machine that has snapshots Yes (Only to Windows Server 2008 R2) Yes Yes From a secondary Data Yes Protection Manager server From tape backups No Yes From NTFS volumes only Yes Not applicable From non-ntfs volumes No Entire VHD only From a VHD that is partitioned using dynamic disk partitioning No Entire VHD only Mount points cannot be traversed or browsed when exploring a VHD for item-level recovery. Item-Level Recovery of files and folders 1. In Data Protection Manager Administrator Console, click Recovery on the Actions pane. 2. Browse or search for the virtual machine name that you want to recover, and then select the item (VHD) from the Results pane. 3. Select the date from which you want to perform a recovery. Dates in bold indicate available recovery points. 4. To view the list of files and folders: a. Double-click the item (VHD) you want to recover on the Recoverable Items list. 30

31 b. Double-click the items (volumes in VHD) you want to recover on the Recoverable Items list. 5. Select the item (files and folders) you want to recover. You can select and recover multiple files/folders from the list. 6. In the Actions pane, click Recover to start the Recovery Wizard. For more information about the Recovery wizard, see Recovery Wizard ( a. Data Protection Manager saves files and folders in a custom directory structure in the following format <Recovery destination selected by user>\<vm name>_<backup Time stamp> with the exact file-system hierarchy on a protected server that has the Data Protection Manager agent installed. 31

32 Item-Level Recovery of volumes 1. In Data Protection Manager Administrator Console, click Recovery on the navigation bar. 2. Browse or search for the virtual machine name that you want to recover, and then select the item (VHD) in the Results pane. 3. Select the date from which you want to perform a recovery. Dates in bold indicate available recovery points. 4. To view the list of volumes, follow these steps: a. Double-click the item (VHD) you want to recover on the Recoverable Items pane. b. Select the item (volume in VHD) you want to recover. i. The list pane will display the volume label or Virtual Machine Volume if no volume label is available. ii. You cannot select and recover multiple volumes at the same time. 5. In the Actions pane, click Recover to start the Recovery Wizard. For more information about the Recovery wizard, see Recovery Wizard ( Item-Level Recovery of VHDs 1. In Data Protection Manager Administrator Console, click Recovery on the navigation bar. 2. Browse or search for the virtual machine name that you want to recover, and then select the item (VHD) in the Results pane. 3. Select the date from which you want to perform a recovery. a. Dates in bold indicate available recovery points. 4. On the Recoverable Items pane, select the item (VHD file) you want to recover. a. The path of the VHD file on the protected server is displayed in the Recoverable Item pane 32

33 b. During recovery, you cannot select multiple VHDs. 5. In the Actions pane, click Recover to start the Recovery Wizard. For more information about the Recovery wizard, see Recovery Wizard ( Note: When you are recovering a VHD of a virtual machine that has Hyper-V snapshots, archive virtual hard disk (AVHD) files will not be displayed in the Recoverable Items pane, but Data Protection Manager will recover the parent VHD and all the associated AVHD files. Data Protection Manager saves VHDs in a custom directory structure of the format DPM_<backuptime>\DPM_Recovered_At_<RecoveryTime>\<Path of the VHD on the protected server> with the exact file-system hierarchy on a protected server that has Data Protection Manager agent installed. Troubleshooting Hyper-V Item-Level Recovery The following table provides guidance for troubleshooting issues that may occur when you during item-level recovery (ILR): Issue Possible Cause Resolution Alert ID: VHD parent locator fixup fails (3130) See the Alert Details pane for more information about the cause of this alert. Possible causes include: The Hyper-V role is not installed in the Data Protection Manager server. A Windows Management Instrumentation (WMI) call to fix the parent locator of the VHD has failed. The error conditions and recommended actions associated with the VHD parent locator fixup fails alert are provided in the alert details. You can recover a VHD and a virtual machine. However you cannot recover volume, files, or folders. Follow the recommended action in the alert to retry the job. Note: No action is required if you are not performing an ILR using the existing recovery point. 33

34 To resolve this alert: 1. Install the Hyper-V role on the Data Protection Manager server. 2. Create a new recovery point. 34

35 2010 Microsoft Corporation. All rights reserved. MICROSOFT CONFIDENTIAL. The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication and is subject to change at any time without notice to you. This document and its contents are provided AS IS without warranty of any kind, and should not be interpreted as an offer or commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented. The information in this document represents the current view of Microsoft on the content. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED, OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT. The descriptions of other companies products in this document, if any, are provided only as a convenience to you. Any such references should not be considered an endorsement or support by Microsoft. Microsoft cannot guarantee their accuracy, and the products may change over time. Also, the descriptions are intended as brief highlights to aid understanding, rather than as thorough coverage. For authoritative descriptions of these products, please consult their respective manufacturers. 35