Offsite Backup Snapshot Using Reference Copying
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The increasing complexity and geographical dispersion of data processing systems, such as those using No-SQL databases like Cassandra, pose challenges in effectively backing up and restoring data across multiple nodes, especially when data is spread across various locations, requiring a solution that addresses these challenges efficiently.
Innovation Solution
A system and method for backing up a node to an offsite location, restoring it, and cloning it to a specific point-in-time, by copying references to data files rather than duplicating them, and utilizing commit logs to recreate data files, allowing for efficient data management and recovery across networks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data is backed up by copying all data files from the node to the offsite location, then data durability is improved, but data transfer time and storage space are worsened due to redundant copying of unchanged files
Solution Approach 1:
The patent extracts only the changed data files from the backup snapshot, rather than copying all files. The system identifies which files have been modified since the last backup and transfers only those specific files to the offsite location, eliminating redundant data transfer while maintaining complete backup capability.
Solution Approach 2:
The patent creates an asymmetric backup structure where the backup snapshot metadata stores references to data files, and the data files themselves are stored separately. This allows the system to efficiently track which files have changed and only transfer the necessary portions, rather than treating all files symmetrically.
2Reliability
If all data files are copied to the offsite location for backup, then data completeness is improved, but storage space at the offsite location is worsened due to duplication
Solution Approach 1:
The system extracts and stores only the changed data files in the backup snapshot, rather than duplicating all files. By identifying and transferring only the modified files, the patent reduces offsite storage requirements while maintaining the ability to restore complete data states.
Solution Approach 2:
The patent uses a reference-based copying mechanism where the backup snapshot stores metadata references to data files rather than duplicating the actual file contents. This allows the system to maintain data completeness through references while minimizing actual data duplication at the offsite location.
3Adaptability or versatility
If commit logs are retained and used for restoration, then point-in-time recovery capability is improved, but system complexity is worsened due to additional log management
Solution Approach 1:
The patent merges the commit log management with the existing backup snapshot mechanism. Rather than treating commit logs as a separate complex subsystem, the system integrates log retention and utilization into the snapshot creation and restoration processes, simplifying overall management while enabling point-in-time recovery.
Solution Approach 2:
The system performs preliminary actions by retaining commit logs alongside backup snapshots. By keeping the logs available before restoration is needed, the system enables efficient point-in-time recovery without requiring complex real-time analysis or reconstruction during the restoration process.
Data Source
AI summary
Various operations, functionalities and systems are described herein for backing up one or more node to an offsite location, restoring the one or more node from the offsite location, restoring the one or more node to a point-in-time (PIT) from the offsite location, cloning the one or more node from the offsite location, and cloning the one or more node to a PIT from the offsite location. Example operating contexts include one or more cluster of nodes running a NoSQL (Not only Structured Query Language) distributed database and backup, restore and/or cloning on those one or more cluster of nodes.