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.
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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
As stated, this is MS Azure, so these are VMs.
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..
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..
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.
ASKER
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
Thanks
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.