Settings and Functions for Protected SQL Servers (4039526)

If you are protecting a Microsoft SQL Server in your Core, there are additional settings you can configure in the Rapid Recovery Core Console, and there are additional functions you can perform.

For the most up-to-date and detailed information regarding SQL Agents, see Settings and function for protected SQL servers in the Rapid Recovery User Guide located at Rapid Recovery Technical Documentation.

Prerequisites

In order to any SQL settings and functions to be present, a SQL database must be present on a protected volume. If Rapid Recovery does not detect the presence of a database, settings and functions will not be present on the Summary tab, Recovery Point, or Agent Settings.

Settings for protected SQL servers

• A single setting, Attachability, is available in the Core Console related to SQL Server.
• If enabled, SQL server attachability checks are ran to verify the integrity of recovery points containing SQL databases. This action checks the consistency of SQL databases and ensures that all supporting MDF (data) and LDF (log) files are available in the backup snapshot.
• SQL attachability checks are a global setting found in Core Settings | Attachability.
• Rapid Recovery now has the option to run SQL attachability checks on the Core or the Agent.
• If attachability checks are ran on the Core, a licensed version of the highest build of SQL server running on the network must be installed on the Core.
• For more information on SQL attachability see Managing Core SQL Attachability Settings.

Functions for protected SQL servers

• Specify SQL server credentials:
  • Rapid Recovery Core lets you set credentials so the Core can authenticate to the SQL server to obtain information.
  • To set credentials, select the Agent on the left navigation are of the Core Console.
  • On the Summary page click the down arrow to the right of the SQL menu, and select Set Default Credentials for All Instances or choose single database instances by name to apply individually.
• Truncate SQL logs:
  • When you force log truncation of a SQL server logs, the transactions within the log file that have been committed are removed. The log file will not actually reduce in size because log entries are cleaned up inside of the log file. Size reduction, if necessary, can be initiated from the SQL Management Studio using Shrink procedure.
  • To force log truncation, select the Agent on the left navigation are of the Core Console.
  • On the Summary page click the down arrow to the right of the SQL menu, and select Force Log Truncation.
  • This process can be set to perform automatically as part of nightly jobs.
• Force an attachability check of a SQL server:
  • This function checks that SQL databases are attachable.
  • To force an attachability check, select the Agent on the left navigation are of the Core Console, and then click the Recovery Points menu.
  • Choose a recovery point, on the far right of the recovery point click on the drop down, and select Force Attachability Check.
  • You can also set attachability checks to occur automatically. Go to the Agent’s Core’s Settings | Attachability, chose and apply the type of attachability you wish to run.
  • For more information on SQL attachability see Managing Core SQL Attachability Settings.