SEP sesam Requirements

From SEPsesam
Jump to: navigation, search

Copyright © SEP AG 1999-2017. All rights reserved.

Any form of reproduction of the contents or parts of this manual is allowed only with the express written permission from SEP AG. When compiling and designing user documentation SEP AG uses great diligence and attempts to deliver accurate and correct information. However, SEP AG cannot issue a guarantee for the contents of this manual.

Docs latest icon.png Welcome to the latest SEP sesam documentation version 4.4.3. For previous documentation version(s), check documentation archive.


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.

Antivirus software

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.

Hardware Requirements

The following are the hardware requirements for SEP sesam Server or RDS. They are similar for both, except that the space for the SEP sesam database required on the file system is not necessary for RDS.

Hardware requirements for SEP sesam Server or RDS are representing 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
Memory (without Si3 deduplication) 8 GB RAM Minimum 16 GB RAM 32 GB RAM Minimum 64 GB RAM
Memory (with Si3 deduplication) Minimum 16 GB RAM Minimum 32 GB RAM 64 GB RAM Minimum 128 GB RAM
Core (without Si3 deduplication) 1x CPU with 4 cores 1x CPU with 8 cores Minimum 1x CPU with 8 cores Minimum 2x CPUs with 4 cores
Core (with Si3 deduplication) 1x CPU with 6 cores 2x CPUs with 8 cores 2x CPUs with minimum 8 cores Minimum 2x CPUs with 8 cores
Minimum hard disk space for SEP sesam metadata 100 GB 300 GB 500 GB 500 GB
No. of backup clients Up to 15 Recommended up to 50 Recommended up to 150 Recommended for more than 150

Si3 Deduplication Hardware Requirements

The following minimum hardware requirements apply for SEP sesam Si3 deduplication server. Keep in mind that the following 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.

Productive environments
  • 16 GB RAM
  • 4 CPU cores for one Si3 data store
  • 1 TB free hard disk space
Test environments only
  • minimum 8 GB RAM
  • 2 CPU cores
  • 1 TB free hard disk space

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 ( This restriction is valid when creating a new Si3 deduplication store in GUI.
Information sign.png Note
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.

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.

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.

Information sign.png Note
It is not recommended to run Si3 deduplication (SEP sesam Server or RDS) on a virtual machine. If this is the case, 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. For other virtual server requirements, you should follow the same recommendations as for physical server.
Si3 data store capacity (check initial size restriction) RAM
10 TB 8 GiB
20 TB 13 GiB
30 TB 18 GiB
40 TB 22 GiB
50 TB 22 GiB
60 TB 22 GiB
RAM required for Si3 data store with 50 TB capacity is 16 GiB RAM for productive environment + 12 GiB RAM for 50 TB Si3 = ~ 32 GiB RAM.

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
10 TB 4
20 TB 4
40 TB 8
80 TB 16
160 TB 32 or 64
Information sign.png Note
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
Java 9 is not supported!
Java 8 (at least patch level 111) ≥ JRE 1.8.0_111 4.4.3 Tigon v. 2 Note
Java 8 (required for Windows) 4.4.3 Note
Java 7 (all OS except Windows) 4.4.3 Note
Java 7 4.4.2
Java 6 4.2.1 & 4.2.2

Note: SEP sesam version ≥ 4.4.3 requires JavaFX for the new web dashboard and user-defined schedules features. Oracle®'s Java 8 already includes JavaFX (e.g., on Windows). Oracle®'s OpenJFX Project provides JavaFX packages that can be installed separately if some other Java version is used, such as IBM Java, which is typically installed on SuSE. Depending on your system and Java version, manually install either OpenJFX package or Oracle®'s Java 8 on your SEP sesam GUI client to have all the latest features available.