Missing guest in Failover Cluster

I have a 3 node Server 2012R2 Hyper-V failover cluster with 18 guests. Today, I migrated a guest from VMWare using my normal method to one of the nodes in the cluster. Upon completion I added a role to the cluster, the guest appeared in the list of available
Virtual Machines and completed successfully. However, I cannot locate the guest on the list of roles within the cluster.
If I connect to the individual node that I know the guest is on, using Hyper-V Manager, I can see the guest, but Failover Cluster Manager refuses to see it.
I have tried this on several workstations, no success.
Any ideas? I have used this same technique for all of the hosted guests without issue until now.
Thanks
Mike

Start with this, substituting names as necessary:
(Get-VM -ComputerName VMHOSTNAME -Name VMNAME).IsClustered
If that's false, then you'll have to re-add it as a cluster resource. I've never seen a clustered VM uncluster on its own, but that would appear to be what happened to you.
If it's true, then run this, again substituting as necessary:
Get-ClusterResource -Cluster CLUSTERNAME
What you're looking for is any mismatch of "Virtual Machine" types against "Virtual Machine Configuration" types. There should be a 1:1 ratio and you should be able to identify which VM goes with which VM Config. Again, I've never seen these become disjointed,
but it could happen.
Eric Siron Altaro Hyper-V Blog
I am an independent blog contributor, not an Altaro employee. I am solely responsible for the content of my posts.
"Every relationship you have is in worse shape than you think."

Similar Messages

Guest VM failover cluster on Hyper-V 2012 Cluster does not work across hosts

Hi all,
We are evaluating Hyper-V on Windows Server 2012, and I have bumped in to this problem:
I have a Exchange 2010SP2 DAG installed on 2 vms in our Hyper-V cluster (a DAG forms a failover cluster, but does not use any shared storage). As long as my vms are on the same host, all is good. However, if I live migrate or shutdown-->move-->start one
of the guest nodes on another pysical host, it loses connectivity with the cluster. "regular" network is fine across hosts, and I can ping/browse one guest node from the other. I have tried looking for guidance for Exchange on Hyper-V clusters but have not
been able to find anything.
According to the Exchange documentation this configuration is supported, so I guess I'm asking for any tips and pointers on where to troubleshoot this.
regards,
Trond

Hi All,
so some updates...
We have a ticket logged with Microsoft, more of a check box exercise to reassure the business we're doing the needful. Anyway, they had us....
Apply hotfix http://support.microsoft.com/kb/2789968?wa=wsignin1.0 to both guest DAG nodes, which seems pretty random, but they wanted to update the TCP/IP stack...
There was no change in error, move guest to another Hyper-V node, and the failover cluster, well, fails with the following event ids I the node that fails...
1564 -File share witness resource 'xxxx)' failed to arbitrate for the file share 'xxx'. Please ensure that file share '\xxx' exists and is accessible by the cluster..
1069 - Cluster resource 'File Share Witness (xxxxx)' in clustered service or application 'Cluster Group' failed
1573 - Node xxxx failed to form a cluster. This was because the witness was not accessible. Please ensure that the witness resource is online and available
The other node stays up, and the Exchange DB's mounted on that node stay up, the ones mounted on the way that fails failover to the remaining node...
So we then
Removed 3 x Nic's in one of the 4 x NIC teams, so, leaving a single NIC in the team (no change)
Removed one NIC from the LACP group on each Hyper-V host
Created new Virtual Switch using this simple trunk port NIC on each Hyper-V host
Moved the DAG nodes to this vSwitch
Failover cluster works as expected, guest VM's running on separate Hyper-V hosts, when on this vswitch with single NIC
So Microsoft were keen to close the call, as there scope was, I kid you not, to "consider this issue
resolved once we are able to find the cause of the above mentioned issue", which we have now done, as in, teaming is the cause... argh.
But after talking, they are now escalating internally.
The other thing we are doing, is building Server 2010 Guests, and installing Exchange 2010 SP3, to get a Exchange 2010 DAG running on Server 2010 and see if this has the same issue, as people indicate that this is perhaps not got the same problem.
Cheers
Ben
Name                   : Virtual Machine Network 1
Members                : {Ethernet, Ethernet 9, Ethernet 7, Ethernet 12}
TeamNics               : Virtual Machine Network 1
TeamingMode            : Lacp
LoadBalancingAlgorithm : HyperVPort
Status                 : Up
Name                   : Parent Partition
Members                : {Ethernet 8, Ethernet 6}
TeamNics               : Parent Partition
TeamingMode            : SwitchIndependent
LoadBalancingAlgorithm : TransportPorts
Status                 : Up
Name                   : Heartbeat
Members                : {Ethernet 3, Ethernet 11}
TeamNics               : Heartbeat
TeamingMode            : SwitchIndependent
LoadBalancingAlgorithm : TransportPorts
Status                 : Up
Name                   : Virtual Machine Network 2
Members                : {Ethernet 5, Ethernet 10, Ethernet 4}
TeamNics               : Virtual Machine Network 2
TeamingMode            : Lacp
LoadBalancingAlgorithm : HyperVPort
Status                 : Up
A Cloud Mechanic.

