Virtual Proxy Deployment Based on Protected VM Count
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current proxy deployment methods in virtual enterprise storage systems inaccurately estimate the number of virtual proxies needed, leading to unnecessary resource consumption and manual deployment errors, as they calculate based on available VMs rather than actively protected VMs.
Innovation Solution
Dynamically determine and automatically deploy the exact number of virtual proxies required by assessing the number of VMs protected by the backup server in real-time, using a point-in-time analysis and adjusting as needed, to optimize proxy usage and avoid human error.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If proxy deployment is based on the number of available VMs in the entire VC, then all available VMs can be protected, but unnecessary proxies are deployed consuming wasted resources
Solution Approach 1:
The system changes the parameter used for proxy deployment from 'number of available VMs' to 'number of actively protected VMs'. This parameter change ensures that proxies are deployed only when needed, eliminating wasted resources while maintaining protection coverage for actually protected VMs.
Solution Approach 2:
The backup server continuously monitors and tracks the actual number of VMs protected through backup policies, using this feedback information to dynamically adjust proxy deployment. This feedback mechanism ensures proxy numbers match actual protection needs rather than relying on static availability counts.
2Ease of operation
If manual proxy deployment is used, then deployment can be controlled, but human error and tediousness increase
Solution Approach 1:
The backup server automatically performs proxy deployment without requiring manual intervention. The system self-manages the entire proxy deployment process by calculating required numbers based on actual protected VMs and automatically provisioning proxies, eliminating human error while maintaining operational control.
Solution Approach 2:
The manual mechanical process of proxy deployment is replaced with an automated software-based system. The backup server uses automated calculations and provisioning mechanisms to deploy proxies, replacing manual administrative tasks with programmable logic that reduces errors and improves reliability.
3Area of stationary object
If proxies are deployed based on entire VC topology, then comprehensive coverage is achieved, but idle proxies consume VC resources
Solution Approach 1:
The system applies local quality by deploying proxies based on actual protected VMs rather than entire VC topology. This ensures proxies are deployed locally where needed based on actual backup policies and protected workloads, rather than uniformly across the entire VC, eliminating idle proxies.
Solution Approach 2:
Instead of deploying proxies for all available VMs (excessive action), the system deploys proxies only for actually protected VMs (partial action). This partial approach ensures sufficient coverage for protected workloads while avoiding the excessive deployment that would occur based on total VC availability.
Data Source
AI summary
In a backup system for a virtual infrastructure, the actual number of virtual machines protected by a backup server is determined for a given instant of time, and is used to calculate the number of virtual proxies required to protect the that actual number of virtual machines, and to deploy automatically the required virtual proxies in the virtual infrastructure.

