Difference between revisions of "Si3 Deduplication Hardware Requirements"

From SEPsesam
Jump to: navigation, search
(Added note as proposed by CR.)
(Updated: added Si3 initial size limit)
Line 29: Line 29:
 
* 2 CPU cores
 
* 2 CPU cores
 
* 1 TB free hard disk space
 
* 1 TB free hard disk space
 +
 +
;{{anchor|restriction}}Restriction: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 [[SEP_sesam_Release_Versions|Tigon V2 (4.4.3.46)]]. This restriction is valid when creating a new Si3 deduplication store in GUI.
 +
{{note|Customers with special requirements for larger Si3 deduplication store should contact [mailto:support@sep.de 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.
 
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.
Line 35: Line 38:
 
{{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.}}
 
{{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.}}
  
{| border="2" cellpadding="4" cellspacing="0" style="width:30%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"
+
{| border="2" cellpadding="4" cellspacing="0" style="width:50%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"
 
|- style="background:#FFCC01; color:#002F55"
 
|- style="background:#FFCC01; color:#002F55"
! scope="col" style="width: 20px;" | Si3 data store capacity  
+
! scope="col" style="width: 20px;" | Si3 data store capacity (check [[Si3_Deduplication_Hardware_Requirements#restriction|initial size restriction]])
 
! scope="col" style="width: 20px;" | RAM
 
! scope="col" style="width: 20px;" | RAM
 
|-
 
|-
Line 71: Line 74:
 
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)!
 
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)!
  
{| border="2" cellpadding="4" cellspacing="0" style="width:30%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"
+
{| border="2" cellpadding="4" cellspacing="0" style="width:50%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"
 
|- style="background:#FFCC01; color:#002F55"
 
|- style="background:#FFCC01; color:#002F55"
 
! scope="col" style="width: 20px;" | Backed up data (before dedup)
 
! scope="col" style="width: 20px;" | Backed up data (before dedup)

Revision as of 09:07, 13 November 2017


Copyright © SEP AG 1999-2020. 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/4.4.3 Tigon. For previous documentation version(s), check documentation archive.


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
Restriction
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 (4.4.3.46). 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 2.5 GiB
20 TB 4.8 GiB
30 TB 7.1 GiB
40 TB 9.4 GiB
50 TB 11.7 GiB
60 TB 14 GiB
Example
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.