...
The illustration given below depicts the DR model recommended by Adeptia.
This can be achieved by having a two zone deployment of the application that share the same database for Read/Write purpose. In an ideal condition, all the requests are handled and processed in the production environment. The application in DR environment does not perform any kind of processing, nor does it interact with the database.
...
Switching from PROD to DR Environment
Pre-requisites:
...
You may want to switch from production to DR environment based on your business requirement. To achieve this, follow the steps given below.
| Warning | ||
|---|---|---|
| ||
Before you follow the steps to switch from production to DR environment, install azcopy CLI on |
...
the client |
...
you use for accessing the Kubernetes cluster. |
...
Steps to switch from PROD to DR environment
Scale down the Runtime and Listener deployments in the prod environmentPROD environment by running the commands in the following formats.
kubectl scale --replicas=0 deployment <Release Name>-ac-runtime -n <namespace>
kubectl scale --replicas=0 deployment <Release Name>-ac-listener -n <namespace>...
The above failover steps are not mandatory. These steps are mandatory only when the Azure File Share is is not accessible due to any failure.
As per Microsoft guideline, the time it takes to failover after initiation can vary though typically less than one hour.
...
Using DR to recover from a failure
Adeptia's DR model helps you recover from a failure. Adeptia's DR model covers the following two scenarios and the action steps you need to perform to address the failure and recover the infrastructure, application, and the data with a quick turnaround time.
...