Moving a standalone database server to a windows 2008 clustered environment

  • Hi All,

    I'm new to clustering and I want to move a standalone database server to a windows server2008 cluster (which already have 3 database servers on it). Any input as to steps to take will be greatly appreciated.

    Thanks.:-)

  • build the clustered instance on your new hardware and migrate the databases across to the cluster from the stand alone machine

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • Thanks. I appreciate it.

    Moses.

  • Hi mashikoo,

    First and foremost, you cannot convert a stand alone instance into a cluster one.

    Here is my recommendation:

    1) Backup your databases and take SQL Server offline

    2) Make sure that you have configure your server(s) network teaming and disks arrays for clustering.

    3) Install Windows Cluster Service on the server(s)

    4) Build your Windows cluster.

    5) Uninstall your Standalone instance.

    6) Install a Single Node instance of SQL Server.

    7) Restore your databases.

    You can add as many nodes as needed when you purchase them. "Up to 16 nodes"

    Please keep in mind that this requires several hours of downtime and you should get approval from Change Management first.

    If you can't afford downtime, it's better if you install a separate instance instead.

    If you have more than one server for your cluster, you could install and setup clustering on the second server, install SQL, restore databases, then attached the existing node.

    QUIGROUP- Need a Certified experienced DBA for a project or troubleshooting? Need help with programming, database recovery, performance tuning, ETL, SSRS or developing new databases? Contact us.. 1-786-273-9809

  • Ysaias Portes-483038 (4/8/2011)


    You can add as many nodes as needed when you purchase them. "Up to 16 nodes"

    Assuming the OP has installed Enterprise edition or above and not Standard edition

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • Thanks Ysaias.

  • This would appear to be easier than the previous replies suggest since you have an existing database instance on a cluster.

    1. Are you able to/allowed to host the this database on the same instance?

    2. reverse engineer the logins required by the database using the sp_revlogins.

    3. Reverse engineer the logins server role membership.

    4. Establish existing job/application dependancies

    Reverse the process on the cluster by applying the logins and jobs. In terms of the database itself, my personal preference is to detach/copy/reattach as this prevents accidental usage and a relatively quick rollback procedure.

    There is nothing related to standalone databases that would prevent you doing this migration but you could encounter application issues.

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply