Like everyone else, I have been reviewing the Release Notes for the latest Update 1 release of vSphere 4.1, but I decided to point out specific fixes that will make full image VM backups better for everyone. Note that I work for Veeam Software, but the fixes I am referring to are all VMware resolved issues that surface from time to no matter what backup solution you use. There are numerous other fixes and impovements in the U1 release, but, since most of my world is backup these days, these particular items â€œpopped outâ€ at me.
As my friend Stu Miniman pointed out, a recent VMware video suggests the company is about to jump into networking in a big way. Dubbed “vFabric,” this new offering would be a generic hypervisor for virtual network devices, from load balancers to security appliances, and would presumably be integrated with the existing vNetwork Distributed Switch functionality. This appears to be more than just a generic version of what Cisco already uses for their Nexus 1000V!
You may have assumed from my previous post on VPLEX that I am negative towards the concept of storage federation. That couldnâ€™t be further from the truth. In fact, ever since I was involved in deploying ESX onto enterprise storage infrastructure (some 4 years ago), Iâ€™ve been waiting for the day true federation would arrive. Hereâ€™s why.
Over the past few years Iâ€™ve been asked to troubleshoot and explain why cloning a virtual machine (VM) from a master template would take a longer time than expected more than once.
A recent announcement from Likewise Software hints that future versions of VMware vSphere may make it easier for companies to manage ESX hosts using Active Directory (AD) credentials. vCenter, which runs on a Windows Server operating system, is commonly added to an AD domain already, but special configurations are necessary to authenticate ESX host access with domain credentials today.
The vSphere Enterprise Plus vNetwork Distributed Switch (vDS) has been heralded as an administratorâ€™s time saver and single point of virtual networking configuration and visibility across many ESX/ESXi 4 hosts. However, the vDS presents some administrative challenges unique from the traditional vNetwork Standard Switch (vSS) that admins are used to. In this post Iâ€™ll first cover (with the help of a several others) general VM and vCenter vDS networking issues, but along the way Iâ€™ll explore thoughts about designing around a vDS for keeping vCenter as a VM.
I've been asked to take a look into the Hot-Add Memory and CPU features which are available with vSphere 4. The concept seems pretty useful and straight forward, but what isn't is the list of Operating Systems that support these features. There doesn't seem to be a definitive list. Either that, or I should have […]
My new DroboPro arrived this week and so far I’m less than impressed. Â As you know, I already haveÂ had aÂ generation 1Â DroboÂ forÂ some time. Â It has been a great device, doing exactly what I wanted. Â After winning a second standard Drobo at Tech Field Day, I paid for the upgrade to the DroboPro in anticipation of a […]
Coming out of stealth at VMworld 2009 in San Francisco, startup EvoStor exemplifies this new virtualization-optimized storage concept. Taking existing storage concepts like scale-out grid and automated storage layout, EvoStor’s offering is designed exclusively to support the VMware vSphere platform.
This weekend I finally had the chance to catchup on some of the new storage features released as part of vSphere 4.0, there are quite a few changes to cover, some of them quite exciting.