Showing posts with label hardware. Show all posts
Showing posts with label hardware. Show all posts

Friday, March 30, 2012

Renaming a SQL 2000 Cluster

I need to migrate our SQL 2000 cluster to a new set of hardware and name
the new cluster with the same name as the existing one so that none of the
applications are affected. How do I change name of a SQL Cluster ?
Amila
Unfortunately, the only way to "Change" the virtual network name is to
uninstall and reinstall.
There are really only two choices: in-place system upgrade (rolling upgrade)
or a new cluster installation while aliasing the old SQL Server host name.
Read through the clustering news group as this question comes up quite
frequently.
Sincerely,
Anthony Thomas

"Amila chandrasekera" <achandra@.insight.com> wrote in message
news:O4HMyfDVHHA.4832@.TK2MSFTNGP04.phx.gbl...
> I need to migrate our SQL 2000 cluster to a new set of hardware and name
> the new cluster with the same name as the existing one so that none of the
> applications are affected. How do I change name of a SQL Cluster ?
>
> Amila
>
|||You can also have the older Cluster Virtual Name redirect to the newer name.
This would require NT Admin help but you dont need to do anything at the SQL
end as long as you are sure that you dont need the older cluster anymore and
can get rid of it.
"Anthony Thomas" wrote:

> Unfortunately, the only way to "Change" the virtual network name is to
> uninstall and reinstall.
> There are really only two choices: in-place system upgrade (rolling upgrade)
> or a new cluster installation while aliasing the old SQL Server host name.
> Read through the clustering news group as this question comes up quite
> frequently.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Amila chandrasekera" <achandra@.insight.com> wrote in message
> news:O4HMyfDVHHA.4832@.TK2MSFTNGP04.phx.gbl...
>
>
sql

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
>

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, SimonOne 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
>

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, SimonOne 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 cluste
r
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 sam
e
> 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
>

Tuesday, March 20, 2012

Rename a cluster.. is it possible

We have a single instance cluster on 2 nodes say SQL1. We want to do a
side-by-side upgrade of the underlying hardware and we have another cluster
with 2 nodes already ready and its called SQL2. At the time of cutover, we
want to just rename SQL1 to SQLOld and SQL2 back to SQL1 so that our
applications can connect to SQL1 without having to go through any connection
name changes.
Can it be done ? We've done many of these on standalone SQL instances by
renaming servers.. Wasnt too sure how it works on a cluster. Especially
since we are not dependent on the node names and the applications just
connect to the Virtual SQL instance, I was not too sure how to go about the
same.
Thanks
We are using SQL 2000...
Also in SQL 2005, is it the same or is it better to do this easily ?
Why not just create a DNS alias and use that?
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"Hassan" <hassan@.test.com> wrote in message
news:OI5fRApRIHA.1212@.TK2MSFTNGP05.phx.gbl...
We have a single instance cluster on 2 nodes say SQL1. We want to do a
side-by-side upgrade of the underlying hardware and we have another cluster
with 2 nodes already ready and its called SQL2. At the time of cutover, we
want to just rename SQL1 to SQLOld and SQL2 back to SQL1 so that our
applications can connect to SQL1 without having to go through any connection
name changes.
Can it be done ? We've done many of these on standalone SQL instances by
renaming servers.. Wasnt too sure how it works on a cluster. Especially
since we are not dependent on the node names and the applications just
connect to the Virtual SQL instance, I was not too sure how to go about the
same.
Thanks
We are using SQL 2000...
Also in SQL 2005, is it the same or is it better to do this easily ?
|||I guess we could, but also curious if a rename is possible too ?
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:OvufTE1RIHA.5136@.TK2MSFTNGP04.phx.gbl...
> Why not just create a DNS alias and use that?
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "Hassan" <hassan@.test.com> wrote in message
> news:OI5fRApRIHA.1212@.TK2MSFTNGP05.phx.gbl...
> We have a single instance cluster on 2 nodes say SQL1. We want to do a
> side-by-side upgrade of the underlying hardware and we have another
> cluster
> with 2 nodes already ready and its called SQL2. At the time of cutover, we
> want to just rename SQL1 to SQLOld and SQL2 back to SQL1 so that our
> applications can connect to SQL1 without having to go through any
> connection
> name changes.
> Can it be done ? We've done many of these on standalone SQL instances by
> renaming servers.. Wasnt too sure how it works on a cluster. Especially
> since we are not dependent on the node names and the applications just
> connect to the Virtual SQL instance, I was not too sure how to go about
> the
> same.
> Thanks
> We are using SQL 2000...
> Also in SQL 2005, is it the same or is it better to do this easily ?
>
|||Check out:
http://msdn2.microsoft.com/en-us/library/ms178083.aspx
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"Hassan" <hassan@.test.com> wrote in message
news:u2ulJiASIHA.5128@.TK2MSFTNGP05.phx.gbl...
I guess we could, but also curious if a rename is possible too ?
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:OvufTE1RIHA.5136@.TK2MSFTNGP04.phx.gbl...
> Why not just create a DNS alias and use that?
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "Hassan" <hassan@.test.com> wrote in message
> news:OI5fRApRIHA.1212@.TK2MSFTNGP05.phx.gbl...
> We have a single instance cluster on 2 nodes say SQL1. We want to do a
> side-by-side upgrade of the underlying hardware and we have another
> cluster
> with 2 nodes already ready and its called SQL2. At the time of cutover, we
> want to just rename SQL1 to SQLOld and SQL2 back to SQL1 so that our
> applications can connect to SQL1 without having to go through any
> connection
> name changes.
> Can it be done ? We've done many of these on standalone SQL instances by
> renaming servers.. Wasnt too sure how it works on a cluster. Especially
> since we are not dependent on the node names and the applications just
> connect to the Virtual SQL instance, I was not too sure how to go about
> the
> same.
> Thanks
> We are using SQL 2000...
> Also in SQL 2005, is it the same or is it better to do this easily ?
>