Windows Virtualization Team Blog : cross-platform management

Microsoft and Red Hat Complete Cooperative Technical Support

porourke — Wed, 07 Oct 2009 10:00:00 GMT

Hi, I'm Mike Neil, general manager of Windows Server and Server Virtualization. Back in February we announced our work with Red Hat to enable cooperative technical support for virtualized environments. I'm excited to announce we've completed certification in each others' programs! Customers now can deploy Microsoft Windows Server and Red Hat Enterprise Linux and a range of select applications, virtualized on Red Hat and Microsoft virtualization products, knowing that the combined solutions will be supported by both companies.

Here are the details:

Red Hat Enterprise Linux 5.2, 5.3, 5.4 have passed cert tests when running on Windows Server 2008 Hyper-V, Microsoft Hyper-V Server 2008, Windows Server 2008 R2 Hyper-V, Microsoft Hyper-V Server 2008 R2. See more at RedHat's certified hardware site.
Windows Server 2003/ Windows Server 2008 / Windows Server 2008 R2 are validated to run on Red Hat Enterprise Linux 5.4, using their KVM-based hypervisor. See more at Microsoft Server Virtualization Validation Program site.

Beyond the OS, both companies have select applications that would receive technical support when running on certified server virtualization software. The Microsoft applications can be seen in KB article 957006. On the Red Hat side, you can now run JBoss Enterprise Middleware within a virtual machine guest on Hyper-V and receive coordinated technical support. This is a step forward for enterprise customers, hosting providers, systems integrators, and those who want to offer their customers the top x86 operating systems to run applications.

And as mentioned in my February post, Microsoft provides the systems management tools, via System Center suite, to manage physical and virtual IT systems and applications, including non-Windows software such as Red Hat Enterprise Linux. We do a world-class job of managing Red Hat Enterprise Linux, so customers can use one pane of glass to manage their legacy Unix and Linux environments together with their Windows Server environments. Read more here, but here's an excerpt from the website:

System Center Operations Manager 2007 R2 supports monitoring of the following operating systems:

HP-UX 11i v2 and v3 (PA-RISC and IA64)
Sun Solaris 8 and 9 (SPARC) and Solaris 10 (SPARC and x86)
Red Hat Enterprise Linux 4 (x86/x64) and 5 (x86/x64) Server
Novell SUSE Linux Enterprise Server 9 (x86) and 10 SP1 (x86/x64)
IBM AIX v5.3 and v6.1 (POWER)

The work with Red Hat is just one of numerous examples of the way we're helping customers and partners running mixed IT environments with Windows and open source technologies. A little over 2 months ago, we announced that the Linux integration components (ICs) for Hyper-V would be contributed to the Linux Driver Project and the drivers licensed under GPLv2. The community has embraced us and helped ready our submission of the drivers for inclusion in the kernel. It was great to see this support and a couple weeks ago what started as our first submission made it into the official kernel tree. The Linux IC code that we contributed is in the staging phase for the next kernel release (2.6.32). See here.

I'll close by saying that Microsoft and Red Hat have competed for customers and partners for some time now, and as platform vendors continue to compete in the marketplace. While the announcement today extends our ongoing technical support collaboration, these agreements do not address, nor do they include provisions relating to patents, open source licensing or other IP matters. We look forward to supporting our joint customers and providing unparalleled solutions for Microsoft's customers and partners!

Thanks,

Mike Neil

Strong end to end management required for Virtualization to be successful (VMworld day 2)

vtango — Wed, 02 Sep 2009 16:39:00 GMT

I am pleased that it is being acknowledged by VMware (evidenced by their keynote announcements yesterday on the vCenter additions) that for a strong virtualization platform a complete end-to-end solution is required. We agree completely!! We at Microsoft provide solutions for configuration/change management, operational/health monitoring, virtual machine management and data protection and have been doing so for a while now. Just to get some perspective I dug up the release dates for our management software (I have trimmed the list a bit for readabilityJ). From the table below its clear that our management lifecycle experience goes back many many years. It is great to see VMware finally acknowledge this and is attempting to now build a solution that spans some aspects of this end-to-end management. We welcome this.

