Chat now with support
Chat with Support

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

Changing ABM settings

To change the Active Block Mapping (ABM) settings for a supported hypervisor host or virtual machine (VM), complete the following steps.

NOTE: For more information, see Understanding Active Block Mapping.

  1. From the Core Console, in the left navigation area, click the host or VM for which you want to change the ABM settings.
  2. From the Summary page of the machine, click Settings.
  3. From the list of machine settings on the left side of the Settings page, click ABM Settings.
  4. Do one of the following:
    1. If changing ABM settings for an agentlessly protected ESXi or Hyper-V virtual machine, proceed to step 5.
    2. If changing ABM settings for a supported hypervisor host, skip to step 6.
  5. If you are on the Settings page of a VM, select whether to use the settings from the host (the default option) or to use the settings for this machine.
    • If you want this VM to use the same ABM settings as the host, select Use the settings of the Hyper-V host. If you made any changes, click Apply. This procedure is complete.
    • If you want this VM to use different ABM settings than the host, select Use the settings of this protected machine, click Apply, and then continue to the next step.
  6. Review the ABM settings and change them if desired. For each of the following options, click the current setting, select (or clear) the selection, and then click [Apply changes] to accept the change or click [Cancel] 
    to cancel.
    Table 72: Active Block Mapping settings
    Option Description
    Enable Active Block Mapping Lets you enable or disable the ABM feature.

    Enable swap file blocks exclusion

    Excludes the content of system files, such as pagefile.sys, hyberfill.sys, and swapfile.sys, from the backup.

    Exclude subdirectories

    Lets you exclude specific files by specifying '<file name>' or '<folder>\<subfolder>\<file name>'.

    Only the files will be excluded. The folders or subfolders that contained excluded files are included in the mount point, with no contents.

    NOTE: This option may affect the performance of the "determining data" phase of transfers.

    + Add

    If you opted to exclude subdirectories, click Add and enter the location in the Path table for each item you want to exclude.

About modifying transfer settings

In Rapid Recovery, you can modify the settings to manage the data transfer processes for a protected machine. The transfer settings described in this section are set at the protected machine level. To affect transfer at the Core level, see Modifying transfer queue settings.

There are three types of transfers in Rapid Recovery:

  • Snapshot. Backs up the data on your protected machine. Two types of snapshots are possible: a base image of all protected data, and an incremental snapshot for data updated since the last snapshot. This type of transfer creates recovery points, which are stored on the repository associated with the Core. For more information, see Managing snapshots and recovery points.
  • Virtual Machine Export. Creates a virtual machine (VM) from a recovery point, containing all of the data from the backup of the protected machine, as well the operating system and drivers and associated data to ensure the VM is bootable. For more information, see VM export.
  • Restore. Restores backup information to a protected machine. For more information, see About restoring volumes from a recovery point.

    NOTE: The entire volume is always rewritten during restore of Windows systems using EFI system partitions.

Data transfer in Rapid Recovery involves the transmission of a volume of data along a network from protected machines to the Core. In the case of replication, transfer also occurs from the originating or source Core to the target Core.

Data transfer can be optimized for your system through certain performance option settings. These settings control data bandwidth usage during the process of backing up protected machines, performing VM export, or performing a restore. These are some factors that affect data transfer performance:

  • Number of concurrent agent data transfers
  • Number of concurrent data streams
  • Amount of data change on disk
  • Available network bandwidth
  • Repository disk subsystem performance
  • Amount of memory available for data buffering

You can adjust the performance options to best support your business needs and fine-tune the performance based on your environment. For more information, see Throttling transfer speed.

Throttling transfer speed

When transferring backup data or replicated recovery points between protected machines and Cores over the network, you can intentionally reduce the speed of the transfer. This process is known as throttling.

When you throttle the transfer speed, you limit the amount of your network bandwidth dedicated to file transfers from Rapid Recovery. When setting up replication, for example, throttling can reduce the likelihood that the transfer of prior recovery points to the replicated Core consumes all of your network bandwidth.

