September 14, 2018 at 4:12 pm
Hello,
I am currently setting up a SQL Server 2017 availability group on Windows fail over clustering. I am following along the VMWare guide and had a question. Which drives do I want to share between the new nodes (VM's)? Do I share the data drive that I am planning to install SQL on? The log drive that I am planning to create?
September 16, 2018 at 9:22 am
If you are looking to set up windows failover cluster just as a requirement to setup always on ( like in a dedicated DB server). you dont need to share drives between VM's. In Always on drive are independent to the VM. only option is if you re going to use Quorum drive then you can share that drive in VM in data store. My recommendation to dont even use quorum drive and use file share witness folder for this. just make sure it is on a separate VM.
I have quite a experience of setting this up On VM. let me know if you need more help.
Regards,
B
September 17, 2018 at 9:23 am
Thank you for this information. This is exactly how I had it setup and everything was working OK. I was worried as all of the guides say you must shared the drives. Here is what my current setup looks like, would you please let me know if this seems sufficient?
VMWare 6.5
2 hosts / 2 VM's
Server 2016 Data Center
SQL Server 2017
Microsoft Failover Cluster (I am not sharing any disk)
File Share Quorum
All VM's have independent think provisioned disks for (SQL install, data, logs, backups) using normal data stores/VMFS6
I am not using any RDM's at all. The only errors I continue to get in failover manager is regarding the network as I am using a 3rd VM as an asynchronous DR site and it's on a different subnet.
Is this supported without sharing ANY of the disks between the VM's? Every guide I find from MS or VMWare says I HAVE to share the disks.
September 17, 2018 at 9:26 am
No shared disks with Availability Groups assuming you just have two standalone SQL instances.
September 18, 2018 at 11:56 am
brysondearen - Monday, September 17, 2018 9:23 AMThank you for this information. This is exactly how I had it setup and everything was working OK. I was worried as all of the guides say you must shared the drives. Here is what my current setup looks like, would you please let me know if this seems sufficient?
VMWare 6.5
2 hosts / 2 VM's
Server 2016 Data Center
SQL Server 2017
Microsoft Failover Cluster (I am not sharing any disk)
File Share Quorum
All VM's have independent think provisioned disks for (SQL install, data, logs, backups) using normal data stores/VMFS6
I am not using any RDM's at all. The only errors I continue to get in failover manager is regarding the network as I am using a 3rd VM as an asynchronous DR site and it's on a different subnet.Is this supported without sharing ANY of the disks between the VM's? Every guide I find from MS or VMWare says I HAVE to share the disks.
Hi,
The setup seems to be fine. I do use thin provisioning on my VM's. Also if this is going to be a very sensitive DB server. please use separate ISCSI control on the VM level for the data, log and temp drive. It gives you better performance.
September 18, 2018 at 12:33 pm
Beatrix Kiddo - Monday, September 17, 2018 9:26 AMNo shared disks with Availability Groups assuming you just have two standalone SQL instances.
Correct, no reason to share drives. WFCS is needed to setup
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply