Chat now with support
Chat with Support

Rapid Recovery 6.6 - User Guide

Introduction to Rapid Recovery The Core Console Repositories Core settings 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 Managing privacy Encryption Credentials Vault Replication Events Reporting VM export Restoring data Bare metal restore
About bare metal restore Differences in bare metal restore for Windows and Linux machines Understanding boot CD creation for Windows machines Managing a Linux boot image Performing a bare metal restore using the Restore Machine Wizard 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 Core Console references REST APIs 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 DVM repository that is currently owned by another functioning Core, you must first prepare for the impending transfer of ownership. The following prerequisites apply:

  • If the original Core containing the repository is functioning, temporarily stop protection of machines on that Core.
  • Then, stop the Core service of the original Core while you transfer ownership.
  • After connecting the repository to the new Core as described in this procedure, return to the original Core. Ensure that all machines you continue to protect have a repository associated with them.
  • Then restart the Core services on the original Core.

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. 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.

Caution: Connecting to a repository from another Core changes ownership of the repository. After you connect to the repository, the information is then accessible only to the second Core. 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.

Complete the following procedure to connect to an existing repository.

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

    The Repositories page displays.

  3. To select a repository type, click the drop-down [More] 
    menu next to Connect to Existing.
  4. In the Connect Existing DVM Repository dialog box, enter the following information for the repository you want to open, and then click Connect.
    Table 14: Open Existing DVM Repository options
    Text Box Description


    The path for the repository (for example, D:\work\machine for a local path, or \\\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.


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

    The dialog box closes, and the selected repository is added to your current Core.

  5. On the Cores page of the wizard, click to select the appropriate Core, and then click Next.
  6. On the Details page of the wizard, to ensure that the selected Core is the one to which you want to connect, review the displayed details, and then 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, or resuming protection that is paused, see Pausing and resuming protection. For more information on pausing replication, or resuming replication that is paused, 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

To view repository details, your Core must first contain a repository. For information about creating a DVM repository, see Creating a DVM repository. For more information about creating an Azure replication repository, see Creating an Azure repository

In the pane for each repository type, each repository added to the Core is displayed.

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

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.
  2. On the icon bar, click [More] 
    (More), and then select Repositories.

    The Repositories page is displayed.

  3. At the top of the page, under the Repositories page title, the following general actions are available:
    Table 15: Repository actions
    Option Description


    This option opens the Create Repository Wizard, a workflow that helps you define all requirements to create a new DVM repository. For more information, see Creating a DVM repository.

    Connect to Existing

    For DVM repositories only, this option opens the Connect Existing DVM Repository dialog box. When you provide the local or CIFS share path and connection credentials, this lets you open a repository from another Core.

    NOTE: This process changes ownership of the repository to your Core.

    For more information, see Connecting to an existing repository.


    Refreshes the list of repositories shown on the page.

  4. From the (More options) drop-down menu for any repository, you can perform the following actions:
    Table 16: Repository options
    Option Description

    Expand repository

    For DVM repositories only, expand the existing repository by adding a storage location.

    NOTE: Before extending a DVM repository volume, Quest recommends pausing protection and pausing all jobs (or waiting for them to complete). Then extend the volume. Finally, resume protection and any paused jobs.


    Perform a repository check.


    View or modify repository settings. These settings include:

    • Viewing the repository name
    • Viewing or changing the maximum concurrent operations
    • Viewing or changing a description for the repository
    • Enabling or disabling deduplication
    • Enabling or disabling compression for data stored in the repository


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


    Delete a repository.

    Caution: This option completely deletes the selected DVM repository and all data it contains.

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:

  • Check repository
  • Mounting repository
  • Loading the recovery points from repository

The check also performs the "Recalculate deduplication cache for repository" task.

NOTE: This procedure should only be performed for diagnostic purposes. For example, run this check in the event of hardware failure, improper shutdown of the Core, or failure when importing a repository.

  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. To check a repository, in any row of the summary table for any repository technology type, click [More] 
    (More options), and then select Check.

    The Check Repository dialog box appears.

  4. 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.

    Active jobs are canceled and the Checking Repository job starts.

Deleting a repository

Complete the steps in this procedure to delete a repository.

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

    The Repositories page is displayed.

  3. In the appropriate repositories summary table, from the row representing the repository you want to delete, click [More] 
    (More options) to expand the drop-down menu, and then select Delete.

    A warning message appears to confirm deletion.

    Caution: When a repository is deleted, the data contained in the repository is discarded and cannot be recovered.

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

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating