It's a custom VIB created with the help of your tool, described at my page here http://www.sysstem.at/2013/01/vmware-vsphere-hypervisor-esxi-5-1-0-patch-2-build-914609-with-ghettovcb-from-january-2013/
The strange thing is, that I was able to manage the host after the update. but somehow (after the cronjob?) both servers went down. One After 5 hours after the first cronjob and nearly exact the same time when the 2nd cronjob should start. (no VMs hosted)
The other server went down some hours later (VMs hosted). Both are in the same timezone.
It could be that the script crashed them, but I also can't prove the opposite.
This is the script.
#delete backups older than 20 days
cd /vmfs/volumes/datastore2/BACKUP
find . -mindepth 1 -mtime +20 -exec rm -f {} \;
#change to original dir
cd /vmfs/volumes/datastore1/BACKUP
find . \( ! -name "*_1-flat.vmdk" \) | cpio -padv /vmfs/volumes/datastore2
written to cron via:
# Stop cron
/bin/kill $(cat /var/run/crond.pid)
# Script for cron injection
/bin/echo "#Backup of all VMs" >> /var/spool/cron/crontabs/root
/bin/echo "0 18 * * 0 /opt/ghettoVCB/ghettoVCB.sh -g /opt/ghettoVCB/ghettoVCB.conf -a" >> /var/spool/cron/crontabs/root
/bin/echo "#Backup of SYSTEM Disk to Datastore2 from existing Backups" >> /var/spool/cron/crontabs/root
/bin/echo "0 23 * * 0 /opt/ghettoVCB/2nd-backup.sh" >> /var/spool/cron/crontabs/root
# Start cron
/usr/lib/vmware/busybox/bin/busybox crond
+ the colleague at the remote side will try a cold reboot next day. if this does not solve the problem, I try to advise him to uninstall the custom VIB via console. And if all of this fails, there is still an backup filesystem with 5.0
