Distributed volumes are mirrored devices from two separate vplex clusters and has extents from both vplex clusters.  1. When distributed volumes assigned to host, they see it as a single device with number of Front end paths zoned with the host. Whenever a Read / Write requests comes on vplex cluster, it writes first on source vplex cluster and then to clustered Vplex.  2. When one vplex cluster is down, data will be still accessible through remote vplex cluster.  3. Distributed volumes can be used for accessing in two different vplex clusters. For migrations we can't migrate vplex distributed volumes but we can use Distributed volumes extent/ device migration to perticular vplex. This data mobility job will run in background and can be used for migration of the data between two different vplex clusters.  Let me know if this information is helpful to you.
I have few questions related to VPLEX Metro cross connect.  1) When a host is connected to both VPLEX clusters in a metro setup and the distributed volumes from both  the VPLEX clusters are assigned to the host ,how does the host handle this?Does it see as a single device with few paths to local vplex and few paths to remote vplex ?  2) How does the host handle when local cluster goes down in this setup ?  3)Can we use this setup for non disruptive migration between backend array's ?
VPLEX Metro Cross Connect