RecoveryManager Plus allows you to configure periodic backups of the database that comes built-in with it. The product also allows you to migrate from the built-in database (PostgreSQL) to MS SQL.
Using this option you can change the built-in database server (PostgreSQL) of RecoveryManager Plus to MS SQL Server or another instance of a PostgreSQL Server.
Important points to remember
- Supported database migrations:
- PostgreSQL Server to MS SQL Server or another instance of PostgreSQL Server.
- MS SQL Server to PostgreSQL Server or another instance of MS SQL Server.
- Supported database versions:
- PostgreSQL: 9.2 to 9.5
- MS SQL: 2005 and above
- Take a backup of the database before you proceed.
- For MSSQL
- Copy the bcp.exe and bcp.rll files from the SQL Server installed directory and paste them in the RecoveryManager Plus bin folder (<RecoveryManager Plus_installed_directory/bin). Instead of manually copying the files, you can also do this while configuring database migration directly from the user interface.
- Location of the bcp.exe file: <MSSQL_installed_folder>\Client SDK\ODBC\130\Tools\Binn\bcp.exe. For example, C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\130\Tools\Binn\bcp.exe.
- Location of the bcp.rll file: <MSSQL_installed_folder>\Client SDK\ODBC\130\Tools\Binn\Resources\1033\bcp.rll. For example, C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\130\Tools\Binn\Resources\1033\bcp.rll
- For migration to MS SQL, please install the corresponding SQL Native Client in the RecoveryManager Plus machine as per the MS SQL Server version.
- If firewall is enabled in the MS SQL Server machine, the TCP and UDP ports must be opened.
- For External Pgsql
- In the machine where PostgreSQL is installed, go to <postgresql_installdir>/data and open the posgresql.conf file. Search for wal_level entry. Uncomment the entry and change its value to archive.
- Copy all the files in <postgresql_installdir>/lib and <postgresql_installdir>/bin folders and paste them in <product_home>/pgsql/lib and <product_home>/pgsql/bin folders respectively. <product_home> refers to the home directory of RecoveryManager Plus.
- Restart the external PostgreSQL server.
- Repeat the steps 1 to 3 from above whenever you update the PostgreSQL server.
Steps to migrate database
- Log in to RecoveryManager Plus as an administrator.
- Navigate to Admin → Administration → Database Settings → Database Configuration.
- From the Select Database Server menu, select the database server that you want to change to.
- If you select PostgreSQL Server, then:
- In the DB Server Name/IP and Port field, enter the host name or IP address and the port number of the PostgreSQL database server.
- Enter the Username and Password of a user who has permission to create a new database.
- If you select MS SQL Server, then:
- In the DB Server Name/IP and Port field, enter the host name or IP address and the port number of the MS SQL database server.
- In the DB Server Instance field, select the SQL Server instance you want to use.
- If you have already moved the bcp.exe and bcp.rll files, the same will be visible in the Select bcp.exe File and Select bcp.rll File fields. If not, click Browse and select the bcp.exe and bcp.rll files from SQL Server installed directory.
- For Authentication, you can either use Windows credentials or a SQL Server user account.
- If you want to use a SQL Server user account, then select SQL Authentication and enter the Username and Password.
- If you want to use Windows authentication, select Windows Authentication, and enter the username and password of a Windows domain user account. To autofill the username and password of the user currently logged into the machine check the box against Use Default Windows Authentication.
Note: The user account used must have permission to create a database in the selected MS SQL Server.
- Check the box against Migrate Existing Data to copy the data from your old database to the new database.
IMPORTANT: Leave this box unchecked only if you want to change the database of a fresh installation of RecoveryManager Plus.
- Click Save.
RecoveryManager Plus stores AD and Azure AD backups and metadata of Microsoft 365, Google Workspace, and on-premises Exchange backups in its Elasticsearch node. When you install RecoveryManager Plus, a default on-premises repository (Elasticsearch node) named RMP-NODE1 is created. This repository cannot be deleted.
- Navigate to the Admin tab > Administration > Database Settings > Database Configuration > Elasticsearch.
- On the displayed page, you will find details about the Node Name, Data Path, Usage, Capacity, Free Space, and Status of the Elasticsearch node.
You can also perform the following operations:
Refresh repository details
To fetch the status of used and available storage space:
- Click the icon located in the Actions column of the repository.
Edit the existing repository
- Click the icon under the Actions column to edit the Data Path or JVM Heap Size.
- To modify the Data Path of the repository, click the icon and select the required storage from the list shown.
- To modify the JVM Heap Size, type the size in gigabytes in the box given.
Note: JVM heap size must be at least 1GB. Also, JVM heap size cannot be more than 50% of the target machine’s usable RAM.
- Click Save.
Configure email notifications
- Click the Alert Settings button.
- Select any one of the below options for which you’d like to receive notifications:
- Alert me if any server is disconnected
- Alert me when used storage space reaches <specific percentage>
- Click Save.