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

Connecting to an existing repository

To perform this procedure, you must have the appropriate credentials for the original Core, and you must have the local or network path, IP address or server name.

If connecting to a tiering repository, that repository must be disconnected from the Core that previously used it. For more information about disconnecting a repository, see the topic Disconnecting a repository.

If connecting to a DVM repository that is not currently associated with another Core, no other prerequisites apply.

If connecting to a DVM repository that is currently owned by another functioning Core, you must first prepare for the impending transfer of ownership. The following prerequisites apply:

For more information about pausing protection, see Pausing and resuming protection. For more information about shutting down and restarting the Core service, see Restarting or shutting down the Core service.

From your Rapid Recovery Core Console, you can connect to an existing repository that is currently managed in a different Core. Completing this connection changes the ownership of the repository from the original Core to your current Core. After you connect to the repository, the information is then accessible only to the second Core, and not in the original Core. The repository you connect to must be accessible on a shared network location, or on a storage device accessible to the second Core.

This process is useful if your original Core is down and you wish to stand up a replacement Core. If you later wish to change ownership again from the second Core to a third Core (or to the original), you can do so. The same rules apply.

The original Core losing the repository must not be in use. For example, the machine must be turned off, not accessible to the network, or the Core services must be stopped.

Tiering repositories can be secured with a unique license. Selecting this additional security setting prevents unauthorized individuals from being able to wrest control of your repository to another repository. If you secure your repository by its unique license, only administrators with access to your license key could connect to your repository. For more information about updating your repository settings, see the procedure Changing repository settings.

Complete the following procedure to connect to an existing repository.

1.
Navigate to the Rapid Recovery Core Console.

The Repositories page displays.

3.
To connect to an existing DVM repository, click the drop-down [More] menu next to Connect to Existing, and then select DVM Repository.
The Connect Existing DVM Repository dialog box opens.
5.
To connect to an existing tiering repository, click the drop-down [More] menu next to Connect to Existing and then select Tiering Repository. Proceed to step 7.
6.
In the Connect Existing DVM Repository dialog box, enter the following information for the repository you want to open, and then click Connect.

Table 35. Open Existing DVM Repository options

Text Box

Description

Path

The path for the repository (for example, D:\work\machine for a local path, or \\10.10.99.155\repositories by IP address, or \\servername\sharename for a network path).

User name

If the repository has a network path, enter the user name for logging in to the network share.

Password

If the repository has a network path, enter the password for logging in to the network share.

7.
In the Connect Repository Wizard, on the Connection page, enter the server name or IP address of the machine hosting the repository you want to connect to this Core, and then click Next.
8.
On the Cores page of the wizard, click to select the appropriate Core, and then click Next.
9.
On the Details page of the wizard, review the details to ensure the selected Core is appropriate. To connect to the selected Core, click Finish.

If you see an error indicating that the selected repository is in use, log into that Core and prepare it for transferring ownership of its repository to this Core. Pause any existing protection; pause any existing replication; wait for queued jobs to complete, or cancel them. Shut down the Core services or gracefully power down the Core server, and then repeat this procedure. For more information on pausing protection, see Pausing and resuming protection. For more information on pausing replication, see Pausing and resuming replication. For more information about shutting down and restarting the Core service, see Restarting or shutting down the Core service.

Viewing or modifying repository details

In the DVM Repositories pane, each DVM repository added to the Core is displayed.

If you click (Expand), child rows display the data and metadata locations for the DVM repository.
You can also (Contract) the view.

In the Tiering Repositories pane, at least three rows of data are used to represent each existing repository:

The top row is the RDS server. You can connect to a maximum of three RDS servers per Core.
The second row shows the storage group. Each RDS server can include a maximum of five storage groups.
The third row lists the tiering repository.

You can (Expand) and (Contract) the view in the Tiering Repositories panes to save space.

Repository details differ based on the repository technology type. To view or modify repository details, use the following procedure:..

1.
Navigate to the Rapid Recovery Core Console.

The Repositories page is displayed.

Option

Description

Create

From the drop-down menu, select the appropriate repository type to create a repository. You can choose from:

Connect to Existing

From the drop-down menu, select repository type to open a repository from another Core. This process changes ownership of the repository to your Core. You can choose from:

For more information, see Connecting to an existing repository.

Refresh

Refreshes the list of repositories shown on the page.

4.
In the DVM Repositories pane, from the (More options) drop-down menu for any DVM repository, you can perform the following actions:

Option

Description

Add Storage Location

Extend the existing repository by adding a storage location

Check

Perform a repository check.

Settings

View or modify repository settings. These settings include:

Optimize

Perform a repository optimization job. For more information, see About DVM repository optimization.

Delete

Delete a repository.

5.
In the Tiering Repositories pane, from the (More options) drop-down menu for any RDS service, you can perform the following actions:

Option

Description

Change Credentials

Lets you change your password associated with the currently selected host. This action is useful when changing ownership of a repository to maintain security.

NOTE: Confirm the new password and click Save to update your credentials.
7.
In the Tiering Repositories pane, from the (More options) drop-down menu for any Tiering repository, you can perform the following actions:

Option

Description

Settings

Opens the Edit Repository Settings wizard, in which you can view or modify repository settings. These settings include:

Check

Cancels all active tasks for the selected repository and then performs a repository check.

Disconnect

Unmounts the selected repository.

NOTE: After you disconnect, you can connect to the repository again later using the Connect to Existing feature at the top of the Repositories page.

Delete

Delete a repository.

Disconnecting a repository

From the Repositories page, you can disconnect an existing repository. This process does not delete data in the repository. It simply dismounts the current connection to the repository and its contents. This is useful, for example, in a situation in which you want to connect to the repository from a different Core.

Perform this procedure to disconnect a tiering repository.

1.
From the Rapid Recovery Core Console, in the icon bar, click the More menu icon (More) menu, and then click More menu icon Repositories.
2.
On the Repositories page, from the row representing the repository you want to disconnect, click Actions icon (More options) and then select Disconnect.
The Disconnect Repository dialog box opens.
The repository disconnects, and the Repositories page refreshes. The repository no longer appears in the list of currently available repositories.

To reconnect to the repository, see the procedure Connecting to an existing repository.

Deleting a repository

Complete the steps in this procedure to delete a repository.

1.
Navigate to the Rapid Recovery Core Console.

The Repositories page is displayed.

A warning message appears to confirm deletion.

4.
Click Yes to confirm the deletion of the repository.
Related Documents