SEP sesam Requirements
For smooth installation of SEP sesam backup software in the network, name resolution must work properly. Specify a fully qualified name for each SEP sesam component, e.g., every server and client in network.
When finding a client, the operating system (Windows or Linux) first checks the hosts file for name resolution. Next, the configured DNS server is checked. If the DNS server is misconfigured or missing, the hosts file must be set up correctly to provide DNS. You have to enter the names and addresses of all SEP sesam components: SEP sesam Server, backup clients and machines running the graphical user interface (GUI). You must not remove or modify any existing entry of localhost in your hosts file. For details, see How to check DNS configuration.
A DNS server is preferred over entries in the hosts files of all devices. A DNS server allows a system-wide solution. All SEP sesam components must have their names and IP addresses (reverse lookup) added to the DNS server.
On 64-bit Linux, FreeBSD and Solaris PostgresSQL is used as the SEP sesam database. When SEP sesam is installed on MS Windows, SQLite database is automatically installed. When SEP sesam is installed on a 64-bit Unix operating system, PostgresSQL has to be installed before the SEP sesam Server to enable the DB instance to be set up for use.
On MS Windows, .Net Framework 4 is required for SEP sesam Server installation.
Deactivate or remove the antivirus software before installing SEP sesam components on each computer. Failure to disable active antivirus software may result in a failed, corrupt or incomplete installation. If antivirus software is installed, it is strongly recommended to turn off any on-demand scanning while a backup is running. For more details, see What effect does an antivirus scanner have on SEP sesam.
The following are the hardware requirements for the SEP sesam Server, RDS or SEP sesam Client. They are similar for both servers, SEP sesam Server and RDS, except for the required space on the file system for the SEP sesam database, which is not necessary for RDS.
The hardware requirements for the SEP sesam components represent the common requirements. Additional amount of RAM/CPU may be required for bigger Si3 data stores. For details, see Si3 Deduplication Hardware Requirements.
|Requirements||SEP sesam Server Standard edition||SEP sesam Advanced Server edition||SEP sesam Premium Server edition||SEP sesam Enterprise Server||SEP sesam Client|
|Memory (without Si3 deduplication)||8 GB RAM||Minimum 16 GB RAM||32 GB RAM||Minimum 64 GB RAM||2 GB (recommended 4 GB)|
|Memory (with Si3 deduplication)||Minimum 16 GB RAM||Minimum 32 GB RAM||64 GB RAM||Minimum 128 GB RAM||Minimum 4 GB|
|Core (without Si3 deduplication)||1x CPU with 4 cores (≥ 2,4 GHz)||1x CPU with 8 cores (≥ 2,4 GHz)||Minimum 1x CPU with 8 cores (≥ 2,4 GHz)||Minimum 2x CPUs with 4 cores (≥ 2,4 GHz)||-|
|Core (with Si3 deduplication)||1x CPU with 6 cores (≥ 2,6 GHz)||2x CPUs with 8 cores (≥ 2,6 GHz)||2x CPUs with minimum 8 cores (≥ 2,6 GHz)||Minimum 2x CPUs with 8 cores (≥ 2,6 GHz)||-|
|Minimum hard disk space for SEP sesam metadata||100 GB||300 GB||500 GB||500 GB||4 GB (for all client data)|
|No. of backup clients||Up to 15||Recommended up to 50||Recommended up to 150||Recommended for more than 150||-|
Si3 Deduplication Hardware Requirements
- For the minimum Si3 hardware requirements that apply to SEP sesam Si3 deduplication server, see the above requirements list. Keep in mind that these requirements represent the demand for deduplication only. In addition, the amount of memory for the operating system and other services should be taken into account.
- For details on the required Java version, see Java Compatibility Matrix. Si3 is not mandatory, therefore there is no dependency rule in the RPM/DEB packages for it.
- When estimating the maximum size for a deduplication store, you have to ensure that there is enough space available for dedup trash or the deduplication store will run out of space. You should calculate the required disk space based on the representative sample of your full backup and add the amount of extra space equal to approx. 50% of the representative full backup.
To avoid issues arising from combination of too large Si3 deduplication stores and inefficient hardware, the maximum initial Si3 deduplication store size is restricted to 40 TB since Tigon V2 (22.214.171.124). This restriction is valid when creating a new Si3 deduplication store in GUI. Note that customers with special requirements for larger Si3 deduplication store should contact SEP support to be able to increase the value up to an optimum size for their specific environments.
Required additional amount of RAM and CPU cores
The following tables show the required additional amount of RAM and CPU cores for one Si3 data store. The TB value is the capacity of the Si3 data store.
|It is not recommended to run Si3 deduplication (SEP sesam Server or RDS) on a virtual machine. If this is the case, like evaluation or test, consider to limit the capacity of Si3 data store to 100 GB thus ensuring normal VM operation. Have in mind that deduplication consumes a lot of server resources for reading, processing, and writing deduplicated data, therefore you should be aware of running Si3 on a VM deployment limitation.|
|Si3 data store capacity (check initial size restriction)||RAM|
|<20 TB||16 GiB|
|20-40 TB||32 GiB|
To find out how much RAM is required by Si3 at which capacity, enter the command sm_dedup_interface propose jvmconfig <Si3-CAPACITY> at an admin command line (you must set sesam profile to run the command). The MaxDirectMemorySize output is the required RAM value.
The following table shows the amount of CPU cores required for one Si3 data store. The TB value is the amount of backed up data (before deduplication)!
|Backed up data (before dedup)||CPU cores|
|Keep in mind that the stated requirements represent the demand for deduplication only. In addition to these requirements, the amount of memory for the operating system and other services should be taken into account.|
Java Compatibility Matrix
|Java version||SEP sesam version|
|OpenJDK 11 LTS||4.4.3 Beefalo Note1|
|Java 11||4.4.3 Beefalo Note1|
Java 10 is not supported!
Java 9 is not supported!
|Java 8 ≥ patch level 111 (both Windows and Linux)||4.4.3 Grolar; 4.4.3 Beefalo Note1|
|Java 8 (at least patch level 111) ≥ JRE 1.8.0_111 (required for Linux)||v. ≥ 4.4.3 Tigon V2|
|Java 8 (required for Windows)||v. ≥ 4.4.3|
|Java 7 (all OS except Windows)||4.4.3 Note2|
|Java 6||4.2.1 & 4.2.2|
Java 1.8 (≥ 1.8.0_111) is only accepted if it is already installed and the computer does not have a 4K display.
SEP sesam versions 4.4.3 until 4.4.3 Tigon V1 running on non-Windows platform require Java 7, however, SEP sesam uses JavaFX for its web dashboard and user-defined schedules features. If you want to have all the 4.4.3 features available, you need OpenJFX package or Oracle®'s Java 8 (already includes JavaFX) on your SEP sesam GUI client.