4 4 3 Grolar:Configuring Si3 Deduplication Store
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
- 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.
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 (126.96.36.199). 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.
|It is not supported 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|
|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.|
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 easily configured and ready to use by selecting Si3 deduplication data store type.
- In the Main selection -> Components, click Data stores to display the data store contents frame.
- From the Data stores menu, select New data store. A New data store dialog appears.
- Under the Data store properties in the Name field, enter a meaningful name for the data store.
- From the Store type drop-down list, select SEP Si3 deduplication store.
- Make sure that the option Create drive for data store is checked under the Drive parameter properties. The predefined value for the drive is automatically added to the Drive number field.
- From the Device server drop-down list, select the device server for your data store.
- In the Path field, enter the location for 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 the recommended size values. You can modify your data store size later under the Size properties (see step 10).
- Under the Drive group properties, select Create new drive group and enter the name for your Si3 deduplication store dedicated group.
- 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. The standard license supports 5 concurrent streams, enabling 5 backup processes to run simultaneously. For details on licensing, see Licensing.
- 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 used disk space. When this value is reached, a purge process is triggered for all EOL-free (End-of-lifetime) savesets, thus freeing up the capacity of the data store.
Note In previous versions of SEP sesam (≤ 188.8.131.52 Tigon), the backups were canceled when the high watermark for data store was exceeded. This behaviour has changed with SEP sesam v. ≥ 184.108.40.206 Tigon V2; now, exceeding HWM will isssue a warning, but a running backup operation will be canceled only if there is not sufficient space left.
- 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 if there are any structural problems (may be caused by a file system error or by a crash of an operating system). The files in the repair area will be removed automatically after the specified amount of time (SEP sesam default: 4 days) or when the disk usage threshold is reached. Note that when the value is set to 0, than the Si3 repair functionality is turned off.
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.
- Deduplication rate: deduplication occurs once the backup process has started. SEP sesam analyses blocks of data and determines whether the data is unique or has already been copied to the Si3 data store. Only single instances of unique data are sent to the data store and replace each deduplicated file with a stub file. The deduplication rate is higher when there are copy and full backups and when there is a larger amount of data. The deduplication ratio is depicted as ratio:1.
You can view the properties of your Si3 deduplication by double-clicking relevant 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. To configure Si3 data encryption, you have to create a deduplication security password file. For details, see Encrypting Si3 Deduplication Store.
- You can view the status of your Si3 deduplication by clicking the Si3 State tab. You can check the last deduplication message, status of active tasks, encryption status, number of stored objects, data size before/after deduplication, DedDup ratio, saved storage space, etc.
|If fsck (file system consistency check) detects irregularity in the Si3 file system, the affected pages and chunks are recorded in the recovery.log. The Si3 deduplication store in GUI is marked red and the Si3 purge is no longer executed. The purge is stopped to prevent the files in the Si3 repair area to be deleted as they may be required 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 red and the Si3 purge is working again.|