Architecture |
x64 |
Operating System |
Any of the following:
|
CPU |
Min. 4 cores (for example, for evaluation purposes). For any real-world uses, at least 8 cores are recommended. |
Memory |
Min. 4GB (for example, for evaluation purposes). For any real-world uses, at least 8GB is recommended.* |
Hard Disk Space |
Min. 14GB when installing all components. 10GB out of that is reserved space that is not in constant use. It is needed for temporary storage during activity peaks such as repository cleanup operations. |
Additional Software and Services |
|
* This is only an observation. To estimate consumed memory (in gigabytes) more accurately, use the following formula:
<number_of_cores> * 0.26 + 6
Remember that this means memory used by InTrust Server alone on average. During activity peaks (such as data merging and report building), the memory requirements of InTrust increase.
If you deploy InTrust on a virtual machine, make sure the CPU and memory requirements above are met, and do not overload the virtual machine host.
Computers that are supposed to run InTrust Server must be configured to allow for incoming connections on the TCP port on which your InTrust Servers are configured to communicate with agents (900 by default), the TCP port used for InTrust Server management (8340 by default) and TCP port 8341.
Any of the following:
|
Notes:
|
|
Notes: * A local or remote installation can be used. Make sure ASP extensions are allowed. ** A local or remote installation of Reporting Services can be used; Microsoft SQL Server Express Edition with Advanced Services is not supported. |
For requirements on local or remote installation of Knowledge Portal, refer to the Knowledge Portal documentation.
Architecture |
|
Operating System | Any of the following:
|
Additional Software and Services |
|
Internet Explorer shipped with Windows, or an upgraded version of Internet Explorer.
|
Notes: Check Internet Explorer security settings as follows:
If you plan to use a web server based on Microsoft IIS 7.0, check that the following role services are installed in addition to default role services of Web Server:
|
Architecture |
|
Operating System |
Any of the following:
|
Additional Software and Services |
|
The requirements for an InTrust repository cannot be stated definitely. This topic outlines the general considerations for choosing the right locations for your repositories.
Disk space requirements depend on many things, and they vary greatly from environment to environment. For some examples, see the following table:
Considerations |
Comments |
---|---|
What kinds of events are stored? |
Windows event log events are highly normalized and compress very well. In events from lesser-known logs, the field values are less predictable, and the events require more disk space. |
What type of environment does the data come from? |
Data from non-Windows environments, especially from Syslog, is generally the least compact. |
Is the repository indexed? |
An indexed repository is roughly twice the size of a non-indexed repository with the same data. |
It is recommended that you host your repositories on computers that are not InTrust servers.
InTrust repositories can be hosted by appliances and virtual appliances based on EMC technology. Support for these systems is provided by the use of the CAS SDK in InTrust.
The following solutions are known to be suitable for hosting InTrust repositories:
Dell EMC Elastic Cloud Storage (ECS)
See also:
© ALL RIGHTS RESERVED. 使用条款 隐私 Cookie Preference Center