Just a quick heads up! Over the last week I’ve been upgrading our vCenter servers from version 5.5 to the most recent 5.5 Update 3b version and have ran into a small hiccup.
The upgrade of SSO, Web Client, Inventory Service and even vCenter server all went as expected without any issues. Then I rebooted the vCenter server and after the reboot noticed that the vCenter server service hadn’t started and when I tried to start it manually I then received the following error:
Error 1053: The service did not respond to the start or control request in a timely fashion.
A component found in the VMware Tools called vShield drivers, which is used to accommodate agent-less antivirus solutions such as McAfee MOVE has been renamed from “vShield drivers” to “Guest Introspection driver”.
While moving some VM’s from Hyper-V to VMware using VMware Converter a VM failed to convert with the error: FAILED: The VSS snapshots cannot be stored.
FAILED: The VSS snapshots cannot be stored because there is not enough space on the source volumes or because the source machine does not have any NTFS volumes. Error code: 2147754783 (0x8004231F).
Come to find out the System Reserved partition was full. Our soon to be retired Appassure backup application was nice enough to fill up the volume.
Luckily Appassure is being replaced by Veeam and fixing the above VMware Converter error is an easy fix.
VMware just published KB 2136854 regarding a new bug found in ESXi 6.0 that causes virtual machine backups, which use Changed Block Tracking (CBT), to be inconsistent. VMware says the cause of the issue is this:
This issue occurs due to an issue with CBT in the disklib area, this causes the change tracking information of I/Os that occur during snapshot consolidation to be lost. The main backup payload data is never lost and it is always written to the backend device. However, the corresponding change tracking information entries which occur during the consolidation task are missed. Subsequent QueryDiskChangedAreas() calls do not include these missed blocks, hence a backup based on this CBT data is inconsistent.
Many servers already come with a DVD/CD-ROM drive or some kind of ability to virtually mount an ISO image from a network share onto your server to then install ESXi. However, not all do or you just want to have your ESXi image readily available. Here’s a quick step by step instructions on how to use a USB flash drive to install ESXi.
- Download ESXi 5.1 from VMware (if you haven’t already) as well as UNettbootin.
- Plug in your USB Flash Drive.
- Open UNetbootin and select “Diskimage”, set Type to “USB Drive”, select Drive letter of your USB flash drive, and set the path of your ESXi 5.1 ISO image. Then click on “OK”.
VMware has released vCenter Server 6.0 Update 2 and ESXi 6.0 Update 2 (build: 3620759) which include a number of new features and fixes. VMware has also released the much anticipate VSAN 6.2 which includes it’s own bunch of new features such as deduplication, compression, QoS, and RAID5/RAID6 Erasure coding.