Virtual Volume Replication via VVol Framework APIs
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional storage arrays cannot autonomously apply storage policies or operations on a per-VM basis in virtualized deployments due to their inability to distinguish between virtual machines, and existing implementations of the VVol framework do not support replication and recovery of virtual volumes across different storage arrays or sites.
Innovation Solution
The VVol framework is enhanced with new workflows and APIs to facilitate the provisioning of virtual volumes for replication, discovery of replication topology, orchestration of test failover, and actual failover of virtual volumes across VVol-enabled storage arrays, enabling autonomous replication and recovery of virtual volumes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If conventional storage arrays use per-LUN/file system volume storage management, then the storage array can manage data at a coarse granularity level, but it cannot distinguish between multiple VMs and apply per-VM storage policies autonomously
Solution Approach 1:
The patent segments the storage management unit from the traditional LUN/file system volume level down to the virtual volume level, which corresponds to individual VMs. This segmentation enables the storage array to distinguish between different VMs and apply storage policies autonomously on a per-VM basis, resolving the contradiction between ease of operation at coarse granularity and adaptability at fine granularity.
Solution Approach 2:
The virtual volume acts as an intermediary between the VM and the physical LUN/file system volume. This intermediary layer allows the storage array to understand and manage data at the VM level without requiring changes to the underlying physical storage structure, enabling per-VM storage policies while maintaining compatibility with existing storage management mechanisms.
2Adaptability or versatility
If existing VVol framework implementations support snapshotting and cloning, then VM storage management operations are enabled, but replication and recovery of virtual volumes across storage arrays/sites is not supported
Solution Approach 1:
The patent extends the VVol framework to provide universal storage management capabilities that include not only snapshotting and cloning but also replication and recovery operations. By making the framework multi-functional, it enables the same virtual volume infrastructure to support both local storage management and cross-site disaster recovery, thereby improving reliability without sacrificing operational versatility.
Solution Approach 2:
The patent implements preliminary replication of virtual volumes to multiple storage arrays/sites before actual failures occur. This preliminary action ensures that backup copies are ready in advance, enabling rapid recovery operations when needed and significantly improving system reliability and business continuity.
3Device complexity
If multiple VMs share a single LUN/file system volume, then storage resources are consolidated, but the storage array cannot apply differentiated storage policies to each VM
Solution Approach 1:
The virtual volume serves as an intermediary layer between multiple VMs sharing physical storage and the storage array's policy enforcement mechanism. This intermediary enables the storage array to apply differentiated storage policies to each VM while the VMs continue to share consolidated storage resources, resolving the contradiction between storage consolidation and differentiated policy application.
Data Source
AI summary
Techniques for supporting replication and recovery of virtual volumes are provided. In various embodiments, these techniques can include workflows and application programming interfaces (APIs) that facilitate: (1) the provisioning of virtual volumes with metadata indicating that the virtual volumes should be replicated from one virtual volume-enabled storage array/site to another; (2) the discovery of a replication topology across virtual volume-enabled storage arrays/sites; (3) the orchestration of a test failover of a set of virtual volumes; and (4) the orchestration of an actual failover of a set of virtual volumes.