Browsing Posts in vSphere

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.

VMware vSphere 5.5 has a new update release and now it’s available the vSphere 5.5 U3 on the download site. For the hypervisor part, except the bug issues fixed, the most interesting news are the certification of PVSCSI Adapter, where the PVSCSI adapter is certified for use with MSCS, core clustering and applications including SQL and Exchange, and the support for Next Generation Processors, with the addition of next generation processors from Intel and AMD.

As announced during the VMworld session “INF5123 – Managing vSphere Deployments and Upgrades – Part 2”, VMware Tools 10.0.0 have been released, and (starting from 3rd September) are available in the MyVMware download page as a separated package. Separated and independed from VMware Fusion, Workstation and ESXi virtualization solutions!

VMware Virtual SAN (VSAN) 6.1 was announced during the VMworld US 2015 with some new interesting features. Now it’s finally available on VMware vSphere download page. Considering that it’s implemented at hypervisor level, there isn’t a specific download: you have to upgrade (or download) vSphere 6.0 Update 1. VMware Virtual SAN 6.1 increases data protection options for business-critical environments with the new Stretched Cluster feature providing zero-point Recovery Point Objective (RPO) and enhanced VMware vSphere Replication. Additionally, VMware Virtual SAN 6.1 enables new advanced management and monitoring through deep integration with VMware vRealize Operations and […]

Several months ago VMware announce vSphere APIs for IO Filtering (VAIO) as a solution to implement 3rd Party Software-Defined Data Services in vSphere 6.0. VAIO offers partners the ability to put their technology directly into the IO stream of a VM through a filter that intercepts data before it is committed to disk. It’s a good and efficient idea to implement features like caching or replication without the need of external components (or appliance) or kernel modules like today. But this a partner program (like the Virtual Volumes) and unless partners have not developed this […]

VMware snapshots are widely used for different purpose, but the main reason why they exist in vSphere is to help backup programs: using VADP a backup can start a VM snapshot in order to have a frozen file, copy it (or copy only the changed block with CBT and virtual hardware 7 or greater) and then release the snapshot. Other usage are to have a just in point rollback during patches or big changes, but a recommended practice is to release the snapshot as soon as possible. Large snapshots or broken or invalid snapshots are […]

If you are planning an in-place upgrade of a vCenter Server (the Windows installable version) you have to read carefully the vSphere Upgrade Center resources to avoid possible issues. Of course you can choose to install a new vCenter Server instance a move all to the new one. Maybe could be the right moment to switch to the vCenter Server Appliance (there is also a Flings to move your vCenter Windows data to a VCSA instance). But sometimes it’s not possible and should be preferable an in-place upgrade.

If you have installed (or upgraded to) VMware vSphere 6.0 and you still use the old legacy vSphere client you may have some false positives about VM snapshots. All VMs seems to have some snapshots, also if they don’t (and using consolidate does not fix it, because there aren’t snapshots to be fixed). But this apper only with the Windows vSphere Client:

© 2017 © 2013 vInfrastructure Blog | Hosted by Assyrus