I’d like to think so or perhaps its written in the stars already (hence the image) …but has replication even been discussed? Sure there is a lot of talk about easing the transition from “private clouds” to “public clouds” but what about replicating internal private clouds 2 private clouds, clearly this is more approachable of a subject then the aforementioned.

Why RecoverPoint?

Besides the obvious plus’s of which I have hooted and hollered over, these points seem to make sense…

• Cisco fabric integration already exists, inline with VCE partnership
• Clearly best of breed in EMC’s replication portfolio. vBlock consists of BoB referenced architectures.
• One replication engine across all vBlock architectures.
• R&D heavy, tighter integration with VMware and EMC product line

Help Please?

• Will RecoverPoint futures include support for the Celerra line? or vBlock0 that is, or will we be forced to use Celerra Replicator? I am talking support for file based replication.
• Will there be support for replication amongst the vBlock Infrastructure packages (ie. vBlock0 to vBlock1 to vBlock2)?
• Will RP be a plate-able addition with each vBlock tier? Or mandated across each tier? Or will native replication hold its own?
• Does this complicate vBlock architectures or not? Does this ease backend support for Acadia?
• Are there “Cluster” configurations for individual vBlock’s? Is RecoverPoint the enabler for this capability?

To me it seems so obvious to include RP as part of these “vBlock-Replicated” configs, what do you think?

Related articles by Zemanta