Chat now with support
Chat with Support

Rapid Recovery 6.1.2 - 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

Understanding deduplication cache and storage locations

Global deduplication reduces the amount of disk storage space required for data your Core backs up. Each repository is deduplicated, storing each unique block once physically on disk, and using virtual references or pointers to those blocks in subsequent backups. To identify duplicate blocks, Rapid Recovery includes a deduplication cache for deduplication volume manager (DVM) repositories. The cache holds references to unique blocks.

By default, for DVM repositories, this deduplication cache is 1.5GB. This size is sufficient for many repositories. Until this cache is exceeded, your data is deduplicated across the repository. Once the amount of redundant information is so great that the deduplication cache is full, your repository can no longer take full advantage of further deduplication for newly added data. The amount of data saved in your repository before the deduplication cache fills varies by the type of data being backed up, and is different for every user.

You can increase the size of the DVM deduplication cache by changing the deduplication cache setting in the Rapid Recovery Core. For more information on how to increase the cache size, see the topic Configuring DVM deduplication cache settings.

When you increase the DVM deduplication cache size, there are two factors to consider: disk space and RAM usage.

Disk space. Two copies of the DVM deduplication cache are stored on disk: a primary cache, and a secondary cache which is a parallel copy. Thus, if using the default cache size of 1.5GB for a DVM repository, 3GB of disk storage is used in your system. As you increase the cache size, the amount of disk space used remains proportionally twice the size of the cache. To ensure proper and fault-resistant performance, the Core dynamically changes the priority of these caches. Both are required, the only difference being that the cache designated as primary is saved first.

RAM usage. When the Rapid Recovery Core starts, it loads the deduplication cache to RAM. The size of the cache therefore affects memory usage for your system. The total amount of RAM the Core uses depends on many factors. These factors include which operations are running, the number of users, the number of protected machines, and the size of the deduplication cache. Each operation the Core performs (transfer, replication, rollup, and so on) consumes more RAM. Once an operation is finished, memory consumption decreases accordingly. However, administrators should consider the highest RAM load requirement for efficient operations.

Default settings for the Rapid Recovery Core place the primary cache, secondary cache, and the metadata cache for DVM repositories in the AppRecovery directory. This folder is installed on the Core machine.

NOTE: Depending on your settings, the AppRecovery directory may not be visible on the Rapid Recovery Core. To see this directory, you may need to change the Folder Options control panel to show hidden files, folders, and drives.

Assuming the Rapid Recovery Core is installed on the C drive, these locations are typically as follows:

Table 12. Default storage locations for DVM deduplication cache settings

Setting

Default Storage Location

Primary Cache Location

C:\ProgramData\AppRecovery\RepositoryMetaData\PrimaryCache

Secondary Cache Location

C:\ProgramData\AppRecovery\RepositoryMetaData\SecondaryCache

Metadata Cache Location

C:\ProgramData\AppRecovery\RepositoryMetaData\CacheMetadata

You can change the storage location of these caches. For example, for increased fault tolerance, you can change location of your secondary cache to a different physical drive than the primary cache, assuming the Rapid Recovery Core has access to the location.

For more information on how to change storage locations for any of these settings, see the topic Configuring DVM deduplication cache settings.

Quest recommends that you plan for deduplication storage separately. Deduplication only occurs in a single repository (not across multiple repositories). If using Core-based encryption, deduplication is further limited to the data protected by a single key, since for security purposes each key serves a single encryption domain.

For more information about deduplication, see Deduplication in Rapid Recovery.

Configuring DVM deduplication cache settings

Complete the steps in this procedure to configure deduplication cache settings for DVM repositories.

1.
Navigate to the Rapid Recovery Core Console.
From the list of Core settings on the left side of the Settings page, click DVM Deduplication Cache. This setting only appears if your Core has one or more DVM repositories.

The DVM Deduplication Cache core settings appear.

The Restore Default dialog box appears

b.
Click Yes to confirm the restore.

The setting you selected becomes editable.

Table 13. DVM deduplication cache settings information

Setting

Description

[Restore Default] Restore Default

This control resets DVM cache locations to system default locations, which are described for each setting.

Primary cache location

If you want to change the primary cache location for DVM repositories, then in the Primary Cache Location text box, type the path for a storage location accessible to the Core.

The default location is:

C:\ProgramData\AppRecovery\RepositoryMetaData\PrimaryCache

