This application is a non-provisional application that claims priority benefits under Title 35, United States Code, Section 119(a)-(d) from United Kingdom Patent Application entitled “AN ENCLOSURE” by Ian D. JUDD, having United Kingdom Patent Application Serial No. GB1211918.6, filed on Jul. 5, 2012, which United Kingdom Patent Application is incorporated herein by reference in its entirety.
The present invention relates to a modular storage system and a method for configuring the modular storage system using two such enclosures.
Modular disk storage systems which use rack-mounted enclosures are widely used in computing. These enclosures are often based on the Storage Bridge Bay (SBB) technology standard. SBB defines a standard electronics “canister”, in terms of its dimensions, mid-plane signals and connectors, power supplies and cooling. For example, the IBM® Storwize® V7000 uses enclosures of size 2U that conform to the current SBB 2.0 standard. Each enclosure provides a number of hot-swap drive bays at the front and two slots for electronics canisters at the rear. The dual canisters provide redundancy to ensure High Availability (HA). The first enclosure is a control enclosure that contains two controller canisters which run complex software to provide functions like remote copy, caching, thin provisioning and RAID. Up to nine expansion enclosures can be attached to support additional drives. An expansion enclosure is configured with two expansion canisters. (IBM and Storwize are registered trademarks of International Business Machines Corp. in the United States and other countries).
The controller canister is tightly packaged and contains a central processing unit (CPU) complex, host interfaces, a Serial Attached SCSI (SAS) protocol chip and a SAS expander chip. However, an expansion canister just contains a single SAS expander chip plus a small amount of memory. SBB is a very efficient package for mid-range storage systems. However it constrains the CPU, memory and I/O resources which can be provided in a high-end controller. One option is to lengthen the SBB canister while keeping the other two dimensions unchanged. This has the advantage of compatibility with existing enclosures but it only provides a modest increase in card area and it offers no relief on power and cooling. The SBB working group is developing a 3.0 standard which may increase the canister height. However packaging two such canisters will probably require an enclosure of 3U size. Current storage systems have two controller canisters in the first enclosure and two expansion canisters per expansion enclosure. All canisters are the same size, as defined by the SBB standard.
Provided is an enclosure for use in a modular storage system, the enclosure comprising a plurality of drive bays, a controller canister, an expansion canister, and a midplane connecting the drive bays to the canisters, wherein the controller canister occupies a greater volume of the enclosure than the expansion canister.
Further provided is a modular storage system comprising: a plurality of drive bays; a first enclosure including a first controller canister coupled to the drive bays and a first expansion canister, wherein the first controller canister occupies a greater volume of the enclosure than the first expansion canister; and a second enclosure including a second controller canister and a second expansion canister, wherein the second controller canister occupies a greater volume of the enclosure than the second expansion canister.
Further provided is a method of configuring a modular storage system comprising: inserting two enclosures into the modular storage system, each enclosure comprising a plurality of drive bays, a controller canister, an expansion canister, and a midplane connecting the drive bays to the canisters, wherein the controller canister occupies a greater volume of the enclosure than the expansion canister.
Preferred embodiments of the present invention will now be described, by way of example only, with reference to the following drawings, in which:
According to one embodiment, there is provided an enclosure for use in a modular storage system, the enclosure comprising a plurality of drive bays, a controller canister, an expansion canister, and a midplane connecting the drive bays to the canisters, wherein the controller canister occupies a greater volume of the enclosure than the expansion canister.
According to a further embodiment, there is provided a method of configuring a modular storage system comprising inserting two enclosures into the modular storage system, each enclosure comprising a plurality of drive bays, a controller canister, an expansion canister, and a midplane connecting the drive bays to the canisters, wherein the controller canister occupies a greater volume of the enclosure than the expansion canister.
With the described embodiments, it is possible to provide an enclosure that can be used to package one controller canister and one expansion canister in each of the first two enclosures used in a modular storage system and the space in the enclosure is divided asymmetrically, so that the controller canister has more space than the expansion canister. This significantly relieves the packaging constraints for high-end controllers. The controller canister occupies a greater volume of the enclosure than the expansion canister and this means that more space is available for the contents of the controller canister. Rather than having two controller canisters in one enclosure, two enclosures can be used with one controller canister in each of the first two enclosures. The asymmetric use of space, with respect to the canisters, allows the functionality of the controller canister to be increased.
The enclosures 10 have a vertical height that is often expressed using the unit “U”, so a specific cabinet may be constructed to receive enclosures of various heights in multiples of 1U. The standardization of the cabinets, enclosures and canisters allows different hardware manufacturers to provide compatible components that mean that an end user can mix and match the enclosures as they desire. The enclosures 10 are commonly used to provide enterprise storage solutions for large businesses for example. A single cabinet will include multiple enclosures 10 which contain disk drives in addition to the canisters 12. The disk drives provide storage solutions for the large amount of data that is now very common in businesses.
A second embodiment of an enclosure 10 is shown in
The canisters 12a, 12b if they conform to the SBB standard, have their external dimensions defined by the standard and also have the structure and function of their interconnects 22a, 22b defined by the standard. An enclosure 10 that wishes to receive SBB canisters must provide slots 14 (
The layout of the enclosure 10 is configured according to the manufacturer's desire, but essentially the drive bays are at the front 24 of the enclosure 10, the midplane 18 separates the drive bays from the back of the enclosure 10 and the canisters 12a, 12b are at the back of the enclosure 10 and are connected to the midplane 18. The canisters 12a, 12b provide functionality that is either specific to the enclosure 10 that contains the canisters 12a, 12b or one or more of the canisters 12a, 12b provide functionality that is related to all of the enclosures 10 within a cabinet. As discussed above, a typical cabinet will have multiple enclosures 10 vertically stacked inside the cabinet.
The enclosures 110a, 110b conform to the current SBB 2.0 standard and are of size 2U. Each enclosure 110a, 110b provides hot-swap drive bays at the front and has two slots for the SBB canisters 112a1, 112a2, 112b1, 112b2 at the rear. The dual canisters 112a1, 112a2, 112b1, 112b2 provide redundancy to ensure so-called high availability. The upper enclosure 110a is a control enclosure that contains two controller canisters 112a1, 12a1 which run complex software to provide functions such as remote copy, caching, thin provisioning and RAID. The lower, expansion enclosure 110b can be attached to support additional drives, as can subsequent additional expansion enclosures 110b. Each expansion enclosure 110b is configured with two expansion canisters 112b1, 112b2.
The construction of the enclosures 110a, 110b and the nature of the SBB standard create a constraint on the high-end controller packing of the controller canister 112a1, 112a2. Equally, the expansion canisters 112b1, 112b2 have far more space than is needed for actual electronic components that are carried in an expansion canister 112b1, 112b2. The upper control enclosure 110a is provided with two controller canisters 112a1, 112a2 in order to provide redundancy in relation to the functions provided by the canisters 112a1, 112a2. For much the same reason that there are two power supplies 126a1, 126a2, 126b1, 126b2 in each enclosure 110a, 110b, the two controller canisters 112a1, 112a2 are able to duplicate their function so that should one of the canisters fail, then the other will still be available.
By contrast, an expansion canister 112b1, 112b2 will only have a subset of the components shown in
Essentially, the two canisters 300a, 302a and 300b, 302b used in the enclosures 310a, 310b, respectively, are of an asymmetric size. In the configuration of
The solution of
The different sizes of the canisters 300 and 302 result in an asymmetric controller canister 300 that is 14 mm higher than the current prior art controller canister 12a. Correspondingly, the expansion canister 302 is 14 mm shorter in its vertical height. The controller canister 300 occupies a greater volume of the enclosure than the expansion canister 302. The resulting larger controller canister 300 is therefore able to accommodate standard 30 mm low-profile DIMM's with 3 mm to spare and supports the use of two HIMs on the same riser using low-profile PCIe cards. A single HIM has a restricted component height, ˜10 mm versus 14.47 mm in PCIe standard. There is a requirement to reposition the enclosure spigot for the controller latch 340.
The table below provides a comparison of the prior art symmetric design of canisters with the improved asymmetric design of canisters.
As can be seen from the above, the use of the asymmetric design has numerous advantageous features when compared with the prior art symmetric design, all of which stem from the increased size of the controller canister 300. If a high availability configuration is being used (final row of the table), then two enclosures 310a, 310b will be needed in the cabinet to provide two individual controller canisters 300a, 300b.
The table above shows the advantages of the asymmetric arrangement of canisters over current SBB designs. The table assumes a layout such as the IBM Storwize V7000 with the two canisters stacked one above the other, as shown in
Number | Date | Country | Kind |
---|---|---|---|
1211918 | Jul 2012 | GB | national |
Number | Name | Date | Kind |
---|---|---|---|
5379184 | Barraza et al. | Jan 1995 | A |
5761033 | Wilhelm | Jun 1998 | A |
7069358 | Sakakibara et al. | Jun 2006 | B2 |
7200008 | Bhugra | Apr 2007 | B1 |
7304855 | Milligan et al. | Dec 2007 | B1 |
7800894 | Davis | Sep 2010 | B2 |
8756440 | Clemo et al. | Jun 2014 | B2 |
10257953 | Judd | Apr 2019 | B2 |
20030033363 | Garnett et al. | Feb 2003 | A1 |
20040103261 | Honda | May 2004 | A1 |
20060039108 | Chikusa et al. | Feb 2006 | A1 |
20060048001 | Honda | Mar 2006 | A1 |
20060101179 | Lee | May 2006 | A1 |
20060134936 | Sullivan et al. | Jun 2006 | A1 |
20060221579 | Liang et al. | Oct 2006 | A1 |
20060265449 | Uemura | Nov 2006 | A1 |
20080037218 | Sharma et al. | Feb 2008 | A1 |
20080055875 | Berke | Mar 2008 | A1 |
20080130219 | Rabinovitz | Jun 2008 | A1 |
20080191590 | Lin et al. | Aug 2008 | A1 |
20080257639 | Yamaguchi | Oct 2008 | A1 |
20090135558 | Hughes | May 2009 | A1 |
20100082874 | Baba | Apr 2010 | A1 |
20100172087 | Jeffery et al. | Jul 2010 | A1 |
20110072290 | Davis | Mar 2011 | A1 |
20110083992 | Stuhlsatz et al. | Apr 2011 | A1 |
20110261526 | Atkins et al. | Oct 2011 | A1 |
20150092788 | Kennedy et al. | Apr 2015 | A1 |
20190166711 | Judd | May 2019 | A1 |
Number | Date | Country |
---|---|---|
2378822 | Feb 2003 | GB |
2008171386 | Jul 2008 | JP |
2010097132 | Sep 2010 | WO |
2013162586 | Oct 2013 | WO |
Entry |
---|
Notice of Allowance, dated Jan. 7, 2021, for U.S. Appl. No. 16/262,906, filed Jan. 30, 2019, Total 13 pages. |
List of IBM Patents or Patent Applications Treated as Related, dated Aug. 1, 2019, 2 pages. |
Final Office Action, dated Nov. 27, 2019, for U.S. Appl. No. 16/262,906, filed Jan. 30, 2019, Total 26 pages. |
Response to Final Office Action2, dated Nov. 24, 2020, for U.S. Appl. No. 16/262,906, filed Jan. 30, 2019, Total 8 pages. |
Pre Appeal Brief, dated Nov. 23, 2020, for U.S. Appl. No. 16/262,906, filed Jan. 30, 2019, Total 6 pages. |
Respone to Final Office Action, dated Feb. 2, 2020, for U.S. Appl. No. 16/262,906, filed Jan. 30, 2019, Total 8 pages. |
Office Action3, dated Mar. 18, 2020, for U.S. Appl. No. 16/262,906, filed Jan. 30, 2019, Total 27 pages. |
Response to Office Action, dated Jun. 18, 2020 , for U.S. Appl. No. 16/262,906, filed Jan. 30, 2019, Total 12 pages. |
Final Office Action2, dated Sep. 28, 2020, for U.S. Appl. No. 16/262,906, filed Jan. 30, 2019, Total 24 pages. |
Machine Translation for JP2008171386, published Jul. 28, 2004, pp. 1-29. |
“Storage Bridge Bay Specification”, dated Sep. 21, 2006, Storage Bridge Bay Working Group, Version 1.0, pp. 1-87. |
S. Bohac et al., “Enterprise Disk Storage Subsystem Directions”, dated Jun. 2009, White Paper, pp. 1-10. |
International Search Report, dated Nov. 1, 2012, for Application No. GB1211918.6, filed Jul. 5, 2012, pp. 1-4. |
Office Action, dated Mar. 10, 2016, for U.S. Appl. No. 13/933,059, filed Jul. 1, 2013, Total 10 pages. |
Response to Office Action, dated Jun. 10, 2016, for U.S. Appl. No. 13/933,059, filed Jul. 1, 2013, Total 10 pages. |
Final Office Action, dated Sep. 28, 2016, for U.S. Appl. No. 13/933,059, filed Jul. 1, 2013, Total 18 pages. |
Response to Final Office Action, dated Dec. 26, 2016, for U.S. Appl. No. 13/933,059, filed Jul. 1, 2013, Total 11 pages. |
Office Action, dated Apr. 25, 2017, for U.S. Appl. No. 13/933,059, filed Jul. 1, 2013, Total 20 pages. |
Response to Office Action, dated Jul. 23, 2017, for U.S. Appl. No. 13/933,059, filed Jul. 1, 2013, Total 11 pages. |
Final Office Action, dated Oct. 4, 2017, for U.S. Appl. No. 13/933,059, filed Jul. 1, 2013, Total 19 pages. |
Pre-Appeal Brief Request for Review, dated Jan. 4, 2018, or U.S. Appl. No. 13/933,059, filed Jul. 1, 2013, Total 9 pages. |
Office Action, dated Jun. 11, 2018, for U.S. Appl. No. 13/933,059, filed Jul. 1, 2013, Total 19 pages. |
Response to Office Action, dated Sep. 11, 2018, for U.S. Appl. No. 13/933,059, filed Jul. 1, 2013, Total 8 pages. |
Notice of Allowance, dated Nov. 19, 2018, for U.S. Appl. No. 13/933,059, filed Jul. 1, 2013, Total 9 pages. |
Preliminary Amendment for U.S. Appl. No. 16/262,906, dated Jan. 30, 2019, 8 pp. |
Office Action 1 for U.S. Appl. No. 16/262,906, dated Apr. 8, 2019, 25 pp. |
Response to Office Action 1 for U.S. Appl. No. 16/262,906, dated Jul. 8, 2019, 11 pp. |
Number | Date | Country | |
---|---|---|---|
20190357374 A1 | Nov 2019 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 16262906 | Jan 2019 | US |
Child | 16529784 | US | |
Parent | 13933059 | Jul 2013 | US |
Child | 16262906 | US |