As written in a previous post, starting from vSphere 5.0U1 in a HA cluster the VM Startup & Shutdown ESXi host properties is disabled.
Anyway wasn’t supported, because according with the vSphere Avalability Guide and also the KB 850 (Automating the process of starting and stopping virtual machines on VMware ESX):
The Virtual Machine Startup and Shutdown (automatic startup) feature is disabled for all virtual machines residing on hosts that are in (or moved into) a vSphere HA cluster. Automatic startup is not supported when used with vSphere HA.
So, how it’s possible handle a correct poweron and shutdown sequence of your infrastructure?
Around a month ago I’ve got an issue with VMware SRM 5.0.1 during a test of the Recovery Plan.
In my case the storage was well configured for the replication, but not to permit the reverse reverse replication. So the reprotect task was locked and there was no way to remove this state because also the Delete Protection group was greyed out. If you fix the storage part usually the issue could be fixed in a clean way, but in my case the original LUN was removed and was not possible resume or fix the operation (also if you build a new LUN the ID could not be same). Also a SRM reboot was unsuccessful because the state was in the database.
I’ve looked around but I’ve not found a clean solution, so I’ve simple build a new Protection Group to look in the SRM DB and compare the wrong state with the clean one. With a little of patiance you can find the tables (note that are more than one and both on the production and the disaster recovery site) and fix the values. After that you can finally delete the Protection Group to really clean the database.
Now I’ve notice that there is a recent KB 2032621 (Protection group in vCenter Site Recovery Manager 5.x hangs in reprotecting state during the reprotect task), available from Aug 9 2012, that describe exactly this situation and the same solution.
Finally the results of the contest Voting for the 2014 top VMware & virtualization blogs are out on vSphere-land web site, after the live show where the top 25 were announced. My guess about the first of each category has almost been matched (where my first options in most cases).
With a big surprise also this year I’ve received some votes and vInfrastructure site is number 29 (last year was 40 and two years ago was 54) in the entire rank.
One possible issue after a vSphere 5 upgrade using an in-place upgrade of vCenter Server could appear when you forget to remove the Converter Enterprise plugin (and/or the Guided Consolidation plugin). As you know some products has been removed from vSphere 5, and their plugins may remain in a “orphan” state.
The result of this issue is that you will have a “broken” plugins list (with some plugins that are no more available) and also a wrong vCenter health status, due to some services that are no more existing:
There could some cases where you may have some Windows (Server) completely isolated from the Internet, for example in some appliances or storage solution.
One interesting aspect that learn on Windows products during a DataCore training was that in this case you can have some delay in the user interface, both on the DataCore GUI, but also on the Windows one.
In the previous post I’ve described how System Center VMM 2012 can handle and manage some storage compatible with the SMI-S interface.
Now I’ll explain how connect an old Dell PowerVault MD3000i (but of course works also with recent models) using the SMIA (SMI Application) package that actually is not available as a standalone package, but it’s only included in the VMware vCenter Center integration (MD Storage Array vCenter Plug-in). You can simple adapt it to work also for SCVMM.
One of the several interesting topics discussed in the recent event Cloud Communities Day, held on Monday 22 in Milan and with the presence of various communities, as well as analysts and academics, was which could be the most interesting type of cloud.
If we limiting to the three basic types: Infrastructure as a Service (IaaS), Platform as a Service (PaaS) or Software as a service (SaaS)… Which one could be the more interesting? As often “it depends” could be the answer, but paradoxically, many have very clear opinions about it (though it is not said that all fit together …).
One trend in the last year(s) is that the virtualization ecosystem is growing outside the boundary where was born: historical partner vendor of VMware now are extending their solution to other hypervisors, and also also new products are designed to managed a more complex virtual environment. This was also called “Hypervisor Agnosticism” in a VKernel post.
We do not talk about interoperability across different hypervisors, but simple use same tools, especially for management, monitoring and data protection, for more type of products.
Does it make sense? For a single customer maybe not… have multiple environment could be an extra cost (also if some tools may be the same, VM format, knowledge, admin tasks will be different for each product) that could be a non sense for small and medium company. But for system integrator this could really be useful because you can push on few products and re-use part of your knowledge and practices. And of course it make sense for the vendor of this multi-platform solutions because they can extend their business to new market.
Microsoft Windows Dynamic Disks (or Dynamic Volumes) are an abstraction layer (introduced in Windows 2000) over the partitions (similar to the LVM layer on Linux environment) to decoupled the volumes (with their NTFS data) from the disk partitions and have a greater flexibility, like hot-extend a volume by simple add new partitions (but also several other advantages).
But in a virtual environment there are other way to handle disk flexibility, like hot-extend a virtual disk at hypervisor level (for VMware this feature was introduced in VI 3.5U2)… so there is no need to use dynamic disks at guest level. The only requirement is that the guest file system also support a hot-extent operation: this is available from the GUI in recent versions of Windows (from Vista, aka NT 6.0), and in a limited way (not, without use 3rd part tools, for OS disks) from the command line (with the diskpart command) also in some previous versions.
In my interview with Sakthi Chandra (NexentaVSA for View Director), during the last Open Storage Summit EMEA, we have talk about the Nexenta approach of the storage for a VDI environment. Their product has been developed from a collaboration with VMware and some aspects sound familiar: for example the overview of the VSA deployment and design seems similar to the VMware VSA, except the scalability limit (that is limited to max 3 host for the VMware solution). But I don’t want talk about the product, yet (I prefer dedicate it a post, when I will be able to make some test), but about the approach: using local storage instead of shared storage.