Category: Failover Cluster
-
Enable Hyper-V Server 2012 R2 Core Virtual Machine Protection using existing Azure Site Replication Policy.
In this post, I’ll be writing about my steps for enabling on premise Virtual Machine protection to Azure Site Recovery using an existing Hyper-V Site Replication policy. In this deployment, I’ll be adding and registering a Hyper-V Core Server 2012 R2 to Azure Site Recovery. The process differs from the steps in registering a full…
-
Moving a Hyper-V Virtual Machine Storage to a Cluster Volume using PowerShell.
I have a Virtual Machine ADS00 running a guest OS WS 2012 R2 .It’s vhdx file is located on a Failover Cluster node physical server running Hyper-V Core 2012 R2. As the services offered and requirements for this VM continued to scale, we decided to migrate it to the Cluster volume and make it highly…
-
Resolving Windows Server 2012 Failover Cluster Kerberos Security Issue – Invalid DNS Error
I’ve been running Windows Server 2012 Failover Cluster for about a year and it’s been stable up until now. Recently, I encountered an issue where Live migration of VMs failed across all hosts in the cluster. In addition, the Failover Cluster Manager started displaying the following error: Cluster network name resource ‘Cluster Name’ failed registration…
-
Configuring Windows Server 2012 as an iSCSI Target SAN in a Two Host Failover Cluster Part 5
As it turns out, I already have two Virtual machines running on one of the cluster nodes. I set these up before the cluster creation. The VMs are currently not cluster roles/resources. I will go ahead and make one of the VMs (WK7) a cluster role by adding it to the cluster. PS C:\> Get-VM…
-
Configuring Windows Server 2012 as an iSCSI Target SAN in a Two Host Failover Cluster Part 4
Here we go over my steps for the actual cluster creation, cluster and node validation, quorum setup and cluster shared volume configuration.We have by running a cluster validation on each node. This can be achieved with the following cmdlets: Test-Cluster -Node hyperv01 Test-Cluster -Node hyperv03 In this case, the test passed. The process basically gives…
-
Configuring Windows Server 2012 as an iSCSI Target SAN in a Two Host Failover Cluster Part 3
In the next part of the series, we will create a simple 1GB iSCSI virtual disk, assign it to the already configured target and verify the disk is visible to the iSCSI initiators. New-IscsiVirtualDisk -Description “Witness Disk” -Path g:\iscsivirtualdisks\Witness00.vhd -Size 1GB -ComputerName labtarget -Verbose (Create the 1GB iSCSI virtual disk) Add-IscsiVirtualDiskTargetMapping -TargetName Target00 -Path g:\iscsivirtualdisks\Witness00.vhd…
-
Configuring Windows Server 2012 as an iSCSI Target SAN in a Two Host Failover Cluster Part 2
In this part of the series, we will configure two hosts as iSCSI initiators. The hosts have already been defined at the Target and ready to log on. Both hosts are running WS 2012 Hyper-v Core and I made sure to install the Failover Clustering and Hyper-v windows features. Following is a snapshot of the cmdlets available…
-
Configuring Windows Server 2012 as an iSCSI Target SAN in a Two Host Failover Cluster Part 1
We’re currently working on virtualizing a large number of our servers and going through the process of deciding whether to deploy a 3rd party SAN or WS 2012 iSCSI Target in production. In the meantime, I have gone ahead and deployed a basic iSCSI Target and Two host WS 2012 Failover cluster in the lab…
Chinny Chukwudozie, Cloud Solutions. 