Container Volume Replication Prioritization for Disaster Recovery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing disaster recovery systems require users to manually determine and reconfigure volume replication based on the order of importance between applications, which is inefficient and costly, especially when new applications are frequently deployed or application priorities change.
Innovation Solution
A method that automatically creates volumes in a first storage system for newly launched containers and establishes replication to a second storage system based on container priority, from highest to lowest, allowing for efficient resource allocation and reduced operational costs by prioritizing replication and de-replication based on application importance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If users manually determine and reconfigure volume replication based on application importance, then disaster recovery can be established, but the process becomes inefficient and costly especially when new applications are frequently deployed or priorities change
Solution Approach 1:
The system automatically determines which volumes to replicate and in what order based on application priority metadata, eliminating the need for manual user determination and reconfiguration. The storage system self-manages the replication configuration by retrieving priority information and autonomously establishing the replication sequence.
Solution Approach 2:
Application priority metadata is established in advance during application deployment or configuration, before disaster recovery needs to be configured. This preliminary assignment of priority values enables the system to immediately determine replication order without requiring manual intervention when new applications are deployed or priorities change.
2Reliability
If users manually reconfigure volume replication whenever new applications are deployed or priorities change, then disaster recovery remains accurate, but operational costs increase due to frequent manual interventions
Solution Approach 1:
The storage system automatically retrieves application priority metadata and determines the replication sequence without requiring user intervention. This self-service approach maintains accurate replication configuration while eliminating the operational burden of manual reconfiguration.
Solution Approach 2:
The system continuously monitors application priority metadata and automatically adjusts replication configuration based on this feedback. When priorities change or new applications are deployed, the system retrieves updated priority information and reconfigures replication accordingly, maintaining accuracy without manual intervention.
3Reliability
If volume replication is established for all applications regardless of priority, then maximum disaster recovery coverage is achieved, but IT resource efficiency decreases
Solution Approach 1:
Different replication configurations are applied to different applications based on their priority levels. High-priority applications receive full replication coverage while lower-priority applications may have reduced or no replication, optimizing IT resource utilization while maintaining adequate disaster recovery coverage for critical systems.
Solution Approach 2:
The system uses application priority as a parameter to dynamically determine replication scope and resources allocated. By changing the replication configuration parameters based on priority values, the system achieves efficient resource utilization while maintaining appropriate disaster recovery coverage for each application.
Data Source
AI summary
Example implementations described herein involve systems and methods which automatically determine volumes to be replicated for disaster recovery based on the execution priority of an application which uses the volumes. Such example implementations can involve systems and methods involving creating a volume in a first storage system for each of one or more containers newly launched on one or more servers managing a container orchestrator; and establishing replication of the volume for the each of the newly launched one or more containers to a second storage system in order from highest container priority to lowest container priority.