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

Replicating to a third-party target Core

A third-party Core is a target Core that it managed and maintained by an MSP. Replicating to a Core managed by a third party does not require the customer to have access to the target Core.

The process of replicating to a third-party Core involves tasks that must be completed by the customer as well as the third party. After a customer submits a request for replication on the source Core or Cores, the MSP must complete the configuration on the target Core by reviewing the request.

NOTE: This configuration applies to Hosted and Cloud Replication. The Rapid Recovery Core must be installed on all source Core machines. If you are configuring Rapid Recovery for Multi-Point to Point replication, you must perform this task on all source Cores.

To replicate to a target Core managed by a third party, complete the following tasks:

Submitting a replication request to a third-party service provider

If you are an end user who subscribes to a core managed by a third party, such as an MSP, complete the steps in this procedure to submit a replication request to your third-party service provider.

1.
Navigate to the Rapid Recovery Core.
The Replication Wizard appears.
3.
On the Target Core page of the Replication Wizard, select I have a subscription to a third-party providing off-site backup and disaster recovery services, and then enter the information as described in the following table.

Table 97. Third-party target core information

Text Box

Description

Host Name

Enter the host name, IP address, or FQDN for the third-party core machine.

Port

Enter the port number that was given to you by your third-party service provider.

The default port number is 8006.

1.
Select Use an existing target core.
3.
Click Next.
4.
Click Next.
5.
On the Request page of the Replication Wizard, enter the information as described in the following table.

Table 98. Third-party target core details

Text Box

Description

Email Address

Enter the email address associated with your third-party service subscription.

Customer ID (optional)

Optionally, enter the customer ID that was assigned to you by the service provider.

6.
Click Next.
7.
On the Protected Machines page of the Replication Wizard, select the protected machines you want to replicate to the third-party core.
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 Replication Wizard, use the Location type drop-down list to select from the following destination types:

Table 99. 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 seed drive 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 Replication Wizard, enter the information as described in the following table.

Table 100. 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:

Do not reuse. Does not overwrite or clear any existing seed data from the location. If the location is not empty, the seed drive write will fail.
Replace this Core. Overwrites any pre-existing seed data pertaining to this core but leaves the data for other cores intact.
Erase completely. Clears all seed data from the directory before writing the seed drive.

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 points 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 AppAssure 5.4 replicated only the latest recovery point to the seed drive, which reduced 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 9.
h.
On the Machines page of the Replication Wizard, select the protected machines you want to replicate to the target core using the seed drive.
9.
Click Finish.

Reviewing a replication request from a customer

After an end user completes the procedure Submitting a replication request to a third-party service provider, a replication request is sent from the source core to the third-party target core. As the third party, you can review the request, and then approve it to begin replication for your customer, or you can deny it to prevent replication from occurring.

Choose from the following options:

Approving a replication request

Complete the following procedure to approve a replication request on a third-party target core.

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.

Select Replace an existing replicated Core, and then select a core from the drop-down list.
Select Create a new source Core, and then confirm that the Core Name, customer Email Address, and Customer ID, provided are correct. Edit the information as necessary.
7.
Optionally, in the Comment text box, enter a description or message to include in the response to the customer.
8.
Click Send Response.

Replication is accepted.

Related Documents