Scaling for Data Availability

Since many business critical processes may be automated using K2 blackpearl, it may be important to have a redundant system for data availability. This scenario is the same as the Small Scale install, but with a SQL cluster as the database back-end rather than a single server.

Scaling for Data Availability Install
Server A	K2 blackpearl (all components)* Internet Information Server (IIS) SharePoint 2007, SharePoint 2010 (Server or Foundation)
Server B, C	SQL Server (Clustered)

Note: Depending on the SharePoint product installed, either the MOSS, WSS, SharePoint 2010 Server or SharePoint 2010 Foundation components will be displayed for installation.

The Scaling for Data Availability scenario is shown below. All of the IIS, K2, SQL Reporting Services, and SharePoint components are installed on one server, with a clustered SQL server instance for data redundancy.

Considerations for the Scaling for Data Availability Install

For this installation topology, the SQL Server configuration needs to be evaluated.

SQL Server

The SQL Server can share physical resources or be located on an independent platform, such as in this install, or it can be clustered. For more information regarding SQL Server clustering, refer to the SQL planning and architecture documentation (http://technet.microsoft.com/en-us/sqlserver/bb331768.aspx).

Considering that in most cases K2 is being introduced into an existing environment, the K2 Databases would be installed on an existing SQL Server cluster. It is important that the DTC component is configured properly in order for communications between the K2 Server and the SQL Server can function properly.

If SQL Server Reporting Services is installed on a separate server, then K2 Pass-Through Authentication (K2PTA) or Kerberos will need to be configured for communications between the K2 Server and Reporting Services.