Quest has been named as an ASP "Ten Best Web Support Sites" award winner. Learn more.

Rapid Recovery 6.0.2 - User Guide

*** Legend Introduction to Dell Data Protection | Rapid Recovery Understanding the Rapid Recovery Core Console Working with repositories Managing Rapid Recovery Core settings Using custom groups Working with encryption keys Protecting machines using the Rapid Recovery Core Working with Microsoft Exchange and SQL Servers Protecting server clusters Exporting protected data to virtual machines Managing protected machines Understanding replication Managing events Generating and viewing reports Restoring data Understanding bare metal restore for Windows machines Retention and archiving Managing cloud accounts Working with Linux machines Understanding the Local Mount Utility Central Management Console Understanding the Rapid Recovery Command Line Management utility Understanding the Rapid Recovery PowerShell module
Prerequisites for using PowerShell Working with commands and cmdlets Rapid Recovery PowerShell module cmdlets Localization Qualifiers
Extending Rapid Recovery jobs using scripting Rapid Recovery APIs Glossary

Viewing incoming and outgoing replication

If you click the Replication [Replication] icon from the icon bar, the Replication page appears. This page gives you an understanding of replication from the scope of this Core. It includes two panes:

  • The Outgoing Replication pane lists any machines protected in this Core that are replicated on another Core.
  • The Incoming Replication pane lists the machines replicated on this Core, and the source Core from which these machines are replicated.

This section describes the information shown in these panes.

Information about outgoing replication from this Rapid Recovery Core is described in the following table.

Table 1. Information about outgoing replication
UI Element Description
Select item For each row in the summary table, you can select the checkbox to perform actions from the list of menu options above the table.
Type Shows the machine type. You can expand a target Core to show individual replicated machines.
Status indicator Status of replication. Colored circles in the Status column show whether a replicated machine is online or unreachable. If you hover the cursor over the colored circle, the status condition is displayed. Status conditions include green (replication established and online), yellow (replication paused), red (authentication error), and gray (offline or unreachable).
Replication Name The display name of the Core machine to which machines from this source Core are replicated.
Machines Lists the number of machines replicated to the selected target Core.
Sync The date and time of the last replication transfer to the target Core.
[Actions] When you click the actions drop-down menu in this column, you see a list of actions to perform to affect the specific replication relationship. These options include:
  • Details
  • Change Settings
  • Schedule
  • Add Machines
  • Delete

You can perform actions on two or more of the target Cores listed in the Outgoing Replication grid. To perform actions on multiple target Cores, select the checkbox for each Core in the grid, and then, from the menu above the grid, select the action you want to perform. You can perform the actions described in the following table.

Table 2. Global actions available in the Outgoing Replication pane
UI Element Description
Add Target Core Lets you define another target Core to replicate machines protected on this source Core.
Refresh Refreshes the information shown in the table.
Force Forces replication.
Pause Pauses established replication.
Resume Resumes paused replication.
Copy Opens the replication wizard, letting you copy existing recovery points for selected protected machines to a seed drive.
Delete Deletes outgoing replication.
Seed Drives

This menu option appears if data was copied to a seed drive when replication was set up.

Displays information about the seed drive file, including the data and time the seed drive was saved. Collapsible menus indicate the target Core and the protected machines from which the seed drive files were generated.

[Actions] When you click the actions drop-down menu in this column, you see a list of actions to perform to affect the specific replication relationship. These options include:
  • Cache lifetime (seconds)
  • Volume image session timeout (minutes)
  • Maximum parallel streams
  • Maximum transfer speed (MB/s)
  • Maximum transfer data size (GB)

Information about incoming replication from another Core is described in the following table.

Table 3. Information about incoming replication
UI Element Description
Select item For each row in the summary table, you can select the checkbox to perform actions from the list of menu options above the table.
Type Shows the machine type. You can expand a source Core to show individual replicated machines.
Status indicator Status of replication. Colored circles in the Status column show whether a replicated machine is online or unreachable. If you hover the cursor over the colored circle, the status condition is displayed. Status conditions include green (replication established and online), yellow (replication paused), red (authentication error), and gray (offline or unreachable).
Replication Name The display name of the source Core machine containing protected machines that are replicated on this target Core.

This name can be optionally specified when establishing replication on the source Core using the Replication Wizard.

Machines Lists the number of machines protected on the source Core that are replicated to this target Core.
Sync The date and time of the last replication transfer from the source Core.
[Actions] When you click the actions drop-down menu in this column, you see a list of actions to perform to affect the specific replication relationship. These options include:
  • Details
  • Consume
  • Fail Over
  • Delete

You can perform actions on two or more of the source Cores listed in the Incoming Replication grid. To perform actions on multiple source Cores, select the checkbox for each Core in the grid, and then, from the menu above the grid, select the action you want to perform. You can perform the actions described in the following table.

Table 4. Global actions available in the Incoming Replication pane
UI Element Description
Refresh Refreshes the information shown in the table.
Force Forces replication.
Pause Pauses established replication.
Resume Resumes paused replication.
Delete Deletes incoming replication.

