4 4 3 Grolar:Configuring Si3 Deduplication Store/en: Difference between revisions

From SEPsesam
(Updating to match new version of source page)
(Updating to match new version of source page)
Line 2: Line 2:
{{Copyright SEP AG en}}
{{Copyright SEP AG en}}


{{Navigation_latest|release=[[SEP_sesam_Release_Versions|4.4.3 ''Grolar''/4.4.3 ''Beefalo'']]|link=[[Special:MyLanguage/Si3_Deduplication|documentation archive]]}}</div><br />
{{Navigation_latest|release=[[SEP_sesam_Release_Versions|4.4.3 ''Grolar''/4.4.3 ''Beefalo V2'']]|link=[[Special:MyLanguage/Si3_Deduplication|documentation archive]]}}</div><br />
==Overview==
==Overview==
<div class="boilerplate metadata" id="Additional resources" style="background-color: #f0f0f0; color:#636f73; border: 1px ridge #cdd3db; margin: 0.5em; padding: 0.5em; float: right; width: 35%; "><center><b>
<div class="boilerplate metadata" id="Additional resources" style="background-color: #f0f0f0; color:#636f73; border: 1px ridge #cdd3db; margin: 0.5em; padding: 0.5em; float: right; width: 35%; "><center><b>
Line 49: Line 49:


