Rollback from Retention Locked Namespace via Fast Copy
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Backup and restore systems face challenges in implementing enhanced retention measures, leading to difficulties in configuring metadata, client, and storage servers to operate effectively, especially when data backups are in retention lock mode, which hinders rollback recovery processes.
Innovation Solution
A method that involves accessing a point-in-time copy and the current namespace to identify retention locked backups not in the current namespace, and performing a special fastcopy operation to restore these backups without removing existing retention locked backups, allowing for rollback recovery even when data backups are retention locked.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If enhanced retention measures are implemented to secure backed up data, then data security and compliance are improved, but the ability to perform rollback recovery operations deteriorates
Solution Approach 1:
The patent segments the backup storage system into multiple namespaces (source namespace and destination namespace) to isolate retention-locked data from rollback operations. This allows retention policies to be enforced on specific data segments while enabling rollback operations on other segments, resolving the contradiction between data security and recovery capability.
Solution Approach 2:
The patent introduces a Fast Copy engine as an intermediary component that bridges the gap between retention-locked backups and rollback recovery needs. This intermediary enables data to be copied and restored without directly modifying or accessing the retention-locked source data, thus maintaining both security and recoverability.
2Ease of operation
If retention locked backups are copied from point-in-time copy into current namespace, then rollback recovery is enabled, but system complexity increases
Solution Approach 1:
The Fast Copy engine operates autonomously to perform the copying of retention-locked backups from point-in-time copies to the current namespace. The system self-manages the identification, copying, and integration of backup data without requiring complex manual configuration or intervention, thereby reducing operational complexity while enabling rollback recovery.
3Manufacturing precision
If existing retention locked backups are preserved during rollback, then data integrity is maintained, but the rollback process becomes more complex
Solution Approach 1:
The patent divides the backup namespace into source and destination segments, allowing the rollback process to target only the destination namespace while leaving the source namespace (containing retention-locked backups) intact. This segmentation enables data integrity to be maintained while simplifying the rollback process through precise operational targeting.
Solution Approach 2:
The patent uses a Fast Copy mechanism to create a separate destination namespace that replicates the source namespace structure. This copying approach allows rollback operations to be performed on the copy without affecting the original retention-locked data, thereby maintaining data integrity while managing process complexity through non-destructive operations.
Data Source
AI summary
One example method includes accessing a point-in-time copy including retention locked backups that were stored on a backup storage server at a time the point-in-time copy was generated. The method further includes accessing a current namespace including retention locked backups that are currently stored on the backup storage server. Each retention locked backup includes data backup files. The method also includes determining a first set of retention locked backups that are included in the point-in-time copy, but are not included in the current namespace. The method finally includes copying the first set of retention locked backups from the point-in-time copy into the current namespace without removing any of the retention locked backups already in the current namespace.