DL4300 Appliance
Deduplication in Rapid Recovery
18
DVM Repository features and attributes include:
•
Supports recovery from Rapid Recovery 6.x archives and recovery points
•
Supports storage locations on Windows OS only. Repository volume can be local (on storage attached to the Core
server), or on a storage location on a Common Internet File System (CIFS) shared location.
•
Supported storage types include Storage Area Network (SAN), Direct Attached Storage (DAS), or Network Attached
Storage (NAS)
•
Requires 8GB RAM, preferably Error Checking and Correction (ECC) memory
•
Requires quad core processor on Core machine (this long-standing requirement is now enforced)
•
Supports multiple DVM repositories per host
•
No additional services required; DVM repository uses native Core services for communication with Core and for tracking
events
•
Each DVM repository supports up to 4096 repository extents (also called storage locations)
•
Fixed size; DVM repository requires you to specify the repository size on a volume. The size that you specify cannot
exceed the size of the volume. Each volume you define as a storage location must have a minimum of 1GB of free space
available on it.
•
Repository storage location can be a simple or dynamic disk, with speed the most important factor
•
Can use standard encryption keys created and managed in the Core Console (Core-based encryption)
•
Deduplicates data across the entire repository (or across encryption domains within each repository, if encryption keys
are used)
•
Uses a dedicated, resizeable DVM deduplication cache, with a configurable storage location in Core settings
•
Optimized for writing data, storing snapshot data in a repository local to the Core, with all data processed through the
Core
•
Cannot be renamed after creation
•
New repositories of this type can be created using REST APIs, the Rapid Recovery Command Line Management Utility
(cmdutil.exe), or Windows PowerShell® cmdlet
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 generally 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
You can create multiple independent repositories associated with a single Core, up to 255 DVM repositories.
Repositories can span across different storage technologies.
You can further increase the size of a DVM repository by adding new file extents or specifications. An extended
repository can contain up to 4096 extents that span across different storage technologies.
For more information on working with DVM repositories, see
.
Parent topic
Deduplication in Rapid Recovery
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, a virtual reference to the
data is stored.
