You are not logged in.
Hi all,
Here is the background info:
- 2 sets ESXi 6.5
- xsibackup 11.0.1
I can successfully backup from 1 ESXi to the other IF the guest has no space on its guest name. However, for other guest name with space (e.g. "Ubuntu 16"), I have found that in the target ESXi, the vmdk file would be placed outside the target directory with the filename "Ubuntu" (it removed the space and character after).
Anyone has the same problem?
Thanks!
Offline
Will check this
UPDATE 2018-07-09
We have made tests backing up a VM with spaces in its name and disk files, the VM is called "New Virtual Machine" from ESXi 6.5.0 build-4564106 to same build and from that same version to ESXi 6.7.0 build-8169922
All the tests using different programs yielded positive results, no issues were found when backing up this VM.
Apart from that, we monitor a lot of backups daily and didn't find any bug in regards to space management.
Please, let us know your exact build and any especial circumstance that could be related to your problem.
Offline
Hi Admin,
Here are the information:
*********************
Source ESXi:
Client version:
1.27.1
Client build number:
7909286
ESXi version:
6.5.0
ESXi build number:
8294253
*********************
Destination ESXi:
Client version:
1.27.1
Client build number:
7909286
ESXi version:
6.5.0
ESXi build number:
8294253
*********************
Command Use:
./xsibackup --backup-point="192.168.1.24:22:/vmfs/volumes/datastore1/backup" --backup-type=custom --backup-prog=rsync --date-dir=yes --smtp-srv=smtp.gmail.com --smtp-port=465 --mail-from=XXX --mail-to=XXX --smtp-usr=XXX --smtp-auth=yes --smtp-sec=TLS --backup-vms="Ubuntu 16" --smtp-pwd=XXX
After the process completes, in the destination ESXi, the files are put in the below hierarchy:
[root@localhost:/vmfs/volumes/5b40e932-32ec64ac-5288-782bcb780a25/backup/20180714054507] ls Ubuntu\ 16/
Ubuntu 16.vmsd Ubuntu 16.vmx vmware.log
[root@localhost:/vmfs/volumes/5b40e932-32ec64ac-5288-782bcb780a25/backup/20180714054507] ls
Ubuntu Ubuntu 16
Offline
Make sure that your VM name does not contain a whitespace that is not really a space character. Many times people just cut & paste text and they don't realize that it might very well be replaced by some encoding which is not ASCII
Create a fake VM from scratch that contains at least a space and back it up. You don't need to install an OS for the test. It should work, if not, please let us know the outcome of this command.
vmware -v
Offline