Was this topic helpful?

[Select Rating]



Configuring replication

To replicate data using Rapid Recovery, you must configure the source and target cores for replication. After you configure replication, you can then replicate protected machine data, monitor and manage replication, and perform recovery.

Performing replication in Rapid Recovery involves performing the following operations:


Was this topic helpful?

[Select Rating]



Replicating to a self-managed target Core

This configuration applies to replication to an off-site location and to mutual replication. The following steps are prerequisite:
  • The Rapid Recovery Core must be installed on all source and target machines.
  • If you are configuring Rapid Recovery for multi-point to point replication, you must perform this task on all source Cores and the one target Core. For descriptions of these replication configurations, see Understanding replication .
  • If you need to create a seed drive and transfer it to a physical removable storage volume to perform the initial transfer of existing recovery points, you must have a suitable portable storage device prepared. You must also have physical access to the source Core machine, to attach the drive to copy the seed drive archive.
  • If using a seed drive in a self-managed target Core, you or a trusted administrator must have physical access to the target Core.

A self-managed target Core is a Core to which you have access. For example, a self-managed Core is often managed by your company at an off-site location, or is hosted at a different geographic location than the source Core. Replication can be set up entirely on the source Core, unless you choose to seed your data using a seed drive. In such cases, you must create a seed drive using this procedure, and later attach the seed drive to the target Core to consume the archived recovery point data. For more information, see Determining your seeding needs and strategy.

Complete the steps in the following procedure to configure your source Core to replicate to a self-managed target Core.

  1. Navigate to the Rapid Recovery Core console of the source Core.
  2. On the button bar, click [Replication] Replicate.

    The Replication Wizard appears.

  3. On the Target Core page of the Replication Wizard, if you are establishing replication with a target Core that has been paired with this source Core previously, select Use an existing target Core, and then select the appropriate target Core from the drop-down list. Skip to step 5.
  4. On the Target Core page of the Replication Wizard, if you are establishing replication with a target Core from this source Core for the first time, select I have my own Target Core, and then enter the information as described in the following table.
    Table 1. Target Core information
    Text Box Description
    Host Name Enter the host name or IP address of the Core machine to which you are replicating.
    Port Enter the port number on which the Rapid Recovery Core will communicate with the machine.

    The default port number is 8006.

    User Name Enter the user name for accessing the machine.
    Password Enter the password for accessing the machine.
  5. Click Next.
    Note: If no repository exists on the target core, a warning appears notifying you that you can pair the source core with the target Core, but that you are unable to replicate agents (protected machines) to this location until a repository is established. For information about how to set up a repository to a Core, see Creating a DVM repository.
  6. On the Request page, enter a name for this replication configuration; for example, SourceCore1. This is the display name used for the Incoming Replication pane on the target Core's Replication page.
  7. Click Next.
  8. 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.
  9. If you want to perform the seeding process for the transfer of the base data, complete the following steps:
    Note: Because large amounts of data need to be copied to the portable storage device, Dell recommends using an eSATA, USB 3.0, or other high-speed connection to the portable storage device.
    1. On the Protected Machines page of the Replication Wizard, select Use a seed drive to perform the initial transfer.
      • If you currently have one or more protected machines replicating to a target Core, you can include these protected machines on the seed drive by selecting Include already replicated recovery points in the seed drive.
    2. Click Next.
    3. On the Seed Drive Location page of the Replication Wizard, use the Location type drop-down list to select from the following destination types:
      • Local
      • Network
      • Cloud
    4. Enter the details for the seed drive file as described in the following table, based on the location type you selected in Step c.
      Table 2. 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 seed drive 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.
      Note: To select a cloud account, you must first have added it in the Core Console. For more information, see Adding a cloud account.
      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]
    5. Click Next.
    6. On the Seed Drive Options page of the Replication Wizard, enter the information as described in the following table.
      Table 3. Seed drive options
      Item Description
      Maximum Size Large archives of data can be divided into multiple segments. Select the maximum size of the segment 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 future use. For example, if the location is D:\work\archive, all of the available space on the D: drive is reserved if required for copying the seed drive, but is not reserved immediately after starting the copying process.
      • Select the text box, enter an amount, and then select a unit of measurement from the drop-down list to customize the maximum space you want to reserve. The default is 250MB.
      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 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 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.
    7. Do one of the following:
      • 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 10.
    8. On the Protected Machines page of the Replication Wizard, select the protected machines you want to replicate to the target Core using the seed drive.
  10. Click Finish.
  11. If you created a seed drive, send it to your target Core.

    The pairing of the source Core to the target Core is complete.

Unless you selected the option to initially pause replication, the replication process begins immediately.

  1. If you selected the option to use a seed drive, replication produces orphaned recovery points on the target Core until the seed drive is consumed and provides the necessary base images.
  2. If you specified the use of the a drive, transfer the seed drive archive file to a volume (shared folder, virtual disk, or removable storage media). Then, consume the seed drive.

Was this topic helpful?

[Select Rating]



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:


Was this topic helpful?

[Select Rating]



Related Documents