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
- 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 27: 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
- 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 28: 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. - For each setting, when satisfied with your changes, click
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. |
Configuring cloud account connection settings
Cloud account connection settings let you determine how much time should pass between Rapid Recovery attempts to connect to your cloud account before the operation times out. Complete the steps in the following procedure to configure the connection settings for your cloud account.
- Navigate to the Rapid Recovery Core Console.
- On the icon bar, click The Settings page appears.
- In the left menu, click
Cloud Accounts.
- In the Cloud Accounts table, click the
drop-down menu next to the cloud account you want to configure, and then complete one of the following actions:
- To return any custom cloud configuration settings to the following default settings, click Reset.
- Request timeout 01:30 (minutes and seconds)
- Write buffer size 8388608 (bytes)
- Read buffer size 8388608 (bytes)
- To change the cloud account connection settings, click Edit, and in the Cloud Configuration dialog box, complete any of the following actions:
- For Request timeout, use the up and down arrows to determine the amount of time in minutes and seconds that Rapid Recovery should spend on a single attempt to connect to the cloud account when there is a delay. Connection attempts will cease after the entered amount of time.
- For Write buffer size, enter the buffer size you want to reserve for writing archived data to the cloud.
- For Read buffer size, enter the block size you want to reserve for reading archived data from the cloud.
- To return any custom cloud configuration settings to the following default settings, click Reset.