This topic provides information about data migration on an existing FAStT installation that contains partitions.
You can enable the SAN Volume Controller to be introduced to an existing SAN environment,
so that you have the option of utilizing image mode LUNs to import the existing
data into the virtualization environment without requiring a backup and restore
cycle. For example, each FAStT partition may contain up to 32 LUNs. Each partition
can only access a unique set of HBA ports (as defined by WWPNs). That is, for a single host to access multiple partitions, unique host fibre ports (WWPNs)
need to be assigned to each partition. All LUNs within a partition are surfaced to assigned host fibre ports (no sub-partition LUN mapping).
Host A is mapped to LUN 0, 1, 2 in Partition 0
Host B is mapped to LUN 0, 1, 2, 3, 4, 5 in Partition 1
Host C is mapped to LUN 0, 1, 2 in Partition 2
To allow Host A to access the LUNs in partition B, it is necessary to remove one of the
HBAs (for example, A1) from the access list for partition 0 and add it to partition 1 (A1 cannot be on the access
list for more than one partition).
To add a SAN Volume Controller into this configuration without save and restore cycles would require that a set of unique SAN Volume Controller HBA port WWPNs for each partition. This would allow the FAStT to surface the LUNs (with your data) to the SAN Volume Controller, which would then configure these LUNs as image-mode LUNs and surface them to the required hosts. Unfortunately, this violates a requirement that all SAN Volume Controller nodes be able to see all backend storage. To work around this problem, change the FAStT to allow more than 32 LUNs in 1 storage partition, so that you can move all the LUNs from all the other partitions into 1 partition and map to the SAN Volume Controller cluster.
For example, lets say the FAStT has 8 partitions with 30 LUNs in each, and all need to be migrated to a 4-node SAN Volume Controller cluster with 4 ports on each SAN Volume Controller. Perform the following: