Chatta subito con l'assistenza
Chat con il supporto

Rapid Recovery 6.6 - User Guide

Introduction to Rapid Recovery The Core Console Repositories Core settings 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 Snapshots and recovery points Managing privacy Encryption Credentials Vault Replication Events Reporting VM export Restoring data Bare metal restore
About bare metal restore Differences in bare metal restore for Windows and Linux machines 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

Configuring DVM deduplication cache settings

For conceptual information about deduplication, see Deduplication in Rapid Recovery. For recommendations about settings to use, see Understanding deduplication cache and storage locations.

Complete the steps in this procedure to configure deduplication cache settings for DVM repositories.

  1. Navigate to the Rapid Recovery Core Console.
  2. On the icon bar, click [Settings] (Settings), and then do one of the following:
    • From the list of Core settings on the left side of the Settings page, click DVM Deduplication Cache.
    • Scroll down on the right side of the Settings page until you can see the DVM Deduplication Cache heading.
  3. If you want to restore default DVM deduplication cache settings at any time, do the following:
    1. At the top of the deduplication cache settings area, click [Restore default] Restore Default.

      The Restore Default dialog box appears

    2. Click Yes to confirm the restore.
  4. Click the setting you want to change.

    The setting you selected becomes editable.

  5. To change individual deduplication cache settings, enter the configuration information as described in the following table.
    Table 25: DVM deduplication cache settings information
    Setting Description
    [Restore default] Restore Default This control resets DVM cache locations to system default locations, which are described for each setting.
    Primary cache location If you want to change the primary cache location for DVM repositories, then in the Primary cache location text box, type the path for a storage location accessible to the Core.

    The default location is:

    C:\ProgramData\AppRecovery\RepositoryMetaData\PrimaryCache

    Since the primary and secondary caches are the same size, collective storage for these two caches requires twice the amount of space as the amount allocated for the deduplication cache size. For example, if you specify the default amount of 1.5GB for the deduplication cache size, ensure that each of the two storage locations have at least 1.5GB. In particular, if both locations belong to the same drive (for example, the C drive), there must be at least 3.0GB of free disk space.

    Secondary cache location If you want to change the secondary cache location for DVM repositories, then in the Secondary cache location text box, type the path for a storage location accessible to the Core.

    The default location is:

    C:\ProgramData\AppRecovery\RepositoryMetaData\SecondaryCache

    Cache metadata location If you want to change the cache metadata location for DVM repositories, then in the Cache metadata location text box, type the path for a storage location accessible to the Core.

    The default location is:

    C:\ProgramData\AppRecovery\RepositoryMetaData\CacheMetadata

    Deduplication cache size (GB)

    If you want to change the deduplication cache size for DVM repositories, then in the Deduplication cache size (GB) text box, enter a new amount in gigabytes.

    NOTE: If you decrease the size of the deduplication cache, the existing contents of the cache are flushed, and the cache is recreated.

    The default location is:

    C:\ProgramData\AppRecovery\RepositoryMetaData\SecondaryCache

    The minimum cache size setting is 1.5GB. Additionally, the cache size cannot exceed 50 percent of the installed RAM.

  6. For each setting, when satisfied with your changes, click [Save] to save the change and exit edit mode, or click [Cancel] to exit edit mode without saving.

Configuring Replay engine settings

You can configure information regarding the Replay engine, which is the communication channel for Rapid Recovery. These settings determine Core settings to provide effective communication.

In general, Quest recommends using default settings. In some cases, you may be directed by Quest Data Protection Support to modify these settings to help adjust the performance specific to your network needs.

