Read-Only Storage Container Status for DR Testing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional cloud-based data storage systems lack effective solutions to preserve data without causing business interruptions and provide a safe, affordable mechanism for disaster recovery (DR) testing, as snapshotting in cloud storage is time-consuming and costly, and managing legal holds is complex, introducing security risks and potential mistakes.
Innovation Solution
A method that sets a storage container to a read-only status to preserve its state, redirecting write operations to another container, allowing read operations while maintaining data integrity for testing purposes, and optionally using cascading redirections across multiple containers for enhanced safety and efficiency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If snapshots are used for DR testing in cloud storage, then testing capability is provided, but time consumption and cost increase
Solution Approach 1:
The system pre-establishes a read-only status mechanism and redirect rules before DR testing is needed. When testing is required, the production storage container is automatically set to read-only status and write operations are redirected to a test container, eliminating the need for time-consuming snapshotting operations while enabling immediate DR testing capability.
2Reliability
If read-only status is set on storage container, then data integrity is preserved for testing, but write operations are blocked
Solution Approach 1:
A test storage container acts as an intermediary between the read-only production container and the write operations. When read-only status is set on the production container, write operations are automatically redirected to the test container, which accepts modifications. This intermediary mechanism preserves data integrity on the production container while maintaining write operation capability through the test container.
3Ease of manufacture
If manual cleanup of test data is performed in cloud storage, then test data can be removed, but security risks and errors increase
Solution Approach 1:
The system automatically manages test data cleanup through its built-in mechanisms. When the read-only status is withdrawn from the production container, the system automatically redirects subsequent write operations to the production container, overwriting test data. This self-service mechanism eliminates the need for manual intervention, reducing security risks and operational errors while maintaining effective test data cleanup capability.
4Productivity
If production systems continue operating during DR testing, then business continuity is maintained, but data operations may be interrupted
Solution Approach 1:
The storage system is segmented into production and test containers with distinct access paths. By setting read-only status on the production container and redirecting writes to the test container, the system segments data operations during DR testing. This segmentation allows production systems to continue operating normally while test operations proceed independently on the test container, maintaining both business continuity and data operation reliability.
Data Source
AI summary
A computer-implemented method according to one approach includes receiving requests to perform data operations on a first storage container, where the data operations include a read operation and a write operation. It is determined whether first data stored on the first storage container is set to a read-only status. In response to determining that the first data is set to the read-only status, the read operation is allowed to be performed on the first container for reading the first data, and the write operation is performed on a second storage container. Moreover, in response to determining that the first data is set to the read-only status, it is determined whether the read-only status has been withdrawn. In response to determining that the read-only status has been withdrawn, further write operations are allowed to be performed on the first storage container.