Virtual Array Storage Virtualization Retaining Physical Services
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing storage virtualization products, such as EMC's Invista and IBM's SVC, reduce the value of disk arrays by blocking services like replication and data copy, and do not simplify storage management, as they require separate management tools and reduce disk arrays to raw capacity.
Innovation Solution
A method and system that creates a virtual array within a physical array, maintaining array services and allowing data migration or replication using existing array services, without the need for external equipment, by assigning unique names and ports to the virtual array and enabling it to be associated with another virtual array, thus simplifying management and retaining investment in physical arrays.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If existing storage virtualization products (EMC Invista, IBM SVC) are used to virtualize storage systems, then storage management is simplified by packaging into a pool, but the disk array value is eliminated by reducing it to raw capacity only
Solution Approach 1:
The invention segments the storage system into multiple independent virtual arrays (e.g., Array1, Array2, Array3) within the physical disk array. Each virtual array can be managed independently while retaining access to underlying physical array services, thus preserving disk array value while achieving virtualization benefits.
Solution Approach 2:
The invention implements nested virtualization by creating virtual arrays inside physical arrays, and potentially virtual arrays inside virtual arrays. This nested structure allows multiple levels of virtualization without eliminating the underlying physical array services, maintaining the value chain from physical to virtual layers.
2Device complexity
If existing storage virtualization products are used, then storage pool is created, but separate management tools are required and physical disk arrays still need manual management
Solution Approach 1:
The virtual arrays inherit and provide universal access to all physical array services (replication, data copy, provisioning, etc.) through a unified interface. This multi-functionality eliminates the need for separate management tools while maintaining simplified management, as the same management framework handles both virtual and physical array operations.
Solution Approach 2:
The virtual array acts as an intermediary layer between the storage management system and the physical disk array. This intermediary provides abstraction and simplification, allowing management operations to be performed at the virtual level while automatically translating to appropriate physical array actions, thus reducing management complexity.
3Adaptability or versatility
If disk arrays are reduced to providing only raw capacity, then virtualization is achieved, but local and remote replication, data copy, and other services are blocked
Solution Approach 1:
The invention performs preliminary action by pre-configuring virtual arrays with access rights and service mappings before data migration or replication operations. This ensures that when services are needed, the virtual arrays can immediately access underlying physical array services without requiring reconfiguration, thus maintaining service availability while enabling virtualization.
Solution Approach 2:
The invention replaces the mechanical blocking mechanism of traditional virtualization products with a software-based service routing mechanism. Virtual arrays use software-defined access controls and service mappings to enable or disable specific services, rather than physically blocking service paths, thus maintaining service availability while achieving virtualization.
Data Source
AI summary
The disclosure relates to a method and system for creating a virtual array in a physical array. Unassigned whole volumes in at least one physical array are identified. The identified volumes are associated with a first virtual array. Unique names are given to the identified volumes. At least one path is assigned to the first virtual array. The first virtual array may be associated with a second virtual array. Data may be migrated or replicated from the first virtual array to the second virtual array using existing array services.