#1 2018-02-23 15:02:22

tschonn
Member
Registered: 2018-01-03
Posts: 22

sha1 hashes are different

Hello,

I just can't figure it out - I'm backing up 8 VMs - and on two of them I always get the error "ERROR (DIFCERT0)" "sha1 hashes are different".
It's no difference if from crontab or manually on command line.

"/vmfs/volumes/datastore1/xsi-dir/xsibackup" --host=192.168.100.6 --backup-point="192.168.100.16:22:/vmfs/volumes/datastore1/backup" --backup-type=custom --backup-vms="Tschonn-BH,Tschonn-VPC10,Tschonn-VPC7,Tschonnnb,TschonnS16Std" --backup-prog=onediff --debug-info=yes --certify-backup=yes 

In the log file (I could send the whole file via mail if of use) there are those entries (among may others ...):

2018-02-22T20:00:43|  [Tschonn-VPC10] info: file [Tschonn-VPC10_0-flat.vmdk]...
2018-02-22T20:00:43|  [Tschonn-VPC10] info: file size check | OK [ 214748364800 bytes | 214748364800 bytes ]
---------------------------------------------------------------------------------------------------------------------------------
2018-02-22T20:00:44|  [Tschonn-VPC10] info: remote VMX file size 3557
---------------------------------------------------------------------------------------------------------------------------------
2018-02-22T20:00:44|  System disk CIDs 924f251d|924f251d
---------------------------------------------------------------------------------------------------------------------------------
2018-02-22T20:00:44|  [Tschonn-VPC10] (c) OneDiff algorithm
---------------------------------------------------------------------------------------------------------------------------------
2018-02-22T20:00:44|  Mirror VM exists and the system disks CID are the same, starting OneDiff...

2018-02-22T20:06:30|  [Tschonn-VPC10] info: Updating CID at [192.168.100.16:22:/vmfs/volumes/datastore1/backup/Tschonn-VPC10/Tschonn-VPC10_0.vmdk]
2018-02-22T20:06:31|  [Tschonn-VPC10] info: finished OneDiff backup, CID updated
---------------------------------------------------------------------------------------------------------------------------------
2018-02-22T20:06:31|  [Tschonn-VPC10] info: certifying backup by means of sha1 algorithm...
---------------------------------------------------------------------------------------------------------------------------------
2018-02-22T20:06:31|  [Tschonn-VPC10] info: computing hashes for [Tschonn-VPC10_0-flat.vmdk]...
---------------------------------------------------------------------------------------------------------------------------------
2018-02-22T20:27:42|  [Tschonn-VPC10] info: sha1 hash is 04ff48a6b6f76dd50781cc098abfaa2bcba93e14
---------------------------------------------------------------------------------------------------------------------------------
2018-02-22T20:27:42|  [Tschonn-VPC10] error: sha1 hashes are different [Tschonn-VPC10_0-flat.vmdk]
---------------------------------------------------------------------------------------------------------------------------------
2018-02-22T20:27:42|  [Tschonn-VPC10] measure DIFRMVMX: took measure, renamed remote .vmx file to reinitialize OneDiff

Same for the VM named TschonnS16Std ... the others run without problems ...
I already deleted the backed up machines on the target ESXi (from inventory AND then directories), but nothing changed (of course except a longer runtime on first backup)

Help!
Thanx :-)

Offline

#2 2018-02-24 00:16:31

tschonn
Member
Registered: 2018-01-03
Posts: 22

Re: sha1 hashes are different

I didn't change the crontab, and today - like any of the past days - the same two VMs weren't backed up, but today I got additional errors "segmentation fault" in the log that had not been here yesterday. So I went back in the logfile and realized that it hasn't been the first time for these "segmentation faults", but not every day. As always - the other VMs on the host are fine ...

What could be the reason, how can I fix it?
I already rebooted both hosts some days ago - to no avail.


