DL4300 Appliance
Understanding deduplication cache and storage locations
55
Setting
Description
Enter the amount of time you want to lapse before a
connection timeout occurs. Uses HH:MM:SS format.
NOTE:
The default setting is 0:05:00 or five
minutes.
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.
Parent topic
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