My evil doppleganger

In all seriousness – there’s a ton of going on at EMC focused on Hyper-V, and while I don’t want to help him too much, I do want to make the introduction :-) I mentioned him earlier – Adrian Simays.   Adrian is “Mr Hyper-V” at EMC – and has now been gathering his strength to emerge publicly.   You can read up on EMC stuff focused on Hyper-V here:  Virtual Winfrastructure There’s a great post on all the technical docs on how to leverage Hyper-V on EMC kit which I’m grabbing the links. EMC Symmetrix with Microsoft Hyper-V Virtualization EMC CLARiiON with Microsoft Hyper-V Server Best Practices: Using EMC Celerra IP Storage with Microsoft Hyper-V R2 over iSCSI EMC Replication Manager for Virtualized Environments EMC Blueprint:  Backup and Recovery for Microsoft Sharepoint Server Enabled by EMC CX, Replication Manager and Microsoft Hyper-V EMC Backup and Recovery for Microsoft Sharepoint Server with Hyper-V EMC Networker: Complete Protection for Microsoft Hyper-V Proven Solution: EMC Backup and Recovery for Microsoft Exchange 2007 Enabled by EMC CX, Replication Manager and Microsoft Hyper-V using iSCSI Reference Architecture: EMC Backup and Recovery for Microsoft Exchange 2007 Enabled by EMC CX, Replication Manager and Microsoft Hyper-V using iSCSI Reference Architecture: EMC Solutions for Microsoft SQL Server on EMC Unified Storage Platforms Reference Architecture: EMC Virtual Architecture for Microsoft Sharepoint Server 2007 Enabled by EMC CX and Hyper-V Disaster Recovery in a Geographically Dispersed Cross-Site Virtual Environment Enabled by EMC CX, RecoverPoint and Microsoft Hyper-V BTW – if you’re a Microsoft IT user interested at the intersection with infrastructure, another great technical blog to follow (IMO) is Brian’s Power Windows Blog .   Brian, for an example recently posted on all the cool sessions at EMC World that touch on Microsoft technologies. Now, of course, we have MORE of all of this on VMware – a lot more!   It’s just proportionally more based on how often our customers ask for VMware-specific content and integration rather than Hyper-V, but now I’m just smack-talkin’…   Adrian, it’s on :-)