Share via


How to install or move the Configuration Manager 2007 site database to a clustered Microsoft SQL Server instance

The System Center Configuration Manager 2007 site database can be installed or moved to a clustered virtual Microsoft SQL Server instance that contains several nodes and this blog post will show the steps and screenshots to clarify how we can achieve this.

Installing the Configuration Manager 2007 database on a clustered virtual Microsoft SQL Server instance

The Configuration Manager 2007 site database can be installed on a clustered virtual Microsoft SQL Server instance by following steps:

1. Create the virtual SQL Server cluster to host the site database on an existing Windows Server cluster environment.  We suggest that you to enable Kerberos and register the SPN for the clustered SQL Server since failure to do so can cause SQL backup issues. 

See the following link for more information: https://social.technet.microsoft.com/forums/en-US/configmgrbackup/thread/de3d7be3-7d1f-47d6-90bc-fe25b1a19321/.

To configure these, please refer the online document on https://msdn.microsoft.com/en-us/library/ms191153.aspx.

2. Add the machine account of the primary site server machine to the Local Administrators group of each Windows Server cluster node computer. This is required to allow the site server to install and configure settings later.

3. In the virtual SQL Server instance, assign the sysadmin SQL Server role to the user account running Configuration Manager Setup.

4. Start Configuration Manager Setup and select to install Configuration Manager using custom settings.

5. On the Configuration Manager Database Server page of the Configuration Manager Setup Wizard, enter the name of the clustered virtual SQL Server instance to host the site database and the name for the site database to be created on that instance by setup.

After the installation, the site system list will show all the SQL Cluster nodes with the database role on them.  In the screen shot below the two SQL Cluster nodes are 2K3SQL1 & 2K3SQL2:

ref: https://technet.microsoft.com/en-us/library/bb680513.aspx

Moving the Configuration Manager 2007 site database to a clustered virtual Microsoft SQL Server instance

The Configuration Manager 2007 site database can be moved to a clustered virtual Microsoft SQL Server instance by following the steps below(and please remember the SQL Collation to move SCCM DataBase.):

1. Back up the site database on the current site database server and restore it on the clustered virtual Microsoft SQL Server instance using the SQL Server Management Studio.  We suggest that you enable Kerberos and register the SPN for the clustered SQL Server to avoid potential SQL backup issues.

2. Ensure the primary site server computer account has administrative privileges over each SQL cluster node computer.

3. Close any open Configuration Manager console connections to the site server.

4. On the primary site server computer, use the hierarchy maintenance tool (Preinst.exe) to stop all site services with the following command:

Preinst /stopsite

5. On the primary site server computer, click Start, click All Programs, click Microsoft System Center, click Configuration Manager 2007, and click ConfigMgr Setup.  Alternatively you can navigate to the .\bin\i386 directory of the Configuration Manager 2007 installation media and double-click Setup.exe.

6. Click Next on the Configuration Manager Setup Wizard Welcome page.

7. Click Perform site maintenance or reset this site on the Configuration Manager Setup Wizard Setup Options page.

8. Select Modify SQL Server configuration on the Configuration Manager Setup Wizard Site Maintenance page.

9. Enter the name of the clustered virtual SQL Server instance to host the site database for the new site database server as well as the site database name on the Configuration Manager Setup Wizard SQL Server Configuration page.

10. Configuration Manager Setup performs the SQL Server configuration process.

11. Restart the primary site server computer and verify the site is functioning normally.

After the process is done, the site system list should show the clustered virtual Microsoft SQL Server temporarily with the database role.  In the screenshot below, the virtual SQL Cluster server is SQL2K8CLUSTERNA and the old database server is SQLCLUSTER-DC.

Just wait few minutes and refresh the Site System list.  After a few moments all of the SQL Cluster nodes should be displayed in the site system list with the  database role, and the clustered virtual Microsoft SQL Server will have no longer with the database role.  In the screen shot below, the SQL Cluster nodes are SQL2K8NMND2 & SQL2K8SP2N, and the SQL Cluster virtual server is SQL2K8CLUSTERNA:

ref: https://technet.microsoft.com/en-us/library/bb680707.aspx

 

Thanks,

Fei