Snapshot Data Backup Without Application Downtime
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional data backup techniques require service interruption and lack mechanisms for identifying problematic steps during the backup process, especially for mission-critical systems, and fail to perform fast online consistent image-level backups for storage hard disks.
Innovation Solution
The method involves capturing a snapshot of data without application downtime by setting a database to backup mode, caching I/O operations for GPFS systems, and copying the snapshot to media while allowing applications to run, enabling asynchronous data backup and real-time status monitoring.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional backup techniques are used, then data backup is achieved, but service interruption occurs and applications must be taken down
Solution Approach 1:
The patent applies preliminary action by capturing a snapshot of data at a specific point in time before the backup process begins. This snapshot represents a consistent state of the data that can be backed up without requiring the application to be stopped, thus maintaining application availability while ensuring data backup reliability
Solution Approach 2:
The patent uses copying by creating a snapshot copy of the data at a specific moment in time. This snapshot is then used for the backup process, allowing the original application to continue running while the copy is being backed up, eliminating service interruption
2Productivity
If conventional backup techniques are used, then backup process is completed, but mechanisms for identifying problematic steps are lacking
Solution Approach 1:
The patent implements feedback by providing notifications to users about the status of the backup process and any problems that occur. The system monitors the backup process and communicates back to users, enabling them to identify problematic steps without difficulty
3Speed
If snapshot copying is performed, then fast online consistent backup is achieved, but service interruption may occur during copying
Solution Approach 1:
The patent applies preliminary action by capturing the snapshot before the actual backup copying begins. This snapshot represents a consistent state that can be copied at high speed without requiring service interruption during the copying process, as the data is already in a stable, frozen state
Solution Approach 2:
The patent uses copying by creating a snapshot copy of the data at a specific moment in time. This snapshot is then used for the backup process, allowing the original application to continue running while the copy is being backed up, eliminating service interruption
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A computer-implemented method includes the following. A start time for a backup of data in a system is received. At the start time, a snapshot of the data in the system is captured. When an environment of the system is a database environment, the capturing includes setting a status of a database to backup mode and freezing data files in the database while permitting applications to run. When the environment of the system is a non-database environment, and when a file system type is general parallel file system (GPFS), the capturing includes caching new input/output operations to a cache and starting a timer (counter) for flushing the cache. At a specified time, the snapshot is copied to media, setting the status of the database to normal mode, and providing copying notifications to users.