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, the SQLite database was automatically installed up to version 4.4.3 Beefalo V2. As of version 5.0.0 Jaglion, you can choose to install a PostgreSQL database that is included in the SEP sesam installer (or use the SQLite database that does not require a server to be set up and is used with SEP sesam by default). For details, see Installation on Microsoft Windows.
- 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 Antivirus Exclusions for 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.
- (Windows only) Make sure that you are using CPUs with supported AVX versions (AVX, AVX2, or AVX-512) and FMA3 (Fused Multiply-Add 3-operand Form) or FMA4 (Fused Multiply-Add 4-operand Form) to prevent the Sesam Transfer Protocol Server (STPD) from automatically disabling the HTTPS port. This happens when the CPU instructions are missing due to unsupported AVX. Consequently, the TLS key and certificate cannot be created. For a list of supported AVX versions, see Advanced Vector Extensions.
|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 32 GB RAM||Minimum 32 GB RAM||64 GB RAM||Minimum 128 GB RAM||Minimum 8 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||200 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 the 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.Si3 Deduplication Hardware Requirements/en
Java Compatibility Matrix
|Java version||SEP sesam version|
|Java 17||on demand Note1|
|OpenJDK 11 LTS||4.4.3 Beefalo, 5.0.0 Jaglion, 188.8.131.52 Jaglion V2, 5.1.0 Apollon Note2|
|Java 11||4.4.3 Beefalo, 5.0.0 Jaglion, 184.108.40.206 Jaglion V2, 5.1.0 Apollon Note2|
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, 5.0.0 Jaglion, 220.127.116.11 Jaglion V2 Note2|
|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 Note3|
|Java 6||4.2.1 & 4.2.2|
- SEP sesam 18.104.22.168 Jaglion V2, including SP1, supports Java 17 only on demand, if the use of Java 17 from the command line has been enabled with
sm_setup set_java_path -f <java_17_installation_path>
- Java 1.8 (≥ 1.8.0_111) is only accepted if it is already installed and the computer does not have a 4K display.
- 22.214.171.124 Jaglion V2 is the last version of SEP sesam that supports Java 1.8.
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.