Asynchronous Data Backup Using Cache Memory for NAS
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Users find it troublesome and time-consuming to create backups of data every time they access it, especially when saving data in Network Attached Storage (NAS), which has a slower data access rate compared to internal storage, leading to negligence in data backup operations.
Innovation Solution
A method and apparatus that allow a computer to select a storage destination for files from multiple drives, enabling editing operations on a first drive while creating asynchronous copies of edited files on a second drive, such as a NAS, by processing tasks listed on a task list, thereby improving user operability and data access efficiency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If backup data is saved in NAS, then fault tolerance of data is improved, but data access rate deteriorates
Solution Approach 1:
The patent introduces a cache memory as an intermediary between the slow NAS storage and the fast CPU. The cache temporarily stores backup data, allowing the CPU to access data quickly without being bottlenecked by NAS's slow access rate. This resolves the contradiction by providing fast access (improving speed) while maintaining NAS as the primary backup destination (maintaining fault tolerance).
Solution Approach 2:
The patent segments the storage system into multiple layers: fast cache memory for frequent access and slow NAS for permanent backup. This segmentation allows different parts of the system to serve different purposes - cache handles speed-critical operations while NAS handles reliability-critical operations, thus resolving the speed-reliability tradeoff.
2Reliability
If manual backup operation is performed, then data is backed up, but operability deteriorates due to troublesome and time-consuming operation
Solution Approach 1:
The patent implements automatic backup functionality where the system performs backup operations without requiring manual user intervention. The backup process is triggered automatically based on file system events (e.g., when files are modified), eliminating the need for users to manually initiate backups. This resolves the contradiction by maintaining data backup reliability while dramatically improving ease of operation.
Solution Approach 2:
The system monitors file system events and automatically triggers backup operations when changes are detected. This feedback mechanism ensures that backups are performed when needed without requiring user awareness or action, thus maintaining reliability while improving operability.
3Reliability
If synchronous backup is performed, then data consistency is maintained, but productivity deteriorates due to waiting time
Solution Approach 1:
Instead of performing synchronous backup every time data is accessed (which would severely impact productivity), the system uses periodic or event-driven backup triggers. Backups are performed at specific intervals or when specific conditions are met (e.g., file system events), rather than continuously. This resolves the contradiction by maintaining data consistency through periodic updates while avoiding the productivity loss of continuous synchronous operations.
Solution Approach 2:
The system performs preliminary backup actions in the background without blocking user operations. By using asynchronous operations and cache buffering, the backup process is initiated in advance and continues without waiting for user confirmation or blocking subsequent operations, thus maintaining data consistency while preserving productivity.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method and apparatus for managing data by a computer capable of selecting a storage destination of a file from a plurality of drives including a first drive and a second drive are provided. The method includes: editing a target file in the first drive in accordance with an input from a user; listing one or more tasks as unprocessed tasks to be processed on a task list, each of the one or more tasks comprising a content of an edit applied to the target file in association with a name of the target file; and creating a copy of the target file in the second drive by sequentially processing the unprocessed tasks listed on the task list independently of a flow of editing the target file.