My organization uses two data centers. In the past, we would have to manually failover between those data centers. This timing would be unpredictable since it required human interaction. With VPLEX, we are able to automate this process where failovers between sites now occur automatically.

We don't see any improvement in the organizational functions.

I’ll give four examples:

1. VPLEX Local configuration: We did experience a serious issue where a storage array needed to be rebooted on a production environment. Fortunately this array was encapsulated under VPLEX, and so we were able to migrate data to another array transparently to users, then reboot the problematic array. Finally we migrated back the data from the “spare array” to the source one. During all these operations no user was aware of migrations, and no downtime was consumed.
2. VPLEX Local configuration: A new array was purchased then encapsulated under VPLEX. The new array had more performance than existing ones, so a data migration to the new storage was recommended from application owners to ameliorate performance. The data migration was done transparently and without application downtime.
3. VPLEX Metro configuration: From a disaster recovery point of view, VPLEX Metro offers more security to data. We didn’t encounter a disaster yet, but we did test the failover of applications to a second site during implementation and the test was really convenient. I would also recommend adding RecoverPoint to the VPLEX Metro solution to add more security to production data.
4. VPLEX deployed for RecoverPoint: We have EMC RecoverPoint that we use to replicate data from non EMC arrays to a VNX. In this case we have to encapsulate the non EMC array under VPLEX then use VPLEX Splitter to replicate data. Without VPLEX, use of RecoverPoint on non EMC arrays would not be possible.

It enables our customers to instantly distribute their block data across two different sites.

The business continuity is sorted, as the data is in two data centers, i.e., readable and writable. If one side goes done, there is no downtime and the other side continues non-disruptively.

We have see performance improvement in our databases. We can use older arrays for archiving.

With the help of EMC VPLEX, we improved the architecture of the geographic redundant infrastructure our application required.

• Hot storage maintenance
• Vendor agnostic environment
• High availability
• Data recovery (DR)

Possibility to replicate volumes with storage devices from multiple vendors.