File System Replica Snap for Non-Disruptive Backup Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data storage systems face challenges in performing backups and disaster recovery testing on replicas at destination sites due to ongoing replication activities, which are not readily accessible as they are busy updating content from source sites.
Innovation Solution
Generating a snap (point-in-time version) of the replica on a destination site that is accessible for reading and writing while replication operations continue, allowing for destination-driven backup operations and disaster recovery testing without disrupting ongoing replication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If replicas on destination sites are used for backup operations, then backup accessibility is improved, but replication consistency deteriorates because replicas are busy updating content from source sites
Solution Approach 1:
The patent segments the replica into two distinct components: the active replica that continues to receive updates from the source, and a separate snapshot object that provides a stable, accessible copy for backup operations. This segmentation allows both replication consistency and backup accessibility to coexist without interference.
Solution Approach 2:
The patent creates a snapshot copy of the replica at a specific point in time. This copy is then made accessible for backup operations while the original replica continues to update. The copying mechanism ensures that backup operations read from a consistent state without affecting ongoing replication.
2Adaptability or versatility
If replicas are made accessible for user operations, then operational versatility is improved, but replication reliability deteriorates due to potential disturbances in ongoing replication activities
Solution Approach 1:
By separating the replica into an active updating component and a user-accessible snapshot component, the patent enables operational versatility on snapshots while maintaining replication reliability on the active replica. Users can perform read/write operations on snapshots without disturbing the replication process.
Solution Approach 2:
The snapshot acts as an intermediary between users and the active replica. Users interact with the snapshot for backup and disaster recovery testing, while the active replica continues its replication duties uninterrupted. This intermediary mechanism protects replication reliability while providing operational versatility.
3Productivity
If destination sites perform backup operations on replicas, then resource utilization efficiency is improved, but system complexity increases due to managing accessible replicas during active replication
Solution Approach 1:
The snapshot mechanism provides multi-functionality: it serves as both a backup copy and a disaster recovery testbed, while the active replica continues its replication function. This universality allows destination sites to perform multiple operations without requiring additional complex infrastructure.
Solution Approach 2:
The copying mechanism creates lightweight snapshot objects that can be rapidly generated and managed. These copies enable backup operations at destination sites without requiring complex coordination or additional hardware, thus improving resource utilization while keeping system complexity manageable.
Data Source
AI summary
A technique for accessing replicas of file systems generates a snap (point-in-time version) of a replica on a destination site and provides access to the snap for reading and/or writing while replication operations on the replica between a source site and the destination site continue to be performed. As the snap is a separate object from the replica itself, users may access the snap without affecting the replica or disturbing ongoing replication activities. Users can also mount the snap to perform destination-driven backup operations, to test disaster recovery, and/or to perform other activities.