Chat now with support
Chat with Support

Rapid Recovery 6.1.2 - User Guide

Introduction to Rapid Recovery Core Console Core settings Repositories Encryption keys Protecting machines
About protecting machines with Rapid Recovery Support for dynamic and basic volumes 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 Settings and functions for protected Exchange servers Settings and functions for protected SQL servers
Managing protected machines Snapshots and recovery points Replication Events Reporting VM export Restoring data Bare metal restore
Bare metal restore for Windows machines Understanding boot CD creation for Windows machines Using the Universal Recovery Console for a BMR Performing a bare metal restore for Linux machines Viewing the recovery progress Starting a restored target server Troubleshooting connections to the Universal Recovery Console Repairing boot problems Performing a file system check on the restored volume
Managing aging data Archiving Cloud storage accounts The Local Mount Utility The Central Management Console Core Console references Command Line Management utility PowerShell module
Prerequisites for using PowerShell Working with commands and cmdlets Rapid Recovery PowerShell module cmdlets Localization Qualifiers
Scripting REST APIs About us Glossary

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. For more information about establishing or modifying database connection settings for the service database, see Configuring database connection settings.

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.

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.

You are prompted to confirm this action, which results in abandoning any customized database connection settings.

The setting you selected becomes editable.

Table 16. Database connection settings information

Text Box

Description

Host name

Enter a host name for the database connection.

Port

Enter a port number for the database connection.

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.

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.

Minimum connection pool size

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

Modifying local 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.

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.

The Local Database core settings appear.

The setting you selected becomes editable.

Table 17. 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.

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.

Managing Cloud configuration settings

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.

Related Documents