Sequeirad, basically is the same but with outage.
- To minimize the outage create the snapmirror relationship first, with the destination volume in the new aggregate
- To simplify the steps use the OnCommand System Manger 3.1 and use the wizard to create the snap mirror relationship
- After the transfer finish, shutdown SQL Services to not impact the LUN disconnect
- Disconnect the drive from windows cluster using snapdrive
- Update the snapmirror relationship, when finish quiesce the snapmirror and then break.
- Then delete the snapmirror relationship
- Now rename the source volume to source_old and then rename the destination volume with the old source volume name.
- From snapdrive reconnect the new LUN with the same drive letter and connect it to the same cluster instance
- Bring back the SQL services and you are done, after you check that and your environment is ok, offline and destroy your source volume
Then you are done.
So your outage will be just a short time.
So hope that can help
Best regrads,
Miguel Valls