Wednesday, March 21, 2012

Rename Cluster Instance - New Hardware - Keep Name

Hello all,
We are moving a sql cluster to new hardware but would like to keep the same
server/virtual instance name.
Could anyone offer some advice on how to go about this or point us in the
direction of some Microsoft how to articles?
Many thanks, Simon
One method that may work is backing up the DBs from the existing instance,
taking the old instance down. Bringing up the new instance on the new cluster
hardware and performing a restore. You may also be able to backup the DBs
onto a volume on the new hardware (over the wire) and then perform a restore
on the new hardware using the .BAK files from the volume on the new hardware.
"Simon" wrote:

> Hello all,
> We are moving a sql cluster to new hardware but would like to keep the same
> server/virtual instance name.
> Could anyone offer some advice on how to go about this or point us in the
> direction of some Microsoft how to articles?
> Many thanks, Simon
>
>
|||Windows clustering depends on unique names within a domain. Keeping an
existing name is almost impossible. You can use DNS to redirect the old
instance name to the new name. When I move servers I generally use a manual
log shipping process to bring the new server "close" to the old one. I then
stop connections to the old server, finalize the logs, apply them to the new
server, then bring the new one up. If you only have a few client machines,
you can set local aliases to redirect connections. Otherwise, DNS is your
friend. Look up the SVC record type for DNS. It allows you to map a name
to an IP address and a specific port.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Simon" <reply@.togroup.com> wrote in message
news:%23$37STSHGHA.1424@.TK2MSFTNGP12.phx.gbl...
> Hello all,
> We are moving a sql cluster to new hardware but would like to keep the
> same server/virtual instance name.
> Could anyone offer some advice on how to go about this or point us in the
> direction of some Microsoft how to articles?
> Many thanks, Simon
>

No comments:

Post a Comment