Configuring One identity with always on availability group sql server

Hello,

I am trying to setup one identity using always on sql server in single zone in azure.

per azure always on sql server setup, two database servers (one primary and another secondary) will be in the same one availability group and the listener to the availability group will be the point of connection for the database.

The one identity documentation says "You want two databases (for example, UAC and QA) to be part of an SQL Server Always On availability group as availability databases. Each database requires its own availability group (for example, AGUAC and AGQA)".

Having two availability group mean having two listeners. In this case when going through  Configuration Wizard, which listener will be used as there are two now ? is there any document other than the installation guide describing this in detail?

Thanks 

Parents
  • Hi  

    Quick question, is this for One Identity Manager, or One Identity Active Roles? For both, you choose whichever availability group you want for each database that needs to be created.

    For example, with Active Roles, when running through the configuration wizard for the Administration Service, there are two steps in the wizard where you get to choose which SQL or Azure SQL Instance the Configuration and Management History databases should be provisioned to. Which availability group you use for each database is up to you.

    For One Identity Manager, the creation of the main database is done as part of the ConfigWizard, and the creation of a History DB is done via a separate process, again which instance of SQL or Azure SQL is up to you.

Reply
  • Hi  

    Quick question, is this for One Identity Manager, or One Identity Active Roles? For both, you choose whichever availability group you want for each database that needs to be created.

    For example, with Active Roles, when running through the configuration wizard for the Administration Service, there are two steps in the wizard where you get to choose which SQL or Azure SQL Instance the Configuration and Management History databases should be provisioned to. Which availability group you use for each database is up to you.

    For One Identity Manager, the creation of the main database is done as part of the ConfigWizard, and the creation of a History DB is done via a separate process, again which instance of SQL or Azure SQL is up to you.

Children
No Data