After the official announce at the last VMworld EU, finally VMware vSphere 6.5 is now GA and available for the download. There are several news in the Web client, in new vCenter, in the availability, in VSAN 6.5, in the new security features, new scalability and lot of other stuff.
The new VMware vSphere 6.5, recently available in GA, increase all configuration maximums to new limits (compared to the 6.0 and previous versions). Maybe we can say with no limit, or at least, to be serious, with really huge numbers compared to the actual needs and the existing compunting power. Those new limits are both for scalability aspect, but also to fit with possible performance requirements, considering that a bigger number of business critical applications are going in the virtual environment. For more information see the official docs Minimum & Maximum for VMware vSphere 6.5.
The new release of VMware vSphere 6.5 will finally add some interesting news of the vCenter Server. Not only the virtual appliance (Linux based) version is not fully featured (was almost in version 6.0, but still with the big limit of VMware Update Manager available only for Windows), but now has some features only for this version and the Windows one become the limited version. First sign was the Fling for the migration from a vCenter edition to the VCSA: the official Windows vCenter Server to vCenter Server Appliance (VCSA) Migration Tool which is part […]
VMware best practices for virtual networking, starting with vSphere 5, usually recommend the vmxnet3 virtual NIC adapter for all VMs with a “recent” operating systems: starting from NT 6.0 (Vista and Windows Server 2008) for Windows and for Linux that include this driver in the kernel, and for virtual machines version 7 and later. For those operating systems the choice is normally between the e1000 or the vmxnet3 adapter: the new virtual machine wizard suggest the e1000 for the recent Windows systems, but only because this driver is included in the OSes. Historically there were some […]
When you create a new virtual machine in VMware vSphere (or also on a standalone ESXi) a default virtual hardware is choosed, according with the version of the ESXi. You can choose your own (with the custom wizard) or upgrade later, but note that the virtual hardware upgrade from the vSphere Client will always upgrade to the latest version supported by the host. Otherwise the upgrade from the vSphere Web Client you can choose the different version of virtual hardware.
VMware has announced the End of Availability (“EoA”) of all versions of vSphere Enterprise, vSphere with Operations Management Standard and vSphere with Operations Management Enterprise. The EoA effective date is June 30, 2016. After these dates, you will only be able to purchase these products on an exception basis VMware has also announced price changes for vSphere with Operations Management Enterprise Plus from $4,245 per CPU to $4,395 per CPU, and VMware vCenter Server™ Standard from $4,995 per instance to $5,995 per instance (referenced pricing represents suggested MSRP for the U.S., in USD; regional prices […]
As announced some months ago, the new Virtual SAN (VSAN 6.2) will add new data services making this solution more rich that before. Version 6.1 was announced during the last VMworld editions with some interesting features, including a ROBO scenario. But was still limited in data service: better snapshot technologies, better VMFS, but still some limits and no deduplication, no compression, no erasure coding at all.
VMware vSphere 6.0 has got some issues, like the several related to CBT and data protection, during the first years of its life. Mostly is finally resolved, but you may still have strange issuesespecially during the upgrade procedure (most when you start from a vSphere 5.1 version). I notice, after an upgrade, also a strange behavior with vMotion where live VM migration fails with this error: A general system error occurred: PBM error occurred during PreMigrateCheckCallback: No connection could be made because the target machine actively refused it.
As you probably know VMware vSphere 6.0 had a critical issue con its Change Block Tracking (CBT) implementation that can impact all incremental backup with “VMware native” backup program (all agent-less implementation using the VMware VDAP API). 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. […]
Changed Block Tracking (CBT) is a VMware feature introduced in vSphere 4.0 in order to implement native incremental backup at source level. VMware VDAP uses this technology and so all backup and recovery software designed for VMware use it for speed the backup. But last week a critical issue has been discovered on all vSphere 6 version (included the lates Update 1a) where Changed Block Tracking (CBT) data on ESXi 6 cannot be trusted.
Mastering VMware vSphere Storage book is intented for users who already have some experience with the VMware vSphere platform and want to learn and design VMware vSphere storage solutions and how to troubleshoot vSphere storage issues. The main purpose of this book is monitor and optimize the storage capabilities of your vSphere environment.