Chat now with support
Chat with Support

Welcome, ApexSQL customers to Quest Support Portal click here for for frequently asked questions regarding servicing your supported assets.

Rapid Recovery 6.3 - User Guide

Introduction to Rapid Recovery The Core Console Repositories Core settings 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 Credentials Vault Snapshots and recovery points Replication Events Reporting VM export Restoring data Bare metal restore
About bare metal restore BMR Windows and Linux Understanding boot CD creation for Windows machines Managing a Linux boot image Performing a bare metal restore using the Restore Machine Wizard 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 Core Console references REST APIs Glossary

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.

This procedure is only necessary if a seed drive file was created as part of Replicating to a self-managed target Core or Replicating to a third-party target Core.

  1. If the seed drive file was saved to a portable storage device, such as a USB drive, connect the drive to the target Core.

    NOTE: If the seed data is comprised of multiple segments, all segments must be available in the location type you specify in step 4. For example, all segments should be attached to the local target Core server, in the same network directory, or in the same cloud account container.

  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:
    • Local
    • Network
    • Cloud
  5. Enter the details for the seed drive archive file, as described in the following table based on the location type you selected in step 4.
    Table 95: 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.

    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 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 dialog box, 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.
  9. To monitor the progress of consuming data, view the [Events]
    Events page.

Abandoning a seed drive

If you create a seed drive with the intent of consuming it on the target Core, but later choose not to consume it, you can abandon the seed drive.

Until you abandon the seed drive or consume it, a link for the outstanding seed drive remains on the Outgoing Replication pane on the source Core.

Until you transmit information from the seed drive, orphaned recovery points (which exist on the original protected machine, but not the target Core) cannot be used to restore data.

Caution: If you abandon the seed drive, then the original recovery points (defined in the seed drive file) are then transmitted over the network to the target Core during the next replication job. Transmitting old recovery points over the network could slow down the network considerably, especially if there are many recovery points.

Complete the steps in the following procedure to abandon an outstanding seed drive.

NOTE: Abandoning the seed drive in the Core Console does not affect the seed drive file from its storage location.

  1. On the source Core, open the Rapid Recovery Core Console, and from the icon bar, click [Replication]
    (Replication).
    The Replication page appears.
  2. On the Replication page, in the Outgoing Replication pane, click Seed Drives (#).
    In the Outgoing Replication pane, a section appears containing information about the outstanding seed drives.
  3. Optionally, click the arrow [Expand]
    to expand the collapsible menu.
    Information appears about outstanding seed drives, including the target Core and the date range of the recovery points included in the seed drive.
  4. For the seed drive file you want to abandon, click [Actions]
    (More options) and then select Abandon.
  5. In the confirmation window, confirm that you want to abandon the seed drive.

    The seed drive is removed.

    If no more seed drives exist on the source Core, the Seed Drives (#) link and outstanding seed drives section are removed from the Outgoing Replication pane.

Managing replication settings

Rapid Recovery Core lets you monitor, schedule, and adjust replication at the overall, Core, and protected machine levels.

You can edit the following replication settings:

Scheduling replication

Unless you change the default behavior by setting a replication schedule, the Core starts a replication job immediately after completion of every backup snapshot, checksum check, attachability check, and the nightly jobs.

You can change the replication schedule to reduce the load on the network.

Complete the steps in the following procedure to set a replication schedule for any replicated machine.

  1. On the target Core, open the Rapid Recovery Core Console, and from the icon bar, click [Replication (Replication).
    The Replication page appears.
  2. In the Outgoing Replication pane, on the Core for which you want schedule replication, click [Actions] (More options) and then select Schedule.

    The Replication Schedule for [CoreName] dialog box opens.

  3. Select from one of the following options:
    • At All Times. Replicates after every new snapshot, checksum check, and attachability check, and after the nightly jobs complete.
    • Daily (Start replication only during the specified time period). Begins replicating only within the time range provided.
      1. In the From text box, enter the earliest time at which replication should begin.
      2. In the To text box, enter the latest time at which replication should begin.

        NOTE: If replication is in progress when the scheduled time ends, the replication job completes after the allotted time period.

    • Custom. Begins replicating only within the time range provided, letting you set one time range for weekdays and another time range for weekends.
      1. Next to Weekdays, in the From text box, enter the earliest time at which replication should occur on a weekday; and then in the To text box, enter the latest time at which replication should occur on a weekday.
      2. Next to Weekends, in the From text box, enter the earliest time at which replication should occur on weekends; and then in the To text box, enter the latest time at which replication should occur on weekends.
  4. Click Save.

    The schedule is applied to all replication to the selected target Core.

Related Documents