Automated Core File Upload for Storage Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for troubleshooting storage servers, such as uploading core files after a kernel panic, are manual, time-consuming, and prone to interruptions due to the large file sizes and lack of resiliency in transfer protocols, leading to significant delays in diagnosing and fixing errors.
Innovation Solution
An automated system that processes error messages from remote storage systems to determine the type of error and, if unknown, automatically requests and securely uploads core files in chunks, ensuring resumption from the last successful transfer point, reducing the need for manual intervention and minimizing transfer time.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If core files are manually uploaded using simple protocols (ftp, http, https), then the upload process can be initiated, but the transfer lacks resiliency and requires manual reinitiation upon connectivity loss, significantly increasing transfer time
Solution Approach 1:
The patent segments the core file into multiple chunks for transmission. Each chunk can be independently transferred and tracked, allowing the system to resume transmission from the last successfully received chunk rather than restarting the entire file transfer when connectivity is lost. This segmentation enables automatic retry mechanisms and significantly improves transfer resiliency.
2Ease of operation
If core files are manually uploaded, then customer intervention is required to initiate and manage the transfer, but this introduces significant delays in engaging customer contacts and starting the upload process
Solution Approach 1:
The patent implements an automated support system where the storage system automatically detects errors, generates core files, and initiates uploads to the support center without requiring customer intervention. The system self-manages the entire process including error detection, core file generation, and transfer initiation, eliminating delays associated with manual customer engagement.
Solution Approach 2:
The patent enables preliminary automated actions to be taken when errors are detected. The storage system automatically generates core files and prepares them for upload immediately upon error detection, before any manual intervention is needed. This preliminary automation significantly reduces the time from error occurrence to support center receipt of diagnostic data.
3Reliability
If core files are transferred using secure methods, then data security is maintained, but the transfer process takes a significant amount of time (up to two days)
Solution Approach 1:
By dividing the large core file into smaller chunks, the system can efficiently manage secure transfers. Each chunk can be transferred independently with proper authentication and encryption, allowing for better error handling and resumption capabilities while maintaining security standards. This segmentation optimizes the balance between security requirements and transfer efficiency.
4Reliability
If the core file upload is interrupted due to connectivity loss, then the transfer must be manually reinitiated, but without a guarantee that it can be resumed from the last uploaded portion
Solution Approach 1:
The core file is divided into multiple numbered chunks that are transferred sequentially. The system tracks which chunks have been successfully received and can automatically resume transmission from the next missing chunk rather than restarting the entire file. This chunking mechanism guarantees transfer completeness while minimizing retransfer time upon connectivity restoration.
Solution Approach 2:
The patent implements a feedback mechanism where the support center acknowledges receipt of each transmitted chunk. The storage system uses this feedback to track transmission status and automatically manage retries for missing chunks. This feedback loop ensures complete and reliable file transfer even in the presence of intermittent connectivity issues.
Data Source
AI summary
A support center receives an error message from a remote storage system indicating that an error, such as a kernel panic, has occurred on the remote storage system. The error message is processed to determine the type of error, whether the type of error is known and whether a solution is known for the type of error. If the type of error is unknown, a core file upload request is automatically generated and sent to the remote storage system.