22

The outcome you want to achieve, and the manner in which you have decided to do it, are very different things. To be blunt, what you want to implement is a bad idea, and if you can somehow manage to make it work, it won't work for very long (or very well). What makes this question difficult to answer is that you've leapt straight to the implementation, and ...


13

The reason you're frustrated is because you're trying to do something that you shouldn't be doing. You say If anyone is now saying, “wait, what about a SAN or a NAS for the file servers?”, well too bad.` You're right. Too bad for you. What you're trying to do cannot work. A cluster disk must be the same disk shared amongst cluster members. You can't ...


12

Having 2-node cluster, it's beneficial to have at least 2 AD DC VM's each located on a separated host. In case of a host failure, you will ensure the AD is up and running. The AD running on a VM also allows you granularly maintain AD and Hyper-V host. Microsoft recommends to run AD either on a Hyper-V VM or/and on a dedicated physical host. It's not ...


9

The physical cluster makes your virtual hardware highly available, i.e. failures of a physical server don't affect any given virtual machine. However, the virtual machine itself can still fail (e.g. OS crashing, someone shutting down the virtual server, etc.), so the service running on top of the virtual machine may still fail at some point (although it's ...


7

We used to have a problem like this where I'm at. I don't remember the exact details, but the final solution had to do with a conflicting mac address assigned dynamically to a virtual network adapter. Pinning those down to they weren't dynamic helped a lot. You normally don't want to do that because it can make it harder to move a virtual machine to a ...


7

First, you need to define what you really mean by "HA". What are you protecting against, what are the costs of an outage of type X and duration Y? How will it affect your organization? What is your role in this organization anyway and what is your time worth? How much time can you spend on this? After that, you have to decide if this requirements allow ...


7

This: Fault Tolerant Shared PERC 8 Card Configuration — [...] The default cache policy for virtual disks created in this configuration is write-through. In this mode, write completion information is returned to the host after the data is written to the disk. is the ultimate performance killer. Change the cache policy to write-back if it is ...


7

Oh god, you've not have you? You've just caused immediate, irretrievable data loss sorry. NTFS isn't a cluster-aware file system, you need something to act as a lock manager too. MS Cluster Services can do some of this for you but they won't be active/active as I suspect you want - for that you might needs something like Symantec Storage Foundation which ...


6

I'd actually recommend Gluster. It is OpenSource, well documented and RedHat recently purchased it. It has a relatively good performance, and since it is a RedHat project now, it is well supported on CentOS. There also is a project called HekaFS, which has the goal of extending glusters Authentication and Security capabilites by adding SSL and other goodies. ...


6

Being that it's a proprietary product I don't think you're going to binary-level analysis of the protocol or even flow diagrams, but I think you can glean some helpful information from: The Design and Architecture of the Microsoft Cluster Service - This paper, co-authored by one of my CompSci heroes Jim Gray (RIP, Jim), published in the 1998 IEEE ...


6

The space actually used by a quorum disk amounts at most to a few kilobytes, not even megabytes. There is really no reason at all to go above the suggested size. That said, creating a LUN and a NTFS volume of a few megabytes in size would be impractical for several reasons; the most common size for quorum disks in my experience is 1 GB, and even that is ...


6

Enabling Conflict detection (which is not enabled by default) will probably resolve this.


6

I have experienced the exact same performance issue with a VRTX with the Dual SPERC8. What I have done to work around this at the moment is, change the dual config to a single config. This way I am able to use write-back, which performs way way better. The exact steps: Remove the second SPERC 8 controller Remove the second expander Re-cable the internal ...


6

You have many options. Which ones you can use depend on how your website is coded. Tightly Coupled, Single State This web-site can only run one instance because of... reasons. Running two in parallel would be an extremely bad idea for some reason. It's pretty uncommon to be this kind of site. CAP Theorem: Consistency over the whole system is paramount, not ...


6

I see similar issue posted on technet. Is there any chance to see what does Event Log show? For the case, from my experience, Microsoft iSCSI target is too slow. Currently, I use StarWind Virtual SAN Free that delivers really fast iSCSI server with the additional functionality of cache and log-structured file system (snapshots, dedupe, etc.). I suggest you ...


6

Decouple your Synology HA setup, RMA one of these units with "Your HA does not work!", and get VMware or similar vSAN to enjoy local disk performance, and reliability. Whatever you'll do you won't squeeze any reasonable IOPS, and transparent failover time out of your current setup. P.S. You might try to use IBM SVC (now IBM Spectrum Virtualize) or already ...


