The Kaseya platform is flexible and scalable and will continue to operate reliably under severe loading conditions. Consider matching your anticipated needs to one of the recommended configurations below. Due to customer requests, configurations above 1000 end points are provided both as a single server and split server configuration. Please note that a split server configuration is not as economical as a single server installation.
Base Configuration
The server configurations below are optimized for maximum performance assuming intensive use of the Kaseya platform in terms of:
Deep use of Monitoring for all managed machines
Deep use of SNMP Monitoring
Frequent Audits for all managed machines
Full use of Patch Management for all managed machines
Extensive use of Agent procedures for all managed machines
All Managed machines are located on remote networks accessible only via the Internet
Add-ons
The Service Desk add-on will require an additional 2.4 Ghz core per 50 concurrent Service Desk users on single server installations on top of the base Kaseya configuration.
KES will incur an additional %15 load on CPU and IO to the base configuration.
On site replication in Backup will cause heavy traffic between the client and the server and extra DB processing when using Full Synthetic Backups.
Virtualization
Kaseya supports virtual machines running under ESX 4.x and 5.x Hypervisors, however, these VMs need to be configured properly with sufficient dedicated CPU and Memory resources. Performance and functionality will be impacted adversely by other VMs on the ESX host when these resources are limited. Kaseya provides a section for each configuration below on minimum CPU and Memory Reservations. Please note, the VM must still be configured with the Suggested Configurations for physical servers.
Microsoft Hyper-V can be used for the application and database server, however, the same resource requirements must be observed in terms of the CPU, IOPS and Memory as VMWare. Hyper-V 2008 and 2008 R2 was limited to 4 processors on the virtual Machine so some of the configurations below may not apply in larger implementations.
Kaseya should be upgraded on a cloned VM, rather than upgrading on a snapshot on the same VM.
Depending upon actual usage, the hardware and software required may be more or less than the configurations specified below.
As a best practice, administrators are encouraged to monitor standard performance metrics on the Kaseya Server (CPU, memory, etc.) and SQL Server to establish the appropriate level of hardware and software based on actual usage.
