Gurus,

Running SQL Server 2005 SP2 on a cluster (two Windows Server 2003 SP2 nodes,
SQL instance running on each, active/active design).

A hardware refresh cycle has arrived and two new sparkling servers are
online in our data center to replace the old ones. I didn't request this,
they just showed up!!! Nice, huh?

Anyway, what would be the best plan of attack in migrating the SQL instances
off of the old cluster and onto the new? The new OS will be Windows 2008.

--
Spin

Interesting timing - I will be leaving for work in about an hour to begin
our migration to a brand new cluster. For me, the simplest option is a
straight backup/restore, since our new servers are also on a new SAN. We
are retiring the older EVA 5000 and replacing with Netapp SAN.

Here is the process:

- Install SQL Server 2005 SP3 on new servers as new cluster instance
- Run the application install for the current version of the application
(builds default databases and CLR components)
- Restore backups of current system over new databases
- Test the new system (I/O tests, connectivity, application, etc...)

The above has already been done - now, tonight we are going to do the
following:

- Disconnect application servers
- Put databases on current system in restricted mode
- Backup current databases
- Restore databases on new system/instance
- Modify application server connections
- Note: this could also be handled by updating DNS if needed
- Release system to I/S team to test and validate

Back-out plan is real simple, if everything goes bad - bring old system back
online, modify connections and release to users. Identify the problems and
rescheduled.

Jeff

"Spin" <Spin (AT) invalid (DOT) com> wrote

So how did everything go? Any lessons learned?

"Jeffrey Williams" <jeff.williams3188 (AT) verizon (DOT) net> wrote

If this is a critical system, I'd suggest you run the new cluster in parallel
for a period of time. This not only help validate the server hardware, but
also help you nail the entire migration plan and its every single step to
precision so by the time to do real cut over, you'll have full confidence.

Linchi

"Spin" wrote:

Well, just finished up some of the post setup tasks - for example,
re-establish report server mirror and create report server snapshot. The
only real issue we had was that the restore took longer than expected. When
we tested, the restore took 1 hour 45 minutes - but, during the process it
took about 3 1/2 hours.

Other than that - the process went as planned.

"Spin" <Spin (AT) invalid (DOT) com> wrote