Zero-Copy Storage Virtual Machine Relocation for Cluster Load Balancing

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing storage network environments lack load balancing technology to balance workloads between storage clusters, leading to increased latency and performance issues when one cluster experiences a higher load than the other.

Innovation Solution

Implementing zero-copy ownership change operations to switch ownership of storage aggregates and virtual machines between storage clusters based on load balancing metrics, allowing seamless relocation without disrupting client access.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If storage virtual machines are replicated between storage clusters for disaster recovery, then reliability is improved, but device complexity increases

Engineering Contradiction:

Improvedisaster recovery capabilityVSAvoidstorage cluster configuration

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent creates replicated storage virtual machines at remote storage clusters that serve as standby copies. These replicas are maintained in a dormant state during normal operation and can be activated for failover, providing disaster recovery capability without permanently duplicating the entire system infrastructure.

Inventive Principle:

Principle #26Copying

Solution Approach 2:

The system dynamically changes the operational state of replicated storage virtual machines between dormant and active based on failover conditions. The replication relationship is maintained but the functional state adapts to operational needs, reducing complexity by only activating resources when required.

Inventive Principle:

Principle #15Dynamics

2Productivity

If load balancing is implemented between storage clusters, then productivity is improved, but device complexity increases

Engineering Contradiction:

Improveworkload distribution efficiencyVSAvoidload balancing mechanism

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The patent implements dynamic load balancing by evaluating operational statistics and load conditions in real-time, then automatically relocating storage virtual machines between clusters. The system adapts its configuration based on current workload demands rather than following a fixed load balancing scheme.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The storage system performs self-load-balancing by automatically evaluating its own operational statistics and making relocation decisions without external intervention. The system monitors its own performance metrics and autonomously optimizes workload distribution across clusters.

Inventive Principle:

Principle #25Self-service

3Productivity

If storage virtual machines are relocated between clusters, then load balancing is improved, but loss of time increases

Engineering Contradiction:

Improveworkload optimizationVSAvoidrelocation time

Core Design Contradiction:

ProductivityVSLoss of time

Solution Approach 1:

The patent pre-replicates storage virtual machines to remote clusters in a dormant state during off-peak periods. When load balancing is needed, the system can quickly activate pre-positioned replicas rather than creating them from scratch, significantly reducing relocation time.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

Instead of moving entire storage virtual machines physically, the system activates pre-existing copies at the target cluster. This copying approach allows instantaneous or near-instantaneous relocation by simply changing which replica is active, avoiding time-consuming data transfer operations.

Inventive Principle:

Principle #26Copying

4Productivity

If operational statistics are continuously monitored for load balancing, then productivity is improved, but use of energy increases

Engineering Contradiction:

Improveworkload monitoring accuracyVSAvoidstatistics collection and evaluation

Core Design Contradiction:

ProductivityVSUse of energy by moving object

Solution Approach 1:

The patent implements periodic sampling of operational statistics rather than continuous monitoring. The system evaluates load conditions at defined intervals and makes relocation decisions based on accumulated data, reducing the energy consumption associated with constant monitoring while maintaining effective load balancing.

Inventive Principle:

Principle #19Periodic action

Data Source

PatentUS12461767B2Storage virtual machine relocation

Publication Date: 2025.11.04 NETAPP INC

AI summary

One or more techniques and/or devices are provided for storage virtual machine relocation (e.g., ownership change) between storage clusters. For example, operational statistics of a first storage cluster and a second storage cluster may be evaluated to identify a set of load balancing metrics. Ownership of one or more storage aggregates and/or one or more storage virtual machines may be changed (e.g., permanently changed for load balancing purposes or temporarily changed for disaster recovery purposes) between the first storage cluster and the second storage cluster utilizing zero-copy ownership change operations based upon the set of load balancing metrics. For example, if the first storage cluster is experiencing a relatively heavier load of client I/O operations and the second storage cluster has available resources, ownership of a storage aggregate and a storage virtual machine may be switched from the first storage cluster to the second storage cluster for load balancing.