System requirements and preparation
In order to create your purchase license, you must provide us with yours in advance FQDN, fully qualified domain name.
For the installation of migRaven.24/7 a standalone server (or a corresponding VM) must be made available.
When making your selection, please note that migRaven.24/7 is a database supported application. For this reason, appropriate speed should be used SSD storage .
The database is included during the initial installation migRaven Server & Hosting Installed. The Neo4j graph database is used. Neo4j recommends open source Java Azul Zulu JRE.
Suggestions: RAM and fast SSD always have a positive effect on the performance of a Database .
The more RAM is available for the system or the faster the SSD, the faster database reads and writes can be processed.
Minimum requirement for the migRaven Server & Hosting is Windows Server 2016 or newer.
Before you begin the installation, please ensure that the server meets the requirements below.
Sizing for the installation of migRaven.24/7
Resource | RAM | CPU | SSD capacity | Description |
Windows Server OS | 6 GB | 4 cores | 80 GB | |
Per 1000 users | 2 GB | 1 core | 2 GB | zusätzlich |
1 TB of data each | 2 GB | 1 core | 5 GB | zusätzlich |
The complete RAM Size must also be available as a reserve on the C: partition for caching.
Regardless, we recommend one second partition to store the database.
The examples below are guidelines and allow for slight tolerances.
Example configuration for 1.500 user + 10 TB data to be managed
Resource | RAM | CPU | SSD capacity |
Windows Server OS | 6 GB | 4 cores | 80 GB |
1500 users | 4 GB | 2 core | 2 GB |
10TB of data | 20 GB | 10 core | 50 GB |
Caching on C:\ | 30 GB | ||
Total | 30 GB | 16 cores | 162 GB |
Example configuration for 3.000 user + 80 TB data to be managed
Resource | RAM | CPU | SSD capacity |
Windows Server OS | 6 GB | 4 cores | 80 GB |
3000 users | 6 GB | 3 cores | 60 GB |
80TB of data | 160 GB | 80 cores | 400GB |
Caching on C:\ | 42 GB | ||
Total | 172 GB | 87 cores | 582 GB |
In significantly larger environments, the dimensioning of the server equipment must be decided individually.
For example, it can make sense to install scan agents on remote servers if there are a large number of file server resources to be scanned.