...
| Tip | ||
|---|---|---|
| ||
The prerequisites for upgrading the production and DR environments remain the same as that for the deployment of the application discussed in this section. |
Anchor prodToDev prodToDev
Switching from PROD to DR Environment
| prodToDev | |
| prodToDev |
You may want to switch from production to DR environment based on your business requirement. To achieve this, follow the steps given below.
...
When the production application goes down
Perform the following steps to switch to the DR environment:
...
Follow the steps given
...
in
...
Click Scheduler in the left pane.
...
You can also resume the Scheduler by using an API. The format for the API is given below.
| Code Block | ||||
|---|---|---|---|---|
| ||||
<Gateway_URL>/event/schedulerservice?_dc=1670999141899&query=Resume&page=1&start=0&limit=25 |
Run the command in the following format to scale up the listener pod from 0 to 1.
| Code Block | ||||
|---|---|---|---|---|
| ||||
kubectl scale --replicas=1 deployment <name of the listener deployment> -n <namespace> |
...
Update the DNS records to point to the DR environment.
...
| title | Switching back to the production environment |
|---|
Once the production environment is restored, you need to do the followings to switch back to it from the DR environment:
...
the Switching from PROD to DR environment section.
When the Primary Database fails
...