availability group. Then create a secondary replica on each destination replica. These secondary replicas act as your destination replicas during resource migration. One of the destination replicas must use synchronous-commit availability mode. The other destination replica can use asynchronous-commit availability mode. The following table summarizes these steps. Step Link (http://msdn.microsoft.com/library/ff878349.aspx) Seed secondary databases: Note: If database-file are identical on On the primary replica, back source and destination instances, the Add up the primary databases and Replica to Availability Group Wizard can seed transaction logs. the secondary databases automatically (select On each instance of Full initial data synchronization). SQL Server 2012 SP1 that is to host a destination replica for the availability group, restore these backups (using RESTORE WITH NORECOVERY). Connect to the primary replica, (http://msdn.microsoft.com/library/hh213247.aspx) and then add a secondary replica to serve as a destination replica on each of the two destination (http://msdn.microsoft.com/library/hh213239.aspx) instances. Use availability mode for one destination replica and asynchronous-commit availability mode for the other. Note: The destination replica becomes the new primary replica migration. Connect to each destination () instance, and then join the (http://msdn.microsoft.com/library/ff878535.aspx) destination replica and its Note: The Add Replica to Availability Group secondary databases to the Wizard automatically joins the new secondary availability group. replica to the availability group, and it optionally, joins its secondary databases to the availability group. Procedure: create an XML configuration file for the current batch of availability groups Before you run MigrateAG.ps1 for a given migration batch, you must create an XML configuration file that describes every availability group in the batch. MigrateAG.ps1 uses the configuration values to generate two scripts for each availability group, as follows: Teardown_ag_name.ps1 CreateAG_ag_name.ps1
availability group. Then create a secondary replica on each destination replica. These secondary replicas act as your destination replicas during resource migration. One of the destination replicas must use synchronous-commit availability mode. The other destination replica can use asynchronous-commit availability mode. The following table summarizes these steps. Step Link Seed secondary databases: On the primary replica, back up the primary databases and transaction logs. On each instance of SQL Server 2012 SP1 that is to host a destination replica for the availability group, restore these backups (using RESTORE WITH NORECOVERY). (http://msdn.microsoft.com/library/ff878349.aspx) Note: If database-file are identical on source and destination instances, the Add Replica to Availability Group Wizard can seed the secondary databases automatically (select Full initial data synchronization). Connect to the primary replica, and then add a secondary replica to serve as a destination replica on each of the two destination instances. Use availability mode for one destination replica and asynchronous-commit availability mode for the other. Note: The destination replica becomes the new primary replica migration. (http://msdn.microsoft.com/library/hh213247.aspx) (http://msdn.microsoft.com/library/hh213239.aspx) Connect to each destination instance, and then join the destination replica and its secondary databases to the availability group. () (http://msdn.microsoft.com/library/ff878535.aspx) Note: The Add Replica to Availability Group Wizard automatically joins the new secondary replica to the availability group, and it optionally, joins its secondary databases to the availability group. Procedure: create an XML configuration file for the current batch of availability groups Before you run MigrateAG.ps1 for a given migration batch, you must create an XML configuration file that describes every availability group in the batch. MigrateAG.ps1 uses the configuration values to generate two scripts for each availability group, as follows: Teardown_ag_name.ps1 CreateAG_ag_name.ps1
AlwaysOn%20AG%20OS%20Upgrade.docx