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. For more information about establishing or modifying database connection settings for the service database, see Configuring database connection settings.
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. |
◦ |
From the list of Core settings on the left side of the Settings page, click Database Connection. |
The Database Connection core settings appear.
◦ |
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. |
The setting you selected becomes editable.
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. |
1. |
◦ |
From the list of Core settings on the left side of the Settings page, click Local Database Settings. |
The Local Database core settings appear.
The setting you selected becomes editable.
Enter the name of a user with administrative privileges to the MongoDB service database. | |
Enter the password associated with the user name you specified. |
Information about configuring an SMTP email server is described in the topic Configuring an email server.
In Rapid Recovery, you can associate storage accounts you have with Cloud storage providers with your Rapid Recovery Core. This lets you archive information from protected machines when the data ages out.
Rapid Recovery integrates with Amazon™ S3, Microsoft Azure, and managed cloud providers using OpenStack open source technology.
For more information about managing cloud storage account information in the Rapid Recovery Core, see Cloud storage accounts.
© 2023 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy