Virtual Application Backup via Hypervisor Identifier Translation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In cloud computing systems with multi-tenancy support, identifying virtual applications for backup is challenging due to the abstraction layer that hides identifiers for virtual subcomponents, making it difficult to back up virtual applications effectively.

Innovation Solution

The solution involves querying the cloud service layer for a listing of virtual applications, transforming the received attributes into identifiers recognizable by the virtual center layer, and then using these identifiers to back up the hypervisor-managed virtual machines associated with the virtual applications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multi-tenancy support is implemented in cloud computing systems, then service providers can create virtualized separate tenants using the same infrastructure, but the abstraction layer hides identifiers for virtual subcomponents making backup operations difficult

Engineering Contradiction:

Improvemulti-tenancy supportVSAvoidbackup operation

Core Design Contradiction:

Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent introduces an intermediary component that translates between cloud service layer identifiers and virtual center layer identifiers. This mediator enables backup operations by converting the hidden virtual machine identifiers into accessible forms, allowing the backup system to operate on virtual applications without direct access to underlying virtual machine identification mechanisms.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the identification process into two distinct layers: the cloud service layer that manages virtual applications using high-level identifiers, and the virtual center layer that manages virtual machines using low-level identifiers. This segmentation allows each layer to operate independently while maintaining compatibility through identifier translation, resolving the conflict between multi-tenancy abstraction and backup accessibility.

Inventive Principle:

Principle #1Segmentation

2Adaptability or versatility

If an abstraction layer is introduced between tenants and storage level, then multi-tenancy is enabled, but identifiers for virtual subcomponents become hidden and difficult to access for backup purposes

Engineering Contradiction:

Improvemulti-tenancy capabilityVSAvoididentifier accessibility

Core Design Contradiction:

Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent employs an intermediary translation mechanism that bridges the abstraction gap between layers. This intermediary maintains identifier mappings without exposing the underlying virtual machine identification mechanisms, thus preserving information accessibility while maintaining the protective abstraction layer required for multi-tenancy.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates a copy or mapping of virtual machine identifiers at the cloud service layer that mirrors the structure and relationships of actual virtual machine identifiers at the virtual center layer. This copied identifier system enables backup operations to proceed using accessible identifiers while the original hidden identifiers remain protected within the abstraction layer.

Inventive Principle:

Principle #26Copying

3Reliability

If direct backup operations are performed on virtual machines, then backup functionality is available, but the hidden identifiers prevent direct access to virtual subcomponents

Engineering Contradiction:

Improvebackup functionalityVSAvoidvirtual subcomponent identification

Core Design Contradiction:

ReliabilityVSDifficulty of detecting and measuring

Solution Approach 1:

The patent introduces an intermediary identification translation system that converts inaccessible virtual machine identifiers into accessible forms for backup operations. This intermediary enables the backup system to detect and identify virtual subcomponents without directly accessing the hidden identifier mechanisms, thus maintaining backup reliability while overcoming identification difficulties.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent performs preliminary identifier translation and mapping before backup operations commence. By pre-establishing the relationship between cloud service layer identifiers and virtual center layer identifiers, the system prepares the identification pathway in advance, making virtual subcomponents detectable and accessible when backup operations are initiated.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS9507622B2Identification of virtual applications for backup in a cloud computing system

Publication Date: 2016.11.29 NETAPP INC

AI summary

Exemplary embodiments provide various techniques for identifying a virtual application for backup in a cloud computing system. A cloud service layer of the cloud computing system is queried for a listing of virtual applications. In response to the querying, an attribute associated with the virtual application is received from the cloud service layer. The attribute associated with the virtual application is then transformed into an attribute associated with a hypervisor-managed virtual machine, and this transformation of the attribute exposes the hypervisor-managed virtual machine associated with the virtual application such that the hypervisor-managed virtual machine is identifiable for backup. As a result, the virtual application can be backed up based on the attribute of the hypervisor-managed virtual machine.