=={{anchor|steps}}Steps==
=={{anchor|steps}}Steps==
{{Note|As of v. [[SEP sesam Release Versions|4.4.3 ''Beefalo'']], the SEP sesam GUI has been redesigned to be more user-friendly without significantly changing the interface logic, thus your display may vary slightly from what is shown here depending on your [[Special:MyLanguage/SEP_sesam_Release_Versions|SEP sesam version]].}}
   
   
The SEP sesam [[Special:MyLanguage/4_4_3_Beefalo:Data_Store| 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.
The SEP sesam [[Special:MyLanguage/4_4_3_Beefalo:Data_Store|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.
<ol><li>In the '''Main selection''' -> '''Components''', click '''Data stores''' to display the data store contents frame.
<ol><li>In the '''Main selection''' -> '''Components''', click '''Data Stores''' to display the data store contents frame.
<li>From the '''Data stores''' menu, select '''New data store'''. A ''New data store'' dialog appears.</li>
<li>From the ''Data Stores'' menu, select '''New Data Store'''. A ''New Data Store'' dialog appears.</li>
<li>Under the '''Data store''' properties in the '''Name''' field, enter a meaningful name for the data store.</li>
<li>Under the ''Data store'' properties in the '''Name''' field, enter a meaningful name for the Si3 data store.</li>
<li>From the '''Store type''' drop-down list, select '''SEP Si3 deduplication store'''.</li>
<li>From the ''Store type'' drop-down list, select '''SEP Si3 Deduplication Store'''.</li>
[[image:New_Si3_data_store_Grolar.jpg|700px|link=]]
[[image:New_Si3_data_store_Beefalo_V2.jpg|850px|link=]]
<br clear=all>
<br clear=all>
<li>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.</li>
<li>Make sure that the option '''Create drive''' is checked under the ''Drive parameter'' properties. The predefined value for the drive is automatically added to the '''Drive number''' field.</li>
<li>From the '''Device server''' drop-down list, select the '''device server''' for your data store.</li>
It is also recommended that the option '''Create second drive''' is checked. Without it, SEP sesam can only allocate a drive either for reading or writing, running one job at a time on the same drive. By using the additional dedicated drive for restore, you are able to run a backup on the first drive and restore your data from the second drive simultaneously. You can also add a third drive for migration.</li>
<li>Then select '''Create new drive group''' and '''enter the name''' for your Si3 deduplication store dedicated group.</li>
<li>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 [[Special:MyLanguage/Licensing|Licensing]].</li>
<li>From the ''Device server'' drop-down list, select the '''device server''' for your data store.</li>
<li>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'''.
<li>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'''.
<br>
<br>
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).</li>
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).</li>
[[image:GUI_new_data_store_information_Grolar.jpg|500px|link=]]
[[image:GUI_new_data_store_information_Beefalo_V2.jpg|430px|link=]]
<br clear=all>
<br clear=all>
<li>Under the '''Drive group''' properties, select '''Create new drive group''' and '''enter the name''' for your Si3 deduplication store dedicated group.</li>
<li>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 [[Special:MyLanguage/Licensing|Licensing]].</li>
<li>
<li>
Under the '''Size''' properties, specify or modify the following:</li>
Under the '''''Size''''' properties, specify or modify the following:</li>
<ul><li>'''Capacity''': Specify the size (in GIB) of the partition for backups.</li>
<ul><li>'''''Capacity''''': Specify the size (in GiB) of the partition for backups.</li>
<li>'''High watermark''': Specify the value (in GIB) for the high watermark (HWM). The HWM defines the upper value for the used disk space on the data store. 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. The oldest free savesets are deleted first.
<li>'''''High watermark''''': Specify the value (in GiB) for the high watermark (HWM). The HWM defines the upper value for the used disk space on the data store. 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. The oldest free savesets are deleted first.


{{Note|In previous versions of SEP sesam (≤ [[SEP sesam Release Versions|4.4.3.42 ''Tigon'']]), if HWM was set and exceeded, backups could no longer be started while running backups were allowed to finish. Purging is done until the low watermark is reached (if set). This behaviour has changed with SEP sesam v. ≥ [[SEP sesam Release Versions|4.4.3.48 ''Tigon V2'']]; if HWM is set, exceeding it will only issue an information message but will no longer prevent backups to be started.}}</li>
{{Note|In previous versions of SEP sesam (≤ [[SEP sesam Release Versions|4.4.3.42 ''Tigon'']]), if HWM was set and exceeded, backups could no longer be started while running backups were allowed to finish. Purging is done until the low watermark is reached (if set). This behaviour has changed with SEP sesam v. ≥ [[SEP sesam Release Versions|4.4.3.48 ''Tigon V2'']]; if HWM is set, exceeding it will only issue an information message but will no longer prevent backups to be started.}}</li>
<li>'''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.</li></ul>
<li>'''''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.</li></ul>
The '''Disk space usage''' properties are used by SEP sesam to report the following:
The '''Disk space usage''' properties are used by SEP sesam to report the following:
<ul><li>
<ul><li>
'''Used''': Total used space (in GIB) on the partition.
'''''Used''''': Total used space (in GiB) on the partition.
<li>'''Total''': Maximum available space (in GIB) on the partition as reported by the operating system.
<li>'''''Total''''': Maximum available space (in GiB) on the partition as reported by the operating system.
<li>'''Free''': Available disk space (in GIB) for SEP sesam.
<li>'''''Free''''': Available disk space (in GiB) for SEP sesam.
<li>'''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''.</ul></ol>
<!--<li>'''''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''. (Where is it shown?)--></ul></ol>


You can view the properties of your Si3 deduplication by double-clicking relevant Si3 deduplication store.  
You can view the properties of your Si3 deduplication by double-clicking relevant Si3 deduplication store.  
<ul><li>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 [[Special:MyLanguage/Encrypting_Si3_Deduplication_Store|Encrypting Si3 Deduplication Store]].</li>
{{anchor|drive}}<ul><li>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 [[Special:MyLanguage/Encrypting_Si3_Deduplication_Store|Encrypting Si3 Deduplication Store]].<br /> In [[SEP_sesam_Release_Versions|4.4.3 ''Beefalo V2'']], under the tab ''OS Access'' specify the credentials  to access the respective systems. Use <tt>DOMAIN\USER</tt> format for domain accounts or <tt>HOST\USER</tt> for local accounts.</li>
[[image:Si3_drive_properties.jpg|700px|link=]]
[[image:Si3_drive_properties_Beefalo_V2.jpg|800px|link=]]
<br clear=all>
<br clear=all>
<li>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.</li>
<li>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.</li>
[[image:Si3_state_tab.jpg|700px|link=]]
[[image:Si3_state_tab_Beefalo_V2.jpg|830px|link=]]
<br clear=all>
<br clear=all>
</ul>
</ul>
Line 93: Line 92:
{{note|If fsck (file system consistency check) detects irregularity in the Si3 file system, the affected pages and chunks are recorded in the <tt>recovery.log</tt>. The Si3 deduplication store in GUI is marked red and the [[Special:MyLanguage/SEP_sesam_Glossary#Si3_purge|Si3 purge]] is no longer executed. The purge is stopped to prevent the files in the [[Special:MyLanguage/SEP_sesam_Glossary#repair_area|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 <tt>recovery.log</tt> is empty, the Si3 data store is no longer marked red and the Si3 purge is working again.}}
{{note|If fsck (file system consistency check) detects irregularity in the Si3 file system, the affected pages and chunks are recorded in the <tt>recovery.log</tt>. The Si3 deduplication store in GUI is marked red and the [[Special:MyLanguage/SEP_sesam_Glossary#Si3_purge|Si3 purge]] is no longer executed. The purge is stopped to prevent the files in the [[Special:MyLanguage/SEP_sesam_Glossary#repair_area|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 <tt>recovery.log</tt> is empty, the Si3 data store is no longer marked red and the Si3 purge is working again.}}


[[image:Si3_deduplication_store_red.jpg|950px|link=]]
[[image:Si3_deduplication_store_red.jpg|900px|link=]]
<br clear=all>
<br clear=all>


==What is next?==
==What is next?==
After configuring the Si3 deduplication store, configure the [[Special:MyLanguage/Configuring_a_Media_Pool|media pools]] first then set up your [[Special:MyLanguage/The_Backup|backup ]] strategy.
After configuring the Si3 deduplication store, configure the [[Special:MyLanguage/Configuring_a_Media_Pool|media pools]] first then set up your [[Special:MyLanguage/4_4_3_Beefalo:Backup|backup ]] strategy.


<div class="noprint">
<div class="noprint">
== See also ==
== See also ==
[[Special:MyLanguage/4_4_3:Configuring_and_Administering_Si3_Deduplication_Store_by_using_CLI|Configuring and Administering Si3 Deduplication Store by using CLI]] – [[Special:MyLanguage/Encrypting_Si3_Deduplication_Store|Encrypting Si3 Deduplication Store]] – [[Special:MyLanguage/Source_Side_Dedup|Configuring Source-side Deduplication]] – [[Special:MyLanguage/Replication|Replication]] – [[Special:MyLanguage/Seeding_Si3_Deduplication_Store|Seeding Si3 Deduplication Store]] – [https://www.sepsoftware.com/sep-sesam/si3-tachometer-analysis/ SEP Tachometer] – [[Special:MyLanguage/List_of Licenses|List of Licenses]]</div>
[[Special:MyLanguage/4_4_3:Configuring_and_Administering_Si3_Deduplication_Store_by_using_CLI|Configuring and Administering Si3 Deduplication Store by using CLI]] – [[Special:MyLanguage/Encrypting_Si3_Deduplication_Store|Encrypting Si3 Deduplication Store]] – [[Special:MyLanguage/Source_Side_Dedup|Configuring Source-side Deduplication]] – [[Special:MyLanguage/Replication|Replication]] – [[Special:MyLanguage/Seeding_Si3_Deduplication_Store|Seeding Si3 Deduplication Store]] – [https://www.sepsoftware.com/sep-sesam/si3-tachometer-analysis/ SEP Tachometer] – [[Special:MyLanguage/List_of Licenses|List of Licenses]]</div>

Revision as of 08:40, 19 March 2020

Other languages:

Template:Copyright SEP AG en

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


Overview

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.

Prerequisites

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

Steps

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.

  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.
  5. New Si3 data store Beefalo V2.jpg
  6. Make sure that the option Create drive is checked under the Drive parameter properties. The predefined value for the drive is automatically added to the Drive number field.
  7. It is also recommended that the option Create second drive is checked. Without it, SEP sesam can only allocate a drive either for reading or writing, running one job at a time on the same drive. By using the additional dedicated drive for restore, you are able to run a backup on the first drive and restore your data from the second drive simultaneously. You can also add a third drive for migration.
  8. Then select Create new drive group and enter the name for your Si3 deduplication store dedicated group.
  9. 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.
  10. From the Device server drop-down list, select the device server for your data store.
  11. 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).
  12. GUI new data store information Beefalo V2.jpg
  13. 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 disk space on the data store. 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. The oldest free savesets are deleted first.
      Information sign.png Note
      In previous versions of SEP sesam (≤ 4.4.3.42 Tigon), if HWM was set and exceeded, backups could no longer be started while running backups were allowed to finish. Purging is done until the low watermark is reached (if set). This behaviour has changed with SEP sesam v. ≥ 4.4.3.48 Tigon V2; if HWM is set, exceeding it will only issue an information message but will no longer prevent backups to be started.
    • 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.

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.
    In 4.4.3 Beefalo V2, under the tab OS Access specify the credentials to access the respective systems. Use DOMAIN\USER format for domain accounts or HOST\USER for local accounts.
  • Si3 drive properties Beefalo V2.jpg
  • 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.
  • Si3 state tab Beefalo V2.jpg
Information sign.png Note
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.

Si3 deduplication store red.jpg

What is next?

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