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.
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.
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:
C:\ProgramData\AppRecovery\RepositoryMetaData\SecondaryCache | |
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.
Complete the steps in this procedure to configure deduplication cache settings for DVM repositories.
1. |
◦ |
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.
a. |
The Restore Default dialog box appears
b. |
The setting you selected becomes editable.
C:\ProgramData\AppRecovery\RepositoryMetaData\SecondaryCache | |
C:\ProgramData\AppRecovery\RepositoryMetaData\SecondaryCache |
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. |
The Replay Engine core settings appear.
The setting you selected becomes editable.
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. |
The Deploy core settings appear.
The setting you selected becomes editable.
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. | |
For example, if your server is Sample, this setting is https://sample:8006/apprecovery/admin/Core | |
The amount of time deployment of the Agent software should be attempted before timing out. | |
© 2023 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy