Scaling for Data and Performance
Both the Scaling for Page Rendering and Scaling for Data Availability scenarios start to address redundancy into the system. This scenario addresses both the data availability, by adding a SQL cluster into the infrastructure, as well as failover via load balancing on the other components.
| Scaling for Data and Performance | |
|---|---|
| Server A, B | NLB SharePoint 2007, SharePoint 2010 (Server or Foundation) and IIS NLB K2 blackpearl (all components) |
| Server C, D | Clustered SQL Server |
 |
Depending on the SharePoint product installed, either the MOSS, WSS, SharePoint 2010 Server or SharePoint 2010 Foundation components will be displayed for installation. |
In the figure below, the Scaling for Data and Performance scenario is shown. There is a SQL cluster, and all IIS, SharePoint, SQL Reporting Services, and K2 components are on an NLB cluster.
Considerations for the Scaling for Data and Performance Install
This scenario introduces a NLB cluster into the installation topology; therefore, it is important to understand NLB before installing this scenario.
Network Load Balancing
NLB can be configured by using either the operating system or specific hardware. In either case, NLB configuration should be completed before installing K2 blackpearl.
When installing components that will be load balanced, the installation must be performed on each machine independently. In this install, all of the components are on NLB servers; therefore, all of the components need to be installed on each NLB server.
SQL Server
The location of the SQL Server is not critical for a K2 installation, as long as the network connection speed to the K2 Server meets minimum requirements. It is also important that the DTC component is configured properly in order for communications between the K2 Server and the SQL Server can function properly. The SQL Server can share physical resources, be located on an independent platform, such as in this install, or it also can be clustered. For more information regarding SQL Server clustering, refer to the SQL Server Failover Clustering documentation (http://msdn.microsoft.com/en-us/library/ms189134.aspx)
In most cases K2 databases are installed on an established SQL Server cluster for an existing environment. This is a common occurrence and the installation documentation takes this into consideration.