"Services and Applications" is missing from the Failover cluster manager menu

Hi,
I am not sure this is the right group for my question, but I couldn't find anything else more suitable.
In my Hyper-V installation (Windows 2012 Data Center), I am missing "Services and Applications". I am using Windows 8 to manage the cluster and I need this menu to import an existing VM into the cluster. How can I get this option or is there a
software that I need to install?
Thanks

Repost here: http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/threads
in the Hyper-V forum. You'll get a lot more help there.
This forum is for Virtual Server 2005.

Guest two node Failover Cluster with SAS HBA and Windows 2012 R1

Hi all, i have two IBM x3560 brand new servers with V3700 IBM Storage. The Servers are connected to the storage through four SAS HBA adabters (two HBA's on each server). I want to create a two node guest Fileserver Failover Cluster. I can present the
LUN's to the guest machines, but when i 'm running the cluster creation wizard it can't see any disk. I can see the disks on disk management console. Is there any way to achive this (the cluster creation) using my SAS HBA presented
disks, or i have to use iSCSI to present the disks to my cluster?
Thank you in advance, George

Hi all, i have two IBM x3560 brand new servers with V3700 IBM Storage. The Servers are connected to the storage through four SAS HBA adabters (two HBA's on each server). I want to create a two node guest Fileserver Failover Cluster. I can present the
LUN's to the guest machines, but when i 'm running the cluster creation wizard it can't see any disk. I can see the disks on disk management console. Is there any way to achive this (the cluster creation) using my SAS HBA presented
disks, or i have to use iSCSI to present the disks to my cluster?
Thank you in advance, George
1) Update to R2 and use shared VHDX which is a better way to go. See:
Shared VHDX
http://blogs.technet.com/b/storageserver/archive/2013/11/25/shared-vhdx-files-my-favorite-new-feature-in-windows-server-2012-r2.aspx
Clustering
Options
http://blogs.technet.com/b/josebda/archive/2013/07/31/windows-server-2012-r2-storage-step-by-step-with-storage-spaces-smb-scale-out-and-shared-vhdx-virtual.aspx
2) If you want to stick with non-R2 (which is a BAD idea b/c tons of reasons) you can spawn an iSCSI target on top of your storage, make it clustered and make it provide LUs to your guest VMs. See:
iSCSI Target in Failover
http://technet.microsoft.com/en-us/library/gg232632(v=ws.10).aspx
iSCSI Target Failover Step-by-Step
http://techontip.wordpress.com/2011/05/03/microsoft-iscsi-target-cluster-building-walkthrough/
3) Use third-party software providing clustered storage (active-active) out-of-box.
I would strongly recommend to upgrade to R2 and use shared VHDX.
StarWind VSAN [Virtual SAN] clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.

Very Strange Network Issue With Two Guests on 2012 R2 Hyper-V Failover Cluster

Hi all. We're having a odd issue with two guests on our 2012 R2 failover cluster.
In a nutshell, if we shutdown a particular server (I'll call it Server A) another totally different server (Server B) on the same node loses it's network connectivity to the domain. If we start server A back up, network connectivity returns on server B.
At first I thought server A might be running a service that was somehow linked to server B, so I decided to disable server A's NIC. Interestingly, that had no affect on server B's connectivity.
The next step I tried was pausing server A and again, no adverse affect on server B's connectivity.
Next step was to live migrate server A to another node. This action did
cause server B to lose its network connection.
One other clue is that if I ping server B from either of the Hyper-V hosts in the cluster, I never lose network connection to server B.
So I would suspect this is some network issue on the cluster, but I'm kind of at a loss where to go from here.
Has anyone seen this behavior before or does anyone have any troubleshooting suggestions I can try?
Thanks!
George Moore

Hi Sir,
I'v never seen this before .
>>Next step was to live migrate server A to another node. This action did
cause server B to lose its network connection.
They are connecting to same virtual switch ?
First please run cluster validation to check if there is any error .
If it is ok , please try the following items for troubleshooting :
1. shutdown serverA serverB
2. then add another virtual NIC for serverB
3. start server B check if the issue happens to both "old" and "new" virtual NIC .
In addition , you can live migrate both A and B to another node , then try to live migrate A to the original node .
If the issue persists , I would suggest you to remove that virtual switch on both nodes then re-create them .
Best Regards,
Elton Ji
If it is not the answer please unmark it to continue
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] .

Hyper-V Failover Cluster virtual guests suddenly reboots

The environment is Server 2012 R2 using dual clusters--a Hyper-V Failover Cluster running guest application virtual machines and a Scale-Out File Server Cluster using Tiered Storage Spaces which are used to supply SMB3 shares
for Quorum and CSV. Has anyone had this problem?

Anything relevant in the host or guest event logs? I would also check the cluster event logs to see if there are any indications there as well.
Does the guest go down hard or gracefully reboot?
Need more info.
Andy Syrewicze
Come talk more about Hyper-V and the Microsoft Server Stack at
Syrewiczeit.com and the Altaro Hyper-V Hub!
Post are my own and in no way reflect the views of my employer or any other entity in which I produce technical content for.

Missing a VM in Failover Cluster Manager

We did eventually cut the power when shutting down the second of the two hosts in the cluster, because it got stuck at some stage during shutdown. The reason we shut down was that there were problems piling up while we moved VMs between the two nodes.
After boot, we no longer see one of the virtual machines in the Failover Cluster Manager. In Hyper-V Manager we see it, and it runs just fine.
How can we add the missing VM back in Failover Cluster Manager? Is there a simple way?
All the servers are Win 2008 R2.
Maybe a simple question - I don't know - but we just don't have enough knowledge right now, nor has searching the net resulted in anything useful. Appreciate a bit of help holding our heads above water while we learn to swim.
Bent Tranberg

