Messaging Server Notification for Cloud Disaster Recovery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Achieving a short Recovery Time Objective (RTO) and minimal Recovery Point Objective (RPO) in disaster recovery procedures for cloud environments is complex, time-consuming, and error-prone, particularly in synchronizing operations across multiple components during events like customer onboarding or failover.
Innovation Solution
An automated notification mechanism using a messaging server with a message-oriented middleware protocol, such as JMS, to facilitate the orchestration of disaster recovery events across client receivers, enabling efficient and accurate communication during failover or failback processes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If manual disaster recovery procedures are used to synchronize operations across multiple components, then flexibility and control are maintained, but the process becomes complex, time-consuming, and error-prone
Solution Approach 1:
The patent introduces a notification service as an intermediary component that receives notifications from multiple source systems and distributes them to target systems. This mediator automates the coordination of disaster recovery operations across multiple components, eliminating the need for manual synchronization while maintaining system control and reducing errors.
Solution Approach 2:
The system enables self-service automation where the notification service automatically processes disaster recovery notifications without human intervention. The service autonomously receives notifications, determines routing requirements, and distributes messages to appropriate target systems, making the disaster recovery process self-executing and reducing manual complexity.
2Loss of time
If automated notification mechanisms are implemented to reduce RTO and RPO, then disaster recovery efficiency improves, but system architecture complexity increases
Solution Approach 1:
The notification service is designed as a universal, multi-functional component that handles various types of disaster recovery notifications from multiple source systems and routes them to different target systems. This single automated service performs multiple functions (receiving, processing, routing, and distributing notifications), reducing the need for separate specialized systems and minimizing overall architectural complexity while achieving rapid automated response.
Data Source
AI summary
Some embodiments provide a system and method associated with disaster recovery from a primary region to a secondary region of a cloud landscape. A disaster recovery service platform may determine that a disaster recovery event has occurred and transmit an indication of the disaster recovery event. A messaging server, coupled to the disaster recovery service platform, may receive the indication of the disaster recovery event transmitted by the disaster recovery service platform and process the received indication via a message-oriented middleware protocol (e.g., in accordance with a subscription/publication framework. The messaging server may then arrange for at least one client receiver to receive information associated with the disaster recovery event. The disaster recover event might be associated with, for example, customer onboarding (or offboarding) a customer account failover (or failback), change in landscape, etc.