December 26, 2014 at 9:35 am
We are beginning to deploy Always ON with a 3 server architecture where 2 nodes participate in the standard active/passive automatic failover with shared storage. There is also a 3rd node which hosts the secondary replica and does not participate in auto-failover, nor is it a possible owner of the shared storage resources. In order for AO to work, the drive letters must be the same on each server.
This is causing me a problem. When I go to install SQL Server 2012 EE on the 3rd node and give it the default drives for data, log, and tempdb, I get an error message saying I cannot use shared drives for my standalone installation.
Is there a standard procedure or sequence of events documented in bringing up the nodes and installing SQL Server, so one does not run into this drive resource conention issue?
Follow on. Found the sequesnce. Pretty straightfoward, eh?
1. Evict the standalone node
2. Install SQL Server
3. Re-Add the node
December 28, 2014 at 4:12 am
nlion84DBA (12/26/2014)
Follow on. Found the sequesnce. Pretty straightfoward, eh?1. Evict the standalone node
2. Install SQL Server
3. Re-Add the node
Pretty sure this is not supported, waiting for clarification
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
December 31, 2014 at 3:07 am
Hi,
You can check the following blog to add SQL Server AlwaysOn Availability Groups to existing Failover Clusters.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply