Registry Writer Snapshot Backup for Bare Metal Recovery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current backup systems face challenges in efficiently performing incremental backups of bare metal recovery (BMR) and system state recovery (SSR) objects due to the complexity and interdependencies of system data, leading to increased storage costs and backup times, as well as limitations in accurately reporting system asset sizes and user experience issues during restoration.
Innovation Solution
The implementation of automated backup recovery techniques in a distributed system that includes a data protection backup management server, data protection agents, and a storage system, which utilize snapshot technology and the Volume Shadow Copy Service (VSS) to facilitate incremental backups, dynamic discovery of new writers, and secure in-memory agent service simulation for BMR restores, while accurately sizing disaster recovery assets.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If full backups are performed for BMR and SSR objects, then data protection is ensured, but storage costs and backup time increase significantly
Solution Approach 1:
The backup system segments BMR and SSR backup objects into multiple components (system state data, boot volume data, system volume data) that can be independently identified and backed up. This segmentation enables incremental backups of specific components rather than requiring full system backups, reducing backup time while maintaining data protection.
Solution Approach 2:
The system implements periodic incremental backups that capture only changes since the last backup, rather than performing repeated full backups. This periodic action on changed data reduces backup time and storage costs while ensuring data protection through regular updates of critical system components.
2Reliability
If full backups are performed for BMR and SSR objects, then data protection is ensured, but storage costs increase
Solution Approach 1:
The system extracts and identifies specific BMR and SSR objects (registry hives, system state files, boot and system volume data) from the overall system data. By taking out only these critical system components for targeted backup, the system reduces storage requirements while maintaining protection of essential recovery elements.
Solution Approach 2:
The system discards redundant data in full backups by implementing incremental backup mechanisms that only capture changed blocks. Previous backup versions are recovered and combined with incremental changes, reducing storage costs while maintaining data protection through versioned recovery capability.
3Object-affected harmful factors
If manual network configuration is required during BMR restore, then security control is maintained, but user experience deteriorates
Solution Approach 1:
The system performs preliminary actions by automatically configuring network settings during the BMR restore process before the user needs to manually intervene. Network parameters are pre-configured based on the restored system's requirements, maintaining security controls while eliminating manual configuration steps and improving user experience.
4Device complexity
If backup products lack support for incremental BMR or SSR backups, then simple backup implementation is maintained, but productivity decreases
Solution Approach 1:
The system introduces an intermediary component that bridges the gap between simple backup implementation and incremental backup capability. This intermediary layer manages the complexity of identifying, tracking, and backing up only changed BMR and SSR objects, enabling incremental backups without requiring complete redesign of the backup product architecture.
Data Source
AI summary
A registry writer is instructed via a copy service on a host to prepare for generation of a snapshot. The registry writer is responsible for saving system hive files to disk before the snapshot is generated. A reporting of the system hive files is received from the registry writer. Communications are exchanged with an API exposed by an operating system of the host to identify user hive files. The system hive files reported by the registry writer and the user hive files identified using the API exposed by the operating system are backed up from the snapshot to secondary storage.