2018-02-23T20:15:41|  ###############################################################################
2018-02-23T20:15:41|     XSIBACKUP-PRO 10.2.9: new execution request                     
2018-02-23T20:15:41|  ###############################################################################
2018-02-23T20:15:41|  
2018-02-23T20:15:41|  NOTICE: (c) XSIBackup will kill any previous processes, make sure you don't overlap backup jobs
---------------------------------------------------------------------------------------------------------------------------------
XSIBackup PID:           329622                                  ESXiT310.schwarzenberger.local
Fri, 23 Feb 2018 20:15:41 +0000                               IPv4: 192.168.100.6/255.255.255.0
VMware ESXi 6.0.0 build-5050593                              (c) Rsync 3.1.0 as opt. dependency
---------------------------------------------------------------------------------------------------------------------------------
Backup Id:                   11                 Intel(R) Xeon(R) CPU           X3440  @ 2.53GHz 
---------------------------------------------------------------------------------------------------------------------------------
2018-02-23T20:15:43|  ADVICE: no SSD disks, please consider adding an SSD cache disk to improve performance
---------------------------------------------------------------------------------------------------------------------------------
2018-02-23T20:15:43|  Backup user is: root
---------------------------------------------------------------------------------------------------------------------------------
2018-02-23T20:15:43|  Backup program is: onediff
---------------------------------------------------------------------------------------------------------------------------------
2018-02-23T20:15:43|  Service OpenSSH ready at server 192.168.100.16:22
---------------------------------------------------------------------------------------------------------------------------------
2018-02-23T20:15:43|  Info: XSIBACKUP-PRO will now try to determine the remote's XSIBACKUP-PRO installation point...
2018-02-23T20:15:43|  Tip: should this process take too long, use the --remote-xsipath argument to set it
---------------------------------------------------------------------------------------------------------------------------------
2018-02-23T20:15:50|  Found (c) XSIBackup installation. Remote path is set dynamically
---------------------------------------------------------------------------------------------------------------------------------
2018-02-23T20:15:51|  Remote xsi path set to: /vmfs/volumes/5a47a3a2-56dcdeb4-627a-0026b94bd274/xsi-dir (filesystem: VMFS-5)
---------------------------------------------------------------------------------------------------------------------------------
2018-02-23T20:15:52|  Remote ESXi version is 6.0.0
---------------------------------------------------------------------------------------------------------------------------------
2018-02-23T20:15:52|  Mirroring to server 192.168.100.16 port 22
2018-02-23T20:15:52|  Checking Rsync exists on the other side...
---------------------------------------------------------------------------------------------------------------------------------
2018-02-23T20:15:53|  (c) Rsync (samba.org) found at [ 192.168.100.16:22:/vmfs/volumes/5a47a3a2-56dcdeb4-627a-0026b94bd27... ]
---------------------------------------------------------------------------------------------------------------------------------
2018-02-23T20:15:53|  (c) XSIDiff found at [ 192.168.100.16:22:/vmfs/volumes/5a47a3a2-56dcdeb4-627a-0026b94bd274/xsi-dir/... ]
2018-02-23T20:18:50|  Info: transfering file | /vmfs/volumes/datastore1/Tschonn-VPC10/Tschonn-VPC10_0-flat.vmdk
---------------------------------------------------------------------------------------------------------------------------------
2018-02-23T20:18:52|  [Tschonn-VPC10] CLXSIDF1 error: file transfer error: Segmentation fault
2018-02-23T20:18:52|  packet_write_wait: Connection to 192.168.100.16 port 22: Broken pipe
2018-02-23T20:28:07|  Info: transfering file | /vmfs/volumes/datastore1/TschonnServer2016Std/TschonnS16Std_2-flat.vmdk
---------------------------------------------------------------------------------------------------------------------------------
2018-02-23T20:28:14|  [TschonnS16Std] CLXSIDF1 error: file transfer error: Segmentation fault
2018-02-23T20:28:14|  Segmentation fault
2018-02-23T20:28:18|  Info: transfering file | /vmfs/volumes/datastore1/TschonnServer2016Std/TschonnServer2016Std_0-flat.vmdk
---------------------------------------------------------------------------------------------------------------------------------
2018-02-23T20:28:20|  [TschonnS16Std] CLXSIDF1 error: file transfer error: Segmentation fault

Offline

#3 2018-02-25 17:05:19

admin
Administrator
Registered: 2017-04-21
Posts: 1,366

Re: sha1 hashes are different

