Users Guide

Table 12. Client timeout settings information (continued)
Setting Description
Read/Write
Timeout
Controls the timeout for the connection between the Core and protected machines when reading or
writing stream data across http. An example is receiving changed data blocks from a protected
machine to the Core for an incremental snapshot.
Enter the amount of time you want to lapse before a timeout occurs during a read/write event. Uses
HH:MM:SS format.
NOTE: The default setting is 0:05:00 or five minutes.
Connection UI
Timeout
Controls the timeout for the connection between the graphic user interface and the Rapid Recovery
Core service across http.
Enter the amount of time you want to lapse before a connection UI timeout occurs. Uses HH:MM:SS
format.
NOTE: The default setting is 0:05:00 or five minutes.
Read/Write UI
Timeout
Controls the timeout for the connection for reading and writing data streams between the graphic
user interface and the Rapid Recovery Core service across http.
Enter the amount of time you want to lapse before a timeout occurs during read or write events. Uses
HH:MM:SS format.
NOTE: The default setting is 0:05:00 or five minutes.
6. For each setting, when satisfied with your changes, click to save the change and exit edit mode, or click to exit edit
mode without saving.
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 on
page 40.
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.
Working with the DL Appliance Core
39