After the remote database servers are prepared, you can start the installation process of the Beta 1 release of HPC Pack 2008 R2.
|To install HPC Pack 2008 R2 Beta 1 with remote databases|
Connect the head node computer to the HPC networks, according to the topology that you chose for your HPC cluster. For more information, see Step 1: Prepare for Your Deployment, in the Windows HPC Server 2008 Design and Deployment Guide (http://go.microsoft.com/fwlink/?LinkID=151466).
If you haven’t already, install on the head node computer Windows Server 2008 R2 HPC Edition or another 64-bit edition of Windows HPC Server 2008 R2. You can download an evaluation version of Windows Server 2008 R2 HPC Edition when you download HPC Pack 2008 R2 Beta 1 from the Microsoft Connect Web site. For more information, see Joining the Windows HPC Server 2008 R2 Beta (http://go.microsoft.com/fwlink/?LinkId=169523).
To start the Microsoft HPC Pack 2008 R2 Installation Wizard on the head node computer, run
setup.exefrom the installation media for the Beta 1 release of HPC Pack 2008 R2 or from a network location.
On the Getting Started page, click Next.
On the Microsoft Software License Terms page, read or print the software license terms in the license agreement, and accept or reject the terms of that agreement. If you accept the terms, click Next.
On the Select Installation Type page, click Create a new HPC cluster by creating a head node, and then click Next.
On the Select Installation Location for HPC Databases page, click the Remote Server column for each database that you want to install on the remote servers, and then click Next.
On the Specify SQL Connection String for Remote HPC Database page, to specify the SQL connection string for the remote database, type or modify the suggested SQL connection string according to the following syntax:
- For Windows authentication:
Data Source=<computer_name>\<instance_name>;Initial Catalog=<database_name>;Integrated Security=True
- For SQL Server authentication:
Data Source=<computer_name>\<instance_name>;Initial Catalog=<database_name>;User ID=<user_name>;Password=<password>
<computer_name>is the name of the remote database server where you want to install the HPC database.
<instance_name>is the name of the instance of SQL Server 2008 that you configured for the HPC database.
<database_name>is the name of the database that you created in the instance.
<user_name>, when using SQL Server authentication, is the login name of the user that you want to use to connect to the HPC database
<password>, when using SQL Server authentication, is the password for the user
- For Windows authentication:
To test the SQL connection string and go to the next step, click Next.
If an error message appears that states the remote database could not be accessed, review the SQL connection string that you specified and try again. If you continue to see the error message, security might not be properly configured for the database, or the Windows Firewall on the remote database server might not be permitting the head node computer to connect. Review Step 1: Prepare the Remote Database Servers, and ensure that the remote database server meets the requirements listed there.
Repeat the two previous steps for all HPC databases that you selected to install on a remote database server.
Continue to follow the steps in the installation wizard.
If an error message appears during the final installation process that states an HPC service could not be started, it might indicate a connection problem between the head node computer and the remote database server where you installed the HPC database for that service. For example, if the error message is for the HPC Management Service, the HPC database affected is the cluster management database. Select to retry the installation because it might be only a transient issue. If the installation succeeds, continue to monitor for issues in the future, and consider the possibility of having to change the remote database server where you store the HPC database. If the installation fails again, try troubleshooting the connection between the head node computer and the remote database server, or try installing the HPC database on a different server.