Configure the Windows HPC Cluster for New Database Locations
Updated: July 2011
Applies To: Windows HPC Server 2008 R2
You can configure your Windows HPC Server 2008 R2 cluster to use a SQL Server instance or database that is different from the one that was configured during the installation of the head node. The SQL Server instance or database can be located on the head node computer or on a remote server running SQL Server. To make the configuration change, you must modify one or more registry settings on the head node of your cluster.
Important |
---|
Only modify these registry settings after you have restored the HPC databases in their new location. For information about scenarios where this step is needed, see Scenarios for Restoring a Windows HPC Server 2008 R2 Cluster. For example, if you have deployed your Windows HPC Server 2008 R2 cluster by using remote databases, and the remote database server fails, you might need to restore the databases on a new server. |
Caution |
---|
Incorrectly editing the registry may severely damage your system. Before making changes to the registry, you should back up any valued data on the computer. |
Registry settings for HPC databases in Windows HPC Server 2008 R2
The following two tables list the registry settings for the HPC databases in Windows HPC Server 2008 R2 and the default values in the case where the HPC databases are installed on the head node.
Note |
---|
Separate tables are provided for the settings in clusters running at least Windows HPC Server 2008 R2 with SP2 and the settings that are configured in the release-to-manufacture (RTM) version of Windows HPC Server 2008 R2 and Windows HPC Server 2008 R2 with SP1. |
Registry settings in Windows HPC Server 2008 R2 with SP2
Path | Key | Default value for installation on head node |
---|---|---|
HKLM\Software\Microsoft\HPC\Security |
DiagnosticsDbConnectionString |
Data Source=.\COMPUTECLUSTER;Initial Catalog=HPCDiagnostics;Integrated Security=True; |
HKLM\Software\Microsoft\HPC\Security |
ManagementConnectionString |
Data Source=.\COMPUTECLUSTER;Initial Catalog=HPCManagement;Integrated Security=True; |
HKLM\Software\Microsoft\HPC\Security |
ReportingDbConnectionString |
Data Source=.\COMPUTECLUSTER;Initial Catalog=HPCReporting;Integrated Security=True; |
HKLM\Software\Microsoft\HPC\Security |
SchedulerDbConnectionString |
Data Source=.\COMPUTECLUSTER;Initial Catalog=HPCScheduler;Integrated Security=True; |
HKLM\Software\Microsoft\HPC\ |
DiagnosticsDbServerName |
.\COMPUTECLUSTER |
HKLM\Software\Microsoft\HPC\ |
ManagementDbServerName |
.\COMPUTECLUSTER |
HKLM\Software\Microsoft\HPC\ |
ReportingDbServerName |
.\COMPUTECLUSTER |
HKLM\Software\Microsoft\HPC\ |
SchedulerDbServerName |
.\COMPUTECLUSTER |
Registry settings in Windows HPC Server 2008 R2 (RTM) and Windows HPC Server 2008 R2 with SP1
Path | Key | Default value for installation on head node |
---|---|---|
HKLM\Software\Microsoft\HPC |
DiagnosticsDbConnectionString |
Data Source=.\COMPUTECLUSTER;Initial Catalog=HPCDiagnostics;Integrated Security=True; |
HKLM\Software\Microsoft\HPC |
ManagementConnectionString |
Data Source=.\COMPUTECLUSTER;Initial Catalog=HPCManagement;Integrated Security=True; |
HKLM\Software\Microsoft\HPC |
ReportingDbConnectionString |
Data Source=.\COMPUTECLUSTER;Initial Catalog=HPCReporting;Integrated Security=True; |
HKLM\Software\Microsoft\HPC |
SchedulerDbConnectionString |
Data Source=.\COMPUTECLUSTER;Initial Catalog=HPCScheduler;Integrated Security=True; |
HKLM\Software\Microsoft\HPC\ |
DiagnosticsDbServerName |
.\COMPUTECLUSTER |
HKLM\Software\Microsoft\HPC\ |
ManagementDbServerName |
.\COMPUTECLUSTER |
HKLM\Software\Microsoft\HPC\ |
ReportingDbServerName |
.\COMPUTECLUSTER |
HKLM\Software\Microsoft\HPC\ |
SchedulerDbServerName |
.\COMPUTECLUSTER |
Configure the cluster to use a different HPC database
The following example shows how to configure a cluster running at least Windows HPC Server 2008 R2 to use the diagnostics database after it has been moved from its default instance on the head node (.\COMPUTECLUSTER) and renamed from its default name (HPCDiagnostics). You can follow similar steps to reconfigure HPC databases in Windows HPC Server 2008 R2withSP2 or other versions of Windows HPC Server 2008 R2 by using the registry settings in the preceding tables.
Important |
---|
Before you configure new registry settings for an HPC database, you should close all instance of HPC Cluster Manager and make sure that no cluster jobs are running or waiting to run. |
The following example describes how to configure a new location for the HPC diagnostics database and instance.
Example: To configure a new location for the HPC diagnostics database and instance
On the head node, open Registry Editor. To open Registry Editor, click Start, click Run, type regedit, and then click OK.)
In the console tree, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\HPC.
Click DiagnosticsDbServerName, and then on the Edit menu, click Modify.
Type the value of the new database instance in which the diagnostics database is stored, for example,
<ComputerName>\<NewInstanceName>
Then click OK.
In the console tree, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\HPC\Security.
Click DiagnosticsDbConnectionString, and then on the Edit menu, click Modify.
Type the value of the new database connection string, for example,
DataSource=<ComputerName>\<NewInstanceName>;Initial Catalog=<NewDatabaseName>;Integrated Security=True;
, and then click OK..Close Registry Editor.