Hi Aarti,  Any Local virtual-volume will only have local visibility and any distributed-device will have global visibility by default. Assuming Host A is connected to cluster-1 and Host B is connected to cluster-2, Host A can be provisioned any virtual-volume visible to its respective cluster 'cluster-1' via Storage-view . If you want a cluster-1 "LOCAL" virtual-volume to be visible to a host B connected to VPlex cluster-2, it has to be remotely exported to cluster-2 so that it can be added to the cluster-2 storage-view of Host B. Both Host A and B can access the volume at the same time.  I do not see need for a remote export of local volume unless its temporarily for a migration. If the Host A and B are on the same host cluster, it would call for a distributed-device usually.  Hope this cluster.  Thanks, Sathya
Hello  I am having difficulty in understanding the purpose of virtual volume with locality as "Remote"? What is their purpose? Also have question regarding the host access to the remote volumes. For example: vplex-cluster1 -> virtual volume A (local) vplex-cluster2 -> virtual volume A (remote)   1) Can either one of them assign to a host, and we have to assume the other virtual volume also assigned to the same host   vplex-cluster1 -> virtual volume A (local) -> found storage path to host B  vplex-cluster2 -> virtual volume A (remote) -> not found storage path, but assume this virutal volume 'A' also allocated to host B ??  2) Can these 2 virtual volumes allocated to 2 different hosts ?  vplex-cluster1 -> virtual volume A (local) -> host B  vplex-cluster2 -> virtual volume A (remote) -> host C
Remote virtual volume