[UPDATE: As with all things in the technology world, things have moved on. Exchange 2010 virtualization opportunities have changed dramatically since the posting of this video.]
In this video post, Justin and I talk a little about Microsoft Exchange 2010 and Virtualization and how architects need to make sure that assumptions they make are not going to catch them out in the end…
Please comment- this is my first Video Blog and I welcome your feedback!
Transcript
Justin Pirie (JP): So welcome to the Mimecast Blog, I’m here today with Barry Gill one of my fellow bloggers.
And I’m here really to pose the question to Barry as an infrastructure guy, about virtualization, because a lot of the time I hear “well we’ll just virtualize it” as a solution to peoples problems when they’re thinking about sprawling infrastructure.
So, in particular with relation to Exchange, because that’s what we really care about on-premise (at Mimecast). How do you get over those issues when people are talking to you about their sprawling infrastructure?
Barry Gill (BG): Possibly one of the most critical things for anybody to think about these days is to really assess whether or not the software they’re looking at, so in this instance Exchange server 2010, whether or not it actually supports virtualization.
You can’t just go out there and say every server will go onto our virtual infrastructure. These days it just doesn’t quite work like that. You know, Exchange Server 2010 has some severe limitations, some would call them limitations, in the way it handles virtualization. For example it utilises the built in Windows clustering technology and as such cannot be put on top of additional virtual environments.
