Forum ©XSIBackup: ©VMWare ©ESXi Backup Software
MenuYou are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 Re: General matters » Mail report gives warning for excluded disks » 2019-11-14 14:24:13
Same for me. Intentionally excluded disks lead to "(!) ... warnings" in the mail report. Would like to have a possibility not to recognize disk exclusion as a warning, because I'm filtering the mail reports depending on the words "warning" and "error" in the mail subject.
#2 Re: General matters » Unable to restore in XSIBACKUP-PRO 10.3.4 » 2018-11-05 23:50:39
Shame on me ... I did understand wrong "create it first" ... thought it means, XSIBackup is trying to create ...
Sorry for my bad english and thank you so much for your patience and help!
Johannes
#3 General matters » Unable to restore in XSIBACKUP-PRO 10.3.4 » 2018-11-03 21:29:57
- tschonn
- Replies: 3
Hello,
now my backup is moothly running for months, so I didn't update anymore and I don't want to ... but today finally I found the time to try a restore - which fails - see the output below.
So, what's going wrong?
Best, Johannes
###############################################################################
#
# (c) XSIBACKUP-PRO 10.3.4 | Backup for (c) VMWARE ESXi Hypervisor by 33hops.com
#
###################################################################################
-------------------------------------------------------------------------------
RESTORE VIRTUAL MACHINES:
-------------------------------------------------------------------------------
XSIBACKUP-PRO is able to detect VMs up to two levels below the provided path
This way it can detect VMs stored to the root of it or in timestamped subfolders
Select one of the folders at /vmfs/volumes/BackupNAS2/, or filter the results:
-------------------------------------------------------------------------------
Searching virtual machines...
Found 5 Virtual Machines:
-------------------------------------------------------------------------------
1| /vmfs/volumes/a89897c4-d921b074/Tschonn-VPC7_XSIBAK/Tschonn-VPC7.vmx (Tschonn-VPC7.vmx)
2| /vmfs/volumes/a89897c4-d921b074/Tschonn-BH_XSIBAK/Tschonn-BH.vmx (Tschonn-BH.vmx)
3| /vmfs/volumes/a89897c4-d921b074/Tschonnnb_XSIBAK/Tschonnnb.vmx (Tschonnnb.vmx)
4| /vmfs/volumes/a89897c4-d921b074/TschonnServer2016Std_XSIBAK/TschonnServer2016Std.vmx (TschonnServer2016Std.vmx)
5| /vmfs/volumes/a89897c4-d921b074/Tschonn-VPC10_XSIBAK/Tschonn-VPC10.vmx (Tschonn-VPC10.vmx)
-------------------------------------------------------------------------------
Enter the selected VM (n) or a search filter: 3
-------------------------------------------------------------------------------
You chose to restore the VM [Tschonnnb_XSIBAK_XSIBAK]
-------------------------------------------------------------------------------
Where do you want to restore the selected VM?: /vmfs/volumes/datastore1/new_dir
-------------------------------------------------------------------------------
The path "/vmfs/volumes/datastore1/new_dir" does not exist, create it first
Exiting...
Killed
[root@ESXiT310-2:/vmfs/volumes/5a47a3a2-56dcdeb4-627a-0026b94bd274/xsi-dir] ls /
vmfs/volumes/datastore1
BCM-Windows-7-Pro-32
Server12
backup
bitnami-lappstack-7.0.22-1-linux-debian-8-x86_64
installs
xsi-dir
[root@ESXiT310-2:/vmfs/volumes/5a47a3a2-56dcdeb4-627a-0026b94bd274/xsi-dir] mkdi
r /vmfs/volumes/datastore1/new_dir
[root@ESXiT310-2:/vmfs/volumes/5a47a3a2-56dcdeb4-627a-0026b94bd274/xsi-dir] ls /
vmfs/volumes/datastore1
BCM-Windows-7-Pro-32
Server12
backup
bitnami-lappstack-7.0.22-1-linux-debian-8-x86_64
installs
new_dir
xsi-dir
#4 Re: © OneDiff » sha1 hashes are different » 2018-02-26 09:47:42
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 pipeSo 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
#5 Re: © OneDiff » sha1 hashes are different » 2018-02-24 00:16:31
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 pipe2018-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 fault2018-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#6 © OneDiff » sha1 hashes are different » 2018-02-23 15:02:22
- tschonn
- Replies: 4
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 :-)
#7 Re: General matters » Remote on-error / on-success triggering problem » 2018-01-21 22:21:21
I did read about that and I'm aware of and I think I'm dealing with it in the right way.
Please read the PM (e-mail) I sent to you - there you can read the crontabs and resulting logs.
Thank you !
#8 General matters » Remote on-error / on-success triggering problem » 2018-01-21 11:55:21
- tschonn
- Replies: 2
Hello,
I have two identical setup ESXI6.0-Hosts with xsibackup-cron as described below where the first (time-scheduled) jobs should trigger a cascade of three more jobs but it's only doing the first "follow-up"
I'll send the rest via PM due to limitation in text here
#9 Re: General matters » ERROR RBAKSRV1 details: Unable to determine the type of server parsed » 2018-01-11 22:51:53
Hello elasoft,
as I have the same problem, I would like to know what was the reason/solution for you?
Thanks!
#10 Re: General matters » Problem with spaces or different vmdk-file or folder-names » 2018-01-08 16:38:15
Hello,
I nearly completely agree with what you're writing.
In my case the naming has "historic" reasons ... but I will modify ("clean naming") it.
The only thing I don't agree is the "clearly stated in the man page"-statement: I did read the man pages and only found "XSIBACKUP-PRO can use datastores with spaces as a backup target, but cannot handle VMs stored in a datastore with spaces" and "Please do remember to double quote this string if there are any VMs with spaces in its name".
So as my DATASTORES are simply named "datastore1" ... I supposed my setup to be supported ... maybe the man pages should be a bit clearer regarding this case, what would help in keeping the time for error fixing low.
Thank you for replying that fast :-)
#11 Re: General matters » Problem with spaces or different vmdk-file or folder-names » 2018-01-08 10:26:25
From .log-file:
---------------------------------------------------------------------------------------------------------------------------------
2018-01-08T08:49:26| Backing up virtual disks...
---------------------------------------------------------------------------------------------------------------------------------
2018-01-08T08:49:26| DISK=/vmfs/volumes/datastore1/BCM Windows 7 Pro 32/BCM Windows 7 Pro 32-000001.vmdk
2018-01-08T08:49:26| DISK=/vmfs/volumes/datastore1/BCM Windows 7 Pro 32/BCM Windows 7 Pro 32-Snapshot3.vmsn
2018-01-08T08:49:26| DISK=/vmfs/volumes/datastore1/BCM Windows 7 Pro 32/BCM Windows 7 Pro 32.vmdk
---------------------------------------------------------------------------------------------------------------------------------
2018-01-08T08:49:26| Disk [/vmfs/volumes/datastore1/BCM Windows 7 Pro 32/BCM Windows 7 Pro 32-000001.vmdk] excluded
2018-01-08T08:49:27| Rsync: transfering file | /vmfs/volumes/datastore1/BCM Windows 7 Pro 32/BCM Windows 7 Pro 32-Snapshot3.vmsn
sending incremental file list
sent 20 bytes received 12 bytes 21.33 bytes/sec
total size is 0 speedup is 0.00
2018-01-08T08:49:28| [0;31m[BCM Windows 7 Pro 32] error CLRSYNC4: rsync: change_dir "/vmfs/volumes/datastore1/BCM\ Windows\ 7\ Pro\ 32" failed: No such file or directory (2)
2018-01-08T08:49:28| rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0][0m
2018-01-08T08:49:29| Rsync: transfering file | /vmfs/volumes/datastore1/BCM Windows 7 Pro 32/BCM Windows 7 Pro 32.vmdk
sending incremental file list
BCM Windows 7 Pro 32.vmdk
sent 761 bytes received 41 bytes 1,604.00 bytes/sec
total size is 658 speedup is 0.82
2018-01-08T08:49:29| [1mRsync[0m: comparing file sizes...
---------------------------------------------------------------------------------------------------------------------------------
2018-01-08T08:49:30| [1mRsync[0m: sizes are different, calculating delta checksums, can take a while, time for a coffee...
---------------------------------------------------------------------------------------------------------------------------------
2018-01-08T08:49:30| [1mRsync[0m: transfering file [ /vmfs/volumes/datastore1/BCM Windows 7 Pro 32/BCM Windows 7 Pro 32-flat.vmdk ]
sending incremental file list
BCM Windows 7 Pro 32-flat.vmdk
sent 3,002,714,274 bytes received 3,932,435 bytes 793,834.11 bytes/sec
total size is 64,424,509,440 speedup is 21.43
---------------------------------------------------------------------------------------------------------------------------------
2018-01-08T09:52:37| Excluded disks removed from backup .vmx file
---------------------------------------------------------------------------------------------------------------------------------
2018-01-08T09:52:37| [BCM Windows 7 Pro 32] info: certifying backup by means of sha1 algorithm...
2018-01-08T09:52:38| [BCM Windows 7 Pro 32] info: computing hashes for [BCM Windows 7 Pro 32-flat.vmdk]
2018-01-08T09:52:38| [BCM Windows 7 Pro 32] info: comparing hashes of /vmfs/volumes/datastore1/BCM Windows 7 Pro 32/BCM Windows 7 Pro 32-flat.vmdk | 192.168.100.6:22:/vmfs/volumes/datastore1/backup/BCM Windows 7 Pro 32/BCM Windows 7 Pro 32-flat.vmdk
2018-01-08T10:04:49| [BCM Windows 7 Pro 32] info: sha1 hash is a718bd0bd039ee4734310a24fc8c89bbd852ac22
---------------------------------------------------------------------------------------------------------------------------------#12 Re: General matters » Problem with spaces or different vmdk-file or folder-names » 2018-01-08 10:24:40
Failing VM Nr. 3:
Same again, only .vmx, .vmdk and flat.vmdk residing in the target dir.
.ERRxxx-file:
<span class=errr>[ Mon Jan 8 08:49:23 UTC 2018 ] <b>ERROR</b> (CLCPNVMX), details [BCM Windows 7 Pro 32] error: cannot copy VMX file, details: /vmfs/volumes/datastore1/xsi-dir/xsibackup: eval: line 1: can't create /vmfs/volumes/datastore1/backup/BCM Windows 7 Pro 32/BCM Windows 7 Pro 32.vmx: nonexistent directory</span><br />
<span class=errr>[ Mon Jan 8 08:49:24 UTC 2018 ] <b>ERROR</b> (CLCPNVMS), details [BCM Windows 7 Pro 32] error: cannot copy VMSD file, details: /vmfs/volumes/datastore1/xsi-dir/xsibackup: eval: line 1: can't create /vmfs/volumes/datastore1/backup/BCM Windows 7 Pro 32/BCM Windows 7 Pro 32.vmsd: nonexistent directory</span><br />
<span class=errr>[ Mon Jan 8 08:49:28 UTC 2018 ] <b>ERROR</b> (CLRSYNC4), details [BCM Windows 7 Pro 32] error: rsync error, details: rsync: change_dir "/vmfs/volumes/datastore1/BCM\ Windows\ 7\ Pro\ 32" failed: No such file or directory (2)
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]</span><br />#13 Re: General matters » Problem with spaces or different vmdk-file or folder-names » 2018-01-08 09:37:35
Failing VM Nr. 2:
The name of the VM differs from the subdir name: the homedir of the vm on the source-ESXi is "/vmfs/volumes/datastore1/Server12 neu", but the display name of the VM is "Server12" (without " neu")
XSIBackup generates the dir "/vmfs/volumes/datastore1/Server12" (without " neu") on the target machine ... in the .ERRxxxx - file the following is logged.
span class=errr>[ Sun Jan 7 22:52:04 UTC 2018 ] <b>ERROR</b> (CLCPNVMX), details [Server12] error: cannot copy VMX file, details: /vmfs/volumes/datastore1/xsi-dir/xsibackup: eval: line 1: can't create /vmfs/volumes/datastore1/backup/Server12/Server12 neu.vmx: nonexistent directory</span><br />
<span class=errr>[ Sun Jan 7 22:52:04 UTC 2018 ] <b>ERROR</b> (CLCPNVMS), details [Server12] error: cannot copy VMSD file, details: /vmfs/volumes/datastore1/xsi-dir/xsibackup: eval: line 1: can't create /vmfs/volumes/datastore1/backup/Server12/Server12 neu.vmsd: nonexistent directory</span><br />
<span class=errr>[ Sun Jan 7 22:52:10 UTC 2018 ] <b>ERROR</b> (CLRSYNC4), details [Server12] error: rsync error, details: rsync: change_dir "/vmfs/volumes/datastore1/Server12\ neu" failed: No such file or directory (2)
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]</span><br />
<span class=errr>[ Sun Jan 7 22:52:14 UTC 2018 ] <b>ERROR</b> (CLRSYNC4), details [Server12] error: rsync error, details: rsync: change_dir "/vmfs/volumes/datastore1/Server12\ neu" failed: No such file or directory (2)
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]</span><br />while on the target machine the following output of pgrep shows two lines with non-escaped spaces:
[root@ESXiT310:~] pgrep -fl xs
2026809 /vmfs/volumes/59398a59-80829997-3b0b-0026b9465979/xsi-dir/bin/xsibackup-rsync --server -vlDpre.is -B131072 --inplace . /vmfs/volumes/datastore1/backup/Server12/Server12 neu-flat.vmdk
2026808 /vmfs/volumes/59398a59-80829997-3b0b-0026b9465979/xsi-dir/bin/xsibackup-rsync --server -vlDpre.is -B131072 --inplace . /vmfs/volumes/datastore1/backup/Server12/Server12 neu-flat.vmdk
2026807 sh -c /vmfs/volumes/59398a59-80829997-3b0b-0026b9465979/xsi-dir/bin/xsibackup-rsync --server -vlDpre.is -B131072 --inplace . /vmfs/volumes/datastore1/backup/Server12/Server12\ neu-flat.vmdkAfter backup, in the target dir for Server12 (which has two virtual disks) there are the vmx, one vmdk, two delta.vmdk and two flat.vmdk files
(Forgot to mention: VMware ESXi 6.0.0 build-5050593, XSIBACKUP-PRO 10.2.1)
#14 Re: General matters » Problem with spaces or different vmdk-file or folder-names » 2018-01-08 09:32:17
OK, next part - failing VM Nr. 1:
Excerpt of a mail i got from XSIBackup
VMXFILEPATH: /vmfs/volumes/datastore1/Tschonn-VPC10/Windows 10 Test.vmx
• VM Tschonn-VPC10 remote VMX path exists at: 192.168.100.16:22:/vmfs/volumes/datastore1/backup/Tschonn-VPC10/Windows 10 Test.vmx
• VM Tschonn-VPC10 SYS DISK1 EXISTS: /vmfs/volumes/datastore1/Tschonn-VPC10/Windows 10 Test_0.vmdk
• VM Tschonn-VPC10 SYS DISK2 EXISTS: /vmfs/volumes/datastore1/backup/Tschonn-VPC10/Windows 10 Test_0.vmdk
• VM Tschonn-VPC10 CID1: 08bbce8a
• VM Tschonn-VPC10 CID2: 08bbce8a
• VM Tschonn-VPC10 CID: 0
• VM Tschonn-VPC10 SNAPSHOT: xsibackupdiff
• VM Tschonn-VPC10 SNAPSHOT NUM: 1
• [ Sun Jan 7 17:44:31 UTC 2018 ] ERROR (CLCPNVMS) details [Tschonn-VPC10] error: cannot copy VMSD file details: /vmfs/volumes/datastore1/xsi-dir/xsibackup: eval: line 1: can't create /vmfs/volumes/datastore1/backup/Tschonn-VPC10/Windows 10 Test.vmsd: nonexistent directory
• [ Sun Jan 7 17:44:31 UTC 2018 ] ERROR (CLCPNVMX) details [Tschonn-VPC10] error: cannot copy VMX file details: /vmfs/volumes/datastore1/xsi-dir/xsibackup: eval: line 1: can't create /vmfs/volumes/datastore1/backup/Tschonn-VPC10/Windows 10 Test.vmx: nonexistent directory
• [ Sun Jan 7 17:44:36 UTC 2018 ] ERROR (CLRSYNC4) details [Tschonn-VPC10] error: rsync error details: rsync: link_stat "/vmfs/volumes/datastore1/Tschonn-VPC10/Windows\ 10\ Test-Snapshot98.vmsn" failed: No such file or directory (2)
• rsync error: some files/at trs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]
From the .ERR-File:
<span class=errr>[ Sun Jan 7 17:44:31 UTC 2018 ] <b>ERROR</b> (CLCPNVMX), details [Tschonn-VPC10] error: cannot copy VMX file, details: /vmfs/volumes/datastore1/xsi-dir/xsibackup: eval: line 1: can't create /vmfs/volumes/datastore1/backup/Tschonn-VPC10/Windows 10 Test.vmx: nonexistent directory</span><br />
<span class=errr>[ Sun Jan 7 17:44:31 UTC 2018 ] <b>ERROR</b> (CLCPNVMS), details [Tschonn-VPC10] error: cannot copy VMSD file, details: /vmfs/volumes/datastore1/xsi-dir/xsibackup: eval: line 1: can't create /vmfs/volumes/datastore1/backup/Tschonn-VPC10/Windows 10 Test.vmsd: nonexistent directory</span><br />
<span class=errr>[ Sun Jan 7 17:44:36 UTC 2018 ] <b>ERROR</b> (CLRSYNC4), details [Tschonn-VPC10] error: rsync error, details: rsync: link_stat "/vmfs/volumes/datastore1/Tschonn-VPC10/Windows\ 10\ Test-Snapshot98.vmsn" failed: No such file or directory (2)
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]</span><br />#15 General matters » Problem with spaces or different vmdk-file or folder-names » 2018-01-08 09:25:09
- tschonn
- Replies: 8
Hello,
the problems that I will describe below are reproducable and after some testing I'm quite sure it IS because for spaces in names and different names of VM and the folders they are residing in.
I can workaround this (by renaming) - but I think it is worth fixing (because it costed me many hours to find out and I'm sure there are some more users being thankful for fixing it ;-))
The problems are arising if one of the following matches:
1. The name of the vmdk differs from the VM Name
2. The name of the vmdk contains spaces
3. The name of the VM differs from its dir name in the source (and thus the target dir name differs from the source dir name)
I would like to write more specific, but there seems to be a limitation in length in this forum?
#16 Re: © OneDiff » XSIDiff error, details: kex protocol error: type 7 » 2018-01-07 20:54:27
Sorry, mail via form dont work. Maybe you send me your mail-Addr?
#17 Re: © OneDiff » XSIDiff error, details: kex protocol error: type 7 » 2018-01-07 20:50:13
Regarding the "record": Not 200 mb(ytes)/s, bit 200 MBit/s (Network transfer) ... that's far from the HD limits ;-)
Detailed log: The mentioned .ERR-file is already overwritten, sorry, but I will forward the then mail that was sent to me by the script.
The "kex"-error never rised again till now.
But i've got an vague suspicion: In the beginning bot ESXi-boxes were multi-homed. The had two vmkernel-Networks, 192.168.66.0 and 192.168.100.0, both connected to (different) switches. And I found out that ESXi can't handle this. I saw the box trying to send packets bound to an adress in 192.168.100.0/24 over its interface 192.168.66.x ... so I deleted the second vmkernel-Network on both machines. Maybe the error was due to this?
#18 Re: © OneDiff » XSIDiff error, details: kex protocol error: type 7 » 2018-01-06 09:59:20
Sorry for having been inprecise: The "log" I'm referring to is the ".ERRxxxxxxxxxxxxxxxxx"-file in /xsi-dir.
The "kex protocol error"-lines were also included in the mail sent to me by the xsibackup script.
Of course I did some reading in the forum and found the mentioned forum-thread and understood that the bug is already addressed ("From XSIBackup 9.1.9 and up") before writing here, but: I am using current version 10.2.1 of xsibackup, so I was upset seeing the "key protocol error".
However, the backups are working and the following differential backups (using OneDiff) don't show up any more errors, I'm happy about it.
Regarding the speed: once the first copy is done, the following OneDiff-backups are running fast, another thing I'm happy about.
Just for being sure: There is no need for me to update ESXi, OpenSSL/OpenSSH or something else on my ESXi-Boxes?
Thank you very much
Tschonn
#19 © OneDiff » XSIDiff error, details: kex protocol error: type 7 » 2018-01-04 20:04:20
- tschonn
- Replies: 5
Hello,
I'm new to XSIBackupPro - and got problems.
My Setup:
2 identical machines with DELL-ESXi-6.0U3-5050593-A00 installed, one running fine for months, the second new, running fine for some days. Dedicated (onboard-)NICs for VMkernel each.
XSIBACKUP-PRO 10.2.1 installed on both, they can SSH each other with no problem.
ssh -V shows "OpenSSH_7.3p1, OpenSSL 1.0.2j-fips 26 Sep 2016" (same on both machines, as expected)
But - running a command like
"/vmfs/volumes/datastore1/xsi-dir/xsibackup" --backup-point="192.168.100.16:22:/vmfs/volumes/datastore1/backup" --backup-type=custom --backup-vms="VM1,VM2,VM3" --backup-prog=onediff --backup-room=1200 --debug-info=yes --mail-from=*** --mail-to=*** --smtp-srv=*** --smtp-port=25 --smtp-usr=*** --smtp-pwd=***
does a backup - not too fast (vSphere WebClient shows around 200 MBit/s) - and in the end there seems to be a valid backup - but what is worrying me, are these entries in the logs:
[ Thu Jan 4 17:12:45 UTC 2018 ] ERROR (CLXSIDF1), details [Tschonn-VPC7] error: XSIDiff error, details: kex protocol error: type 7 seq 677110
kex protocol error: type 7 seq 1354425
kex protocol error: type 7 seq 2034312
kex protocol error: type 7 seq 2721475
kex protocol error: type 7 seq 3406309
kex protocol error: type 7 seq 4092443
kex protocol error: type 7 seq 4776557
kex protocol error: type 7 seq 5456368
And an additional question: Is the speed normal? Machines are Xeon 3440, 32GB RAM, GBit-Network, little load, Storage working fine (accessing the VMs runs as expected for a GB-Connection)
Thanks in advance and sorry for my bad english.
Tschonn
#20 Re: General matters » 33hops.com Registered Users -> Unable to login? » 2018-01-03 12:33:58
Now working as expected.
Thank you very much :-)
#21 Re: General matters » 33hops.com Registered Users -> Unable to login? » 2018-01-03 12:07:28
Tried again ... now I'm getting "your subscription expired on 2000-01-01" ... ?
#22 Re: General matters » 33hops.com Registered Users -> Unable to login? » 2018-01-03 11:41:50
Sorry, but still the same problem for me. Tried in IE, FF, Chrome ...
I can login, the page tells me that my credential are accepted, but there is still the "registered users"-Link in the upper right corner and still no chance to get my registered version of XSIBackup :-(
Pages: 1