Best practices for server configuration - Consider the following best practices when configuring your servers for a Security Center deployment. - Security Center 5.11 - 5.13

Security Center Best Practices - Enterprise

Product
Security Center
Content type
Best practices
Version
5.13
5.12
5.11
ft:locale
en-US
Last updated
2025-01-30

Consider the following best practices when configuring your servers for a Security Center deployment.

  • To ensure that your servers do not get overloaded, follow the server requirements.
    CAUTION:
    Before activating KiwiVision™ Security video analytics, make sure that your system can handle the additional load. Running video analytics with insufficient resources can negatively impact performance or can cause system failure. For more information, see the System requirements for KiwiVision™ in Security Center 5.11.
  • Configure a separate archive database for each server assigned to an Archiver role or Auxiliary Archiver role. Because of this requirement, it is a best practice to host the archive database locally on each server. When two or more archiving roles are hosted on the same server, you must assign a different database to each role instead of using the default one.
  • Make sure that each Archiver role uses a separate logical disk for archive storage.
  • Secure servers that are exposed to the internet. If necessary, isolate the servers on a separate network.
    Example: If the server hosting the Mobile Server role is exposed to the internet, you can put that server on a separate DMZ network.