terra4d:hwsetup []

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Hardware Requirements and Virtualisation Environments ======
The following examples are showing typical configurations. Which configuration to choose in a project depends on several factors:
  * number of different types of sub-systems
  * number of data points per sub-system
  * failover configuration required or not
  * multiple data centres or not
  * operating system requirements of integrated sub-system plugins

The configurations can also be mixed, changed and grow with the project phases. Example: a POC installation can start at entry level and later grow to enterprise with multiple data centres. 
----
\\ 
====== Entry Level ======
{{:terra4d:t4d_architecture_entry.svg?300|}}
In this configuration all software components are running on one physical server platform. There is no virtualisation environment and it is a basic configuration which is often used for POC installations or demonstrations. 

==== Physical Server Hardware Requirements ====
|CPU|Quad core, Intel Core i7, 10th Gen. or higher\\ OR \\ equivilant AMD|
|Graphics (optional*)|Nvidia graphics (GeForce 10 series or higher with >= 1 GB RAM)\\ OR \\ Intel integrated graphics\\ OR \\ AMD integrated graphics|
|RAM| >= 8 GB RAM (16GB RAM recommended)|
|HDD/SSD|>= 50 GB free disk space excl. OS (SSD recommended)|
[*]: no GPU in server: 3D GIS visualization when running applications not possible;  client workstations are not affected\\
Remark: this is a recommendation for most common configurations; please consider the points mentioned above or contact FAST Support

==== Server Software Requirements ====
|OS|Windows 10, 64 bit or later\\ Windows Server 2019 or later|
|Docker Engine|Version 20.10.0 or later|
|Database|MySQL version 8.0 or later\\ MariaDB version 11.0 or later|
==== Storage Requirements ====
Amount of storage depends on the number of incidents, the content of incidents and the retention time.
As a benchmark we calculate 0.5-2MB per incident.
----
\\ 
====== Business Level ======
{{:terra4d:t4d_architecture_business.svg?700|}}
This configuration is using hardware virtualisation. The physical hardware platforms are decoupled from the virtual machine servers. A failure of one physical server hardware will not result in a failure of software processes running on the virtual machines.

==== Physical Server Hardware Requirements ====
|CPU|4 cores per Management Server VM\\ 4 cores per Process Server VM\\ 2-4 cores per Communication Server VM\\ 4 cores per DB Server VM\\ 2-4 cores per Acquisition Plugin VM|
|Graphics (optional*)|Nvidia graphics (GeForce 10 series or higher with >= 1 GB RAM) \\ OR \\ Intel integrated graphics\\ OR \\ AMD integrated graphics|
|RAM| >= 8 GB RAM per VM|
|Storage|>= 250 GB per VM\\ 500GB..5TB Database storage for incidents and processes|
Remark: this is a recommendation for most common configurations; please consider the points mentioned above or contact FAST Support

==== Server Software Requirements ====
|OS Windows|Windows 10, 64 bit or later\\ Windows Server 2019 or later|
|OS Linux|Ubuntu version 18.04 or later\\ Debian version 8 or later\\ Red Hat version RHEL 8 or later\\ CentOS version 6 or later|
|Docker Engine|Version 20.10.0 or later|
|Virtualisation|VMware: vSphere/ESXi version 7.0 or later (incl. vCenter)\\ Proxmox VE 8.1 or later|
|VM|4 cores, 4GB RAM or more|
|Database|MySQL version 8.0 or later\\ MariaDB version 11.0 or later\\ MS SQL Server version 2016 or later[*]|
[*] if already existing in project or requested by customer; MS SQL does not work as docker image and not under Linux
==== Storage Requirements ====
Amount of storage depends on the number of incidents, the content of incidents and the retention time.
As a benchmark we calculate 0.5-2MB per incident.
----
\\ 
====== Enterprise Level ======
{{:terra4d:t4d_architecture_enterprise.svg?900|}}
\\ 
For hardware, software and storage requirements please refer to previous chapter: [[#business_level|Business Level]]
User Tools

Site Tools

Page Tools
