Migrating ADManager Plus database to a Microsoft SQL Always On availability group

    In every organization, the Always On availability groups are high availability and disaster recovery solutions that offer scalability and continuous access to data even if the primary servers are down. If you wish to migrate the existing ADManager Plus database to an availability group in Microsoft SQL database, follow these steps.

    Prerequisites

    1. Database synchronization

      The databases in your Microsoft SQL server must be in a synchronized state across all replicas. Learn more

      Adding a database to the availability group databases in Microsoft SQL server management studio

      • Before adding a new database to the Always On High Availability node in the server management studio, create a database and take a full backup of it by referring to the steps given here.
      • Now, add the created database to the Availability Databases by referring to the steps here.

    2. SQL Authentication synchronization
      • Synchronize the SQL login credentials of a user in the Always On availability group setup. This helps synchronize their login across servers and grants them access rights to the available databases. To synchronize the SID of a user in the primary server across the secondary server, follow these steps.

    Steps to migrate existing ADManager Plus database to an availability group listener

    1. Stop ADManager Plus.
    2. Invoke (ADManager Plus Home)\bin\ChangeDB.bat via the command prompt. Make sure that the user running the command prompt is same as the one running ADManager Plus.
    3. A database configuration wizard will display. There, select the server type as Microsoft SQL and provide the following details:
      • In the Host Name field, fill in the IP or the name of the availability group listener.
      • In the Port field, enter the port number of the availability group listener.
      • In the Database Name field, fill in the newly created database's name.
        • Migrating ADManager Plus database to the Microsoft SQL Always On availability group

      4. Note The name of the Microsoft SQL server instance has to be entered manually if you have not chosen the Auto Discover option.

    4. Select the Authentication type. If you have selected Windows Authentication, the credentials are automatically taken. If you have selected SQL Server Authentication, enter the corresponding synchronized credentials.

      5. Note If SQL Server Authentication is used to move the database, access and permissions to the Microsoft SQL instance are automatically provided. However, when Windows Authentication is used, access and permissions have to be granted, as explained here.

    5. Click Test Connection to check whether the credentials are correct.
    6. Click Save.

      7. The migration procedure will start, and it will take a few minutes to complete. Once the migration is successful, you should see this screen:

      Migrating ADManager Plus database to the Microsoft SQL Always On availability group

    Specifying the failover time for a database

    A failover in an availability group occurs at the level of an availability replica. For uninterrupted running of ADManager Plus databases, it's important to provide the time within which the secondary replica must become the primary replica. To achieve this, provide the values (in seconds) for the DBConnectionRetryCount and DBConnectionRetryInterval parameters in the <ADManager Plus installation folder>\conf\product-config.xml file

    Migrating ADManager Plus database to the Microsoft SQL Always On availability group