4 4 3 Grolar:Configuring Si3 Deduplication Store

From SEPsesam
Other languages:

Template:Copyright SEP AG en

This is not the latest version of SEP sesam documentation and, as such, does not provide information on features introduced in the latest release. For more information on SEP sesam releases, see SEP sesam Release Versions. For the latest documentation, check Configuring Si3 NG Deduplication Store.

Information about deduplication store types

SEP sesam v. 5.0.0 Jaglion has introduced a new generation Si3 deduplication store: Si3 NG. The Si3-related information differs slightly depending on which datastore is used: Si3 or Si3 NG. The procedures presented in this article apply only to the older type of SEP Si3 deduplication store, which is deprecated. To learn more about the new generation of Si3 NG, see Configuring Si3 NG Deduplication Store.

It is strongly recommended to use the newer type SEP Si3 NG deduplication store. It offers significantly higher performance for backup, restore and migration, as well as backup to S3 and backup to Azure, the new immutable storage feature SiS, resulting in improved performance, scaling, and resource savings. For details, see the Si3 and Si3 NG comparison section below.
To learn how to upgrade from Si3 to Si3 NG by configuring a new Si3 NG on the same host and creating a replication job to replicate from Si3 to Si3 NG, see Configuring Si3 NG Deduplication Store.

Deprecated Si3 data store

The old generation Si3 deduplication store is deprecated. This means that the old generation Si3 is no longer being enhanced, but is still supported until further notice. SEP strongly recommends using the new Si3 NG data store instead, especially if the data is to be stored to S3 Cloud.

  • If you are using an old generation Si3 deduplication store with S3, you will not be able to restore from S3 via the GUI.
  • You can configure a new Si3 NG and an old Si3 in parallel on the same host and replicate from the old Si3 to the Si3 NG store. For details, see Configuring Si3 NG Deduplication Store.


SEP sesam provides a target-based (Si3T) and source-based deduplication (Si3S). For details on deduplication concept and recommendations, see Deduplication.

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. Note that you can also configure an Si3 deduplication store by using a command line. For details, see Configuring and Administering Si3 Deduplication Store by using CLI.

You can download SEP Tachometer to analyse the structure of your data and calculate potential savings with SEP sesam Si3 deduplication. Check SEP Tachometer.


For the minimum Si3 hardware requirements that apply to SEP sesam Si3 deduplication server, see Hardware requirements. 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.

In addition, the following prerequisites must be met to configure an Si3 deduplication store.

Additional RAM / CPU requirements

Si3 Deduplication Hardware Requirements/en


The SEP sesam data store is a disk based storage that enables savesets (backed-up data) to be backed up directly to the configured storage locations. SEP Si3 target deduplication is easy to configure and ready to use by selecting the Si3 deduplication store type.

  1. In the Main selection -> Components, click Data Stores to display the data store contents frame.
  2. From the Data Stores menu, select New Data Store. A New Data Store dialog appears.
  3. Under the Data store properties in the Name field, enter a meaningful name for the Si3 data store.
  4. From the Store type drop-down list, select SEP Si3 Deduplication Store.
    As of SEP sesam v. 5.0.0 Jaglion, two Si3 data store types are available. SEP sesam recommends using the new generation Si3 NG when creating a new data store. To learn how to upgrade from Si3 to Si3 NG by configuring a new Si3 NG on the same host and creating a replication job to replicate from Si3 to Si3 NG, see Configuring Si3 NG Deduplication Store.

  5. Make sure that the option Create drive is checked under the Drive parameter properties. The predefined value for the drive is automatically inserted in the Drive number field.
  6. It is recommended that the option Create second drive is also enabled. Without it, SEP sesam can only allocate a drive for either reading or writing, running one job on the same drive at a time. By using the additional dedicated drive for restore, you can perform a backup on the first drive and restore your data from the second drive simultaneously. You can also add a third drive for migration.
  7. Then select Create new drive group and enter the name for your Si3 deduplication store dedicated group.
  8. The predefined number of channels is already displayed in the Max. channels drop-down list. The number of available channels depends on your SEP sesam Server package. For details on licensing, see Licensing.
  9. From the Device server drop-down list, select the device server for your data store.
  10. In the Path field, enter the location of your data store or use the Browse button to select the relevant folder. Check the relevant folder and click OK.
    When using the Browse button to select the folder, the New Data Store information window appears with predefined recommended values for your Si3 deduplication store size. Click OK to confirm the selected location and recommended size values. You can modify your data store size later under the Size properties (see step 10).

  11. Under the Size properties, specify or modify the following:
    • Capacity: Specify the size (in GiB) of the partition for backups.
    • High watermark: Specify the value (in GiB) for the high watermark (HWM). The HWM defines the upper value for the used storage space. When this value is reached, the status of a datastore changes from OK to Warning, but backups continue to be performed. Make sure that you provide enough storage space for your backed up data.
    • Si3 repair area: Specify the value (in GiB) for the Si3 repair area. The Si3 repair area (subdirectory trash) defines space for Si3 files (DDLs) that were identified by a garbage collection job and are no longer used. These files are still kept in the repair area to enable possible repair of Si3 in case of structural problems (which may be caused by a file system error or an operating system crash)). The files in the repair area are automatically removed after the specified period of time (SEP sesam default: 4 days) or when or when the disk usage threshold is reached. Note that the Si3 repair function is disabled when the value is set to 0.
    • Note
      The Si3 repair area for managing disk space dedicated to Si3 files (DDLs) is only available in the Expert UI mode. So if you run the GUI in Basic or Advanced UI mode, you first have to change the mode to Expert, as described in Selecting UI mode.

    The Disk space usage properties are used by SEP sesam to report the following:

    • Used: Total used space (in GiB) on the partition.
    • Total: Maximum available space (in GiB) on the partition as reported by the operating system.
    • Free: Available disk space (in GiB) for SEP sesam.

