This post has been republished via RSS; it originally appeared at: Configuration Manager Archive articles.
First published on TECHNET on Aug 01, 2017Hello everyone,
Our colleague Umair Kahn has a helpful post on his blog where he and Sean Mahoney walk through adding a new secondary replica node to an existing SQL Server Always On availability group for a primary site server.
This process involves several steps
- Adding the new server as a secondary replica.
- Stopping the Configuration Manager site.
- Backing up and restoring the site database from the primary replica to the new secondary replica.
- Configuring each secondary replica.
Umair and Sean call out the issues that are specific to primary site servers. You'll find the complete text for Umair's post here:
ConfigMgr 1702: Adding a new node (Secondary Replica) to an existing SQL AO AG