You mean what I see in Cluster Events in Failover Cluster Manager? I saved it, opened it in Event Viewer, and saved it as tab delimited text. Is that ok?
I have removed the text after the event IDs whenever the text was exactly identical to the preceding event with the same event ID, to shorten my post. I also cut away a long list of repetitive events where you see the ellipsis'.
Level Date and Time
Source Event ID
Task Category
Error 05.01.2012 10:25:15
Microsoft-Windows-FailoverClustering
1205 Resource Control Manager
The Cluster service failed to bring clustered service or application 'Cluster Group' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.
Error 05.01.2012 10:25:15
Microsoft-Windows-FailoverClustering
1069 Resource Control Manager
Cluster resource 'Cluster IP Address' in clustered service or application 'Cluster Group' failed.
Error 05.01.2012 10:25:15
Microsoft-Windows-FailoverClustering
1049 IP Address Resource
Cluster IP address resource 'Cluster IP Address' cannot be brought online because a duplicate IP address '10.10.1.16' was detected on the network. Please ensure all IP addresses are unique.
Error 05.01.2012 10:25:07
Microsoft-Windows-FailoverClustering
1069
Error 05.01.2012 09:24:43
Microsoft-Windows-FailoverClustering 1205
Error 05.01.2012 09:24:43
Microsoft-Windows-FailoverClustering
1069
Error 05.01.2012 09:24:43
Microsoft-Windows-FailoverClustering
1049
Error 05.01.2012 09:24:35
Microsoft-Windows-FailoverClustering
1069
Error 04.01.2012 14:04:33
Microsoft-Windows-FailoverClustering 1205
Error 04.01.2012 14:04:33
Microsoft-Windows-FailoverClustering
1069
Error 04.01.2012 14:04:33
Microsoft-Windows-FailoverClustering
1049
Error 04.01.2012 14:04:25
Microsoft-Windows-FailoverClustering
1069
Error 04.01.2012 14:04:25
Microsoft-Windows-FailoverClustering
1049
Critical 04.01.2012 13:59:40
Microsoft-Windows-FailoverClustering
1135 Node Mgr
Cluster node 'VSH2' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a
Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected
such as hubs, switches, or bridges.
Error 04.01.2012 13:06:52
Microsoft-Windows-FailoverClustering
1205
Error 04.01.2012 12:00:38
Microsoft-Windows-FailoverClustering 1205
Error 04.01.2012 12:00:38
Microsoft-Windows-FailoverClustering
1069
Error 04.01.2012 12:00:37
Microsoft-Windows-FailoverClustering
1049
Error 04.01.2012 12:00:25
Microsoft-Windows-FailoverClustering
1069
Error 04.01.2012 12:00:25
Microsoft-Windows-FailoverClustering
1049
Critical 04.01.2012 11:54:36
Microsoft-Windows-FailoverClustering
1146 Resource Control Manager
The cluster resource host subsystem (RHS) stopped unexpectedly. An attempt will be made to restart it. This is usually due to a problem in a resource DLL. Please determine which resource DLL is causing the issue and report the problem to the resource
vendor.
Error 04.01.2012 11:54:36
Microsoft-Windows-FailoverClustering
1230 Resource Control Manager
Cluster resource 'SCVMM AP Configuration' (resource type '', DLL 'vmclusres.dll') either crashed or deadlocked. The Resource Hosting Subsystem (RHS) process will now attempt to terminate, and the resource will be marked to run in a separate monitor.
Critical 04.01.2012 11:49:35
Microsoft-Windows-FailoverClustering
1146
Error 04.01.2012 11:49:35
Microsoft-Windows-FailoverClustering
1230
Critical 04.01.2012 11:44:33
Microsoft-Windows-FailoverClustering
1146
Error 04.01.2012 11:34:23
Microsoft-Windows-FailoverClustering
1205
Error 04.01.2012 11:34:23
Microsoft-Windows-FailoverClustering
1069
Error 04.01.2012 11:34:23
Microsoft-Windows-FailoverClustering
1049
Error 04.01.2012 11:24:22
Microsoft-Windows-FailoverClustering 1069
Critical 04.01.2012 11:24:22
Microsoft-Windows-FailoverClustering
1564 File Share Witness Resource
File share witness resource 'File Share Witness' failed to arbitrate for the file share '\\sm\QuorumFolder_Do_Not_Delete'. Please ensure that file share '\\sm\QuorumFolder_Do_Not_Delete' exists and is accessible by the cluster.
Error 04.01.2012 11:24:21
Microsoft-Windows-FailoverClustering
1069
Warning 04.01.2012 11:24:21
Microsoft-Windows-FailoverClustering
1562 File Share Witness Resource
File share witness resource 'File Share Witness' failed a periodic health check on file share '\\sm\QuorumFolder_Do_Not_Delete'. Please ensure that file share '\\sm\QuorumFolder_Do_Not_Delete' exists and is accessible by the cluster.
Error 04.01.2012 11:23:39
Microsoft-Windows-FailoverClustering
1069 Resource Control Manager
Cluster resource 'SCVMM vs2005Bent' in clustered service or application 'SCVMM vs2005Bent Resources' failed.
Error 04.01.2012 11:19:39
Microsoft-Windows-FailoverClustering
1069
Error 04.01.2012 11:19:19
Microsoft-Windows-FailoverClustering
1069
Critical 04.01.2012 11:05:36
Microsoft-Windows-FailoverClustering
1135 Node Mgr
Cluster node 'VSH2' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a
Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected
such as hubs, switches, or bridges.
Critical 04.01.2012 10:48:51
Microsoft-Windows-FailoverClustering
1135
Critical 04.01.2012 10:41:47
Microsoft-Windows-FailoverClustering
1135
Error 04.01.2012 10:33:51
Microsoft-Windows-FailoverClustering
1205
Error 04.01.2012 10:33:51
Microsoft-Windows-FailoverClustering
1069
Error 04.01.2012 10:33:51
Microsoft-Windows-FailoverClustering
1049
Error 04.01.2012 08:33:10
Microsoft-Windows-FailoverClustering 1069
Error 04.01.2012 08:33:10
Microsoft-Windows-FailoverClustering
1049
Bent Tranberg

