Re: Migrating stand-alone SQL server to cluster

Yes. You will need to re-apply the latest Service pack and any post-SP
hotfixes you may have had. The installer puts RTM binaries on the new node
and they must be updated.

--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP

"GaryC" <GaryC@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3B5ADAC4-3E42-467B-960D-6BF319F6BD76@xxxxxxxxxxxxxxxx
> Ignore this last post. I found what I did wrong and corrected it. One
> othe
> question though, do I need to run the SP3a update on the cluster node
> again?
> Thanks.
>
> "GaryC" wrote:
>
>> I un-installed the second node successfully, then ran the SQL setup on
>> the
>> 1st node successfully adding the 2nd node as a failover. During the
>> install
>> it prompts for an IP address. I tried to use the exiting virtual
>> server's
>> IP, but it said that it was already in use. So I added a second IP, but
>> it
>> used the cluster heartbeat subnet. So now I have one virtual server with
>> 2
>> SQL IP address objects assigned to it. The original is10.0.3.240, the
>> added
>> IP is 192.168.57.113. Is this OK? Do I need to change the
>> 192.168.57.113
>> to the same subnet as the original? The clients will use the virtual
>> server
>> name so maybe this is OK. Please help me out!!
>> Thanks.
>>
>> "Anthony Thomas" wrote:
>>
>> > Here's a TechNet link. This will reinstall SQL Server on the new
>> > cluster
>> > node; however, to service pack that node is tricky: there is a registry
>> > hack
>> > that you need in order to just update the binaries on the new node.
>> > You
>> > need to contact Microsoft Product Support Services for the procedures
>> > as
>> > they are not published.
>> >
>> > Troubleshooting SQL Server 2000 Failover Clusters
>> > http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/failclus.mspx#EGAA
>> >
>> > Hope this helps.
>> >
>> > Sincerely,
>> >
>> >
>> > Anthony Thomas
>> >
>> >
>> > --
>> >
>> > "GaryC" <GaryC@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> > news:94AAEA9E-0691-453B-913F-4D25BE89A3B0@xxxxxxxxxxxxxxxx
>> > When I select Option 2, the error comes up. "Cancel" exits the setup
>> > and
>> > "OK" brings me back to the menu to choose options 1 or 2. Do I need to
>> > re-run the setup on the new server where the SQL virtual cluster is
>> > installed
>> > and working?
>> >
>> > Gary
>> >
>> > "Geoff N. Hiten" wrote:
>> >
>> > > Option 2) Advanced options. That is where SQL installer hides the
>> > > virtual
>> > > server/failover clustering options.
>> > >
>> > > --
>> > > Geoff N. Hiten
>> > > Senior Database Administrator
>> > > Microsoft SQL Server MVP
>> > >
>> > > "GaryC" <GaryC@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> > > news:CFB27364-C424-4179-81C0-9FCE66775759@xxxxxxxxxxxxxxxx
>> > > >I was able to build the new server as a one-node cluster and
>> > > >installed
>> > the
>> > > > SQL virtual server successfully. The DBs re-attached fine and all
>> > > > the
>> > > > data
>> > > > looks good. I was also able to add the original server as a second
>> > > > node
>> > > > to
>> > > > the cluster, but I'm stuck at the point of re-installing SQL on the
>> > > > it.
>> > > > When
>> > > > I run the SQL setup on the original server (2nd node) I get to
>> > > > specify
>> > the
>> > > > virtual server, then it prompts me to with two options.
>> > > > 1. Upgrade, remove, or add components to an existing instance of
>> > > > SQL
>> > > > server.
>> > > > 2. Advanced options.
>> > > > If I choose 1. then my only path is to "Uninstall". If I choose 2.
>> > > > then
>> > > > it
>> > > > gives me an error saying "Changing installation options at this
>> > > > level is
>> > > > not
>> > > > allowed. If you do this, you will need to exit setup and restart."
>> > > > What am I missing? Do I need to re-run SQL setup on the new server
>> > > > (1st
>> > > > node)?
>> > > >
>> > > > Thanks.
>> > > >
>> > > >
>> > > >
>> > > > "Tony Sebion" wrote:
>> > > >
>> > > >> You should be able to install the clustering service with only one
>> > > >> node
>> > > >> and then install SQL Server on that one node. You can then
>> > > >> transfer
>> > the
>> > > >> databases from the existing server to the new one-node cluster
>> > > >> however
>> > > >> you'd like to copy databases (copy and reattach mdb's, DTS,
>> > > >> restore
>> > > >> backups...). When the databases are moved and accessible on the
>> > > >> cluster, add the 2nd node to the cluster service with Cluster
>> > > >> Administrator, and re-run SQL Server setup to add the SQL Service
>> > > >> to
>> > the
>> > > >> 2nd node.
>> > > >>
>> > > >> Good luck,
>> > > >> Tony Sebion
>> > > >>
>> > > >>
>> > > >> "GaryC" <GaryC@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> > > >> news:B4CBAC01-F83B-413D-BDEE-F8600075BA4C@xxxxxxxxxxxxx:
>> > > >>
>> > > >> > I have a Windows 2003 Enterprise Ed. server running SQL 2000
>> > Enterprise
>> > > >> > Ed.
>> > > >> > with SCSI attached storage. I have a new server (identical
>> > hardware),
>> > > >> > HP
>> > > >> > fiber switches, etc to build a SAN config with the existing
>> > > >> > storage.
>> > I
>> > > >> > can
>> > > >> > build the SAN portion fine, but I don't know how to transition
>> > > >> > the
>> > live
>> > > >> > SQL
>> > > >> > server to a clustered config. Can I install the new server as a
>> > stand
>> > > >> > alone
>> > > >> > cluster with SQL installed, then somehow tie the two together?
>> > > >> > I
>> > don't
>> > > >> > know
>> > > >> > where to start. I've found a lot of info on building SQL
>> > > >> > clusters as
>> > a
>> > > >> > new
>> > > >> > installation, but nothing that addresses this specific scenario.
>> > > >> > Any
>> > > >> > ideas
>> > > >> > or help would be appreciated.
>> > > >>
>> > > >>
>> > >
>> > >
>> > >
>> >
>> >
>> >


