We have a WMware host with a SQL2008R2 cluster.
Disks are raw mapped to a EVA 6400 SAN.
We have performance problems, we have located it to network problems.
To much packet los and there for resend, this is a hardware/ hardware driver issue.
We have issued it to the hardware vendor and they are aware about the problem and are looking in to it.
The vendor can't provide us with an estimated date for fixing it, there are critical systems on the cluster and we can't wait for
the fix to get ready, so we need another fix.
We have two new machines (physical) machines installed (atm windows only).
Now we need a method to migrate to the new machines.
As i se we have a couple of options.
1. Side by Side (system by system), takes much time but it's a failsafe method however it takes much time.
Pro: No need for roolbackplan, safe
Coins: Takes time
2. Install new servers, add them to the cluster, install SQL. Failover to the new nodes, shutdown the old machines.
This method sounds good, but has it ever been tested with the combination of physical and virtual machines?
Between physical only machines it should work.
Pro: Fast, minimum downtime, Roolback plan available.RollbackFeels risky, due to diskmappings. (Wmware on this lvl isn't board).
3. Install a new cluster, backup/ restore (deattach/ attach not an option since i dont want to change the enviroment due to roolback plan) from old cluster to new cluster.
Shutdown old cluster, rename new cluster and restart machines, and pray that the 30 systems will find the cluster.
Another thing is DNS, pray that windows will accept the new cluster with same name.
Pro: Prettyfast, accepted downtime.
Coins: A bit risky
Any other suggestions, or what would you do?
I allways like to go the safe way like method 1, but buissnes requirements might think other...
Sorry for any kind of bad english gramar and such...