Re: Physical move of clustered SQLServer

If you are fully re-locating the kit, and the IP addressing stays the same,
there should be nothing more to do on the cluster itself.

However;
- there is no alternative for a good backup and restore, ensure you have a
good back of your databases and cluster (and know how to restore in case of
a disaster, have your restore procedures ready)
- ensure that you know how to powerdown and powerup your miniSAN. Many
storage equipment have specific sequences in powering up and powering down.

Then for moving the kit, consider the following:
- set the cluster service to manual on both nodes, this to ensure the
cluster is not trying to start when relocated
- once relocated and booting your nodes, ensure that you have base
connectivity, IP's and all networking (including heartbeat) is working. All
software/networking, except cluster and clustered applications, must be
working at this point.
- set the cluster service to Automatic on Node 1 and start the cluster
service (only) on Node 1
- check your application / data, all should come online, all should be
functional
- when you are happy that all is working on Node1, set cluster service to
automatic on Node 2 and start cluster service on Node 2
- test moving all groups from/to all nodes, to ensure your cluster is
functional
- when your cluster is functional, all OK, then test client connectivity to
your databases

If you take a planned approach like the above steps, you can troubleshoot if
anything goes wrong after each step.
Plan your move in detail, make a checklist of steps, and execute step by
step, testing that each step is sucsesful before moving on to the next.

HTH,
_Edwin.


"adb2303" <atrc76@xxxxxxxxxxxxx> wrote in message
news:1166609860.391666.300310@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hello,

All of our Intranet servers are physically moving from one datacentre
to another. We have already catered for the front-ends, but I need to
find out what needs doing to our clustered SQL Server 2000 environment.

We have a 2 node Win2k cluster, with SQL Server 2000 Enterprise
Edition. The database files are stored on a miniSAN. We're physically
picking up the kit, and moving it to another datacentre.

I need to know what considerations need to be made to bring the cluster
back-up, database intact, once it's in the new datacentre.

Any suggestions/recommendations are gratefully received.

Andrew



.

Relevant Pages

  • Re: How to change directory
    ... Moving the databases is very easy. ... Exchange server in order to get the binaries on another drive. ... I would recommend that you instead consider moving to an A/P cluster. ...
    (microsoft.public.exchange2000.admin)
  • Re: moving to a new server
    ... > the box an upgrading it or are you moving the entire installation? ... > a stand-alone server or a SQL Server Fail Over cluster? ... Can someone point me to a white paper for ...
    (microsoft.public.sqlserver.server)
  • Re: How to migrate Windows NT4 cluster to Windows Server 2003 cluster?
    ... One thing to watch is "file share" premissions since you are moving to a new ... > I have question about migration method from Windows NT4 cluster to Windows ... We have a service window on 24 hours to do this. ...
    (microsoft.public.windows.server.clustering)
  • Re: Move cluster to new HW and new domain
    ... I would break the excersise into two parts, each a seperate action, which ... need to be completed before moving on to the next task. ... move the cluster into the new domain ... We want to migrate our 2 node File and Print cluster from a W2K3 domain to ...
    (microsoft.public.windows.server.clustering)
  • Re: Real Problems nobody talks about
    ... >>> velocity away from a common center, ... >> If they were not moving, the cluster would collapse. ... They are not crashing into each other, ...
    (sci.physics.relativity)
Loading