Saran , VIAS will not help with downtime. Understand the reason for downtime is because the WWN of the LUN changes from a backend array WWN to a VPLEX WWN from a host perspective.
I can say that there's no downtime required for claiming storage from the arrays. I presume you're talking about adding new volumes and presenting them to VPLEX.
I'm not sure on the licensing question, I'd reach out to your EMC account rep.
Gary, not about the new volumes , we are planning to migrate data volumes from VNX to VMAX . we need a downtime to encapsulate the backend volumes to storage volumes. So i am just curious with the help of VIAS does the downtime be avoided ?
Ah I see, thanks for the clarification. As Ankur says, VIAS doesn't help here. Fortunately, if it's any consolation, the VPLEX encapsulation is process is a one-time thing (never have to perform it again! :-)
VPLEX does not modify the contents of the underlying lun. Windows hosts will see the same signature on the lun and use assign appropriate drive letters based on the registry, etc. All that the hosts sees is a new path to the same device.
It will vary by host OS, but in general all the host see's is a path change. VPLEX does not modify the underlying physical disk as part of an encapsulation process. Some logical volume managers do 'care' about the physical path (for example older AIX and HPUX), but today most Unix's and Linux's are fine with a device path change. For specifics for your particular host OS you should consult the procedures provided by the SolVeDesktop application. It is available on support.emc.com.
ankur.patel
2 Intern
•
286 Posts
1289
2
Posted November 6th, 2014 06:00
Saran , VIAS will not help with downtime. Understand the reason for downtime is because the WWN of the LUN changes from a backend array WWN to a VPLEX WWN from a host perspective.