Breaking a Sql Cluster

We have an Active/Active/Passive SQL 2000 cluster and budgetary constraints
have made it impossible for us to upgrade the hardware to new servers. Our
current servers are capable of handling the upgrade but some of our databases
might not be compatible with SQL 2005. Can we evict the passive node, make
it a standalone, upgrade it and then migrate the databases to the new server
without killing the cluster? Will the cluster run if the passive node is
evicted?
.

Relevant Pages

  • Re: Installing DHCP & Print Server on a Win2K3 Enterprise server cluster
    ... I am back here after the upgrade (not successful. ... Introduced the new Win2K3 cluster tried ... additional servers if I have to implement two DHCP servers with two ... High availability is so much more than that. ...
    (microsoft.public.windows.server.clustering)
  • Re: upgrading sql2k cluster to sql2005
    ... Doesn't matter if it is a new instance on the same cluster or an entirely ... install this into either a new cluster or a new instance of SQL Server, ... for connections, linked servers, and remote servers hasn't been screwed up ... the side-by-side upgrade, you could still be running into issues. ...
    (microsoft.public.sqlserver.clustering)
  • Re: Share offline
    ... Thanks Mike. ... as there some times is not an upgrade path. ... With servers I never like doing ... through explorer and then created my cluster share. ...
    (microsoft.public.windows.server.clustering)
  • VMS V7.2 upgrade - TCPIP and PWRK
    ... Well it is hard to believe but we are getting closer to actually upgrading our servers from V7.2 to V7.3-2. ... we are bringing another server online into our existing V7.2 cluster. ... My understanding is that we need to upgrade A/S. ...
    (comp.os.vms)
  • Re: Windows 2003 Network Load Balancing Problem
    ... Sadly my servers websites were configured with specific IPs and host ... I find it very strange why the NLB driver can receive on a virtual IP ... he set his IIS website to use ALL UNASSIGNED addresses rather than ... specifically pointing it at the single virtual cluster address. ...
    (microsoft.public.windows.server.clustering)