Here we assume that mirroring for the database of Active Roles is already set up on the SQL Server side in accord with the recommendations and instructions found in Microsoft’s documentation, so that the following conditions are fulfilled:
- The Administration Service is connected to the Configuration database on the principal database server.
- Replication is not configured for the Configuration database (the database server acts as a stand-alone server as applied to Active Roles replication).
- The Administration Service is connected to the Management History database on the principal database server (by default, the Management History database is the same as the Configuration database).
- Replication is not configured for the Management History database (the database server acts as a stand-alone server as applied to Active Roles replication).
Under these conditions, the Administration Service can be instructed to automatically connect to the new principal database in the event of database server role switching. On the computer running the Administration Service, add a string value to each of these two registry keys, and then restart the Administration Service:
- Key: HKLM\SOFTWARE\One Identity\Active Roles\7.5.3\Service\DatabaseConnectionString\
Value Name: Failover Partner
Value Data: <Identifies the SQL Server instance that currently owns the mirror server role for the Configuration database>
- Key: HKLM\SOFTWARE\One Identity\Active Roles\7.5.3\Service\CHDatabaseConnectionString\
Value Name: Failover Partner
Value Data: <Identifies the SQL Server instance that currently owns the mirror server role for the Management History database>
If the default instance is used, the value data is the short name of the computer running SQL Server. Otherwise, the value data is the short name of the computer, followed by a backslash, followed by the name of the instance (such as ComputerName\InstanceName).
By default, the same database is used for the Configuration and Management History data; therefore, the value data would be the same in the DatabaseConnectionString and CHDatabaseConnectionString keys.
To restart the Administration Service, open Configuration Center and click the Restart button at the top of the Administration Service page in the Configuration Center main window. For instructions on how to run Configuration Center, see Running Configuration Center later in this document.
- In the console tree, select Configuration | Server Configuration | Administration Services.
- In the details pane, double-click the name of the Administration Service whose database you want to examine.
- In the Properties dialog box, click the Configuration Database or Management History Database tab, and observe the information in the Database mirroring area:
- Role Current role of the database in the database mirroring session (Principal or Mirror).
- Partner The instance name and computer name for the other partner in the database mirroring session.
- State Current state of the mirrored database and of the database mirroring session. For more information about this field, see the “Mirroring States” topic at http://msdn.microsoft.com/en-us/library/ms189284.aspx
If no information is displayed in the Database Mirroring area, then database mirroring is not configured.
You can also view the mirroring status of a Configuration database or a Management History database on the General tab in the Properties dialog box for the object representing that database in the Configuration/Server Configuration/Configuration Databases or Configuration/Server Configuration/Management History Databases container, respectively.