Primary Storage Controller Virus Recovery via Secondary Query
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In storage systems, primary storage controllers face challenges in efficiently recovering from viral infections, as anti-virus scans can be time-consuming and disrupt I/O operations, and existing methods lack effective mechanisms for synchronizing data between primary and secondary storage controllers to restore infected areas.
Innovation Solution
The system employs a method where the primary storage controller queries the secondary storage controller for virus-free data, allowing for either overwriting the quarantined area or writing recovered data to a new area, while maintaining metadata to track infection history and prevent repeated queries, thus enabling efficient recovery and synchronization.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If anti-virus scans are performed on the primary storage controller, then data integrity is improved, but I/O operations are disrupted and time is lost
Solution Approach 1:
The system performs anti-virus scans on asynchronously copied data at the secondary storage controller before the primary storage controller needs to access it. This preliminary scanning ensures that when data is recovered from secondary to primary, the integrity is already verified, allowing I/O operations to continue uninterrupted on the primary controller.
Solution Approach 2:
The secondary storage controller acts as an intermediary that performs anti-virus scanning on copied data. Instead of the primary controller scanning its own data (which would disrupt I/O), the secondary controller scans copies of the data, serving as a mediator that protects data integrity without interfering with primary controller operations.
2Productivity
If data is copied asynchronously from primary to secondary storage controller, then I/O operations continue uninterrupted, but recovery from viral infections becomes more complex
Solution Approach 1:
The system implements a feedback mechanism where the primary storage controller queries the secondary storage controller to check for virus-free data before initiating recovery. This feedback loop ensures that recovery operations are only performed when necessary and when clean data is available, simplifying the overall recovery process despite the asynchronous architecture.
Solution Approach 2:
The system maintains simplified recovery by relying on the existing copy mechanism. When viral infection is detected on the primary controller, the system simply copies clean data back from the secondary controller to the primary controller, leveraging the already-established asynchronous copy infrastructure rather than requiring complex recovery procedures.
3Measurement precision
If the primary storage controller queries the secondary storage controller for virus-free data, then recovery accuracy is improved, but communication overhead increases
Solution Approach 1:
Instead of continuously monitoring or pre-verifying all data on the secondary controller, the system performs partial verification only when needed - specifically when the primary controller detects viral infection and needs to recover data. This on-demand querying approach balances accuracy with time efficiency, avoiding excessive communication overhead while ensuring recovery accuracy when required.
Data Source
AI summary
A primary storage controller determines that a quarantined area of the primary storage controller cannot be repaired, wherein the quarantined area is infected with a virus. A query is sent to a secondary storage controller to determine whether the secondary storage controller has data that is free of virus in an area of the secondary storage controller corresponding to the quarantined area of the primary storage controller. In response to receiving a notification that the secondary storage controller has data that is free of virus, the primary storage controller is repaired to remove the virus.