Can a SQL Server Failover Cluster Instance (FCI) be Implemented Between Two Hyper-V Hosted Virtual Machines?

I haven't had the opportunity to implement a SQL Server Failover Cluster Instance (FCI) for over 10 years and that was done with two physical, identical database servers way back in the day of Windows Server 2003 and SQL Server 2000 (old school).
Can a SQL Server 2008 R2 Failover Cluster Instance (FCI) be implemented between two Hyper-V hosted virtual machines? The environment in question already has Windows Server 2012 R2 Hyper-V hosts in place, so I'm just looking to see if this is even
possible and/or supported when utilizing virtual machines.
The client in question is currently using SQL Server 2008 R2 instances running on Win2008R2, Win2012, and Win2012R2, but I'd also be interested how this can be done or not with SQL Server 2012 or 2014 as well. Thanks in advance.
Bill Thacker

Yes, it can be done with Hyper-V guests. In fact, with Windows Server 2012 R2 Hyper-V, guests can use the Shared VHDX feature for shared storage used by Windows clusters. The guests can run Windows Server 2008 and higher provided that the Hyper-V Integration
Services are installed to support Shared VHDX. The only challenge here is making the Hyper-V hosts highly available as well, running it on WSFC.
Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
Blog |
Twitter | LinkedIn
SQL Server High Availability and Disaster Recover Deep Dive Course

Similar Messages

Service Accounts for Reporting Service in SQL Server Failover Cluster setup

I am setting up 2 Report Services (SSRS) in SQL Failover Clustering (Version: 2012SP1) on Windows 2012, as part of scale out architecture.
There are 2 options to configure the service account for SSRS:
Option 1) Using domain accounts, as what I have done for DB Engine and SQL Agent.
Option 2) accept the default, which is virtual account for SSRS. Per documentation URL:
http://msdn.microsoft.com/en-us/library/ms143504.aspx
which is the recommended one? is it option 2?
There is security note on above URL as well, but does not clearly mention that option 1 is not recommended.
Security Note: Always run SQL Server services by using the lowest possible user rights. Use a MSA or virtual account when possible. When MSA and virtual accounts are not possible, use a specific low-privilege user account or domain account instead
of a shared account for SQL Server services. Use separate accounts for different SQL Server services. Do not grant additional permissions to the SQL Server service account or the service groups. Permissions will be granted through group membership or granted
directly to a service SID, where a service SID is supported.
Thanks very much for your help!

Hi Luo Donghua,
In SQL Server Failover Cluster Instance, personally two options can run well. If you use the virtual account for SQL Server Reporting Service. Virtual accounts in Windows Server 2008 R2 and Windows 7 are managed local accounts that provide the features to
simplify service administration. The virtual account is auto-managed, and the virtual account can access the network in a domain environment.
Of cause, you can also use domain accounts in your clustering.
Just make sure your service account is set up here, or that it is using a proper built-in account.For more information, see:http://ermahblerg.com/2012/11/08/cluster-ssrs-in-2008/
Thanks,
Sofiya Li
Sofiya Li
TechNet Community Support

SQL Server Failover Cluster Questions

Dear All,
            I am building a two-node failover cluster on SQL Server 2012 SP1 (inside Hyper-V as a Guest Cluster) and want clarification on few things that I am facing.
1.  I am receiving MSDTC Warning. I can go ahead and create the cluster, but want to understand whether this MSDTC is to be configured as a role on the cluster or not. I plan to run SCVMM, SCOM, Orchestrator and Windows Azure Pack Databases
and Reports through it so in such a scenario, do I need MSDTC? If yes, how much should be the size of the MSDTC Drive? Is following process correct?
http://www.sqlnotebook.info/configure-msdtc-on-windows-cluster-2012/
2. During First Node configuration, one needs to provide the "SQL CLUSTER RESEOURCE GROUP NAME". Does it have any bearing on how it will be accessed by other servers for databases and logs? or is it just how the cluster resource group
would be named? would it be required for every instance that is created inside the cluster? Just to be clear, so one can name it according to the instance name.
3. During the instance creation, one needs to provide "SQL Server Network Name". As stated above, I plan to run SCVMM, SCOM, Orchestrator and Windows Azure Pack Databases and Reports through it, so would I be required to provide this
for all instances that I create or this is only required once in the cluster:
4. During the instance creation, one needs to provide the features required for installation i.e. instance features and shared features. As stated above, I plan to run SCVMM, SCOM, Orchestrator and Windows Azure Pack Databases and Reports through
it, so which features should be selected? so that there is less workload on the server.
5. All the instances use TempDB for databases that are present inside it. What would be the best practice with respect to TempDB. One TempDB for all instance on the servers on a separate LUN or all instance having their own TempDB LUN?  What
should be the ideal size of the TempDB LUN?
6. Should all the disks required for DBs and Logs be added to Cluster?  Should they be added normal disks or CSV Volumes?
Thanks in advance.

