1. Coordination among multiple systems: In highly resilient systems, there may be multiple systems and applications that need to be integrated and coordinated in order to achieve proper disaster recovery. Ensuring proper coordination and communication among these systems can be challenging.
2. Complexity of system architecture: Architecturally resilient systems are often highly complex, which can make disaster recovery more challenging. It may be difficult to identify all the components of the system, understand their interdependencies and their priorities for recovery.
3. Data Replication and Backup: To ensure resilience (high availability) of data intensive systems like databases, redundant copies of database instances are kept in a separate data center as part of an overall disaster recovery strategy. However, maintaining and synchronizing these copies can become complex and difficult.
4. Testing Disaster Recovery procedures: Testing disaster recovery procedures in architecturally resilient systems can be challenging, given that the systems are often complex and interdependent. Proper testing of disaster recovery procedures is critical, but can be time-consuming and expensive.
5. Risk assessment and planning: There is a need to assess and balance the risks associated with possible disasters with the costs involved in various recovery strategies. With respect to accessing cloud based system infrastructure this could include issues related to network access and recovery time objectives.
6. Resource Allocation: Getting the right resources in place to both develop and implement disaster recovery strategies can be challenging. This could include personnel, technology and budgetary considerations.
Publication date: