Forum ©XSIBackup: ©VMWare ©ESXi Backup Software

[b]--run-backup[/b] is a helper, XSIBackup doesn't need it to operate. The issue affects it in some cirmcumstances, like when using a [b]--host[/b] argument. We'll fix the issue ASAP, but we don't consider it to be critical.

Remove the 2>/dev/null in the long command and also the chained piped commands and see if you are able to grab the error.

dd if="Win-Test-flat.vmdk" bs=1048576 count=50 skip=0 2>/dev/null | openssl sha1 2>/dev/null | grep "(stdin)=" | awk -F '=' '{print $2}' | sed -e 's/^ *//g' -e 's/ *$//g'

We haven't tested XSITools in ESXi 5.1 since some time ago, but all newer versions are tested.

There are subtle differences between command line utilities from one ESXi version to the next. Sometimes [b]grep[/b] or [b]sed[/b] arguments are changed and this causes some compounded commands to fail. We'll probably end up adding our own utilities to make sure they behave as expected for every build.

We are aware of that. That bug will only affect some e-mail servers, but we have a new Free version with that bug corrected that will be released this week.

You can use any [b]gmail.com[/b], [b]hotmail.com[/b], [b]yahoo.com[/b] account in the meanwhile.

No, there isn't, each VM needs to be accounted and data needs to be collected for each one of them.

Well, that is the expected output. Can you provide your exact version and build number by running this

vmware -v

Also, please run this extended command

dd if="Win-Test-flat.vmdk" bs=1048576 count=50 skip=0 2>/dev/null | openssl sha1 2>/dev/null | grep "(stdin)=" | awk -F '=' '{print $2}' | sed -e 's/^ *//g' -e 's/ *$//g'

And post the output again

Please, run this command from the VM folder once the backup job gets to the error above and paste the output here.

dd if="Win-Test-flat.vmdk" bs=1048576 count=50 skip=0 | openssl sha1

That's some sort of syntax error in the [b]xsibackup-cron[/b] file.
Don't add this

find /vmfs/volumes/afccbe1c-eb281aaa/backup/* -maxdepth 2 -type d -mtime +15 -exec rm -rf {} \;

to the cron file, it will be triggered every minute.
Use the ESXi crontab instead at: [b]/var/spool/cron/crontabs/root[/b], and program it there.

Have you cut & pasted texts into the [b]xsibackup-cron[/b] file?, maybe some character is not what you think it is.

You have not pasted the backup command you are using, the less information, the more we are guessing.

This has nothing to do with the guest OS, it's something with the backup point (--backup-point). The only possibility that you get this error is that XSIBackup has not been able to determine whether [b]/vmfs/volumes/NAS[/b] is a local path. So, make sure that you have not pasted some invisible character into the [b]--backup-point[/b] variable, that the path does exist within your server, that you aren't leaving white spaces between the equal sign and the values in the backup job command, etc...

You can reproduce this very same error by just parsing a non-existent --backup-point path.

If you don't have other option, then don't backup to the same data store where the VM to backup is, this way at least you'll split the [b]I[/b]n traffic from the [b]O[/b]utgoing one.

Nevertheless you'll suffer from a clogged disk controller while you are performing the backup, so VMs on both data stores will function more slowly. That is the price to pay when you are short of resources.

If you can afford it, I would suggest that you buy the [b][https://33hops.com/xsibackup-pro-vmware-esxi-backup.html]Pro version[/url][/b], as it will offer you other tools that will minimize the impact, like [b][https://33hops.com/xsibackup-pro-onediff.html]OneDiff[/url][/b], which allows you to backup just differential data. By using OneDiff you will be copying just the changed bytes since last backup, of course the first backup will be full.

We don't usually take the chance to promote the Pro version in the forum, but in your case, the benefit would be obvious. We are currently offering a Black Friday discount coupon that you can use to get a 10% rebate, voucher is [b]XSIDREWYH[/b]

[b]smtp.amazonaws.com[/b] needs to have the PIPELINING extension enabled, by what I see in the SMTP conversation, it probably doesn't. Fortunately you can use any other SMTP server that does, including: gmail.com, hotmail.com, yahoo.com, etc...

We have not tested this SMTP server (smtp.office365.com), if it follows the SMTP especification it should work though. I don't see the [b]--smtp-sec=TLS[/b] argument in your command. I don't think [b]smtp.office365.com[/b] is going to allow you send mail in plain text.