| We are planning to migrate an existing AG (2-node AG cluster, no shared storage) to a new SAN, and want to keep the same drive letters, say F and G . Note that all databases, including
the master, model and msdb are all on the same drive. The plan is as follows: Present new volumes to each node - say M and T Suspend data movement from the AG to the secondary Turn SQL off on the secondary Copy all data files to the new volumes Rename the M drive to F and rename the T drive to G Reboot the server SQL should come up with no issues since the drive and folder structure is the same. Resume data movement to the secondary. Failover the cluster to the secondary (the node that just moved to the new san) Repeat the same steps for the node as above. See any holes or pitfalls to this? There is no concern for transaction log bloat - - this will be done during a maintenance window, and is very low transaction. |
↧
SAN Migration with existing Availability Group
↧