Unified Backup Methodology for Multi-Volume Data Protection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing backup systems face challenges in efficiently protecting data for applications that span multiple volumes, as they either waste storage space by using volume-level backups for all volumes or duplicate data when using file-by-file backups, failing to balance storage efficiency and granular recovery needs.
Innovation Solution
A computer system that performs file-by-file backups for specific application files on one volume and volume image backups for another volume, storing metadata for application-specific references to enable efficient restoration, allowing for granular recovery while minimizing storage waste.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If volume-level backup is performed for all volumes, then restoration speed is improved, but storage space is wasted by backing up data that does not need protection
Solution Approach 1:
The backup system segments the backup approach by volume type: application volumes use file-by-file backup while non-application volumes use volume-level backup. This segmentation allows each volume type to receive the appropriate backup method, avoiding the waste of backing up entire volumes when only specific files need protection.
Solution Approach 2:
Different backup qualities are applied to different volumes based on their content. Application volumes receive granular file-level backup for precise control, while non-application volumes receive full volume backup for rapid restoration. This local quality differentiation optimizes both storage efficiency and restoration performance for each volume type.
2Loss of substance
If file-by-file backup is performed for application files, then storage space is saved, but restoration time increases due to manual file selection
Solution Approach 1:
The system performs preliminary organization of backup files by creating a structured backup dataset that groups files by application and volume. This preliminary organization enables automated restoration processes to quickly locate and restore needed files without manual browsing, significantly reducing restoration time while maintaining file-by-file backup efficiency.
Solution Approach 2:
The patent introduces an intermediary backup dataset structure that sits between the source files and the restoration process. This intermediary structure organizes files with metadata that enables automated restoration, acting as a mediator that preserves storage efficiency while eliminating the need for manual file selection during restoration.
3Adaptability or versatility
If file-by-file backup is performed for application files across multiple volumes, then granular recovery is enabled, but data duplication occurs when also performing volume-level backup
Solution Approach 1:
The system segments the backup scope by identifying which volumes contain application data and which do not. Only application volumes undergo file-by-file backup, while non-application volumes receive volume-level backup. This segmentation eliminates duplicate backups of the same data while preserving granular recovery capability for applications.
Solution Approach 2:
The backup system dynamically adapts its approach based on volume content analysis. By dynamically determining whether a volume contains application data, the system applies the appropriate backup method, avoiding static application of a single backup strategy to all volumes and thereby preventing unnecessary duplication.
Data Source
AI summary
A computer system and methods. The computer system includes a host that hosts applications and includes storage volumes. The host identifies an application and associated first files to be protected. The first files are stored on a first volume. The host performs a file-by-file backup of the first files to a first backup medium. The host identifies a second volume to be protected and performs a volume image backup of the second volume to a second backup medium. The host identifies second files that are associated with the identified application and stored on the second volume and stores metadata in a third backup medium including application-specific references to data objects that correspond to the second files. Third files not associated with the identified application are stored on the first volume and not included in the file-by-file backup. The second files are not included in the file-by-file backup.