Replication is not yet configured
When initially configuring Active Roles replication, you can ensure that the Management History data will not participate in Active Roles replication by assigning the Publisher role as follows (for definitions of the replication roles, see Configuring replication):
-
With the Active Roles Console, connect to the Administration Service whose SQL Server you want to hold the Publisher role.
-
In the Console tree, expand Configuration > Server Configuration and select the Configuration Databases container.
NOTE: The Replication Support column is added under configuration databases container to indicate the replication support.
If the value of this column is Supported, it indicates that the replication is allowed for the database. If the value of this column is Unsupported value indicates that the database does not allow replication.
-
In the details pane, right-click the database, and click Promote.
-
Wait while the console performs the Promote operation.
-
In the Console tree, under Server Configuration, select the Management History Databases container.
-
In the details pane, right-click the database, and click Demote.
-
Wait while the Console completes the Demote operation.
Then, you can configure Active Roles replication by using the Active Roles Console as described in Configuring replication: Use the Add Replication Partner command on the database in the Configuration Databases container to add Subscribers to the Publisher you have configured.
Replication is already configured
This section outlines the instructions on how to turn off replication of Management History data in case that Active Roles replication is already configured as described in Configuring replication. You need to first delete all Subscribers for Management History data, and then demote the Publisher for Management History data. This only stops replication of Management History data, leaving the other replication functions intact.
To turn off replication of Management History data
-
With the Active Roles Console, connect to the Administration Service whose SQL Server holds the Publisher role.
-
In the Console tree, expand Configuration > Server Configuration, and select the Management History Databases container.
-
Use the Delete command on each of the Subscriber databases to delete all Subscribers in the Management History Databases container.
-
Right-click the Publisher database, and click Demote.
-
Wait while the console completes the Demote operation.
Re-configuring replication of Management History data
With replication of Management History data turned off, it is still possible to have multiple Administration Services maintain the same Change History log by configuring them to use the same database. Note that the Administration Service version 6.x allows you to install multiple Services with the option to connect to a single configuration database. Thus, you can install the first Service in your environment, having the Setup program create a database. Then, you can install one more Service, having the Setup program configure the new Service to use the same database as the existing Service.
However, if different Administration Service in your environment use different database servers, you may need to re-configure replication of Management History data in order to take full advantage of the Management History feature. You can do so by managing objects in the Management History Databases container as follows.
To re-configure replication of Management History data
-
With the Active Roles Console, connect to the Administration Service whose SQL Server holds the Publisher role for configuration data.
-
In the Console tree, expand Configuration > Server Configuration, and select the Management History Databases container.
-
In the details pane, right-click the database, and click Promote.
-
Wait while the Console performs the Promote operation.
-
Use the Add Replication Partner command on the Publisher database in the Management History Databases container to add Subscribers for Management History data.
The Add Replication Partner command starts the wizard that is similar to that discussed in the Adding members to a replication group section. The only difference is that the list of Administration Services whose database servers can be designated as Subscribers for Management History data is limited to those Services that share the configuration data hosted on the Publisher you have selected.
Centralized Management History storage
With the default replication settings in Active Roles, the Management History data is synchronized between replication partners, along with the Configuration data. Given a large volume of Management History data, this behavior may result in high network traffic and may cause performance degradation of Active Roles in certain scenarios, such as when adding a new partner to the Active Roles replication group. Here you can find instruction on how to eliminate replication of Management History data by implementing a common storage of that data for all replication partners.
Synchronization of the Management History data can be removed from the Active Roles replication process by implementing a common storage of that data for all replication partners. The common storage ensures the consolidation of the portions of Management History data that are generated by different Administration Services, while eliminating the need to synchronize that data between multiple storages.
By default, Active Roles allows you to implement a centralized, common storage for the Management History data. In this way, all the Administration Services that share common configuration use the same Management History storage - the Management History database you created.