Source:Si3 Deduplication Hardware Requirements: Difference between revisions

From SEPsesam
mNo edit summary
(Marked this version for translation)
 
(63 intermediate revisions by 5 users not shown)
Line 1: Line 1:
<noinclude>
<noinclude><div class="noprint"><languages />
<languages />
<br />


<translate><!--T:1-->
<translate>== Si3 hardware requirements == <!--T:6--> </translate>
{{Copyright SEP AG|en}}
{{Navigation_latest|release=4.4.3/4.4.3 ''Tigon''|link=[[SEP_sesam_Documentation#previous|documentation archive]]}}</translate><br />


<div class="boilerplate metadata" id="Additional resources" style="background-color:#ecedf1; color:#8695a7; border: 1px ridge #cdd3db; margin: 0.5em; padding: 0.5em; float: right; width: 25%; "><center><b>
</div></noinclude>
<translate><!--T:2-->
*<translate><!--T:42--> For the minimum Si3/Si3-NG hardware requirements that apply to the SEP sesam Si3/Si3-NG deduplication server, see [[Special:MyLanguage/SEP_sesam_Requirements#hardware|Hardware Requirements]].</translate>
Additional resources</translate></b></center>
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"
| rowspan="2" style="padding:0px 10px 0px;" |
<translate><!--T:3-->
[[File:SEP_next.png|45px|link=Special:MyLanguage/Configuring_an_Si3_Deduplication_Store|Configuring an Si3 Deduplication Store]]</translate>
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" |
<translate><!--T:4-->
See also: [http://www.sep.de/products/deduplication/deduplication-analysis/#_ SEP Tachometer] – [[Special:MyLanguage/Deduplication|Deduplication]] – [[Special:MyLanguage/Configuring_an_Si3_Deduplication_Store|Configuring an Si3 Deduplication Store]] – [[Special:MyLanguage/SEP_sesam_Requirements|SEP sesam Requirements]] – [[Special:MyLanguage/Licensing|Licensing]]</translate>
|}
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"
| rowspan="2" style="padding:0px 10px 0px;" |
[[File:support-matrix.png|45px|link=SEP sesam OS and Database Support Matrix|]]
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" |
<translate><!--T:5-->
Check supported [[SEP sesam OS and Database Support Matrix|configurations and versions]] and [[Special:MyLanguage/Java_Compatibility_Matrix|Java compatibility matrix]].</translate>
|}</div></noinclude>
<translate><!--T:6-->
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.</translate>


; <translate><!--T:7-->
*<translate><!--T:16-->
Productive environments</translate>
For details on the required Java version, see [[Special:MyLanguage/Java_Compatibility_Matrix|Java Compatibility Matrix]]. Si3/Si3-NG is not mandatory, so there is no dependency rule for it in the RPM/DEB packages.</translate>


* 16 GB RAM
*<translate><!--T:29-->
* <translate><!--T:8-->
When estimating the maximum size of a deduplication store, you have to ensure that there is enough space available for dedup trash, otherwise the deduplication store will run out of space. You should calculate the required disk space based on a representative sample of your full backup and add the additional storage space equal to approximately 50% of the representative full backup.</translate>
4 CPU cores for one Si3 data store</translate>


* <translate>1 TB free hard disk space</translate>
===={{anchor|protocols}}<translate><!--T:31-->
Disk attachment and protocols====
Si3/Si3-NG supports all types of direct-attached disk storage, such as serial attached SCSI (SAS), Serial ATA (SATA), and Fibre Channel (FC)/LUN.</translate>


; <translate><!--T:9-->
<translate><!--T:32-->
Test environments only</translate>
====Performance tip====
'''''Applies to Windows only''''': SEP AG recommends using the ''High performance'' power plan to increase the performance of your backup. Note that Windows sets all computers to the ''Balanced'' power plan by default and you must manually switch to the ''High Performance'' power plan. This way, your Windows computer will use more power, but the systems with Si3 will always operate at the highest performance level.
*From the Start menu, go to ''Control Panel'' -> ''System and Security'' -> ''Power Options'' and change the setting to ''High performance''.</translate>


* <translate><!--T:10-->
===={{anchor|restriction}}<translate><!--T:40--> Restrictions</translate>====
minimum 8 GB RAM </translate>


* <translate><!--T:11-->
<ul><li><translate><!--T:41--> '''Si3 NG''' deduplication store is not supported for NSS and MooseFS volumes.</translate></li>
2 CPU cores</translate>


* <translate><!--T:12-->
<li><translate><!--T:13-->
1 TB free hard disk space</translate>
To avoid problems resulting from the combination of excessively large Si3 deduplication stores and inefficient hardware, the '''maximum initial Si3/Si3-NG deduplication store size''' is '''limited to 40 TB'''. If you would need to increase this limit, contact [mailto:support@sep.de SEP support].</translate></li>


<translate><!--T:33-->
This limitation applies to the creation of a new Si3/Si3-NG deduplication store in the GUI.</translate></ul>
{{note|<translate><!--T:19-->
It is recommended to run Si3 deduplication (SEP sesam Server or RDS) on the physical host. It is also possible to run it on a virtual machine. In this case, take into account that deduplication consumes a lot of server resources for reading, processing and writing the deduplicated data, as well as for some other deduplication tasks such as housekeeping and various checks. These tasks require a large amount of IO and a large amount of memory. Si3 performance can be affected by other virtual machines running on the same host. Therefore, if you are running Si3 on a VM, you should be aware of possible bottlenecks and shortcomings.</translate>}}


;<translate><!--T:13-->
<translate>====Required additional amount of RAM and CPU cores==== <!--T:17-->
{{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.</translate>


{{<translate><!--T:14-->
<!--T:34-->
note</translate>|<translate><!--T:15-->
Memory requirements are dependent on the number of concurrent streams and expected workload. The following tables show the recommended '''''minimum additional'' amount of RAM''' and '''CPU cores''' for a Si3/Si3-NG data store to ensure good performance. The TB value corresponds to the capacity of the Si3/Si3-NG data store.</translate>
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.</translate>}}


<translate><!--T:16-->
{{note|<translate><!--T:25-->
For details on the required Java version, see [[Special:MyLanguage/Java_Compatibility_Matrix|Java Compatibility Matrix]]. Si3 is not mandatory, therefore there is no dependency rule in the RPM/DEB packages for it.
These requirements relate solely to the need for deduplication. In addition, you should consider the amount of memory for the operating system and other services.</translate>}}
 
<!--T:17-->
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.</translate>
{{<translate><!--T:18-->
note</translate>|<translate><!--T:19-->
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.</translate>}}


{| border="2" cellpadding="4" cellspacing="0" style="width:50%; 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;" | <translate><!--T:20-->
! scope="col" style="width: 20px;" | <translate><!--T:20-->
Si3 data store capacity (check [[Special:MyLanguage/Si3_Deduplication_Hardware_Requirements#restriction|initial size restriction]])</translate>  
Si3/Si3-NG data store capacity (check [[#restriction|initial size limit]])</translate>  
! scope="col" style="width: 20px;" | RAM
! scope="col" style="width: 20px;" | RAM
|-
|-
|   10 TB  || 8 GiB
| <20 TB  || <translate><!--T:35--> at least 16 GiB</translate>
|-
|  20 TB  || 13 GiB
|-
|  30 TB  || 18 GiB
|-
|-
|   40 TB   || 22 GiB
| 20-40 TB || <translate><!--T:36--> at least 32 GiB</translate>
|-
|  50 TB  || 22 GiB
|-
|  60 TB  || 22 GiB
<!--
  70 TB:  16314M
  80 TB:  18609M
  90 TB:  20904M
  100 TB:  23199M
  110 TB:  25494M
  120 TB:  27789M
  130 TB:  30083M
  140 TB:  32378M
  150 TB:   34673M
  160 TB:  36968M
  170 TB:  39263M
  180 TB:  41558M
  190 TB:  43853M
  200 TB:  46148M
-->
|}
|}
;<translate><!--T:21-->
 
''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.
<!--T:30-->
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)!</translate>
<translate><!--T:37--> The following table shows the '''number of CPU cores''' required for a Si3/Si3-NG data store. The TB value is the amount of data backed up (before deduplication)!</translate>


{| border="2" cellpadding="4" cellspacing="0" style="width:50%; 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;"
Line 109: Line 62:


! scope="col" style="width: 20px;" | <translate><!--T:23-->
! scope="col" style="width: 20px;" | <translate><!--T:23-->
CPU cores</translate>
CPU cores <sup>[[#note|'''Note''']]</sup></translate>


|-
|-
Line 117: Line 70:
|-
|-
|  40 TB  ||8
|  40 TB  ||8
|-
 
|  80 TB  ||16
|-
|  160 TB  ||32 or 64
|}
|}
<div id="note"><span style="font-size:92%; line-height: 1.3em; color:black;"><translate><!--T:38--> '''Note'''</translate></span></div>
<span style="font-size:92%; line-height: 1.3em; color:black;"><translate><!--T:39--> This is the minimum amount to ensure good performance. Depending on the number of concurrent streams, more cores may be needed.</translate></span>


{{<translate><!--T:24-->
<noinclude><div class="noprint">{{Copyright}}</div></noinclude>
note</translate>|<translate><!--T:25-->
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.</translate>}}
<div class="noprint"><noinclude>
<translate>==See also== <!--T:26-->
 
<!--T:27-->
[http://www.sep.de/products/deduplication/deduplication-analysis/#_ SEP Tachometer] – [[Special:MyLanguage/Deduplication|Deduplication]] – [[Special:MyLanguage/Configuring_an_Si3_Deduplication_Store|Configuring an Si3 Deduplication Store]] – [[Special:MyLanguage/SEP_sesam_Requirements|SEP sesam Requirements]] – [[Special:MyLanguage/Licensing|Licensing]]</translate>

Latest revision as of 13:33, 21 September 2023

  • For the minimum Si3/Si3-NG hardware requirements that apply to the SEP sesam Si3/Si3-NG deduplication server, see Hardware Requirements.
  • For details on the required Java version, see Java Compatibility Matrix. Si3/Si3-NG is not mandatory, so there is no dependency rule for it in the RPM/DEB packages.
  • When estimating the maximum size of a deduplication store, you have to ensure that there is enough space available for dedup trash, otherwise the deduplication store will run out of space. You should calculate the required disk space based on a representative sample of your full backup and add the additional storage space equal to approximately 50% of the representative full backup.

Disk attachment and protocols

Si3/Si3-NG supports all types of direct-attached disk storage, such as serial attached SCSI (SAS), Serial ATA (SATA), and Fibre Channel (FC)/LUN.

Performance tip

Applies to Windows only: SEP AG recommends using the High performance power plan to increase the performance of your backup. Note that Windows sets all computers to the Balanced power plan by default and you must manually switch to the High Performance power plan. This way, your Windows computer will use more power, but the systems with Si3 will always operate at the highest performance level.

  • From the Start menu, go to Control Panel -> System and Security -> Power Options and change the setting to High performance.

Restrictions

  • Si3 NG deduplication store is not supported for NSS and MooseFS volumes.
  • To avoid problems resulting from the combination of excessively large Si3 deduplication stores and inefficient hardware, the maximum initial Si3/Si3-NG deduplication store size is limited to 40 TB. If you would need to increase this limit, contact SEP support.
  • This limitation applies to the creation of a new Si3/Si3-NG deduplication store in the GUI.
Information sign.png Note
It is recommended to run Si3 deduplication (SEP sesam Server or RDS) on the physical host. It is also possible to run it on a virtual machine. In this case, take into account that deduplication consumes a lot of server resources for reading, processing and writing the deduplicated data, as well as for some other deduplication tasks such as housekeeping and various checks. These tasks require a large amount of IO and a large amount of memory. Si3 performance can be affected by other virtual machines running on the same host. Therefore, if you are running Si3 on a VM, you should be aware of possible bottlenecks and shortcomings.

Required additional amount of RAM and CPU cores

Memory requirements are dependent on the number of concurrent streams and expected workload. The following tables show the recommended minimum additional amount of RAM and CPU cores for a Si3/Si3-NG data store to ensure good performance. The TB value corresponds to the capacity of the Si3/Si3-NG data store.

Information sign.png Note
These requirements relate solely to the need for deduplication. In addition, you should consider the amount of memory for the operating system and other services.
Si3/Si3-NG data store capacity (check initial size limit) RAM
<20 TB at least 16 GiB
20-40 TB at least 32 GiB

The following table shows the number of CPU cores required for a Si3/Si3-NG data store. The TB value is the amount of data backed up (before deduplication)!

Backed up data (before dedup) CPU cores Note
10 TB 4
20 TB 4
40 TB 8
Note

This is the minimum amount to ensure good performance. Depending on the number of concurrent streams, more cores may be needed.

Copyright © SEP AG 1999-2024. 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.