![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I have a customer that currently has Windows 32 bit OS, running a SQL 2005 32 bit cluster. They want to install Windows 64 bit OS and a new SQL 2005 32 bit cluster. Are there any procedures out there, on how the SQL data will be migrated from one to the other? |
#3
| |||
| |||
|
|
That is pretty much a nuke and pave operation. You can evict a node, reformat it, then build the new cluster around that hardware, but that is tricky. The data is fairly simple since the on-disk formats do not vary. You can detach from one cluster, switch zoning, import the disks to the new cluster, define resources arounbd them and apply to the new SQL instance. Unfortunately I don't have any good public resources on that. I have done it before for a client, but I used Windows 2008 along with a mix of old and new hardware since they wanted to expand the cluster anyway. However you do this, careful planning is the key. I am probably biased towards the consultant business model, but this is a place where you might find it worthwhile to hire somebody who has experience in cluster migrations. -- Geoff N. Hiten Principal SQL Infrastructure Consultant Microsoft SQL Server MVP "eternoamar" <angeltides (AT) hotmail (DOT) com> wrote in message news:F028EFCF-A64A-4F60-BFBB-75D70B947066 (AT) microsoft (DOT) com... I have a customer that currently has Windows 32 bit OS, running a SQL 2005 32 bit cluster. They want to install Windows 64 bit OS and a new SQL 2005 32 bit cluster. Are there any procedures out there, on how the SQL data will be migrated from one to the other? |
#4
| |||
| |||
|
|
Thanks for replying Geoff! I actually failed to mention that they will be doing this on new hardware. So with the old OS and SQL still intact, we will build a new Windows OS 64 bit, and build a new SQL 2005 32 bit cluster. So being that we are using completely new hardware, is it just a matter of detaching the database from old cluster, and re-attaching to the new cluster? Would I be able to refer to documents that talk about moving SQL database for this scenario? SQL 2005 32 bit can run on Windows 64 bit OS ok? Thanks! "Geoff N. Hiten" wrote: That is pretty much a nuke and pave operation. You can evict a node, reformat it, then build the new cluster around that hardware, but that is tricky. The data is fairly simple since the on-disk formats do not vary. You can detach from one cluster, switch zoning, import the disks to the new cluster, define resources arounbd them and apply to the new SQL instance. Unfortunately I don't have any good public resources on that. I have done it before for a client, but I used Windows 2008 along with a mix of old and new hardware since they wanted to expand the cluster anyway. However you do this, careful planning is the key. I am probably biased towards the consultant business model, but this is a place where you might find it worthwhile to hire somebody who has experience in cluster migrations. -- Geoff N. Hiten Principal SQL Infrastructure Consultant Microsoft SQL Server MVP "eternoamar" <angeltides (AT) hotmail (DOT) com> wrote in message news:F028EFCF-A64A-4F60-BFBB-75D70B947066 (AT) microsoft (DOT) com... I have a customer that currently has Windows 32 bit OS, running a SQL 2005 32 bit cluster. They want to install Windows 64 bit OS and a new SQL 2005 32 bit cluster. Are there any procedures out there, on how the SQL data will be migrated from one to the other? |
#5
| |||
| |||
|
|
Thanks for replying Geoff! I actually failed to mention that they will be doing this on new hardware. So with the old OS and SQL still intact, we will build a new Windows OS 64 bit, and build a new SQL 2005 32 bit cluster. So being that we are using completely new hardware, is it just a matter of detaching the database from old cluster, and re-attaching to the new cluster? Would I be able to refer to documents that talk about moving SQL database for this scenario? SQL 2005 32 bit can run on Windows 64 bit OS ok? Thanks! "Geoff N. Hiten" wrote: That is pretty much a nuke and pave operation. You can evict a node, reformat it, then build the new cluster around that hardware, but that is tricky. The data is fairly simple since the on-disk formats do not vary. You can detach from one cluster, switch zoning, import the disks to the new cluster, define resources arounbd them and apply to the new SQL instance. Unfortunately I don't have any good public resources on that. I have done it before for a client, but I used Windows 2008 along with a mix of old and new hardware since they wanted to expand the cluster anyway. However you do this, careful planning is the key. I am probably biased towards the consultant business model, but this is a place where you might find it worthwhile to hire somebody who has experience in cluster migrations. -- Geoff N. Hiten Principal SQL Infrastructure Consultant Microsoft SQL Server MVP "eternoamar" <angeltides (AT) hotmail (DOT) com> wrote in message news:F028EFCF-A64A-4F60-BFBB-75D70B947066 (AT) microsoft (DOT) com... I have a customer that currently has Windows 32 bit OS, running a SQL 2005 32 bit cluster. They want to install Windows 64 bit OS and a new SQL 2005 32 bit cluster. Are there any procedures out there, on how the SQL data will be migrated from one to the other? |
![]() |
| Thread Tools | |
| Display Modes | |
| |