I have just updated my ESXi to 6.7 update 2 from update 1 and now I am getting the following error when running xsibackup
/vmfs/volumes/datastore1/xsi-dir/xsibackup: line 605: syntax error: unexpected "&"
I have tried reinstalling XSIBACKUP PRO but still getting the same errors when executing xsibackup
I have PRO and the error is at line 605, while building debuginfo string
it seems related to special chars like "&", "(", ")", I tried escaping some lines and the scripts runs just until next unescaped char. Very ugly shell bug, or perhaps just a config option to set...
I'm afraid no config option should control wether a plain ampersand or parenthesis character is parsed by the interpreter when enclosed in double or even single quotes. We have found this to be happening even on commented out lines, thus is seems to be a bug.
Hello I have the somme problem - when will we "Pro" Users get an update?????
Using the latest software in production is playing Russian roulete with your feet. This case is a clear example of that statement.
Some changes were made in the Bash interpreter that would break Bash script execution.
The Problem is - I installed the update already.
Can I "deinstall" teh update?
Does anyone know if VMWARE is aware of the problem? Will the make a patch?
It's easy to revert ESXi to the previous version by pressing CTL+R when ESXI is booting from the disk. This is what I did and got back to my Update 1 Build 11675023 version.
For PRO users that can't revert ESXi and use remote backups, in addition to the workaround suggested in the bug tracker post, change the file <xsi-dir>/src/pro/host at the line 47 from
so the auto update fase will not override the xsibackup script that must to be modified on the remote hosts affected by the busybox bug.
Well, we have not tested Sistemi procedure, so anyone trying this out does at his own risk.
We have developed a new version that incorporates a fix as XSIBACKUP-PRO 11.3.0
The recommended procedure is:
1 - Skip ESXi 6.7.0 U2 if you can.
2 - Contact support to get your 11.3.0 version copy.
We have not published it yet as it's in testing phase, it's working fine so far anyway.
For those of you using more intrincate topologies, some bug may still arise.