Hello,
1.You can run the Microsoft Distributed Transaction Coordinator service (MSDTC) as a clustered resource on a failover cluster server for increased reliability, based on the failover capabilities of the clustered servers. You can
refer to the MSDTC section of the following blog about determine whether the Microsoft Distributed Transaction Coordinator (MSDTC) cluster resource must be created.
Reference:http://msdn.microsoft.com/en-us/library/ms189910.aspx#MSDTC
2. The Cluster Resource Group is where SQL Server failover cluster resource will be placed. Each clustered SQL Server will belong to a Failover
Cluster Resource Group. For example, if you had configure a two node SQL Server Cluster, each clustered instance on the two node belong to a same Cluster Resource Group.
You can change the Cluster Resource Group name, but notes the following name is reserved and already used as Resource Group names: Available Storage, Cluster Group.
3. Each SQL Server cluster is assigned a virtual Network name and IP address, which client applications use to connect to the clustered SQL Server.
4. Not familiar with SCVMM, SCOM, Orchestrator, but you should install the Database Engine Services and SQL Server Management tools.If you want to use SQL Server Reporting Services, you can install Reporting Servers, but Report Server service cannot participate
in a failover cluster.
5. You can use isolated disk for user database and temp DB of each SQL Server Cluster
6. Yes. You should use Cluster Disks which add to Clustered Shared Volumes to host the data file and log of databases.
http://www.pythian.com/blog/how-to-install-a-clustered-sql-server-2012-instance-step-by-step-part-1/
Regards,
Fanny Liu
Fanny Liu
TechNet Community Support

New SQL Server Failover Cluster Installation - No disk is available to select in section "Cluster Disk Slection"

Hello Everyone,
I am in a deep need for your help regarding the problem I am facing.
I am doing a New SQL Server Failover Cluster Installation in a virtual server that is part of a failover cluster. I am able to complete all the steps successfully but, when I reach the point where I am supposed to select the shared disk that will
be included in the SQL server resource cluster group, I don't find any disk in the list (as u can see in the figure below).
I have already created the a 2 nodes failover cluster and added 3 disks (1 as a witness in Quorum and 2 other available storage).
No roles were created, 2 nodes are available and 1 network is there in the cluster.
If u take a look at the message it say: "The search for mount points failed. Error: the system cannot find the path specified". What is this and how can I solve this issue??
Thanks in advance for your support and looking forward for your valuable feedbacks.
Mark as answer if it was an answer for you question.. Please don't hesitate to ask for any further help..

Dear Ashwin,
I have granted the privileges mentioned in the link you provided as below:
Act as Part of the Operating Sywstem = SeTcbPrivileg
  Bypass Traverse Checking = SeChangeNotify
  Lock Pages In Memory = SeLockMemory
  Log on as a Batch Job = SeBatchLogonRight
  Log on as a Service = SeServiceLogonRight
  Replace a Process Level Token = SeAssignPrimaryTokenPrivilege
I was not able to solve the problem by giving these privileges to the domain account I am using to install SQL.
Mark as answer if it was an answer for you question.. Please don't hesitate to ask for any further help..

How Can we force the Hyper-V Replica to use a dedicated network between two hyper-v hosts?

Dear Team,
How can we force Hyper-V Replica to use a dedicated network between two hyper-v hosts?
For live migration, we can choose the desired network in Hyper-V Manager (Use these IP addresses for Live Migration).
I have two 10G adapters teamed together, the virtual switch is created on top as converged network with several vNICs (MangementOS, LiveMigratrion, Backup, etc...)
Each network is set with a specific VLAN to isolate the traffic.
The two Hyper-V hosts are on the same LAN and domain.
Thank you.
Regards,

