Log in to the primary Avaya Control Manager SQL Server.
You must log as the Avaya Control Manager SQL Server domain user with administrative rights for all machines in the Avaya Control Manager database cluster. To check the user name, see Finding the Avaya Control Manager SQL Server domain user.
Click Start > Microsoft SQL Server > Open SQL Server Management Studio.
In the Object Explorer pane, click Connect > Database Engine.
SQL Server Management Studio displays the Connect to Server dialog box.
In the Server name field, select the local instance of SQL Server.
In the Authentication field, select SQL Server Authentication.
In the Login and Password fields, enter the system administrator credentials.
The system administrator is usually the default sa user created during SQL Server installation.
Click Connect.
In the Object Explorer pane, click Databases > <EDM Database>.
Right-click the EDM database and click Tasks > Back Up.
SQL Server Management Studio displays the Back Up Database dialog box.
In the navigation pane, click General.
In the Backup type field, select Full.
In the Destination area, click Add.
In the Select Backup Destination dialog box, select the path to the backup folder location, specify the backup file name with the .bak extension, and click OK.
Ensure that the SQLService User login (services.msc) has full permissions on the backup folder.
To provide full permissions to the SQLService User login, do the following:
Go to the backup folder location.
Right-click the backup folder and click Properties.
On the Security tab, select the SQLService User login and click Edit.
In the Permissions area, select the Full control check box.
Click OK.
Click OK.
In the Object Explorer pane, click Always On High Availability.
Right-click Availability Groups and click New Availability Group Wizard.
SQL Server Management Studio displays the New Availability Group dialog box.
In the navigation pane, click Specify Options.
In the Availability group name field, enter a name for the Context Store availability group.
In the Cluster type field, select Windows Server Failover Cluster.
Select the Database Level Health Detection check box.
Select the Per Database DTC Support check box.
Click Next.
In the Select user databases for the availability group field, select the EDM database.
Click Next.
Click Add Replica, specify the other SQL Server as the secondary replica and connect to the database engine of the other SQL Server.
To connect to the database engine, use SQL Server Authentication and System Administrator login credentials.
Do the following for each replica:
Select the Automatic Failover check box.
Select the Synchronous Commit check box.
Set the Readable Secondary field to No.
On the Backup Preferences tab, select Prefer Secondary.
On the Listener tab, select Create an Availability Group Listener and do the following:
In the Listener DNS Name field, enter the full FQDN of the listener that you use to access AAG from Context Store.
In the Select your data synchronization preference field, select Automatic seeding.
It creates the EDM database on the secondary SQL Server.
While creating the Availability Group for EDM, you might get an error message asking you to check the disk configuration. To resolve the error, ensure that the locations for EDM data and log files on the primary replica match the drive letters for the EDM data and log files locations on the secondary replica.
The time taken to replicate Context Store EDM data from the primary to secondary SQL Server is approximately 1 minute/GB.
Click Next.
Validate the AAG and click Next.
Check the summary and click Finish.
To test a manual failover of the Availability Group, do the following:
On the primary or secondary SQL Server, click Always On High Availability > Availability Groups.
Right-click the EDM Availability Group and click Failover.
