Chat now with support
Chat with Support

The Quest and One Identity Support Portals will be unavailable on Friday July 10, 2020 from 5:30 PM to 6:30 PM for website maintenance.

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

Denying a replication request

Complete the steps in the following procedure to deny a replication request sent to a third-party core from a customer.

To deny a request without reviewing it, see Ignoring a replication request from a customer.

1.
On the target Core, navigate to the Rapid Recovery Core Console.
The Replication page appears.
3.
On the Replication page, click Request (#).

The Pending Replication Requests section appears.

The Review Replication Request window appears.

5.
Click Deny.

Replication is denied. Notification of denial appears under Alerts on the Events page of the source Core.

Ignoring a replication request from a customer

As a third-party service provider of a target core, you have the option to ignore a request for replication sent from a customer. This option could be used if a request was sent by mistake or if you want to deny a request without reviewing it.

For more information about replication requests, see Reviewing a replication request from a customer.

Complete the following procedure to ignore a replication request from a customer.

1.
On the target Core, navigate to the Rapid Recovery Core Console.
The Replication page appears.
3.
On the Replication page, click Request (#).

The Pending Replication Requests section appears.

5.
On the Ignoring request dialog box, click Yes to confirm the command.

Notification that the request has been ignored is sent to the source Core, and the request is removed from the Replication page on the target Core.

Adding a machine to existing replication

After replication is established between a source and target Core, it is possible to add new protected machines to replicate to the target. Complete the steps in the following procedure on the source Core to add a new protected machine to a paired target Core for replication.

For more information about replication, see Replication and Replicating to a self-managed target Core.

1.
Navigate to the Rapid Recovery Core console of the source Core.
The Replication Wizard opens to the Protected Machines page.
3.
On the Protected Machines page, select the protected machines you want to replicate, and then use the drop-down lists in the Repository column to select a repository for each protected machine.
a.
On the Protected Machines page of the Replication Wizard, select Use a seed drive to perform initial transfer.
b.
Click Next.
c.
On the Seed Drive Location page of the wizard, use the Location type drop-down list to select from the following destination types:

Table 101. Archive details

Option

Text Box

Description

Local

Output 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

Output 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 the archived data is to be saved. The default name is Rapid-Recovery-Archive-[DATE CREATED]-[TIME CREATED]

e.
Click Next.
f.
On the Seed Drive Options page of the wizard, enter the information as described in the following table.

Table 102. Seed drive options

Item

Description

Maximum Size

Large archives of data can be divided into multiple segments. Select the maximum amount of space you want to reserve for creating the seed drive by doing one of the following:

Select Entire Target to reserve all available space in the path provided on the Seed Drive Location page (for example, if the location is D:\work\archive, all of the available space on the D: drive is reserved).

Recycle action

In the event the path already contains a seed drive, select one of the following options:

Comment

Enter a comment that describes the seed drive.

Add all Agents to Seed Drive

Select this option to replicate all protected machines on the source core using the seed drive. This option is selected by default.

Build recovery point chains (fix orphans)

Select this option to replicate the entire recovery point chain to the seed drive. This option is selected by default.

NOTE: Typical seeding in Rapid Recovery 5.4 replicates only the latest recovery point to the seed drive, which reduces the amount of time and space required for creating the seed drive. Opting to build recovery point (RP) chains to the seed drive requires enough space on the seed drive to store the latest recovery points from the specified protected machine or machines, and may take additional time to complete the task.
If you cleared the Add all Agents to Seed Drive check box, click Next.
If you selected Add all Agents to Seed Drive, go to Step 5.
h.
On the Protected Machines page of the wizard, select the protected machines you want to replicate to the target Core using the seed drive.
5.
Click Finish.

Consuming the seed drive on a target Core

Complete the follow procedure to consume the data from the seed drive file on the target Core.

2.
On the target Core, open the Rapid Recovery Core Console, and from the icon bar, click [Replication] (Replication).
The Replication page appears.
3.
On the Replication page, under Incoming Replication, click the drop-down menu for the correct source Core, and then select Consume.

The Consume dialog box appears.

4.
In the Location type field, select one of the following options from the drop-down list:

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

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

6.
Click Check File.

The Core searches for the file.

After finding the file, the following text boxes appear in the Consume window, pre-populated with the data gathered from Step 4, Step 5, and the file. The Date Range displays the dates of the oldest and newest recovery points contained in the seed drive. Any comments entered when the seed drive was created are automatically imported.

7.
On the Consume dialog box, under Agents, select the machines for which you want to consume data.
8.
Click Consume.
Related Documents