- 18 Hot IT Certifications for 2014
- CIOs Opting for IT Contractors Over Hiring Full-Time Staff
- 12 Best Free iOS 7 Holiday Shopping Apps
- For CMOs Big Data Can Lead to Big Profits
Network World - The System Center 2012 modules that we previously tested -- Orchestrator and Configuration Manager -- require forklift upgrades. But the modules we tested this time around - App Controller, Virtual Machine Manager and Data Protection Manager -- are more graceful and, in some cases, more powerful.
The most interesting combination is the new App Controller coupled with Virtual Machine Manager (VMM) 2012. These two modules are peas in a pod. App Controller deploys VMs into fabrics, which can live in private clouds, plain old hypervised locations or public clouds, especially Windows Azure.
Although VMM doesn't deliver the depth of control that you can achieve with the tools that Citrix and VMware provide for their own platforms, you can successfully manage a mixed environment of Microsoft Hyper-V, Citrix XenServer and VMware vSphere with the Microsoft management tools.
The final module, Data Protection Manager, is the least exciting, yet a mainstay of all systems everywhere. Data Protection Manager is comprised of a set of monitored backup components for Microsoft applications and servers. While it was boring, we were thrilled to find that one new feature, a bare-metal restore, not only worked the first time, but presented no adrenaline moments at all.
We installed these and the other modules via the Unified Installer; readers are cautioned not to attempt discrete deployment of these modules. Like other System Center 2012 apps, they require Microsoft SQL Server 2008 R2 and SQL Server, which is recommended to be placed on alternate instances.
The most tempting and overarching feature we wanted to test was the ability to have VMM control over Citrix XenServer and VMware vSphere ESXi infrastructures. We have Hyper-V, but also both of Hyper-V's strongest commercial competitors in the lab and one hefty server instance of all three (See How we did it). We also pestered Microsoft for an Azure account, which the company supplied to us to test cloud control.
We found some Draconian changes had to be made. As an example, we use Network File System (NFS) as a large storage pool hosted on our Dell Compellent SAN. Another NFS pool is located on another server. To use these pools, VMM required us to change them to read/write, which violates a security problem in our workflow. Inasmuch as VMM 2012 essentially takes over workflow (and subsequent controls are administered through App Controller), we moaned a bit and changed the permissions of our pools.
Then, by name, we told VMM where to find our Citrix and ESXi hypervisor metal, and in short order, VMM snacked on all of the live VMs and switched off VM assets within each server type. Each resource type, XenServer and VMware, is then made available. Various tools need to be installed, and there are other considerations to moving VMs around, especially on an inter-fabric basis. A live VM move from one platform to another isn't possible, but it is possible under confined circumstances from one type of fabric to another of the same hypervisor family.