The following procedure has been done many times with success
- don't use pinning, it's a management nightmare
- use separate physical links and VSAN's to connect the new SAN
- create additional vhba in the service profile, and move them to the new VSAN
This allows you to migrate, read from the old storage, and write to the new one (e.g. with storage vmotion)
Indeed, it's simple, and btw. even works, if the SAN fabrics are Brocade, which doesn't support VSAN's; VSAN's are used UCS internally for routing the traffic, and on exiting fabric interconnect to the Brocade, the VSAN tag is removed.
The fabrics are indeed Brocade but that sounds like that is a non issue. Excellent. I will proceed with that and reply about that results.