Failover Clustering / High Availability on KSC - Onprem

[Tahmeed702]

Dear Community

We want to deploy Failover Clustering / High Availability on KSC from current deployment schema , We have 500 workstation in currently connected with KSC , Now we want to make Disaster Management of Kaspersky Security Center Server.

Please find below requirements ,
1. What is the process of deploying Failover Clustering / High Availability on KSC .
2. What is the requirement we have to follow for Failover Clustering
3. What will be the challenges or Troubleshooting steps we may have to facing during Failover Clustering deployments
4. What will be the Hardware and Software Sizing Guide .

Regards
Ahnaf Tahmeed

[JL - KL DACH]

Hello,

you will find all descriptions about failover cluster and sizing guide in the online help of KSC 15.1

Sizing Guide

About the Kaspersky Security Center failover cluster

[Danijel Jovanovic JAPICOM]

This part in documentation also

https://support.kaspersky.com/KSC/15.1/en-US/13055.htm

You need shared folder accessible from both KSC servers and database also.

 

For that number of endpoints i would rather go with 2 KSC servers in hierarchy, one master, other one secondary and configrue policy profiles to point endpoints to secondary if master is not reachable.

I played with failover cluster instalations, it works, it requires more work for deployment, its unnecessary unless its mandatory 🙂 

[Sang]

On 8/12/2025 at 4:05 PM, Danijel Jovanovic JAPICOM said:

This part in documentation also

https://support.kaspersky.com/KSC/15.1/en-US/13055.htm

You need shared folder accessible from both KSC servers and database also.

 

For that number of endpoints i would rather go with 2 KSC servers in hierarchy, one master, other one secondary and configrue policy profiles to point endpoints to secondary if master is not reachable.

I played with failover cluster instalations, it works, it requires more work for deployment, its unnecessary unless its mandatory 🙂 

Hi, the idea of creating two separated KESs and point agents to the second one is really great, i would like if there's actually documents about that scenario. Is that out of office configuration from network agent profile ?

[Danijel Jovanovic JAPICOM]

5 minutes ago, Sang said:

Hi, the idea of creating two separated KESs and point agents to the second one is really great, i would like if there's actually documents about that scenario. Is that out of office configuration from network agent profile ?

You first go one step back from there and in the lower part add profile. That profile should point to other KSC server or connection gateway network agent.

After that you go there in network location, select your new profile and configure conditions when to use that profile.

You have in documentation about that, just search for conection profiles.

Thats not out of office policy, that is something else. Out of office policy is activated when network agent cant reach KSC server 3 times.