The Recovery Points Only menu appears in the left navigation area if one of the following is true:
You can collapse or expand the view of recovery points-only machines by clicking the arrow on the left side of this menu.
The menu includes a drop-down menu on the right side which lists functions that can be performed on all recovery points-only machines simultaneously. In this case, the only function you can perform is to remove recovery points from the Core.
Describes the Custom Groups menu that appears in the left navigation menu if you define custom groups in your Core.
The custom groups menu appears in the left navigation area only if you have defined one or more custom groups. As with all menu labels in the navigation area, the label for this menu appears in all upper-case letters.
You can collapse or expand the view of items in this menu by clicking the arrow on its left side.
The custom groups menu includes a drop-down menu on the right side which lists functions that can be performed simultaneously on all of the like items in that group.
For more information, see Understanding custom groups.
This section describes how to work with repositories. It discusses the deduplication volume manager repository and describes its features and attributes. It describes types of deduplication used in Rapid Recovery, and how deduplication is used throughout the application. 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. Finally, this section describes how to migrate recovery points manually from one repository to another.
A repository is used to store the snapshots that are captured from your protected workstations and servers. The repository can reside on different storage technologies such as Storage Area Network (SAN), Direct Attached Storage (DAS), or Network Attached Storage (NAS).
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. For more information, see Dell Knowledge Base article 118153, "Repository Options: Direct Attached Storage, Storage Area Network or Network Attached Storage."
The storage location for any 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 DVM repository format uses Deduplication Volume Manager (DVM). DVM supports multiple volumes, up to 255 repositories on a single Core, and supports extents. You can create DVM repositories on machines with Windows operating systems only. You can use this repository type when upgrading existing AppAssure installations, and when using new Rapid Recovery installations. You can specify the size of a DVM repository upon creation, and can add extents later.
DVM Repository features and attributes include:
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 Managing a DVM repository.