Backup Application Synchronizes Cloning via File Recovery Monitoring
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The two-step backup process for relational databases is tedious and prone to failures due to unsynchronized backup and cloning schedules, leading to incomplete or delayed creation of clone copies of backup files.
Innovation Solution
A backup application synchronizes backup and cloning schedules by determining if a backup file is stored in the file recovery area and creating a clone copy as soon as the backup file is stored, ensuring timely and successful cloning to an external destination.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a two-step backup process is used with separate backup and cloning schedules, then the backup and cloning operations can be independently configured, but the process becomes tedious and prone to failures due to unsynchronized schedules
Solution Approach 1:
The patent merges the backup and cloning schedules into a unified scheduling mechanism. The system automatically coordinates the cloning operation with the backup schedule, eliminating the need for separate independent configuration while maintaining the ability to customize backup timing. This resolves the contradiction by combining the scheduling functions to reduce administrative complexity while preserving configurability.
Solution Approach 2:
The system implements self-service by automatically detecting when backup files are stored in the file recovery area and triggering cloning operations without requiring manual intervention. The backup application monitors the file system directory and autonomously coordinates cloning timing, reducing the tedious administrative burden while maintaining operational flexibility.
2Adaptability or versatility
If manual scheduling of cloning operations is used, then flexibility in timing is provided, but the process is tedious and failure-prone due to lack of synchronization
Solution Approach 1:
The system implements feedback by continuously monitoring the file recovery area for newly stored backup files and automatically triggering cloning operations when backup completion is detected. This feedback mechanism ensures reliable synchronization between backup and cloning operations while maintaining scheduling flexibility, as the system adapts to actual backup completion times rather than relying on fixed manual schedules.
Solution Approach 2:
The system performs preliminary action by preparing the cloning mechanism in advance and automatically activating it when backup files are available in the file recovery area. This ensures that cloning operations are ready to execute immediately when backup completes, improving reliability by eliminating delays and coordination failures associated with manual scheduling.
3Ease of manufacture
If backup files are stored in a file system directory before cloning, then the backup process is simplified, but clone copies may be incomplete or delayed if cloning is not synchronized
Solution Approach 1:
The patent introduces an intermediary mechanism - the file recovery area monitoring system - that acts as a bridge between the backup file storage and cloning operations. This intermediary automatically detects when backup files are complete in the file system directory and triggers cloning only when ready, maintaining the simplicity of storing files in a directory while ensuring clone copy completeness and timeliness through automated synchronization.
Solution Approach 2:
The system replaces manual coordination mechanics with an automated electronic monitoring and triggering mechanism. Instead of requiring manual verification that backup files are ready before cloning, the system uses automated file system monitoring to detect backup completion and trigger cloning operations, maintaining simplicity while improving precision of clone copy creation timing.
Data Source
AI summary
Synchronizing backup and cloning schedules is described. A determination is made whether any session is running disk backup. A determination is made whether a backup file is stored in a file recovery area if no session is running disk backup. A determination is made whether a successful clone copy was created of the backup file if the backup file is stored in the file recovery area. A clone copy of the backup file is created if the successful clone copy was created of the backup file. The clone copy is stored on an external destination node.


