Rollback Recovery for Retention Locked Backup Namespaces
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Backup and restore systems face challenges in performing rollback recovery processes when data backups are in retention lock mode, as existing methods fail to efficiently manage retention locked data backups, leading to issues with data restoration and garbage collection processes.
Innovation Solution
A method that involves comparing a snapshot with the current namespace to determine which data backups are retention locked and performing a special fastcopy operation to restore only those data backups that are included in the snapshot but not in the current namespace, while extending the retention lock time of copied backups to maintain their locked state.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If retention lock mode is enabled to secure backed up data, then data security and reliability are improved, but the ability to perform rollback recovery and garbage collection is worsened
Solution Approach 1:
The patent segments the backup system into distinct components: retention locked namespaces that maintain security and unlocked namespaces that enable recovery operations. By dividing the namespace into these functional segments, the system can simultaneously maintain data security through retention locks while enabling rollback recovery by operating on unlocked copies.
Solution Approach 2:
The patent creates point-in-time copies of retention locked namespaces that are unlocked, allowing rollback operations to be performed on these copies without affecting the security of the original retained data. This copying mechanism enables recovery operations while preserving the integrity and security of the source backup data.
2Duration of action of stationary object
If retention lock time is extended to maintain data security, then data protection duration is improved, but garbage collection efficiency and storage management are worsened
Solution Approach 1:
The patent segments backup data into retention locked portions that require long-term protection and non-retention locked portions that are eligible for garbage collection. This segmentation allows the system to maintain extended retention periods for critical data while simultaneously performing garbage collection on expired or non-critical backups, thus improving overall storage management efficiency.
Solution Approach 2:
The patent applies different retention policies to different portions of backup data based on their importance and requirements. By implementing local quality differentiation where some data receives extended retention lock protection while other data follows standard retention schedules, the system optimizes both data protection duration and garbage collection efficiency across the entire backup repository.
Data Source
AI summary
One example method includes providing, during a rollback recovery process, a current namespace of a backup storage server. The current namespace includes data backups including a first set of data backups there were restored from a point-in-time copy and a second set of data backups that are retention locked. The method also includes providing, during the rollback recovery process, a recovery metadata backup of a metadata backup server including metadata backups. The method further includes performing a garbage collection optimization procedure that removes the need to disable a garbage collection procedure at the backup storage server and the metadata backup server.