I have accomplished this by using a DNS pointer specifying an IP address on that dedicated network. That will force traffic done that network.
John Johnston

Configure SSL SQL Server 2012 Cluster Instance

Hi,
I am trying to configure a SSL Certificate on a named clustered instance but i can't
This is the errorlog message
2014-12-11 14:28:51.49 spid10s Error: 17182, Severity: 16, State: 1.
2014-12-11 14:28:51.49 spid10s TDSSNIClient initialization failed with error 0xd, status code 0x38. Reason: An error occurred while obtaining or using the certificate for SSL. Check settings in Configuration
Manager. The data is invalid.
2014-12-11 14:28:51.49 spid10s Error: 17182, Severity: 16, State: 1.
2014-12-11 14:28:51.49 spid10s TDSSNIClient initialization failed with error 0xd, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. The data is invalid.
2014-12-11 14:28:51.49 spid10s Error: 17826, Severity: 18, State: 3.
2014-12-11 14:28:51.49 spid10s Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error
log.
2014-12-11 14:28:51.50 spid10s Error: 17120, Severity: 16, State: 1.
2014-12-11 14:28:51.50 spid10s SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

Hi Jame,
According to your description, you encountered the error when you were trying to configure a named clustered instance to use SSL certificate.
Based on my research, the error 17182 "TDSSNIClient initialization failed with error 0xd, status code 0x38" occurs specifically because of the fact that the string under Certificate value cannot be properly converted back to a valid thumbprint
of the certificate.
A common root cause for these symptoms is an invisible character that may have been inadvertently added to the certificate's Thumbprint value, when it gets copied out of the Certificates snap-in's rich-edit control in MMC. For example, if the thumbprint
contains the Unicode character, then it may cause this issue, the following similar issue is for your reference:
http://blogs.msdn.com/b/sqljourney/archive/2013/07/23/when-using-ssl-sql-failover-cluster-instance-fails-to-start-with-error-17182.aspx
For more details and the resolution about this issue, please refer to the following article:
https://support.microsoft.com/kb/2023869?wa=wsignin1.0
If you have any question, please feel free to let me know.
Regards,
Jerry Li

Disable Remote Resigtry service for SQL Server failover cluster

Hi,
Is it safe to disable Remote Registry service from the the two nodes of SQL Server failover clustering?
Operating system: Microsoft Server 2008 R2 Enterprise Edition (64-bit)
Database software: Microsoft SQL Server 2008 R2 Enterprise Edition (64-bit), Failover Clustering
Thank you.
Regards,
Gan

Hi Pradeep,
You are right. I tested and verified that the GUI of cluster (Failover Cluster Manager) was not working properly after disabling Remote Registry service. Thank you :)
Regards,
Gan

DSC, SQL Server 2012 Enterprise sp2 x64, SQL Server Failover Cluster Install not succeeding

