Suppose you have the Active Roles Administration Service installed and configured as described in the Active Roles Quick Start Guide. This section provides instructions on how to configure the Administration Service to use the database that belongs to an availability group (an availability database).
Note that the Administration Service whose database belongs to an availability group cannot participate in Active Roles replication. Active Roles does not support the replication function for availability databases. If you attempt to perform the “Promote to Publisher” or “Add Subscriber” operation with the Administration Service connected to an availability database, you receive an error.
Here we assume that the Active Roles database is already added to an availability group on SQL Server. For instructions on how to configure an availability group, and how to add a database to an availability group, refer to Microsoft's documentation (see “Getting Started with AlwaysOn Availability Groups (SQL Server)” at http://technet.microsoft.com/en-us/library/gg509118.aspx). We also assume that Active Roles replication is not configured, neither for Configuration data nor for Management History data.
Under these conditions, you can configure the Administration Service to connect to the database via the availability group listener. By using the listener, the Administration Service can connect to the current primary replica of the availability group that holds the Active Roles database without knowing the name of the physical instance of SQL Server that hosts the primary replica. The listener enables support for failover redirection. In case of a failover, the listener automatically redirects the Administration Service’s connection to the new primary replica.
To enable the use of the availability group listener, you need to modify the database connection setting of the Administration Service. You can specify the availability group listener in the SQL Server field on the Change Active Roles Database wizard pages provided by Active Roles Configuration Center.
Depending upon the location of the Management History database in your Active Roles environment, you need to specify the listener in the SQL Server field on the Connection to Database page, on the Connection to Management History Database page, or on both pages. The value in the SQL Server field must identify the DNS host name and, optionally, the TCP port of the listener of the availability group to which the database belongs. For example, if the DNS host name of the listener is AGListener and the TCP port used by this listener is
1234, the value is AGListener,1234. You may omit the port number in case of the default port, 1433.
Using Active Roles, it is mandatory to store the Management History data in a separate database. If you do this, then you have two databases, the Configuration database and the Management History database, each of which (or both) can belong an availability group. In this case:
To specify the listener
You can start Configuration Center by selecting Active Roles Configuration Center on the Apps page or Start menu, depending upon the version of your Windows operating system. For detailed instructions, see Running Configuration Center.
Active Roles can use the Microsoft SQL Server database mirroring technology to improve the availability of the Administration Service. Database mirroring provides a standby database server that supports failover. Once the current database server fails, the Administration Service can recover quickly by automatically reconnecting to the standby server.
Database mirroring increases database availability by supporting rapid failover. This technology can be used to maintain two copies of a single Active Roles database on different server instances of SQL Server Database Engine. One server instance serves the database to the Administration Service; this instance is referred to as the principal server. The other instance acts as a standby server; this instance is referred to as the mirror server.
© 2021 One Identity LLC. ALL RIGHTS RESERVED. Feedback 이용 약관 개인정보 보호정책