We've got a simple 3-node Hyper-V cluster setup which initially passed the verify tool 100%. We created it, added the drives from the SAN, everything works great (including planned/unplanned fail-overs) BUT.... when we now re-verify the cluster we get a quorum warning.
I understand that we can designate one of the disks on the SAN as a quorum disk, and if we do that warning goes away, but if we do that does that mean we cannot use that disk for actual storage of VMs?
I am in the process on converting my existing Windows 2008 host servers (2 host cluster) to a Windows 2012 R2 (2 host cluster).
All 4 servers will be accessing the same SAN via ISCSI.
Currently the Windows 2008 host servers are running both File server roles and Hyper-V in clustered environment.
How can I transfer the File Server roles from 2008 to 2012R2 will still keeping access to the same SAN and LUNS?
Thanks
--Steven B.
We're prepping to dramatically increase our IT infrastructure here, and I need a little advice. We're changing our practice management software from something running on a relatively lightweight database to MS SQL Server. With that we're planning a big upgrade in computing and storage, plus we'd like to add failover clustering to help guarantee a certain level of service.
The current plan calls for 3 physical servers running WS2012R2 connected directly to a SAS array on an IBM DS3524. Physical server A will host the primary SQL Server database, plus a few light-usage VMs for testing and dev stuff. Physical server B will host images and files, no SQL Server, plus a bunch of RDP VMs. Physical server C will host a nightly copy of the primary database used for heavy reports, plus another couple of VMs for various network functions.
Ideally we would like to cluster the physical server A to a VM on physical server B. I'm unsure, though, if that can be done using the direct attach SAS drives. We do not want to set up an iSCSI SAN.
Two questions, then:
Is this type of failover setup even possible? If so, how would we set up a shared storage between a physical server and a VM on a second physical server using direct attached SAS?
If this isn't possible, would we be better off virtualizing the primary database and clustering the two VMs (best practices from our software vendor recommend virtualizing everything *except* the primary DB server), or setting up a physical failover from Server A to Server C? In the event of a failure, server C would then find itself hosting 2 databases, though we could restrict reporting during a failure to lighten load.
Thanks -
Mike
Can anyone please advise on how to do this or if it is not possible? I am running W8 on my laptop and I need to have the ability to remotely manage my 2008R2 clusters. I have this tool because we have also begun converting our lower level environments to server 2012. I am getting the following error message:
The cluster to which you are attempting to connect is not a version of the cluster supported by this version of Failover Cluster Manager.
Any thoughts?
Hi all,
We have a window 2008 R2 hyper-V failover cluster working fine. It has two hosts, with 104 GB of memory on each of them.As I added new virtual instances I had been updating memory.
The point is that as I do that page file for virtual memory has been growing and now System volumen has only 20 GB free space.
I had like to go on adding memory for new virtual instances, so I need to fix this problem. Which is the recommended configuration for this? Can I disable virtual memory as long as I have an enormous quantity of physical memory available?
Thank you very much.
Kind regards,
David.
Best Practice for a FC SAN Zone has always been one Iniator Port and one Target Port per Zone. This insures that communication between the Server and Storage remain "clean" and also makes Troubleshooting easier.
If your lazy and do not feel like making so many Zones, you can also have a Zone with one Iniator Port and multiple Target Ports, if your Storage has multiple Controllers/Ports. Of course, when you have multiple Fabrics, you should not mix the two together.
That being said, I was recently in a MOC Hyper-V + VMM Course and the Instructor said that Microsoft Best Practise for a Hyper-V Cluster is to put one Iniator Port from each Cluster Node (multiple Iniator Ports) with multiple Target Ports all in one Zone. The reason being, he said, was that the Cluster reacted faster in case of a Failover. I have tried to find Microsoft Documentation that Support this statement but have not been able to find any.
Can anyone point me to any Documentation that backs this "Best Practise" Statement up or if you are doing the same thing in your Organisation?
Thanks in advance!
Paolo
Hello
When remove the Failover Cluster feature has following message:
Cannot remove Failover Clusting
This server is an active node in a failover cluster. Uninstalling the Failover CVlustering feature on thos node may impact the availabilty of clustered service and applications. It is recommended that you first evict the server from cluster membership. This can be done through the Failover Cluster Management snap-in by expanding the console tree under Nodes, selecting the node, clicking More Actions, and then clicking Evict.
I'm sure there no cluster formed, so how can I remove it?
Thanks !
Hello Everyone,
I have 2-2012 servers that I'm trying to setup clustering with. Individually they can create their own 1 node cluster no problem, adding to an existing cluster doesn't seem to work either. If I destroy one cluster and try to add it to the other existing cluster it fails with timeout. I use the Validate a Confirguration Wizard it says everything checks out successfully (warning on Storage and Network for minor stuff), then fails once it tries to create the cluster with the following:
Tried going into ACU, then giving full access under Security to the computer accounts by prestaging a cluster name as well. That didn't seem to help even after it enabled the disabled computer account when forming the cluster. I can see if I try to join one to an existing node that it joins, never comes "UP" then gets evicted after a timeout.
Suggestions on where to go next would be much appriciated. It's intersting to me since I've setup multiple clusters on 2008/R2 and am currently running clustered Hyper V 2012 servers as the hosts for these without any issues, so right now 2 clusters are in the environment without any problems. Started a debug log during the creating of the Failover Cluster, didn't see anything that caught my attention as useful information. Not quite sure where to go next.
Environment
OS = windows 2008/2012
Query
Any native replication solution available to replicate windows volumes ? I want to replicatewindows shared volume to other site.
Any comment will be appreciated. Thanks. Zahid Haseeb.
Hi,
I was wondering if it is possible to make a VM dependent or to always migrate a VM to the same node as a CSV on a Hyper-V cluster.
For example, I have a a VM with directly attached volumes as hard drives. These volumes sit on the same storage fabric as my CSV which the VM resides on. If the HBA on the owner Node1 fail, it will move the CSV to Node2. If the VM is one Node1 it will lose the attached volumes, but if it migrates to the same CSV owner node the volumes will be restored.
So it would preferable if the VM always moved to the same node the CSV is on after the CSV comes back online.
Any suggestions are welcome, thanks.
Dear all,
I recently had experience creating Hyper-V Server 2012 cluster. This allows for deploying a highly available virtual machine. That's fine. The business machine (virtual machine) becomes highly available. This includes an existing VM enabled to be highly available or a new VM installed into cluster from scratch.
On the other hand; we have cluster aware applications (SQL Server, SCVMM etc.) which are installed in clustered OS (Windows 2008 R2 Enterprise edition which has failover clustering service) .
Just for clearing concept; what is correct way of deploying a cluster aware technology (SQL Server, SCVMM) in the scenario where the underlying OS; running in VM(s) can be made highly available.
Method 1:
Create simple non clustered VM, install cluster aware application (SQL Server e.g.). Make this VM highly available using Hyper-V cluster. (This seems to be clustering the VM running cluster aware application, not the cluster ware application; which requires clustering.)
Method 2:
Create HA-enabled VM onto Hyper-V Servers cluster; install cluster aware application within this HA-enabled VM. (This again; the underlying OS/VM is clustered first, the cluster aware application (SQL server or others) how would it leverage the cluster?)
Please shed light on what is correct method. In both cases it seems the VM running the cluster aware application; is made highly available; meaning leveraging clustering. What about clustering the application
itself? The objective is to be able to not only make the VM highly available; but also deploy clustered SQL Server or other cluster aware technology using such HA VM.
Regards,
Shahzad.
Hi All,
I have a two node 2003 cluster, When any one of the cluster node holding resources goes down, the resources are not failing over to the running node.
In the running node I receive the pop-up error message
""An error occured attempting to read properties for 'Cluster Group' group. The remote procedure call failed. Error ID:1726 (000006be).""
After I click on ok on the pop-up error message the resources are coming online on the running node. If I dont click ok the pop-up error message. The Cluadmin screen is not responding and the resources are not coming online.
In the cluster log i see the below messages realted to Error ID 1726
00000874.00000b10::2014/03/17-23:38:58.276 WARN [EVT] EvtBroadcaster: EvPropEvents for node 2 failed. status 1726
00000874.00000b10::2014/03/17-23:38:58.276 INFO [NM] RpcExtErrorInfo: ProcessId= 2164
00000874.00000b10::2014/03/17-23:38:58.276 INFO [NM] RpcExtErrorInfo: SystemTime= 3/17/2014 23:38:58:276
00000874.00000b10::2014/03/17-23:38:58.276 INFO [NM] RpcExtErrorInfo: GeneratingComponent= 2
00000874.00000b10::2014/03/17-23:38:58.276 INFO [NM] RpcExtErrorInfo: Status= 0xc002100b
00000874.00000b10::2014/03/17-23:38:58.276 INFO [NM] RpcExtErrorInfo: Detection Location= 641
00000874.00000b10::2014/03/17-23:38:58.276 INFO [NM] RpcExtErrorInfo: Flags= 0x0
00000874.00000b10::2014/03/17-23:38:58.276 INFO [NM] RpcExtErrorInfo: Number of Parameters= 2
00000874.00000b10::2014/03/17-23:38:58.276 INFO [NM] RpcExtErrorInfo: Long Val= 32000
00000874.00000b10::2014/03/17-23:38:58.276 INFO [NM] RpcExtErrorInfo: Long Val= 32000
00000874.00000b10::2014/03/17-23:38:58.276 INFO [NM] RpcExtErrorInfo: ProcessId= 2164
How to FIX this issue?
Regards,
Stunner.
We have 2 nodes (Node 1-hpwdsql003 node 2-hpwdsql004) with windows server 2012 R2 on them.I am trying to create a failover cluster
We created a cluster called hpwcsql002 for the nodes hpwdsql003 and hpwdsql004
we have a shared SAN lun's for these nodes.
I validated the cluster and there were no errors .
I could also see the shared storeage on both nodes.but when i try to failover the disk from node hpwdsql003 to node hpwdsql004 by right clicking on the Cluster disk1->Add to cluster shared volume.it failovers the shared to storage node from hpwdsql003 to hpwdsql004 .
but when i go hpwdsql004 i dont find the failover drive in windows explorer.I can see the volume but not the drive on the node hpwdsql004 after the failover.
Can someone please guide me on this.
Thanks,
Lucky
lucky
Hi everybody,
I have a little soft ware and i would like realize it for the high available, i want to put it on the CSV disk then share to our staf, but i get stack in how to do that, anybody can help me some advice?
Thanks so much.
Hello!
There're a lot of iSCSI targets with one or two 1Gbps nics on market today but I have serious doubts about their performance: 1Gbps(or 2Gbps) compared to 6 Gbps in raw SAS/SATA make me think their network speed will be the bottleneck in any setup (for example,
two node cluster with an iscsi target). Can anybody please tell me what performance issues may arise, for example, if I place a VM with SQL server on such target?
Thank you in advance,
Michael
I have 2 X M600 Dell Blades (100 GB local storage and 2 NICs) and a Single R720 File Server (2.5 TB local SAS storage and 6 NICs). I´m planning a Lab/developer enrironment using 2 Hyper-V Servers with Failover Cluster and a single File Server putting all .VHDs stored on a SMB 3 Share on the File Server.
The ideia is to have a HA solution, live migration, etc, storing the .VHDs onm a SMB 3 share\\fileserver\shareforVHDs
It is possible? How Cluster will understand the \\fileserver\shareforVHDs as a cluster disk and offer HA on it?
Or i´ll have to "re-think" and forget about VHDs on SMb 3 Share and deploy using iSCSI?
Storage Spaces makes difference in this case?
All based on wind2012 R2 STD English version
Hi All,
We have a prduction setup with,
1. Two node windows 2008 r2 enterprise active passive failover cluster with one instance of MS SQL 2008
2. One network for heart beat, one for management and one for production client access
Now business has decided to have a separate network for backup and restore, introduced new VLAN, network connections can be added to the virtual connect.
Request you to support me with the steps to be followed to configure the new network connections to the cluster setup so that the the SQL DB can be backed up through the same.
Shaji P.K.
Hi Team,
I need to increase the cluster host master shifting interval, currently it is 5 seconds to the best of my knowledge, if it doesnt get response in 5 seconds it starts shifting the Exchange DBs to the next available node.
Can I increase this time interval?
OS: windows server2008 R2 sp1
application: exchange 2010 sp3 in 4 node DaG.
any help?
Muhammad Nadeem Ahmed Sr System Support Engineer Premier Systems (Pvt) Ltd T. +9221-2429051 Ext-226 F. +9221-2428777 M. +92300-8262627 Web. www.premier.com.pk
I have a Windows 2008 R2 File Server/SQL Cluster on 2 node active/passive setup. One of the developers at my work was trying to access a hidden share for a partition that is on the iSCSI drive. She was using the clustered name. It would come up with Network
Name Cannot Be Found. I could browse to the share using the ip and the hostname of the node that was active.
I noticed that all shares were still up and nothing looked wrong from the clustering part. I deleted the share and restarted the Server Service. Once I did that all shares that were located on the iSCSI drives that were clustered disappeared.
Now at this point the file sharing cluster is failing because of the missing shares. Now when I try to recreate the shares in Cluster Management it won't let me because it says Network Name Cannot Be Found.
At this point the following has been checked
-Ping the DNS name of the cluster and it translates fine
-Did an nbtstat and everything resolves fine
-The SQL Server Cluster is still up and has no errors
From all I have read one thing that could be wrong is the provider ordering. I checked it and at this point lanmanworkstation is the last in the order after symantec backup, rdp and one other provider.
But if that is the issue why would it start just not working? Why would I still be able to browse by the name of the active node originally?
Any other ideas would be appreciated.