Replicated Storage Key Access Management With Staged Unavailability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In replicated storage systems, when encryption keys become inaccessible, replication instances become inconsistent, leading to accumulation of unmanageable replication logs and potential data loss due to inconsistent replication instances.
Innovation Solution
An instance manager schedules replication instances to become unavailable after a threshold time if the encryption key remains inaccessible, allowing for a controlled shutdown and preventing data inconsistency by ensuring only accessible keys are used for updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the first replication instance remains available while its encryption key is inaccessible, then data access continuity is maintained, but data inconsistency and replication log accumulation occur
Solution Approach 1:
The system proactively schedules the second replication instance to become unavailable before the first instance is actually made unavailable, creating a preliminary protective measure. This preemptive scheduling prevents potential data inconsistency by ensuring that a backup replication instance is ready in advance, so that when the first instance becomes unavailable due to key issues, the system can smoothly transition to the second instance without data loss or inconsistency.
Solution Approach 2:
The system creates a cushioning mechanism by scheduling the second replication instance to be unavailable in advance, creating a buffer period. This cushioning allows the system to monitor key accessibility and make controlled transitions between replication instances, preventing sudden data inconsistency while maintaining access continuity through the staged unavailability approach.
2Loss of information
If the first replication instance is immediately set as unavailable when the encryption key becomes inaccessible, then data consistency is maintained, but data access continuity is disrupted
Solution Approach 1:
The system schedules the second replication instance to become unavailable in advance, creating a preparatory state that allows for controlled transitions. This preliminary scheduling ensures that when the first replication instance needs to be made unavailable, the system has already prepared the second instance, allowing for a smoother transition that maintains data access continuity while preserving consistency.
Solution Approach 2:
The system implements dynamic availability management by allowing the first replication instance to remain available temporarily even after its encryption key becomes inaccessible. The staged approach dynamically adjusts the availability state of replication instances based on monitored key accessibility, allowing the system to adapt between maintaining access continuity and ensuring data consistency based on current conditions.
3Reliability
If multiple replication instances are kept available with different encryption keys, then data access continuity is improved, but system complexity increases
Solution Approach 1:
The system segments the replication instance management into distinct phases: the first replication instance handles initial data access, while the second replication instance is scheduled to become unavailable in advance as a preparatory measure. This segmentation allows the system to manage multiple encryption keys and replication instances in a structured manner, reducing the operational complexity of handling multiple available instances while maintaining data access continuity through the staged transition approach.
Data Source
AI summary
A method includes obtaining a key status for a first cryptographic key. The first cryptographic key is used to encrypt replicated data of a first replication instance. The method also includes determining, based on the key status, that the first cryptographic key is inaccessible which causes the first replication instance to be unavailable. In response to determining that the first cryptographic key is inaccessible, the method includes scheduling a second replication instance to be unavailable after a threshold amount of time has passed. The second replication instance includes replicated data encrypted by a second cryptographic key that is accessible. After the threshold amount of time has passed and when the first cryptographic key is still inaccessible, the method includes setting the second replication instance as unavailable.