You can view the properties of your Si3 deduplication by double-clicking the corresponding Si3 deduplication store.

  • You can modify existing and set additional drive options by double-clicking the first drive. In the Drive Properties window, you can browse the path for the data store, set the access mode for data store drives, etc. To configure Si3 data encryption, you have to create a deduplication security password file. For details, see Encrypting Si3 Deduplication Store.
    Use the tab OS Access and specify the credentials to access the respective systems. Use DOMAIN\USER format for domain accounts or HOST\USER for local accounts.

Monitoring deduplication status

You can view the status of your Si3 deduplication in the GUI by clicking the Si3 State tab. You can check the last deduplication message, the status of active tasks, the encryption status, the number of stored objects, the data size before/after deduplication, the dedup ratio, the saved storage space, etc.

You can also check the status in SEP sesam Web UI. You can use the Dependencies tab to see the diagram of all dependencies of the datastore and drives, RDS, media pools, etc., and use other tabs to check the details of the data store operation.
If fsck (file system consistency check) detects an irregularity in the Si3 file system, the affected pages and chunks are recorded in recovery.log. The Si3 deduplication store in the GUI and Web UIis highlighted in red and Si3 purge is no longer executed. The purge is stopped to prevent the files in the Si3 repair area from being deleted, as they may be needed to repair Si3 in case of problems. Once the errors are fixed and the recovery.log is empty, the Si3 data store is no longer marked in red and the Si3 purge works again.

What is next?

After configuring the Si3 deduplication store, configure the media pools first then set up your backup strategy.

Comparison of Si3 and Si3 NG

SEP sesam v. 5.0.0 Jaglion has introduced a new generation Si3 deduplication store. Si3 offers significantly higher performance for backup, restore and migration, as well as backup to S3 cloud and backup to Azure, the new immutable storage feature SiS, resulting in improved performance, scaling, and resource savings.

Function Si3 Si3 NG
Si3 backup YesY YesY
Si3 deduplication (source-side and target-side) YesY YesY
Si3 replication: local to remote store Notea YesY Si3 V1 to Si3 V1 YesY Si3 V1 to Si3; Si3 to Si3
Si3 replication: to S3 cloud YesY NoN (provides more powerful features for backing up directly to the cloud, see the next two lines)
Backup to S3 Cloud Storage NoN YesY
Backup to Azure Storage NoN YesY (as of Jaglion V2)
SiS (SEP Immutable Storage) NoN YesY (as of Jaglion V2)
Si3 restore YesY YesY
Si3 encryption YesY YesY (as of Jaglion V2)
Seeding Si3 deduplication store Noteb YesY NoN
Usage of tachometer YesY NoN

SEP sesam does not support a direct upgrade from the Si3 V1 to new Si3. However, to use the new Si3 you can:

  • Back up all data again to the newly configured Si3 deduplication store.
  • After configuring a new Si3, you can also create a replication job to replicate from the Si3 V1 to the Si3 store. Replication reads all the data from the source-side store on the source-side RDS and sends it to the target store using the source-side deduplication function. For details, see Replicating from Si3 V1 to Si3.
  • You can also configure a new Si3 and an old Si3 V1 in parallel on the same host by enabling the key enable_gui_allow_multi_dedup.

The Initial Seed feature does not work in v. 5.0.0 Jaglion, but you can use it in earlier SEP sesam versions.