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

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.
  2. From the icon bar, click [Replication] (Replication).
    The Replication page appears.
  3. On the Replication page, click Request (#).

    The Pending Replication Requests section appears.

  4. Under Pending Replication Requests, click the drop-down menu next to the request you want to ignore, and then click Ignore.
  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.


Was this topic helpful?

[Select Rating]



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 Understanding replication and Replicating 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 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.
  4. 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, an eSATA, USB 3.0, or other high-speed connection to the portable storage device is recommended.
    1. On the Protected Machines page of the Replication Wizard, select Use a seed drive to perform initial transfer.
      • If you currently have one or more protected machines replicating to a target Core, you can include these machines on the seed drive by selecting the option Include already replicated recovery points in the seed drive.
    2. Click Next.
    3. On the Seed Drive Location page of the wizard, use the Location type drop-down list to select from the following destination types:
      • Local
      • Network
      • Cloud
    4. Enter the details for the archive as described in the following table based on the location type you selected in Step c.
      Table 1. 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.
      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 wizard, enter the information as described in the following table.
      Table 2. 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).
      • Select the blank 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.
      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 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.
    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 5.
    8. 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.

Was this topic helpful?

[Select Rating]



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.

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

Was this topic helpful?

[Select Rating]



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 downward-facing 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. Click [Actions] to open the drop-down menu for the seed drive file you want to abandon, 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.


Was this topic helpful?

[Select Rating]



Related Documents