Source:Si3 Deduplication Hardware Requirements: Difference between revisions

Revision as of 16:56, 26 April 2022

Other languages:

Deutsch
English

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.

Welcome to the latest SEP sesam documentation version 4.4.3 Beefalo/5.0.0 Jaglion. For previous documentation version(s), check documentation archive.

Additional resources

Check supported configurations and versions and Java compatibility matrix.

Si3 hardware requirements

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.

Restriction

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.

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.

	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.

@@ Line 12: / Line 12: @@
 | rowspan="2" style="padding:0px 10px 0px;" |
 <translate><!--T:3-->
-[[File:SEP_next.png|45px|link=Special:MyLanguage/Configuring_Si3_Deduplication_Store|Configuring an Si3 Deduplication Store]]</translate>
+[[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: [[Special:MyLanguage/Deduplication|Deduplication]] – [[Special:MyLanguage/5_0_0:Configuring_Si3_NG_Deduplication_Store|Configuring Si3 NG Deduplication Store in v. ≥ 5.0.0 Jaglion]] – [[Special:MyLanguage/4_4_3_Grolar:Configuring_Si3_Deduplication_Store|Configuring Si3 Deduplication Store v. ≤ 4.4.3 Beefalo V2]] – [[Special:MyLanguage/SEP_sesam_Requirements|SEP sesam Requirements]] – [[Special:MyLanguage/Licensing|Licensing]] – [https://www.sep.de/sep-sesam/si3-tachometer-analyze/ SEP Tachometer] (only for Si3)</translate>
+See also: [[Special:MyLanguage/Deduplication|Deduplication]] – [[Special:MyLanguage/Configuring_an_Si3_Deduplication_Store|Configuring Si3 Deduplication Store]] – [[Special:MyLanguage/Si3 Deduplication Troubleshooting|Si3 Deduplication Troubleshooting]] – [[Special:MyLanguage/SEP_sesam_Requirements|SEP sesam Requirements]] – [[Special:MyLanguage/Licensing|Licensing]] – [https://www.sep.de/sep-sesam/si3-tachometer-analyze/ SEP Tachometer] (only for Si3)</translate>
 |}
 {|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"
@@ Line 63: / Line 63: @@
 <translate>====Restriction==== <!--T:13-->
-{{anchor|restriction}}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'''.
+{{anchor|restriction}}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].
 <!--T:33-->
@@ Line 69: / Line 69: @@
 {{<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, e.g., during an evaluation or test, you should '''limit the capacity''' of the Si3/Si3-NG data store to '''100 GB''' to ensure normal VM operation. Have in mind that deduplication consumes a lot of server resources for reading, processing, and writing the deduplicated data, so you should be aware of the  limitations when running Si3 on a VM.</translate>}}
+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>====Required additional amount of RAM and CPU cores==== <!--T:17-->
-The following tables show the required '''''additional'' amount of RAM''' and '''CPU cores''' for a Si3/Si3-NG data store. The TB value corresponds to the capacity of the Si3/Si3-NG data store.</translate>
+<!--T:34-->
+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>
 {{<translate><!--T:24-->
 note</translate>|<translate><!--T:25-->
-These requirements relate solely to the need for deduplication. In addition to these requirements, the amount of memory for the operating system and other services should be taken into account.</translate>}}
+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>}}
 {| border="2" cellpadding="4" cellspacing="0" style="width:50%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"
@@ Line 84: / Line 86: @@
 ! scope="col" style="width: 20px;" | RAM
 |-
-|  <20 TB   || 16 GiB
+|  <20 TB   || <translate><!--T:35--> at least 16 GiB</translate>
 |-
-|  20-40 TB || 32 GiB
+|  20-40 TB || <translate><!--T:36--> at least 32 GiB</translate>
 <!--
 TB:   16314M
@@ Line 104: / Line 106: @@
 -->
 |}
-<translate><!--T:21-->
-Depending on the deduplication store used, Si3 or Si3-NG, you can use the following command (from the admin command line) to find out how much RAM is needed at what capacity of Si3/Si3-NG. Note that you need to set the [[FAQ#profile_setting|sesam profile]] to run the command.
-;Si3-NG:Enter the command <code>sm_dedup_interface -T dedup2 propose jvmconfig <Si3-CAPACITY></code>.
-;Si3:Enter the command <code>sm_dedup_interface propose jvmconfig <Si3-CAPACITY></code>. The output of ''MaxDirectMemorySize'' is the required RAM value.
 <!--T:30-->
-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>
+<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;"
@@ Line 118: / Line 116: @@
 ! scope="col" style="width: 20px;" | <translate><!--T:23-->
-CPU cores</translate>
+CPU cores <sup>[[#note|'''Note''']]</sup></translate>
 |-
@@ Line 128: / Line 126: @@
 |}
+<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>
 </onlyinclude>
 <noinclude><div class="noprint">
@@ Line 133: / Line 133: @@
 <!--T:27-->
-[[Special:MyLanguage/Deduplication|Deduplication]] – [[Special:MyLanguage/5_0_0:Configuring_Si3_NG_Deduplication_Store|Configuring Si3 NG Deduplication Store in v. ≥ 5.0.0 Jaglion]] – [[Special:MyLanguage/4_4_3_Grolar:Configuring_Si3_Deduplication_Store|Configuring Si3 Deduplication Store v. ≤ 4.4.3 Beefalo V2]] – [[Special:MyLanguage/SEP_sesam_Requirements|SEP sesam Requirements]] – [[Special:MyLanguage/Licensing|Licensing]] – [https://www.sep.de/sep-sesam/si3-tachometer-analyze/ SEP Tachometer] (only for Si3)</translate></div></noinclude>
+[[Special:MyLanguage/Deduplication|Deduplication]] – [[Special:MyLanguage/Configuring_an_Si3_Deduplication_Store|Configuring Si3 Deduplication Store]] – [[Special:MyLanguage/Si3 Deduplication Troubleshooting|Si3 Deduplication Troubleshooting]] – [[Special:MyLanguage/SEP_sesam_Requirements|SEP sesam Requirements]] – [[Special:MyLanguage/Licensing|Licensing]] – [https://www.sep.de/sep-sesam/si3-tachometer-analyze/ SEP Tachometer] (only for Si3)</translate></div></noinclude>