Backup Agent Automates VM Application Discovery

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Virtual machine backup applications lack the ability to automatically discover applications within a virtual machine and associate them with backup policies, as well as perform application-specific pre- and post-backup actions, leading to inefficient data backup processes.

Innovation Solution

A backup agent within the virtual machine communicates with a backup server to discover and list applications, transmit a universally unique identifier, and perform application-specific actions, including pre- and post-backup operations, ensuring data is backed up according to defined policies.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Extent of automation

If virtual machine backup applications use traditional backup methods, then backup processes are simple to implement, but they cannot automatically discover applications within the virtual machine or associate them with backup policies

Engineering Contradiction:
Improveautomatic application discoveryVSAvoidbackup system complexity
Core Design Contradiction:
Extent of automationVSDevice complexity

Solution Approach 1:

The patent introduces a backup agent as an intermediary component installed within the virtual machine that communicates with the backup server. This agent automatically discovers applications inside the VM, retrieves their metadata, and associates them with appropriate backup policies, thereby enabling automatic application discovery without significantly increasing overall system complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The backup agent enables the virtual machine to perform self-service by automatically discovering its own applications, generating inventory lists, and associating data with backup policies without requiring external manual intervention. This self-service capability enhances automation while keeping the backup system manageable.

Inventive Principle:
Principle #25Self-service

2Extent of automation

If virtual machine backup applications manually manage backup policies, then policy association is simple and clear, but it requires manual intervention and cannot automatically perform application-specific actions

Engineering Contradiction:
Improveautomatic policy associationVSAvoidoperation simplicity
Core Design Contradiction:
Extent of automationVSEase of operation

Solution Approach 1:

The backup agent implements feedback mechanisms by continuously monitoring the virtual machine environment, discovering applications, and automatically associating them with backup policies based on predefined criteria. The agent receives feedback from the backup server regarding policy requirements and adjusts its discovery and association processes accordingly, enabling automatic policy association while maintaining operational simplicity through rule-based automation.

Inventive Principle:
Principle #23Feedback

3Adaptability or versatility

If backup applications focus on basic backup functionality, then the system is easy to operate, but it cannot perform application-specific pre-backup or post-backup actions

Engineering Contradiction:
Improveapplication-specific actionsVSAvoidbackup process complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the backup process into distinct phases: pre-backup actions, the actual backup operation, and post-backup actions. The backup agent is designed to execute specific actions during each phase based on the application being backed up. This segmentation allows the system to perform application-specific actions without overwhelming complexity, as each phase can be independently configured and managed.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The backup agent performs preliminary actions before the actual backup process, such as application-specific preparations, data validation, and policy verification. By executing these preliminary actions automatically, the system enhances adaptability to different application requirements while maintaining operational simplicity through pre-configured action templates.

Inventive Principle:
Principle #10Preliminary action

4Extent of automation

If virtual machine backup applications do not integrate with backup servers, then the system architecture is simple, but it cannot automatically transmit identifiers or discover applications

Engineering Contradiction:
Improveautomatic identifier transmissionVSAvoidsystem integration complexity
Core Design Contradiction:
Extent of automationVSDevice complexity

Solution Approach 1:

The backup agent is designed as a universal component that can operate across different virtual machine environments and communicate with backup servers using standardized protocols. It performs multiple functions including application discovery, metadata collection, identifier transmission, and policy association. This multi-functionality enables automatic identifier transmission and application discovery while managing system integration complexity through a unified agent architecture.

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

Data Source

PatentUS10445186B1Associating a guest application within a virtual machine to create dependencies in backup/restore policy
Publication Date: 2019.10.15 EMC IP HLDG CO LLC
  • US10445186B1 patent drawing
  • US10445186B1 patent drawing
  • US10445186B1 patent drawing

AI summary

Systems and methods are disclosed for performing a backup of data to a backup server for one or more applications on a virtual machine having a universally unique identifier (UUID). A backup application can be deployed within the virtual machine, residing on a guest operating system. The backup application can report a list of applications on the virtual machine to the backup server. The backup server can deploy any application-specific modules that may be needed to perform the backup, and a list of pre- and post-backup actions to take, per application. The backup server can trigger the pre- and/or post-backup actions. The virtual machine can inform the backup server that the pre- and/or post-backup actions have completed. Backups can be in accordance with one or more policies stored at the backup server and associated with the virtual machine UUID or associated with an account that the virtual machine, or its user, are associated with.