Re: New Hardware, moving

I have done that exact same migration. Shift all resources to one node
(arbitrarily called NodeA). Upgrade the OS for the other node (NodeB)
in-place. If it detonates, kick it out, rebuild it, and add it back. You
can have mixed OS platforms in a cluster for a short time. Shift all
resources to NodeB and repeat the upgrade. Then you can add the new nodes
to the cluster and eventually kick out the old ones. You will be running on
an in-place upgrade OS for a short time, but when all is completed, you will
be on Windows 2003 hosts loaded from scratch.


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





"CD" <mcdye1@xxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:%23HXIZx0rGHA.4844@xxxxxxxxxxxxxxxxxxxxxxx
Thanks for the reply, But we are moving from a 2000 cluster to a 2003.

"Geoff N. Hiten" <SQLCraftsman@xxxxxxxxx> wrote in message
news:ePQb5frrGHA.1140@xxxxxxxxxxxxxxxxxxxxxxx
This is actually pretty easy.

SQL 2000 and Windows 2003 support up to four node clusters. Simply add
the new nodes and after you have checked that they are working, remove
the old ones. There are a lot of details to cover during the process,
but that is the basic outline.

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





"CD" <mcdye1@xxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:uc5LompqGHA.1796@xxxxxxxxxxxxxxxxxxxxxxx
We currently have a 2 node active/passive cluster
(Win2000sp4SQL2000sp3). We have several drives configured with multiple
databases on the different drives. The SQL drives are on a SAN.



We want to move the SQL virtual instance to new 2 node hardware with
Windows 2003 freshly installed. We need to take the virtual name with
the move so not to interrupt the client side until the clients are
upgraded.





So the how to lost is



1) How to move and keep the same virtual name?

2) How to keep the old system up but with different name?

3) I have done moves before by setting the server up the same and
stopping SQL and copying system and user databases to the new server
don't know if something similar could be done. The virtual name makes
me leery of type of move.

4) Is it possible to use DNS for the old virtual name and point to
the sql virtual name?

5) We have the option to go as far as brake the two nodes now to
single servers, then we would need to rename server to the virtual
names.



Trying to find options

TIA








.

Relevant Pages

  • RE: MSDE to SQL Server
    ... I understand that you want to upgrade MSDE instances ... We can upgrade the instance SHAREPOINT to SQL and it is not recommended ... Business Server 2003 ...
    (microsoft.public.windows.server.sbs)
  • Problem upgrading named instance in SQL 2000
    ... I have installed SQL 2000 Server on my machine with Default Instance ... After selecting the Database Engine ... Reason: Your upgrade is blocked. ...
    (microsoft.public.sqlserver.clients)
  • Re: MSSQL on XP-Pro
    ... These old versions of SQL Server should run on XP. ... There are two ways to upgrade. ... upgrade when you run the 7.0 install. ...
    (microsoft.public.sqlserver.setup)
  • Re: upgrading from SQL 7.0 to SQL2000
    ... I like the idea of doing a fresh install of SQL> 2000. ... > 2) install SQL 7.0 on a separate machine which is a test server. ... > 3) Restore the databases from my production server on to my test server> running SQL 7.0. ... While the upgrade should work just fine I like to start>> fresh if possible. ...
    (microsoft.public.sqlserver.setup)
  • Re: Get serverinstance name(s) using Physical node name
    ... Senior Database Administrator ... Microsoft SQL Server MVP ...
    (microsoft.public.sqlserver.clustering)
Loading