Dynamic Multiple Proxy Deployment via Instant Cloning
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current proxy deployment methods in virtual hard disk networks are not dynamic and are time-consuming, leading to insufficient backup proxies during peak demand, resulting in missed backup windows and performance degradation due to resource constraints.
Innovation Solution
Implementing a dynamic multiple proxy deployment method using instant cloning, where additional proxies are rapidly provisioned from a source proxy, sharing memory and disk state, and configured independently to scale as needed without relying on backup server resources.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If traditional proxy deployment methods are used, then initial deployment can be planned and configured, but deployment time is long and cannot scale dynamically
Solution Approach 1:
The system enables dynamic proxy deployment by allowing the backup server to automatically provision additional proxies based on real-time backup queue status. The deployment process transitions from static initial configuration to dynamic scaling, where proxies can be added or removed as backup workload changes, eliminating the need for manual reconfiguration and enabling rapid response to varying backup demands.
Solution Approach 2:
The system uses template-based proxy deployment where new proxies are created by copying and instantiating a standardized proxy template. This template contains all necessary configuration, services, and resource allocations, allowing rapid provisioning of multiple proxies simultaneously without manual configuration of each individual proxy, thus significantly reducing deployment time.
2Productivity
If more proxies are deployed to handle increased VM backup demand, then backup capacity increases, but hypervisor resources are consumed exclusively and datacenter performance may degrade
Solution Approach 1:
The system implements resource allocation policies that assign specific resource quotas and constraints to each proxy based on its role and the backup workload it needs to handle. This ensures that proxies receive only the necessary resources to perform their backup functions efficiently, preventing resource exhaustion that would degrade overall datacenter performance while still enabling high backup processing capacity through coordinated proxy operation.
Solution Approach 2:
The system deploys proxies with predetermined resource allocations that are optimized for backup processing rather than providing full hypervisor resource access. By using partial resource allocation tailored to backup needs, the system achieves sufficient backup capacity without consuming excessive hypervisor resources that would impact other datacenter workloads and overall performance.
3Adaptability or versatility
If proxy deployment is manual and requires user agreement on number of proxies, then initial configuration is controlled, but deployment becomes slow and cannot respond to changing backup windows
Solution Approach 1:
The backup server automatically monitors backup queue status and autonomously provisions additional proxies based on detected workload conditions. This self-service capability eliminates the need for manual user intervention to approve or configure additional proxies, allowing the system to dynamically scale proxy deployment in response to changing backup demands without human delay or bottleneck.
Solution Approach 2:
The system implements a feedback loop where the backup server continuously monitors backup job status, queue depth, and proxy performance metrics. Based on this feedback, the system automatically adjusts proxy deployment by provisioning additional proxies when backup capacity is insufficient and terminating excess proxies when demand decreases, enabling rapid adaptation to changing backup window requirements without manual reconfiguration.
Data Source
AI summary
Dynamically generating proxy virtual machines (VMs) in a virtual center (vCenter) serving a backup server, by deploying a source proxy VM by passing network data to the vCenter, passing a set of internet protocol (IP) addresses and network configuration information to the vCenter to be used by the dynamically generated proxy VMs, receiving an indication from the backup server that new proxy VMs are required, and performing, in the vCenter, an instant clone operation to spawn one or more new proxy VMs. The method may further comprise passing the IP address and network configuration information for the new proxy VMs to the backup server for registration within the backup server, and using the new proxy VMs for backup operations of the backup server.