Products	Date
Operations Manager 2000 Enterprise Edition	3/1/2001
Operations Manager (MOM) 2005	11/24/2004
System Center Operations Manager 2007	6/23/2007
System Center Virtual Machine Manager 2007	11/29/2007
System Center Virtual Machine Manager 2008	1/29/2009
System Center Virtual Machine Manager 2008 R2	8/2009
System Center Data Protection Manager	10/22/2005
System Center Data Protection Manager 2006	10/22/2005
System Center Data Protection Manager 2007	12/15/2007
System Center Data Protection Manager 2007 Service Pack 1	12/19/2008
Systems Management Server 1.2 Standard Edition	10/23/1996
Systems Management Server 2.0 Service Pack 3	2/13/2001
Systems Management Server 2.0 Standard Edition	4/1/1999
Systems Management Server 2003	1/20/2004
Systems Management Server 2003 R2	8/25/2006
Systems Management Server 2003 Service Pack 3	4/27/2007
System Center Configuration Manager 2007	11/29/2007
System Center Configuration Manager 2007 R2	11/29/2008
System Center Configuration Manager 2007 Service Pack 1	5/21/2008

Over the past two days I have had the opportunity to interact with large number of customers and partners (so much so that I could barely make it to one of my sessions yesterday). Universally, I have heard that customers are looking to have a solution that provides them end-to-end visibility/monitoring and control over their infrastructure spanning all layers from the hardware, virtualization, OS and applications. The depth and breadth of our experience and products provided by us and our partners provides customers with the tools that they need for a responsive and effective IT infrastructure.

Vijay Tewari

Principal Program Manager, Windows Server Virtualization

Update: What you won't see at VMworld 2009

porourke — Thu, 27 Aug 2009 02:30:00 GMT

This post is for the readers out there that will be attending VMworld, or have colleagues attending VMworld.

There’s been some speculative statements made in the press and blogs in the past 24 hours, so I want to try to set the record straight:

1. Microsoft will be exhibiting at VMworld 2009. Can't wait! We have a 10x10 booth, #2422. If you have a chance, please stop by booth. It's right next to the Blogger lounge. See more below.

2. Unlike prior VMworld conferences, we’re no longer allowed to sponsor the event. We can only be an exhibitor. Why? Let's look at excerpts from VMworld’s rules (my highlights):

VMworld 2009 Sponsor and Exhibitor Rules and Regulations

Booth/Session Demonstrations (pg. 2)

Sponsors and exhibitors must market or demonstrate products on the exhibition floor and in the sessions

which are complementary to VMware products and technologies. Complementary products and services are

defined as products/services that do not overlap/substitute with VMware’s products/capabilities, and help

expand the reach and solution scope of VMware’s capabilities solely as deemed by VMware. All sponsors

and exhibitors must adhere to following guidelines in regards to booth demonstrations (please also review

the “Promotion, Giveaways, Contests” section below):

Eligibility (pg. 4)

To sponsor or exhibit at VMworld a company must be a VMware partner in good standing in our TAP,

Strategic Global Partner or VIP Partner Programs. Companies that are not VMware partners may be allowed

to exhibit at VMworld under exception by VMware.

Both sides (us and VMware) agreed that, apart from the features in System Center Virtual Machine Manager that manage ESX, Microsoft products aren’t complementary to VMware’s products. We discussed and confirmed their intent of these clauses in early August, and had a follow-up Aug. 11 email from VMware, that reads in part:

As I mentioned, the rules require all exhibitors to market and demonstrate products that are complimentary to VMware products and technologies. We are open to reviewing any proposals for complimentary positioning of Microsoft products and demos at the show…

As a result, based on the clause above, phone/email with VMware employees, we don't believe we have the right to demo our products in the booth. This decision runs counter to Microsoft’s geek culture, as you can imagine, but we've also become more pragmatic over the years :-).

