This section describes how to protect, configure, and manage the protected machines in your Rapid Recovery environment.
To protect your data using Rapid Recovery, you need to add the workstations and servers for protection in the Rapid Recovery Core Console; for example, your Exchange server, SQL Server, Linux server, and so on.
You must install the Rapid Recovery Agent software on all physical or virtual machines you want to protect in the Core.
In the Rapid Recovery Core Console, using one of the Protect Machine wizards, you can identify the machines you want to protect. You can do the following:
When identifying your protection requirements for a single machine in the wizard, you can specify which volumes to protect. When you protect multiple machines, all volumes are protected by default. (You can change this later on an individual machine basis).
The wizard also lets you define a customized schedule for protection (or re-use an existing schedule).
Using advanced options, you can add additional security measures by specifying or applying an encryption key to backups for the machines you want to protect.
Finally, if one does not already exist, you can define a repository using the wizard.
After installing the Agent software, each machine must be restarted after installation.
For more information on how to protect workstations and servers, see Protecting a machine.
Rapid Recovery supports taking snapshots of all dynamic and basic volumes. Rapid Recovery also supports exporting simple dynamic volumes that are on a single physical disk. As their name implies, simple dynamic volumes are not striped, mirrored, spanned, or RAID volumes.
The behavior for virtual export of dynamic disks differs, based on whether the volume you want to export is protected by the Rapid Recovery Agent software, or is a VM using agentless protection. This is because non-simple or complex dynamic volumes have arbitrary disk geometries that cannot be fully interpreted by the Rapid Recovery Agent.
When you try to export a complex dynamic disk from a machine with the Rapid Recovery Agent software, a notification appears in the user interface to alert you that exports are limited and restricted to simple dynamic volumes. If you attempt to export anything other than a simple dynamic volume with the Rapid Recovery Agent, the export job fails.
In contrast, dynamic volumes for VMs you protect agentlessly are supported for protection, virtual export, restoring data, and BMR, and for repository storage, with some important restrictions. For example:
However, the volumes are exported at the disk level, with no volume parsing. For example, if exporting a dynamic volume spanned across two disks, the export will include two distinct disk volumes.
Repository storage: Additionally, Rapid Recovery supports the creation of repositories on complex dynamic volumes (striped, mirrored, spanned, or RAID). The file system of the machine hosting the repository must be NTFS or ReFS.
Rapid Recovery lets you download installers from the Rapid Recovery Core. From the Downloads page, you can choose to download the Agent Installer, the Local Mount Utility (LMU), or an SNMP MIB file. For more information about the LMU, see Understanding the Local Mount Utility. For more information about SNMP, see Understanding SNMP settings.
The Agent installer is used to install the Rapid Recovery Agent application on machines that are intended to be protected by the Rapid Recovery Core. If you determine that you have a machine that requires the Agent Installer, you can download the web installer from the Downloads page of the Rapid Recovery Core Console.