SHA1 chunk hashes check failed error

alexa · 2019-09-25 07:47:38

I get this error: "SHA1 chunk hashes check failed error " when doing a backup on VMware ESXi 6.5.0 with --backup-point set to another Vmware ESXi 6.5.0 via ssh and --certify-backup=yes. xsibackup-pro is installed on both machines. How to troubleshoot this problem?

admin · 2019-09-25 10:27:01

It can be due to many different reasons, we need more detail. Contact support to provide the full log and backup job.

alexa · 2022-04-08 10:30:41

now it floods our hdd, look

-rwx------ 1 root root 18.3K Mar 11 02:37 1646965165-188.117.105.67-config.tgz
-rwx------ 1 root root 18.5K Mar 18 02:37 1647569974-188.117.105.67-config.tgz
-rwx------ 1 root root 18.5K Mar 25 02:37 1648174781-188.117.105.67-config.tgz
-rwx------ 1 root root 18.3K Apr 1 02:39 1648779657-188.117.105.67-config.tgz
-rwx------ 1 root root 18.3K Apr 8 02:39 1649384469-188.117.105.67-config.tgz
drwxr-xr-x 1 root root 72.0K Mar 18 02:28 20220318000006
drwxr-xr-x 1 root root 72.0K Mar 25 02:28 20220325000007
drwxr-xr-x 1 root root 72.0K Apr 1 02:29 20220401000007
drwxr-xr-x 1 root root 72.0K Apr 8 02:29 20220408000007
[root@esxi2:/vmfs/volumes/5d404b0f-df13b95c-7836-2c44fd83e520/vm-backups] df -h ./
Filesystem Size Used Available Use% Mounted on
VMFS-6 1.1T 934.7G 183.1G 84% /vmfs/volumes/datastore2

so, I need fast help, please tell me how to contact support

alexa · 2022-04-08 10:31:41

Also we got this error in the email report:

Fri Apr 1 00:01:32 UTC 2022
XSIBACKUP-PRO 11.2.10 AT HOST:
localhost.localdomain
IP v4: 188.117.105.67/ 255.255.255.248
VMware ESXi 6.5.0 build-8294253

Done hot backup (id: prod) using rsync (no compression)
Backing up to folder 188.117.105.66:22:/vmfs/volumes/datastore2/vm-backups/20220401000007
Mirroring following VMs to 188.117.105.66:22:/vmfs/volumes/datastore2/vm-backups...
(Id)VM Name State Size (Gb) Stop Copy Start Time (min:sec) Speed (mb/s)
(1) firewall-pfsense ON 10.00/ 10.00 NO (hot backup) sha1 CERTIFIED - 04:51 35/ 35
(2) sbc-freepbx ON 30.00/ 30.00 NO (hot backup) sha1 CERTIFIED - 13:49 37/ 37
(3) fusionPBX ON 150.00/ 150.00 NO (hot backup) sha1 CERTIFIED - 69:23 36/ 36
(8) dialer ON 67.81/ 67.81 NO (hot backup) sha1 CERTIFIED - 41:09 28/ 28
(9) stunnel-proxy ON 20.00/ 20.00 NO (hot backup) KO! - 09:49 34/ 34
Last error raised for the above VM:
ERROR CLNCERT0, details: [stunnel-proxy] error: sha1 hashes are different [stunnel-proxy-flat.vmdk], details: 0
--del-dirs | deleted folders older than 22 days:
/vmfs/volumes/datastore2/vm-backups/20220304000007
Complete backup elapsed time: 139 min
The ESXi configuration was saved to 188.117.105.66:22:/vmfs/volumes/datastore2/vm-backups
• [ Fri Apr 1 02:20:39 UTC 2022 ] ERROR (CLNCERT0), details [stunnel-proxy] error: sha1 hashes are different [stunnel-proxy-flat.vmdk], details: 0

admin · 2022-04-10 17:12:36

(c)XSIBackup-Classic has been deprecated.
Your version is not even the latest one available, you should upgrade.
You have not published your job nor the output, just one error.
This does not seem to be an XSITools related error but an Rsync replica related one.
Without all the details on your job and output there is very little that we can do to help you but to make asumptions and offer general advice.

Asuming that this is indeed an Rsync replica and that you have used the --certify-backup option to compare checksums on both ends, you should read this post, it is rather generic and can be used to comprehend how you should interpret a hash mismatch.

Checksum verification and silent corruption

Read it, not only our post but also the study on data corruption and if you still have some doubt reach us back here.

Forum ©XSIBackup: ©VMWare ©ESXi Backup Software

#1 2019-09-25 07:47:38

SHA1 chunk hashes check failed error

#2 2019-09-25 10:27:01

Re: SHA1 chunk hashes check failed error

#3 2022-04-08 10:30:41

Re: SHA1 chunk hashes check failed error

#4 2022-04-08 10:31:41

Re: SHA1 chunk hashes check failed error

#5 2022-04-10 17:12:36

Re: SHA1 chunk hashes check failed error

Board footer