Chat now with support
Chat with Support

Rapid Recovery 6.4 - User Guide

Introduction to Rapid Recovery The Core Console Repositories Core settings 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 Credentials Vault Snapshots and recovery points 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

Attaching an archive

Attaching an archive lets you see recovery points from the archive.

You must have a pre-existing archive created in Rapid Recovery Core release 6.0.1 or later to complete this procedure. For more information, see Creating an archive.

When you attach an archive, the archive name you provide appears as an archive menu in the left navigation menu of the Core Console. Each protected machine with recovery points in the archive is listed separately below the archive menu. You can click any machine name in the archive and browse its recovery points. You can then take the same actions as with any other recovery points currently visible in your Core.

Attaching the archive also caches the credentials for accessing the information. Unless you delete the attached archive permanently, you can easily detach and re-attach an archive, making its recovery points easily accessible without cluttering the Core Console. For information about detaching an archive, see Detaching an archive.

Use this procedure to attach an archive.
  1. On the Rapid Recovery Core Console, click the [Archives]Archive [Drop-down menu] drop-down menu, and then select [Attach]Attach Archive.
    The Attach Archive dialog box appears.
  2. In the Name text box, enter a name for this attached archive.

    The value you type in this field appears in the left navigation menu as the archive menu name.

    Following best practice for display names, the archive name should contain between 1 and 64 alphanumeric characters, including spaces. Do not use prohibited characters or prohibited phrases.

  3. In the Location type drop-down list, select the location type of your archive from the following options:
    • Local
    • Network
    • Cloud
  4. Enter the details for the archive as described in the following table based on the location type you selected in step 3.
    Table 160: Location type details
    Option Text Box Description

    Local

    Location

    Enter the path to the archive; for example, D:\Work\Archive.

    Network

    Location

    Enter the path to the archive; for example, \\servername\sharename.

    User name

    Enter user name for logging in to the network share.

    Password

    Enter the password for logging in to the network share.

    Cloud

    Account

    Select an account from the drop-down list.

    NOTE: To select a cloud account, you must first have added it in the Core Console. For more information, see Adding a cloud account.

    Container

    Select the container of the archive associated with your account from the drop-down menu.

    Folder name

    Enter the name of the folder of the archived data; for example, Rapid-Recovery-Archive-[DATE CREATED]-[TIME CREATED].

  5. Click Attach.
    The archive attaches to this Core and mounts the contents as a file system.

Detaching an archive

You must have an archive attached to your Core to perform this task.

When an archive is attached to your Core, you can navigate through the data in the archive as if the data were currently protected machines.Once you attach an archive, its credentials are cached and it remains visible in your Core until you detach it.

Perform this task after you have accomplished your objectives for attaching the archive, to remove it from view on your Core.

NOTE: Detaching the archive does not delete the data; it only removes the data from current view.

Use this procedure to detach an archive.
  1. On the left navigation menu of the Rapid Recovery Core Console, locate the archive you want to detach.
  2. Click on the [Ellipsis] ellipsis for the archive, and from the context-sensitive menu, select [Delete] Delete.
  3. In the resulting dialog box, confirm that you want to remove the selected archive.
    The dialog box closes. After a brief pause, the attached archive is removed from the Core Console. This action is logged as an alert.

Importing an archive

You can use this procedure to import an archive one time, or schedule an archive to import on a recurring basis.

When you want to recover archived data, you can import the entire archive to a specified location.

Caution: Perform this step only after careful consideration. Importing an archive repopulates the repository with the contents of the archive, replacing any new data in the repository since the archive was captured.

