The following table includes the applications and services that SQL Safe Backup is comprised of, with a summary of the requirements of each to be fully fault tolerant using the Microsoft Windows Clustering technology.

SQL Safe Backup components can work in either active-passive or active-active cluster configurations.
ComponentClustering Configuration Considerations

SQL Safe Management Console

None.

SQL Safe Command Line

None.

SQL Safe Management Service, SQL Safe Collection Service, and SQL Safe Rest Service.

This components are responsible for managing operational and policy status and alerting for your entire SQL Safe Backup deployment. If you require these SQL Safe Backup functions to be fault tolerant, configure this components as a Generic Service Resource on a clustered server. You need to deploy this components only once onto a single cluster, not on each server you are backing up. For more information, visit Registering SQL Safe Backup services as a Clustered Resource.

SQL Safe Repository Database

This component is a SQL Server database used to stored operational history and policy configuration information. The SQL Safe Repository Database is used by the Management Console to display operational history and by the Management Service to process and send alerts. For this component to be fault-tolerant, simply host the database on a clustered SQL Server.

SQL Safe Backup Service

This component is responsible for executing backup and restore operations on nodes hosting any clustered SQL Servers. You need to install this service only on each node of the cluster. No failover or cluster resource configuration is necessary. You can deploy the agent from the Management Console or the product installer.

SQL Safe Filter ServiceThis component is responsible for performing instant restore operations on nodes hosting any clustered SQL Servers. If you require that SQL Safe Instant Restore functionality be fault tolerant, configure this component via the SQL Safe Command Line. You should not configure this service as a clustered resource. Instead, a failover mechanism is activated via a Generic Script Resource, and is automatically configured for you using a SQL Safe command. For more information about installing the SQL Safe Filter Service on a Windows cluster, see Installing backup/restore components in a clustered environment.



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