After demoting the previous Publisher, you can promote the appropriate SQL Server to Publisher and designate the other SQL Servers as Subscribers to the new Publisher, thus configuring the new replication group.
TIP: After you add a Subscriber, the configuration data stored on the Publisher is replicated to the Subscriber, overriding the data on that Subscriber. Therefore, in order to retain your existing Active Roles configuration, it is advisable to assign the Publisher role to SQL Server that belonged to the old replication group. This ensures that each Administration Service in the new replication group inherits the configuration that was in place when you removed the Subscribers and demoted the Publisher.
To configure the new replication group using the Active Roles Console
-
Right-click the Console tree root, click Connect, and then select the Administration Service the SQL Server of which you want to hold the Publisher role.
-
In the Console tree, expand Configuration > Server Configuration, and select Configuration Databases.
-
In the Details pane, right-click the database and click Promote.
-
In the confirmation message box, click Yes.
-
Wait while Active Roles performs the operation.
-
In the Details pane, right-click the Publisher, and click Add Replication Partner.
-
On the Welcome page in the New Replication Partner wizard, click Next.
-
On the Database Selection page, click Browse.
-
To configure the SQL Server of an Administration Service as a Subscriber to this Publisher, specify the corresponding Administration Service in the Connect to Administration Service dialog. Click OK.
-
In the New Replication Partner wizard, click Next, click Next, and then click Finish.
-
Repeat the steps for adding a replication partner for each SQL Server you want to make a Subscriber.
If there are any replication failures in Active Roles, the Active Roles Console provides a visual indication of this issue by placing a red triangle on the Server Configuration and Configuration Databases containers in the console tree. To get more information on a replication failure, you can use SQL Server Management Studio. For more information, see Monitoring replication.
The following sections discuss specific actions to take if you encounter a replication problem in Active Roles.
Symptoms
Replication stops synchronizing changes to configuration data, that is, changes made on a replication partner are not propagated to other replication partners. Replication Monitor in SQL Server Enterprise Manager or SQL Server Management Studio does not indicate any error.
Solution
To verify that the SQL Server Agent service is started on the Publisher SQL Server
-
With SQL Server Management Studio, connect to the Publisher SQL Server.
-
In the Console tree, right-click SQL Server Agent, and then click Start.
If the Start button is disabled, it means that the SQL Server Agent service is already started.
To ensure that the Merge Agents are started on the Publisher SQL Server
-
With SQL Server Management Studio, connect to the Publisher SQL Server.
-
In the Console tree, right-click Replication, and click Launch Replication Monitor.
-
In Replication Monitor, in the left pane, browse the My Publishers branch to select the AelitaReplica publication.
-
In Replication Monitor, in the right pane, right-click a subscription and click Start Synchronizing. Perform this step for each subscription of the AelitaReplica publication.
If the Start Synchronizing command is unavailable, the agent is already started.
Verify that the Replication Agent is scheduled correctly at the Publisher. The Merge Agents must be configured to run continuously. The Snapshot Agent must be configured to start daily at 00:00. For more information, see Replication Agent schedule.
The following section describes the symptoms and solutions for Replication Agent authentication problems.
Solution
By using SQL Server Enterprise Manager or SQL Server Management Studio, verify that the Replication Agent credentials are set properly. The following conditions must be met:
Table 120: Conditions for Replication Agent credentials
Publisher |
Windows Authentication |
Impersonate the SQL Server Agent account on the computer running the Publisher SQL Server (trusted connection). For more information on impersonating the SQL Server Agent account, see . |
SQL Server Authentication |
SQL Server login and password that the Publisher Administration Service uses to connect to its SQL Server |
Subscriber |
Windows Authentication |
Impersonate the SQL Server Agent account on the computer running the Publisher SQL Server (trusted connection). For more information on impersonating the SQL Server Agent account, see Adding members to a replication group. |
SQL Server Authentication |
SQL Server login and password that the Subscriber Administration Service uses to connect to its SQL Server |
For more information on how to view or modify the credentials that the Snapshot Agent and Merge Agents use to connect to the Publisher and Subscribers, see Modifying Replication Agent credentials.