#1 2018-01-08 09:25:09

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

Problem with spaces or different vmdk-file or folder-names

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?

Offline

#2 2018-01-08 09:32:17

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

Re: Problem with spaces or different vmdk-file or folder-names

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 />

Offline

#3 2018-01-08 09:37:35

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

Re: Problem with spaces or different vmdk-file or folder-names

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.vmdk

After 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)

Offline

#4 2018-01-08 10:24:40

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

Re: Problem with spaces or different vmdk-file or folder-names

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 />

Offline

#5 2018-01-08 10:26:25

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

Re: Problem with spaces or different vmdk-file or folder-names

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
---------------------------------------------------------------------------------------------------------------------------------

Offline

#6 2018-01-08 11:23:34

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

Re: Problem with spaces or different vmdk-file or folder-names

Thank you very much for giving us feedback.

All those limitations in regards to the use of spaces are clearly stated in the man page and all over the posts covering different topics. XSIBackup can nevertheless manage spaces in VMs and disk names, just as long as you stick to some basic naming conventions.

A system is basically a set of rules applied to a set objects, you can give the system a greater degree of freedom, in regards to naming, but that won't offer you any advantage.

In fact you can stretch your reasoning to infinite. Why would you desire to have a VM with disks named after a different thing?, or name disks containing special characters (which ESXi VMFS will allow). You may decide that the -flat.vmdk file does not really need to be named after the descriptor file, or that snapshot files could be named differently. Why calling the snapshot xsibackup?, why not giving it a different name?

We will revise your report and fix whatever issue needs fixing, but XSIBackup will remain more strict in regards to naming that ESXi itself, why?, the answer is easy, cause there's is nothing on the other side of that hill, and on the contrary, keeping a simple and clean naming convention will help you make your system more stable, not only in regards to using XSIBackup, but also ESXi and any other tool you may use.

Offline

#7 2018-01-08 16:38:15

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

Re: Problem with spaces or different vmdk-file or folder-names

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 :-)

Offline

#8 2018-01-08 21:00:20

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

Re: Problem with spaces or different vmdk-file or folder-names

There might be a mix of things, we'll re-check the program and use your report as our first guide. We had to redo the file transfer mechanisms (scp, ssh) lately, so there might be some bug related to spaces.

Again, thank you.

Offline

#9 2018-01-09 18:48:40

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

Re: Problem with spaces or different vmdk-file or folder-names

Confirmed, there are some bugs in regards to espace escaping in v 10.2.1. This will be solved in next version 10.2.2, we'll try to launch it ASAP.

http://33hops.com/forum/viewtopic.php?id=151

Offline

Board footer