8.5 Windows Server 2012 clustered environment

Registering the SQL Safe services with Microsoft Failover Cluster Manager allows the Microsoft Cluster Service to manage the services in failover situations. The following configuration ensures the high availability of the services during a failover.

There are two separate set of instructions that can be followed to register the SQL Safe services as a clustered resource.

Configuring the SQL Safe Management Service as a Generic Service Resource using Windows Server 2008/ Windows Server 2008 R2 and later

After installing the SQL Safe Management components on your cluster nodes, create the clustered service resource to allow SQL Safe to recognize the cluster nodes.

Use the following steps if you do not have an existing application or service that you want to use for the SQL Safe Management Service.

1. Log onto the currently active cluster node using an administrator account, and then start the Microsoft Failover Cluster Manager application named cluadmin.msc.
2. Go to Roles on the left side of the pane, select the SQL Server Instance role.
3. Right-click on the SQL Server role, and then select Add Resource > Generic Service.
4. The Select Service wizard opens with a list of all services installed on the clustered environment.
   Select the SQL Safe services required to configure as a Generic Service Resource:
   • SQLsafe Management Service
   • SQLsafe Collection Service
   • SQLsafe Rest Service
   You cannot perform the operation for all of them at the same time. You have to perform the operation for each one.

5. Select the SQLsafe Management Service and click Next. 

6. On the Confirmation window, click Next.

7. The wizard configures the service as displayed on the Configure Generic Service window.

8. On the Summary window, click Finish.

9. Repeat these steps for:SQLsafe Collection Service and SQLsafe Rest Service.

10. Then, go to Roles on the right side of the pane. Right-click on your new Generic Service Resource (SQLsafe Management Service), and then select Properties. 

11. SQL Safe now displays the SQL Safe Management Service Properties window.
12. On the Dependencies tab, click on "Click here to add a dependency" and a scroll down list appears under the selection of  .
13. Select the Cluster Name and click Apply.
14. Go to General tab, select the box "Use Network Name for computer name" and click Apply.
15. Go the Dependencies tab, click the scroll down option and select the SQL Server.
16. Click the  scroll down option, select the IP Address, and click Apply.
17. Go to the Registry Replication tab and click Add. 
18. In the Root registry key, type the following text: SOFTWARE\Idera\SQLsafe\Management Service
    You can get this path by going to the Registry Editor, open the LOCAL MACHINE folder - SOFTWARE- Idera - SQLsafe - Management Service. At the end of the pane, you can see the folder destination path. Copy it on the Root registry key.
19. Click OK.

20. On the SQL Safe Management Service Properties window, click Apply, and Ok.

    Add same dependencies for SQLsafe Collection Service, and SQLsafe Rest Service.

21. Go to Roles on the right side of the pane. Right-click on your new Generic Service Resource (SQLsafe Collection Service), and then select Properties. 

22. SQL Safe now displays the SQLSafeCollectionService Properties window.
23. On the Dependencies tab, click on "Click here to add a dependency" and a scroll down list appears under the selection of  .
24. Select the Cluster Name and click Apply.
25. Go to General tab, select the box "Use Network Name for computer name" and click Apply.
26. Go the Dependencies tab, click the scroll down option and select the SQL Server.

27. Click the  scroll down option, select the IP Address, and click Apply.

    The SQLSafeCollectionService does not need a Replication Service.
28. Click OK.
29. Go to Roles on the right side of the pane. Right-click on your new Generic Service Resource (SQLsafe Rest Service), and then select Properties. 
30. SQL Safe now displays the SQLSafeRestService Properties window.
31. On the Dependencies tab, click on "Click here to add a dependency" and a scroll down list appears under the selection of  .
32. Select the Cluster Name and click Apply.
33. Go to General tab, select the box "Use Network Name for computer name" and click Apply.
34. Go the Dependencies tab, click the scroll down option and select the SQL Server.
35. Click the  scroll down option, select the IP Address, and click Apply.
36. Go to the Registry Replication tab and click Add. 
37. In the Root registry key, type the following text: SOFTWARE\Idera\SQLSafeRestService
    You can get this path by going to the Registry Editor, open the LOCAL MACHINE folder - SOFTWARE - Idera - SQLSafeRestService. At the end of the pane, you can see the folder destination path. Copy it on the Root registry key.
38. Click OK.
39. On the SQLSafeRestService Properties window, click Apply, and Ok.
40. Then, go to Roles on the right side of the pane. Right-click on your new Generic Service Resource (SQLsafe Management Service), and select Bring Online. Do the same for SQLsafe Collection Service, and SQLsafe Rest Service.

Use the following steps if you do have an existing application or service that you want to use for the SQL Safe Management Service.

1. Log onto a new cluster node using an administrator account, and then start the Microsoft Failover Cluster Manager application named cluadmin.msc.
2. Go to Roles on the left side of the pane, select the SQL Server Instance role that is the same as the one you used on the other node.
3. On the Resources tab you can see the resource services added on the other node.
   If you want to add more resource services, follow the steps specified above. You only have to make sure to specifiy the dependencies and regisrty replication.
4. Then, failover your SQL Server Instance.
   Right-click on the SQL Server role, and select Move > Select Node.
5. The Move Clustered Role wizard appears. Select your Cluster Node and click OK.
   All your resources configured on the other node are transferred to the new node.

Once you configure SQL Safe for the Cluster, you need to update your SQL Safe Management Console settings.

1. Launch the SQL Safe Management Console. Go to Tools > Repository and Management Service Settings.
2. You get an error message "User preferences repository connnection information is not set", click OK.

3. The Repository and  Management Service Settings window appears.
   On the Location of Management Service for this console, sºelect the Change button next to the Computer. 
   The SQLsafe Preferences window appears, type the hostname or IP Adress for the computer that hosts the SQL Safe Management Service, and click OK.

   Make sure to type the Cluster name.

4. You get an error message "User preferences repository connnection information is not set", click OK.
5. On the Repository database for Management Service and Console fill the information with the Clustered SQL Server Instance and Database name.
   By default, the Windows Authentication is selected.
   If you want to use the Microsoft SQL Server Authentication, select this option and specify the login name and password for this account, and click save.
   Before you continue, you can Test Connections to make sure the SQL Server instance is connected. Then, click OK.
6. At the bootm of the SQL Safe Management Console you see an alert " There are problems with the Management Service. Clik here for details".
   A SQL Safe Management Console window appears saying "This console is configured to use the Management Service installed on the hostname or IP Adress for the computer that hosts the SQL Safe Management Service", click OK.
7. Go to Tools > Management Console Preferences. On this window, go to User Experience, select the Enable Debug Logging and click OK.