Guest cluster on Hyper-V failover cluster

I want to implement Hyper-V failover cluster on Windows Server 2012 R2. Then Install Windows 2003 R2 as Hyper-V guest OS.
Do you know whether Windows 2003 R2 guest cluster support on Hyper-V on Windows Server 2012 R2?

Hi steventsf,
Windows Server 2003 R2 with Service Pack 2 (SP2) is in the supported guest operation system list :
http://technet.microsoft.com/library/hh831531.aspx
The guest OS is independent of hyper-v host , I think windows server 2003 R2 SP2 guest cluster is a supported scenario .
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Failover cluster name missing subnet on DAG

I've seen this multiple times and can't figure it out and end up having to recreate the DAG. On Server 2012 / Exchange 2013 I've experienced problems with the IP / subnet in failover cluster.
Its like the DAG name loses the ip address (or someone deleted it).
But the problem is when I open failover cluster manager and look at the properties of the "DAG Name" and try to add an IP address, it doesn't have the subnet that DAG nic is on. Each server has a MAPI and a DAG nic. Why does it only show the MAPI
nic subnet and not the DAG nic?

Hi,
Based on the description, you can't check "Allow clients to connect through this network" on MAPI network.
Is there any error message when you try to check "Allow clients to connect through this network"?
Besides, please check if there is any related events in the application log.
And please check the network settings on DAG member, you can look at the folllowing article.
https://technet.microsoft.com/en-us/library/ff622321(v=exchg.141).aspx
Best regards,
Belinda Ma
TechNet Community Support

Failover Cluster Manager Missing

I created new Windows 2012 R2 Servers (non-core) and configured a functional failover cluster.
I then removed the GUI using the Powershell command:
Remove-WindowsFeature Server-Gui-Shell, Server-Gui-Mgmt-Infra
After testing applications, it was determined that the applications would not run properly without the server GUI shell. I added it back using the following PowerShell command:
Add-WindowsFeature Server-Gui-Shell, Server-Gui-Mgmt-Infra
I notice that after this, when I go into Server Manager, Failover Cluster Manager is no longer available.
How do I restore it?

Hi;
Simply remove the Failover Cluster Management Tools from the Remote Server Administration Tools in Server Manager and reinstalling it again should resolve your problem.
Please VOTE as HELPFUL if the post helps you and remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading
the thread.

Event Trace Session missing for Failover Cluster

I have a failover cluster setup and is managed via a Windows Domain controller for the failover cluster network. I am troubleshooting a potential issue with the failover cluster and the recommendation is to go into event viewer, app & service
logs, Microsoft, windows and look for failover cluster diagnostics and operations logs and these do not exist.
It appears they are created by having an event trace session associated with windows failover clustering but apparently it was't created when the cluster was created for some reason. I am wondering how to create the proper event trace session
in order to get these additional failover cluster logs created?

Hello,
the following forum mat be the better one for your needs:
https://social.technet.microsoft.com/Forums/windowsserver/en-US/home?forum=winserverClustering
Best regards
Meinolf Weber
MVP, MCP, MCTS
Microsoft MVP - Directory Services
My Blog: http://blogs.msmvps.com/MWeber
Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.
Twitter:

Cluster Network 2 is missing from Failover cluster Manager

I have two node Windows 2008 R2 SP1 MS SQL cluster, there was an issue with one node NIC card which was replaced and since then "Cluster Network 2" is not visible in failover cluster manager, also Heartbeat and Public IP nic card of both nodes
are appearing in "Cluster Network 1" container. even though both network public and hearbeat are on differenet subnet, but still cluster detects it as one subnet. Need to know how to bring back "Cluster Network 2"