The key to your problem is on some other errors in your log:

packet_write_wait: Connection to 192.168.100.16 port 22: Broken pipe

This is self explanatory. The reason why it's always the same VMs that fail could be in some timely issue.
Split your backups into two and treat those two VMs in a different backup job. Try to back them up manually and see if you still get those errors. Try to find out if there is some automated job that brings the backup link down at the communications layer.

Offline

#4 2018-02-26 09:47:42

tschonn
Member
Registered: 2018-01-03
Posts: 22

Re: sha1 hashes are different

Yes, but the broken pipe seems not to be the cause but the result, because its always within a few seconds after a line like "Info: transfering file"

---------------------------------------------------------------------------------------------------------------------------------
2018-02-25T13:50:04|  Info: transfering file | /vmfs/volumes/datastore1/Tschonn-VPC10/Tschonn-VPC10_0-flat.vmdk
---------------------------------------------------------------------------------------------------------------------------------
2018-02-25T13:50:06|  [Tschonn-VPC10] CLXSIDF1 error: file transfer error: Segmentation fault
2018-02-25T13:50:06|  packet_write_wait: Connection to 192.168.100.16 port 22: Broken pipe

So I tried to backup only one VM in one line manually from command line:

"/vmfs/volumes/datastore1/xsi-dir/xsibackup" backupId=11 --host=192.168.100.6 --backup-point="192.168.100.16:22:/vmfs/volumes/datastore1/backup" --backup-type=custom --backup-vms="Tschonn-VPC10" --backup-prog=onediff --debug-info=yes --certify-backup=yes

... but what is that - why is it using XSIDiff now (scroll down to the end) ... as I can read in the log file it never did before. The command reads "... --backup-prog=onediff ...":

