Per Microsoft recommendations https://technet.microsoft.com/en-us/library/jj612868(v=ws.11).aspx you should consult your storage vendor that may recommend configuring each LUN with one partition and place one CSV volume on it.
Generally, I would recommend having iSCSI LUN and CSV numbers equal to hypervisor hosts. You can bound each cluster shared volume (...
I would recommend you to use your old hardware in another way. I would purchase a new Dell server with the similar specs and create a Highly Available cluster. You can take a look at StarWind Virtual SAN that, as I know, can provide you with Highly Available storage. You will be able to create a redundant cluster with two nodes. As another option, you could ...
Windows Clustering's full name is Windows Failover Clustering. It's not active/active database instances. It doesn't sound like it's what you're looking for. MSSQL server doesn't do sharding or any of that stuff. It "scales up" instead of "scaling out" so to speak.
I used FreeNAS for a few months a while ago and gave up on it from too many bugs, especially around SMB, obviously, that is native to Windows environments. In you FreeNAS case I would suggest you bring the FreeNAS drive online, add to FC as available storage and then add as CSV. That works for me.
Since your approach is to deploy a cluster and run SQL ...
Few words about Hyper-V Replica as it's one of the most frequently deployed scenarios.
You can PowerShell automate Hyper-V Replica no problem!
There are some caveats however:
1) There's no ...
This is an important question and I'd say a more common scenario than it appears from your searching.
As you may know there are three types of teaming provided by MS Server.
1. Active / Standby
Based on your statement about whether you will have to
tear everything down
it sounds to me like you are using Static teaming which ...
Yes, you can setup S2D in Azure adding to existing VLANs. It can be done as you would setup S2D on-site https://www.tech-coffee.net/2-node-hyperconverged-cluster-with-windows-server-2016/
Since you need shared storage in Azure, I do not think S2D is an option here. The shared storage can be done using Shared VHDXs over redundant underlying Azure object ...
Take something like Starwinds to replicate the data between the servers. I'm not sure can it handle your specific services, but you can always ask their engineers. https://www.starwindsoftware.com/starwind-virtual-san#VSAN-FREE
In retrospect, I guess I should've known. The answer is in two parts, because, in my mind, there's planned failover and "real"/unplanned failover---and planned failover doesn't count.
Planned failover is actually just the Clustering system draining the node, then rebooting it for you. So when you directly reboot the node via RDP or "Stop ...
I did exactly what you did - I was adding a new node to an SQL 2014 AlwaysOn cluster and I forgot to uncheck the "Add Storage" button at the end of the wizard.
To get the storage back, and your cluster online:
Remove all the disks "Cluster Shared Volumes" (Right-click, Remove from Cluster Shared Volumes)
Remove all the disks from the cluster completent (...
Launch FCM, specify a required cluster and go Networks. Then select the network you want to modify settings for and click Properties. This way you can allow or forbid cluster/client communication on certain networks. You can also manually configure live migration channels over there.
More recommendations on how to isolate network traffic on Hyper-V ...
Sam is right. You can build Failover Cluster and configure high availability for your application using either S2D which is officially supported in Azure or third-party HA shared storage solutions, for example, StarWind Virtual SAN. The resulting highly-available CSV can be used for virtual machine files and as a backend storage for File Server SMB shares.
Are you trying to update an already registered cluster task or to register a new cluster task ?
From MSDN Blog :
Set-ClusteredScheduledTask : Update an already registered cluster
Register-ClusteredScheduledTask : Register a cluster task.
I guess you are looking for Register-ClusteredScheduledTask.
A Hyper-V Failover Cluster on it's own does not provide any load balancing of the virtual machines.
You're misunderstanding things a bit. The cluster you're referring to could/would probably not withstand the failure of 6 of the 7 nodes. The cluster could probably handle the failure of several nodes, but it could not withstand the failure of a majority of ...
Dynamic quorum doesn't work by changing the quorum type, it works by modifying the NodeWeight property on one or more nodes as required.
For example, let's say I have a three node cluster running in Node Majority quorum mode. You would choose this mode as it gives the quorum an odd number of participating votes, which is required in order to make a ...
There is no problem running a File Server role on Hyper-V hosts. In general, mixing other roles with Hyper-V is not a good thing. However, the File Server role has been specifically designed and tested to run alongside Hyper-V. One thing I suggest doing is using Windows 2012 R2's QoS features to carve out network capacity for your Hyper-V role vs. your File ...
Ok, so after several weeks of debugging this on my own and together with Microsofts Message Queue support team, a solution has been found.
TLDR; the solution is to remove or rename the registry key
The reason for the error is that the MQ client cannot find a MQ service ...
You can try setting up an iSCSI target on top of Storage Spaces which will allow you to connect to it from the virtual machine potentially gaining the performance boost by avoiding .vhdx abstraction layer.
But, unfortunately, this option does not seem to be suitable for your scenario as you will lose the benefits of CSV and high availability for your ...
The simplest way for you would be using a PowerShell script that will migrate your roles to a healthy node in case of network failure.
Usually, if a network adapter fails an event is logged into windows server system log. Just create a windows task that will run the PowerShell script and bind it to that specific event. You can recheck the interface status ...
IMHO granular LUN configuration is still the best way to properly distribute workload within an environment. This will really make the management easier, and I think it makes sense for any environment. But in you case, I would just distribute the VMs by type of workload or something.
A Hyper-V Failover Cluster will afford you automatic failover and failback in the event of a host failure. This requires shared storage between the cluster nodes.
Hyper-V Replica affords you manual failover and failback in the event of a host failure and doesn't require shared storage.
It's really a matter of what your budget will allow and what type of ...
To my mind this basically means that the failover was caused by the fact that File Share Witness gone offline. But - why?
That's not what it means. Reading through the logs that were posted, I can see the core cluster group failed to another node (in hopes that it fixes the connectivity issue with the witness), however there is nothing in regards to SQL ...
SOFS isn't expected to work with anything except supported scenarios: Hyper-V VMs, and SQL Server databases. Reason is simple: SOFS uses CA (Continuously Available) File Shares and these "guys" aren't cached, so "general purpose" file access performance is going to be mediocre at best.
I mean if you want implement a File sharing server in cluster some of the disk have to be shared between the VMs so for that disk the only choice is VHD set which is designed for this purpose.
If sharing disk is not necessary I'm suggesting you to use VHD which (as per the description in the image) seems more stable then VHDX which provide up ...
Windows 10 guest is not aware that there are any CSVs. The guest VM will see it as local device. The attached disk should be found in VMs “Disk Management”.
P.S. Here is a good guide for WSFC home lab - https://www.hyper-v.io/setting-windows-failover-cluster-home-lab/