Follow

What hardware is required to install Vitrium Security?

(Available for Enterprise Edition only)

Front-End Application Servers

Software Requirements

The Vitrium Security software requires the following software components to run.  Unless otherwise specified, the components must be installed on the front-end machine prior to running the Vitrium Security Server installer.

  • Microsoft® Windows Server 2008 R2, Windows Server 2012, or higher recommended
  • Microsoft® IIS 7.5 or higher
  • Microsoft® .NET Framework 4.5.1. and later
  • Microsoft® ASP.MVC 4

Hardware Requirements

The machine should have the following minimum requirements.

  • GHz dual-core (or multi core) processor
  • 8 GB RAM
  • 100 GB hard disk for file storage

Note that the document conversion performance is CPU-bounded, and also depends on network speed to upload/download the content to/from the server.

Storage Requirements

Disk space on the front-end machine is dictated by the size of the content to be processed and stored. The Vitrium Security Server will effectively need 2-4x the amount of space for each document. You should plan disk-space for the front-end machine based on the total volume of protected documents.

Vitrium recommends using a SAN or NAS or network share for storing the raw and/or protected content and Webviewer converted files in anything but large volume environments.

 

Back-End Database Server(s)

Software Requirements

The following must be installed on the back-end machine prior to running the Vitrium Security installer.

  • Microsoft® Windows Server 2008 R2, Windows Server 2012, or higher recommended
  • Microsoft® SQL Server 2008 or higher

 

Load Balancing

The Vitrium Security software is designed to be load balanced for scalability, redundancy and ease of maintenance.  Session state is persisted all the way to the database so any of the front-end servers can randomly serve requests and perform the security handshake.  To set this up, install as many front-end application servers with the same configuration.  All of these servers should point to the same SAN or NAS or network share for the content repository and to the same back-end database server.  And, the back-end database server can leverage Microsoft SQL Server’s built-in clustering for scalability, redundancy and ease of maintenance.

 

 

0 Comments

Please sign in to leave a comment.
Powered by Zendesk