Hello. I have some clarifications.
1. What would be the best practice for an environment with 3 Domain Controller Servers when i want it to be high-available?
2. If the Primary DC Server is down because of hardware problems, which server would take place?
3. How can i control which server would the users connect to if Primary Server is down?
4. In case Primary Server is up and running again, would i need to configure ADDS to point out again which server should the users connect to?
Thanks!
Hi ,
I found the following document about live migration and work group cluster on Windows 2016.
https://techcommunity.microsoft.com/t5/Failover-Clustering/Workgroup-and-Multi-domain-clusters-in-Windows-Server-2016/ba-p/372059
I understand Live migration is not support, and support quick migration. Is it same on windows 2019? or any plans about it ?
I am running a 4 node 2016 Hyper V failover cluster with about 30+ servers. I just noticed one of my servers is leaving behind a .avhdx .avhdx.mrt and a .avhdx.rct file after every backup with DPM 2016.
The machine list not checkpoints under hyper V via the gui or powershell. These are being created when DPM backs up(Which happens successfully). How do figure out what is causing this and how do i go about cleaning this up?
Hello,
So I'm curious about having Windows updates being synced between machines. From my understanding if you have 2 domain controllers on the same domain (Server 2016) and they're set to have Automatic Updates that they sync in a way with the reboot, so one DC is always up and then they work together somehow so they're not out of sync with anything. Is that possible for DHCP, SQL and IIS servers if those are setup as a cluster or fail-over state? It's something I'm trying to research and am just not 100% sure on. I know there's SCCM (which I'm also looking at), but if I can just cluster/fail-over the servers and set to automatic updates and just move onto other things that'd be ideal. Any help appreciated. Thanks in advance.
Hi Experts,
Our windows team have applied patches on two nodes of a cluster.Post patch,file share witness is accessible from one server and from other it is not accessible.Hence
After deep dive,we could see below extra security patches has been applied on server where file share witness is not accessible.
KB3161949
KB3172729
KB3173424
KB3175024
KB4338824
KB4499165
KB4503290
we are not sure what patch is creating this problem as we don't see any official MS doc on this .Please let us know if you have any information on this matter.
Also advise,if there is any forum to check on bug details quickly.
Many thanks in advance !
Regards,
Naren poosa
Hi,
I know it's not recommended to upgrade the OS, okay!
if we choose to upgrade the hyperv cluster nodes with 2012 R2 to 2016, what are the recommendations?
- Remove the cluster node;
- Remove functions;
- Upgrade to Windows 2016;
- Reinstall functions;
- Insert the cluster node again;
Or can we update it directly with the node in the cluster?
Thank you.
Hello Team,
We received the event id 5120 in couple of our Hyper V nodes which are in the cluster.
The error mentioned in the Title is the error that shows up with below description
Cluster Shared Volume ‘Volume1’ (‘name’) is no longer available on this node because of ‘STATUS_IO_TIMEOUT(c00000b5)’. All I/O will temporarily be queued until a path to the volume is reestablished
All servers are using Windows Server 2012 R2 as Operating System. Another event id generated at that time is 5217.
I would like to know if there are any hotfixes for the present time. All the hyper v nodes were updated with the March month of 2019 security patches.
Can anyone please help me to find a solution for this? And how to find the actual cause of this issue.
Regards
SJ
We are designing a new SQL farm in our company, they want HA/DR (so a WSFC cluster), but we only need DR for some certain Databases not HA, due to the amount of databases. These other Databases will be on other separate VMs due to size and separation.
If you have a cluster with three nodes two in one site with HA and 1 in another site for DR, what should you do for the databases with no need for HA. I had planned to have the non-HA databases in a read scale availability group between two VMs away from the cluster to provide the DR ability.
But thinking about it would it not make more sense to have the two WMs in the cluster, with no quorum votes, with just a synchronous, manual failover availability group between these two VMs?
Is there ever a situation where you would use read scale availability group where you have a cluster available?
Hi,
If there is two node and both nodes are up and running but the heartbeat lost , in that case how node will decide who aill be active
Thanks
Hello,
due to specific constraints in my environment I've had to build an AD-Detached WSFC to host a SQL AAG.
The cluster was configured with a specific user created specifically on each machine of the cluster so the credentials would be consistent on each machine due to the lack of AD.
The current setup is as is :
3 VM : 2 Windows 2016 servers for SQL (Let's call them SQL1 & SQL2)+ 1 Windows 2016 server to act as a quorum with only WSFC role (Called QRM01) (these 3 servers are VMs). no possibility to have shared storage or a witness due to the AD-Detached+ environment constraints, this is why a 3-node configuration (Majority node) was chosen to have the quorum and avoid split-brain.
The cluster was created by specifying the "ClusterUser" credentials.
The issue I encounter is the following :
I can mange the cluster ONLY from the QRM01 server, and with the account the cluster was created under (ClusterUser).
If I try to manage the cluster using the WSFC mmc either running under a local admin on any node or under the ClusterUser account on one of the 2 SQL nodes, I get an Access Denied error : "Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))"
The Get-ClusterAccess shows me Full access for all my local Admin users.
I'm sure it was working perfectly before adding the QRM01 server, can't be sure it worked after that but at the moment it doesn't.
How can't I access my cluster with local Administrator or ClusterUser accounts (both members of local Administrators group) from my 2 sql nodes ?
Thanks for your insights and help.
hi
how to configure 2 DC server and 1DR server mirror in 2016 sql server
Pl suggest
We have a two node cluster (Server 2016 datacenter) where I've added the MSMQ cluster role. I have two networks this cluster can talk to, 192.168.0.0 and 10.10.0.0. The message queuing role has both cluster IPs added as dependencies. If I run netstat (netstat -abno | findstr 1801) I can see the 192.168.0.0 address is listening on port 1801 but not the 10.10.0.0 cluster IP. I've tried adding the "BindInterfaceIP" string to the below reg key but it doesn't change anything. I've went as far as rebooting both nodes after making the registry changes. The firewall is completely turned off on both nodes. I feel like I'm missing something small to make the cluster listen on the 10.10.0.0 IP as well as the 192.168.0.0 IP. Has anyone seen this before or have an idea on what else to try?
Registry Key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSMQ\Clustered QMs\<Clustered Message Queuing Name>\Parameters
s2d newbie here. This is a test environment, so nothing is probably supported hardware.
the setup
Running two optiplex 3050's with windows server 2016. They each have a spinning disk and an ssd via sata. the spinning disk is partitioned for the operating system and the rest i dumped into the s2d pool. With this hardware i setup a fail-over cluster w/ quarm coming from my domain controller, and the clusters' storage coming from the s2d pool. Everything was working well, but terrible slow.
the issue
To cure the slowness i decided to add a pcie, m.2 drive to each. After adding it to one machine the cluster and s2d drive came back w/ an error, i ran a repair inside of server manger. After that completed i added the same drive to the other machine and my s2d drive has been gone since. I've tried removing the last HD I added, rebooted each several times w/ no luck.
error's
when i look at the critical events for the cluster's disk in "fail-over cluster manager" there are a lot of repeating event ID. 5142, 1069, 1793
Any help would be greatly appreciated. I'd like to see if i can fix this in a test environment before i see it in production.
many thanks!
IT guy
Hello All,
I am about to start a cluster upgrade from 2012 R2 to 2016. There are a lot of good guides out there and the process seems strait forward. I would like to know if it is ok the keep the same computer names and ips for my servers once I add them back to the cluster.
Thanks,
Scott
Hi,
Good Day!
May I ask if anyone have encounter below error. Please see the screenshot for the reference.
Thanks,
Raymond
I have a 3 node cluster with a iSCSI / MPIO CSV. This has been running for about 1 1/2 years with no issue.
Host 1 is the current owner of the CSV. I verified that by going to Disk Management on host 2 and host 3, and seeing that for the CSV disk, they both have the 'disk is offline because of a policy set by an administrator' message. Host 1 does not have that message which makes it the owner.
Recently, whenever any VM function is attempted on host 2 (like start a VM, live migrate a VM, shutdown a VM, etc..) I get a non-stop flow of event id 153 and whatever process was started takes longer than normal to complete. If the VM does start after a long delay, access to the VM is slow and choppy from the end user's standpoint.
If I migrate or shutdown all VMs on host 2, the 153 messages stop.
Host 2 itself is never slow or laggy. Only the VM operations are slow.
Host 1 and host 3 DO NOT have ANY event id 153.
Does anyone have any ideas why this single node is displaying this behavior?
Thanks in advance!
Hi,
I have my homelab with two Dell R710 with 6 HDD and 2 NVMe in both servers.
I have configured two virtual disks, created as nested mirror-accelerated parity, but if I suspend a node and reboots it, all vdisks goes offline with the error
The pack does not have a quorum of healthy disks.
This was working fine on the same servers on 2016.
But if I run this before the reboot, all vdisks stays online as they should.
Get-StorageScaleUnit -FriendlyName $Env:COMPUTERNAME | Enable-StorageMaintenanceMode
Anyone else have the same experience ?
BR
Martin
Hi
We have two nodes Failover Cluster Node A Node B
connected with MSA2040 via 4 SAS connectors
As soon as Node A restart Node B unable to see storage and all the VMs restarts rather failover
1- Both Nodes can see Cluster Storage in the C drives
2- Currently Owner node is A
3- VM can be live migrated no issues
3.1- Unable to see how we are mapping the Storage to HyperV Nodes as theresnt any iscsi initiator ?
4- Its setup by previous employees
5- I am in field quite long but new to storage and stuff
6- Tried various forums but unable to get this resolve
any help would be highly appreciated.
I have a brand new Hyper V Cluster using Server 2019 Core with 6 nodes. Everything updated hardware-wise from the manufacturer (HPE) and connected SAN (netApp). Everything updated software-wise from HPE and Microsoft. I am using Veeam Backup 9.5 update 4a also.
What I have had happen on more than one occasion now, is I will get a VM or two get into a hung or locked state. My backup shows it has failed and I cannot Live Migrate nor shutdown the individual VM either from the guest itself or from the host node from task manager. Problem also causes my other VMs on that node to not be able to Live Migrate (it gets stuck at 3%). My only recourse has been to restart the server from command line. Today when it happened, I had to hardware reset the server to get it to reboot as even after an hour, it was still draining roles.
My first inclination is to blame this on Veeam and I will take this up with them if, after I have updated to 9.5 update 4b today, I encounter the issue again...but wanted to see if anyone else has had this or might provide some insight of what could be hosing the entire node for an errant VM?