Chat now with support
Chat with Support

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

Changing the vSphere settings for a VMware protected virtual machine

This procedure applies to VMware ESXi or Workstation virtual machines (VMs) that are protected using Rapid Recovery Rapid Snap for Virtual (agentless protection).
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.
  1. On the Rapid Recovery Core Console, under Protected Machines in the left navigation area, click the display name of the Hyper-V host you want to change.
    The Summary page for the host opens.
  2. On the menu bar for the host, click Settings.
    The Settings page opens.
  3. In the list on the left side, click vSphere.

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

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

  5. Enter the configuration information as described in the following table.
    Table 70: vSphere settings information
    Text Box Description
    Allow Rapid Recovery to delete user created in 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.

Understanding Active Block Mapping

Active Block Mapping (ABM) is a patent-pending technology that filters out inactive blocks of data from managed images, thereby letting Rapid Recovery protect only the active blocks, which optimizes function and performance. This feature is only available for agentless (Rapid Snap for Virtual) protection of ESXi or vCenter virtual machines (VMs) and Hyper-V servers and clusters.

ABM delivers a query to the file system header of a volume. The query returns a list of active blocks within the image. For this reason, ABM only works with NTFS file systems. When protecting ESXi and vCenter VMs, ABM can be combined with Changed Block Tracking (CBT), to read only active and changed blocks when taking incremental or differential snapshots.

When configuring agentless protection of a VM with the Protect Multiple Machines wizard, you have the option to enable ABM. If you opt to automatically protect new VMs added to the specified host, then the ABM rule also applies to any new VMs subsequently added to protection on the host.

You can change your ABM choice at any time in the Settings page for the host or VM. For more information, see Changing ABM settings.

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 71: 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.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating