Migration of Always On Availability Group from old to new SAN within same data center
Method 4

Depending on the size (and contents) of the data store, if you connect your new SAN to your VMWare infrastructure, you can storage vMotion in addition to moving the guest itself. 

If you have large databases in the Availability Group, I'd recommend a modification of Tony Hinkle's answer under Method 1.


Remove secondary replica (call it "B") from the AG
Stop the "B" guest
Storage vMotion "B"'s data store to the new SAN
Bring "B" guest online
Rejoin "B" to Availability Group
Manually failover the Availability Group to "B"
Remove the secondary (former primary, call it "A") from Availability Group
Stop the "A" guest
Storage vMotion "A"'s data store to the new SAN
Bring "A" guest online.
Rejoin "A" to Availability Group
Test with a failover to "A"


Note that depending on how long this takes, you may have to apply any log backups (WITH NORECOVERY, remember) taken during the storage vMotion process on the primary (either time) as part of steps 5 and 11.