Quest has been named as an ASP "Ten Best Web Support Sites" award winner. Learn more.

Rapid Recovery 6.0.2 - User Guide

*** Legend Introduction to Dell Data Protection | Rapid Recovery Understanding the Rapid Recovery Core Console Working with repositories Managing Rapid Recovery Core settings Using custom groups Working with encryption keys Protecting machines using the Rapid Recovery Core Working with Microsoft Exchange and SQL Servers Protecting server clusters Exporting protected data to virtual machines Managing protected machines Understanding replication Managing events Generating and viewing reports Restoring data Understanding bare metal restore for Windows machines Retention and archiving Managing cloud accounts Working with Linux machines Understanding the Local Mount Utility Central Management Console Understanding the Rapid Recovery Command Line Management utility Understanding the Rapid Recovery PowerShell module
Prerequisites for using PowerShell Working with commands and cmdlets Rapid Recovery PowerShell module cmdlets Localization Qualifiers
Extending Rapid Recovery jobs using scripting Rapid Recovery APIs Glossary

About Exchange database mountability checks

When using Rapid Recovery to back up Microsoft Exchange Servers, mountability checks can be performed on all Exchange databases after every snapshot. This corruption detection feature alerts administrators of potential failures and ensures that all data on the Exchange servers will be recovered successfully in the event of a failure.

To enable or disable this feature, go to the Settings menu for a protected machine, and set the Enable automatic mountability check option to Yes or No, respectively. For more information about modifying settings for a protected machine, see Viewing and modifying protected machine settings.

Mountability checks are not part of nightly settings. However, if the automatic mountability check is enabled, and if the Truncate Exchange logs nightly job is enabled, then the mountability check is triggered after the completion of log truncation.

You can also perform a mountability check on demand, from the Recovery Points pane on a protected Exchange server machine. For more information, see Forcing a mountability check of an Exchange database.

Note: The mountability checks only apply to Microsoft Exchange 2007, 2010, and 2013. Additionally, the Rapid Recovery Agent service account must be assigned the Organizational Administrator role in Exchange.

Was this topic helpful?

[Select Rating]



Forcing a mountability check of an Exchange database

In order to force a mountability check, an Exchange database must be present on a protected volume. If Rapid Recovery does not detect the presence of a database, the mountability check function does not appear in the Core Console.

Complete the steps in this procedure to force the system to perform a mountability check for a specific Exchange server recovery point on demand.

  1. In the left navigation area of the Rapid Recovery Core Console, select the protected Exchange server machine for which you want to force the mountability check, and then click the Recovery Points menu.
  2. Scroll down to the Recovery Points pane.
  3. Navigate through the recovery points to find the desired recovery point. Optionally, click the [Expand] arrow to the right of a recovery point in the list to expand the view.
    In the expanded recovery point information, you can see volumes included in the recovery point.
  4. In the Recovery Points pane, from the row representing the correct recovery point, click [Settings], and from the drop-down menu, select Force Mountability Check.
  5. In the resulting dialog box, click to confirm that you want to force a mountability check.
    The dialog box closes. The system performs the mountability check. If Toast alerts are enabled for this type of event, you see a message that the mountability check starts.

For instructions on how to view the status of the mountability check, see Viewing events using tasks, alerts, and journal.


Was this topic helpful?

[Select Rating]



Forcing a checksum check of Exchange database files

In order to force a checksum check, an Exchange database must be present on a protected volume. If Rapid Recovery does not detect the presence of a database, the checksum check function does not appear in the Core Console.

Complete the steps in this procedure to force the system to perform a checksum check for a specific Exchange server recovery point.

  1. In the left navigation area of the Rapid Recovery Core Console, select the protected Exchange server for which you want to force a checksum check, and then click the Recovery Points menu.
    The Recovery Points page appears for the protected Exchange server.
  2. Scroll down to the Recovery Points pane.
  3. Navigate through the recovery points to find the desired recovery point. Optionally, click the [Expand] arrow to the right of a recovery point in the list to expand the view.
    In the expanded recovery point information, you can see volumes included in the recovery point.
  4. In the Recovery Points pane, from the row representing the correct recovery point, click [Settings], and from the drop-down menu, select Force Checksum Check.
  5. In the resulting dialog box, click to confirm that you want to force a checksum check.
    The dialog box closes. The system performs the checksum check. If Toast alerts are enabled for this type of event, you see a message that the checksum check starts.

For instructions on how to view the status of the checksum check, see Viewing events using tasks, alerts, and journal.


Was this topic helpful?

[Select Rating]



Settings and functions for protected SQL Servers

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.

A single setting, Attachability, is available in the Core Console related to SQL Server.

Rapid Recovery Core lets you perform a SQL attachability check 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.

In previous releases, SQL attachability checks have historically required a licensed version of SQL Server on the Core machine. Rapid Recovery Core now provides the ability to perform SQL attachability checks from an instance of SQL Server on the Core, or from a licensed version of SQL Server on a protected SQL Server machine.

The attachability settings let you specify which licensed version of SQL Server is used to perform this check. For more information about configuring attachability settings, see Managing Core SQL attachability settings.

For more information on SQL attachability, see About SQL attachability.

Following are functions you can perform for a SQL server protected by the Core.

  • Specify SQL Server credentials. Rapid Recovery Core lets you set credentials so the Core can authenticate to the SQL Server to obtain information. You can set credentials for a single protected SQL Server machine, or set default credentials for all protected SQL Servers.

    For more information about setting credentials for SQL servers, see Setting credentials for a SQL Server machine.

  • Truncate SQL logs. When you force log truncation of SQL Server logs, this process identifies the available space on the protected server. This process does not reclaim any space.

    For more information about truncating SQL Server logs on demand, see Forcing log truncation for a SQL machine.

  • Force an attachability check of a SQL Server. This function checks the consistency of SQL databases and ensures that all supporting MDF (data) and LDF (log) files are available in the backup snapshot.

    For more information about forcing an attachability check for SQL Servers on demand, see Forcing a SQL Server attachability check.

Other than specifying credentials, each of the functions described in the preceding list can be accomplished on demand, and can also be configured to occur as part of the nightly jobs performed for the Core. For more information about the tasks you can schedule as nightly jobs, see Understanding nightly jobs. For information on configuring nightly jobs, see Configuring nightly jobs for the Core.


Was this topic helpful?

[Select Rating]



Related Documents