2018-02-26T00:22:26|  ###############################################################################
2018-02-26T00:22:26|     XSIBACKUP-PRO 10.2.9: new execution request                     
2018-02-26T00:22:26|  ###############################################################################
2018-02-26T00:22:26|  
2018-02-26T00:22:27|  NOTICE: (c) XSIBackup will kill any previous processes, make sure you don't overlap backup jobs
---------------------------------------------------------------------------------------------------------------------------------
XSIBackup PID:           146396                                  ESXiT310.schwarzenberger.local
Mon, 26 Feb 2018 00:22:26 +0000                               IPv4: 192.168.100.6/255.255.255.0
VMware ESXi 6.0.0 build-5050593                              (c) Rsync 3.1.0 as opt. dependency
---------------------------------------------------------------------------------------------------------------------------------
Backup Id:                   11                 Intel(R) Xeon(R) CPU           X3440  @ 2.53GHz 
---------------------------------------------------------------------------------------------------------------------------------
2018-02-26T00:22:29|  ADVICE: no SSD disks, please consider adding an SSD cache disk to improve performance
---------------------------------------------------------------------------------------------------------------------------------
2018-02-26T00:22:29|  Backup user is: root
---------------------------------------------------------------------------------------------------------------------------------
2018-02-26T00:22:29|  Backup program is: onediff
---------------------------------------------------------------------------------------------------------------------------------
2018-02-26T00:22:29|  Service OpenSSH ready at server 192.168.100.16:22
---------------------------------------------------------------------------------------------------------------------------------
2018-02-26T00:22:29|  Info: XSIBACKUP-PRO will now try to determine the remote's XSIBACKUP-PRO installation point...
2018-02-26T00:22:29|  Tip: should this process take too long, use the --remote-xsipath argument to set it
---------------------------------------------------------------------------------------------------------------------------------
2018-02-26T00:22:31|  Found (c) XSIBackup installation. Remote path is set dynamically
---------------------------------------------------------------------------------------------------------------------------------
2018-02-26T00:22:32|  Remote xsi path set to: /vmfs/volumes/5a47a3a2-56dcdeb4-627a-0026b94bd274/xsi-dir (filesystem: VMFS-5)
---------------------------------------------------------------------------------------------------------------------------------
2018-02-26T00:22:33|  Remote ESXi version is 6.0.0
---------------------------------------------------------------------------------------------------------------------------------
2018-02-26T00:22:33|  Mirroring to server 192.168.100.16 port 22
2018-02-26T00:22:33|  Checking Rsync exists on the other side...
---------------------------------------------------------------------------------------------------------------------------------
2018-02-26T00:22:34|  (c) Rsync (samba.org) found at [ 192.168.100.16:22:/vmfs/volumes/5a47a3a2-56dcdeb4-627a-0026b94bd27... ]
---------------------------------------------------------------------------------------------------------------------------------
2018-02-26T00:22:34|  (c) XSIDiff found at [ 192.168.100.16:22:/vmfs/volumes/5a47a3a2-56dcdeb4-627a-0026b94bd274/xsi-dir/... ]
---------------------------------------------------------------------------------------------------------------------------------
2018-02-26T00:22:35|  Getting list of all VMs...
---------------------------------------------------------------------------------------------------------------------------------
2018-02-26T00:22:35|  10     Tschonn-VPC10                                             [datastore1] Tschonn-VPC10/Tschonn-VPC10.vmx                                                                                windows9_64Guest        vmx-11               
2018-02-26T00:22:36|  2      TschonnS16Ess                                             [datastore1] TschonnServer16Ess/TschonnServer16Ess.vmx                                                                      windows9Server64Guest   vmx-11               
2018-02-26T00:22:37|  3      TschonnS16Std                                             [datastore1] TschonnServer2016Std/TschonnServer2016Std.vmx                                                                  windows9Server64Guest   vmx-11               
2018-02-26T00:22:38|  4      Tschonn-VPC7                                              [datastore1] Tschonn-VPC7/Tschonn-VPC7.vmx                                                                                  windows7_64Guest        vmx-11               
2018-02-26T00:22:39|  5      Tschonn-BH                                                [datastore1] Tschonn-BH/Tschonn-BH.vmx                                                                                      windows7_64Guest        vmx-11               
2018-02-26T00:22:40|  6      Tschonnnb                                                 [datastore1] Tschonnnb/Tschonnnb.vmx                                                                                        winXPProGuest           vmx-11               
---------------------------------------------------------------------------------------------------------------------------------
2018-02-26T00:22:41|  VMs to backup:
---------------------------------------------------------------------------------------------------------------------------------
2018-02-26T00:22:41|  10     Tschonn-VPC10                                             [datastore1] Tschonn-VPC10/Tschonn-VPC10.vmx                                                                                windows9_64Guest        vmx-11               
---------------------------------------------------------------------------------------------------------------------------------
2018-02-26T00:22:46|  [Tschonn-VPC10] starting backup...
---------------------------------------------------------------------------------------------------------------------------------
2018-02-26T00:22:46|  XSIBackup will backup your VMs while they are running and will quiesce guest services too, so that users
2018-02-26T00:22:46|  can continue to use the VM while the backup is taking place. You can also run cold and warm --backup-how
---------------------------------------------------------------------------------------------------------------------------------
2018-02-26T00:22:46|  Hot backup selected for VM: [Tschonn-VPC10], will not be switched off
---------------------------------------------------------------------------------------------------------------------------------
2018-02-26T00:22:47|  [Tschonn-VPC10] info: boot partition is MBR
---------------------------------------------------------------------------------------------------------------------------------
2018-02-26T00:22:47|  [Tschonn-VPC10] info: Win64 OS (windows9_64) detected on MBR, applying Windows algorithm
---------------------------------------------------------------------------------------------------------------------------------
2018-02-26T00:22:50|  [Tschonn-VPC10] notice DIFRMMIS: no [Tschonn-VPC10_0-flat.vmdk] in remote OneDiff mirror, first run?.
---------------------------------------------------------------------------------------------------------------------------------
2018-02-26T00:22:50|  [Tschonn-VPC10] (c) OneDiff algorithm
---------------------------------------------------------------------------------------------------------------------------------
[Tschonn-VPC10] info: OneDiff backup first run, removing snapshots
[Tschonn-VPC10] info: all snapshots removed
---------------------------------------------------------------------------------------------------------------------------------
2018-02-26T00:22:50|  Snapshot & Quiescing
---------------------------------------------------------------------------------------------------------------------------------
2018-02-26T00:22:50|  [Tschonn-VPC10] info: the VM will now be quiesced to ensure proper data handling
2018-02-26T00:22:58|  [Tschonn-VPC10] info: snapshot taken, quiescing status: YES
---------------------------------------------------------------------------------------------------------------------------------
2018-02-26T00:23:02|  Syncronizing config files
---------------------------------------------------------------------------------------------------------------------------------
2018-02-26T00:23:05|  [Tschonn-VPC10] info: created dir to host VM backup
2018-02-26T00:23:06|  [Tschonn-VPC10] info: VMX file succesfully queued
2018-02-26T00:23:06|  [Tschonn-VPC10] info: VMSD file succesfully queued
---------------------------------------------------------------------------------------------------------------------------------
2018-02-26T00:23:08|  Backing up virtual disks...
---------------------------------------------------------------------------------------------------------------------------------
2018-02-26T00:23:08|  DISK=/vmfs/volumes/datastore1/Tschonn-VPC10/Tschonn-VPC10-Snapshot141.vmsn
2018-02-26T00:23:08|  DISK=/vmfs/volumes/datastore1/Tschonn-VPC10/Tschonn-VPC10_0-000001.vmdk
2018-02-26T00:23:08|  DISK=/vmfs/volumes/datastore1/Tschonn-VPC10/Tschonn-VPC10_0.vmdk
---------------------------------------------------------------------------------------------------------------------------------
2018-02-26T00:23:09|  Rsync: transfering file | /vmfs/volumes/datastore1/Tschonn-VPC10/Tschonn-VPC10-Snapshot141.vmsn
---------------------------------------------------------------------------------------------------------------------------------
sending incremental file list
Tschonn-VPC10-Snapshot141.vmsn

         32,218 100%    0.00kB/s    0:00:00  
         32,218 100%    0.00kB/s    0:00:00 (xfr#1, to-chk=0/1)

sent 32,326 bytes  received 35 bytes  64,722.00 bytes/sec
total size is 32,218  speedup is 1.00
---------------------------------------------------------------------------------------------------------------------------------
2018-02-26T00:23:10|  Disk [/vmfs/volumes/datastore1/Tschonn-VPC10/Tschonn-VPC10_0-000001.vmdk] excluded
---------------------------------------------------------------------------------------------------------------------------------
2018-02-26T00:23:10|  Rsync: transfering file | /vmfs/volumes/datastore1/Tschonn-VPC10/Tschonn-VPC10_0.vmdk
---------------------------------------------------------------------------------------------------------------------------------
sending incremental file list
Tschonn-VPC10_0.vmdk

            555 100%    0.00kB/s    0:00:00  
            555 100%    0.00kB/s    0:00:00 (xfr#1, to-chk=0/1)

sent 653 bytes  received 35 bytes  458.67 bytes/sec
total size is 555  speedup is 0.81
---------------------------------------------------------------------------------------------------------------------------------
2018-02-26T00:23:11|  Info: transfering file | /vmfs/volumes/datastore1/Tschonn-VPC10/Tschonn-VPC10_0-flat.vmdk
---------------------------------------------------------------------------------------------------------------------------------
[32m(c) XSIDiff 1.0.6.1 licensed: 000106E500000000000000000050566ac8b8
[0mFile#1 size 225485783040 bytes
Writing to file /vmfs/volumes/datastore1/backup/Tschonn-VPC10/Tschonn-VPC10_0-flat.vmdk

... and in the end:

Time taken: 1940 seconds
Speed 56.85 mb/s, overall speed 110.85 mb/s
2018-02-26T00:55:35|  [Tschonn-VPC10] CLXSIDF1 error: file transfer error: kex protocol error: type 7 seq 673698
---------------------------------------------------------------------------------------------------------------------------------

I don't understand what's going on ...


P.S.: Did already vmkfstool the vmdk with extending (-X) as read in a different thread here - to no avail

Offline

#5 2018-02-26 09:53:40

admin
Administrator
Registered: 2017-04-21
Posts: 1,366

Re: sha1 hashes are different

Please, contact support to ask for help. The forum is a good way to share common issues and bugs, but this seems to be something particular.

Offline

Board footer