Good Afternoon,
We are in the process of migrating our databases that are currently SQL 2005 and SQL 2008 to new servers.
Server OS is Windows 2012 R2 w/ SQL 2012 installed.
SQL Servers are virtual built on ESX 6.0 hosts. Microsoft Clustering is being used along with the SQL Always On technology.
Our DBAs have been able to get SQL 2012 installed, setup the resources in the cluster and not have issues.
One of the applications they are migrating is only certified on SQL 2008. The servers were built and Failover Clustering was installed. The cluster was created and has the core resources..cluster name, cluster IP and FSW for the Quorum.
SQL 2008 was installed on the first node of this cluster without issue. When the DBAs attempt to install it on the second node they are receiving errors during the rule checks.
First error was resolved by using the Install-WindowsFeature RSAT-Cluster-ServerAutomation Command. Ran through the install again and it is failing the rule check looking for a cluster disk. Normally, when SQL 2012 is installed and using Always
On, we do not have to add the disks into cluster since they will not be failing over between nodes.
Is there some difference between how a cluster installation is performed for SQL 2008 vs. SQL 2012?
Are AlwaysOn availability groups an option in SQL 2008? And if so, how do we get past this rule check? Did see where you can run the setup.exe with a switch to skip rules checks, but can't imagine that is a best practice.
Since it is a SQL 2008 cluster, does there need to be at least one shared disk in the cluster? This presents the problem because the nodes of the clusters are in out data centers. The disks are vmdk files.
Any insights would be greatly appreciated. Up to this point all the clusters using the Always On Technology have been Windows 2012 R2\ w SQL 2012 installed. This is the first AO cluster that is using SQL 2008.
Thank You