Rapid Recovery 6.1.2 - 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

Downloading the SNMP MIB file

The Simple Network Management Protocol is used to monitor devices on a network for conditions that require attention. When the Rapid Recovery Core is set as an SNMP agent, the Core report information such as alerts, repository status, and protected machines. This information can be read by an SNMP host using a standalone application called an SNMP browser.

Data objects managed by SNMP agents are organized into a Management Information Base (MIB) file that contains Object Identifiers (OIDs). Each OID identifies a variable that can be read or set using SNMP.

You can download a MIB file from the Rapid Recovery Core. This file, named quest-rapid-recovery-core.mib, can then be read by an SNMP browser in a more user-friendly fashion than data it receives directly from the Core.

Use this procedure to download the SNMP MIB file from the Rapid Recovery Core.

1.
Navigate to the Rapid Recovery Core Console.

The Downloads page appears.

4.
To download the MIB file, click the SNMP MIB file download link.

The SNMP Configuration settings appear.

5.
In the Opening quest-rapid-recovery-core.mib dialog box, do one of the following:
To open the log file, select Open with, then select an SNMP browser application for viewing the text-based MIB file, and finally click OK.

The MIB file opens in the selected application.

To save the file locally, select Save File and click OK.

The quest-rapid-recovery-core.mib file saves to your Downloads folder. It can be opened using an SNMP browser or a text editor.

Configuring vSphere settings

VMware vSphere is a suite of virtualization software, from which you can manage ESXi or vCenter Server virtual machines. If using vSphere, you no longer need to load the Rapid Recovery Agent software onto individual VMs to protect them. This is called the agentless protection feature, which applies only to virtual machines.

Use this procedure to configure vSphere settings for the Core.

1.
Navigate to the Rapid Recovery Core Console.

The vSphere settings appear.

Table 21. vSphere Core settings information

UI Element

UI Type

Description

Connection lifetime

Spin box

Establishes duration of time before a timeout for the connection with the ESXi server. Uses HH:MM:SS format.

Maximum simultaneous consolidations

Text field

Sets the maximum number of simultaneous consolidations for protected virtual machines.

Maximum retries

Text field

Sets the maximum number of attempts for connection to a virtual disk or read and write operations before a timeout.

Allow parallel restore

Boolean (check box)

When this option is checked, enables parallel restore for an agentless virtual machine.

When this option is cleared, this function is disabled.

Managing VMware proxy settings

The VMware proxy settings are intended for protected VMware ESXi machines that require Virtual Disk Development Kit (VDDK) APIs to access the VMware disk storage. Rapid Recovery addresses this access and possible timeouts associated with it by using a process called the VMware proxy. This service is automatically installed with the Rapid Recovery Core and only runs when it is needed. The Core Settings page lets you adjust the service timeout settings as you see appropriate.

1.
On the icon bar of the Rapid Recovery Core Console, click [Settings] (Settings), and then do one of the following:
2.
Under VMware Proxy, modify the timeout settings described in the following table.

Table 22. VMware proxy settings information

UI Element

Description

Service port

The port that the VMware proxy uses to communicate with the VMware disk storage.

Connection timeout

The maximum amount of time that should pass before the VMware proxy should stop trying to connect to the VMware disk storage, designated by hh:mm:ss.

Read/Write timeout

The maximum amount of time that should pass before the VMware proxy should stop trying to read or write to the VMware disk storage, designated by hh:mm:ss.

Start service timeout

The maximum amount of time that should pass before Rapid Recovery should stop trying to start the VMware proxy service, designated by hh:mm:ss.

Stop service timeout

The maximum amount of time that should pass before Rapid Recovery should stop trying to stop the VMware proxy service, designated by hh:mm:ss.

Backing up and restoring Core settings

You can back up Core setting information to a file, and later restore these settings if you have problems with the Core machine or if you want to migrate those settings to a different machine. Information that gets backed up includes repository metadata (such as the repository name, data path, and metadata path); machines protected in the Core; replication relationships (targets and sources); which machines are configured for virtual standby; and information about encryption keys.

This process restores the configuration settings only, not the data. Security information (such as authentication credentials) is not stored in the configuration file. There is no security risk to saving a Core configuration file.

Use this procedure to back up and restore Core settings.

1.
Navigate to the Rapid Recovery Core Console.

The Settings page appears. At the top of the Settings pane, above the categories of settings, you see two buttons, Back Up Settings and Restore Settings.

3.
If you want to back up Core settings, proceed to Step 4. If you want to restore Core settings, proceed to Step 6.

The Back Up Core Configuration dialog box appears.

For example, type C:\Users\Your_User_Name\Documents\AA5CoreSettings and then click Back Up.

A file named AppRecoveryCoreConfigurationBackup.xml is saved to the local destination you specified.

NOTE: When you restore the Core configuration settings, the Rapid Recovery Core service restarts.
a.
From the top of the Settings page, click Restore.

The Restore Core Configuration dialog box appears.

b.
In the local path text box, enter the local path of the location where you stored the core configuration settings.

For example, type C:\Users\Your_User_Name\Documents\AA5CoreSettings.

The Restore Repositories dialog box appears.

If you choose to restore repository information from the backed-up configuration data, then any repositories configured when the Core settings were saved appear for verification. By default, each existing repository is selected.

The Restore Repositories dialog box closes.

g.
In the Restore Repositories dialog box, click Restore.

The Restore Repositories dialog box closes, and the restore process begins. An alert appears indicating that the repository service configuration has changed.

Related Documents