Configuring an Si3 Deduplication Store
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.
Both, Si3T and Si3S require a configured Si3 deduplication store. Only one Si3 deduplication store can be configured on a server. A valid licence is required for each Si3 deduplication store.
You can download SEP Tachometer to analyse the structure of your data and calculate potential savings with SEP sesam Si3 deduplication. Check SEP Tachometer.
The following prerequisites must be met to configure an Si3 deduplication store.
The Si3 deduplication store only supports 64-bit versions of the following operating systems:
- Windows 2008/2008 R2
- Windows 2012/2012 R2
- SLES 11/12
- RHEL 6/7
- Debian Wheezy/Jessie
Additional RAM / CPU 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 (126.96.36.199). This restriction is valid when creating a new Si3 deduplication store in GUI.
|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.
|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|
|160 TB||32 or 64|
|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.|