Posted by: MikeLaverick
Yesterday I had the pleasure meeting Jacob Jensen of VMware. He’s VMware new Product Group Manager for the SRM product – prior to this he was heavily involved in the network piece of vSphere4, and prior to that worked for Cisco. Jacob has been over in EMEA for some weeks, sounding out customers and partners about what they would like see VMware Site Recovery Manager to do in the future. It was a really insightful and useful two hours spent in London (and I don’t often say that about London, except at the London VMUG!), and the added bonus was I got spend sometime with my partner (Carmel) who is working down there on a contact currently. Carmel wasn’t bored – having been the proof-reader for my end of the Vi3Book, vSphere4 and two SRM books – she knows just about as much as I do. In fact she sometimes finds herself not just correcting my typos, but the odd technical error now and then. Plus she set me and Jacob straight her perspective on licensing of the SRM product and DR.
Anyway, we had a very detailed chat about the current position of SRM and future directions – as well as general chat about the guiding philosophies at VMware. I promised Jacob I would get back to him with an extended email about things I want to see SRM do in the future. I’ve got quite a few ideas of my own. But I do that I thought it might be interesting to reach out to the community of bloggers, partners and customers who come to RTFM each day – and ask if for you input. I’m really interested in hearing from you if you are VMware Customer using SRM, but even more so if you are VMware Customer who’s not. Aside from product improvements and increasing the scope of SRM – I’m really interested in what the barriers are to customers adopting the product, and identifying imaginative and creative ways of getting round those barriers if they exist.
I dare say I won’t come up with anything original or different that Jacob hasn’t heard already. But perhaps with it coming from a different direction – there might be a different perspective. Anyway, if you interested in contributing. Leave an extended comment on this blogpost – and make your voice heard here!