.

Relevant Pages

  • Re: error trying to start new maintance plan
    ... One of the "improvements" for SQL 2005 is that the client tool installer is not cluster aware. ... The action you attempted to perform on a remote instance of SQL Server has failed because the action requires a SQL Server component that is not installed on the remote computer. ...
    (microsoft.public.sqlserver.clustering)
  • Re: Push Binaries after installation SQL Server 2000 virtual server
    ... Run the installer to remove then re-add the ... BOL topic 'Maintaining a Failover Cluster' has details. ... I support the Professional Association for SQL Server ... > Windows 2003-based cluster fails to push binaries to the other node. ...
    (microsoft.public.sqlserver.clustering)
  • Re: error trying to start new maintance plan
    ... Thanks Geoff, but I have installed on both and now I am wondering if this is ... You have to run the installer on each cluster node ... The action you attempted to perform on a remote instance of SQL Server ...
    (microsoft.public.sqlserver.clustering)
  • Re: Proper procedure for adding a 3rd node to a SQL 2005/MSCS cluster
    ... With SQL 2000 you had to re-run the installer to change the cluster ... Enterprise Edition x64 and SQL Server 2005 Enterprise Edition x64. ...
    (microsoft.public.sqlserver.clustering)
  • Re: Unable to Apply SP4 to SQL 2000 Cluster (new Node)
    ... Now, for the first problem, adding the 3rd node as a member of the cluster. ... You then installed a 2nd instance of SQL Server. ... DBC01 (Disks, SQL Server resources) ... Install RTM SS2K and designate the node membership. ...
    (microsoft.public.sqlserver.clustering)