You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

Adding the SQL Safe Backup services to an existing role helps with the high availability of the services in failover situations. The following set of instructions helps you to add the SQL Safe Backup services to an existing role:

  1. Log onto the active cluster node using an Administrator Account.

  2. Launch the Microsoft Failover Cluster Manager.

  3. Right-click on the role created for the clustered instance and select Add Resource > Generic Service. 
    On the Select Service screen, locate and select the SQL Safe Collection Service. Click Next to proceed.
    On the Confirmation screen, click Next.
    On the Summary screen, click Finish .
  4. Right-click on the role created for the clustered instance and select Add Resource > Generic Service.

    On the Select Service screen, locate and select the SQL Safe Management Service. Click Next to proceed.
    On the Confirmation screen, click Next.
    On the Summary screen, click Finish.
  5. Right-click on the role created for the clustered instance and select Add Resource > Generic Service.

    On the Select Service screen, locate and select the SQL Safe Rest Service. Click Next to proceed. 
    On the Confirmation screen, click Next.
    On the Summary screen, click Finish.
  6. Right-click on the newly added Role for the SQL Safe Collection Service and select Properties.

    On the Properties window, go to the Dependencies tab.
    Add the following dependencies:
    1. Name of the clustered role. 
    2. IP address. 
    Click Apply
    Go to the General tab. 
    Enable the Use Network Name for computer name checkbox, then click OK .
  7. Right-click on the newly added Role for the SQL Safe Management Service and select Properties.

    On  the Properties window, go to the Dependencies tab.
    Add the following dependencies:
    1. Name of the clustered role. 
    2. IP address. 

    Click Apply
    Go to the General tab. 
    Enable the Use Network Name for computer name checkbox, then click Apply.
    Go to the Registry Replication tab. Click the Add button and enter SOFTWARE\Idera\SQLsafe\Management Service into the Root Registry Key field, then click OK.

    There is a bug in Windows 2012 where the Registry Replication tab is not available. If the tab is unavailable, use the Add-ClusterCheckpoint PowerShell cmdlet to add the necessary setting.

    EXAMPLE: Add-ClusterCheckpoint -ResourceName "SQLsafe Management Service" -RegistryCheckpoint "SOFTWARE\Idera\SQLSafe\Management Service" -Cluster "[ClusterName]"

  8. Right-click on the newly added Role for the SQL Safe Rest Service and select Properties
    On the Properties window, go to the Dependencies tab. 
    Add the following dependencies:

    1. Name of the clustered role.
    2. IP address. 

    Click Apply.
    Go to the General tab.
    Enable the Use Network Name for computer name checkbox, then click Apply.
    Go to the Registry Replication tab. Click the Add button and enter SOFTWARE\Idera\SQLSafeRestService into the Root Registry Key field, then click OK.

    There is a bug in Windows 2012 where the Registry Replication tab is not available. If the tab is unavailable, use the Add-ClusterCheckpoint PowerShell cmdlet to add the necessary setting.

    EXAMPLE: Add-ClusterCheckpoint -ResourceName "SQLsafeRestService" -RegistryCheckpoint "SOFTWARE\Idera\SQLSafeRestService" -Cluster "[ClusterName]"

  9. Bring each of the newly created roles for the SQL Safe services online (in any order).

  10. Launch the SQL Safe Management Console (Start > All Programs > IDERA > SQL Safe Management Console).

  11. Go to Tools > Repository and Management Service Settings.

  12. Next to the Computer field, click the Change button.

  13. On the window that appears, enter the cluster name that SQL Safe Management Service is associated to, then click OK

  14. Click OK on the Repository and Management Service Settings window.



IDERA |  Products | Purchase | Support |  Community |  Resources |  About Us  | Legal
  • No labels