With all possible respect to Chad Sakac (and his post here) I'm still waiting for my VM teleporter.  As a service provider, my customers aren't interested in moving VMs 65 miles, they are interested in moving them from one time-zone to another.  They are interested in moving their VMs from one coast to another.  They are interested in moving their VMs from one continent to another. 

Now, don't get me wrong: I know why VPLEX is being slow-rolled, but it doesn't make me happy.  Obviously there are a ton of campus-based enterprises out there who are excited about the announcement, and there is certainly a use case for companies that are looking to virtualized storage across multiple existing arrays.  Unfortunately we don't need either of those things, we need to be able to move customer workloads from site to site, seamlessly and without interruption.

I actually have a meeting with Chad this afternoon, and you can bet I'm going to ask what we have to do in order to be able to beta the v2 (async distance) version of this product.  Because my customer want their Virtual Machine Teleporter, and I don't quite have what I need to give it to them.

11,667 total views, no views today

 

2 Responses to My Virtual Machine Teleporter Isn’t Quite Ready

  1. Kim Dooley says:

    If Chad has just a regular run-of-the-mill teleporter, tell him I’ll take one of those.

  2. Chad Sakac says:

    Jeremiah – that’s totally fair :-) Not every customer is in your shoes (loads of demand for VPLEX local and Metro), but don’t worry – we wouldn’t describe a 2011 date for VPLEX Geo (async) unless there was direct line of sight to a firm target.
    To be honest, I have had it up over async. The key is a bit of work with VMware we need to iron out, but working furiously on it.
    Thank you for your support – if every, anything, there is I can do – drop me a line!