Chat now with support
Chat with Support

Rapid Recovery 6.1.2 - Third-Party Integration Guide

Introduction to Rapid Recovery Add-on for Kaseya Introduction to Rapid Recovery and installing it using the Add-on for Kaseya Using the Rapid Recovery Add-on for Kaseya About us

Managing replication in the Rapid Recovery Add-on for Kaseya

Replication is the managing and transference of data (recovery points) between a source and target core. A snapshot of the recovery points on the source core is captured and then transmitted to a target core for redundancy. There are multiple ways in which replication can be configured; for example, between two cores at the same site or across two locations on a per machine basis. Rapid Recovery asynchronously transmits the snapshot of the replicated data (recovery points) to the target core for storage. Outbound replication can also be configured to a Managed Service Provider (MSP) providing off-site backup and disaster recovery service, or to a self-managed core.

The Rapid Recovery Add-on for Kaseya supports two types of replication. Replication by request is useful when you know the name but do not know the credentials for the Core to which you want to replicate; for example, an MSP-hosted core. On-demand replication is replication for a self-managed core, that is, a core that you own.

In the Rapid Recovery Add-on for Kaseya, the following list describes the replication tasks you can perform:

Preparing for replication

Use Prepare Replication to configure replication and pair (establish a connection) between two Cores, that is, one source and one target.

The Prepare Replication dialog box opens.

3.
On the Select remote Core tab, do one of the following:
For replication by request, select I have a subscription to a third-party providing off-site backup and disaster recovery services and wish to replicate my backups to that service (generate replication request), and then enter the information described in the following table.

Table 14. Replication request settings

Text Box

Description

Host Name

Enter the fully qualified domain name (FQDN) for the Core.

Port

Enter the port number that you received from the service provider. The default port number is 8006.

For on-demand replication, select I have my own remote Core I wish to replicate to (establish replication on-demand), and then enter the credentials for the target core as they are described in the following table.

Table 15. On-demand replication settings

Text Box

Description

Host Name

Enter the host name for the target (remote) Core.

Port

Enter the port number. The default port number is 8006.

User Name

The user name for logging on to the Core.

Password

The password associated with this user name.

4.
Click Continue.
b.
Click Finish to close this dialog box and submit the replication request.

On the Prepare Replication page, a message displays in the State column indicating that replication by request is in progress, followed by a status of Pending. If the request is approved, this status changes to Established. For replication on demand, the State column displays the text, Pairing.

Establishing replication

Use Establish Replication to configure on-demand replication when you have credentials for both source and target Cores. For example, you own the Cores and do not need to send a request or get approval to establish replication.

The machine should have the status of Pairing in the State column, or a status of Validated on the Events page.

3.
Click the Review icon.

The Establish Replication dialog box opens.

4.
Under Choose the protected machine(s) whose backups you want to replicate to, and on which repository each Agent should be stored, do one of the following:
Select Replace an existing replicated Core on, and then select an existing target core from the drop-down list.
Select Create a new replicated Core on, and then enter the name of the new target core.
6.
Click Start Replication.
On the Establish Replication page, the State column for the selected Core machine displays the status of Pending. When replication is established, the status changes to Established.

Viewing pending replication requests in the Rapid Recovery Add-on for Kaseya

If you have protected machines for which others can send replication requests, this page lets you get and view the requests that have been submitted for those protected machines. The list of protected machines includes the following information:

Machine. The name of the machine that has the Core installed.
Credentials. The user name associated with that machine.
Source Core. The Core that protects the machines that have the Agent installed.
Target Core. The Core to whose repository the request wants to send replicated data.
Machine. The means by which you can select a machine.
Customer Id. The identification number for the customer who made the replication request.
Email Address. The contact information for the customer who requested replication to this core.
Core Name. The name of the source core from which the customer wants to replicate.
Status. The state of replication between the cores (for example, Pending or Approved.)

You can then review those requests and accept or deny them as appropriate. If you accept, replication is established and recovery points are sent from the source to the target cores.

3.
To refresh the list, click Update Status, and then click Yes in the dialog box to confirm.

The Pending Request dialog box opens.

d.
Click Send Response to establish replication.

On the Pending Requests page, the Status column updates to display the status as either Approved or Denied as appropriate.

Related Documents