Complete the steps in this procedure to configure Replay engine settings.

  1. Navigate to the Rapid Recovery Core Console.
  2. On the icon bar, click [Settings] (Settings), and then do one of the following:
    • From the list of Core settings on the left side of the Settings page, click Replay Engine.
    • Scroll down on the right side of the Settings page until you can see the Replay Engine heading.
  3. Click on the setting you want to change.

    The setting you selected becomes editable.

  4. Enter the configuration information as described in the following table.
    Table 26: Replay engine settings information
    Text Box Description
    IP address The Core uses this IP address when performing mount and restore for a recovery point, to allow feedback between protected machines and the Сore.

    The IP address for the Replay engine automatically populates with the IP address of the Core machine. If you manually enter the server IP address, then this value is used in cases where the protected machine cannot resolve the automatically provided IP address.

    You do not need to set this value manually unless you are having issues with protected machines being able to communicate with the Core.

    Preferred port Enter a port number or accept the default setting. The default port is 8007.

    The port is used to specify the communication channel for the Replay engine.

    Port in use Represents the port that is in use for the Replay engine configuration.
    Allow port auto-assigning Click for allow for automatic TCP port assignment.
    Admin group Enter a new name for the administration group. The default name is BUILTIN\Administrators.
    Minimum asynchronous I/O length Enter a value or choose the default setting. It describes the minimum asynchronous input/output length.

    The default setting is 65536.

    Read timeout Enter a read timeout value or choose the default setting. The default setting is 00:05:00.
    Write timeout Enter a write timeout value or choose the default setting. The default setting is 00:05:00.
    Receive buffer size Enter an inbound buffer size or accept the default setting. The default setting is 8192.
    Send buffer size Enter an outbound buffer size or accept the default setting. The default setting is 8192.
    No delay It is recommended that you leave this check box unchecked as doing otherwise will impact network efficiency. If you determine that you need to modify this setting, contact Quest Data Protection Supportfor guidance in doing so.
  5. For each setting, when satisfied with your changes, click [Save] to save the change and exit edit mode, or click [Cancel] to exit edit mode without saving.

Configuring deployment settings

Rapid Recovery lets you download installers from the Rapid Recovery Core to machines you want to protect.

NOTE: You can also download Rapid Recovery software from the QorePortal.

You can configure settings related to the deployment of the Rapid Recovery Agent software from your Core to the machines you want to protect.

Complete the steps in this procedure to configure deployment settings.

  1. Navigate to the Rapid Recovery Core Console.
  2. On the icon bar, click [Settings] (Settings), and then do one of the following:
    • From the list of Core settings on the left side of the Settings page, click Deploy.
    • Scroll down on the right side of the Settings page until you can see the Deploy heading.
  3. Click on the setting you want to change.

    The setting you selected becomes editable.

  4. Enter the configuration information as described in the following table.
    Table 27: Deployment settings information
    Text Box Description
    Agent installer name The default filename is Agent-Web.exe. If you wish to change this file name for any reason, you can use this setting to specify a new name of the Core Web Installer executable file. This file streams a download of the latest version of the Rapid Recovery Core installer, which runs directly from the web and lets you pause and resume the process as needed.
    Core address Enter the address of your Core server. This typically consists of the protocol, the name of your Core server and port, and the directory where the Core files reside.

    For example, if your server is Sample, this setting is https://sample:8006/apprecovery/admin/Core.

    Failed receive timeout The amount of time deployment of the Agent software should be attempted before timing out.

    The default setting is 00:25:00 or twenty-five minutes. If you wish to change this setting, enter the length of time you want the system to attempt to deploy the Agent software before a timeout occurs during read or write events. Uses HH:MM:SS format.

    Maximum parallel installs This setting controls the maximum number of deployments of the Agent software for the Core to attempt at one time.

    The default setting is 100.

  5. For each setting, when satisfied with your changes, click [Save] to save the change and exit edit mode, or click [Cancel] to exit edit mode without saving.

Core-level tools

In addition to configuring Core settings, you can also use the Core-level tools described in the following table.

Table 28: Other Core-level tools
UI Element Description

System information

Rapid Recovery lets you view information about the Rapid Recovery Core that includes system information, local and mounted volumes, and Replay engine connections.

For more information on the information displayed on the System information page, see Understanding system information for the Core.

For more information on how to view System information, see Viewing system information for the Core.

Downloading Core log files

Information about various activities for the Rapid Recovery Core are saved to the Core log file. To diagnose possible issues, you can download and view logs for your Rapid Recovery Core. For more information on accessing and viewing the Core logs, see Accessing Core logs.

Each protected machine also saves a log of activity. This log can be uploaded to the Core if you select the nightly job called Downloading the logs from the protected machines. For more information about nightly jobs, see Understanding nightly jobs. For more information about how to configure nightly job settings for the Core, see Configuring nightly jobs for the Core. For more information about configuring nightly jobs for specific protected machines, see Customizing nightly jobs for a protected machine.

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione