Changing addresses of clustered SQL Server hosts.

We have created a Windows 2012 R2 cluster to host SQL Server 2014 in MS Azure (IaaS).

We've found that we need to move these to a different resource group and will have to give them both new static IP Addresses.

Alternatively, we could build a new DB cluster, however having spent several weeks so far, we'd like to just change the addresses.  We don't know how "challenging" that is though and so we're looking for information on how to do so.  I haven't been able to find anything via the Googling I've done so far, but I'm thinking the experts on Windows clustering will know of some places where the process is described.

So I'm looking for links and also some rough idea of how problematic it could be.
LVL 1
Gene KlamerusTechnical ArchitectAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

lcohanDatabase AnalystCommented:
Actually there is a pretty good article here https://mssqlnuggets.wordpress.com/2017/06/13/change-vlans-ip-addresses-of-a-sql-server-failover-cluster-instance/ and the only difference is that this is for VM's and not physicals but that is not 100% clear what your actual configuration is.
Microsoft has some of their own but not that complete here: https://docs.microsoft.com/en-us/sql/sql-server/failover-clusters/windows/change-the-ip-address-of-a-failover-cluster-instance?view=sql-server-2014
At my place the systems guys are usually doing this kind of work ad DBA's don't have admin domain rights, OU rights where WFC config is stored, etc. during downtime and as it looks pretty scary and painful to do I believe is possible without too much "damage" if all is done as described at first links and in particular if nothing is running on it yet.
If you have any production on it one thing that must be done is to fully backup all your DB's - system(master,msdb) and user and keep a copy handy just in case. Alternatively - images can be taken so rollback is less painful if ever need to go back.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Raja Jegan RSQL Server DBA & Architect, EE Solution GuideCommented:
As you might be moving the VM to new Resource groups, I would suggest to try the first link provided by lcohan.
Ideally, it should work as it is just the IP changes but if it has any problems, I would suggest configuring the Cluster from scratch to avoid any unexpected issues.
0
Gene KlamerusTechnical ArchitectAuthor Commented:
As stated, this is MS Azure, so these are VMs.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Raja Jegan RSQL Server DBA & Architect, EE Solution GuideCommented:
Yes, after you move your resource groups, it would be assigned with a new IP..
Kindly follow the steps mentioned in the first link and try changing IP address across all the necessary places and test whether it works or not.
If not, then start from the scratch..
0
lcohanDatabase AnalystCommented:
So if they are VM's and the databases attached to the cluster are not very large I would try clone the SQL Cluster using details from here https://blogs.msdn.microsoft.com/psssql/2016/07/06/tips-tricks-on-cloning-azure-sql-virtual-machines-from-captured-images/ and if possible shutdown the existing one so you have solid/quick fail-back then work on the new cloned SQL cluster to bring it up and change the IP's on this clone. Later on assuming it is all good all left is to just discard the old clones and take a fresh snapshot of new one.
0
Gene KlamerusTechnical ArchitectAuthor Commented:
First the response was very helpful.  Coincidentally, as of today (after my response) we were informed that the resource groups we need to move this DB cluster between are both in the same Azure subscription and hence we don't need to switch any addresses so I'm afraid the information won't be applied, but we appreciate the quick and complete response nonetheless.

Thanks
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows OS

From novice to tech pro — start learning today.