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

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. Until you delete the attached archive definition, you can easily re-attach and detach the archive, making its recovery points easily accessible.

Use this procedure to attach an archive.

1.
On the Rapid Recovery Core Console, click the Archive drop-down menu, and then select 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:

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

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.

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.

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

1.
On the menu bar of the Rapid Recovery Core Console, click the Archive drop-down menu, and then select Import Archive.
The Import Archive Wizard opens.
2.
On the Import Type page of the wizard, select one of the following options:
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 160. 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.

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.
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 selected Continuous import (by schedule) in step 2, you selected Import all machines in step 6, and at least one machine is not present on the Core—as a protected, replicated, or recovery points only machine—click Next, and then go to step 9.
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.
9.
Click Next.
10.
On the Repository page, complete one of the following options:

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

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

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:

About cloud accounts

Rapid Recovery works with cloud accounts in the following ways:

Archive. You can store a one-time archive or continual scheduled archive in the cloud. This feature is supported for all supported cloud account types. When you archive to the cloud, you can later access the information in the archived recovery points by attaching the archive (for archives created in release 6.0.1 or later). For all archives, you can also import the archive. You can also perform bare metal restore from an archive.
Virtual export. You can perform virtual export to an Azure cloud account. This includes one-time export of a virtual machine, or continual export for a virtual standby VM.

For conceptual information regarding various cloud accounts, see Considering cloud storage options.

For information about configuring timeout settings between the Core and cloud accounts, see Configuring cloud account connection settings.

For information about performing virtual export to the Azure cloud, see Exporting data to an Azure virtual machine.

Related Documents