Server Dormant Mode for Seamless Virtualization Upgrades

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing enterprise content management systems face challenges in synchronizing multiple components for data integrity, leading to downtime during upgrades and maintenance, and lack flexibility in scaling and load balancing.

Innovation Solution

Implementing a dormant state for server components, where they can no longer accept new connections and become read-only, allowing for safe upgrades and dynamic resource allocation, with only privileged users able to set and use this state.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual shutdown of each component is performed to ensure data integrity, then data integrity is improved, but system downtime increases

Engineering Contradiction:
Improvedata integrityVSAvoidsystem downtime
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system dynamically transitions components between active and dormant states based on operational needs. The dormant state allows components to be safely shut down or upgraded without affecting overall system availability, as the virtualization layer maintains service continuity through live migration and load balancing across remaining active components.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system divides the infrastructure into physical components and virtual components. Physical hardware can be shut down or maintained while virtual server instances are migrated to other physical hosts. This segmentation allows independent management of physical and virtual layers, enabling maintenance without service interruption.

Inventive Principle:
Principle #1Segmentation

2Reliability

If multiple components are synchronized for upgrades, then data integrity is improved, but upgrade complexity increases

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

Solution Approach 1:

The virtualization management system automatically handles component synchronization, state transitions, and coordination during upgrades. The system self-manages the complexity of coordinating multiple components by providing automated orchestration of dormant state transitions, migration operations, and synchronization protocols, reducing manual intervention requirements.

Inventive Principle:
Principle #25Self-service

3Reliability

If server capacity is increased to handle load spikes, then system availability is improved, but resource utilization efficiency decreases

Engineering Contradiction:
Improvesystem availabilityVSAvoidresource utilization efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system dynamically provisions virtual server capacity by transitioning physical hosts between active and dormant states based on real-time load conditions. During load spikes, dormant hosts can be rapidly activated and integrated into the cluster. During low-utilization periods, hosts are placed in dormant state to conserve resources, enabling elastic scaling without permanent over-provisioning.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The dormant state serves multiple functions: it enables rapid capacity expansion during load spikes, facilitates maintenance windows, supports load balancing operations, and provides a mechanism for resource consolidation. This multi-functional state allows the system to adapt to various operational scenarios without requiring separate mechanisms for each use case.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS9319274B1Method and system for dynamic provisioning using server dormant mode for virtual server dormancy
Publication Date: 2016.04.19 DELL EMC
  • US9319274B1 patent drawing
  • US9319274B1 patent drawing
  • US9319274B1 patent drawing

AI summary

A method for dynamic provisioning of server deployments using a dormant mode for content servers. Client devices may conduct transactions with servers when the servers are in an active mode. However, in the dormant mode, the servers do not accept new transactions. Thus, by utilizing the dormant mode on one or more servers, a server deployment scheme can be effectively scaled down by reducing the number of active servers. In order to scale up the deployment, one or more active servers are added to the deployment.