Chat now with support
Chat with Support

Rapid Recovery 6.1.3 - User Guide

Introduction to Rapid Recovery Core Console Core settings Repositories Encryption keys Protecting machines
About protecting machines with Rapid Recovery Support for dynamic and basic volumes Understanding the Rapid Recovery Agent software installer Deploying Agent to multiple machines simultaneously from the Core Console Using the Deploy Agent Software Wizard to deploy to one or more machines Modifying deploy settings Understanding protection schedules Protecting a machine About protecting multiple machines Settings and functions for protected Exchange servers Settings and functions for protected SQL servers
Managing protected machines Snapshots and recovery points Replication Events Reporting VM export Restoring data Bare metal restore
Bare metal restore for Windows machines Understanding boot CD creation for Windows machines Using the Universal Recovery Console for a BMR Performing a bare metal restore for Linux machines Viewing the recovery progress Starting a restored target server Troubleshooting connections to the Universal Recovery Console Repairing boot problems Performing a file system check on the restored volume
Managing aging data Archiving Cloud storage accounts The Local Mount Utility The Central Management Console Core Console references Command Line Management utility PowerShell module
Prerequisites for using PowerShell Working with commands and cmdlets Rapid Recovery PowerShell module cmdlets Localization Qualifiers
Scripting REST APIs About us Glossary

Forcing log truncation for an Exchange machine

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

When you force log truncation for a protected Exchange Server, the size of the logs are reduced. Complete the steps in this procedure to force log truncation on demand.

1.
In the left navigation area of the Rapid Recovery Core Console, select the protected Exchange server for which you want to force log truncation
The Summary page for the protected machine appears.
2.
At the top of the page, click the Exchange drop-down menu and select Force Log Truncation.
3.
In the resulting dialog box, click to confirm that you want to force log truncation.
The dialog box closes. The system starts truncating the Exchange server logs. If Toast alerts are enabled for this type of event, you see a message that the log truncation process starts.

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.

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 pages.

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 pages.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating