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.
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. |
2. |
The Downloads page appears.
4. |
The SNMP Configuration settings appear.
5. |
◦ |
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.
◦ |
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. |
4. |
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. |
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 |
◦ |
Scroll down on the right side of the Settings page until you can see the VMware Proxy heading. |
2. |
The port that the VMware proxy uses to communicate with the VMware disk storage.
| |||
| |||
| |||
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. | |||
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. |
3. |
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. |
Use this procedure to back up and restore Core settings.
1. |
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. |
4. |
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.
a. |
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.
d. |
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.
The Restore Repositories dialog box closes.
g. |
The Restore Repositories dialog box closes, and the restore process begins. An alert appears indicating that the repository service configuration has changed.
h. |
▪ |
▪ |
▪ |
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. |
▪ |
© 2023 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy