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

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.
  2. From the icon button bar, click [Replication] Replicate.
    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 1. 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.

    • If the Core you want to add has been paired with this source core previously, you can do the following:
      1. Select Use an existing target core.
      2. Select the target core from the drop-down list.
      3. Click Next.
      4. Skip to Step 7.
  4. Click Next.
  5. On the Request page of the Replication Wizard, enter the information as described in the following table.
    Table 2. 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.
  8. If you want to perform the seeding process for the transfer of 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 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 archive as described in the following table, based on the location type you selected in Step c.
      Table 3. 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.
      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 4. 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 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.
    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 9.
    8. 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.
  10. If you created a seed drive, send it as directed by your third-party service provider.

Was this topic helpful?

[Select Rating]



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:


Was this topic helpful?

[Select Rating]



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.
  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 review, and then click Review.

    The Review Replication Request window appears.

    Note: The information that appears in the Source Core Identity section of this window is determined by the request completed by the customer.
  5. Under Source Core Identity, do one of the following:
    • 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.
  6. Under Agents, select the machines to which the approval applies, and then use the drop-down lists in the Repository column to select the appropriate repository for each machine.
  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.


Was this topic helpful?

[Select Rating]



Denying a replication request

Complete the steps in the following procedure to deny a replication request sent to a third-party core from a customer.

To deny a request without reviewing it, see Ignoring 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 review, and then click Review.

    The Review Replication Request window appears.

  5. Click Deny.

    Replication is denied. Notification of denial appears under Alerts on the Events page of the source Core.


Was this topic helpful?

[Select Rating]



Related Documents