Monday, March 19, 2012

Migrate from non-cluster to Cluster

I have a single SQL 2000 Enterprise server and I need to turn it into a
cluster. We have several applications using SQL, so the hostname and
configuration of the cluster must be the same as the existing single server.
The operating system is WS2003E and they are in a AD domain.
Is there a fairly easy migration path from a single to clustered
configuration, or do I have to setup two new servers and somehow get the
cluster to use the old hostname? Do I just do a SQL backup of the old
server, power it off, setup the cluster using the old hostname and then do a
SQL restore? I need to minimize downtime and I can't reconfigure the
applications to point to another SQL server.
Do I register the SPNs for the virtual hostname of the cluster?
Thanks,
Derek
Reusing the name is not really an option for several reasons (AD name
conflict, DNS name conflict, SQL cluster naming options). You can use DNS to
alias the old name to the new name.
While it is possible to migrate a non-clustered instance to a clustered
instance, I would recommend setting up a new system. That way if anything
goes wrong, your existing system is right there to pick up and run. Failure
isn't so painful. You can use manual log shipping or a simple log shipping
script to minimize downtime by getting your new server 'close' to the old
one. Be sure and plan the cutover process and test it (maybe in a smaller
scale using a couple of SQL instances on a test box).
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Derek" <dseaman@.spawar.navy.mil> wrote in message
news:ep1mEXCyEHA.3584@.TK2MSFTNGP10.phx.gbl...
> I have a single SQL 2000 Enterprise server and I need to turn it into a
> cluster. We have several applications using SQL, so the hostname and
> configuration of the cluster must be the same as the existing single
server.
> The operating system is WS2003E and they are in a AD domain.
> Is there a fairly easy migration path from a single to clustered
> configuration, or do I have to setup two new servers and somehow get the
> cluster to use the old hostname? Do I just do a SQL backup of the old
> server, power it off, setup the cluster using the old hostname and then do
a
> SQL restore? I need to minimize downtime and I can't reconfigure the
> applications to point to another SQL server.
> Do I register the SPNs for the virtual hostname of the cluster?
> Thanks,
> Derek
>
>
|||How about if I backup the non-clustered server, remove it from AD, and built
up a cluster with the virtual name being the name of the old SQL server and
then do a SQL restore? We have too many apps to be changing the name, and I
hate to play tricks with DNS that are prone to human error.
Derek
"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
news:eKaQfWDyEHA.1188@.tk2msftngp13.phx.gbl...
> Reusing the name is not really an option for several reasons (AD name
> conflict, DNS name conflict, SQL cluster naming options). You can use DNS
> to
> alias the old name to the new name.
> While it is possible to migrate a non-clustered instance to a clustered
> instance, I would recommend setting up a new system. That way if anything
> goes wrong, your existing system is right there to pick up and run.
> Failure
> isn't so painful. You can use manual log shipping or a simple log
> shipping
> script to minimize downtime by getting your new server 'close' to the old
> one. Be sure and plan the cutover process and test it (maybe in a smaller
> scale using a couple of SQL instances on a test box).
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "Derek" <dseaman@.spawar.navy.mil> wrote in message
> news:ep1mEXCyEHA.3584@.TK2MSFTNGP10.phx.gbl...
> server.
> a
>
|||Try this in a test environment first.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Derek" <dseaman@.spawar.navy.mil> wrote in message
news:uyD4T%23czEHA.3336@.TK2MSFTNGP11.phx.gbl...
> How about if I backup the non-clustered server, remove it from AD, and
built
> up a cluster with the virtual name being the name of the old SQL server
and
> then do a SQL restore? We have too many apps to be changing the name, and
I[vbcol=seagreen]
> hate to play tricks with DNS that are prone to human error.
> Derek
>
> "Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
> news:eKaQfWDyEHA.1188@.tk2msftngp13.phx.gbl...
DNS[vbcol=seagreen]
anything[vbcol=seagreen]
old[vbcol=seagreen]
smaller[vbcol=seagreen]
the
>

No comments:

Post a Comment