Hyper-V 3.0 --- One-Way Replication between Non-Cluster Hosts on the same AD domain (part 4)

In Hyper-V 3.0, there is new exciting function as “Replica” that belong to be an asynchronous replication from one Hyper-V’s VM to another Hyper-V Server.
Its synchronization exists four types:
          1. non-cluster to non-cluster
          2. non-cluster to cluster
          3. cluster to non-cluster
          4. cluster to cluster
In the following lab, I will introduce how to do it on non-cluster environment.

Configure the firewall on Replica Server
To configure the firewall rules for Kerberos authentication, click Advanced settings link to open Windows Firewall with Advance Security Management in Control Panel/System and Security/Windows Firewall.In Windows Firewall with Advanced Security Management, click Inbound Rules next to select Hyper-V Replica HTTP Listener (TCP-In) and click Enable Rule

Configure the Replica server to receive replication
In Hyper-V Manager, click the Replica Server next to click Hyper-V Setting… link in the Actions panelIn the Hyper-V Settings dialog, click Replication Configuration Enabled as a Replica server in Server panel, select Enable this computer as a Replica server and User Kerberos (HTTP) check box in the Authentication and ports sectionIn the Authorization and storage section, select Allow replication from the specified servers radius button next to click Add… buttonIn Add Authorization Entry dialog, write down the individual primary server as vw-hyperv-01.dw.com by <FQDN> or the particular domain as *.dw.com by *.<Domain Name> in Specify the primary server field, designate the special location for storing replica files, and assign a name as Trust Group 01 with the trust group tag.Click OK button if we are finishedClick OK button if this reminding message “Inbound traffic needs to be allowed in the Firewall” has already been done.

