locked
Moving Database from Physical Cluster into Virtual Cluster RRS feed

  • Question

  • Hello All...........I have a Physical SQL Cluster 1 cluster1.domain.com (Node A and Node B) using SAN A.  Physical SQL Cluster contains three-3 instances.  One of the instance is for SCCM that holds its databases.

    I have built a Hyper-V Failover Cluster and upon it I have also built a Guest/Virtual SQL Cluster 2 cluster2.domain.com (Node A and Node B) using SAN B.

    Now, I want to move the instance/databases from Physical SQL Cluster 1 cluster1.domain.com to Guest/Virtual SQL Cluster 2 cluster2.domain.com.  Is this supported?

    Or do I have to add the Virtual Nodes (NodeC and NodeD) to cluster1.domain.com and then failover the instances/database to new virtual nodes and then remove the Physical Nodes (NodeA and NodeB).

    Also, confused as to how would I manage the Storage as old Physical SQL Cluster cluster1.domain.com uses SAN A and I have new Virtual SQL Cluster cluster2.domain.com on SAN B.  Would I be requiring to change the instances/databases location as well?

    Any help on this would be appreciated.   

    Thursday, December 4, 2014 7:53 PM

Answers

  • The process for moving a ConfigMgr database is well documented and completely agnostic of the cluster of physical configuration as long as the SQL instance is valid and accessible: http://technet.microsoft.com/en-us/library/hh427336.aspx#BKMK_ModifyDatabaseConfig

    Joining the nodes to an existing cluster and then breaking them off to form their own cluster is probably not supported from a SQL Server perspective. Most of questions are SQL Server clustering specific and probably should be addressed in a SQL Server forum; however, the process for moving a DB is pretty simple and documented above assuming you have a valid source and valid destination SQL Server instance -- all of your other questions are SQL Server implementation details but ultimately have nothing to do with moving the DB itself.


    Jason | http://blog.configmgrftw.com | @jasonsandys

    • Proposed as answer by TorstenMMVP Tuesday, December 9, 2014 7:11 AM
    • Marked as answer by Joyce L Thursday, December 11, 2014 10:35 AM
    Friday, December 5, 2014 2:03 PM

All replies

  • Hello All...........I have a Physical SQL Cluster 1 cluster1.domain.com (Node A and Node B) using SAN A.  Physical SQL Cluster contains three-3 instances.  One of the instance is for ADRMS that holds its databases.

    I have built a Hyper-V Failover Cluster and upon it I have also built a Guest/Virtual SQL Cluster 2 cluster2.domain.com (Node A and Node B) using SAN B.

    Now, I want to move the instance/databases from Physical SQL Cluster 1 cluster1.domain.com to Guest/Virtual SQL Cluster 2 cluster2.domain.com.  Is this supported?

    Or do I have to add the Virtual Nodes (NodeC and NodeD) to cluster1.domain.com and then failover the instances/database to new virtual nodes and then remove the Physical Nodes (NodeA and NodeB).

    Also, confused as to how would I manage the Storage as old Physical SQL Cluster cluster1.domain.com uses SAN A and I have new Virtual SQL Cluster cluster2.domain.com on SAN B.  Would I be requiring to change the instances/databases location as well?

    Any help on this would be appreciated.   

    • Merged by Vivian_Wang Thursday, December 11, 2014 6:41 AM duplicate
    Thursday, December 4, 2014 7:59 PM
  • Any comments ladies and gentlemen.
    Friday, December 5, 2014 7:13 AM
  • Any comments ladies and gentlemen.
    Friday, December 5, 2014 7:13 AM
  • The process for moving a ConfigMgr database is well documented and completely agnostic of the cluster of physical configuration as long as the SQL instance is valid and accessible: http://technet.microsoft.com/en-us/library/hh427336.aspx#BKMK_ModifyDatabaseConfig

    Joining the nodes to an existing cluster and then breaking them off to form their own cluster is probably not supported from a SQL Server perspective. Most of questions are SQL Server clustering specific and probably should be addressed in a SQL Server forum; however, the process for moving a DB is pretty simple and documented above assuming you have a valid source and valid destination SQL Server instance -- all of your other questions are SQL Server implementation details but ultimately have nothing to do with moving the DB itself.


    Jason | http://blog.configmgrftw.com | @jasonsandys

    • Proposed as answer by TorstenMMVP Tuesday, December 9, 2014 7:11 AM
    • Marked as answer by Joyce L Thursday, December 11, 2014 10:35 AM
    Friday, December 5, 2014 2:03 PM
  • Thanks for the reply.

    I am just not sure what would be required on the target SQL Server for restoration of Database? Same instance name or does backup already has that?

    Friday, December 5, 2014 8:03 PM
  • Instance Names are irrelevant to the SCCM restore. Whether they are relevant to your SQL cluster is beyond the scope of this forum.
    Saturday, December 6, 2014 1:19 AM
  • When you perform the recovery in ConfigMgr, you will/can set that so no, the same instance name is not required.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Saturday, December 6, 2014 3:11 AM
  • Thanks for the reply.

    Can I have a checklist of things that are required at the target SQL in case a Database is coming from another Cluster with named instance and service accounts?

    Saturday, December 6, 2014 5:29 AM
  • There's nothing special required beyond the normal per-requsities. Please read the documentation I linked above.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Sunday, December 7, 2014 12:11 AM
  • Thanks for the reply; appreciate it.
    Tuesday, December 9, 2014 5:28 AM