Forum ©XSIBackup: ©VMWare ©ESXi Backup Software

Update to latest version. There was a bug, that we already fixed, that could cause this in some circumstances.

That looks very weird, Something is returning wrong size figures. Contact support with full log.

Mmmm, thank you for the feedback. Please send us the log with the details if you have the chance. VMFS block size is 1M, on addition, du bundled with busybox in ESXi can't count bytes. We can easily create some binary or look for othe binary in the system that is able to, but the blocksize fact kept us from doing it. Did you import that .vmdk?, some tools, including VMWare's might not round up to a 1M block count.

That first line

#!/usr/bin/vmware

Does not follow ESXi standards. Beware of custom builds distributed by manufaturers, they are commercial traps mainly. Always use official ESXi builds, unless you have no other choice. In case of the latter, you'll have to assume you are using a custom build and call your hardware manufaturer with a credit card at hand.

To solve your particular issue, you can disable that check, or delete that first line in your .vmx file, of course, at your own risk. We do not offer support for custom builds.

We offer the same support quality regardless of future aquisitions.
As stated, XSIBackup is a bash script, it doesn't close or kill anything selectively. We cannot offer support for any Linux distro, although it should simply work, just as long as you meet some minimun requirements.

You should probably increase the level of debuging, you may find out that you aren't able to run your job cause KEX is failing. OpenSSH has made some changes to KEX priorities lately, so you may need to tweak your SSH command or config file.

It's probably a missconception. When the remote backup job finishes, it will look for the next backup job in its local crontab, not in the master server. You may need to reorganize your backup jobs in a different way.

I think you should take a look at this:
[url]https://www.experts-exchange.com/questions/28703884/ESXi-5-5-Cannot-boot-any-vms-after-crash.html[/url]

And this:
[url]https://www.rootlinks.net/2014/02/08/invalid-syntax-error-of-df-command-on-esxi-5-5/[/url]

Thank you, but the -E switch is present indeed. I have to correct myself, I missed that they key is obvious:

Traceback (most recent call last):
  File "/bin/df", line 101, in <module>
    sys.exit(main(sys.argv))
  File "/bin/df", line 55, in main
    o = eval(output)
  File "<string>", line 1
    Errors:

Which is a Python error, where no Python code is present. This could be a broken installation, have you thought of that possibility?

This is due to grep lacking the -E switch for regexp patterns in ESXi 5.1
We'll update this thread ASAP

As a rule of thumb, I would not delete anything in your source VM, you don't need to.
The [b]___hash[/b] is the hash of the corresponding file, it is overwritten on every file comparison. The rest of the files belong to the VM, check VMWare documentation for more details.

The fix is available to download as XSIBACKUP-PRO 10.2.3

GMail SMTP client has been custom programmed, as GMail has some special requirements. We cannot develop something for a small base of users, but you can use any other SMTP server, including some free options like regular GMail. You can also program it on your own and keep your personalized src/sendmail module.