Source:Si3 Deduplication Hardware Requirements: Difference between revisions

From SEPsesam
(Testing transclusion.)
(Fixing transclusion.)
(37 intermediate revisions by 3 users not shown)
Line 4: Line 4:
<translate><!--T:1-->
<translate><!--T:1-->
{{Copyright SEP AG|en}}
{{Copyright SEP AG|en}}
{{Navigation_latest|release=4.4.3/4.4.3 ''Tigon''|link=[[SEP_sesam_Documentation#previous|documentation archive]]}}</translate><br />
{{Navigation_latest|release=[[Special:MyLanguage/SEP_sesam_Release_Versions|4.4.3/4.4.3 ''Beefalo V2'']]|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 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>
Line 12: Line 12:
| rowspan="2" style="padding:0px 10px 0px;" |
| rowspan="2" style="padding:0px 10px 0px;" |
<translate><!--T:3-->
<translate><!--T:3-->
[[File:SEP_next.png|45px|link=Special:MyLanguage/Configuring_an_Si3_Deduplication_Store|Configuring an Si3 Deduplication Store]]</translate>
[[File:SEP_next.png|45px|link=Special:MyLanguage/4_4_3_Grolar:Configuring_Si3_Deduplication_Store|Configuring an Si3 Deduplication Store]]</translate>
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" |
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" |
<translate><!--T:4-->
<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>
See also: [https://www.sep.de/sep-sesam/si3-tachometer-analyze/ SEP Tachometer] – [[Special:MyLanguage/Deduplication|Deduplication]] – [[Special:MyLanguage/4_4_3_Grolar:Configuring_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;"
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"
Line 24: Line 24:
Check supported [[SEP sesam OS and Database Support Matrix|configurations and versions]] and [[Special:MyLanguage/Java_Compatibility_Matrix|Java compatibility matrix]].</translate>
Check supported [[SEP sesam OS and Database Support Matrix|configurations and versions]] and [[Special:MyLanguage/Java_Compatibility_Matrix|Java compatibility matrix]].</translate>
|}</div></noinclude>
|}</div></noinclude>
<translate><!--T:6-->
<translate>===Si3 hardware requirements=== <!--T:6-->
<onlyinclude>*For the minimum Si3 hardware requirements that apply to SEP sesam Si3 deduplication server, see</onlyinclude> <noinclude>[[Special:MyLanguage/Hardware_requirements|Hardware requirements]].</noinclude><includeonly>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.</includeonly></translate>
<noinclude>*For the minimum Si3 hardware requirements that apply to SEP sesam Si3 deduplication server, see [[Special:MyLanguage/SEP_sesam_Requirements#hardware|Hardware requirements]].</noinclude></translate>
 
<translate><!--T:16-->
<translate><!--T:16-->
<onlyinclude>*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.</translate>
<onlyinclude>*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.</translate>
<translate>
<!--T:29-->
*When estimating the maximum size for a deduplication store, you have to ensure that there is enough space available for dedup trash or the deduplication store will run out of space. You should calculate the required disk space based on the representative sample of your full backup and add the amount of extra space equal to approx. 50% of the representative full backup.</translate>
<!--
<!--
; <translate><!--T:7-->
; <translate><!--T:7-->
Line 52: Line 54:
1 TB free hard disk space</translate> -->
1 TB free hard disk space</translate> -->


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


<!--T:17-->
;Required additional amount of RAM and CPU cores: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-->
{{<translate><!--T:18-->
note</translate>|<translate><!--T:19-->
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>}}
It is not recommended to run Si3 deduplication (SEP sesam Server or RDS) on a virtual machine. If this is the case, like evaluation or test, 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.</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 67: Line 70:
! scope="col" style="width: 20px;" | RAM
! scope="col" style="width: 20px;" | RAM
|-
|-
|   10 TB  || 8 GiB
| <20 TB  || 16 GiB
|-
20 TB  || 13 GiB
|-
|  30 TB  || 18 GiB
|-
|  40 TB  || 22 GiB
|-
|  50 TB  || 22 GiB
|-
|-
|   60 TB   || 22 GiB
| 20-40 TB || 32 GiB
<!--
<!--
   70 TB:  16314M
   70 TB:  16314M
Line 95: Line 90:
-->
-->
|}
|}
;<translate><!--T:21-->
<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.
To find out how much RAM is required by Si3 at which capacity, enter the command ''sm_dedup_interface propose jvmconfig <Si3-CAPACITY>'' at an admin command line (you must set [[FAQ#profile_setting|sesam profile]] to run the command). The ''MaxDirectMemorySize'' output is the required RAM value.
 
<!--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>
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>


Line 113: Line 110:
|-
|-
|  40 TB  ||8
|  40 TB  ||8
|-
 
|  80 TB  ||16
|-
|  160 TB  ||32 or 64
|}
|}


Line 122: Line 116:
note</translate>|<translate><!--T:25-->
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>}}</onlyinclude>
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>}}</onlyinclude>
<div class="noprint"><noinclude>
<noinclude><div class="noprint">
<translate>==See also== <!--T:26-->
<translate>===See also=== <!--T:26-->


<!--T:27-->
<!--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>
[https://www.sep.de/sep-sesam/si3-tachometer-analyze/ SEP Tachometer] – [[Special:MyLanguage/Deduplication|Deduplication]] – [[Special:MyLanguage/4_4_3_Grolar:Configuring_Si3_Deduplication_Store|Configuring an Si3 Deduplication Store]] – [[Special:MyLanguage/SEP_sesam_Requirements|SEP sesam Requirements]] – [[Special:MyLanguage/Licensing|Licensing]]</translate></div></noinclude>

Revision as of 10:21, 11 August 2020

Other languages:

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.

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


Si3 hardware requirements

  • For the minimum Si3 hardware requirements that apply to SEP sesam Si3 deduplication server, see Hardware requirements.
  • 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.
  • When estimating the maximum size for a deduplication store, you have to ensure that there is enough space available for dedup trash or the deduplication store will run out of space. You should calculate the required disk space based on the representative sample of your full backup and add the amount of extra space equal to approx. 50% of the representative full backup.

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. Note that 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.

Required additional amount of RAM and CPU cores

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, like evaluation or test, 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.
Si3 data store capacity (check initial size restriction) RAM
<20 TB 16 GiB
20-40 TB 32 GiB

To find out how much RAM is required by Si3 at which capacity, enter the command sm_dedup_interface propose jvmconfig <Si3-CAPACITY> at an admin command line (you must set sesam profile to run the command). The MaxDirectMemorySize output is the required RAM value.

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
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.