Caution: Throttling transfer speed is not always required or recommended. This information is provided to provide insight into a potential solution for performance issues in your Rapid Recovery environment. For example, sometimes, throttling may solve issues related to repeated transfer failures or network slowdowns caused by transferring a substantial amount of data for your protected or replicated Cores.

There are several factors involved in determining the best approach to throttling. The type of machine being protected is a key factor. For example, a busy Microsoft Exchange server has a much higher change rate than a seldom-used legacy web server.

The input and output capabilities of the storage volumes on your protected machines can also contribute to more or less efficiency.

The speed of your network is another critical factor, with many variables. The network backbone in place (for example, 1GbE versus 10GbE), architecture, configuration, intentional use of NIC teaming, and even the type of cables used can all affect network transfer speed. If your environment has a slower wide area network, and if transfer jobs fail for backup or replication, consider throttling the transfer speed using some of these settings.

Ultimately, the process of network throttling involves trial and error. Quest recommends that you adjust and test your transfer settings, and revisit these settings periodically to ensure that your settings continue to meet your needs.

Adjusting transfer speed should be accomplished on an individual machine basis. In the Core Console, navigate to a specific machine, select Settings, and adjust the Transfer speed. For specific information about viewing and changing these settings, see Viewing and modifying protected machine settings.

That topic also includes descriptions of each of the settings used for throttling transfer. Those descriptions may be useful in determining which settings you should experiment with first.

The four main settings involved in throttling transfer speed are described in the following table:

Table 73: Transfer speed settings
Machine-Level Setting Default Setting Suggested Throttle Setting
Maximum Concurrent Streams 8 4
Maximum Concurrent Writes 8 4
Maximum Segment Size 4194304 2097152
Outstanding Reads per Stream 0 Start at 24

Quest recommends adjusting and testing the other settings prior to changing the default setting for outstanding reads per stream, unless directed otherwise by a Quest Support representative. When tuning and testing this setting, start with a value of 24.

When you specify limitations to protected machine transfer parameters, these limitations apply per job. If two transfer jobs occur simultaneously or overlap, twice the bandwidth is used. If four transfer jobs across the network overlap, four times the bandwidth is used; and so on.

Customizing nightly jobs for a protected machine

Nightly jobs can be configured at the Core level or at the machine level. When nightly jobs are set at the Core level, the changes are applied to all relevant machines protected by that Core. Changes made to the nightly jobs at the machine level supersede the changes made at the Core level, and apply only to the machines specified.

For a list of all nightly jobs, including descriptions and the scope available for each, see the topic Understanding nightly jobs.

Complete the steps in the following procedure to make changes to the nightly jobs for a single protected machine.

  1. In the Rapid Recovery Core Console, under the Machines menu, click the IP address or machine name for the machine for which you want to customize nightly jobs.
    The Summary page for the selected machine appears.
  2. Click the Settings menu.

    The Settings page appears, showing configuration settings for the selected machine.

  3. Optionally, click the Nightly Jobs link to scroll down in the Settings page to view nightly jobs settings.
  4. Under the Nightly Jobs heading, click [Change] 

    The Nightly Jobs dialog box appears.

  5. In the Nightly Jobs dialog box, select the jobs you want to include to run nightly, or clear the options you want to omit for this machine.

    NOTE: Options may vary by machine. For example, a protected machine using Exchange Server may include Check checksum of Exchange databases and Truncate Exchange logs.


    NOTE: For information about the Rollup setting, including setting a custom retention policy, see Customizing retention policy settings for a protected machine.

  6. Click OK.

    NOTE: The results of this procedure apply only to the selected protected machine. To apply elsewhere, repeat the procedure for each machine you want to customize. To change the nightly job settings for all machines protected by a Core, see Configuring nightly jobs for the Core.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating