Storage System Disaster Preparation for Data Integrity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current hierarchical storage systems face challenges in ensuring 100% data recovery during disasters, as they often rely on onsite storage solutions that may be compromised or destroyed, lacking effective offsite data protection mechanisms.

Innovation Solution

The implementation of a disaster preparation method that involves managing onsite data volumes to peer sites and storing cached data and management information on removable media, allowing for temporary offsite storage and subsequent recovery, enabling 100% data integrity post-disaster.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data is stored only on onsite storage systems, then fast access and high-capacity storage are achieved, but data recovery is compromised when disaster strikes the onsite location

Engineering Contradiction:
Improvedata recovery capabilityVSAvoiddisaster vulnerability
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The system performs preliminary disaster preparation by identifying and protecting critical data before a disaster occurs. When a disaster warning is received, the system proactively copies data from vulnerable onsite storage to protected offsite storage locations, ensuring data survival without waiting for the disaster to strike.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system introduces an intermediary disaster preparation layer between onsite and offsite storage. This intermediary mechanism manages data replication and protection workflows, coordinating between local storage systems and remote backup locations to ensure data integrity during disaster scenarios.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If data is replicated to offsite storage locations, then data protection during disasters is improved, but storage complexity and management overhead increase

Engineering Contradiction:
Improvedata protection capabilityVSAvoidstorage system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system implements self-service automation where the storage manager autonomously identifies data to be protected, initiates replication workflows, and manages offsite storage operations without requiring complex manual intervention. The system automatically responds to disaster warnings and executes protection protocols, reducing management complexity despite the distributed architecture.

Inventive Principle:
Principle #25Self-service

3Speed

If all data is stored on fast DASD storage, then access speed is maximized, but storage cost and capacity limitations increase

Engineering Contradiction:
Improvedata access speedVSAvoidstorage capacity
Core Design Contradiction:
SpeedVSQuantity of substance

Solution Approach 1:

The system segments data storage across multiple tiers and locations. Critical frequently-accessed data resides on fast DASD storage for rapid access, while disaster protection copies are replicated to offsite storage locations. This segmentation allows the system to maintain high-speed access for active data while distributing capacity requirements across different storage resources.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS7757111B2Method and system for insuring data integrity in anticipation of a disaster
Publication Date: 2010.07.13 X CORP
  • US7757111B2 patent drawing
  • US7757111B2 patent drawing
  • US7757111B2 patent drawing

AI summary

A preparation of a storage system of a pending disaster at an onsite location of the storage system involves the storage system receiving a disaster preparation initiation from an offsite client. In response to receiving the disaster preparation initiation from the offsite client, the storage system to executes disaster preparation of onsite data including managing a temporary storage of onsite data volumes to at least one peer site, managing a storage of onsite cached data to a first onsite removable media, and/or managing a storage of onsite management information to a second onsite removable media.