Chat now with support
Chat with Support

Rapid Recovery 6.5 - User Guide

Introduction to Rapid Recovery The Core Console Repositories Core settings Managing privacy Encryption Protecting machines
About protecting machines with Rapid Recovery 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 Enabling application support Settings and functions for protected Exchange servers Settings and functions for protected SQL servers
Managing protected machines Credentials Vault Snapshots and recovery points Replication Events Reporting VM export Restoring data Bare metal restore
About bare metal restore Differences in bare metal restore for Windows and Linux machines Understanding boot CD creation for Windows machines Managing a Linux boot image Performing a bare metal restore using the Restore Machine Wizard Using the Universal Recovery Console for a BMR Performing a bare metal restore for Linux machines Verifying a bare metal restore
Managing aging data Archiving Cloud accounts Core Console references REST APIs Glossary

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.

  1. From the Rapid Recovery Core Console, on the icon bar, click [More] (More) and then click [Core log] Core Log.
  2. On the Download Core Log page, click [Download] Click here to begin the download.
  3. If prompted to open or save the Core AppRecovery.log file, click Save.
  4. 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.

  1. Navigate to the Rapid Recovery Core Console.
  2. On the icon bar, click [Settings] (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.
  3. From the top of the Database Connection settings area, you can do the following:
    • Click [Test Connection]Test Connection to verify your settings.

      Testing the connection is recommended when you change any of the database connection settings.

    • Click [Restore Default]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.

  4. Click on the setting you want to change.

    The setting you selected becomes editable.

  5. Enter the configuration information as described in the following table.
    Table 26: 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.

  6. For each setting, when satisfied with your changes, click [Save] to save the change and exit edit mode, or click [Cancel] 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.

  1. Navigate to the Rapid Recovery Core Console.
  2. On the icon bar, click [Settings] (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.
  3. Click on the setting you want to change.

    The setting you selected becomes editable.

  4. Enter the appropriate credentials for connecting to the service database, as described in the following table.
    Table 27: 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.
  5. For each setting, when satisfied with your changes, click [Save] to save the change and exit edit mode, or click [Cancel] to exit edit mode without saving.

Managing SMTP server settings

If you configure simple mail transfer protocol (SMTP) server settings for the Core, you can send task, event, and alert notifications by email.

Information about configuring an SMTP email server is described in the topic Configuring an email server.

NOTE: To send event information by email, you must also configure notification group settings. For more information on specifying events to receive email alerts, see Configuring notification groups.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating