Quick Rapid Recovery Initial Installation and Configuration Guide (4042244)

Pre-requisites

To get Rapid Recovery system installed and configured, initially ensure the following requirements are met or available:

• Desktop-based OS like Windows 11 can host Rapid Recovery Core software, however installed and fully updated Windows server-grade OS is preferable. Please consult Rapid Recovery System Requirements Guide to make sure that OS version is supported
• Adequately sized hardware for the Core server and storage to host the repository is required. Storage types that Rapid Recovery can work with are (from better to worse): DAS (local storage), SAN, NAS (iSCSI-connected), NAS (CIFS/SMB-connected). For additional information, please consult Rapid Recovery Sizing Guide.
• Core and Agent software can be downloaded from Quest Support Portal.
• The license file can be downloaded by logging into the organization license portal.

Installation

1. Install Rapid Recovery Core software on the system. A reboot might be required.
2. Once installation completes, wait until Quest Core services start, then open a Core console. A shortcut will be put on the desktop during product installation.
3. Next, apply the LIC file downloaded from the Licensing Portal.
4. Install the Agent software on the machine(s) that is/are going to be protected. Please note that agent software installation requires a reboot. Agentless type of protection does not require agent software installation on VMs (except for Hyper-V hosts themselves)

Initial Configuration

• The very first step that must be performed is repository creation. Repository is a set of very large files that act as a virtual disk container. Repository information will be stored on Data and Metadata directories. There's no need to create separate Data and Metadata folders if both will be stored on the same disk.
• Create an empty folder (or folders if Data and Metadata will be separate)
• If storage is local (DAS) or network-attached by iSCSI, then write down it's "bytes per sector" value using this command from elevated CMD:
  • fsutil fsinfo ntfsinfo <drive_letter>:
• On the Core console, click on More (...), Repositories, and click on Create.
• Specify logical name of the repository on top and click on Add Storage Location.
• In the following dialog box, click on More Details to expose additional parameters.
• Specify Data and Metadata folders path, size of the repository (in GB or TB), make sure that Write Caching Policy option is set to Off and Bytes Per Sector value is matching the output of the fsutil command. Click on Save.
• Click on Create button. Repository will be created taking all the specified size immediately. For performance reasons, repository is thick provisioned
• Once repository is created, it's recommended to change the DVM Deduplication cache size in Core console, Settings (gearbox icon). When doing that please consider the following guidelines:
  • It's recommended to size DVM dedupe cache as 1GB per 1TB or repository size, however not bigger than 1/2 of the RAM on Core server.
  • Realistically, there's not much benefit increasing DVM dedupe cache size bigger than 10 or 16GB even though there's a plenty of RAM
  • DVM dedupe cache will be flushed to the disk C periodically into 2 separate folders, so please make sure that there's enough free disk space for 2 x DVM_dedupe_size GB.

Protect machines

• Click the Protect button on the top of Core console and specify name or IP of the machine where agent software was installed previously. Follow the wizard prompts to specify a protection schedule. Please avoid using default 24/7 hourly schedule as it's rarely needed. Protection schedule should overlap the time, when content if created of changed on the protected machine.
• To protect VMs agentlessly, please click on Protect button drop down and select Protect Multiple. Follow the wizard to select the hypervisor and VMs on it.