Virtual Storage Manager Failover with Scaled-Down Standby Nodes

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Enterprises using third-party virtual computing providers to host storage managers face additional financial burdens due to computing costs per virtual machine, especially when enabling live synchronization configurations, and there is a need for efficient failover mechanisms that minimize resource usage.

Innovation Solution

Implementing standby passive nodes in scaled-down or reduced states that replicate data changes and initiate failover processes upon detection, scaling down the failed active node after completion.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Use of energy by moving object

If standby passive nodes are operated in scaled down or reduced states to reduce computing resource usage, then computing resource usage and costs are reduced, but the nodes must still maintain data replication capability and failover functionality

Engineering Contradiction:
Improvecomputing resource usageVSAvoidfailover capability
Core Design Contradiction:
Use of energy by moving objectVSReliability

Solution Approach 1:

The standby passive node dynamically adjusts its operational state based on requirements. In normal operation, it runs in a reduced state with minimal resources, replicating only essential data changes. When failover is detected, the node dynamically transitions to an active state, requesting additional computing resources from the host and initiating full failover services, thus resolving the contradiction between resource savings and reliability maintenance

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes operational parameters of the standby node by modifying its resource allocation state. The node transitions from a resource-constrained reduced state to a resource-rich active state through parameter changes in virtual machine configuration, enabling it to maintain failover capability while minimizing resource consumption during normal operation

Inventive Principle:
Principle #35Parameter changes

2Reliability

If live synchronization storage manager configuration is enabled to ensure data protection and availability, then data integrity and availability are improved, but computing costs increase due to per-virtual machine pricing

Engineering Contradiction:
Improvedata availabilityVSAvoidcomputing cost
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

Instead of maintaining a full active storage manager virtual machine as backup, the system creates a simplified copy (standby passive node) that replicates only essential data change information. This copy is sufficient for failover purposes but consumes minimal resources, resolving the contradiction between data availability and computing cost

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The standby passive node functions as a lightweight, cost-effective backup mechanism that is activated only when needed. Rather than maintaining expensive live synchronization infrastructure, the system uses a minimal-cost standby node that replicates critical data changes and initiates failover only when the active node fails, significantly reducing ongoing computing costs while maintaining reliability

Inventive Principle:
Principle #27Cheap short-living objects (Disposable)

Data Source

PatentUS12585555B2Efficient failover of storage manager in virtualized environments
Publication Date: 2026.03.24 COMMVAULT SYSTEMS INC
  • US12585555B2 patent drawing
  • US12585555B2 patent drawing
  • US12585555B2 patent drawing

AI summary

An illustrative efficient failover process and system in virtualized environment to reduce costs and resources associated with maintaining live stand-by failover scheduling and maintenance system is described herein. The illustrative embodiment uses incremental backup data to maintain a failover or passive virtualized computing platforms comprising of one or more virtual machines that are configured to and ready to be scaled up and initiated to take over the tasks and operations of a lost storage manager. Each virtualized failover or passive node is initially configured to use minimal computing resources to maintain a live backup of the active storage manager. During a failover, a passive virtual node will initiate the failover process. In an embodiment, the failover process comprises restoring a secondary copy of the lost storage manager, initiating a scale up process to increase computing resources, and continuing scheduled tasks and operations of the lost storage manager.