Partitioned Content Platform Tenant Replication

Resolve Bottlenecks,
Find Innovative Solutions
Generate 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, allowing for segregation of data into logical partitions, with replication across multiple nodes to ensure availability and reliability, and a replication algorithm that enables adding tenants to a replication link without stalling other data transfers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data is replicated across multiple nodes in a RAIN storage system, then reliability and availability are improved, but system complexity and management difficulty increase

Engineering Contradiction:
Improvedata reliabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the storage system into independent nodes that can be individually managed, added, or removed without affecting the entire system. Each node maintains portions of the replicated data, allowing the system to scale while maintaining reliability through distributed storage and replication across these segmented units.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If nodes are allowed to join and exit the cluster dynamically, then system adaptability is improved, but data consistency and replication management become more difficult

Engineering Contradiction:
Improvesystem adaptabilityVSAvoiddata consistency
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent implements dynamic node management where nodes can join and exit the cluster without manual reconfiguration. The system automatically adjusts replication patterns and data distribution when nodes are added or removed, maintaining data consistency through automated replication protocols that adapt to changing cluster topology in real-time.

Inventive Principle:
Principle #15Dynamics

3Reliability

If multiple tenants are replicated across clusters, then data availability is improved, but replication management complexity and resource consumption increase

Engineering Contradiction:
Improvedata availabilityVSAvoidreplication efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent creates a universal replication mechanism that handles multiple tenants across clusters through a single standardized process. The replication system is designed to manage diverse tenant data types and access patterns uniformly, reducing the need for tenant-specific replication configurations and improving overall replication efficiency through consolidated resource utilization.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS9727627B2Fixed content storage within a partitioned content platform, with replication
Publication Date: 2017.08.08 HITACHI VANTARA LLC
  • US9727627B2 patent drawing
  • US9727627B2 patent drawing
  • US9727627B2 patent drawing

AI summary

A content platform cluster that comprises an array of nodes is logically partitioned. Using a web-based interface, an administrator defines “tenants” within the cluster, wherein a tenant has a set of attributes: namespaces, administrative accounts, data access accounts, and a permission mask. A namespace is a logical partition of the cluster that serves as a collection of objects typically associated with at least one defined application. Each namespace has a private file system with respect to other namespaces. This approach enables a user to segregate cluster data into logical partitions. Tenant information, including all associated namespaces, in the cluster (the “source cluster”) is replicated to at least one target cluster over a replication link. Preferably, replication is available for multiple tenants in the source cluster, and a replication algorithm ensures that a particular tenant can be added to the replication link without stalling the progress of other tenants.