You are not logged in.
Pages: 1
During a remote restore, I received the following 2 ERRORS for 2 VM's
1.[bugs feb] - Note - space in machine name
2.[build5vm]
1. [ Mon Jun 11 02:04:09 UTC 2018 ] <b>ERROR</b> (CLRSYNC4), details [bugs feb] error: rsync error, details: rsync: change_dir "/vmfs/volumes/Releng_1/bugs\ feb" failed: No such file or directory (2)
2. [ Mon Jun 11 02:10:34 UTC 2018 ] <b>ERROR</b> (CLXSIDF1), details [cvs] error: XSIDiff error, details: Segmentation fault</span><br />
<span class=errr>[ Mon Jun 11 02:17:47 UTC 2018 ] <b>ERROR</b> (DIFQMSH4), details [build5vm] error: first 500M mistmatch [build5vm-flat.vmdk]</span><br />
<span class=warn>[ Mon Jun 11 02:17:48 UTC 2018 ] <b>WARNING</b> (DIFRMVMX), details [build5vm] measure DIFRMVMX: took measure, renamed remote .vmx file to reinitialize OneDiff</span><br />
Last edited by jaycox (2018-06-11 14:17:07)
Offline
Those errors, correspond to the backup module: [b]CLRSYNC4[/b], [b]CLXSIDF1[/b], so what you really mean is that you are using the backup features of XSIBackup to bring one or more VMs from a remote server. This is clearly not affecting the restore module, which is invoked in a totally different way. The mechanism used to trandfer the VM data is nevertheless similar.
Error number 1 is an Rsync error, but it has to do with paths. XSIBackup can handle spaces in paths, so it has to be related to something that's not being parsed correctly. Please, post the backup job syntax you are using.
Error number 2 is the result of a broken [b](c)OneDiff[/b] operation with a clear [b]segfault[/b] being the root of all subsequent errors. This can be due to a broken pipe due in turn to a connectivity issue. It's anyway hard to say by just taking a look at the error texts.
What are the facts?. Are you backing up through a WAN?, what speed is it?, are you having other similar errors?, what's the full output?
Offline
Hi, thank you for your reply.
Backup syntax used:
/vmfs/volumes/datastore1/xsi-dir/xsibackup --restore-vms=2
16.111.92.68:22:/vmfs/volumes/Edial_2/backup_il-esxi-01/bugs feb
/vmfs/volumes/datastore1/xsi-dir/xsibackup --restore-vms=2
16.111.92.68:22:/vmfs/volumes/Edial_2/backup_il-esxi-01/build5vm
The backup is over a WAN. I'm not sure the exact throughput, but it seems very slow.
I will try the backup again tonight and capture the full output.
Offline
Just launched this job. Logging console output. I'll update you tomorrow. - Thanks again.
[root@hk-esxi-01:/vmfs/volumes/5890ad3b-b6b9fa80-a225-941882798de8/xsi-dir] /vmfs/volumes/datastore1/xsi-dir/xsibackup --restore-vms=21
6.111.92.68:22:/vmfs/volumes/Edial_2/backup_il-esxi-01/bugs feb
###############################################################################
#
# (c) XSIBACKUP-PRO 10.2.7 | Backup for (c) VMWARE ESXi Hypervisor by 33hops.com
#
###################################################################################
--------------------------------------------------------------------------------------------------------------------------------------
RESTORE VIRTUAL MACHINES:
--------------------------------------------------------------------------------------------------------------------------------------
Detected OpenSSH server at 216.111.92.68:22 and folder at "/vmfs/volumes/Edial_2/backup_il-esxi-01/bugs feb"
Checking the type of backup...
The remote folder "/vmfs/volumes/Edial_2/backup_il-esxi-01/bugs feb" at 216.111.92.68:22 seems to contain a VM
Where do you want that backup to be restored to?: /vmfs/volumes/datastore2
Source: "/vmfs/volumes/Edial_2/backup_il-esxi-01/bugs feb"
Target: "/vmfs/volumes/datastore2"
receiving incremental file list
bugs feb/bugs feb-aux.xml
13 100% 12.70kB/s 0:00:00 (xfr#1, to-chk=4/6)
bugs feb/bugs feb-flat.vmdk
3,047,424 0% 473.66kB/s 53:31:19
Offline
That looks more like an unstable connection, you are probably trying to bring a camel through a needle eye. In those cases, it's better to install XSIBackup on the remote end or run a remote backup by means of the [b]--host[/b] argument and push the VM by forcing use of Rsync [b]--backup-prog=rsync:z[/b]. In this very particular cases, using compression on the SSH tunnel might help a bit too.
If you want more control on every step, you can use xsibackup-rsync to push each file individually. Should the pipe break, just re-engage the file in the Rsync transfer until you bring them all to your local server.
Another option is to create an .ova package, that will compact the VM in a single file and use Rsync the same way.
Offline
Pages: 1