The following steps guide you to configure the SQL Safe Repository databases as highly available using the Windows Failover Cluster Service for Windows Server.
- Open the SQL Server Management Studio (SSMS) and connect to the secondary nodes of the availability group.
- Delete the copies of the SQL Safe Repository databases from the secondary nodes.
- Go to Databases, right-click on SQL Safe Repository, and select Delete.
- In SQL Server Management Studio (SSMS), connect to the active node of the availability group.
- Set the recovery model of the IDERA Dashboard Repository and SQL Safe Repository databases to Full.
- Go to Databases, right-click on SQL Safe Repository, and select Properties.
- Go to Options and set the Recovery Model to Full. Click OK.
- Perform a Full backup of the SQL Safe Repository.
- Go to Databases, right-click on SQL Safe Repository, select Tasks, and Backup.
- The Backup Database - SQL Safe Repository window opens.
- Select the Backup Type as Full, and click OK.
- Sign in to the listener machine.
- Open the SQL Server Management Studio (SSMS), and connect to the listener name.
- Add Databases to the Availability Group.
- Go to AlwaysOn High Availability, expand Availability Groups, right-click on the availability group, and select Add Database.
- The Add Database to Availability Group wizard opens, displaying information about what is needed to add one or more availability databases to an existing availability group. Click Next.
- Select the SQL Safe Repository databases for the availability group. Click Next.
- Select your data synchronization preference. Click Next.
- Connect to all the existing secondary replicas. Click Next.
- Ensure the availability group validation tests are successful. Click Next.
- Once the Database is ready to add to the availability group, review the Summary. Click Finish.
If you want to edit your settings, select Previous to apply your changes. - When the Database is included in the availability group, the results section displays it. Click Close to exit the wizard.
- In SQL Server Management Studio (SSMS), connect to the secondary replica(s) and ensure that the databases have been added successfully.
Once you complete it, you have successfully upgraded SQL Safe Backup with the repository databases hosted in an availability group.
You may begin using SQL Safe Backup by launching the SQL Safe Management Console from the Start menu.
In an AlwaysOn Environment, the SQL Safe Backup requires a license key for each replica to ensure continued functionality of the product after a failover event.
The license key for SQL Safe Backup is tied to the name of the SQL Server instance hosting the repository database.