WORM State Provisioning via Volume-Level Identifiers

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing WORM storage systems require separate aggregates for each type of implementation, leading to inefficient utilization of storage devices and potential capacity issues due to RAID overhead, as a minimum of three storage devices are often needed for RAID 6 configurations.

Innovation Solution

Decoupling the WORM states between aggregates and volumes by using distinct identifiers for each, allowing different types of WORM states to be provisioned within a single aggregate, thereby eliminating the need for separate aggregates and enabling efficient device utilization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If separate aggregates are created for each type of WORM storage implementation, then the system can provide different WORM states, but the utilization of storage devices becomes inefficient

Engineering Contradiction:

Improveability to provide different WORM statesVSAvoidutilization of storage devices

Core Design Contradiction:

Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent combines multiple WORM storage implementations into a single aggregate by introducing a WORM state identifier that can be assigned to individual volumes within the aggregate. This allows different volumes to have different WORM states (e.g., strict WORM, flexible WORM) while sharing the same underlying storage resources, thereby improving device utilization while maintaining adaptability to different compliance requirements

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The aggregate structure is designed to support multiple WORM state types simultaneously through the use of volume-level WORM state identifiers. This universal approach allows a single aggregate to serve multiple compliance functions (e.g., SEC Rule 17a-4, HIPAA, PCI-DSS) without requiring separate dedicated aggregates for each standard

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If separate aggregates are created for each type of WORM storage implementation, then the system can provide different WORM states, but the device complexity increases

Engineering Contradiction:

Improveability to provide different WORM statesVSAvoidnumber of aggregates required

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

Multiple WORM implementations are merged into a single aggregate structure, reducing the total number of aggregates from N (one per implementation) to 1. The complexity is shifted from the aggregate level to the volume level, where WORM state identifiers are assigned to individual volumes based on their compliance requirements

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The WORM state configuration is segmented to the volume level rather than the aggregate level. Each volume can independently have its own WORM state identifier, allowing fine-grained control over compliance requirements while simplifying the overall aggregate structure

Inventive Principle:

Principle #1Segmentation

3Adaptability or versatility

If separate aggregates are created for each type of WORM storage implementation, then the system can provide different WORM states, but the minimum storage devices required increases due to RAID overhead

Engineering Contradiction:

Improveability to provide different WORM statesVSAvoidnumber of storage devices required

Core Design Contradiction:

Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

Storage devices are merged across multiple WORM implementations by allowing a single aggregate to host volumes with different WORM states. This eliminates the need to allocate separate minimum device sets (e.g., 3 devices per RAID 6 aggregate) for each implementation, thereby reducing the total quantity of storage devices required

Inventive Principle:

Principle #5Merging (Combining)

4Adaptability or versatility

If separate aggregates are created for each type of WORM storage implementation, then the system can provide different WORM states, but the capacity utilization becomes inadequate

Engineering Contradiction:

Improveability to provide different WORM statesVSAvoidcapacity utilization

Core Design Contradiction:

Adaptability or versatilityVSProductivity

Solution Approach 1:

The aggregate is designed as a universal container that can host volumes with different WORM state identifiers, allowing the same storage capacity to serve multiple compliance functions. This multi-functionality improves capacity utilization by eliminating idle or underutilized storage resources that would exist in dedicated single-purpose aggregates

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS8631215B1Provisioning different types of write once, read many states

Publication Date: 2014.01.14 NETAPP INC

AI summary

Example embodiments provide various techniques for provisioning a write once, read many (WORM) state. In one embodiment, an identifier is accessed. This identifier is assigned to a volume that is associated with an aggregate of storage devices and identifies a first type of the WORM state that is different from a second type of the WORM state associated with the aggregate. The first type of the WORM state is applied to the volume and the application results in different types of WORM states between the aggregate and the volume. Modification of data stored in the volume is then restricted based the first type of WORM state.