IBM Storwize family

IBM Storwize systems are virtualizing RAID computer data storage systems with raw storage capacities up to 4PB.[1] Storwize is based on the same software as IBM SAN Volume Controller (SVC).

Models

The Storwize family offers eight members:[2]

Each of the above family members run software that is based on a common source codebase, although each has a type specific downloadable package.

Architecture

Storwize V7000 provides a very similar architecture to SVC, using the RAID code from the DS8000 to provide internal managed disks and SSD code from the DS8000 for tiered storage.[3]

Features and software

All Storwize systems offer the following features:[4]

In addition, the Storwize V7000 offers the following features:[5]

In addition, the Storwize V7000 Unified offers the following feature:[6]

Hardware

The Storwize family hardware consists of control enclosures and expansion enclosures, connected with wide SAS cables (Four lanes of 6Gbit/s or 12Gbit/s). Each enclosure houses 2.5" or 3.5" drives. The control enclosure contains two independent control units (nodes) based on SAN Volume Controller technology, which are clustered via an internal network. Each enclosure also includes two power supply units (PSUs).

Storwize V7000 Gen 2

The IBM Storwize V7000 SFF Control Enclosure Model 524, announced 6th May 2014, features two node canisters and up to 128 GB cache (system total) in a 2U, 19-inch rack mount enclosure. 1 Gb iSCSI connectivity is standard, with options for 8 Gb FC and 10 Gb iSCSI/FCoE connectivity. It holds up to twenty-four 2.5-inch SAS drives and supports the attachment of up to 20 Storwize V7000 expansion enclosures.

IBM Storwize V7000 next-generation models offer increased performance and connectivity, integrated compression acceleration, and additional scalability with the following features:

Hardware Details:

Software Details:

Storwize V7000

Storwize V7000 consists of one to four control enclosures and up to 36 expansion enclosures, for a maximum of 40 enclosures altogether. It can scale up to 960 disks and 1.44PB raw internal capacity.[7]

Hardware details:

Storwize V5000

Storwize V5000 consists of one to two control enclosures and up to 12 expansion enclosures, for a maximum of 18 enclosures altogether. It can scale up to 480 disks and 960TB raw internal capacity.[8]

Hardware details:

SAN Volume Controller

An entry-level SAN Volume Controller configuration contains a single I/O group, can scale out to support four I/O groups and can scale up to support 4,096 host servers, up to 8,192 volumes and up to 32 PB of virtualized storage capacity.[9] For the full article, see IBM SAN Volume Controller.

Hardware details (per node - an I/O group consists of TWO nodes):

Storwize V3700

Storwize V3700 consists of one control enclosure and up to 4 expansion enclosures. It can scale up to 240 2.5-inch disk drives or 120 3.5-inch disk drives and 480TB raw internal capacity.[10]

Hardware details:

Flex System V7000 Storage Node

Flex System V7000 can scale up to 240 (2.5" disks) per control enclosure; 960 (2.5" disks) per clustered system. This is not supported at v7.3.0.

Hardware details:

External links

References

  1. "IBM Storwize family". IBM. Retrieved 6 May 2013.
  2. "We are family ! – Meet the IBM Storwize Family". Storage CH Blog. Retrieved 6 May 2013.
  3. "IBM’s New Midrange with Easy Tier & External Virtualization". The Storage Buddhist. Retrieved 6 May 2013.
  4. "Storwize V3700 overview". IBM Storwize V3700 Version 6.4.1. IBM. Retrieved 6 May 2013.
  5. "Storwize V7000 overview". IBM Storwize V7000 Version 6.4.1. IBM. Retrieved 6 May 2013.
  6. "Storwize V7000 Unified overview". IBM Storwize V7000 Unified Version 1.4. Retrieved 6 May 2013.
  7. "IBM Storwize V7000 and Storwize V7000 Unified Disk Systems". IBM. Retrieved 6 May 2013.
  8. "IBM Storwize V5000". IBM. Retrieved 16 Aug 2014.
  9. "IBM System Storage SAN Volume Controller". IBM. Retrieved 16 Aug 2014.
  10. "IBM Storwize V3700". IBM. Retrieved 16 Aug 2014.
This article is issued from Wikipedia - version of the Thursday, February 18, 2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.