3Par InServ Architecture
So, we continue to get acquainted with the innovations in the line of HP storage systems, which appeared after the acquisition of 3Par. Let me remind you that the first date took place right here - there we learned about the past life of 3Par products and made the first impression. Now we will get even closer and look at the subtleties of their architecture.
Now the 3Par InServ lineup consists of four systems: two F-Series, supporting up to 384 disks, and two T-Series, which support up to 1280 disks. If traditional modular disk arrays (for example, HP StorageWorks EVA) are based on two controllers combined into a cluster, the 3Par InServ array architecture already supports up to eight controllers, which together form a fully connected multi-node full-mesh cluster.
Of course, this architecture provides a more flexible load balancing between controllers and gives more opportunities for scaling the performance of the disk array. It also provides some insurance in the event that one of the controllers fails. For the same purpose, the Persistent Cache mechanism is used, which mirrors the controller's cache memory.
The second feature of the hardware of 3Par arrays is the use of an ASIC chip in each controller, which at the iron level implements additional useful functionality. For example, thin provisioning (“thin initialization”), which we will talk about further, as well as independent processing of control commands and data streams, allowing an array to efficiently process different I / O streams in parallel: both with a large amount of data and with a large number of transactions .
')
Over the past three years, thin provisioning support has become a standard feature for middle and high-end arrays. But it was 3Par that, in 2003, was the first storage system in the industry to implement this functionality, incorporating it into the architecture of the first generation of its disk arrays. Since then, the company has constantly improved its thin provisioning, ahead of other manufacturers.
In addition to the main purpose of thin provisioning - the dynamic allocation of capacity from a virtual pool to applications - 3Par engineers implemented thin conversion and thin reclamation (probably, thin processing). The first is used to quickly migrate data from a traditional disk array to a thin provisioning array without sacrificing performance. And the second is to return unused allocated capacity to the virtual pool.
The use of these “thin” technologies greatly increases the efficiency of storage system resources, saves the administrator’s work time and eliminates the need to purchase additional disks for future use.
For virtualization of disk space in 3Par arrays, a three-level structure is used:
The system of virtual domains allows you to cut a disk array into isolated virtual private arrays at the logical level. This feature is very popular with service providers, as it can be used to guarantee the safe storage of data belonging to different clients (or different divisions of the corporation) on one disk array. For example, Savvis, one of the largest US service providers, has been using 3Par products since 2004 and installed more than thirty InServ systems with a total capacity of more than 2 PB in 28 of its data centers.
“It was nice to meet you!” Say HP 3Par arrays. Questions?
Now the 3Par InServ lineup consists of four systems: two F-Series, supporting up to 384 disks, and two T-Series, which support up to 1280 disks. If traditional modular disk arrays (for example, HP StorageWorks EVA) are based on two controllers combined into a cluster, the 3Par InServ array architecture already supports up to eight controllers, which together form a fully connected multi-node full-mesh cluster.
Of course, this architecture provides a more flexible load balancing between controllers and gives more opportunities for scaling the performance of the disk array. It also provides some insurance in the event that one of the controllers fails. For the same purpose, the Persistent Cache mechanism is used, which mirrors the controller's cache memory.
The second feature of the hardware of 3Par arrays is the use of an ASIC chip in each controller, which at the iron level implements additional useful functionality. For example, thin provisioning (“thin initialization”), which we will talk about further, as well as independent processing of control commands and data streams, allowing an array to efficiently process different I / O streams in parallel: both with a large amount of data and with a large number of transactions .
')
Where "thin", there and ... solid benefits
Over the past three years, thin provisioning support has become a standard feature for middle and high-end arrays. But it was 3Par that, in 2003, was the first storage system in the industry to implement this functionality, incorporating it into the architecture of the first generation of its disk arrays. Since then, the company has constantly improved its thin provisioning, ahead of other manufacturers.
In addition to the main purpose of thin provisioning - the dynamic allocation of capacity from a virtual pool to applications - 3Par engineers implemented thin conversion and thin reclamation (probably, thin processing). The first is used to quickly migrate data from a traditional disk array to a thin provisioning array without sacrificing performance. And the second is to return unused allocated capacity to the virtual pool.
The use of these “thin” technologies greatly increases the efficiency of storage system resources, saves the administrator’s work time and eliminates the need to purchase additional disks for future use.
From each according to his ability, to each according to his needs
For virtualization of disk space in 3Par arrays, a three-level structure is used:
- At the base of the structure are 256-megabyte segments into which physical disks are broken.
- Segments are grouped into logical volumes based on the level of service required and data protection. Within one logical volume there can be several regions with different types of disks (Fiber Channel, SATA or SSD), RAID levels and degree of fault tolerance. In this case, the logical volume may include segments from different physical disks located on different disk shelves of the array.
- In turn, logical volumes are grouped into virtual disks , which "see" the servers connected to the array.
Provider note
The system of virtual domains allows you to cut a disk array into isolated virtual private arrays at the logical level. This feature is very popular with service providers, as it can be used to guarantee the safe storage of data belonging to different clients (or different divisions of the corporation) on one disk array. For example, Savvis, one of the largest US service providers, has been using 3Par products since 2004 and installed more than thirty InServ systems with a total capacity of more than 2 PB in 28 of its data centers.
“It was nice to meet you!” Say HP 3Par arrays. Questions?
Source: https://habr.com/ru/post/112063/
All Articles