So what is Microsoft doing at VMworld?

We’ve learned over the course of 4 years attending VMworld (first was Vegas 2005) that there are many attendees who use, admin, manage, sell, support Windows Server, SQL Server, Exchange Server, Windows XP/Vista, System Center, etc. They want the opportunity to engage and receive information from Microsoft virtualization experts. So we’ll have Microsoft virtualization experts in the booth. These experts will be there to answer your questions. They’ll also be Tweeting about their experiences and impressions as they talk to customers and attend sessions. I encourage you to follow them on Twitter - see the table below for their usernames.

Expert in	Name	Twitter Username
Disaster Recovery, Backup	Allen Stewart	dynamic_dc
Desktop Virtualization	Ben Armstrong	virtualpcguy
App & Desktop Virtualization	Jeff Johnson	JJ_VDI
Virtualization Management	Stuart Schaefer	Sshaffer_MS
Cloud	Isaac Roybal	DDACloudGuy
Business value	Edwin Yuen	edwinyuen
Workloads, partners, licensing	Kenon Owen	MS_Int_Virt
Server Virtualization	Vijay Tewari	vtango

We’ll also have two customers in the booth at different times. I’ll be there. See you there!

Patrick O’Rourke

What you won't see at VMworld 2009 - a demo of SCVMM 2008 R2

porourke — Tue, 25 Aug 2009 03:32:00 GMT

Ordinarily it'd be great news that we RTM'd System Center Virtual Machine Manager 2008 R2 ahead of schedule, so close to the RTM of WS08 R2 Hyper-V and one week before VMworld conference. You can't beat the timing of it all. And the ~10,000 beta testers of SCVMM08 R2 are a big part of why we were able to deliver a high-quality release in the time we did. Some of the early adopters included Continental Airlines, Lionbridge Techologies, Sporton, Indiana University Auxilary IT and MaximumASP. Thanks to all!

But unfortunately, next week at VMworld 2009 we can't show SCVMM 2008 R2, or any other products, in our booth. You've probably read about it. In short, it's their show, it's not an industry show, and they set the rules. So we'll make the best of it; always lots of Microsoft customers and partners on the floor. Stop by the booth to meet some of the best/brightest minds at Microsoft.

As for the RTM of SCVMM 2008 R2, Zane summarizes his thoughts here. Kerim blogged about upgrade path to R2 from SCVMM 2008. See here. And on May 11, Vishhwa provided some details on features of SCVMM 2008 R2 here.

