Overview

This article provides an example Disaster Recovery Plan that you can use as a starting point to create your individual DRP.

Important factors to consider:

• Keep your backups in a geographically separated location as up-to-date as needed, to meet your disaster recovery point objectives.
• Store database credentials and any other environment configuration steps in a safe location.
• Practice your DRP annually.

Disclaimer: Tricentis is not responsible in the event you lose your data. This article is only an example of how you can prepare your Disaster Recovery Plan. 

Prerequisites

1. Keep your database backups. (Postgres and MongoDB.)
   If you do not know how to perform a database backup, follow the instructions linked below for your Operating System.
   • Postgres=Manager and Sessions
   • MongoDB=Parameters and Pulse
2. Keep the Attachments and Sessions storage backups. 
   If you do not know how to perform a backup of your data files for Attachments and Sessions storage, follow the links below:
   
   • Manager data files
   • Sessions data files
3. Backup your Insights reports at the following location:
   • qtestctl/insights/build/tomcat/webapp/ROOT/SavedDashboards and
   • qtestctl/insights/build/tomcat/webapp/ROOT/SavedReports
4. Identify your qtest database names.
   Example: manager, sessions, parameters, and pulse
5. Identify the Attachments and Sessions storage location.
   Example: NFS, shared drive, etc..

Architecture

You will replicate your current architecture in the DRP environment.

Actual Architecture

Example:

RDP Architecture

Example:

Application Recovery

In the event of a disaster, follow the instructions below to restore your data:

1. Restore Postgres and MongoDB databases on the database server.
   • Postgres
   • MongoDB
2. Restore the Attachments and Session storage on the database server, or in the shared drive location.
   • Manager data files
   • Sessions data files
3. Install qtest (the same release that you are currently using in production) in the new DR environment.
4. If you are using a load balancing/clustered environment, install qtest in each server.
5. Run the configuration script to set up the databases, attachments and session storage files.
6. Start up the qtest application, starting with the Manager server.
7. Stop insights.
8. After you install the qtest service, copy your backup Insights Reports to the correct location:
   • qtestctl/insights/build/tomcat/webapp/ROOT/SavedDashboards and
   • qtestctl/insights/build/tomcat/webapp/ROOT/SavedReports