You are not logged in.
Pages: 1
OK, thanks, that worked. I wasn't keen on updating previously since everything was working fine and I have some customizations in place, but I guess it was time. I was able to port over my customizations and cursory tests show everything working now.
Thanks!
I know there were issues last year with ESXi 6.7 U2 and the BusyBox shell. However, I just updated ESXi 6.5.0 to the latest version/patches and now my XSIBackup jobs aren't running and getting the same error. Are there known issues with ESXi 6.5.0 U3?
I'm current running:
VMware ESXi 6.5.0 Update 3
ESXi build number: 16576891
XSIBACKUP-PRO 11.0.1
BusyBox v1.29.3 (2019-08-06 16:31:47 PDT) multi-call binary.
Thanks!
Hello,
I believe a cursory Google search will reveal that a 'b' typically refers to bits and a 'B' refers to bytes, or at the very least, will support the reasonableness of my initial interpretation.
Nonetheless, I'm not here to argue the semantics or nuances of capitalization of acronyms. I'm simply suggesting a minor code change that I think will be an improvement. Feel free to take it or leave it; I've already updated my copy of the code.
Thanks for the consideration.
Suggested patch to xsibackup (original md5sum b467ca74bca0ad8bb356eca591a94705):
@@ -3616,14 +3616,14 @@
fi
vmlistHTMLStr=$vmlistHTMLStr"<tr>\r\n
-<td><b>(Id)VM Name</b></td>\r\n
+<td><b>(Id) VM Name</b></td>\r\n
<td><b>State</b></td>\r\n
-<td><b>Size (Gb)</b></td>\r\n
+<td><b>Size (GB)</b></td>\r\n
<td><b>Stop</b></td>\r\n
<td><b>Copy</b></td>\r\n
<td><b>Start</b></td>\r\n
<td><b>Time (min)</b></td>\r\n
-<td><b>Speed (mb/s)</b></td>\r\n
+<td><b>Speed (MB/s)</b></td>\r\n
</tr>\r\n"
fi
For a while (longer than I care to admit) I thought "mb/s" was megabits/second....
I have the same experience. I do see conf/root-crontab; those entries get copied to ESXi's crontab (/var/spool/cron/crontabs/root) but, I believe, only on boot and when updating cron jobs in the ncurses UI.
Have you tried creating jobs in the ncurses UI and seeing if they run? Works for me.
I do appreciate the xsibackup documentation but sometimes I wonder if what I'm reading applies to the current version. I'd encourage the author(s) to consider versioning the documentation. I know a lot of projects use https://readthedocs.org/ but I know you guys are more than capable of doing/hosting it yourself.
I've been using XSIBackup (free) and thinking about going Pro.
I do have a question ... how does the "smart-info" feature work in environments where ESXi is running an a box with a RAID controller (using, of course, RAIDed disks)?
Looking at the code, xsibackup is a glorified shell script that at its core leverages the tools that come with ESXi. (Now, don't get me wrong, XSIBackup is an impressive and worthy piece of software that greatly simplifies and enables backups so please don't think I'm belittling the software.) But if the "smart-info" is just scraped from the esxcli tool (e.g. 'esxcli storage core device smart get -d <device>') then in situations where a RAID controller is in use, the "smart-info" feature of XSIBackup may not prove to be useful.
Thank you.
Pages: 1