Disaster recovery models

Due to any planned or unplanned event, an application may face a downtime in any form and at any time. This may cause huge data loss and irreversible damage to your business causing a disastrous scenario. ITES industry usually keeps a business continuity plan to address such outages. Therefore, Adeptia also recommends installing Adeptia Connect in a disaster recovery environment that would ideally keep the business running in case the main production environment is down.

Adeptia recommends you to follow any of the two models to ensure continuous operation in case of unexpected scenario of disaster: 

• Basic Standby model
• High Availability model

Basic Standby model

Basic Standby model is achieved by backing up the data from production environment's RAID to the RAID of disaster recovery constantly. This helps in copying all the activities created and stored in the RAID of the Production environment to the Disaster Recovery environment, protecting the data and application during disaster and keeps the business continuity intact. 

To achieve this, you must install another instance of Adeptia Connect other than regular production environment. This instance can be termed as Disaster Recovery environment. After you have installed Adeptia Connect in the Production Environment, follow the post installation steps given below:

If you are setting a disaster recovery environment then you need to use DNS name instead of IP address in both front-end (Adeptia Connect) and back-end (Adeptia Suite) applications.

• Clustered Environment
  If you have installed Adeptia Connect in a clustered environment then use DNS of the internal load balancer and external load balancer.
  
  
• Non-Clustered Environment
  If you have installed Adeptia Connect in a non-clustered environment then use DNS of Adeptia Suite and Adeptia Connect.

After this, you need to install another instance of Adeptia Connect in Disaster Recovery Environment. Follow the instructions described here to install Adeptia Connect in the Disaster Recovery Environment.

While installing Adeptia Connect, you need to keep in mind the following points.

• Select existing tables option while configuring backend and log database wizard.
• Configure the same mail server parameters that you have specified in the production environment.
• Configure the replicated shared path folder that you have specified in the production environment while enabling clustering. 
• Configure the same values in the application.properties file that you have specified in the production environment.

After you have installed Adeptia Connect, stop Kernel, WebRunner, and Tomcat since RAID will automatically update all the activities without running the services.

Follow the relevant sections mentioned in the table below to have a Basic Standby disaster recovery model: 

High Availability model

Adeptia Connect High Availability (HA) deployment architecture defines the components of Adeptia Connect (Connect Portal and Connect Server), shared storage, and redundant databases which ensure optimal operational performance, even at times of high loads. This architecture also helps you understand one of the disaster recovery mechanisms of Adeptia Connect system.

The diagram below represents the high availability of Adeptia Connect in different availability zones (data center). All these nodes are accessible to each other.

High Availability deployment architecture mandates the following requirements and configuration:

• Redundant and highly available architecture.
• Minimum 8 servers: 2 for Connect Portal, 4 for Connect Server, and 2 for Database.

• Cluster of Connect Server nodes can be increased to scale with high data and transaction volumes.