Rapid Recovery 6.1.3

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.

Navigate to the Rapid Recovery Core Console.

On the icon bar, click

(More) and then click Downloads.

The Downloads page appears.

Scroll down to the Other Files pane.

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

The SNMP Configuration settings appear.

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.

Navigate to the Rapid Recovery Core Console.

On the icon bar, click

(Settings), and then do one of the following:

◦

From the list of Core settings on the left side of the Settings page, click vSphere.

◦

Scroll down on the right side of the Settings page until you can see the vSphere heading.

The vSphere settings appear.

Modify the vSphere settings as described in the following table.

Table 21. vSphere Core settings information

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

NOTE: The default setting is 00:10:00 or ten minutes.

Maximum simultaneous consolidations

Text field

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

NOTE: The default setting is 0.

Maximum retries

Text field

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

NOTE: The default setting is 10.

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.

NOTE: The default setting is No (cleared).

For each setting, when satisfied with your changes, click the check mark to save the change and exit edit mode, or click X to exit edit mode without saving.

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.

On the icon bar of the Rapid Recovery Core Console, click

(Settings), and then do one of the following:

◦

From the list of Core settings on the left side of the Settings page, click VMware Proxy.

◦

Scroll down on the right side of the Settings page until you can see the VMware Proxy heading.

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.

NOTE: The default is 8016.

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.

NOTE: The default setting is 5 minutes (00:05:00).

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.

NOTE: The default setting is 5 minutes (00:05:00).

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.

NOTE: The default setting is 1 minute (00:01:00).

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.

NOTE: The default setting is 1 minute (00:01:00).

For each setting, when satisfied with your changes, click the check mark to save the change and exit edit mode, or click X to exit edit mode without saving.

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.

NOTE: You must first back up Core setting information before you can use this process to restore Core settings.

Use this procedure to back up and restore Core settings.

Navigate to the Rapid Recovery Core Console.

On the icon bar, click

(Settings).

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.

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

To back up the current settings in an XML file, from the top of the Settings page, click Back Up Settings.

The Back Up Core Configuration dialog box appears.

In the Local path text box, type a directory path accessible locally to the Core machine where you want to store core settings as an XML file, and then click Back Up.

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.

To restore Core settings from a backup XML file saved previously using this method, perform the following steps.

NOTE: When you restore the Core configuration settings, the Rapid Recovery Core service restarts.

From the top of the Settings page, click Restore.

The Restore Core Configuration dialog box appears.

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.

If you do not want to restore repository information, proceed to Step g.

Optionally, if you want to restore repository information as configured in the backup file, select Restore Repositories and then click Restore.

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.

Verify the repository information you want to restore. If multiple repositories appear in the lists for verification, and you only wish to restore information for some of them, then clear the selection for each repository you do not want.

When you are satisfied with the selection of repositories you want to restore, click Save.

The Restore Repositories dialog box closes.

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.

If any configuration settings could not be restored you will see an error message. Review the details of the error to see if any action is required on your part. For more information, see Viewing events using tasks, alerts, and journal pages. To continue, click Close to clear the error dialog box.

After restoring the configuration, verify the following:

▪

Unlock all encryption keys. For more information, see Unlocking an encryption key.

▪

If virtual standby is configured to continually update a VM to a network destination, you must specify the network credentials in the virtual standby settings before a successful synchronization. For more information, see VM export.

▪

If scheduled archive is configured to archive to a cloud storage account, you must specify credentials so the Core can connect to the cloud account. For more information on linking the Core with a cloud storage account, see Adding a cloud account.

▪

If replication is set up and you want to restore to a target Core, verify the target Core settings (particularly the host) on the source Core. For more information, if managing your own Core, see Replicating to a self-managed target Core. If replicating to a Core managed by a third party, see Replicating to a third-party target Core.

▪

If the SQL attachability check is configured, and if the SQL Server instance performing the check is on the Core machine, then specify the SQL credentials in Attachability settings. For more information, see Managing Core SQL attachability settings.