Logical Namespace Data Protection via Share-Level Failover

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing namespace services fail to detect failures in source shares, leading to inaccessible data and failed failover operations, as they monitor at the filer level rather than the managed data object level, resulting in service disruptions and data protection inefficiencies.

Innovation Solution

An integrated management framework that monitors failures at a managed data object granularity, enabling automatic failover from a primary share to a secondary share within the logical namespace, with a data protection policy specifying failover characteristics and actions for link points, ensuring robust data protection and accessibility.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If namespace services monitor at the filer level, then the monitoring scope is simplified, but failure detection capability for source shares is lost

Engineering Contradiction:
Improvemonitoring scopeVSAvoidfailure detection capability
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent segments the monitoring scope from the filer level to the managed data object level (share level). The namespace service now monitors individual shares for accessibility and availability, rather than only monitoring the filer level. This segmentation enables precise failure detection at the share level while maintaining manageable monitoring complexity through structured policy-based approaches.

Inventive Principle:
Principle #1Segmentation

2Reliability

If automatic failover is implemented at share level, then data protection is improved, but system complexity increases

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

Solution Approach 1:

The patent implements preliminary action through pre-configured failover policies that define failover characteristics and actions before failures occur. Administrators can specify failover behavior in advance, and the system automatically executes these predefined policies when share-level failures are detected, eliminating the need for complex real-time decision-making during failures.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent employs feedback mechanisms where the namespace service continuously monitors share accessibility and availability, detects failures, and triggers failover operations based on configured policies. This closed-loop feedback system automates the failover process and reduces manual intervention while maintaining controlled system complexity.

Inventive Principle:
Principle #23Feedback

3Measurement precision

If granular monitoring at managed data object level is implemented, then failure detection precision is improved, but monitoring overhead increases

Engineering Contradiction:
Improvefailure detection precisionVSAvoidmonitoring overhead
Core Design Contradiction:
Measurement precisionVSUse of energy by moving object

Solution Approach 1:

The patent applies partial action by monitoring only the specific managed data objects (shares) that are configured with data protection policies, rather than continuously monitoring all possible objects. This selective monitoring approach maintains high detection precision for protected shares while reducing overall monitoring overhead by focusing resources on critical assets.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS7734951B1System and method for data protection management in a logical namespace of a storage system environment
Publication Date: 2010.06.08 NETAPP INC
  • US7734951B1 patent drawing
  • US7734951B1 patent drawing
  • US7734951B1 patent drawing

AI summary

A system and method for data protection in a logical namespace of a storage system environment is provided. An integrated management framework implements a data protection technique that monitors failures in the logical namespace at a managed data object granularity, e.g., a share. In the event of a failure to the data object, e.g., a primary share, the data protection technique enables automatic failover for a link point to the object (primary share) that is protected by a backup copy of the data object, e.g., a secondary share. That is, the data protection technique enables failover from the primary share to a secondary share and corresponding linking of the secondary share to the link point in the logical namespace.