To import an archive, complete the steps in the following procedure.

  1. On the menu bar of the Rapid Recovery Core Console, click the [Archives] Archive[Drop-down menu] drop-down menu, and then select [Import] Import Archive.

    The Import Archive Wizard opens.

  2. On the Import Type page of the wizard, select one of the following options:
    • One-time import
    • Continual import (by schedule)
  3. Click Next.
  4. On the Location page, select the location of the archive you want to import from the drop-down list, and then enter the information as described in the following table:
    Table 161: Imported archive location type options
    Option Text Box Description
    Local

    Location

    Enter the local path where you want the archive to reside; for example, d:\work\archive.

    Network

    Location

    Enter the network path where you want the archive to reside; for example, \\servername\sharename.

    User name

    Enter the user name for the user with access to the network share.

    Password

    Enter the password for the user with access to the network share.

    Cloud

    Account

    Select an account from the drop-down list.

    NOTE: To select a cloud account, you must first have added it in the Core Console. For more information, see Adding a cloud account.

    Container Select a container associated with your account from the drop-down menu.
    Folder name Enter a name for the folder in which the archived data is saved.
  5. Click Next.
  6. On the Archive Information page of the wizard, if you want to import every machine included in the archive, select Import all machines.
  7. Complete one of the following options based on your selection:
    • If you selected One-time import in step 2, you selected Import all machines in step 6, and all the machines are present on the Core—as protected, replicated, or recovery points only machines— go to step 12.
    • If you did not import all machines in step 6, click Next, and then continue to step 8.
  8. On the Machines page, select the machines that you want to import from the archive.
    • If you selected One-time import in step 2, and at least one machine is not present on the Core—as a protected, replicated, or recovery points only machine—use the drop-down lists to select a repository for each machine you want to import, and then go to step 12.
    • If all machines are already present on the Core—as protected, replicated, or recovery points only machines—go to step 12.
  9. Click Next.
  10. On the Repository page, complete one of the following options:
    • If a repository is associated with the Core, select one of the options in the following table.
      Table 162: Repository options
      Option Description

      Use an existing Repository

      Select a repository currently associated with this Core from the drop-down list.

      Create a Repository

      In the Server text box, enter the name of the server on which you want to save the new repository—for example, servername or localhost—and then see Creating a DVM repository.

    • If no repository is associated with the Core, enter the name of the server on which you want to save the new repository—for example, servername or localhost—and then see Creating a DVM repository or Connecting to an existing repository.
  11. If you chose to Continuous import (by schedule) in step 2, on the Schedule page, select the options described in the following table.
    Table 163: Schedule import options
    Option Description
    Daily Click the clock icon and use the up and down arrows to select at what time you want to the archive job to begin.

    If you are using a 12-hour time system, click the AM or PM button to specify the time of day.

    Weekly Select the day of the week and then the time you want the archive job to begin.

    If you are using a 12-hour time system, click the AM or PM button to specify the time of day.

    Monthly Select the day of the month and the time you want the archive job to begin.

    If you are using a 12-hour time system, click the AM or PM button to specify the time of day.

    Pause initial importing

    Select this option if you do not want the import job to begin at the next scheduled time after you complete the wizard.

    NOTE: You may want to pause the scheduled import if you need time to prepare the target location before importing resumes. If you do not select this option, importing begins at the scheduled time.

  12. Click Finish.

Cloud accounts

Rapid Recovery lets you define connections between existing cloud storage or cloud service providers and your Rapid Recovery Core. Compatible cloud services include Microsoft Azure, Amazon Web Services (AWS), any OpenStack-based provider (including Rackspace), and Google Cloud. US government-specific platforms include AWS GovCloud (US) and Azure Government. You can add any number of cloud accounts to the Core Console, including multiple accounts for the same provider.

The purpose of adding cloud accounts to your Core Console is to work with them as described in the topic About cloud accounts.

Once added, you can manage the connection between the Core and the cloud accounts. Specifically, you can edit the display name or credential information, configure the account connection options, or remove the account from Rapid Recovery. When you edit or remove cloud accounts in the Core Console, you do not change the cloud accounts themselves—just the linkage between those accounts and your ability to access them from the Core Console.

This section describes how to define links between existing cloud storage provider or cloud service provider accounts, and the Rapid Recovery Core Console. It also describes how to manage those cloud accounts in Rapid Recovery.

Topics include:

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating