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

Adjusting client timeout settings

Client timeout settings control the length of time that various operations are attempted before the operation times out.

Note: Dell recommends leaving default timeout settings unless you experience specific issues in your environment, and you are advised by a Dell Support representative to modify the settings.

Complete the steps in this procedure to adjust client timeout 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 Client Timeout.
    • Scroll down on the right side of the Settings page until you can see the Client Timeout heading.

      The Client Timeout core settings appear.

  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.

  5. Table 1. Client timeout settings information
    Setting Description
    Connection Timeout Controls the timeout for the connection between the Core and protected machines when sending data across the hypertext transfer protocol (http).

    Enter the amount of time you want to lapse before a connection timeout occurs. Uses HH:MM:SS format.

    Note: The default setting is 0:05:00 or five minutes.
    Read/Write Timeout Controls the timeout for the connection between the Core and protected machines when reading or writing stream data across http. An example is receiving changed data blocks from a protected machine to the Core for an incremental snapshot.

    Enter the amount of time you want to lapse before a timeout occurs during a read/write event. Uses HH:MM:SS format.

    Note: The default setting is 0:05:00 or five minutes.
    Connection UI Timeout Controls the timeout for the connection between the graphic user interface and the Rapid Recovery Core service across http.

    Enter the amount of time you want to lapse before a connection UI timeout occurs. Uses HH:MM:SS format.

    Note: The default setting is 0:05:00 or five minutes.
    Read/Write UI Timeout Controls the timeout for the connection for reading and writing data streams between the graphic user interface and the Rapid Recovery Core service across http.

    Enter the amount of time you want to lapse before a timeout occurs during read or write events. Uses HH:MM:SS format.

    Note: The default setting is 0:05:00 or five minutes.
  6. For each setting, when satisfied with your changes, click [Check mark] to save the change and exit edit mode, or click [Cancel] to exit edit mode without saving.

Was this topic helpful?

[Select Rating]



Understanding deduplication cache and storage locations

Global deduplication reduces the amount of disk storage space required for data your Core backs up. Each repository is deduplicated, storing each unique block once physically on disk, and using virtual references or pointers to those blocks in subsequent backups. To identify duplicate blocks, Rapid Recovery includes a deduplication cache for deduplication volume manager (DVM) repositories. The cache holds references to unique blocks.

By default, for DVM repositories, this deduplication cache is 1.5GB. This size is sufficient for many repositories. Until this cache is exceeded, your data is deduplicated across the repository. Once the amount of redundant information is so great that the deduplication cache is full, your repository can no longer take full advantage of further deduplication for newly added data. The amount of data saved in your repository before the deduplication cache fills varies by the type of data being backed up, and is different for every user.

You can increase the size of the DVM deduplication cache by changing the deduplication cache setting in the Rapid Recovery Core. For more information on how to increase the cache size, see the topic Configuring DVM deduplication cache settings.

When you increase the DVM deduplication cache size, there are two factors to consider: disk space and RAM usage.

Disk space. Two copies of the DVM deduplication cache are stored on disk: a primary cache, and a secondary cache which is a parallel copy. Thus, if using the default cache size of 1.5GB for a DVM repository, 3GB of disk storage is used in your system. As you increase the cache size, the amount of disk space used remains proportionally twice the size of the cache. To ensure proper and fault-resistant performance, the Core dynamically changes the priority of these caches. Both are required, the only difference being that the cache designated as primary is saved first.

RAM usage. When the Rapid Recovery Core starts, it loads the deduplication cache to RAM. The size of the cache therefore affects memory usage for your system. The total amount of RAM the Core uses depends on many factors. These factors include which operations are running, the number of users, the number of protected machines, and the size of the deduplication cache. Each operation the Core performs (transfer, replication, rollup, and so on) consumes more RAM. Once an operation is finished, memory consumption decreases accordingly. However, administrators should consider the highest RAM load requirement for efficient operations.

Default settings for the Rapid Recovery Core place the primary cache, secondary cache, and the metadata cache for DVM repositories in the AppRecovery directory. This folder is installed on the Core machine.

Note: Depending on your settings, the AppRecovery directory may not be visible on the Rapid Recovery Core. To see this directory, you may need to change the Folder Options control panel to show hidden files, folders, and drives.

Assuming the Rapid Recovery Core is installed on the C drive, these locations are typically as follows:

Table 1. Default storage locations for DVM deduplication cache settings
Setting Default Storage Location
Primary Cache Location C:\ProgramData\AppRecovery\RepositoryMetaData\PrimaryCache
Secondary Cache Location C:\ProgramData\AppRecovery\RepositoryMetaData\SecondaryCache
Metadata Cache Location C:\ProgramData\AppRecovery\RepositoryMetaData\CacheMetadata

You can change the storage location of these caches. For example, for increased fault tolerance, you can change location of your secondary cache to a different physical drive than the primary cache, assuming the Rapid Recovery Core has access to the location.

For more information on how to change storage locations for any of these settings, see the topic Configuring DVM deduplication cache settings.

Dell recommends that you plan for deduplication storage separately. Deduplication only occurs in a single repository (not across multiple repositories). If using Core-based encryption, deduplication is further limited to the data protected by a single key, since for security purposes each key serves a single encryption domain.

For more information about deduplication, see Deduplication in Rapid Recovery.


Was this topic helpful?

[Select Rating]



Configuring DVM deduplication cache settings

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. This setting only appears if your Core has one or more DVM repositories.
    • Scroll down on the right side of the Settings page until you can see the DVM Deduplication Cache heading.

      The DVM Deduplication Cache core settings appear.

  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.

      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 1. 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 text box, enter a new amount (in GB).

    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 [Check mark] to save the change and exit edit mode, or click [Cancel] to exit edit mode without saving.

Was this topic helpful?

[Select Rating]



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, Dell recommends using default settings. In some cases, you may be directed by Dell 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.

      The Replay Engine core settings appear.

  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 1. 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.

    Preferable 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 Async 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 Dell Rapid Recovery support for guidance in doing so.
  5. For each setting, when satisfied with your changes, click [Check mark] to save the change and exit edit mode, or click [Cancel] to exit edit mode without saving.

Was this topic helpful?

[Select Rating]



Related Documents