After replacing NIC, cluster worked fine on other node for couple of days and then cluster services started terminating on both the nodes.
when checked cluster logs found below error.
"ERR [CORE] Node 2: exception caught AlreadyExists(183)' because of 'already exists'(AODBP2DB1 - Local Area Connection)"
Hence to correct this problem, renamed both nodes NIC cards as Public and Private and cluster was started and tested the failover also. but since then only able to see "Cluster Network 1" and all NIC are listed under this container.
Though when looked at cluster validation report, it shows Cluster Network 1 and Cluster Network 2 entries in it
Pasted network section from Cluster Validation report
Network: Cluster Network 1
DHCP Enabled: False
Network Role: Enabled
Prefix
Prefix Length
10.100.18.0
25
Item
Value
Network Interface
Node1 - Public
DHCP Enabled
False
IP Address
10.100.18.11
Prefix Length
25
Item
Value
Network Interface
Node2 - Public
DHCP Enabled
False
IP Address
10.100.18.16
Prefix Length
25
Network: Cluster Network 2
DHCP Enabled: False
Network Role: Internal
Prefix
Prefix Length
10.101.130.0
25
Item
Value
Network Interface
Node1 - Private
DHCP Enabled
False
IP Address
10.101.130.11
Prefix Length
25
Item
Value
Network Interface
Node2 - Private1
DHCP Enabled
False
IP Address
10.101.130.13
Prefix Length
25
Verifying that each cluster network interface within a cluster network is configured with the same IP subnets.
Examining network Cluster Network 1.
Network interface Node1- Public has addresses on all the subnet prefixes of network Cluster Network 1.
Network interface Node2- Public has addresses on all the subnet prefixes of network Cluster Network 1.
Examining network Cluster Network 2.
Network interface Node1- Private has addresses on all the subnet prefixes of network Cluster Network 2.
Network interface Node2- Private1 has addresses on all the subnet prefixes of network Cluster Network 2.
Verifying that, for each cluster network, all adapters are consistently configured with either DHCP or static IP addresses.
Checking DHCP consistency for network: Cluster Network 1. Network DHCP status is disabled.
DHCP status (disabled) for network interface Node1- Public matches network Cluster Network 1.
DHCP status (disabled) for network interface Node2- Public matches network Cluster Network 1.
Checking DHCP consistency for network: Cluster Network 2. Network DHCP status is disabled.
DHCP status (disabled) for network interface Node1- Private matches network Cluster Network 2.
DHCP status (disabled) for network interface Node2- Private1 matches network Cluster Network 2.

Hyper-V Failover Cluster Configuration Confirmation

Dear All,
I have created a Hyper-V Failover Cluster and I want you to confirm if the configuration I have done is okay and I have not missed
out anything that is mandatory for a Hyper-V Failover Cluster to work. My configuration is below:
1. Presented Disks to servers, formatted and taken offline
2. Installed necessary features, such as failover clustering
3. Configured NIC Teaming
4. Created cluster, not adding storage at the time of creation
- Added disks to the cluster
- Added disks as CSV
- Renamed disks to represent respective CSV volumes
- Assigning each node a CSV volume
- Configured quorum automatically which configured the disk witness
- There were two networks so renamed them to Management and Cluster Communication
- Exposed Management Network to Cluster and Clients
- Exposed Cluster Communication Network to Cluster only
5. Installed Hyper-V
- Changed Virtual Disks, Configuration and Snapshots Location
- Assigned one CSV volume to each node
- Configured External switch with allow management option checked
1. For minimum configuration, is this enough?
2. If I create a virtual machine and make it highly available from hyper-v console, would it be highly available and would live
migrate, etc.?
3. Are there any configuration changes required?
4. Please, suggest how it can be made better?
Thanks in advan

Hi ,
Please refer to following steps to build a hyper-v failover cluster :
Step 1: Connect both physical computers to the networks and storage
Step 2: Install Hyper-V and Failover Clustering on both physical computers
Step 3: Create a virtual switch
Step 4: Validate the cluster configuration
Step 5: Create the cluster
Step 6: Add a disk as CSV to store virtual machine data
Step 7: Create a highly available virtual machine
Step 8: Install the guest operating system on the virtual machine
Step 9: Test a planned failover
Step 10: Test an unplanned failover
Step 11: Modify the settings of a virtual machine
Step 12: Remove a virtual machine from a cluster
For details please refer to following link:
http://technet.microsoft.com/en-us//library/jj863389.aspx
Hope it helps
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

DPM 2012 R2 Consistency Check (Replica Inconsistent) Error for Failover Cluster

I have a SCDPM 2012 R2 instance running against a Windows Server 2012 R2 Failover Cluster on the network.
However, any new/migrated Roles/Virtual machines that I add under an existing protection group always gives me an error saying that the replica is inconsistent.
I've verified the following :
1. All windows updates are applied on the cluster hosts & the DPM server.
2. The VSS and DPMRA services are running on the hosts & DPM server.
3. The Windows Server Backup feature has been installed on all the machines as well.
4. The short term storage disks attached to the DPM server are LUNs and there is enough free space on those.
What else am I missing that could be causing the Replica to be inconsistent - considering that these are new VMs on the hosts themselves - is there a way to force a fresh replica to be created?

Do not remove any of the providers they come with the system. There is just something wrong with that VM, your trying to backup, as it could take the initial replica creation.
Check all of the following
1) Make sure you have enough C drive space on the guest - need space to create a snapshot
2) Check the vssadmin list wirters for any errors
If none of the above, rerun the consistency check when no other backup is running. Check the Application log on the host for any vss failures
Ensure you have all the DPM hotfixes - I am compiling a list since i've been thru many DPM issues.
Great product when you get it going but like any product there are bumps in the road :)
ANNCEX

VM will not boot after moving using Failover Cluster Manager - "a disk read error occurred......"

My current Configuration:
3 node cluster, using clustered shared storage and about 22 VM's.   The Host servers are running 2012 Data Center while all guest are running 2012 Standard. The SAN is EqualLogic and we are using HIT Kit 4.5.
I have a CSV that is running out of space, so I created another CSV so that I could move some of the VM's to a new home.    I tested this by creating a test VM, and moved it successfully 3 times.     I then moved an actual
LIVE VM and while it seemed to move ok, it will now not start.   The message is "a disk read error occurred Press ctrl+alt+del to restart".     I moved the test VM and it failed as well.
I have read several things about this, but nothing seems to relate to my specific issue.   I have verified that VSS is working and free of errors as well.    From the Settings menu for the VM, if I select "Inspect" the drive,
the properties all look fine.    It is a VHDX and both the current file size and maximum disk size seem correct.
The VM's were moved using the "move - virtual machine storage" option within Failover Cluster Manager.
Suggestions?
Thanks.

Lets see if I can answer all of those and I appreciate the brain storming.   This really needs to work, correctly.
1. The Storage is moving.
2.   VM's and SAN are on same device.
3. No, my Clustered Shared Volume, CSV, is out of room, (more one that later)
4. No, I actually have 2 sans grouped together.   However, I'm moving the VM', form one CSV to another CSV on the Same san. EqualLogic PS 6110 is the one I am trying to move VMS around on, and the other SAN not involved in any way except
for it is in a SAN group is an EqualLogic PS6010.
5. No error During move, it took about 5-10 minutes, no error messages.   Note, I did a test and it worked GREAT 3 times.   Now both a live VM, and the test VM are doing the same thing.
6. No, the machine is not to large.   The test making was a 50 gig drive, just 2012 standard installed with updates.   The live VM was a 75 gig VM that was my Trend Micro Server, or anti-virus host.
7. Expand the existing SCV?   Yes I should be able to, but there is an issue there.   The volume was expanded correctly, Equallogic sees the added space, Fail Over cluster manager sees the added space, however disk manager only
sort of does.    When looking at disk manager, there are 2 areas that tell you a little bit about the drive.   The top part and then the bottom part.   The top part only shows 500G, the original size, while the bottom part
says that it is 1 TB in size.   I call Dell's technical support and after they looked at it I was told by the technician that they had seen this a couple of times and the only way to fix it was to move all the VM's to another CSV and delete the troubled
CSV.   I thought about adding more space to the troubled CSV, but its on a production server with about 12 VM's running on it and I did not want to take a chance.   The Trend VM was running on CSV-1 and working fine.
I must admit that the test VM, was on CSV-2.    I moved the Test VM from csv-2 to csv-3 back and forth several times with no errors.   The Trend Server was on CSV-1 and was moved to CSV-3, however it failed. Again, I then moved
the test VM from CSV-2 to CSV-3 and it failed the same way.   I could not test the "TEST - VM" on csv-1 due to csv-1 not having enough space.
8.   I did disable the network from the VM to see if that mattered it did not.
9.   I have not yet had a chance to connect the VHDX to a new VM, but I will do that in about an hour, hopefully.    Once I am able to test that suggestion I will post the results as well.
Again, thanks for all the suggestions and comments, as I had rather have lots to look at and try.   I hope I answered them well enough.
Kenny

Missing guest in Failover Cluster

Similar Messages

Maybe you are looking for