You are not logged in.
Hello,
i'm trying to use XSIBackup 9.0.1 on a ESXi free 6.5.0 (build 4887370) host.
The backup seems to end fine, but the mail subject is reporting "XSIBACKUP errors detected in backup job!!".
I cannot see any details in the mail body, where can I find these errors?
Below is a screenshot of the mail:
[b]Old Dropbox link removed[/b]
Many thanks,
Eros
Offline
I don't see that notice in the screenshot you attached, maybe I'm only seeing it partially. You can copy and paste the output here.
Your speeds are very slow for what XSIBackup can achieve, try to add an SSD disk as host cache whenever you have the chance.
Thanks for the reply Daniel.
I reuploaded a complete image here:
[b]Old Dropbox link removed[/b]
Thanks for the tip on SSD, will consider in the next upgrade.
Here is the copy pasted result:
✖ XSIBACKUP errors detected in backup job!! | ESXi Backup Report. More OSS at [url=https://33hops.com/xsibackup-vmware-esxi-backup.html]VMWare ESXi Backup software[/url]
Done hot backup, using vmkfstools.
Available room in device /vmfs/volumes/bak_datastore/XSIBackup before backup: 941 Gb.
Needed room in device /vmfs/volumes/bak_datastore/XSIBackup for backup: 353 Gb.
VM Name State Size Stop Copy Start Time (min) Speed (mb/s)
Server01 ON 106G NO (hot backup) OK - 136 13
Server04 OFF 76G Off yet OK - 92 14
Server08 ON 3G NO (hot backup) OK - 6 9
Server03 ON 2G NO (hot backup) OK - 11 3
Server05 ON 49G NO (hot backup) OK - 61 13
Server07 ON 50G NO (hot backup) OK - 57 14
Server02 ON 58G NO (hot backup) OK - 85 11
Server06 ON 6G NO (hot backup) OK - 10 10
Available space in device /vmfs/volumes/bak_datastore/XSIBackup after backup: 596 Gb.
Complete backup elapsed time: 462 min
Offline
Everything seems to be O.K., XSIBackup uses a temporary .ERR-XXXXXXXXX... file to store backup job errors. You probably have an empty one at your xsi-dir directory, just delete it.
I'm still worried about your speed figures, you should be getting at least 50 mb/s with commodity hardware (i3 + SATA disks), unless there is a heavy load on the server when the backup takes place.
I cannot find any .ERR-XXXX file in the xsi executable directory:
[root@vmhost01:/vmfs/volumes/58af7e80-1ea8c5c2-373f-e0071bfff7ad/xsibackup] ls -la
total 5136
drwxr-xr-x 1 root root 1260 Apr 22 19:37 .
drwxr-xr-t 1 root root 1960 Mar 14 12:37 ..
-rw-r--r-- 1 root root 4248 Feb 26 13:01 EULA
-rwxrwxrwx 1 root root 35147 Feb 23 21:56 LICENSE.txt
-rwxrwxrwx 1 root root 13435 Feb 23 21:56 README.txt
-rwxrwxrwx 1 root root 368 Feb 23 21:56 cold-backup.sh
-rwxr-xr-x 1 root root 385 Mar 20 10:35 hot-backup.sh
-rwxrwxrwx 1 root root 137935 Feb 26 13:01 xsibackup
-rwxrwxrwx 1 root root 939248 Feb 23 21:56 xsibackup-rsync
The speed slowness probably is related to the datastore config.
The VM storage is a Synology NAS with a RAID5 connected via NFS.
The backup storage is a single Western Digital MyBook 1TB also connected via NFS.
I don't have local storages on this host.
Regarding the error, do you think that I can safely ignore it?
Thanks again,
Eros
Offline
Regarding the error, if there aren't any .ERR-XXXX files you should not receive it any more. Just make sure that you list with ls -la to show hidden files (beggining with .). If you keep on getting it just let us know.
Your setup is quite common, your network could be the bottleneck. Take on account that many of these chineese 1gbps cheap brands will barely get over the 100mbps limit. We strongly recommend using Intel NICs, if you don't want to spend much, any desktop Intel card will perform much better than others. The switch is a very important piece of hardware, you don't need to spend much either, we recommend Microtik, they have amazingly performing models around 100 eur.
Found it, it was in the datastore root, deleted now.
Host's NIC is an Intel I219-LM 1gbps, the switch is an HP 1810-8G.
Datastore NAS is a Synology DS414slim with 4 Kingston SSD SV300S37A240G 240GB in RAID5.
Backup datastore is a Western Digital MyCloud 2TB.
Don't know why is so slow.
Thanks,
Eros
Offline
Tried another backup but the same error happened.
I have no ERR-XXXX files on the datastore, and here is the mail content:
Mon Apr 24 10:29:30 UTC 2017
XSIBACKUP-FREE 9.0.1 AT HOST:
vmhost01.nti.lan
IP v4: 192.168.91.200/ 255.255.255.0
VMware ESXi 6.5.0 build-4887370
Done hot backup, using vmkfstools.
Available room in device /vmfs/volumes/datastore1/Backups before backup: 817 Gb.
Needed room in device /vmfs/volumes/datastore1/Backups for backup: 362 Gb.
VM Name State Size Stop Copy Start Time (min) Speed (mb/s)
Server01 ON 106G NO (hot backup) OK - 83 21
Server04 ON 76G NO (hot backup) OK - 62 20
Server08 ON 3G NO (hot backup) OK - 5 11
Server03 ON 2G NO (hot backup) OK - 11 3
Server05 ON 49G NO (hot backup) OK - 36 23
Server07 ON 58G NO (hot backup) OK - 33 30
Server02 ON 58G NO (hot backup) OK - 57 17
Server06 ON 6G NO (hot backup) OK - 6 16
Available space in device /vmfs/volumes/datastore1/Backups after backup: 469 Gb.
Complete backup elapsed time: 297 min
I noticed that on the shell, before ending, it says:
Error backing the ESXi host config to /vmfs/volumes/datastore1/Backups
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Errors detected in backup, check logs
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Some warnings were raised
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Maybe are there some problems in host configuration backup? What does it means?
Thanks!
Eros
Offline
All error reporting is done by using the .ERR-XXXX... files (note that the file begins by .)
They are not kept in the datastore, but the XSIBackup installation directory.
Behaviour is simple, if the file exists when the backup cycle is finishing and it contains more than zero (0) data, then the content is read and displayed as errors. It is previously put there by the error handling functions. On every new backup cycle the .ERR-XXXX... file is deleted and reinitialized. Just watch what happens in your installation dir and inside the .ERR-XXXXX... file while the backup is taking place.