Chat now with support
Chat with Support

Rapid Recovery 6.1.2 - 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

Forcing an archive job

Using this procedure, you can force Rapid Recovery to perform the archive job on a scheduled archive at any time.

1.
From the Rapid Recovery Core Console, in the icon bar, click the More drop-down, and then select Archives.
Rapid Recovery archives the recovery points according to the settings you chose for that archive, regardless of the scheduled archive time you set.

Checking an archive

Checking an archive verifies whether an archive and its contents are healthy enough to be restored.

You can scan an archive for the integrity of its structure, data segments, and index files by performing an archive check. The archive check verifies the presence of all necessary files within the archive and that the files are healthy. To perform an archive check, complete the steps in the following procedure.

1.
From the Rapid Recovery Core Console, click the More drop-down menu in the icon bar, and then select Archives.
2.
On the Archives page, click Check.
The Check Archive dialog box appears.
3.
For Location type, select one of the following options from the drop-down list:
4.
Based on the location type you selected in Step 3, enter the details for the archive as described in the following table.

Table 161. Archive details

Option

Text Box

Description

Local

Location

Enter the path for the archive.

Network

Location

Enter the path for the archive.

User Name

Enter the user name. It is used to establish logon credentials for the network share.

Password

Enter the password for the network path. It is used to establish logon credentials for 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

Select the folder in which the archived data is saved; for example, Rapid Recovery -5-Archive-[DATE CREATED]-[TIME CREATED]

Option

Description

Index files mapping offsets

This option checks that all the data on the internal structure of the archive is in the correct location.

Structure integrity

This option verifies the presence of certain internal files and the folder structure of the archive. If any files or folders are missing, the check fails.

Checksum integrity

This option checks the integrity of the data segments in the archive to ensure that the segments are healthy.

6.
Click Check File.
Rapid Recovery checks the archive according to your selections.

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 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 162. 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 163. Imported archive location type options

Option

Text Box

Description

Local

Location

Enter the location for the output. It is used to define the location path where you want the archive to reside; for example, d:\work\archive.

Network

Location

Enter the location for the output. It is used to define the location path where you want the archive to reside; for example, \\servername\sharename.

User name

Enter a user name. It is used to establish logon credentials for the network share.

Password

Enter a password for the network path. It is used to establish logon credentials for 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 you want to save the archived data.

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 164. 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 165. 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.
Related Documents