Storage Virtual Machine Configuration Update Consolidation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In cluster storage environments, inefficient replication of configuration updates between primary and partner storage virtual machines leads to wastage of network bandwidth, processing resources, and CPU usage due to redundant, stale, and irrelevant updates, such as creating and subsequently deleting volumes or modifying volumes unnecessarily.
Innovation Solution
Implementing a consolidation rule system that evaluates and manages configuration updates by discarding redundant updates, modifying queued updates to achieve the same result with fewer commands, and ensuring the partner storage virtual machine reflects up-to-date configurations efficiently, thereby reducing resource wastage and optimizing failover operations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If configuration updates are replicated between primary and partner storage virtual machines, then failover recovery capability is improved, but network bandwidth and processing resources are wasted on redundant and stale updates
Solution Approach 1:
The system evaluates configuration updates before queuing them, performing preliminary analysis to determine if an update is redundant or stale. This preliminary action prevents wasteful replication of unnecessary updates while ensuring valid updates are properly queued and applied for failover capability.
Solution Approach 2:
The system discards redundant and stale configuration updates by evaluating each update against the current state of the storage virtual machine. Updates that would not change the final configuration state are identified and discarded, recovering network bandwidth and processing resources while maintaining reliable failover capability through selective replication of only necessary updates.
2Reliability
If configuration updates are queued and applied based on recovery point objectives, then data accessibility is improved, but CPU usage and processing resources increase due to redundant updates
Solution Approach 1:
The system performs preliminary evaluation of configuration updates before they are queued, analyzing whether each update is redundant or stale. This preliminary action reduces the total number of updates that need to be processed and applied, thereby reducing CPU usage and processing resource consumption while maintaining data accessibility through proper queuing and recovery point objective compliance.
Solution Approach 2:
Redundant and stale configuration updates are discarded through evaluation against the current storage virtual machine state. This discarding mechanism reduces the workload on the queuing and application processes, lowering CPU usage and processing resource requirements while ensuring that only necessary updates are queued and applied to maintain data accessibility.
3Manufacturing precision
If multiple configuration updates are processed sequentially, then configuration accuracy is maintained, but processing time increases due to redundant updates
Solution Approach 1:
The system performs preliminary evaluation of configuration updates before sequential processing, identifying and filtering out redundant and stale updates. This preliminary action reduces the total number of updates that require sequential processing, thereby reducing processing time while maintaining configuration accuracy by ensuring that only valid, non-redundant updates are processed in sequence.
Solution Approach 2:
Redundant and stale configuration updates are discarded through evaluation against the current state, reducing the number of sequential processing operations required. This discarding mechanism maintains configuration accuracy by preserving the essential update sequence while eliminating unnecessary processing steps, thereby reducing overall processing time.
Data Source
AI summary
One or more techniques and/or systems are provided for managing configuration updates used to replicate configuration of a primary storage virtual machine to a partner storage virtual machine. For example, the partner storage virtual machine may be configured to provide failover operation in place of the primary storage virtual machine in the event the primary storage virtual machine fails. Configuration updates are queued and replayed on the partner storage virtual machine to replicate objects of the primary storage virtual machine to the partner storage virtual machine (e.g., replay of create, modify, or delete object commands for synchronizing volumes, logical unit numbers, and/or other configuration objects of the primary storage virtual machine to the partner storage virtual machine). Configuration updates may be retained, modified, or discarded/removed based upon consolidation rules, which improves computing resource utilization by consolidating configuration updates and/or removing stale configuration updates while achieving a similar replication consistency result.