As much as I enjoy waxing existential over what is means to be truly free, this discussion is limited to what it means for a LUN to be truly free in Storage Manager. Storage Manager is able to monitor storage environments containing devices from different vendors. These devices can define free LUNs differently. To understand what it means for a LUN to be truly free, we must  understand the definition of a free LUN and the definition of a Replication Target LUN.


Definition of a Free LUN

Generally free LUNs are created but not assigned to a host. These LUNs are potential candidates for reclaiming space on a storage array. Because free LUNs are not assigned to a host, they do not have an HBA mapping.


Definition of a Replication Target LUN

Replication target LUNs are used to replicate a source LUN so the information on the Replication Target LUN is redundant. These Replication Target LUNs are associated with their source LUN, and the Replication Target LUNs are not presented to a Host. Unlike the space on a free LUN, the space of a Replication Target LUN is used and cannot be reclaimed by a storage array. Replication Target LUNs do not have HBA mappings since there is no association with a host.


Example: LSI and HP EVA

According to LSI and HP EVA arrays, a free LUN is any LUN without an HBA mapping.So for these arrays, Storage Manager lists the Replication Target LUNs as "Free LUNs".


Navigate to the Free LUNs report from the left-hand navigation pane > SAN Groups > YourArrayName > Storage tab. An example is illustrated below.


But as we saw in the definition of a Replication Target LUN, these LUNs are not truly free. However, if a meaningful naming convention is employed, and the names are adequately descriptive, then the replication LUNs can be identified within the Storage Manager reports. For example, use names such as <LUNName>_replication for your Replication Target LUNs.