Forum ©XSIBackup: ©VMWare ©ESXi Backup Software

Well, you shouldn't be getting any errors. How blank is your ESXi host?, If you have no VMs so far, you may be getting errors due to empty lists, we'll improve that in future GUI versions with warning messages.

To get the details of the errors, just Ctrl+C on the subsequent screen, scroll up and send us the details.

1/ That is an informational message, so as long as it's not causing some nested errors (additional errors on the report), the backup should be fine.
2/ Yes, we already addressed that issue on the Pro version. You have some additional -must have- features created to compare backup files by means of their SHA1 checksums.

Great to know. Should somebody experience ESXi host slowing down, command line behaving sluggish or GUI not showing up, after having configured it as explained in the GUI manual: [url]https://33hops.com/xsibackup-pro-gui-manual.html#1[/url]

A reboot will be the best solution. If the problem reappears, you might be suffering some hardware problem or lack of memory. A quite inexpensive and effective way of making things move faster is to add an SSD disk as a host cache device. Of course memory is still faster than SSDs, so adding extra memory is always a good idea.

SSD Samsung M2 PCIE 960/970 EVO series are NVMe disks with a much higher transfer rate, much closer to RAM speed. Installing one of this, or anything equivalent, like Intel Optane, as a host caché disk, will speed everything up. The bigger the disk, the better, of course. Believe me, it's probably the best money you could spend to speed up your hosts.

The GUI is more than tested.
The cause has to be a particular problem.
Contact support to find where your problem relies.

The statement

The e-mail server [out.postassl.it] is not reachable at port [465]

Has nothing to do with the host responding to pings.
Finding out why is part of your general learning curve.

As a hint: ICMP and TCP are different protocols. The message is stating port TCP 465 is not reachable, so some firewall must be blocking it somewhere between your ESXi host and the SMTP server itself. It's not the ESXi firewall, as XSIBackup opens up the SMTP port automatically.

[url]https://33hops.com/xsibackup-smtp-client.html[/url]

The "arithmetic syntax error" is a symptom, not the disease, just as coughing is not a disease on its own. Those two posts are treating different issues from older versions.

We will try to work this eventual kind of issues around by silently making XSIBackup rescan datastores, although this could be a drawback for most users not having this issue due to the time the rescan might take to complete.

Things don't pop out of nowhere and computers are still not smart enough to cheat us, so that must have come from some previous operation.

Edit the job file manually, we will fix this in the next release.

Things don't happen twice magically. XSIBackup prevents overlapping cron execution requests, so this has all the appeareance that you launched a job through the cron and another one manually. Or that you just duplicated some cron line.

Just kill all jobs using the GUI tools and try again.

The [b]--date-dir=yes[/b] argument still exists.
We really can't grasp what you want to know.
Everything that could be said in regards to using this argument or using a dynamic folder instead has already been said in this post.
The matter is much simpler than the extension of the post.

1 - Use [b]--date-dir=yes[/b] to generate a timestamped folder, or don't use it to backup to the same folder (dangerous)
2 - Use a dynamic name by employing the bash [b]date[/b] command, which offers you endless possibilities.

I'm sorry sir, but we are not quite getting what you try to say. If you are using the Free version and want to use a backup, you have various choices:

1 - Use the VM where it was backed up by just adding it to your inventory.
2 - Copy it somewhere else and then add it to your inventory
3 - If you are using [b](c)XSITools[/b] or [b]Borg[/b] as backup programs, you will need the Pro version.

In case you are in situation number [b]2[/b] and want to copy the backup folder somewhere else, you may very well use [b]Vmkfstools[/b], that should give you 70-80 mb/s of sustained transfer rate, at a minimum. If you are getting poor transfer rates when using [b]Vmkfstools[/b], the most likely reason is that you have some clogged or cheap network hardware in the path.

Please, do keep in mind that cheap gigabit switches and NICs will normally offer a real speed about what your are declaring: 10-12MB/s or 15-20 MB/s

vCenter and other backup software vendors, such as Veeam have nothing to do with the matter.

Next Pro version 11.0.3 will contain a fix for this bug.

Your OneDiff backup is failing because of the following

The specified key, name, or identifier '6' already exists.

You most probably already have a VM by that name at the remote end.