Virtual Desktop Backup via Variable Length Deduplication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional backup solutions struggle to efficiently protect virtual desktop environments and facilitate restore operations due to the dynamic nature of virtual machines and the loss of user customizations in non-persistent systems, posing risks to data integrity and business continuity.
Innovation Solution
A system and method for optimized backup and restore operations in virtual desktop environments using a variable length deduplication system that stores unique daily changes while maintaining daily full backups, enabling fast and efficient data recovery through a desktop broker and deduplication technologies like EMC Avamar, which reduces network bandwidth usage and simplifies data management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If traditional backup solutions are used for virtual desktop environments, then data protection is provided, but backup windows are not met and restore operations are inefficient
Solution Approach 1:
The backup system segments virtual desktop data into multiple components (base images, differential data, user profiles, application data) and backs them up separately using different methods. Base images use full backups while differential data uses incremental backups, allowing parallel processing and optimizing overall backup speed while meeting backup windows.
Solution Approach 2:
The system dynamically changes backup parameters based on data characteristics. For example, it adjusts compression levels, deduplication ratios, and backup frequencies based on the specific component being backed up, thereby improving backup efficiency and reducing backup window requirements.
2Reliability
If traditional backup solutions are used for virtual desktop environments, then data protection is provided, but storage requirements increase
Solution Approach 1:
The system merges multiple backup streams (full backups, incremental backups, differential data) into a unified storage structure with centralized deduplication. This allows efficient storage of backup data by eliminating redundant copies across different virtual desktops while maintaining data integrity through verified backup chains.
Solution Approach 2:
The system implements selective retention policies where older full backups are discarded after successful incremental backup chains are established. Only essential base images and differential data are retained, significantly reducing storage requirements while maintaining the ability to recover any point in time through the incremental chain.
3Adaptability or versatility
If virtual machines are constructed dynamically during runtime, then user customization is enabled, but backup complexity increases
Solution Approach 1:
The system performs preliminary actions by capturing user customizations and application data at defined checkpoints (e.g., at logoff or before critical operations). This allows the backup process to work with pre-prepared data states rather than attempting to backup dynamic runtime environments, simplifying the backup process while preserving user customizations.
4Loss of energy
If non-persistent virtual desktop systems are used, then resource efficiency is improved, but user customizations are lost after restart
Solution Approach 1:
The system creates persistent copies of user customizations and application data separate from the volatile virtual desktop environment. User profiles, document data, and application settings are copied to persistent storage locations that survive restarts, allowing the virtual desktop to remain non-persistent for resource efficiency while preserving user information.
Data Source
AI summary
A system and method of performing backups of a system having persistent and non-persistent virtual desktop infrastructure components, database storage components, and file management components. The method first backs up the file management components, then a database server of the database storage components, and then the virtual desktop infrastructure components in an order of a virtual center server, connection server, and then a composer server. If the virtual desktop environment is non-persistent, the system backs up a master image that is used to create non-persistent desktops, and if the virtual desktop environment is persistent, the system backs up the master image that is used to create non-persistent desktops and virtual storage objects that maintain persistence of an identity of the virtual desktop environment.


