September 22, 2014 at 2:18 pm
Background information: We have two physical servers in an FCI with SQL Server 2012 Enterprise(SS2k12) and Windows 2008 R2(W2k8r2) is the OS. We are using a SAN from EMC. The virtual servers are VM ware. Servers are old and underpowered and starting to go into year five, without any maintenance agreement in place. Yes, I’m nervous about what could happen.
I’ve been tasked with moving our SS2K12 physical database servers to VM ware virtual servers using a Windows Server Failover Cluster (WSFC) with the primary and secondary talking via AlwaysOn Available Group(AOAG).
Once I’ve finished moving everything I need to and shutdown the physical servers; will I be able to use the DNS name and IP address from the FCI in the AOAG listener address for database connections?
What if everything goes to h… in a hand basket and I need to power on the physical servers to fail back. I know I’ll need to change the AOAG listener name to something different and with a different IP address. Does anyone think bringing the physical server up in correct order will allow me to use the original DNS name and IP address and make the FCI viable again without me jumping through hoops?
Thanks in advance for any advice/comments.
September 22, 2014 at 3:22 pm
Introduce a VM into the existing cluster, this will allow you to retain the physical servers into the config. Once you're happy remove the physical boxes from the cluster
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply