Point-in-Time Copy Restore via Repository Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current point-in-time copy techniques in storage environments fail to efficiently restore data to a specific point-in-time different from the full copy, as they require data transfers and impact system performance, and lack independent management of restore operations.
Innovation Solution
A computer program product and method that create a restore copy from a full copy of source data in a repository, using separate repository and storage controller components to manage point-in-time copies and change information, allowing data restoration at different point-in-times without impacting system performance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If point-in-time copy techniques are used to restore data to a specific point-in-time different from the full copy, then data restoration capability is improved, but system performance is impacted due to data transfers
Solution Approach 1:
The system segments restore operations from storage controller logic by introducing a separate repository component. The storage controller creates point-in-time copies and manages change information, while the repository handles restore operations independently. This segmentation eliminates performance impact on the storage controller during restore operations while maintaining full restore capability to any point-in-time.
Solution Approach 2:
The system performs preliminary actions by creating and maintaining a repository of full copies and change information in advance. When a restore request arrives, the system can immediately retrieve pre-prepared data from the repository without performing data transfers during the restore operation, thus avoiding performance impact.
2Ease of operation
If restore operations are managed by storage controller logic, then integration is improved, but system reliability is reduced due to single point of failure
Solution Approach 1:
The system divides the restore management function into two independent components: the storage controller that creates and manages point-in-time copies, and the repository that stores full copies and change information. This segmentation creates redundancy and eliminates single points of failure, as either component can be restored or replaced independently while maintaining system functionality.
Solution Approach 2:
The repository acts as an intermediary between the storage controller and restore operations. It receives and stores change information from the storage controller, then independently provides data for restore operations. This intermediary structure improves reliability by decoupling the system components while maintaining their collaborative function.
3Manufacturing precision
If data transfers are performed during restore operations to achieve specific point-in-time restoration, then restoration precision is improved, but operation time is increased
Solution Approach 1:
The system performs preliminary actions by pre-computing and storing change information that tracks data modifications between point-in-times. When restoration is needed, the system retrieves pre-prepared data from the repository using change information, eliminating the need for time-consuming data transfers during the restore operation while maintaining precise point-in-time restoration.
Solution Approach 2:
The system uses copying by maintaining a repository that contains full copies of data at different point-in-times along with change information. Instead of transferring data during restore operations, the system copies pre-prepared data from the repository, significantly reducing operation time while preserving restoration precision through the use of change information to identify the correct data state.
Data Source
AI summary
Provided are a computer program product, system, and method for creating a restore copy from a copy of a full copy of source data in a repository that is at a different point-in-time than a restore point-in-time of a restore request. A repository has a full copy of source data as of a full copy point-in-time and for each of a plurality of point-in-time copies at different point-in-times of the source data, change information indicating changed data in the source data that changed between the point-in-time of the point-in-time copy and a subsequent point-in-time, and changed point-in-time data comprising data in the source data as of the point-in-time of the point-in-time copy indicated in the change information as changed. A point-in-time copy of the full copy is created in response to a restore request and returned as a restore copy to the restore request.