Interrupt Service Routine for Uninterrupted Data Restore
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data transfer methods for restoring large datasets are inefficient, as they require restarting from the beginning after unexpected abort events, leading to potential data corruption and failure to meet service level agreements due to interruptions from events like power outages or network failures.
Innovation Solution
Implementing a method that uses a parent interrupt service routine to poll for abort events, writing data to a conditional construction container, and generating re-entrant child ISRs to save and restore the state of the restore process, allowing for resumed data transfer from the point of interruption without restarting from the beginning.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data transfer is restarted from the beginning after an abort event, then data integrity is maintained, but transfer time increases and service level agreements may be violated
Solution Approach 1:
The patent implements preliminary actions by continuously polling for abort events during the data transfer process and saving the current transfer state before interruption occurs. This allows the system to resume from the saved state rather than restarting from the beginning, reducing transfer time while maintaining data integrity through state validation mechanisms.
Solution Approach 2:
The patent employs feedback mechanisms through the parent interrupt service routine that continuously monitors for abort events and triggers state saving. The system uses feedback loops to detect interruptions, save progress, and resume transfers only when the abort condition is resolved, ensuring data integrity while minimizing time loss.
2Reliability
If data transfer is restarted from the beginning after an abort event, then complete data restoration is ensured, but productivity decreases due to repeated transfers
Solution Approach 1:
The system performs preliminary state saving during the data transfer process, capturing the exact point of interruption. When an abort event occurs, the system resumes from this pre-saved state rather than restarting the entire transfer, significantly improving restore operation efficiency while ensuring complete data restoration through validation checks.
Solution Approach 2:
The patent implements discarding and recovering by abandoning the restarted transfer portion and recovering only the essential state information needed to resume. The parent interrupt service routine saves critical transfer state, and upon resumption, the system discards redundant re-transmission of already transferred data, improving productivity while maintaining restoration completeness.
3Reliability
If multiple abort events occur during data transfer, then system resilience is tested, but service level agreement compliance deteriorates
Solution Approach 1:
The patent ensures continuity of useful action by implementing a parent interrupt service routine that continuously polls for abort events and saves transfer state without interruption to the overall transfer process. When multiple abort events occur, the system maintains continuous progress by resuming from the most recent saved state, reducing time loss and improving SLA compliance while demonstrating system resilience.
Solution Approach 2:
The system uses feedback loops to detect multiple abort events and trigger state saving at each interruption point. The parent interrupt service routine provides continuous feedback on transfer status and abort conditions, enabling the system to resume operations quickly after multiple interruptions and maintain SLA compliance while demonstrating resilience to repeated failures.
Data Source
AI summary
Embodiments are described for performing an uninterrupted restore in a storage system in view of one or more abort events. A restore agent receives writes one or more data blocks to a conditional construction container. A parent interrupt service routine (ISR) polls for abort events. In response to an abort event, an intermediate interrupt is generated that spawns a child processes for each process of the restore. The intermediate ISR logs each child ISR, the process it is responsible for, and the intermediate interrupt, for later restoration of the restore state. After a recovery of the above event, then each child ISR can be called to restore its state. After restoring the state, the restore agent resumes the restore from where the abort event was detected. The child ISRs are re-entrant. If another abort event is detected, the restore state can again be saved and later resumed from that state.