Backup Server Data Lifecycle Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data backup methods, such as ASAP and available capacity approaches, face challenges in efficiently managing storage resources, leading to potential storage space issues, increased backup durations, and higher capacity costs due to inadequate scheduling and resource conflicts.

Innovation Solution

A time-based lifecycle policy for data images is implemented, allowing a backup server to select point-in-time values for moving data between storage tiers, considering calendar dates, hours, data classes, available capacity, and other criteria to optimize data migration and reduce scheduling conflicts.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If ASAP approach is used for data migration, then storage resource utilization is improved, but scheduling conflicts occur and backup operations are delayed

Engineering Contradiction:
Improvestorage resource utilizationVSAvoidbackup operation delay
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system performs preliminary scheduling of backup operations by evaluating multiple candidate time windows and selecting optimal migration times before execution. This advance planning prevents scheduling conflicts and ensures that backup operations are delayed minimally, resolving the contradiction between resource utilization and operation timing.

Inventive Principle:
Principle #10Preliminary action

2Quantity of substance

If available capacity approach is used, then storage space management is improved, but another operation may be accessing the storage resource

Engineering Contradiction:
Improvestorage space managementVSAvoidoperation access conflict
Core Design Contradiction:
Quantity of substanceVSReliability

Solution Approach 1:

The system implements feedback mechanisms by continuously monitoring storage resource access status and adjusting migration schedules accordingly. Before executing data migration, the system checks whether storage resources are currently accessed by other operations, and only proceeds when resources are available, thus preventing access conflicts while maintaining effective storage space management.

Inventive Principle:
Principle #23Feedback

3Ease of operation

If data classification approach is used, then data organization is improved, but data may be moved to another storage tier too early or too late

Engineering Contradiction:
Improvedata organizationVSAvoidrestore operation time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The system dynamically adjusts data migration timing based on multiple factors including data classification, storage tier characteristics, and current system workload. Rather than using static classification-based rules, the system continuously evaluates whether migrating data now would cause restore operations to be delayed, and adapts migration schedules in real-time to prevent both premature and delayed migrations.

Inventive Principle:
Principle #15Dynamics

4Quantity of substance

If predetermined limit is set too high, then storage capacity is improved, but backup operations fail due to insufficient available storage space

Engineering Contradiction:
Improvestorage capacityVSAvoidbackup operation success
Core Design Contradiction:
Quantity of substanceVSReliability

Solution Approach 1:

The system performs preliminary evaluation of storage capacity requirements before scheduling backup operations. By calculating the actual space needed and comparing it against available capacity in advance, the system can identify potential failures before they occur and adjust schedules or notify administrators, preventing backup operation failures due to insufficient storage space.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS8812436B2Schedule based data lifecycle management
Publication Date: 2014.08.19 COHESITY INC
  • US8812436B2 patent drawing
  • US8812436B2 patent drawing
  • US8812436B2 patent drawing

AI summary

A system and method for defining a separate lifecycle policy for each of one or more data images. A backup server is configured to select a first point-in-time value, which indicates when to begin moving a data image from a first data storage medium to a second storage medium. The point-in-time value corresponds to a calendar date and an hour or hours of the day. The backup server is configured to continue selecting a respective point-in-time value for each data storage medium within a tiered storage hierarchy in order to define the lifecycle policy. The backup server may be further configured to delete a copy of the data image on a source data storage medium when completion of a move of the data image to a destination data storage medium is detected. Further, the backup server may detect scheduling conflicts between two or more lifecycle policies.