Chat now with support
Chat with Support

Rapid Recovery 6.1.3 - User Guide

Introduction to Rapid Recovery Core Console Core settings Repositories Encryption keys Protecting machines
About protecting machines with Rapid Recovery Support for dynamic and basic volumes 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 Settings and functions for protected Exchange servers Settings and functions for protected SQL servers
Managing protected machines Snapshots and recovery points Replication Events Reporting VM export Restoring data Bare metal restore
Bare metal restore for Windows machines Understanding boot CD creation for Windows machines Using the Universal Recovery Console for a BMR Performing a bare metal restore for Linux machines Viewing the recovery progress Starting a restored target server Troubleshooting connections to the Universal Recovery Console Repairing boot problems Performing a file system check on the restored volume
Managing aging data Archiving Cloud storage accounts The Local Mount Utility The Central Management Console Core Console references Command Line Management utility PowerShell module
Prerequisites for using PowerShell Working with commands and cmdlets Rapid Recovery PowerShell module cmdlets Localization Qualifiers
Scripting REST APIs About us Glossary

Changing the settings for a Hyper-V protected virtual machine

This procedure applies to Hyper-V virtual machines (VMs) that are protected using Rapid Recovery Rapid Snap for Virtual (agentless protection).

A Hyper-V VM that is being protected by Rapid Snap for Virtual (agentless protection) is indicated in the left navigation area by the host icon . The settings for a Hyper-V agentless VM the same as a typical protected machine with the exception of the Hyper-V section at the bottom of the Settings page. The following task provides instructions for only the Hyper-V section settings. For all other protected machine settings, see Viewing and modifying protected machine settings.

On the Core Console, in the left navigation area under Protected Machines, click the Hyper-V VM whose settings you want to change.
The Summary page for the VM opens.
The Settings page opens.

The setting you selected becomes editable, as a text field or a drop-down menu.

Under Hyper-V, click Snapshot configuration.

The setting you selected becomes editable a drop-down menu.

Table 89. Hyper-V settings information

Text Box


Try to create VSS snapshot during transfer first, if it fails, create a checkpoint

If the VSS snapshot succeeds, the recovery point will be in an application-consistent state. If the VSS snapshot fails and a checkpoint is created, the recovery point will be in a crash-consistent state.

Do not create VSS snapshot during transfer

Generates a recovery point in a crash-consistent state.

Use only VSS snapshots during transfers. If VSS snapshot creation fails, the entire transfer will fail

Generates only application-consistent recovery points. If the VSS snapshot fails, no recovery point is generated.

Changing the vSphere settings for a VMware protected virtual machine

The settings for a VMware VM that is protected agentlessly include the same settings that are used for a typical protected machine, with one exception. The vSphere section of the Settings page includes settings that apply only to agentlessly protected VMware VMs. The following task provides instructions for only the vSphere section of the Settings page. For all other protected machine settings, see Viewing and modifying protected machine settings.

The Summary page for the host opens.
The Settings page opens.

The setting you selected becomes editable, as a text field or a drop-down menu.

Under vSphere, click the setting that you want to change.

The setting you selected becomes editable, as a text field or a drop-down menu.

Table 90. vSphere settings information

Text Box


Allow Rapid Recovery to delete user created VMware

The default setting is No.

Allow transfer for volumes with invalid used capacity

The default setting is Yes.

Allow quiesced snapshots

The default setting is Yes.

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.

Rapid Recovery supports Windows 8 and Windows Server 2012 for normal transfers, both base and incremental, as well as with restore, bare metal restore, and virtual machine export.

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.

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:

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 provided 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 91. Protected machine settings used to throttle transfer speed

Machine-Level Setting

Default Setting

Suggested Throttling Setting

Maximum Concurrent Streams



Maximum Concurrent Writes



Maximum Segment Size



Outstanding Reads per Stream


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.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating