Chat now with support
Chat with Support

Rapid Recovery 6.1.3 - User Guide

Introduction to Rapid Recovery Core Console Core settings Repositories Encryption keys Protecting machines
About protecting machines with Rapid Recovery Support for dynamic and basic volumes 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 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 Viewing the recovery progress Starting a restored target server Troubleshooting connections to the Universal Recovery Console Repairing boot problems Performing a file system check on the restored volume
Managing aging data Archiving Cloud storage accounts The Local Mount Utility The Central Management Console Core Console references Command Line Management utility PowerShell module
Prerequisites for using PowerShell Working with commands and cmdlets Rapid Recovery PowerShell module cmdlets Localization Qualifiers
Scripting REST APIs About us Glossary

Managing an R3 repository

Creating an R3 repository
Changing R3 repository settings

The R3 repository stores outdated snapshots that are captured from the protected machines in your environment.

Managing an R3 repository involves the following operations:

1.
Adding an R3 repository. To tier your outdated recovery points to secondary storage, you must first use the RDS services native to the DR appliance to create a repository. For more information, see Understanding repositories. For information about creating an R3 repository, see Creating an R3 repository.
2.
Viewing repository details. For more information about viewing repository details, see Viewing or modifying repository details.
3.
Modifying repository settings. For more information about modifying repository settings for an R3 repository, see Viewing or modifying repository details.
4.
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 an R3 repository

This process describes how to create an R3 repository for secondary storage of recovery points on a DR appliance from the Rapid Recovery Core. The DR appliance includes Rapid Data Storage (RDS) services, which support the R3 repository.

* 
NOTE: If you want to create a DVM repository, see the topic Creating a DVM repository.
•
You must have administrative access to the DR appliance on which you want to create the R3 repository.
•
You must specify the host name of the DR appliance.
•
For planning purposes, 128GB of the storage volume is reserved by default for the deduplication dictionary.
•
The Core server can be a software-based Windows server meeting system requirements, or it can be any DL backup appliance other than the DL1000. The DL1000 backup appliance only supports DVM repositories.

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 repository using the Rapid Recovery Repository (R3) technology.

1.
Navigate to the Rapid Recovery Core Console.
2.
On the icon bar, click [More] (More), and then select Repositories.

The Repositories page appears.

3.
At the top of the page, under the Repositories page title, click the drop-down arrow next to Add New DVM Repository, and then click Add New R3 Repository.

The Create Repository Wizard appears.

4.
On the Connection page, in the Server text field, enter the IP address or network server name for the DR appliance on which the R3 repository is located. Then click Next.
5.
If you see an RDS Authorization page, it means that the DR appliance that you specified has non-default credentials. Enter the information about the machine to which you want to connect as described in the following table, and then click Next.

Table 25. Admin authorization settings

Descriptions of the credentials required for connecting to the machine on which you want to create a repository.

Text Box

Description

User name

The user name used to connect to the DR appliance running the RDS service; for example, backup_user.

Password

The password used to connect to the DR appliance running the RDS service.

6.
On the Configuration page, enter repository configuration information as described in the following table and then click Next.

Table 26. Configuration page settings

Descriptions of the settings available for configuring the repository.

Text Box

Description

Name

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.

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

Comments

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.

7.
On the Security options page, to make it 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 a required 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.
8.
On the Security options page, when satisfied with your settings, click Finish.

The Create Repository Wizard closes. The repository information you specified generates a Create Repository job, which starts immediately. It may take several minutes to complete. When the job is completed, the new repository is then listed in the summary table in the R3 Repositories pane.

9.
Optionally, you can track the progress of the R3 repository creation task. For more information, see Viewing tasks.

Changing R3 repository settings

This procedure assumes that your Core has a functioning R3 repository.

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

1.
From the Core Console, in the icon bar, click the More More menu icon menu, and then click Repositories.
2.
On the Repositories page, click the Actions Actions icon menu for the repository whose settings you want to change, and then click Settings.
The Edit Repository Settings Wizard appears.
3.
On the Configuration page, you can change the settings described in the following table.

Option

Description

Name

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

Comments

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

4.
Click Next.
5.
On the Security options page, to make it 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 a required 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.
6.
Click Finish.
The changes are applied to the repository.

Managing a DVM repository

Creating a DVM repository
Adding a storage location to an existing DVM repository
About checking the integrity of DVM repositories
Opening an existing DVM repository
About the Repository Optimization Job

Before you can use Rapid Recovery, you need to set up one or more repositories on the Rapid Recovery Core. A repository stores your protected data; more specifically, it stores the snapshots that are captured from the protected machines in your environment.

Managing a DVM repository involves the following operations:

1.
Creating a DVM repository. Before creating a repository, consider the appropriate technology type.

For information about repositories, see Understanding repositories.

For information about creating a DVM repository, see Creating a DVM repository.

2.
Adding a new storage location. For more information on adding a new storage location to a DVM repository, see Adding a storage location to an existing DVM repository.
3.
Modifying repository settings. For more information about modifying repository settings for a repository, see Viewing or modifying repository details
4.
Checking a repository. For more information about checking a DVM repository, see Checking a repository.
5.
Performing a repository optimization job. For more information about the repository optimization job, see About the Repository Optimization Job. For steps to optimize an existing DVM repository, see Optimizing a DVM repository.
6.
Deleting a repository. For more information about deleting a repository, see Deleting a repository.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating