Hello all,
I am planning to try to move some SQL2005 and SQL2008 from a 2nodes (VMs) to another 2nodes (physical).
A. What I plan to do is :
1. add physical machines as 3rd and 4th node of Windows cluster and form a 4node Windows cluster
2. stop all scheduled user created jobs (backups etc.)
3. for each instance existing, run on 1st physical machine (3rd node) the "add node" for all existing SQL2005 and SQL2008 failover clustered instances (FCIs) and Service Packs
4. for each instance existing, run on 2nd physical machine (4th node) the "add node" for all existing SQL2005 and SQL2008 failover clustered instances (FCIs) and Service Packs
5. one-by-one, faiolover the instances from VMs to physical nodes and do all the ckecks for the health of the system. If ok run backups and continue failover the next one. If there is anything wrong failback check and retry.
6. Run backups, enable jobs
the tricky part is that the systems is a live system.
we plan to do the installations during non-maintenance window an do the failover inside maintenance window.
Is there anything causing the SQL Server to actually failover DURING sql setup of "add node"? (e.g.: cluster validation before addign to cluster)?
B. We have all kind if services to be installed, includingn SSAS, SSIS, SSRS and thye already exist in VMs in one resource group per instance. I guess that during each "add node" run per instance they are all going to be installed at once for this instance, right?
C. anything special we should be aware of?
thank you very much!
kind regards, Thomas G. Apostolou
