This article explains which Hyper-V best practice items to control I/O operations and improve the performance of Hyper-V and Virtual machines.
Hyper-V Network Virtualization technology, sometimes referred as HNV, is primarily designed to be used by the hosting providers, but every SMB should know the benefits offered by HNV.
In Part 1 and Part 2 of this article series, we focused on the various conditions which might cause Hyper-V Replication to fail. In the final part of this article series, we’ll tackle the remaining issues I’ve listed which may cause issues in Hyper-V replication.
Starting with Windows Server 2012 R2, it is possible to re-size a Virtual Hard Disk for a running Virtual Machine on Hyper-V! It was not possible to do so before for an online Virtual Machine running on Windows Server 2012 and earlier Hyper-V versions. Let’s have a look at some of the benefits this feature offers and requirements before you dive in and use it.
In Part 1 of this series, we learned about the different possibilities which may cause communication issues between Primary and Replica Server. In this part, we continue to focus on other possibilities and also explain a mechanism which can be used to rule out network port or firewall issues.
Troubleshooting issues with the Hyper-V Replica requires extensive knowledge of the technology. Not only you need to have knowledge but you must also be able to follow a troubleshooting approach which helps you fix the issues and also benefits in finding the root cause. This is what I intend to explain throughout the articles of “Advanced Troubleshooting of Hyper-V Replica” series.
As explained in the previous parts of this article series, we can use Hyper-V Manager to get detailed information about the replication health which includes replication statistical data. The replication health data not only help in troubleshooting the issue but also helps in finding the root cause.
In Part 1 of this article series, we saw how to check replication health status of virtual machines using Hyper-V Manager and the different health status a virtual machine can enter into. In Part 2, we’re going to explain in detail the different replication health status (Warning and Critical) a virtual machine can enter into and also point out the differences between “Critical” and “Warning” replication health status.
Hyper-V Replica provides built-in tools and utilities to do a health check for Hyper-V Replication. There are a number of ways to check Hyper-V Replication health but two easiest way to check status of replication of virtual machines are using the “Hyper-V Manager” snap-in and Hyper-V Replica PowerShell modules.
There are two topics I’m going to explain in this article (1) why you can’t relocate paging file to a Virtual Hard Drive connected to a SCSI Controller in Hyper-V running on Windows Server 2012 and earlier versions and (2) how you can utilize the new booting architecture introduced in Windows Server 2012 R2 to relocate paging file to a SCSI Controller.
Hyper-V Replica is a new feature introduced in Windows Server 2012. It is a disaster recovery solution designed for small and medium sized businesses. Using Hyper-V Replica, the virtualized workloads can be replicated from the Production to disaster recovery site. In case of any disaster, the virtualized workloads can be brought online at Replica Server which is running in a disaster recovery site. In Windows Server 2012 R2, Microsoft enhanced Hyper-V Replica feature to replicate virtualized workloads to a second disaster recovery site but I’m not going to talk about this here.
In my recent post series on Hyper-V Replica I provided a general overview of Hyper-V Replica technology and some basic steps to configure and enable Hyper-V Replica in a production environment. In this article, we’re going to learn how Hyper-V Replica actually works and what all components have been included to implement the replication functionality. This article explains the basic functionality of Hyper-V Replica components in a non-clustered environment. It does not explain the Hyper-V Replica Broker role which is used when the Hyper-V Replica is operating in a cluster environment.
We have a newer and more detailed over of replication in Hyper-V and Hyper-V Replica if you want to check that out. In this article, we are going to learn about the types of failover which are available with Hyper-V Replica. The concept of Hyper-V Replica starts from learning how to enable Hyper-V Replica on a Hyper-V Server to how to configure a virtual machine for replication. But that is just how to enable and configure Hyper-V Replica. There is much more to talk about, for example how different types of failover are available and how to use them. When you need to bring a virtual machine online at Replica Site, you use something called “failover”. There are three types of failover available with Hyper-V Replica as listed below: Test Failover Planned Failover Unplanned Failover Test Failover Test Failover, as the name suggests, can be used to test the… Read More»
We have a newer and more comprehensive article about Hyper-V Replica and the function of replication that you might want to check out. In this article we are going to learn why Hyper-V Replica is not a replacement for virtual machine backup products. Many systems administrators think that Hyper-V Replica can be used in a scenario where there is no need to use a backup product for virtual machines running on Hyper-V but that is misunderstood and that is what we’re going to clear this misconception in this article. Hyper-V Replica component is designed to provide “disaster recovery” services for the virtual machines running on Hyper-V 3.0. In a general disaster recovery environment, one set of services is running in production and another set of services are running in a disaster recovery site. Generally, services running at disaster recovery do not provide any services to clients. In case of any… Read More»