Thanks! I will check that out. I believe I have 1 very small advantage - pretty sure this isn't supposed to be a multi-site cluster, so that eliminates a bit of configuration (in our case, we need a script to run at failover, so that the LUNs at the DR site are marked as the "active" copy in our RecoverPoint replication).
On Fri, Nov 3, 2017 at 10:09 PM, Damien Solodow <[email protected]> wrote: > I did something quite similar and made use of this guide: > https://dba.stackexchange.com/questions/139282/sql-server-2012-on-a-windows-2008-r2-cluster-would-like-to-upgrade-windows-to-2 > > > It worked quite well. :) > > > > DAMIEN SOLODOW > IT Engineering Lead > 317.447.6033 (office) > 317.447.6014 (fax) > HARRISON COLLEGE > ________________________________ > From: [email protected] <[email protected]> on > behalf of Michael Leone <[email protected]> > Sent: Friday, November 3, 2017 2:36:57 PM > To: [email protected] > Subject: [NTSysADM] Re: Advice: moving SQL cluster instance from 1 cluster > to another > > Anyone? Teachable comments most welcome ... > > On Thu, Nov 2, 2017 at 10:41 AM, Michael Leone <[email protected]> wrote: >> Looking for some advice. I've just been told that in a couple weeks, >> I've got some cluster re-arranging to do. (Mind you, I've had a week's >> vacation scheduled for the last 6 months, so I really only have 1 week >> to do this ...) >> >> Here's what I have now: >> >> Windows 2008 R2 / SQL 2008 R2 cluster (call it "UnusedSQLCluster) >> - This is a 1 node cluster, at the moment. >> Windows 2008 R2 / SQL 2008 R2 cluster with 3 named SQL instances >> - This is a 2 node cluster >> >> So here's what they want. >> >> Get rid of UnusedSQLCluster; reformat it as a Win2012 R2/SQL 2012 R2 >> cluster. >> Move one of the named SQL instances to what used to be >> UnusedSQLCluster but *keeping* the current instance name and IP >> address. >> >> Got all that? >> >> So here's what I think I need to do. >> >> Gracefully uninstall the old UnususedSQLCluster (both SQL and Win >> clusters); >> (This should be relatively straightforward - uninstall SQL node; evict >> Windows node) >> reformat it and install Win 2012 R2/SQL 2012 R2, using a temporary SQL >> cluster name - "TempSQLCluster". >> >> Uninstall SQLInstance01 from the cluster it is in. >> (this cluster remains in production, servicing the 2 other SQL instances) >> >> Rename TempSQLCluster to SQLInstance01, using same IP address, >> >> Have I missed a step? >> >> BIG QUESTIONS / CONCERNS: >> >> 1. It is possible to rename a SQL cluster instance name to something >> else, that looks straightforward enough. And there is no log shipping, >> event forwarding, etc, that I know of. I know I may have to do some >> DNS cleanup. >> >> 2. I know that SQL cluster instances register themselves into AD, >> hence why I want to gracefully uninstall everything. But re-using the >> same SQL instance name should be OK? Or do I need to clean that object >> out of AD after uninstalling it? >> >> I did this once, months ago, and I know I didn't do all the steps >> properly at that time, as my boss deleted the AD account of a SQL >> instance without uninstalling it first. So it's still there in SQL, in >> a zombie state. >> >> What have I missed? What do I need to look out for? (DNS, etc) >> >> I'm sure I didn't explain everything clearly enough, so feel free to >> interrogate further. > >
