This week I clocked up a lot of miles doing another 4 corners tour of Ireland, with the MSFT partner team, speaking to MSFT partners in Belfast, Galway and Cork. It covered a number of things with different speakers, cloud, Windows 8, Windows Server 8, and I spoke for around an hour on System Center 2012 and Windows Server 8 Hyper-V. The audience was mostly a manager/sales audience so we kept more to the business side of things, but some tech just proves the argument, and I had a feeling that nothing would do that better than Hyper-V Replica.
If you’re presenting to this kind of audience, it’s one thing to show them a new product they can sell, and that will get some interest/traction. But if you can show them a whole new service that they can develop and use to do develop yet another service, and be able to sell this to the breadth audience that hears way too much about Fortune1000 tech, then you really have a winner. And that’s Hyper-V Replica:
- A DR replication solution built into Hyper-V, at no extra cost, designed for small/medium businesses with commercial broadband
- Replicate from host-host, host-cluster, cluster-host, or cluster-cluster.
- Replicate office to office, data centre to data centre, branch office to HQ, or customer to hosting provider (which could be a managed IT services company with some colo hosted rack space) … and maybe use that as an entry point into a cloud/IaaS solution for SMEs.
And that’s the hook there. Most MSFT partners have experience with s/w based replication in the past. It’s troublesome, and often assumes lots of low latency bandwidth and a 3rd witness site. Not so with Hyper-V Replica, as I demonstrated in this video:
Of all the stuff I’ve presented in the last 2 weeks, Hyper-V Replica was the one that caused the most buzz, and rightfully so in my opinion. It’s an elegant design; the genius is the “simplicity” of it. It should prove to be reliable, and perfect for the audience it’s being aimed at.
This blog post is the property of Aidan Finn (@joe_elway / http://www.aidanfinn.com) and may not be reused in any manner without prior consent of Aidan Finn. You may quote one paragraph from this blog post if you link to the original blog post.