Comments on: Defining a nomenclature for storage allocations http://itknowledgeexchange.techtarget.com/server-virtualization/defining-a-nomenclature-for-storage-allocations/ A SearchServerVirtualization.com and SearchVMware.com blog Wed, 12 Sep 2012 17:14:56 +0000 hourly 1 By: Rick Vanover http://itknowledgeexchange.techtarget.com/server-virtualization/defining-a-nomenclature-for-storage-allocations/#comment-1539 Rick Vanover Tue, 21 Oct 2008 17:20:50 +0000 http://servervirtualization.blogs.techtarget.com/2008/10/20/defining-a-nomenclature-for-storage-allocations/#comment-1539 I would rename the LUN if that was something that mattered to the VMware side. In cases where something like an IBM SAN Volume Controller is used – I may not. I may just make a name like SVC4-GOLD-1750 for a LUN on the gold SVC that is 1.75 TB.

The renames of datastores is permitted in VI3.

]]> By: Janåke Rönnblom http://itknowledgeexchange.techtarget.com/server-virtualization/defining-a-nomenclature-for-storage-allocations/#comment-1538 Janåke Rönnblom Mon, 20 Oct 2008 18:02:57 +0000 http://servervirtualization.blogs.techtarget.com/2008/10/20/defining-a-nomenclature-for-storage-allocations/#comment-1538 What happens if you move the LUN inside the SAN from one enclosure to another enclosure? Then you would need to rename the LUN on perhaps both the SAN and perhaps even in your VMware environment.

For example EMC has the ability to migrate a LUN to new disks and/or enclosure and I suppose the EVA also have that ability.

-J

]]>