Copyright © SEP AG 1999-2022. 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.
Repairing Si3 deduplication store
- There are problems with my Si3 deduplication store.
Repair the Si3 deduplication store as follows:
- Update the SEP sesam Server (where the Si3 runs) to the latest version, see Updating SEP sesam.
- Check the recovery log (in the Si3 root directory). If only one, two or three savesets are shown, check whether they have been deleted (purged) due to the expired EOL. If this is the case, delete the entire contents of recovery.log (but do not delete the file!). In a few seconds, the Si3 status should be changed to OK ; in the GUI and in the Web UI, the Si3 store will change from red to black. In this case the problem is solved. However, see also next step.
- If there are many entries in recovery.log, you have to use the repair command.
- Check if gc or fsck is running (
sm_dedup_interface -d <Si3_drive> status). If they are, stop them with the command
sm_dedup_interface -d <Si3_drive> gc stop and fsck stop
- Check again if 'gc or fsck are stopped (note that fsck can restart quickly).
- Start the quick repair; this only works if there are ddl files in
sm_dedup_interface -d <Si3_drive> repair start asc quick <si3-root-dir>/trash/data
- Use sm_dedup_interface -d <Si3_drive> repair start asc quick <si3-root-dir>/trash/data
- If the sanity state is not OK, use sm_dedup_interface -d <Si3_drive> repair start asc quick <si3-root-dir>/data/lostnfound
- If the sanity state is still not OK, use sm_dedup_interface -d <Si3drive> repair start asc quick <si3-root-dir>/data
- Check that the repair works: sm_dedup_interface -d <Si3_drive> status The following line confirms that it works: … GC: 0 FSCK: 0, Repair: 1
- Wait a few minutes. Check the repair with dedup-status. Once the repair is complete, the Si3 state should change to OK. If not, use FULL instead of QUICK repair. Have in mind that this can be quite time-consuming.
Si3 remains in "shutting down" state
- Manually stopping Garbage Collection (GC) fails and consequently Si3 remains in the "shutting down" state.
- Restart the Si3 daemon by using sm_main restart sds. For more details on stopping and starting the SEP sesam services, see How to Start and Stop SEP sesam.
Si3 deduplication may not work with NFSv4
- Si3 deduplication may not work with Network File System version 4 (NFSv4).
- SEP sesam operations, such as backup, restore and migration, may fail due to Java problems with NFSv4.
- To avoid this problem, connect your backup devices via NFSv3.
This is the main utility for configuring and managing data stores. Below is a list of some commands and their usage.
|Depending on the deduplication store used, Si3 or Si3-NG, some of the commands may be slightly different. When relevant, both command versions are described.|
sm_dedup_interface -d <datastore> <command>
- purge - objectinfo <remote filename> - put <input filename> <dest filename> - get <remote filename> <dest filename> [<bytes skipped then> [<bytes read at beginning>]] - delete <remote filename> [<filename 2>]* - getlabel - getuuid - list - fsck [start|stop|autopurge|status|incremental|purge now|dump status into <file>|fsck incr start from <file>] - gc <start|stop|status|result> - key <set <key> <value>|get <key>|list> - log@server <msg> - propose serverconfig <repository netto GiB> - propose jvmconfig <repository netto Gib> (for Si3 store; slightly different usage for Si3 NG, see Notea) - snapshot - replicate from [-f] <remote hostname> <remote port> <remote filename> - replicate show - replicate abort <task id>
Depending on the deduplication store used, Si3 or Si3-NG, the command to find out how much RAM is needed at what capacity of Si3/Si3-NG differs slightly. Example:
- Use the command
sm_dedup_interface -T dedup2 propose jvmconfig <Si3_capacity>.
- Use the command
sm_dedup_interface propose jvmconfig <Si3_capacity>.
The output of MaxDirectMemorySize is the required RAM value.
Note, however, that SEP sesam calculates the RAM consumption and uses these commands in the background. It is usually not needed to set the values manually. These manual changes are overwritten with the next drive configuration.
The index calculation is also associated with the command. If the index grows and is 95% full, backups can no longer be performed. The RAM must hold the entire index (described by max_pages) in memory. The MaxDirectMemorySize depends directly on max_pages. To solve the problems with the growing index, refer to Si3 Deduplication Troubleshooting.
Most of the parameters are for internal use only.
Provides information about used space, stored data, label uuid and running processes (gc or fsck), etc.
sm_dedup_interface -d ds1_2 status INFO Successfully initialized i2dedup library version v2.1.0-SNAPSHOT5 Server Status: Repository information: Version: 2.1.1 UUID: 3b9ec2ae-34e1-11e3-b88b-001b2146 Label: ds1 Max Pages: 481900 Max Pages recommended: 154100 (-Xmx1010M -XX:MaxDirectMemorySize=603M) GC process status: not running: GC finished. Fsck process status: not running: Fsck finished. Interrupted: false. Total Runtime: 1296.68s Bytes in repository: 259.02 GB Bytes delete pending: 9.18 GB Object information: Objects stored: 258 Data before deduplication: 1541.56 GB Data after deduplication: 58.94 GB Overall DeDup ratio: 96.18 % Key-Values: No keys stored.
sm_dedup_interface -d 3 status Server Status: Repository information: 2022-03-07 16:01:31 Start time: 2022-02-22 16:32:15 Server: localhost:11704 Path: /srv/single_disk/Si3-NG-b11 Version: Version: Si3-NG Branch: 4321a7ba7bafbfb7e9a186a3821b0e0bf08d19bc Build: 4321a7b Commit: 2022-02-09 15:37:49 Build date: 2022-02-09 15:41:18 UUID: 5e999930-bd3f-11ea-8471-b79d351122df Label: Si3-NG-b11 PCCK process status: not running: No items found to process: Stop time: 2022-03-07 16:00:48 (Started: 2022-03-07 16:00:48) OCCK process status: not running: No items found to process: Stop time: 2022-03-07 16:00:47 (Started: 2022-03-07 16:00:47) GC process status: not running: Sweep Phase: swept 97124/97124 pages [deleted=2194,rewritten=13611,skipped=79550,locked=1769,missing=0]: Stop time: 2022-03-07 10:00:15 (Started: 2022-03-07 08:10:56) Bytes in repository: 534.49 GiB Bytes delete pending: 159.60 GiB Pages dir size: 534.42 GiB Object dir size: 0.45 GiB Trash dirs size: 159.60 GiB Active tasks: All: 0, Backup: 0, Restore: 0, GC: 0, OCCK: 0, PCCK: 0 Sanity state: OK JVM arguments: -Xmx3335M, -Dlogback.configurationFile=/var/opt/sesam/var/ini/sm_sdslog2.xml, -Dgv_rw_stpd=/var/opt/sesam/var/log/sms, -Dlogs.dir=/var/opt/sesam/var/log/sms, -Ddrive_num=3, -Dconfig.inifile=/var/opt/sesam/var/ini/stpd_conf/Si3-NG-b11_3.ini Recommended JVM arguments: -Xmx3312M Si3-storage: Bytes All: 1999421108224, Use: 736072216576, Free: 1263348891648, Used: 36% Index information: Size: 0.34 GiB Utilization: 57.35% (32890421/57344000) Reindex: - Object information: Objects stored: 36090 Data before deduplication: 10.66 TiB Overall DeDup ratio: 1 / 20.32 Saved storage space: 95.08 % S3 information: State: OFF Bucket:
The value Overall dedup ratio shows by how many percent the stored data has been reduced.
- gc start
- Starts the garbage collection.
- Identifies unreferenced chunks and moves them to the trash.
- Is started by SEP sesam with sm_start.
- gc stop
- Stops the garbage collection.
- Can be restarted later.
- gc status
- Si3 NG gc status output example
sm_dedup_interface -d 3 gc status Current gc status: State: Finished Started: 2022-03-07 08:10:56 Ended: 2022-03-07 10:00:15 Message: Sweep Phase: swept 97124/97124 pages [deleted=2194,rewritten=13611,skipped=79550,locked=1769,missing=0] STATUS=SUCCESS MSG=Sweep Phase: swept 97124/97124 pages [deleted=2194,rewritten=13611,skipped=79550,locked=1769,missing=0]
- Reads an object (file, saveset) from the deduplication store.
- '-' can be used to specify STDIN.
- Writes an object (file, saveset) to the deduplication store.
- '-' can be used to specify STDOUT.
- Starts a data store check.
- Must be started manually.
- If the parameter autopurge is set, all corrupted objects are deleted.
- fsck status
- Displays the current state or the state of the most recent data store check.
The Si3 NG deduplication store has two types of fsck: object check (occk), which checks if the Si3 data part is still readable, and page check (pcck), which checks the physical data on the disk. All processes (gc, occk and pcck) can run simultaneously.
si3fix:/var/opt/sesam/var/log/sms # sm_dedup_interface -d Si3_5 fsck status INFO Successfully initialized i2dedup library version v2.0.0-beta2 Current fsck status: Message: Logfile check progress: Bytes: 1270925865083/1512422546049 Throughput: 91.25 MiB/s Running: yes Started: 2018-05-29 20:57:17 Ended: - Bytes Checked: 0 Bytes Lost: 0 Objects checked:
sm_dedup_interface -d 3 fsck status Current occk status: Mode: Incremental. Since 2022-03-07 09:18:25 State: Finished Started: 2022-03-07 16:01:53 Ended: 2022-03-07 16:01:53 Last Full successful: 2022-01-04 10:41:20 Message: No items found to process Previous error: - Current pcck status: Mode: Incremental. Since 2022-03-07 09:58:48 State: Finished Started: 2022-03-07 16:01:53 Ended: 2022-03-07 16:01:53 Last Full successful: 2022-01-04 11:58:25 Message: No items found to process Previous error: -
- Deletes all pages marked as obsolete (empty trash) by the last run of garbage collection (gc).
- Is started by sm_start after a SEP sesam day change.
- getlabel and getuuid can be replaced with status