Since the primary and secondary caches are the same size, collective storage for these two caches requires twice the amount of space as the amount allocated for the deduplication cache size. For example, if you specify the default amount of 1.5GB for the deduplication cache size, ensure that each of the two storage locations have at least 1.5GB. In particular, if both locations belong to the same drive (for example, the C drive), there must be at least 3.0GB of free disk space.

Secondary cache location

If you want to change the secondary cache location for DVM repositories, then in the Secondary Cache Location text box, type the path for a storage location accessible to the Core.

The default location is:

C:\ProgramData\AppRecovery\RepositoryMetaData\SecondaryCache

Cache metadata location

If you want to change the cache metadata location for DVM repositories, then in the Cache Metadata Location text box, type the path for a storage location accessible to the Core.

The default location is:

C:\ProgramData\AppRecovery\RepositoryMetaData\CacheMetadata

Deduplication cache size (GB)

If you want to change the deduplication cache size for DVM repositories, then in the Deduplication Cache Size text box, enter a new amount (in GB).

The default location is:

C:\ProgramData\AppRecovery\RepositoryMetaData\SecondaryCache

The minimum cache size setting is 1.5GB. Additionally, the cache size cannot exceed 50 percent of the installed RAM.

Configuring Replay engine settings

You can configure information regarding the Replay engine, which is the communication channel for Rapid Recovery. These settings determine Core settings to provide effective communication.

In general, Quest recommends using default settings. In some cases, you may be directed by Quest Support to modify these settings to help adjust the performance specific to your network needs.

Complete the steps in this procedure to configure Replay engine settings.

1.
Navigate to the Rapid Recovery Core Console.

The Replay Engine core settings appear.

The setting you selected becomes editable.

Table 14. Replay engine settings information

Text Box

Description

IP Address

The Core uses this IP address when performing mount and restore for a recovery point, to allow feedback between protected machines and the Сore.

The IP address for the Replay engine automatically populates with the IP address of the Core machine. If you manually enter the server IP address, then this value is used in cases where the protected machine cannot resolve the automatically provided IP address.

You do not need to set this value manually unless you are having issues with protected machines being able to communicate with the Core.

Preferable Port

Enter a port number or accept the default setting. The default port is 8007.

The port is used to specify the communication channel for the Replay engine.

Port in use

Represents the port that is in use for the Replay engine configuration.

Allow port auto-assigning

Click for allow for automatic TCP port assignment.

Admin Group

Enter a new name for the administration group. The default name is BUILTIN\Administrators.

Minimum Async I/O Length

Enter a value or choose the default setting. It describes the minimum asynchronous input/output length.

The default setting is 65536.

Read Timeout

Enter a read timeout value or choose the default setting. The default setting is 00:05:00.

Write Timeout

Enter a write timeout value or choose the default setting. The default setting is 00:05:00.

Receive Buffer Size

Enter an inbound buffer size or accept the default setting. The default setting is 8192.

Send Buffer Size

Enter an outbound buffer size or accept the default setting. The default setting is 8192.

No Delay

It is recommended that you leave this check box unchecked as doing otherwise will impact network efficiency. If you determine that you need to modify this setting, contact Quest Support for guidance in doing so.

Configuring deployment settings

Rapid Recovery lets you download installers from the Rapid Recovery Core to machines you want to protect.

You can configure settings related to the deployment of the Rapid Recovery Agent software from your Core to the machines you want to protect.

Complete the steps in this procedure to configure deployment settings.

1.
Navigate to the Rapid Recovery Core Console.

The Deploy core settings appear.

The setting you selected becomes editable.

Table 15. Deployment settings information

Text Box

Description

Agent installer name

The default filename is Agent-Web.exe. If you wish to change this file name for any reason, you can use this setting to specify a new name of the Core Web Installer executable file. This file streams a download of the latest version of the Rapid Recovery Core installer, which runs directly from the Web and lets you pause and resume the process as needed.

Core address

Enter the address of your Core server. This typically consists of the protocol, the name of your core server and port, and the directory where the Core files reside.

For example, if your server is Sample, this setting is https://sample:8006/apprecovery/admin/Core

Failed receive timeout

The amount of time deployment of the Agent software should be attempted before timing out.

The default setting is 00:25:00 or twenty-five minutes. If you wish to change this setting, enter the length of time you want the system to attempt to deploy the Agent software before a timeout occurs during read or write events. Uses HH:MM:SS format.

Maximum parallel installs

This setting controls the maximum number of deployments of the Agent software for the Core to attempt at one time.

The default setting is 100.

Related Documents