Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2005-09-19 : 07:41:46
|
| Gerry writes "I have an active/passive 2 node cluster running MS SQL Server 200 SP3 attached to a SAN. The SAN data is replicated to a contingency site where I have a single node cluster.In the event of contingency I want as little manual intervention as possible and for the transfer of service to be as seamless as possible to users. The contingency virtual server should therefore be the same name as the live virtual server. Obvioulsy I cannot have two virtual servers with the same name presented on the LAN at the same time. To do this (and I am about to try this out) I think the following will work;1. Isolate the single node cluster from our LAN by connecting it to a stand alone hub.2. Isolate a live Domain Controller from our LAN and connect it to the hub above.3. Perform a System Stae backup of the DC.4. Delete the existing Computer Account for the Virtual Server from the DC. The Computer Account exists because we use Kerberos authentication.5. Install SQL Server 2003 SP3 on the single node cluster using the live virtual server name but a diiferent IP Address.6. Use an existing domain account to run the SQL Services.7. Take all SQL Services offline, as well as the Network Name.8. Restore the System State to the Domain Controller.9. Re-attach the DC to our LAN and demote it.My question is WILL this work and is there a better way?" |
|
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
Posted - 2005-09-19 : 09:50:38
|
| wow, that is lot of work.why don't you just make an alias in the DNS instead? -ec |
 |
|
|
Michael Valentine Jones
Yak DBA Kernel (pronounced Colonel)
7020 Posts |
Posted - 2005-09-19 : 10:49:45
|
| The procedure you outlined seems way too complicated to work in the real world, expecially messing with the domain controllers and reconfiguring the network.I would think it would be better to re-point the applications to the new server. It depends on the application, but we usually have a .INI file in our applications with the server name, and if we have to move to a new server, we just change that. The .INI is on a network share, so we just have to change that.CODO ERGO SUM |
|
|
|
|
|
|
SQL Server 2000, Cluster & SAN