Namespace-Based Fixed Content Storage with Versioning
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
There is a need for highly available, reliable, and persistent data storage solutions for 'fixed content' that can replace or supplement traditional tape and optical storage, particularly in distributed computer networks, where data must be retained without change for reference or other purposes.
Innovation Solution
A content platform utilizing a redundant array of independent nodes (RAIN) is logically partitioned into tenants and namespaces, enabling versioning, retention policies, and replication across nodes, ensuring data availability and integrity through a web-based interface and distributed software application.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data is replicated across multiple nodes for high availability, then reliability is improved, but device complexity increases
Solution Approach 1:
The patent segments the storage system into independent nodes that can be individually managed, added, or removed. Each node stores portions of replicated data, allowing the system to maintain high availability through replication while managing complexity through modular segmentation. The logical partitioning into namespaces further segments data organization, making the complex replicated storage system more manageable.
2Reliability
If multiple versions of data objects are stored for versioning, then reliability is improved, but loss of substance increases
Solution Approach 1:
The patent implements versioning by creating copies of data objects with version identifiers rather than storing multiple complete versions indefinitely. The system maintains current and historical versions through controlled copying mechanisms, allowing data integrity to be preserved while managing storage consumption through selective retention and deletion of older versions.
3Ease of operation
If logical partitioning into namespaces is implemented, then ease of operation is improved, but device complexity increases
Solution Approach 1:
The patent divides the storage system into logical namespaces that partition data by function, tenant, or application. This segmentation provides ease of operation by allowing independent management of different data sets while the underlying replication and node management complexity is abstracted away through the namespace layer.
Solution Approach 2:
The namespace structure acts as an intermediary layer between users and the complex distributed storage system. It provides a simplified interface for data management while the underlying complexity of replication, node management, and data distribution is handled by the namespace abstraction layer.
Data Source
AI summary
Archive management is enhanced by logically partitioning a physical cluster. Using an interface, an administrator defines “tenants” within the cluster. A namespace is a logical partition of the cluster for a collection of objects. Each namespace has a private file system. This approach enables a user to segregate cluster data into logical partitions. Using the interface, a namespace for a tenant is configured without affecting a configuration of another namespace. One configuration option is “versioning,” by which an administrator can elect to enable multiple versions of a same data object to be stored in association with a namespace. Once versioning is enabled for a namespace, the administrator can set a configuration parameter identifying a time period for maintaining a version. Preferably, versioning is dasabled for a data object under retention.