Recovery Workflow

In a typical Amorphic disaster recovery scenario, the following workflow is employed to ensure business continuity and minimize data loss:

Recovery Workflow:

1. Detection of Primary Region Failure:

   • The scenario begins with the detection of a failure in the primary region. This failure can involve critical services such as data sources or network infrastructure, impacting the Amorphic deployment.
   • In case of a critical service failure, users have the option to contact the Amorphic support team for assistance and guidance throughout the recovery process.

2. Activation of DR Resources in Secondary Region:

   • Upon detecting the primary region failure, the DR (Disaster Recovery) resources in the secondary region are activated.
   • If the primary region issue cannot be quickly resolved and the failover is deemed necessary, the decision to fail over to the secondary region is made, Whether to leverage Amorphic in the secondary region is at user's discretion.

3. Data Replication and Synchronization:

   • To ensure data consistency and minimize potential data loss, all activities in the workspace are stopped. This includes user workloads, ongoing jobs, and any other processes that could impact data integrity.
   • Data replication and synchronization mechanisms are initiated to ensure that the secondary region is up-to-date with the latest data from the primary region. This step helps maintain data integrity during the failover process.
   • Extensive testing is conducted to ensure that the secondary region is fully operational and meets performance expectations. Once testing is successful, the secondary region is declared operational, and production workloads can resume. Users regain access to the active deployment.

4. User Access Redirection to the Secondary Region:

   • User access is redirected to the secondary region to ensure uninterrupted service availability. Users interact with the Amorphic deployment as if it were still in the primary region.

5. Ongoing Monitoring and Validation of System Health:

   • Continuously, we will monitor the primary region to check its availability and ensure that resources are operational, meeting performance expectations.

Note

During these recovery and failover processes, it's important to acknowledge that some data loss may occur. It's essential to define acceptable levels of data loss and implement mitigation strategies accordingly to minimize any potential impacts. Data loss mitigation measures should be carefully planned and documented as part of the overall disaster recovery strategy.