Windows Server 2012 Beyond Virtualizationadvancedtechnologysupportinc.com/website/labfiles/manuals...• New in Windows Server 2012 Hyper -V Role • Storage and Workload agnostic
Windows Server 2012 Beyond Virtualization Hyper-V Replica
What is Hyper-V Replica?
Why should I care?
Technology Overview
Demo
Next Steps
Hyper-V Replica What is it?
What is Hyper-V Replica? A virtual machine level replication solution which efficiently replicates data over a LAN/WAN to a remote (Replica) site without relying on software or hardware technologies outside of the Windows Server 2012 operating system
• New in Windows Server 2012 Hyper-V Role • Storage and Workload agnostic • Servers can be standalone or members of a Failover Cluster • Servers can be members of a workgroup or a domain (same or
different); Primary and Replica servers do not need to be in the same domain unless part of a Failover Cluster
• Managed locally (Hyper-V Manager) or remotely (Hyper-V Remote Server Administration Tools (RSAT) or System Center Virtual Machine Manager (SCVMM)
• 4 Deployment Scenarios • Head Office and Branch Office (HO-BO) • Enterprise Datacenter • Hosting Provider Datacenter • Customer Office and Hosting Provider Datacenter (Cross-
Premise)
Presenter
Presentation Notes
What Is Hyper-V Replica? Hyper-V Replica enables organizations using Windows Server 2012 to implement an affordable Business Continuity and Disaster Recovery (BCDR) solution for virtualized workloads without using 3rd-party technology. This allows virtual machines running at a primary site to be efficiently replicated to secondary location (Replica site) across a WAN link. In this discussion, we define two “sites”: the “primary site,” which is the location where the virtualized environment normally operates; and the “Replica site,” which is the location of the server that will receive the replicated data. At the primary site, the primary server is the physical server that hosts one or more primary virtual machines. At the Replica site, the Replica server similarly hosts the Replica virtual machines. Hyper-V Replica provides a storage-agnostic and workload-agnostic solution that replicates efficiently, periodically, and asynchronously over IP-based networks, typically to a remote site. It is simple to configure and does not require either shared storage or any particular storage hardware. Any server workload that can be virtualized in Hyper-V can be replicated. Replication works over any ordinary IP-based network, and the replicated data can be encrypted during transmission. (continued on next hidden slide)
Hyper-V Replica Why should I care?
Why should I care?
Hyper-V Replica provides an efficient, cost-effective solutions…
• Allows a Hyper-V administrator to execute a failover of production workloads to replica servers at a secondary location within minutes (in the event of fire, power outage, server failure, etc.)
• Provides the necessary management APIs to enable IT management vendors to build an enterprise class Disaster Recovery solution for customers
• Enables Infrastructure as a Service (IaaS) for hosting providers that host dedicated/virtual servers for customers
• Seamlessly integrates with Clustering and Volume Shadow Services (VSS) • Supports heterogeneous storage between primary and recovery
The challenge… • Provide business continuity and minimal downtime of virtualized servers during
times of disruption
Presenter
Presentation Notes
Organizations need business continuity and minimal downtime of virtualized servers during times of disruption. Hyper-V Replica allows a Hyper-V Administrator, in the event of a failure at a primary site (e.g. fire, natural disaster, power outage, server failure etc…), to execute a failover of production workloads to replica servers at a secondary location within minutes, thus incurring minimal downtime. The configurations at each site do not have to be the same with respect to server or storage hardware. Hyper-V Replica provides a System Administrator the option to restore virtualized workloads to a point in time depending on the Recovery History selections for the virtual machine. Hyper-V Replica provides the necessary management APIs that enable IT management vendors to build an enterprise class Disaster Recovery (DR) solution for their customers. Hyper-V Replica enables Infrastructure as a Service (IaaS) for hosting providers that host dedicated/virtual servers for their customers. With Hyper-V Replica, Hosters can provide solutions that offer DR as a service to their customers (specifically Small and Medium Business (SMB) customers).
Hyper-V Replica Technical Overview
Installation Requirements
• Hardware that supports the Hyper-V Role on Windows Server 2012 • Sufficient storage on both Primary and Replica servers to host the files used by
virtualized workloads • Network connectivity between the locations hosting the Primary and Replica
servers • Properly configured firewall rules to permit replication between the Primary and
Replica sites • An X.509v3 certificate to support Mutual Authentication with certificates (if
desired or needed) • For detailed certificate requirements, see
You can set up replication of Hyper-V virtual machines as long as you have any two physical Windows Server 2012 servers which support the Hyper-V role. To take advantage of the Hyper-V Replica the following prerequisites must be met: Hardware that supports the Hyper-V Role on Windows Server 2012 Sufficient storage on both the Primary and Replica servers to host the files used by virtualized workloads Network connectivity between the locations hosting the Primary and Replica servers Properly configured firewall rules to permit replication between the Primary and Replica sites An X.509v3 certificate to support Mutual Authentication with certificates (if desired or needed). If you plan to use certificate-based authentication (required for the replicated data to be encrypted during transmission), you will need an appropriate certificate, which can either be local and self-signed, or supplied by a certificate server in your deployment.
1. Add Hyper-V role on Primary and Replica servers • Add Role and Feature Wizard (ARFW) in Server Manager • Deployment Image and Service Management (DISM)
• Server Manager Powershell cmdlet Install-WindowsFeature –Name Hyper-V –IncludeManagementTools
Presenter
Presentation Notes
To add the Hyper-V Role to a server installation, use the Add Role and Feature Wizard (ARFW), which is part of Server Manager or use the Deployment Image and Servicing Management (DISM) command line tool. A reboot is required. This can occur automatically if the installation is being executed in the Server Manager interface by checking a box (Restart each target machine automatically if needed) in the wizard (Confirmation screen). This allows the server to reboot, if needed. When adding the Hyper-V Role using the ARFW, there is an opportunity to create Virtual Switches in Hyper-V. This step can be accomplished in the wizard when installing the Role or it can be done afterwards using the Hyper-V Manager interface. You can allow the Hyper-V server to receive Live Migrations and specify the default location for virtual hard disks and virtual machine configuration files. The Hyper-V Role can also be installed from the command line interface by using the Deployment Image and Service Management (DISM) command line tool. At a command prompt, type: dism /online /enable-feature /featurename: Microsoft-Hyper-V. A reboot is required to complete the installation. The Server Manager PowerShell cmdlet Install-WindowsFeature can also be used. Once the installation is completed (following a reboot of the server), the Hyper-V role will show as installed in Server Manager and the Hyper-V Manager will be listed under Administrative tools. To verify proper functioning of Hyper-V, run the Hyper-V Best Practices Analyzer (BPA) and then create a new virtual machine and verify it starts correctly. Hyper-V Replica settings are configured in the Hyper-V Manager interface for standalone Hyper-V servers and the Failover Cluster Manager interface for Hyper-V Failover Clusters. Run the Enable Replication Wizard. Replication is configured on a per virtual machine basis.
Architectural Components
Presenter
Presentation Notes
Hyper-V Replica tracks the write operations on the primary virtual machine and then replicates these changes to the Replica server over a WAN. The network connection between the two servers uses the HTTP protocol and supports Kerberos authentication and certificate-based authentication, with optional support for encryption. Hyper-V Replica is closely integrated with failover clustering in Windows Server 2012, and it provides nearly seamless replication across different migration scenarios in the Primary and Replica servers. This allows virtual hard disks to be stored in a different location to enable recovery in case the data center goes down due to natural disaster or other causes. Component/Purpose Replication Engine: The Replication Engine, in many respects, is the 'heart' of Hyper-V Replica. It manages the replication configuration details and handles initial replication, delta replication, failover, and test-failover operations. It also tracks virtual machine and storage mobility events and takes appropriate actions as needed (i.e., it pauses replication events until migration events complete and then resumes where they left off) Change Tracking: The Change Tracking module provides a virtual machine level change tracking mechanism on the Primary server by keeping track of the write-operations, which happen in the virtual machine. This component is designed in such a way that it makes the scenario work irrespective of where the virtual machine VHD file(s) resides; VHD files can be hosted on Direct Attached Storage (DAS), a SAN LUN, an SMB share on a File Server, or a Cluster Shared Volume (CSV). (Continued on next hidden slide)
Hyper-V Replica DEMO
Windows Server 2012 Product Download http://aka.ms/hwws2012
System Center 2012 Evaluation Download http://aka.ms/hwsc2012
