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.
sathyaprakash.mohandass
41 Posts
0
January 9th, 2018 06:00
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
artRanade
46 Posts
0
January 22nd, 2018 08:00
Thank you.