As Cheng wrote in his blog (I can't say it any better)

Go download a trial and give it a try, go get it now, and unleash the virtualization power that Microsoft brings to you.

Patrick

SCVMM and VMware ESX management

porourke — Tue, 10 Mar 2009 05:43:00 GMT

The threat of virtualization sprawl. That was a theme my colleagues heard last week at IDC's "Directions" conference in San Jose. And true to IDC's form, they backed up their predictions with some numbers. Here's an excerpt from one article:

Virtualization has often been seen as something of a magic bullet to this problem, promising to consolidate a number of low-utilization servers onto a single piece of hardware. But the average number of virtual machines per server is only five, Bailey noted, with that number going to eight by 2012. So much for the vision of consolidating dozens of servers onto one machine. More important, though, was that IDC found that just going from five virtual machines to eight means there will be 100 million new servers by 2012, and "all of them still need to be managed." That's a problem, she said, since the tools to do this are not keeping pace.

Our customers have referred to this issue as "islands," referring to the need for different management tools, interfaces, etc. to manage their heterogeneous environment. After all, customers and partners tell us, they're trying to manage services, no matter if the applications run on Windows or non-Windows, physical or virtualized.

For those of you in that last camp, like Atlanta Journal Constitution, Mamut and Maxol, you know that Microsoft and some other systems management vendors are creating tools to keep pace with heterogeneous hypervisors and VMs, and as well traditional physical systems and non-virtualized applications. System Center is one such management tool; VMware vCenter isn't (yet, according to Alessandro). To elaborate on this point, check out RakeshM's latest blog post here. Here's an excerpt from his intro:

Put simply, people want to use a single primary console for day to day management of virtual machines across multiple hypervisors so we went after this problem. As a result, multi-hypervisor management via SCVMM 2008 has proven to be enormously popular with customers and partners alike.

Rakesh sheds light on VMware's concocted "demos" (nice touch using Microsoft exec names "muglia" and "ballmer" as host names) and conjecture. Rakesh summarizes his post with the following:

If you are thinking of using SCVMM 2008 to manage VMware because you have a mixed environment (and we have many many customers who are doing just that), keep in mind that SCVMM does not require you to uninstall or remove VMware Virtual Center from your environment. In fact, you have to keep Virtual Center around because VMware does not expose some APIs (like Vmotion) through ESX. We’re a manager of managers so it is nearly risk free to try it out and make up your own mind about how effective we are.

Oh, and by the way, Rakesh also says that the beta of SCVMM 2008 r2 will be coming this month.

I can't wait to see what demos VMware concocts next to counter the physical/virtual management sales and marketing by HP, IBM, CA and BMC. HP's Peter Spielvogel tips his hand here with HP's reaction. I'm sure this reaction will become stronger once VMware crosses the line to be more competitor than partner.

Patrick

Microsoft and Red Hat Cooperative Technical Support

porourke — Mon, 16 Feb 2009 00:00:00 GMT

Hi, I’m Mike Neil, general manager of virtualization at Microsoft. It’s been a while since I’ve blogged here, but today’s post is worth a read.

Ever since we released Windows Server 2008 Hyper-V and Terminal Services, System Center Virtual Machine Manager 2008 and Microsoft App-V 4.5 last year, customers and partners have been getting huge value from server consolidation projects, have been able to increase business continuity at much lower costs than with VMware, and have decreased the time and cost required to deliver applications to end users. And while doing this, they’ve been able to use a familiar set of system management tools for both their virtualized and non-virtualized systems and applications across the datacenter and desktops. In fact, Chris from Kroll Factual Data wrote about his DR project on this blog last year. So in many ways I’m pleased that we’ve been able to help so many customers and partners break down the barriers to enterprise-wide virtualization.

But until today there’s been one barrier, not product related, that we haven’t been able to overcome to meet customer and partner demand: the ability to run and support Red Hat Enterprise Linux within a guest VM on WS08 Hyper-V and Hyper-V Server 2008. For all of those who have emailed me, my colleagues and your Microsoft account teams and partners, I’m pleased to say that today is the first big step to delivering that support.

Microsoft and Red Hat recently signed agreements to test and validate our server operating systems running on each other’s hypervisors. Customers with valid support agreements will be able to run these validated configurations and receive joint technical support for running Windows Server on Red Hat Enterprise virtualization, and for running Red Hat Enterprise Linux on Windows Server 2008 Hyper-V or Hyper-V Server 2008. You can see Red Hat’s news release here, and watch a public webcast discussing this news.

So how are we doing this? Red Hat has joined Microsoft’s Server Virtualization Validation Program, and Microsoft is now a Red Hat partner for virtualization interoperability and support. Microsoft will be listed in the Red Hat Hardware Certification List once we’ve completed the Red Hat certification process in H2. In addition to the agreements, Microsoft will publish Linux Integration Components for RHEL when the testing and validation is complete. The folks at Red Hat tell me that they’ll provide WHQL [Windows Hardware Quality Labs] drivers for a variety of Windows Server versions. So not only will you get cooperative technical support, you’ll also get high-performing enlightened VMs.

You might also be wondering – when can I get this? I don’t have a calendar date for you just yet, but I know that validations are now underway and will be as comprehensive as possible. Each company is doing its respective validations separately with the first validated configurations available at different times later this year.

And I’m sure you’re wondering about tools to manage those RHEL guests running on Hyper-V? Good news there. We know virtualization projects aren’t successful unless the right management tools are in place to manage both the virtual and physical. System Center Operations Manager 2007 R2, which will be released in calendar Q2 2009, includes cross platform monitoring and support for Red Hat Enterprise Linux server versions 4 and 5 so that you can manage the applications and OS in the guest VM. Other Linux distros will be supported, too. This will allow you to monitor end-to-end data center applications that are distributed across both Windows Server and RHEL, whether these servers are physical or virtual.

I suspect that you’re now as excited as me about these agreements. But maybe you’re wondering … what took so long? That’s a fair question given the number of customers and partners that have been asking for this result.

Let me say that I’m sure everyone reading this can appreciate the distance between Microsoft and Red Hat is measured in more than just the 2,900 miles between Redmond, WA and Raleigh, NC. Microsoft and Red Hat have competed for customers and partners for some time now and as platform vendors continue to compete in the marketplace. Yet, our customers have told us that technical support for server virtualization is an area we must work together. And that’s certainly understandable when you consider the fact that roughly 80% of the primary guest (in a VM) operating systems on x86 servers today come from Microsoft or Red Hat. Indeed, customer demand is the main driver behind these agreements with our competitor.

One thing I’d like to point out: since these agreements are focused on joint technical support for Microsoft and Red Hat’s mutual customers using server virtualization, the activities included in these agreements do not require the sharing of IP. Therefore, these agreements do not include any patent or other IP licensing rights.

I want to leave you with the point that Microsoft is pragmatically focused on helping customers and partners be successful in a heterogeneous IT world. We’re committed to enable and support interoperability with non-Windows OSes. As a result we take a multifaceted approach to interoperability, be it customer-driven industry collaborations, such as this Server Virtualization Validation Program, be it standards that promote common technologies (e.g., device virtualization through the PCI-SIG), or proactive licensing of IP (e.g., Microsoft’s Virtual Hard Disk format, Microsoft’s Hypercall APIs), or the creation of technologies that bridge different systems (e.g., protocol licensing and documentation, Integration Components for Linux). In the end, customers with mixed IT environments expect it all to work together and today’s announcement is one way of making that happen.

Below you can read an FAQ that is also on Red Hat's website.

Mike

FAQ

Q1: Is this a joint agreement between Red Hat and Microsoft?

A1: It’s not a joint agreement. Red Hat has signed an agreement to join Microsoft’s Server Virtualization Validation Program, while Microsoft has joined Red Hat’s Virtualization Certification Program . Microsoft will be listed in the Red Hat Hardware Certification List once it has completed the Red Hat certification process.

Q2: It seems like customers should have had this type of support some time ago. What took so long to provide customers with technical support?

A2: Microsoft and Red Hat started hearing requests for bilateral validation soon after Microsoft’s Server Virtualization Validation Program went live in June 2008. Both companies quickly agreed to work together; finalizing the details around comprehensive, coordinated technical support has taken some time. As a result, customers will be able to confidently deploy Microsoft Windows Server and Red Hat Enterprise Linux, virtualized on Microsoft and Red Hat hypervisors, knowing that the solutions will be supported by both companies.

Q3: Are there other components of the deal that have not been disclosed yet?

A3: No. The agreements are specific to establishing coordinated technical support for our mutual customers using server virtualization. The agreements have nothing to do with patents, and there are no patent rights or other open source licensing rights implications provided under these agreements. The agreements contain no financial clauses other than test fees for industry-standard certification and validation.

While Microsoft and Red Hat continue to compete in the marketplace, customers have told us that technical support for server virtualization is an area where we must work together. Now we have agreements to test and coordinate technical support and provide customers with a new level of mutual support between Red Hat Enterprise Linux and Windows Server for their heterogeneous IT environments.

Q4: What versions of Red Hat Enterprise Linux and Red Hat Virtualization will be validated, to what versions of Windows and Hyper-V?

A4: Validations are now getting underway, and are planned to be comprehensive. Each company is doing its respective validations separately, with the first results expected later this year.

As a participant in Microsoft’s Server Virtualization Validation Program, once Red Hat submits test logs indicating that Windows Server 2008 runs properly on the Red Hat Enterprise virtualization, the specific version of Red Hat used in the tests along with parameters of the virtual machine tested will be posted on Microsoft’s Server Virtualization Validation Program website. At that point customers can confidently deploy Windows Server 2008, Windows Server 2003 SP2, or Windows 2000 Server SP4 and later and receive coordinated technical support from both vendors.

Red Hat Enterprise Linux SVVP completion is planned for calendar H2 2009.

Microsoft currently plans to validate Red Hat Enterprise Linux 5 as a guest on Windows Server Hyper-V. Windows Server 2008 Hyper-V (all editions) and Microsoft Hyper-V Server 2008 will now support uni-processor virtual machines running:

· Red Hat Enterprise Linux 5.2 (x86)

· Red Hat Enterprise Linux 5.2 (x64)

· Red Hat Enterprise Linux 5.3 (x86)

· Red Hat Enterprise Linux 5.3 (x64)

Q5: How do customers get support for the validated solutions? Who do they call?

A5: Customers with valid support agreements with both companies call either Microsoft or Red Hat to have their issues resolved. If the first vendor contacted cannot resolve the issue they will work with the other vendor to come to a resolution for the mutual customer.

Q6: What level of support agreement is required from Red Hat and Microsoft for a customer to receive support when running RHEL on Windows or Windows on RHEL?

A6: Customers with current Microsoft support agreements for Windows Server 2008 will be entitled to obtain support under this agreement. Where an existing agreement is not in place, customers can identify their willingness to purchase ‘per-call’ support.

Any customer with a valid Red Hat Enterprise Linux subscription, and using Red Hat Enterprise Linux 5.2 or 5.3 guests will be entitled to support under this agreement.

Q7: How do these agreements compare to agreements you both have with VMware and/or Citrix?

A7: There is no change in Microsoft's or Red Hat's relationship with VMware. Note that both Windows Server and Red Hat Enterprise Linux can be deployed on VMware ESX. Red Hat doesn’t have any virtualization agreements with Citrix at this time. Both VMware and Citrix have product configurations that have been validated through the Microsoft Server Virtualization Validation Program.

Q8: How do I find out what validations have been completed?

A8: Validations will be posted to the respective Microsoft and Red Hat web sites:

http://www.redhat.com/rhel/compatibility/hardware/

http://www.windowsservercatalog.com/svvp.aspx

Q9: Who will be the primary beneficiary of this agreement?

A9: The primary beneficiary of this agreement will be Microsoft and Red Hat customers. Of course, a secondary beneficiary will be the virtualization ecosystem because it will be more useful to customers, leading to wider deployments and faster technology development.

Guest Post: Virtual Eggs in One Virtualization Basket?

porourke — Tue, 27 Jan 2009 09:43:00 GMT

Hi, my name is Dave Demlow and I am the Chief Technology Officer at Double-Take Software.

Double-Take Software has been a leading provider of data replication and failover technologies for Microsoft Windows Server and applications going all the way back to Windows NT 3.51. So like many of you, we’ve seen many changes in the role that Windows Servers play in the enterprise and in the increased requirements for the availability and protection of Windows-based workloads. Hyper-V will accelerate those changes but at the same time make it much easier and more cost effective than ever to provide those higher levels of availability to an even broader range of workloads.

As Jeff Woolsey highlighted so well in his post on Hyper-V Quick Migration, “Virtualization actually creates a major problem: single point of failure.” And if the problem with that isn’t crystal clear,” If that virtualization server goes down and I don’t have a HA solution in place, I will lose my job.”

The hypervisor is only one of many possible points of failure to be concerned with. If the shared storage in a Hyper-V cluster is unavailable due to a site failure, power failure or corruption, ALL of your workloads that rely on that storage or site will also be down.

Fortunately, Windows Server 2008 provides two enabling technologies, Hyper-V and Failover Clustering, that when used with 3^rd party products such as our GeoCluster for Windows or Double-Take for Windows software can create clusters of Hyper-V servers that offer redundancy through replicated storage. Optionally, these can be geographically dispersed to maintain availability of virtualized workloads even when entire sites or datacenters are inoperative also providing for off-site disaster recovery. These are sometimes referred to as “multi-site” or “stretched” clusters and our customers often simply refer to them by our brand name GeoCluster.

As an example, with our GeoCluster product, multiple Hyper-V nodes in a cluster could store independent replicas of each protected virtual machine that are continuously updated as the virtual machine is changed. An example cluster might have 4 nodes in New York, Chicago, LA and Seattle. On the New York node, 10 virtual machines are running and replicating to the other 3 nodes. In LA, 5 other VMs are running in LA but only replicating to Chicago and so on. In the event of an unplanned outage, virtual machines could automatically failover to any site with a replica in a pre-set priority order…perhaps the VMs in New York failover to Chicago first, then Seattle then to any surviving site. The flexibility with software-based replication technologies is extensive, allowing replication between different types of servers, between different storage technologies and allowing very granular selection of which VMs should be replicated and which should not, even on the same disk or LUN.

While SANs and iSCSI storage are supported in a GeoCluster, cluster nodes can even use direct attached storage of nearly any type. VMs normally stored on high performance Fibre Channel or SAS drives could be replicated to a node with internal SATA drives to optimize costs. Hardware independence and flexibility are two key benefits of many software based replication and failover solutions such as Double-Take and GeoCluster software.

While the emphasis on multi-site clusters is often to maintain availability of VMs across unexpected site outages, it is also possible to use our GeoCluster product to perform planned migration of running virtual machines with minimal downtime, also known as Quick Migration. This process works exactly the same as it would between cluster nodes using a shared disk with the additional step that “under the hood” the saved memory state on the previous node is automatically replicated to the destination node before the VM is “resumed” and continues running exactly where it was previously.

In conclusion, if you are concerned about the availability of the virtual eggs in your virtualization basket, consider implementing Windows Server 2008 Hyper-V along with 3^rd party multi-site cluster solutions to provide complete infrastructure and datacenter redundancy to maintain availability of your virtualized workloads across server, storage or even site level disasters.

Dave Demlow

DPM for data backup/recovery of virtualized apps and environments

porourke — Tue, 13 Jan 2009 20:47:00 GMT

We want to congratulate the Microsoft Storage Solutions team for releasing Service Pack 1 for System Center Data Protection Manager 2007.

SP1 for DPM 2007 brings some great new capabilities for protecting Hyper-V environments. Most notably, of course, is the ability to protect guests within Hyper-V environments, often without downtime (for those guests running a Windows operating system that supports VSS). Also new for DPM with SP1 is the ability to run the DPM server on the Hyper-V host itself, so that the DPM server can protect the guests from the host viewpoint, within the same physical server - to disk, to tape and even to the cloud.

And unlike other (shall-not-be-named) virtualization platforms’ backup mechanisms, DPM does not require a SAN and does not require 3rd party backup software or add-ons. It’s an all Microsoft backup and recovery solution for Microsoft’s virtualization platform.

For more details on the SP1 release for DPM 2007, check out:

· Bala’s executive viewpoint on DPM 2007 sp1

· Some early SP1 customers are also blogging about their experiences and you can see at these links – ICON & Convergent Computing

· A feature overview of DPM SP1 is located here

The DPM folks have dedicated resources on “How to protect virtualized environments with DPM 2007” – http://www.microsoft.com/DPM/virtualization. And a very cool podcast showing how to protect Hyper-V with DPM 2007 SP1 - http://edge.technet.com/Media/DPM-2007-SP1-Protecting-Hyper-V

Congrats to the DPM crew – and nice job on backing up Hyper-V !!!

Patrick

Guest post: Moving VM automation and inventory beyond Excel files

porourke — Wed, 19 Nov 2008 10:28:00 GMT

Hi, I’m John Suit, CTO and principal founder of Fortisphere, which is a member of the Microsoft Startup Accelerator Program.

In this tough economy, the cost savings of virtualization are driving faster adoption – and the introduction of Microsoft Hyper-V is exposing more companies, large and small, to the benefits of this deceptively simple technology.

In fact, from what we’ve seen, the scale of deployments has grown tremendously in the past year. When we did market research a year ago, people were calling their 90-VM environments “large.” Today, similar-sized deployments are “really, not very big.” Today, 300-400 VMs are commonplace, with a mix of Microsoft Hyper-V and others platforms running together.

So, the deployment of VMs has become nearly routine. But, with scale, another problem has emerged: management of the environments. Today, we mostly see folks provisioning VMs and mostly ignoring them until someone calls with a problem, at which point they scramble to prove that the virtual infrastructure is not to blame. Inventories of VM are either kept in Excel files or outsourced to teams of inventory-keepers. Change alerting, reclamation of idle VMs, and a whole bunch of other functions are untouched, as most folks are too busy with provisioning and troubleshooting.

A little automation can go a long way to changing reactive to proactive. Our customers have found that setting rules like a Time-to-Live for a VM can ease the reclamation process. Alerting – and even blocking – of certain configuration changes means fixing a change before it becomes a problem. Setting these rules by VM owner or functional group makes it intuitive and aligned with the way virtualized environments are built – to deliver infrastructure to the application owner.

Fortisphere provides the automation needed to operate a virtual environment. Fully cross-platform, the Fortisphere solution enables administrators to tag and track each VM, set rules to govern change management, alert on events, troubleshoot issues, and even remediate in real time. With full reporting capabilities, upcoming integration with Microsoft System Center VMM, and a focus on automating the daily challenges of operating a growing virtual environment, Fortisphere’s solutions have reduced the time, effort, and cost of virtualization for many customers.

John Suit

Listen to John’s podcast interview in DABCC Radio.

New VDI, Management Technology Announced

porourke — Tue, 04 Nov 2008 09:17:00 GMT

A few items to call out.

First up is Manlio's post about the renaming of Terminal Services - it'll be known as Remote Desktop Services in Windows Server 2008 R2 -- and the new VDI features. Here's an excerpt:

The key here is that RDS in Windows Server 2008 R2 makes the new server OS the ideal platform for companies to implement a centralized desktop strategy and for partners to provide additional innovation. It introduces the new Remote Desktop Connection Broker – an expansion of the Session Broker in Windows Server 2008 – which provides the administrator with a unified experience for setting up user access to both virtualized desktops (running as a full Windows client OS on top of Microsoft’s virtualization infrastructure) and traditional session-based remote desktops. Together with Hyper-V and System Center Virtual Machine Manager, the Remote Desktop Connection Broker enables a VDI solution for low-complexity, departmental environments, and a platform for partners who are delivering rich, extensible solutions where heterogeneous client support is a prerequisite, and when enhanced management and scalability is a requirement. The Remote Desktop Connection Broker it complements other, shared RDS infrastructure components in Windows Server 2008, such as Remote Desktop Web Access or Remote Desktop Gateway. With the Remote Desktop Connection Broker, partners will find an extensive set of APIs that will allow them to continue innovation and deliver added value to customers.

Second, over at the System Center team blog, Paul announced the beta of System Center Operations Manager 2007 R2. Check out the video with Barry Shilmover. Here's an excerpt:

The beta itself will include a number of enhancements including the cross platform capabilities that we originally released as separate beta at MMS earlier this year, some enhanced service level monitoring reports and dashboards, and a number of UI improvements that include a new version of the management pack authoring console. Combined these will provide a lot of opportunities for organizations to make their data center and server management activities more cost effective and efficient.

Last item is a recent CRN magazine interview with Microsoft GM Mike Neil (who's blogged here before). It's about 6 minutes long. See below or go here.

Patrick