![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I'm moving our production DB from a stand alone install to an active/passive cluster. Current system is running Windows 2008 and SQL 2008 SP1, the cluster will run Windows 2008 R2. The machine that is actively running the database now will become the second node in the cluster when it's all said and done. I think have two options and am looking for any advice or other ideas. Option 1: Setup a single node cluster and restore the system databases. When ready to migrate, stop SQL on the existing server and change the LUNs over to the new server. Attach the databases and things should be ready to go. Then ugrade the old server and bring it in as the second node. Option 2: Setup a single node cluster using newly provisioned LUNs that match the current production setup. Backup system and user databases from the current server and restore them onto the cluster. Then ugrade the old server and bring it in as the second node. Option 1 seems much easier, Option 2 seems safer but more work. I have a lab where I've been testing this stuff, but curious what others think. |
![]() |
| Thread Tools | |
| Display Modes | |
| |