6

Take something like Starwinds and create Highly Available shared storage with your two nodes. AFAIR, they have a lot of manuals which may help you. BTW, it's for free. https://www.starwindsoftware.com/starwind-virtual-san#VSAN-FREE


5

I am aware that this is an old question, but I encountered the same issue and wasted so much time getting it resolved that I thought I would share the solution that worked for me. I found the solution to my problem here: http://invendows.wordpress.com/2008/03/06/network-issue-with-hyper-v/ The solution in my situation was to disable TCP Offloading on the ...


5

Don't forget to take a reality pill along the way, though. You need to understand the required uptime for your application, and more importantly, the maximum amount of time your application can be unavailable when it does fail. And it will. This second point is critical; I've seen a "five nines" application being managed by a large systems integrator ...


5

The book is correct, however there are pieces it left out. MAC addresses are not as fixed as you would think, most higher end NICs have the ability to change the MAC address to something specific. Either in the NIC's BIOS or in the driver itself. There are specific ranges of MAC address set aside for 'virtual' systems (see What range of MAC addresses can I ...


5

I don't have a Windows Server 2008 R2 failover cluster to check at the moment but deleting the VM from Failover Cluster Manager should remove it as a clustered role/service but leave the VM intact. It should be the equivalent to the Remove option in a Windows Server 2012 Failover Cluster.


5

It is no longer required to remove the second SPERC controller to be able to use write-back instead of write-through as described in Erik's post. You can now disable the second PERC8 controller from the CMC. In the current firmware (1.35), the second disabled controller can be set as disabled and requires manual intervention to activate if the primary active ...


5

What is the relationship between number of buffers and ring size? They're related, but independent. The rx "ring" refers to a set of buffers in memory that are used as a queue to pass incoming network packets from the host (hypervisor) to the guest (Windows VM). The memory gets reserved in the guest by the network driver, and it gets mapped into host memory....


5

Based on the shared storage requirement I assume it's AlwaysON FCI (Failover Cluster Instances) The easiest solution for you would be deploying a virtual SAN. Virtual SAN will take the local storage of the 2 SQL nodes you have and present it back to them as a highly available virtual disk. Now if one of the SQL cluster nodes fail you still have one live ...


5

I'm not sure why that is considered an error rather than informational but the gist of it is, if you plan to use Hyper-V Replica then you need to configure a Hyper-V Replica Broker. If you don't plan on using Hyper-V Replica then you can ignore that error or exclude it from the BPA results so that you don't see it again. If you're not using Hyper-V Replica ...


5

In Windows Server 2012 R2, "The clustering service will automatically assign the witness a vote, the witness dynamic vote, depending on if there is an odd or even number of votes present for the cluster nodes." Dynamic Witness in Windows Server 2012 R2 Failover Clustering "To check the vote status of the witness, use the Windows PowerShell command below. A ...


5

If you use Broadcom NICs, try to disable VMQ on a virtual switches and on a physical network adapters: http://www.dell.com/support/article/ua/ru/uabsdt1/SLN132131/EN You might also check if there are the latest hyper-v drives installed. Besides, are your VHDX files formatted to NTFS? One more thing that comes to mind is MTU. Try to change it to 9000. But ...


5

Since you about deliver shared storage system having local I/O preferably, I would suggest to look at solutions that do kind of asynchronous replication between clustered hosts. I suspect the creation of multiple clustered shared volumes over active-passive shared storage will provide required local I/O. I can suggest StarWind Virtual SAN as it seems to be ...


5

NTFS is not a cluster-aware file system. It was never designed to support simultaneous access from different clients. In order to allow multiple access: configure MPIO, deploy the Failover Cluster feature on both servers, create the new cluster and add your SAN volume to Failover Cluster as CSV (Cluster Shared Volume).


5

You have to have supported media types with Storage Spaces Direct which is no-RAID, no-FC and no-iSCSI. Should be SATA, SAS and NVMe. https://docs.microsoft.com/en-us/windows-server/storage/storage-spaces/storage-spaces-direct-hardware-requirements Drives Use local-attached SATA, SAS, or NVMe drives. You can easily workaround this issue if you say don't ...


Only top voted, non community-wiki answers of a minimum length are eligible