Sharing of thoughts and information is what blogging is all about. This way we can learn from each other. Post A Comment!These postings are provided "AS IS" with no warranties, and confers no rights. You assume all risk for your use.
Anthony Bartolo Twitter | LinkedIn
Pierre Roman Twitter | LinkedIn
As mentioned in previous posts, now that #CANITPRO Camp V2 is in play, labs from version 1 are being converted into Step-By-Step posts to be provided as a resource to IT Professionals. One of the labs conducted in version 1 of the camps was Virtual Machine replication using Hyper-V Replica.
New to Windows Server 2012, Hyper-V Replica is an asynchronous, virtual machine replication technology designed for business continuity and disaster recovery. With Hyper-V Replica, one can replicate a virtual machine from one location to another simple utilizing Hyper-V and a network connection. Hyper-V Replica works with any server network and/or storage vendor and provides unlimited replication capability out of the box.
Benefits achieved by to your organization include:
Hyper-V Replica can be utilized on hardware certified for Windows Server 2012. The following prerequisites are required to take advantage of Hyper-V Replica included as part of the Hyper-V server role
Enabling Replication on the Replica Server
Note: Replica Server AuthorizationAfter deciding authentication types, specification of which primary servers are permitted to replicate virtual machines to your Replica server is required. Authorization can be allowed from any authenticated server, or a specified primary server. Hyper-V Replica allows the option to designate a specific location to store your recovery virtual machine files in either case via a SAN, SMB file server, or using direct-attached storage.
Note: Properly configured firewall rules permit replication between the primary and Replica servers and sites. To allow any incoming virtual machine replication traffic for configured replication ports, you must ensure an inbound firewall rule is created.
Replication Firewall Rules
Properly configured firewall rules permit replication between the primary and Replica servers and sites. To allow any incoming virtual machine replication traffic for configured replication ports, you must ensure an inbound firewall rule is created.
Initial Virtual Machine Replication
An initial copy of all your virtual hard disks (VHDs) must be transferred to the Replica server (at your Replica site) before using Hyper-V Replica.
Click Send initial copy over the network and Start replication immediately then Click Next
Hyper-V Replica Failover Operations
Hyper-V Replica is designed to help both planned (scheduled events) and unplanned (disaster recovery) failover situations. Hyper-V Replica allows for fail over to a protected virtual machine on the Replica server at anytime. There are three main options you need to understand for failover operations.
Be sure to test in lab Virtual Machine Replication Using Hyper-V Replica for yourself by downloading Windows Server 2012, and Hyper-v Server 2012.
Thank you for the great presentation
Great post! But what about the ip settings will them also be transferred? How my clients on the primary site will access the virtual server on the replica site in case it fails?
Egberto - Hyper-V Manager provides the ability to configure the IP address that the Replica virtual machine should use in the event of failover.