SVM metaset LUN migration using storage based copy
Hi,
We have a Solaris 11.2 SRU 7.4 having an SVM metaset with 2 LUNs that's residing on an old storage controller, and using one of the migration tool provided by the storage we moved the 2 LUNs to a new storage device (of the same vendor).
Once the LUN is moved to the new storage controller, the LUN serial number of the migrated LUN changes.
The old LUN is now off-lined.
The migrated LUN is provided to the same Solaris host and the host is rebooted and the new LUNs is now seen and as expected it has different device id because the LUN serial number changes.