Issues with moving existing single production server setup to a New Cluster installation

According to the documentation the chosen Cluster name and IP address need
to be unused before installing the cluster. The IP address is not a problem,
but it will be a difficult task with the Cluster Name as the business
processes have many scripts, DTS packages, stored procedures and views that
have the production server name hard coded. There are many other servers
involved for updating and transferring data, so there was no way around it
and I would like to keep it that way if possible.
Therefore, my question is how can I reuse the production server name for the
cluster without jeopardising the Cluster installation ?
Hello,
You may need to rename the current production server name "ServerA" to
another name before installing virtual server. After that, you could reuse
the name "ServerA" as the virtual server name.
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||You can't, however there are a lot of workarounds. If you are in an AD/DNS
envorinment, you can create an alias record that points the old name to the
new server. You can also set up a SQL alias on each client, but that is
generally harder.
Geoff N. Hiten
Microsoft SQL Server MVP
"GMG" <nospam@.nospam.com> wrote in message
news:uNQ4jV6dFHA.4060@.TK2MSFTNGP10.phx.gbl...
> According to the documentation the chosen Cluster name and IP address need
> to be unused before installing the cluster. The IP address is not a
> problem,
> but it will be a difficult task with the Cluster Name as the business
> processes have many scripts, DTS packages, stored procedures and views
> that
> have the production server name hard coded. There are many other servers
> involved for updating and transferring data, so there was no way around it
> and I would like to keep it that way if possible.
> Therefore, my question is how can I reuse the production server name for
> the
> cluster without jeopardising the Cluster installation ?
>