Enable replication for VM on Primary serverIn Hyper-V Manager,  select a VM that want to be replicated next to click Enable Replication… link to launch the Enable Replication wizard.In Before You Begin page, click Next > buttonIn Specify Replica Server page, enter either NETBIOS or FQDN on Replica server field next to click Next > button In Specify Connection Parameters page, the port number and authentication type of the Replica server will automatically be populated if Remote WMI is enabled. So that keep the original setting about Compress the data that is transmitted over the network check box and then click Next > button.In Choose Replication VHDs page, clear the check box of some VHDs that we don’t want to replicate next to click Next > button In Configure Recovery History page, select Additional recovery points option, assign a number of additional recovery points to be stored, enable and change copy frequency for Replication incremental VSS next to click Next > buttonIn Choose Initial Replication Method page, select the initial replication method and schedule initial replication based on the decision next to click Next > buttonClick Finish button to complete the enable replication wizard (# 2)Due to we choose the initial copy over the network, the transmission traffic will begin to be high in the send of Primary Server or the receive of Replica Server.


Monitor replication health
In Hyper-V Manager of Replica Server, right-click the replicating VM next to select Replication and View Replication Health… in menu to launch the health report.In Replication Health dialog, it will show the current replication status and some statistics.Repeat the above steps on primary server and also can view replication health.

Perform a Test Failover on Replica Server
In Hyper-V Manager, right-click VM of Replica Server next to select Replication and Test Failover… in menuIn Test Failover dialog, choose a recovery point next to click Test Failover buttonSo does that will create a new VM with name ““<virtual machine name>-Test” as VM-MB-01-test and no connect to any network segment. In the moment, we will setup another virtual switch into this network adapter to avoid Server name conflict when it powers on. Then we need to confirm whether this VM can Start/Pause/Stop, and that any applications in the virtual machine run properly.If the Test VM function is normal, please right-click VM of Replica Server again next to select Replication and Test Failover… in menuClick Stop Test Failover buttonSo does that the Test VM will be deleted and its data will be discarded now.
In the next article, I will introduce the planned failover & unplanned failover on Hyper-V 3.0
See you next time!

Reference : 
(# 1) Configure your Replica server to receive replication traffic from specific primary server(s)
(# 2) In the moment, a dialog box appears and tell us replication enabled successfully. In this dialog, we can click Settings… button to configure network for VM on Replica Server. We can configure the same or different network setting so that the virtual machine will connect to our decided network after a failover to the Replica server.If click Close button, we have to manually configure the network setting for Replica VM because it doesn’t connect to any network on Replica Server by default.


<<<  Hyper-V 3.0 --- Copied VM is working in another Hyper-V 3.0 Server (part 3)

Hyper-V 3.0 --- Execute Planned Failover for Kerberos authentication on the same AD Domain (part 5) >>>

Hyper-V 3.0 --- Copied VM is working in another Hyper-V 3.0 Server (part 3)

In Hyper-V 2.0, we have to export VM so that we can re-create the VM and attach the VHD when disaster happens in the future. Before do the export VM, we also have to shutdown this VM so that the related Service in this VM will be stopped then. This mechanism is not smart and the function is less than VMWare Product.

Since Hyper-V 3.0 release, we just only point to the path with the associated VM files so that VM can be live after power on.
How to do it?
Copy the backup VM files to the default folder that store VM configuration files in Hyper-V 3.0 Server. (# 1)
Open Hyper-V Manager and click one Hyper-V Server that will locate his VM next to click Import Virtual Machine linkIn Before You Begin page, click Next > buttonIn Locate Folder page, click Browse… button
Select the specify path that with xml file next to click Select Folder buttonClick Next > button to go ahead next step if the folder containing the VM is rightIn Select Virtual Machine page, select the VM that will be imported next to click Next > buttonDue to the VM and its files have already been in the right place, we will choose Register option that just want to register VM’s unique ID with Hyper-V. After choosing the import type, click Next > button to go ahead the next step.So do that we will complete the Import Wizard.Now the imported VM will exist in this Hyper-V Server.
Start this VM by click Start link in Actions panelNext to click Connect … linkThe imported VM will be live and normal now.
Reference :(# 1) How to know the default path to store VM configuration files?
          In Hyper-V Settings, click Virtual Machine in Server item so that can see where it is.

<<<   Hyper-V 3.0 --- Create NIC Teaming after Hyper-V online (part 2)

 Hyper-V 3.0 --- One-Way Replication between Non-Cluster Hosts on the same AD domain (part 4) >>>

Microsoft Access Database Engine 2010 Redistributable --- No 64 bit ODBC Drivers in Windows 7 x64

In Windows 7 x64, the default Data Source(ODBC) will point to 64 bit DLL in “C:\Windows\System32”. If we want to run 32 bit Apps on 64 bit Windows 7, we need to use 32 bit ODBC Administrator Tool by launching “C:\Windows\SysWOW64\odbcad32.exe”. (# 1)

When we launch ODBC Data Source Administrator and want to configure Excel Files in User DSN tab,
we get an error message “Cannot find Microsoft Excel Driver (*.xls, *.xlsx, *.xlsm, *.xlsb) ODBC driver”.
Although I know use the different ODBC administrator to configure 32bit or 64 bit DSN setting (#  1), I don’t when 64 bit ODBC driver for Office 2010 miss. In my intuition, the solution is very simple that reinstall ODBC driver!
So I download AccessDatabaseEngine_x64.exe from Microsoft Download Center(# 2) and double-click this file for installing it. But the warming message show up “Cannot install it besides remove the 32 bit installation of Office products firstly”.I don’t want to follow its suggestion because it will spend more time to remove and reinstall Office.
I search Web information by Google and find out it can be resolve by adding passive switch. The full command line is AccessDatabaseEngine_X64.exe /passiveAfter finish the above command and redo the ODBC configuration, its function is normal now.

Reference :
(# 1) Unable to create DSN for Microsoft Office System Driver on 64-bit versions of Windows
(# 2) Microsoft Access Database Engine 2010 Redistributable