This section describes how to work with repositories. It discusses the features and attributes of the repository technology supported by Rapid Recovery release 6.5, called Deduplication Volume Manager (DVM). It briefly describes deduplication used in Rapid Recovery. Then this section describes how to manage DVM repositories, including creating a repository, viewing and editing its details, and deleting a repository. You can learn how to open a repository from one Core on another Core.
A repository is a data structure used to store and manage Rapid Recovery data. Backup snapshots are saved to a repository in the form of recovery points. Before you can protect machines, replicate, or restore data in Rapid Recovery, you need at least one repository.
Deduplication Volume Manager (DVM) is native to Rapid Recovery and can be installed on the Rapid Recovery Core using the Core Console, the Command Line utility, or PowerShell.
On the Repositories page, you can create a new repository, or connect your Core to an existing repository (currently used by another Core). In general, you can view details for a repository, view repository settings, check a repository, or delete a repository, as well as add a storage location or optimize a repository. For more information about managing a repository, including how to create one, see Managing a DVM repository.
A Rapid Recovery administrator explicitly creates a DVM repository within a storage location (a disk volume) associated with a specific Core. You can create a repository from the UI, or from the command line. From the Rapid Recovery Core Console, you can create a new repository of either type. When protecting a machine, you can also define a DVM repository as an advanced step in the wizard workflow.
A repository can reside on different storage technologies, including Direct Attached Storage (DAS), Storage Area Network (SAN), or Network Attached Storage (NAS).
NOTE: When designating a location for a Rapid Recovery repository, speed for the storage volume is the most critical factor. Archival storage devices such as Data Domain are not supported due to performance limitations. Do not store repositories on NAS filers that tier to the cloud, as these devices tend to have performance limitations.
DAS offers the highest data bandwidth and fastest access rate, and is easy to implement. For optimum results, use DAS with Redundant Array of Independent Disks (RAID) 6 storage.
The storage location for a DVM repository should always be in a subdirectory that you specify (for example, E:\Repository), never in the root of a volume (for example, E:\).
The following list describes the features of the DVM repository type:
When you create a DVM repository, the Rapid Recovery Core pre-allocates the storage space required for the data and metadata in the specified location. The minimum DVM repository size is 1GB, which for practical purposes is too small except for testing.
Since DVM deduplication requires a primary and secondary cache, ensure the storage space you reserve is twice the size of your deduplication cache. For example, if you have 1.5GB reserved in the DVM deduplication cache settings on the Core, reserve 3GB on the cache volume. The default installation path for the cache is on the C drive. For more information, see Understanding deduplication cache and storage locations.
Deduplication is a data compression technique that reduces both storage requirements and network load. The process involves physically storing unique blocks of data only once on disk. In Rapid Recovery, when any unique data block occurs a second time within a repository, instead of storing the data again, the Core stores a reference to the first occurrence of the data in the repository. When the information is needed (for example, when restoring), the Core retrieves the data by following the references and reconstructing the original data stream.
Deduplication occurs in backup snapshots captured by Rapid Recovery Core.
For maximum gains, Rapid Recovery uses different types of deduplication, as described in the following sections.
DVM technology uses target-based deduplication.
Target-based deduplication can take place inline (during the transfer of backup information), or as post-processing (occurring on the repository). Post-processing is sometimes called pass-through deduplication.
As for when deduplication occurs, standard deduplication occurs inline.
Rapid Recovery also uses post-processing in one instance: when performing a repository optimization job. This feature is also called duplicate block reclamation.
Thus, Rapid Recovery takes advantage of target-based deduplication, inline deduplication, and post-processing deduplication.
For more information about where the references to unique blocks are stored for DVM repositories, see Understanding deduplication cache and storage locations. For information about adjusting DVM deduplication cache settings, see Configuring DVM deduplication cache settings.
Managing a DVM repository involves the following operations:
For information about the different repository types, see Understanding repositories.
For information about creating a DVM repository, see Creating a DVM repository.