Storage Repository Space Management During Data Resynchronization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current data mirroring systems face inefficiencies in space usage during logical copy operations, as they often require full secondary storage space for updates, which is not fully utilized due to the difference in data volume between source and target volumes during the copy process.
Innovation Solution
A method and system that determine whether to use a repository or a third storage equal in size to the secondary storage for storing data updates during resynchronization, based on available space, allowing for efficient allocation of storage resources by transferring writes to a repository when sufficient space is available and using the third storage when it is not, thereby minimizing storage requirements.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If a repository is used to store data updates during resynchronization, then storage space is reduced, but data integrity may be compromised if repository space is insufficient
Solution Approach 1:
The system dynamically determines whether to use repository or third storage based on available space conditions. The storage allocation is not fixed but adapts to current repository space availability, allowing the system to optimize between space efficiency and data integrity by switching storage paths as needed
Solution Approach 2:
The system introduces an intermediary decision-making mechanism that evaluates repository space availability before determining storage allocation. This intermediary assessment layer ensures that data integrity is maintained by preventing repository overflow while still allowing space-efficient storage when conditions permit
2Reliability
If full secondary storage space is allocated for updates, then data integrity is ensured, but storage efficiency is reduced due to unused space
Solution Approach 1:
The system changes the storage allocation parameter dynamically based on repository space conditions. When repository space is sufficient, it uses repository storage (higher efficiency); when insufficient, it switches to third storage (full capacity). This parameter adjustment resolves the contradiction by adapting storage allocation to current conditions
Solution Approach 2:
The storage allocation transitions from a static full-capacity approach to a dynamic system that adjusts between repository and third storage based on real-time space availability, achieving both data integrity and storage efficiency through conditional adaptation
3Reliability
If repository space is monitored and switching to third storage is implemented, then data integrity is maintained, but system complexity increases
Solution Approach 1:
The system performs self-service by automatically monitoring repository space and making its own decision about whether to use repository or third storage. This eliminates the need for complex external control mechanisms while maintaining data integrity through autonomous space management
Solution Approach 2:
The system implements a simple feedback loop where repository space availability is continuously monitored and feeds into the storage allocation decision. This feedback mechanism maintains data integrity through a straightforward conditional check rather than complex control logic
Data Source
Figure 1
Figure 2~3
Figure 4~5
AI summary
Provided are a method, system, and a computer program product for determining whether to use a repository to store data updated during a resynchronization. Writes to a primary storage are transferred to a secondary storage. A logical copy of the secondary storage as of a point-in-time is established. Writes to the secondary storage in the logical copy received from the primary storage during a logical copy duration after the point-in-time are stored in a repository that comprises less storage space than the secondary storage in the logical copy. The transferring of writes to the secondary storage is suspended. During the suspension writes to the primary storage are indicated in an out-of-synch data structure. A determination is made as to whether available storage space in the repository is sufficient to store writes transferred from the secondary storage while transferring the writes from the out-of-synch data structure in response to ending the suspension of the transferring of writes from the primary to the secondary storages. The repository is used to store data in the secondary storage as of the point-in-time that is to be updated by writes transferred from the primary storage following the ending of the suspension in response to determining that the available storage space in the repository is sufficient to store writes transferred from the secondary storage while transferring the writes indicated in the out-of-synch data structure.