System Copy of a Non-Clustered SQL2005 to a clustered system

[Former Member]

Hi,

I have installed a Development system and also have a QA system.ECC6 SQL2005 windows AMD64(Opteron.

Now my production hardware has come its a cluster of 2 blade servers.I dont want to install SAP ECC6 again.So i am planning to use the DB of the development server and install the production server.

How do i go about this as my development was not on a cluster while my prodcution is going to be on a clustered system.I have done this kind of an intallation where in i have installed SAP only once and then created the production as a system copy in Oracle(saves time and effort as no need to apply SPs etc proper Client Copy & transports take care of data consistency.)I am looking for advise mostly in terms of how to cluster the SQL 2005 and then install SAP CI on both nodes for the cluster to work properly.

Regards

Ankan Majumdar

[Former Member · Accepted solution]

Hi Ankan,

What you can do Install SAP like system copy installation.

1. Install SQL software with cluster option.

2. Using detach Dev DB, copy and attach to production

3. Install CI

4. During Database installation choose system copy, it will automatically recognize existing DB.

5. execute Homogenoues system copy post processing.

6. Continue with MSCS conversion as normal cluster installation.

Regards,

Dedi Hermawan

Dedi Hermawan

[former_member192350]

You have to re-install to make the installation cluster-aware in an MSCS installation unfortunately. I clustered a customers production system by performing a fresh installation on new clustered hardware from the CD's, and once I verified that the packages were able to fail back and forth successfully, shut everything down and re-zoned the disks so their former production database LUNS were visible instead; this allowed us to do the cluster installation while production was up, and take a brief outage to shut down PRD, re-zone the disks to the new clustered hardware, and bring it back up in the cluster.

You should be able to do something similar, but instead of re-zoning, just copy your DEV database files over (while it's down, or do a backup/restore), then bring PRD back up afterward with the data from the DEV environment.

Unfortunately there are a couple of steps during the installation of the SQL Server software that you have to check to make it cluster-aware; I've heard recommendations from SQL Server DBAs to always install SQL Server with these options, even if you only intend to use a single node, because then down the road when/if plans change, the installation can be easily clustered without re-installing.

Rich

[andreurban_blumberg]

Do a full / normal install of the system on the production servers, in a MSCS clustered install.

Afterwards you can detach the Dev DB files and attach them to the Prod DB. Then do the normal homogeneous system copy post-processing steps.