Rapid Recovery 6.10 - User Guide

Information about various activities for the Rapid Recovery Core are saved to the Core log file. This file, AppRecovery.log, is stored by default in the path C:\ProgramData\AppRecovery\Logs.

NOTE: Depending on your settings, the AppRecovery directory may not be visible on the Rapid Recovery Core. To see this directory, you may need to change the Folder Options control panel to show hidden files, folders, and drives. If these settings include the option to hide extensions for known file types, the Core log file may appear as AppRecovery with no .log extension.

The Core log includes information about completed Core jobs, connection failures, results of attempts on the part of the Core to contact the License Portal, and other information. Each statement stored in the Core log file is preceded by one of four qualifiers: INFO, DEBUG, ERROR, and WARN. These qualifiers help categorize the nature of information stored in the log when diagnosing an issue.

NOTE: Similarly, a log file is also stored on each protected machine containing information relating to its attempts at communicating with the Core. For more information about machine logs, see Downloading and viewing the log file for a protected machine.

The ability to access logs can be useful when troubleshooting an issue or working with Quest Data Protection Support. To access logs, see the following procedures:

Downloading and viewing the Core log file

If you encounter any errors or issues with the Core, you can download the Core logs to view them or to share them with your Quest Support representative.

From the Rapid Recovery Core Console, on the icon bar, click (More) and then click Core Log.
On the Download Core Log page, click Click here to begin the download.
If prompted to open or save the Core AppRecovery.log file, click Save.
If you see the Opening Core AppRecovery.log dialog box, do one of the following:

To open the log file, select Open with, then select an application (such as Notepad) for viewing the text-based log file, and finally click OK.
The Core AppRecovery.log file opens in the selected application.

To save the file locally, select Save File and click OK.
The Core AppRecovery.log file saves to your Downloads folder. It can be opened using any text editor.

Configuring database connection settings

Rapid Recovery displays information about Core tasks, events, and alerts on the Events page. Rapid Recovery stores this transactional information in a MongoDB service database that is installed locally by default on the Core machine. You can configure these settings to change how long information is retained in the database, or to change the connection pool size to allow for more or fewer concurrent connections.

If using a second Rapid Recovery Core, you can configure the database connection settings on the first Core to point to the second Core machine. In this way, the event data for both Cores will be stored in the MongoDB on the second Core.

Alternatively, you can configure the database connection settings on the Core to point to another machine that has a separately installed MongoDB which is accessible over the network to the Rapid Recovery Core. The event transaction data for your Core is then saved to that service database, not locally.

NOTE: For more information about viewing event information from the Rapid Recovery Core, see Viewing events using tasks, alerts, and journal pages.

Customers can choose to specify installation of the MongoDB service database on another machine accessible on the network to the Rapid Recovery Core. If the service database for your Rapid Recovery Core is installed on a machine other than the machine hosting the Rapid Recovery Core, you must provide database credentials (a user name and password) in these settings.

Complete the steps in this procedure to modify the database connection settings for the service database used by the Rapid Recovery 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 Database Connection.
- Scroll down on the right side of the Settings page until you can see the Database Connection heading.
From the top of the Database Connection settings area, you can do the following:
- Click Test Connection to verify your settings.
  Testing the connection is recommended when you change any of the database connection settings.
- Click Restore Default to restore all default database connection settings.
  You are prompted to confirm this action, which results in abandoning any customized database connection settings.
Click on the setting you want to change.

The setting you selected becomes editable.

Enter the configuration information as described in the following table.

Table 30: Database connection settings information

Text Box

Description

Host name

Enter a host name for the database connection.

NOTE: When localhost is the parameter specified as the host, the MongoDB is installed locally on the machine hosting the Core.

Port

Enter a port number for the database connection.

NOTE: The default setting is 27017.

User name

Enter the name of a user with administrative privileges to the MongoDB service database.

NOTE: If the host name parameter is localhost, this field is not required.

Password

Enter the password associated with the user name you specified.

NOTE: If the host name parameter is localhost, this field is not required.

Retention period (day)

Enter the number of days to retain the event and job history in the service database.

Maximum connection pool size

Sets the maximum number of database connections cached to allow dynamic reuse.

NOTE: The default setting is 100.

Minimum connection pool size

Sets the minimum number of database connections cached to allow dynamic reuse.

NOTE: The default setting is 0.

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

Modifying loca database connection settings

You can view system events related to the Rapid Recovery Core on the Events page. The Rapid Recovery Core stores this transactional information in a MongoDB service database. By default, this database is installed locally on the Core machine, and the hostname in the database connection settings defaults to localhost. In this situation, the loopback interface bypasses local network interface hardware, and database credentials are not required.

Optionally, to increase security, you can explicitly specify database credentials (a user name and password) for the MongoDB database used by the Rapid Recovery Core.

NOTE: For more information about viewing event information from the Rapid Recovery Core, see Viewing events using tasks, alerts, and journal pages. For information about database connection settings, see Configuring database connection settings.

Complete the steps in this procedure to modify the local database connection settings to specify database credentials.

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 Local Database Settings.
- Scroll down on the right side of the Settings page until you can see the Local Database Settings heading.
Click on the setting you want to change.

The setting you selected becomes editable.

Enter the appropriate credentials for connecting to the service database, as described in the following table.

Table 31: Local database settings information
Text Box	Description
User name	Enter the name of a user with administrative privileges to the MongoDB service database.
Password	Enter the password associated with the user name you specified.