The new operating system (OS) requirements mean we will see even more instances of vCenter as a VM (virtual machine).
IO DRS provides performance Isolation to VMs in shared storage environments, and it might not be as far away as first thought.
Lately I’ve been doing a lot of work in a lab environment. Some of the work I’m doing is quite important to me so I decided to workout a way I can backup my VM’s onto a backup device. To my surprise this was pretty simple to do.
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.
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.
VMware officially launched their next-generation (version 4) enterprise family of products today under the â€œvSphere 4â€³ name. As Iâ€™ve been doing for the last few major ESX releases, Iâ€™m focusing this post on the storage changes present in vSphere 4.