Retention Locked Replication Component for Backup Servers
Solution Overview
Problem
Existing backup and restore systems face challenges in implementing enhanced retention measures, as not all elements, such as backup servers, client servers, and storage servers, can easily be configured to operate in a retention locked mode, leading to operational issues.
Innovation Solution
The implementation of a retention locked (RL) mode compliant replication component in a data backup server configured to operate in a non-RL mode, which virtually copies backup data files from a non-RL mode to an RL mode and transfers control to an RL mode data backup server, allowing for retention locked data management without requiring all clients to be upgraded.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If enhanced retention measures are implemented in backup servers, then data security and retention compliance are improved, but system complexity and configuration difficulty increase
Solution Approach 1:
The system is divided into two distinct backup server types: retention locked mode servers that enforce security policies and non-retention locked mode servers that provide operational flexibility. This segmentation allows each server type to be optimized for its specific function, resolving the contradiction between security and complexity by distributing these roles across separate system components.
Solution Approach 2:
A replication component acts as an intermediary between non-retention locked mode backup servers and retention locked mode backup servers. This intermediary automatically replicates backup data from non-RL servers to RL servers, enabling enhanced retention measures without requiring direct configuration changes to existing backup servers, thus maintaining low system complexity while improving data security.
2Reliability
If all backup servers are upgraded to retention locked mode, then retention compliance is improved, but operational disruption and upgrade complexity increase
Solution Approach 1:
Instead of requiring all backup servers to be upgraded to retention locked mode simultaneously, the system implements retention compliance through partial action by deploying a subset of RL servers. These RL servers receive replicated data from non-RL servers, achieving retention compliance without forcing a complete system upgrade, thus maintaining operational continuity while improving retention compliance.
3Reliability
If retention locked mode is enforced across the entire backup system, then data protection is improved, but flexibility in client configuration is reduced
Solution Approach 1:
Different parts of the backup system are assigned different operational modes based on their specific functions. Non-retention locked mode servers maintain configuration flexibility for clients that require it, while retention locked mode servers provide enhanced data protection for compliant clients. This local differentiation of quality allows the system to simultaneously support both flexible and secure configurations without forcing a one-size-fits-all approach.
Data Source
AI summary
One example method includes adding a retention locked (RL) mode compliant replication component to a first data backup server that is configured to operate in a non-RL mode. The retention locked mode compliant replication component causes backup data files that are stored in a non-RL mode on a backup storage server to be virtually copied to backup data files that are stored in a RL mode on the backup storage server. The backup data files are for backup server clients that are configured to operate in the non-RL mode. The retention locked mode compliant replication component causes control of the backup data files stored in the RL mode to be given to a second data backup server that is configured to operate in the RL compliant mode.



