I'm moving XSIBackup-PRO from ESXi 6.0 Free to a new ESXI 6.7 Free installation and found that I cannot run xsibackup --install-cron:
Only ESXi 5.X and 6.X series are supported. It will not work in previous versions of ESXi
using XSIBACKUP-PRO 10.3.3
It could be just an error in the version check because everything else is working as expected.
Just go to line 795 of the main xsibackup file and add the version to the compatibility check.
We haven't still certified XSIBACKUP-PRO to be used with ESXi 6.7, but there's no reason why it shouldn't work.
Give us some feedback on how it worked for you.
The only issues that may show up are related to shell's binaries: sed, grep, awk, etc...
They are pretty buggy and bugs change from one version the the subsequent one, although we will be able to work them around one way or another in case they appear.
And do remember one of our favourite quotes:
"Being the first to use some new version in production, is equivalent to being the first to try the Caesar's food"
Yes, after starting this topic I realized that xsibackup is a script and not a binary and found the same solution searching for the error message text.
Thanks anyway, the backup process is working as expected, also the restore is working.
I used backup and restore features for moving 36 VMs from one ESXi 6.0 to another ESXi 6.7 pivoting on the shared iSCSI datastore where backups are made.
At the end of the day I activated the cron job and the automated backup worked as expected.
No problems so far, and by the way, I do like Ceasar Salad.
Thank you for your feedback.
Risky business, don't complain if you hit some ESXi bug then ;-)
Sorry for hijacking the thread. Any insight as to when support for 6.7 will be available?
As per our preeliminary tests and user feedback, it seems last XSIBACKUP-PRO version is compatible. So, we will be launching an officially enabled version in short. In the meanwhile, you can enable ESXi 6.7 on your own by editing the main xsibackup file as explained above.
There is indeed one bug that has to be addressed in ESXi 6.7 and prevents any over IP backup from being fulfilled.
The OpenSSH binary now spits the absolutely unnecessary line: FIPS mode initialized
If I was the programmer that decided to offer such redundantly unnecessary poetry, I would not comment in bars ;-), as many thousands of people are probably now thinking what would be a fair nemesys for such unwanted piece of information on STDOUT.
We are already working this verse around and an almost fully compatible version will be launched with XSIBACKUP-PRO 11.0.0 RC3, which will be distributed to Pro users tonight or tomorrow morning the latest.
The problem was fixed in v 11.0.1