Skip to main content

K2 5.2, installed on premise

 

We currently have a Separate SQL server topology as described here.

 

We would like to use a Farm topology as described here to provide high availability in case one K2 server/node goes down.

 

Question - Is this simply a matter of installing the K2 software on another server and pointing it to the same SQL Server database? I  understand that the load balancer would route incoming requests between the two K2 servers but does K2 handle the multiple read/write connections to the same SQL server database or does that need any additional configuration?

 

Can someone please describe this in detail or point to some resource that does?

 

Thanks for your help

 

 

You have to do more than that. You are right in that your K2 servers will point to the same database on the SQL server. You should not  need to perform any additional configuration on your SQL server.


 


But on your K2 servers, you need to configure them such that they belong under the same farm. You can refer to the help document here for more information. If you already have an existing server that is not configured to be part of a farm, then you should only need to run the Setup Manager and perform the configuration.


 


Reply