Expandable Storage Volume Replication via Unified Namespace
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional network storage systems lack flexibility in accessing data across multiple protocols and storage volumes, requiring path name updates when files are moved, which limits system flexibility and scalability.
Innovation Solution
A method and system for generating a disaster recovery copy of an expandable storage volume using a unified namespace, allowing data objects to be stored across different storage volumes, with snapshot replication and configuration information transfer between locations, enabling seamless access and migration of data objects without changing their paths.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional network storage systems use path names mapped to specific volumes and file locations, then data access is straightforward, but system flexibility deteriorates when files need to be moved to different storage volumes
Solution Approach 1:
The patent introduces a namespace as an intermediary layer between the file system and physical storage volumes. The namespace contains directory entries that map path names to global object IDs, which in turn map to actual data locations. This mediator allows files to be moved between volumes without changing their path names, as the namespace layer handles the mapping dynamically.
Solution Approach 2:
The patent creates a copy of the namespace and directory structure at the destination volume during replication. This copy includes updated mappings that allow clients to access replicated data through the same path names, enabling seamless failover and flexibility without requiring clients to update their path references.
2Ease of operation
If traditional storage systems require path name updates when files are moved, then storage location tracking is simple, but scalability and ease of operation deteriorate
Solution Approach 1:
The global object ID serves as an intermediary that decouples the path name from the physical storage location. When files are moved, only the mapping in the namespace and global object ID structure needs to be updated, not the path names themselves. This maintains path name consistency while enabling easy file migration.
Solution Approach 2:
During replication, the namespace and directory entries are copied to the destination volume with updated mappings. This ensures that path names remain consistent across the system while the underlying storage locations are replicated, allowing seamless file access regardless of physical location.
3Adaptability or versatility
If network storage systems support multiple access protocols, then client accessibility is improved, but system complexity increases due to requiring different storage mechanisms for each protocol
Solution Approach 1:
The patent implements a universal namespace and global object ID system that serves multiple access protocols simultaneously. The same namespace structure and mapping mechanism work for both file-level (NFS) and block-level (iSCSI) access, eliminating the need for separate storage mechanisms for each protocol and reducing overall system complexity.
Solution Approach 2:
The namespace and global object ID structure act as a universal intermediary layer that translates requests from different protocols into unified storage operations. This mediator allows multiple protocols to access the same data objects without requiring duplicate storage mechanisms, simplifying the system architecture.
4Adaptability or versatility
If storage volumes are expanded or migrated, then storage capacity and flexibility are improved, but data access reliability may deteriorate during transition
Solution Approach 1:
The patent performs preliminary actions by creating snapshots of the source volume and pre-configuring the destination volume with the namespace and mapping structures before actual data migration. This ensures that data access reliability is maintained throughout the transition, as the destination is prepared in advance to handle requests seamlessly.
Solution Approach 2:
The namespace, directory entries, and global object ID mappings are copied to the destination volume before data migration. This preliminary copying ensures that once data is transferred, access reliability is immediately restored without interruption, as the mapping infrastructure is already in place at the destination.
Data Source
AI summary
Machine implemented method and system for generating a disaster recovery copy of an expandable storage volume having a namespace for storing information for accessing data objects stored at a data constituent volume is provided. A transfer operation for transferring a point in time copy of the expandable storage volume from a first location to a second location is generated. Information regarding the expandable storage volume from the first location is retrieved and a destination expandable storage volume is resized to match components of the expandable storage volume at the first location. Thereafter, the point in time copy of the expandable storage volume from the first location to the second location is transferred and configuration information regarding the point in time copy is copied from the first location to the second location; a data structure for storing information regarding the transferred point in time copy of the expandable storage volume is updated.