Backup Server Fallback to VM Host During CMS Outage

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In virtual machine (VM) environments, communication loss between the backup server and the central management server (CMS) disrupts backup processes, leading to potential data loss and increased recovery time objectives (RTO) and recovery point objectives (RPO), as backups fail and service delays occur, impacting data protection and availability.

Innovation Solution

The backup server is configured to maintain log-in credentials for both the CMS and the VM host, allowing it to switch connections and continue the backup process directly with the host if communication with the CMS is lost, using APIs like VMware's vStorage APIs for Data Protection (VADP) to manage snapshots and deduplicate data, ensuring seamless backup operations even during communication disruptions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If the backup server communicates through the CMS to backup VMs, then centralized management and control are improved, but backup reliability deteriorates when communication between backup server and CMS is lost

Engineering Contradiction:

Improvecentralized managementVSAvoidbackup reliability

Core Design Contradiction:

Ease of operationVSReliability

Solution Approach 1:

The patent introduces the CMS as an intermediary for normal backup operations, but also implements a fallback mechanism where the backup server can directly communicate with VM hosts when the CMS is unavailable. This dual-path approach maintains centralized management benefits while ensuring backup reliability through alternative communication routes.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The backup server pre-establishes communication capabilities and credentials for both CMS-based and direct host-based backup methods. By preparing multiple communication paths in advance, the system can switch to an alternative path when the primary CMS communication fails, ensuring continuous backup operations.

Inventive Principle:

Principle #10Preliminary action

2Stability of the object's composition

If the backup server waits for communication resumption before performing backups, then communication stability is maintained, but productivity deteriorates due to service delays and missed backup windows

Engineering Contradiction:

Improvecommunication stabilityVSAvoidbackup productivity

Core Design Contradiction:

Stability of the object's compositionVSProductivity

Solution Approach 1:

The backup system dynamically adjusts its communication path based on real-time availability. When CMS communication is available, it uses the centralized path; when lost, it switches to direct host communication. This dynamic adaptation ensures both communication stability and continuous backup productivity without missed windows.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The patent ensures continuous backup operations by implementing a fallback mechanism that allows the backup server to proceed with backups through direct host communication when CMS communication is lost. This eliminates service delays and ensures backup windows are never missed, maintaining continuous productive action.

Inventive Principle:

Principle #20Continuity of useful action

3Reliability

If the backup server switches to direct host connection when CMS communication is lost, then backup reliability is improved, but device complexity increases due to multiple connection management requirements

Engineering Contradiction:

Improvebackup reliabilityVSAvoidconnection management complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The backup server is designed with multi-functionality to handle both CMS-based and direct host-based communication protocols. By integrating multiple communication capabilities into a single system, the patent reduces the need for separate backup systems and simplifies overall connection management while maintaining high reliability.

Inventive Principle:

Principle #6Universality (Multi-functionality)

4Reliability

If communication loss occurs between backup server and CMS, then data protection is jeopardized, but maintaining dual connection capabilities increases storage and computational resources required

Engineering Contradiction:

Improvedata protectionVSAvoidcomputational resources

Core Design Contradiction:

ReliabilityVSQuantity of substance

Solution Approach 1:

The backup server autonomously monitors CMS communication status and automatically switches to direct host communication when needed, without requiring additional external resources or manual intervention. This self-service capability ensures data protection while minimizing the need for additional computational resources.

Inventive Principle:

Principle #25Self-service

Data Source

PatentUS10552268B1Broken point continuous backup in virtual datacenter

Publication Date: 2020.02.04 EMC IP HLDG CO LLC

AI summary

Providing backup of virtual machines can be performed by a backup server. The backup server can maintain log-in credentials for a central management server and a virtual machine host. If communication is lost between the backup server and the central management server, the backup server can initialize a connection directly to the host and back up a target virtual machine.