The current version of EMC's Unisphere for the VNX does not allow for more than one storage array to be present in a single "management domain"-- meaning you cannot (today) manage multiple EMC arrays from a single Unisphere session. Bummer. While this has been promised for a future release, it's a known limitation today.

And generally speaking, it's not a major issue, but rather a temporary inconvenience.

However, having more than one array in the storage or management domain has traditionally been a requirement of EMC's SAN Copy and MirrorView array-based software solutions. And when migrating data from a prior generation EMC array (or even a non-EMC array) to the VNX, these tools (SAN Copy specifically) come in very handy.

The good news is that there are documented workarounds to use SAN Copy and MirrorView on the VNX.

http://www.youtube.com/watch?v=-nbuD85X0_g

Lastly, some other things to know when planning to configure either SAN Copy or MirrorView.

Know the ports that your array uses for each and (assuming a FC network) zone them appropriately. For example, on the VNX arrays used in the videos above, SP port "0" are used for MirrorView, and SP port "1" are used for SAN Copy. They CANNOT share the same SP port.

The MirrorView Write Intent Log requires two 128MB LUNs, one for each SP. For whatever reason we could not get 128MB LUNs provisioned from a Storage Pool to show as available LUNs for the log-- but had no trouble using 128MB LUNs from a RAID Group. This may have just been that the LUN from the SP had some overhead taking it below the 128MB... but something I wanted to share.