Chat now with support
Chat with Support

Rapid Recovery 6.2 - User Guide

Introduction to Rapid Recovery Core Console Core settings
Core settings key functions Rapid Recovery Core settings Core-level tools
Repositories Managing privacy Encryption Protecting machines
About protecting machines with Rapid Recovery Understanding the Rapid Recovery Agent software installer Deploying Agent to multiple machines simultaneously from the Core Console Using the Deploy Agent Software Wizard to deploy to one or more machines Modifying deploy settings Understanding protection schedules Protecting a machine About protecting multiple machines Enabling application support Settings and functions for protected Exchange servers Settings and functions for protected SQL servers
Managing protected machines Snapshots and recovery points Replication Events Reporting VM export Restoring data Bare metal restore
Bare metal restore for Windows machines Understanding boot CD creation for Windows machines Using the Universal Recovery Console for a BMR Performing a bare metal restore for Linux machines Verifying a bare metal restore
Managing aging data Archiving Cloud accounts The Local Mount Utility Core Console references REST APIs About us Glossary

Managing a tiering repository

A tiering repository is a secondary repository defined on your Core into which recovery points can be relocated from a primary DVM repository.

Once they are moved, recovery points are deleted from your primary DVM repository. The Core continues to manage the relocated recovery points until they are eventually rolled up and deleted.

To tier backup data, you must define the age at which recovery points in your DVM repository should begin to tier. You accomplish this on the retention period page.

Before you can relocate recovery points to a tiering repository, you must create the secondary repository on your Rapid Recovery Core.

Managing an tiering repository involves the following operations:

Creating a tiering repository. To tier your outdated recovery points to secondary storage, you must first define the tiering repository in the Rapid Recovery Core Console. In release 6.2, tiering is only supported on DR Series deduplication appliances running OS 4.0. The repository requires RDS services native to the DR appliance. For more information, see Understanding repositories. For information about creating a tiering repository, see Creating a tiering repository.
Connecting to a repository. For more information about connecting to an existing tiering repository, see Connecting to an existing repository.
Define retention period. After you have added a tiering repository to your Core, define in the retention period the age for recovery points to begin tiering them from your DVM repository to your tiering repository. You must set up tiering using a customized retention policy for specific protected machines. For information about setting your retention policy to tier recovery points for specific protected machines, see Customizing retention policy settings for a protected machine.
Modifying repository settings. For more information about modifying repository settings for a tiering repository, see Viewing or modifying repository details.
Checking a repository. For more information about checking a repository, see Checking a repository.
Deleting a repository. For more information about deleting a repository, see Deleting a repository.

For information on managing a DVM repository, see Managing a DVM repository.

Creating a tiering repository

This process describes how to create a tiering repository from the Rapid Recovery Core Console, which can be used as secondary storage only for backups of machines protected in your Core.

NOTE: In release 6.2, the only supported physical location for tiering repositories is a DR Series deduplication appliance running OS 4.0. Setting your retention policy to tier, you can specify a time after which recovery points are relocated from your DVM repository to the tiering repository on your DR appliance. The DR appliance includes Rapid Data Storage (RDS) services.

If you want to create a primary DVM repository, see the topic Creating a DVM repository.

The Core server can be a properly-sized software-based Windows server meeting Rapid Recovery operating system and file system requirements. It can also be any DL backup appliance other than the DL1000 or DL4000. These appliance models currently only support DVM repositories.
NOTE: For information about system requirements, see the Rapid Recovery System Requirements Guide.

On a thin-provisioned storage volume, the repository volume displays the amount of space consumed from the operating system. A thick-provisioned volume may show the entire contents of the drive to be consumed with data. You can monitor your repositories regularly using the repository report, which helps you to avoid filling a repository volume. For information on manually generating a repository report, see Generating a Core report on demand. For information on automating the generation of reports on an ongoing basis, see Scheduling a report.

Complete the steps in this procedure to create a tiering repository.

Navigate to the Rapid Recovery Core Console.

The Repositories page appears.

The Create Repository Wizard appears.

On the Connection page, in the Server text field, enter the IP address or network server name for the machine to which you want to connect and add a repository. Then click Next.
On the Configuration page, enter repository configuration information as described in the following table and then click Next.

Table 34. Configuration page settings

Text Box



Enter a display name for your repository.

By default, this text box consists of the word Repository and a number. The suggested name corresponds to the number of repositories that currently exist for this Core. For example, for the first repository, the suggested name is Repository 1; for the second repository, the suggested name is Repository 2; and so on.

If using repositories of more than one technology type, you may want to include the type in the name, such as TieringRepository1.

Repository names must contain between 1 and 40 alphanumeric characters, including spaces. Do not use prohibited characters or prohibited phrases.


This information is optional.

You can use it to describe the type of information you save in this repository. For example, “This repository holds outdated recovery points for all SQL and Exchange Servers in the Accounting domain.”

This information can be modified at any time.

Storage group and container options

Select options for your tiering repository as follows:

Select Use default storage group and container to create the structure for your repository in default locations. Most users can select this default option.
Select Choose an existing storage group and container if you want to specify the structure for your tiering repository, and select the appropriate objects. This option is for advanced users that are aware of the storage group and container options.
On the Security options page, do one of the following:

This step is an optional precaution. Your repository is already secure; however, access to the Rapid Recovery Core requires authentication. These security options apply when a user attempts to open this repository from of a different Rapid Recovery Core. For additional security, you can also apply Core-level encryption keys to backups for any protected machine.

To complete the process for creating a tiering repository without also securing the repository with your license, clear the Secure this repository with your unique license option, click Finish, and in he Unsecure Repository Warning dialog box, click Yes.
The Create Repository Wizard closes. The repository information you specified generates a Create Repository job, which starts immediately. This job and the resulting repository creation takes several minutes to complete. When the job completes, a Tiering Repositories pane appears at the bottom of the Repository page, showing the new tiering repository you just added.

Checking a repository

Rapid Recovery lets you perform a diagnostic check of a repository volume when errors occur on the Core. Errors could be the result of the Core being improperly shut down, a repository failing to mount or unmount, a hardware failure, or other environmental, lower IP stack factors that can be exposed in Rapid Recovery functionality.

For all repository technology types, the check performs the following tasks:

For DVM repositories only, the check also performs the "Recalculate deduplication cache for repository" task.

Navigate to the Rapid Recovery Core Console.

The Repositories page appears.

The Check Repository dialog box appears.
In the Check Repository dialog box, confirm that you understand that all active tasks associated with this repository will be canceled and that you want to proceed.
Optionally, to track the status of the job, click the Running tasks drop-down menu in the button bar, and then click the Maintaining Repository job.

Changing repository settings

In the repository settings, you can change the display name, comments, and security option.

From the Rapid Recovery Core Console, in the icon bar, click [More] (More), and then select Repositories.
On the Repositories page, scroll down to the Tiering Repositories pane.
The Edit Repository Settings wizard displays.
On the Configuration page, you can change the settings described in the following table.




The display name of the repository. For example, Repository 1.


Notes or a description that you want to associate with this repository.

Click Next.
On the Security Options page, to establish security so that only a Core with the same license number as this Core is permitted to communicate with the repository, select Secure this repository with your unique license.
NOTE: This step is an optional precaution. Your repository is already secure; however, access to the Rapid Recovery Core requires authentication. These security options apply when a user attempts to open this repository from of a different Rapid Recovery Core. For additional security, you can also apply Core-level encryption keys to backups for any protected machine.
Click Finish.
If you chose not to add additional security to your repository in the prior step, the Unsecure Repository Warning dialog box appears. Click Yes to confirm that you do not want to secure the repository by license key.
The Edit Repository Settings wizard closes. The changes you made to the repository settings are immediately applied.
Related Documents