You are not logged in.
Pages: 1
Hi,
restoring from a local repository works as expected
################################################################################
# (c) XSIBACKUP-PRO 11.2.3 | 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/NFS_VOL1/XSITOOLS/, or filter the results:
-------------------------------------------------------------------------------
Searching virtual machines...
Found 1 Virtual Machines:
-------------------------------------------------------------------------------
1| /vmfs/volumes/e5ff9f49-598f4433/XSITOOLS/20190415101959/Centos7_Samba_109/Centos7_Samba.vmx (Centos7_Samba.vmx)
-------------------------------------------------------------------------------
Enter the selected VM (n) or a search filter:
but when I try to restore the same VM backup from the XSItools repo on a remote Linux box I am getting this:
###############################################################################
#
# (c) XSIBACKUP-PRO 11.2.3 | Backup for (c) VMWARE ESXi Hypervisor by 33hops.com
#
###################################################################################
-------------------------------------------------------------------------------
RESTORE VIRTUAL MACHINES:
-------------------------------------------------------------------------------
Detected OpenSSH server at 1.2.3.4:22 and folder at "/data2/201904-xsitools/"
-------------------------------------------------------------------------------
Checking the type of backup...
-------------------------------------------------------------------------------
This folder contains an (c)XSITools backup, VM name is [cat: : No such file or directory]:
-------------------------------------------------------------------------------
Where do you want to restore the VM to?:
Thanks for your help.
Offline
This seems to be a problem determining the name of the remote VM. Does it contain some space or special character?
Offline
No, it does not.
Centos7_Samba_109/Centos7_Samba.vmx
But the source VM was renamed once (adding the number) with the use of the VMware client.
Offline
That may be the reason. If that was the case we would obviously add some logic to fix it, as the restore process has to work even if the VM is renamed. We are now busy with some ESXi bug in the bash interpreter, so we would hopefully have something ready after Easter holydays.
Offline
I performed a test backup of a VM which was never renamed and the behaviour when trying to restore it is the same.
Offline
We were just thinking loud, the cause of your problem could be something else. Please allow some days for us to check this issue and point you in the right direction. Restore locally in the meanwhile if you need to .
Offline
Just testing the features of the full version. I have had a possibly similar sort of problem with comments in the job files causing chained jobs not to start, BTW. Removing them solved it.
Offline
Yes, job files aren't supposed to hold comments. You have a description argument for that purpose.
Offline
Pages: 1