Summary: DSC fails to fully install the SQL Server 2012 Failover Cluster, but the identical code snippet below run in powershell ise with administrator credentials works perfectly as does running the SQL server install interface.
In order to develop DSC configurations, I have set up a Windows Server 2012 R2 failover cluster in VMware Workstation v10 consisting of 3 nodes. All have the same Windows Server 2012 version and have been fully patched via Microsoft Updates.
The cluster properly fails over on command and the cluster validates. Powershell 4.0 is being used as installed in windows.
PDC
Node1
Node2
The DSC script builds up the parameters to setup.exe for SQL Server. Here is the cmd that gets built...
$cmd2 = "C:\SOFTWARE\SQL\Setup.exe /Q /ACTION=InstallFailoverCluster /INSTANCENAME=MSSQLSERVER /INSTANCEID=MSSQLSERVER /IACCEPTSQLSERVERLICENSETERMS /UpdateEnabled=false /IndicateProgress=false /FEATURES=SQLEngine,FullText,SSMS,ADV_SSMS,BIDS,IS,BC,CONN,BOL /SECURITYMODE=SQL /SAPWD=password#1 /SQLSVCACCOUNT=SAASLAB1\sql_services /SQLSVCPASSWORD=password#1 /SQLSYSADMINACCOUNTS=`"SAASLAB1\sql_admin`" `"SAASLAB1\sql_services`" `"SAASLAB1\cubara01`" /AGTSVCACCOUNT=SAASLAB1\sql_services /AGTSVCPASSWORD=password#1 /ISSVCACCOUNT=SAASLAB1\sql_services /ISSVCPASSWORD=password#1 /ISSVCSTARTUPTYPE=Automatic /FAILOVERCLUSTERDISKS=MountRoot /FAILOVERCLUSTERGROUP='SQL Server (MSSQLSERVER)' /FAILOVERCLUSTERNETWORKNAME=SQLClusterLab1 /FAILOVERCLUSTERIPADDRESSES=`"IPv4;192.168.100.15;LAN;255.255.255.0`" /INSTALLSQLDATADIR=M:\SAN\SQLData\MSSQLSERVER /SQLUSERDBDIR=M:\SAN\SQLData\MSSQLSERVER /SQLUSERDBLOGDIR=M:\SAN\SQLLogs\MSSQLSERVER /SQLTEMPDBDIR=M:\SAN\SQLTempDB\MSSQLSERVER /SQLTEMPDBLOGDIR=M:\SAN\SQLTempDB\MSSQLSERVER /SQLBACKUPDIR=M:\SAN\Backups\MSSQLSERVER > C:\Logs\sqlInstall-log.txt "
Invoke-Expression $cmd2
When I run this specific command in Powershell ISE running as administrator, logged in as domain account that is in the Node1's administrators group and has domain administrative authority, it works perfectly fine and sets up the initial node properly.
When I use the EXACT SAME code above pasted into my custom DSC resource, as a test with a known successful install, run with the same user as above, it does NOT completely install the cluster properly. It still installs 17 applications
related to SQL Server and seems to properly configure everything except the cluster. The Failover Cluster Manager shows that the SQL Server Role will not come on line and the SQL Server Agent Role is not created.
The code is run on Node1 so the setup folder is local to Node1.
The ConfigurationFile.ini files for the two types of installs are identical.
Summary.txt does have issues..
Feature:                       Database Engine Services
Status:                        Failed: see logs for details
Reason for failure:            An error occurred during the setup process of the feature.
Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name:                SQL Server Database Engine Services Instance Features
Component error code:          0x86D8003A
Error description:             The cluster resource 'SQL Server' could not be brought online. Error: There was a failure to call cluster code from a provider. Exception message: Generic
failure . Status code: 5023. Description: The group or resource is not in the correct state to perform the requested operation. .
It feels like this is a security issue with DSC or an issue with the setup in SQL Server, but please note I have granted administrators group and domain administrators authority. The nodes were built with the same login. Windows firewall
is completely disabled.
Please let me know if any more detail is required.

Hi Lydia,
Thanks for your interest and help.
I tried "Option 3 (recommended)" and that did not help.
The issue I encounter with the fail-over cluster only occurs when trying to install with DSC!
Using the SQL Server Install wizard, Command Prompt and even in Powershell by invoking the setup.exe all work perfectly.
So, to reiterate, this issue only occurs while running in the context of DSC.
I am using the same domain login with Domain Admin Security and locally the account has Administrators group credentials. The SQL Server Service account also has Administrators Group Credentials.

SQL SERVER Failover Cluster switch failure because the passive node automatically reassign drive letter

I switch the sql server resource group to the standby node , when the disk resource ready bring online in the passive node ,then occur exception. because the original dependency disk resource the drive letter is 'K:' , BUT when the disk bring online , it
automatically reassign new drive letter 'H:' , So the sql server resource couldnot bring online . And After Manual modify the drive letter to 'K:' in the passive node , It Works ! So my question is why it not use the original drive letter
and reassign a new one . what reasons would be cause it ? mount point ? Some log as follows:
00001cbc.000004e0::2015/03/12-14:41:11.377 WARN [RES] Physical Disk <FltLowestPrice_K>: OnlineThread: Failed to set volguid \??\Volume{e32c13d5-02e6-4924-a2d9-59a6fae1a1be}. Error: 183.
00001cbc.000004e0::2015/03/12-14:41:11.377 INFO [RES] Physical Disk <FltLowestPrice_K>: Found 2 mount points for device \Device\Harddisk8\Partition2
00001cbc.00001cdc::2015/03/12-14:41:11.377 INFO [RES] Physical Disk: PNP: Update volume exit, status 1168
00001cbc.00001cdc::2015/03/12-14:41:11.377 INFO [RES] Physical Disk: PNP: Updating volume
\\?\STORAGE#Volume#{1a8ddb8e-fe43-11e2-b7c5-6c3be5a5cdca}#0000000008100000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
00001cbc.00001cdc::2015/03/12-14:41:11.377 INFO [RES] Physical Disk: PNP: Update volume exit, status 5023
00001cbc.000004e0::2015/03/12-14:41:11.377 ERR [RES] Physical Disk: Failed to get volname for drive H:\, status 2
00001cbc.000004e0::2015/03/12-14:41:11.377 INFO [RES] Physical Disk <FltLowestPrice_K>: VolumeIsNtfs: Volume
\\?\GLOBALROOT\Device\Harddisk8\Partition2\ has FS type NTFS
00001cbc.000004e0::2015/03/12-14:41:11.377 INFO [RES] Physical Disk: Volume
\\?\GLOBALROOT\Device\Harddisk8\Partition2\ has FS type NTFS
00001cbc.000004e0::2015/03/12-14:41:11.377 INFO [RES] Physical Disk: MountPoint H:\ points to volume
\\?\Volume{e32c13d5-02e6-4924-a2d9-59a6fae1a1be}\

Sounds like you have an cluster hive that is out of date/bad, or some registry settings which are incorrect. You'll want to have this question transferred to the windows forum as that's really what you're asking about.
-Sean
The views, opinions, and posts do not reflect those of my company and are solely my own. No warranty, service, or results are expressed or implied.

Exploring AlwaysOn Failover Cluster Instances in SQL Server 2014 Tecnet Labs

I like the Labs and have found them very usful. I have a problem with: Exploring AlwaysOn Failover Cluster Instances in SQL Server 2014. The lab starts but hangs on opening SQLONE and the Manual never loads. I have tried coming out and starting again but
get returned to the same failing session. I thought I would mention it here as the is no way to feedback a response as the appraisal only happens once the lab is completed, i.e. no apparent link on the lab site. The session ends when the HOL is reported
as not responding.

Hi,
I'd try this first:
https://vlabs.holsystems.com/vlabs/SystemRequirements.aspx
If that's no help, try the 'Help and Support' link on this page:
https://vlabs.holsystems.com/vlabs/technet?eng=VLabs&auth=none&src=vlabs&altadd=true&labid=12693#
Don't retire TechNet! -
(Don't give up yet - 13,085+ strong and growing)

How to Perform Forced Manual Failover of Availability Group (SQL Server) and WSFC (Windows Server Failover Cluster)

I have a scenario with the three nodes with server 2012 standard, each running an instance of SQL Server 2012 enterprise, participate in a
single Windows Server Failover Cluster (WSFC) that spans two data centers.
If the nodes in the primary data center are unavailable due to data center outage. Then how I can able to access node in the WSFC (Windows Server Failover Cluster) in the secondary disaster recovery data center automatically with some script.
I want to write script that can be able to check primary data center by pinging some IP after every 5 or 10 minutes.
If that IP is unable to respond then script can be able to Perform Forced Manual Failover of Availability Group (SQL Server) and WSFC (Windows Server Failover Cluster)
Can you please guide me for script writing for automatic failover in case of primary datacenter outage?

please post you question on failover clusters in the cluster forum. THey will explain how this works and point you at scipts.
You should also look in the Gallery for cluster management scripts.
¯\_(ツ)_/¯

How to Perform Forced Manual Failover of Availability Group (SQL Server) and WSFC (Windows Server Failover Cluster) with scrpiting

I have a scenario with the three nodes with server 2012 standard, each running an instance of SQL Server 2012 enterprise, participate in a
single Windows Server Failover Cluster (WSFC) that spans two data centers.
If the nodes in the primary data center are unavailable due to data center outage. Then how I can able to access node in the WSFC (Windows Server Failover Cluster) in the secondary disaster recovery data center automatically with some script.
I want to write script that can be able to check primary data center by pinging some IP after every 5 or 10 minutes.
If that IP is unable to respond then script can be able to Perform Forced Manual Failover of Availability Group (SQL Server) and WSFC (Windows Server Failover Cluster)
Can you please guide me for script writing for automatic failover in case of primary datacenter outage?

You are trying to implement manually what should be happening automatically in the cluster. If the primary SQL Server becomes unavailable in the data center, it should fail over to the secondary SQL Server automatically. Is that not working?
You also might want to run this configuration by some SQL experts. I am not a SQL expert, but if you have both hosts in the data center in a cluster, there is no need for replication between those two nodes as they would be accessing
the database from some form of shared storage. Then it looks like you are trying to implement Always On to the DR site. I'm not sure you can mix both types of failover in a single configuration.
FYI, it would make more sense to establish a file share witness in your DR site instead of placing a third node in the data center for Node Majority quorum.
. : | : . : | : . tim

How to install a DB Instance in a SQL Server 2005 cluster

Hi all,
I have an installation scenaro is install SCS/CI in machine A, and DB instance on a already exist cluster. This is based on Windows 2003 SR2 and SQL Server 2005 cluster. But now after i finish SCS, i don't know how to install the DB instance. Do i just need sign in the active node of the DB cluster and start the sapinst.exe. I am worry about any of my mis-action will broke the cluster.. Appreciate any tips or idea about it, thanks.
Peter

directly start sapinst.exe on the cluster node.

Dedicated network for AlwaysON replication traffic when a replica is a Failover Cluster Instance

Hi,
We are planning to setup dedicated network for our Availability Group replication traffic. We have a Failover Cluster Instance as the primary replica and a standalone SQL server instance as the secondary.
I understand that we will need to manually configure the database mirroring endpoints on both the replicas to listen on the specific IP.
But how do I configure the database mirroring endpoint on the Failover Cluster Instance ?
Please help.
Thanks and Regards,
Jisha

If you have a dedicated network for your Availability Group replication traffic between the FCI and the standalone instance, you need to identify if there will be other network services included in the mix. For example, your public network is already using
it's own DNS server by virtue of Active Directory integration. Your dedicated network for replication traffic may or may not have its own DNS server so configuring the endpoints would involve using either IP addresses like the one highlighted in the
blog post or using hosts file with fully qualified domain names so you can use them when creating the endpoints
Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
Blog |
Twitter | LinkedIn
SQL Server High Availability and Disaster Recover Deep Dive Course

Sql Server 2012 Cluster IP Responses to MS Dynamics APP server broadcasts

Hi All,
We are facing issues in our brand new MS Dynamics AX 2012 R3 installation with clustered MS SQL 2012.
The DB server responses to the APP servers is like broadcasting to every system connected to the subnet. In our case that subnet is 192.168.2.0/24. But the packets sent from the AOS / APP server is not refelecting on other machines. We haven't made any changes
to the routing / switching config after the installation.
Attaching a screenshot for your reference.
Please guide us on what can be done to find the cause and solve it
Thanks,
Sriram A Das

Hi D. Graf,
According to my knowledge, you can choose the order (each server's IP address-> SQL Server instance IP-> Failover cluster instance IP) to change these IP addresses.
And before the process, please take SQL Server Cluster Instance Offline in Failover Cluster Manager . For more details, please review the following articles.
How to change the IP address of the cluster nodes hosting a SQL Server instance
http://iamoffthebus.wordpress.com/2012/03/30/how-to-change-the-ip-address-of-the-cluster-nodes-hosting-a-sql-server-instance/
Change the IP Address of a Failover Cluster Instance
http://msdn.microsoft.com/en-us/library/ms190460(v=sql.110).aspx
In addition, about network adapter issues and cluster nodes issues, I would like to
recommend you post the question in the Windows
server clustering forum at
https://social.technet.microsoft.com/Forums/windowsserver/en-US/home?forum=winserverClustering
. It is appropriate and more experts will assist you.
Thanks,
Lydia Zhang
If you have any feedback on our support, please click
here.

Can a SQL Server Failover Cluster Instance (FCI) be Implemented Between Two Hyper-V Hosted Virtual Machines?

Similar Messages

Maybe you are looking for