This section contains the plan and description regarding the operational activities for Pyplan application disaster recovery.
The section describes the operational procedures for Pyplan application recovery when a disaster event occurs that affects an entire IaaS Cloud Availability Zone where Pyplan production environment resides.
The temporal objectives to recover the entire application are:
To reactivate the Pyplan application service, the following conditions must be met:
Event Type | Description | Examples | Response |
---|---|---|---|
DISASTER | Event that disables the Data Center to provide its services | Earthquakes, general fire, power failure, natural catastrophes, others | Activation of disaster recovery plan |
INTERRUPTION | Event that needs to be evaluated to be handled as a disaster or as a contingency. Depends on the impact determined in incident management. | Systems or service failure | Activation of disaster recovery plan or contingency application |
CONTINGENCY | Event that impacts a resource necessary for the provision of services | Module failure or temporary failure | Contingenc |
Notification of the unavailability of information systems or IT services can come from different sources, depending on the nature of the event, the time at which it occurs and the source that causes it.
The following is a description of the process by which the management plan is activated, after notification of the disaster:
Next table shows the operational tasks that will be carried out in the event of applying the disaster recovery plan
Task | Target time (hours) |
---|---|
Deployment of architecture in a new availability zone | 20 |
Data restoration using the latest available backup | 12 |
Manual operation tests | 2 |
Run the automatic stress tests | 1 |
URL release for production use | 1 |
Pyplan performs annual disaster recovery plan tests