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
>
Showing posts with label advice. Show all posts
Showing posts with label advice. Show all posts
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, 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
>
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
>
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
>
Wednesday, March 7, 2012
Removing Guest and BUILTIN\Administrator accounts
Alll, I am looking for advice on disabling the "guest" account on SQL Server
2000.
-Are there any negatives or issues with doing this?
I am also looking to remove the BUILTIN\administrator account.
-Are there any negtive implications of removing this account?You can remove the guest user account from all database
except for master and tempdb. The guest account is needed in
these databases.
In terms of removing the builtin\administrators group, it
depends. The following article has an additional information
section with links to some issues that could come up:
INF: How to impede Windows NT administrators from
administering a clustered instance of SQL Server
http://support.microsoft.com/?id=263712
-Sue
On Fri, 27 Feb 2004 12:16:08 -0800, "RobDowdy"
<anonymous@.discussions.microsoft.com> wrote:
>Alll, I am looking for advice on disabling the "guest" account on SQL Serve
r 2000.
>-Are there any negatives or issues with doing this?
>I am also looking to remove the BUILTIN\administrator account.
>-Are there any negtive implications of removing this account?|||Usually you would replace the Builtin\administrators login with one of your
own creation. I create a group in AD called SQLAdmins, map it to a login in
SQL Server, make it a member of the sysadmins fixed server role. If the
service account is getting sysadmin permission thru membership in the local
administrators group, be sure and add the service account to your new
SQLAdmins group in AD.
Remove Pubs and Northwind from a production server.
Don't create a guest account in any production databases.
Refrain from using the public role to grant permissions to users.
Bill
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:s8bv301qe57kudb5vs2h72ah2vr52k1kdt@.
4ax.com...
> You can remove the guest user account from all database
> except for master and tempdb. The guest account is needed in
> these databases.
> In terms of removing the builtin\administrators group, it
> depends. The following article has an additional information
> section with links to some issues that could come up:
> INF: How to impede Windows NT administrators from
> administering a clustered instance of SQL Server
> http://support.microsoft.com/?id=263712
> -Sue
> On Fri, 27 Feb 2004 12:16:08 -0800, "RobDowdy"
> <anonymous@.discussions.microsoft.com> wrote:
>
Server 2000.
>
2000.
-Are there any negatives or issues with doing this?
I am also looking to remove the BUILTIN\administrator account.
-Are there any negtive implications of removing this account?You can remove the guest user account from all database
except for master and tempdb. The guest account is needed in
these databases.
In terms of removing the builtin\administrators group, it
depends. The following article has an additional information
section with links to some issues that could come up:
INF: How to impede Windows NT administrators from
administering a clustered instance of SQL Server
http://support.microsoft.com/?id=263712
-Sue
On Fri, 27 Feb 2004 12:16:08 -0800, "RobDowdy"
<anonymous@.discussions.microsoft.com> wrote:
>Alll, I am looking for advice on disabling the "guest" account on SQL Serve
r 2000.
>-Are there any negatives or issues with doing this?
>I am also looking to remove the BUILTIN\administrator account.
>-Are there any negtive implications of removing this account?|||Usually you would replace the Builtin\administrators login with one of your
own creation. I create a group in AD called SQLAdmins, map it to a login in
SQL Server, make it a member of the sysadmins fixed server role. If the
service account is getting sysadmin permission thru membership in the local
administrators group, be sure and add the service account to your new
SQLAdmins group in AD.
Remove Pubs and Northwind from a production server.
Don't create a guest account in any production databases.
Refrain from using the public role to grant permissions to users.
Bill
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:s8bv301qe57kudb5vs2h72ah2vr52k1kdt@.
4ax.com...
> You can remove the guest user account from all database
> except for master and tempdb. The guest account is needed in
> these databases.
> In terms of removing the builtin\administrators group, it
> depends. The following article has an additional information
> section with links to some issues that could come up:
> INF: How to impede Windows NT administrators from
> administering a clustered instance of SQL Server
> http://support.microsoft.com/?id=263712
> -Sue
> On Fri, 27 Feb 2004 12:16:08 -0800, "RobDowdy"
> <anonymous@.discussions.microsoft.com> wrote:
>
Server 2000.
>
Subscribe to:
Posts (Atom)