View source for Source:Troubleshooting Si3 Deduplication

<noinclude><languages /></noinclude>
==Si3 Deduplication==

===<translate><!--T:49--> Failed backups to Si3 data store</translate>===

'''<translate><!--T:50--> Problem</translate>'''

<translate><!--T:51-->
If the system running the SEP sesam Server is suspended and an attached hard disk is hibernated, backups to an Si3 data store located on that disk fail. However, backups to a standard data store may continue to function as expected.

<!--T:52-->
In the log files the following entry may be found:</translate>
 Drive 27:
   14:51:08 Automatic backup 0-01gb-test completed
   14:51:08 553 STOR Failed. error in write_http: Failed to send chunks. Error: {“code”: “UNEXPECTED_SERVER_ERROR”, “message”: “java.io.IOException: The device is not ready”} error in finish_http: Unexpected error on session abort, sid: 103 . Error: {“code”: “SESSION_NOT_FOUND”, “message”: “103”}

'''<translate><!--T:53--> Cause</translate>'''

<translate><!--T:54--> The Si3 data store requires continuous access to the underlying storage system. When the attached hard disk is hibernated or the system is suspended, the storage becomes unavailable.</translate>

&rArr; '''<translate><!--T:55--> Solution</translate>'''

<translate><!--T:56--> Verify that the disk hosting the Si3 datastore is fully operational and accessible. Ensure that the attached hard disk is not set to hibernate and avoid suspending the system during backup operations.</translate>

===<translate><!--T:42-->
Unable to establish connection to S3 data store===

<!--T:43-->
'''Problem'''

<!--T:44-->
Si3 data store may be unable to establish secure connection to S3 storage with the following error:
 Error: Could not access data store. Server Status: 2023-03-30 10:17:10: ERROR Not started due to error: S3 is not connected Server Status: 2023-03-30 10:17:10: ERROR Not started due to error: S3 is not connected

<!--T:45-->
'''Cause'''

<!--T:46-->
In case Si3 data store connects to a storage provider that uses a self-signed certificate, this certificate is not recognized as trustworthy by default because it is not issued by a trusted certificate authority. This can result in connection being denied and log files in {{path|/var/opt/sesam/var/log/sms}} may contain a log message similar to this:</translate>
 [...default-dispatcher-6] [1;31mERROR[0;39m [36mS3[0;39m - Unexpected error: {}, cause: {}
 software.amazon.awssdk.core.exception.SdkClientException: Unable to execute HTTP request: javax.net.ssl.SSLHandshakeException: General OpenSslEngine problem

&rArr; <translate><!--T:47-->
'''Solution'''

<!--T:48-->
To solve this problem use the <tt>keytool</tt> utility to import the <tt>public.crt</tt> certificate to the server certificate store. This will allow the Si3 server to recognize and trust the S3 storage provider's certificate, and establish a secure connection.
#Obtain the public certificate. Note that you can export it from the browser.
#Locate the <tt>cacerts</tt> file on your server. This is the location of your JVM certificate keystore.
#Import the <tt>public.crt</tt> certificate into the JVM's certificate keystore with the following command:
:''on Linux:''
 keytool -import -trustcacerts -keystore /var/lib/ca-certificates/java-cacerts -storepass changeit  -noprompt -alias <storage backend endpoint URL> -file /<path_to_certificate>/public.crt
:''on Windows:''
 C:\Program Files\ojdkbuild\java-11-openjdk-11.0.15-1\bin>keytool -import -trustcacerts -keystore "C:\Program Files\ojdkbuild\java-11-openjdk-11.0.15-1\lib\security\cacerts" -storepass changeit -noprompt -alias <storage backend endpoint URL> -file <path_to_certificate>\public.crt
</translate>

<translate>
===Issues with S3 or S3-compatible storage=== <!--T:34-->

<!--T:39-->
'''Problem'''

<!--T:40-->
*Si3 data store using S3 or S3-compatible storage can experience various issues, depending on cloud storage provider. These issues can affect backups, migrations, and replications. In addition, sanity state check of Si3 could report errors that have similar root cause.

<!--T:35-->
'''Cause'''

<!--T:36-->
*Some cloud storage providers (for example, Wasabi) have request rate restrictions (how many HTTP(S) requests are allowed per second). Also on local storage with S3 option enabled, when multiple RDSs access the same local S3 storage, this can generate a lot of IOPS (I/Os per second).</translate>

&rArr; <translate><!--T:37-->
'''Solution'''

<!--T:38-->
*You can adjust the settings on the affected Si3 data store:
#In the '''Main selection''' -> '''Components''', click '''Data Stores''' to display the data store contents frame.
#Right-click the selected Si3 data store and then click '''Properties'''.
#Double-click a drive to open ''Drive Properties'' dialog, and then in '''Options''' field enter as follows:</translate>
 dedup.s3.timeoutInSeconds=1200,dedup.s3.page.workers=2,dedup.maxAsyncRequests=50
:<translate><!--T:41--> This will increase the timeout period, active page workers and request rate.</translate>

<translate>=== Si3 remains in "shutting down" state === <!--T:22-->

<!--T:23-->
'''Problem'''
* Manually stopping ''Garbage Collection'' (GC) fails and consequently Si3 remains in the "shutting down" state.</translate>

&rArr; <translate><!--T:24--> '''Solution'''</translate>
*<translate><!--T:25--> Restart the Si3 daemon by using <tt>sm_main restart sds</tt>. For more details on stopping and starting the SEP sesam services, see [[Special:MyLanguage/How_to_Start_and_Stop_SEP_sesam|How to Start and Stop SEP sesam]].</translate>

==={{anchor|NFS}}<translate><!--T:26-->
Si3 deduplication may not work with NFSv4=== 

<!--T:27-->
'''Problem'''
*Si3 deduplication may not work with ''Network File System version 4'' (''NFSv4'').

<!--T:28-->
'''Cause'''
*SEP sesam operations, such as backup, restore and migration, may fail due to Java problems with ''NFSv4''.</translate>

&rArr; <translate><!--T:29--> '''Solution'''</translate>
*<translate><!--T:30--> To avoid this problem, connect your backup devices via ''NFSv3''.</translate>

<translate>=== Repairing corrupted Si3 NG data store === <!--T:31-->

<!--T:33-->
{{Source:Administering_Si3_NG_Deduplication_Store/Repairing_corrupted_Si3_NG_data_store}}</translate>

<noinclude>{{Copyright}}</noinclude>