How do I configure multiple Kaseya servers for testing or redundancy (resiliency) purposes?
Either you want to:
1. Configure a Kaseya server as a test bed to test upgrades to the Kaseya software or other software on the machine.
2. Configure a hotswap or standby Kaseya server or servers, so that in the event of the first server failing, you can fail over to a second server.
Kaseya currently does not support any resiliency on the Kaseya server running the web console and Kaseya Server service. It is recommended that you configure a standby or hotswap server as described in here in order to provide the maximum resiliency of the front end server. This means that you cannot cluster or network load balance (NLB) the Kaseya web console in any way.
The backend (SQL) server can be configured to use Microsoft clustering to take advantage of a resilient SQL solution using shared storage.
For Microsoft SQL Server 2005, please see the following Microsoft white paper: http://www.microsoft.com/downloads/details.aspx?FamilyID=818234dc-a17b-4f09-b282-c6830fead499&displaylang=en
For Microsoft SQL Server 2000, please see the following Microsoft white paper: http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/failclus.mspx
Important note: When you fail over the cluster, you must stop the Kaseya Server service prior on the front end Kaseya server prior to failing the cluster over, and start the service once the cluster has completely failed over and the SQL instance running the ksubscribers database is back online.
The Primary K Server and Secondary K Server details provided in the Agent tab > Configure Agents > Check-In Controlare not intended to provide any resiliency; in particular, attempting to have these addresses point to two different simultaneously running Kaseya Servers will cause issues. These addresses are only intended to provide two alternate addresses to a single Kaseya server - such as a DNS address and a single IP address, or an internal and external address.
The exception is where the addresses are configured to point to two different Kaseya servers as a part of a migration: as long as the servers are not running simultaneously, you should not experience any problems.
Microsoft SQL Server
Microsoft Windows 2003 Enterprise Edition