WO2010150321A1 - Storage system and controlling methods for the same - Google Patents

Storage system and controlling methods for the same Download PDF

Info

Publication number
WO2010150321A1
WO2010150321A1 PCT/JP2009/002947 JP2009002947W WO2010150321A1 WO 2010150321 A1 WO2010150321 A1 WO 2010150321A1 JP 2009002947 W JP2009002947 W JP 2009002947W WO 2010150321 A1 WO2010150321 A1 WO 2010150321A1
Authority
WO
WIPO (PCT)
Prior art keywords
cluster
storage
storage device
protocols
processing unit
Prior art date
Application number
PCT/JP2009/002947
Other languages
French (fr)
Inventor
Hidehisa Shitomi
Takuya Okamoto
Original Assignee
Hitachi, Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Hitachi, Ltd. filed Critical Hitachi, Ltd.
Priority to EP09787895A priority Critical patent/EP2446345A1/en
Priority to PCT/JP2009/002947 priority patent/WO2010150321A1/en
Priority to CN200980157791.6A priority patent/CN102341777B/en
Priority to JP2011547070A priority patent/JP5255127B2/en
Priority to US12/526,664 priority patent/US8347028B2/en
Publication of WO2010150321A1 publication Critical patent/WO2010150321A1/en
Priority to US13/693,114 priority patent/US20130097400A1/en

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0638—Organizing or formatting or addressing of data
    • G06F3/0644—Management of space entities, e.g. partitions, extents, pools
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
    • G06F3/0604—Improving or facilitating administration, e.g. storage management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
    • G06F3/061—Improving I/O performance
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
    • G06F3/0614—Improving the reliability of storage systems
    • G06F3/0617—Improving the reliability of storage systems in relation to availability
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0629—Configuration or reconfiguration of storage systems
    • G06F3/0635—Configuration or reconfiguration of storage systems by changing the path, e.g. traffic rerouting, path reconfiguration
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0646—Horizontal data movement in storage systems, i.e. moving data in between storage devices or systems
    • G06F3/0647—Migration mechanisms
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
    • G06F3/067—Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H04L67/125—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/18—Multiprotocol handlers, e.g. single devices capable of handling multiple protocols

Definitions

  • This invention relates to a storage system and controlling methods for the same, specifically to the technology of optimizing the performance separation according to the usage status of the protocol and the storage system performance.
  • LPARs Logical Partitions
  • PTL 1 discloses that, in a cluster-type storage system in which multiple, relatively small-scale storage systems (cluster) are connected by the interconnection network and used as one system, for the purpose of solving the problem that the logical partitioning in the range of the limited bandwidth of the interconnection network cannot ensure the performance deserving the resources allocated to the Logical Partitions, the resources of the same cluster are allocated to each Logical Partition.
  • PTL 2 discloses that, for the purpose of efficiently utilizing the unused resources in the storage system, the control processor logically partitions the resources including the host I/F, the drive I/F, the disk drive, the data transfer engine, the cache memory and the control processor as the target of partitioning and configures multiple Logical Partitions, and dynamically changes the partitioning ratio for each Logical Partition depending on the number of accesses from the host computer.
  • PTL 3 discloses that, when managing Logical Partitions of the subsystem for which storage consolidation has been performed, for preventing the operational errors by the administrator or others when changing the RAID configuration, the function of changing the RAID configuration is allowed to be released in a specified range.
  • COS Cloud Optimized Storages
  • TCO Total Cost of Ownership
  • iSCSI Internet Small Computer System Interface
  • NFS/CIFS Network File System
  • CIFS Common Internet File System
  • FC Fibre Channel
  • This invention is intended in view of the above-mentioned background for the purpose of providing the storage system and the controlling methods for the same which can optimize the performance separation according to the usage status of the protocol and the storage system performance.
  • An aspect of this invention for solving the above-mentioned and other problems is a storage system comprising multiple storage devices, the storage device including: a storage controlling unit writing data to a storage and reading data from the storage according to data input/output requests transmitted from an external device; and a protocol processing unit responding to the processing result for the input/output requests to the external device and being capable of responding to the data input/output requests following at least two or more protocols transmitted from the external device; wherein each of the storage devices includes a cluster processing unit configuring a cluster along with the other storage devices for the external device, and the cluster processing unit can configure cluster groups for each of the protocols.
  • Another aspect of this invention is the above-mentioned storage system, wherein the storage device stores a cluster management table in which the protocols handled by the cluster groups to which the storage devices belong are managed, and the cluster processing unit configures a cluster group for each of the protocols by forwarding or redirecting the data input/output requests transmitted from the external device to the other storage devices according to the cluster management table.
  • This invention enables easy configuration of cluster groups for each of the protocols by the cluster management table in which the protocols handled by the cluster group to which the storage devices belong are managed and the forwarding or redirecting function included in the cluster processing unit.
  • Another aspect of this invention is the above-mentioned storage system, wherein if cluster groups for each of the protocols are configured, the cluster processing unit inactivates resources for achieving the protocols other than the protocol handled by the cluster group to which the storage device belongs among the resources for processing the protocols in the storage device.
  • the storage device stores the cluster management table in which the protocols handled by the cluster group to which each of the storage devices belongs are managed, the storage device provides the storage area of the storage in units of logical volumes which are the logically set storage area to the external device, and if the contents of the cluster management table are changed when the cluster group for each of the protocols has already been configured and if the protocol to which the logical volumes corresponded do not match the protocol which the storage device to which the relevant logical volume belongs is supposed to handle after the change, the cluster processing unit migrates the data of the logical volume to the logical volume of the storage device of the other storage device which is supposed to handle the protocol after the change with which the relevant logical volume corresponded.
  • the cluster processing unit automatically migrates the data to the logical volume of the other storage device matching the protocol to which the logical volume corresponds. Therefore, for example, by changing the cluster management table from a management device, the configuration of the cluster groups can be changed easily and flexibly.
  • the storage device stores the cluster management table in which the protocols handled by the cluster group to which each of the storage devices belongs are managed
  • the storage device provides the storage area of the storage in units of logical volumes which are the logically set storage area to the external device, and if the contents of the cluster management table are changed to adding the storage device newly to the already configured cluster group when the cluster groups for each of the protocols have already been configured
  • the cluster processing unit determines whether it is necessary to relocate the data or not according to load information of the logical volume, and if it is determined to be necessary, migrates the data between the logical volumes.
  • the cluster processing unit determines whether it is necessary to relocate the data or not according to the load information of the logical volume, and if it is determined to be necessary, migrates the data between the logical volumes.
  • this invention enables easy addition of a new storage device to the already configured cluster group by changing the contents of the cluster management table. It is also possible to optimize the performance of the storage system by attempting load distribution at the time of relocation.
  • the storage device stores the cluster management table in which the protocols handled by the cluster group to which each of the storage devices belongs are managed
  • the storage device provides the storage area of the storage in units of logical volumes which are the logically set storage area to the external device, and if the contents of the cluster management table are changed to deleting the storage device from the already configured cluster group when the cluster groups for each of the protocols have already been configured, the cluster processing unit migrates the data of the logical volume of the storage device to be deleted to the logical volume of the other storage device handling the protocol which the relevant storage device used to handle.
  • the cluster processing unit migrates the data to the logical volume of the other storage device handling the protocol which the relevant storage device used to handle.
  • this invention enables easy deletion of a storage device from the already configured cluster group by changing the contents of the cluster management table.
  • the storage device stores the cluster management table in which the protocols handled by the cluster group to which each of the storage devices belongs are managed
  • the storage device provides the storage area of the storage in units of logical volumes which are the logically set storage area to the external device, and if the contents of the cluster management table are changed to migrating the storage device configuring a certain cluster group to the other cluster group when the cluster groups for each of the protocols have already been configured, the cluster processing unit determines whether it is necessary to relocate the data or not according to the load information of the logical volume, and if it is determined to be necessary, migrates the data between the logical volumes.
  • the cluster processing unit determines whether it is necessary to relocate the data or not according to the load information of the logical volume, and if it is determined to be necessary, migrates the data between the logical volumes.
  • this invention enables easy migration of a storage device configuring a certain cluster group to the other cluster group by changing the contents of the cluster management table. It is also possible to optimize the performance of the storage system by attempting load distribution at the time of relocation.
  • the protocol is at least one of iSCSI (Internet Small Computer System Interface), NFS/CIFS (NFS: Network File System, CIFS: Common Internet File System), and FC (Fibre Channel).
  • iSCSI Internet Small Computer System Interface
  • NFS/CIFS NFS/CIFS
  • CIFS Common Internet File System
  • FC Fibre Channel
  • Fig. 1 is a schematic diagram of the configuration of the storage system 1.
  • Fig. 2 is a diagram showing the functions of the client device 1000, the management device 1100, and the storage device 2400.
  • Fig. 3 is a diagram showing the operations of the storage device 2400.
  • Fig. 4 is a diagram showing the method of accessing the LU 2420 when newly installing a Unified Storage.
  • Fig. 5 is a diagram showing the case of achieving a cluster by forwarding.
  • Fig. 6 is a diagram showing an example of the cluster management table 2517.
  • Fig. 7 is a diagram showing the case of achieving a cluster by redirection.
  • Fig. 8 is a diagram showing the case of setting cluster groups 2812 in units of protocols.
  • Fig. 9 is an example of the cluster management table 2517.
  • Fig. 10 is a flowchart showing the cluster group setting processing S1000.
  • Fig. 11 is a diagram showing the case of changing the settings of the cluster groups 2812.
  • Fig. 12 is a flowchart showing the setting changing processing S1200.
  • Fig. 13 is an example of the volume management table 1300.
  • Fig. 14 is a flowchart showing the migration processing 1234.
  • Fig. 15 is a diagram showing the case of adding a new node to the cluster group 2812.
  • Fig. 16 is a flowchart showing the node addition processing S1600.
  • Fig. 17 is a diagram showing the case of deleting a node from the cluster group 2812.
  • Fig. 18 is a flowchart showing the node deletion processing S1800.
  • Fig. 19 is a diagram showing the case of migrating a node between the cluster groups 2812.
  • Fig. 20 is a flowchart showing the node migration processing S2000.
  • FIG. 1 shows the schematic view of the configuration of the storage system 1 described as an embodiment.
  • this storage system 1 includes multiple storage devices 2400, one or more client devices 1000 (external device), and a management device 1100 installed in the first site 6000 such as a data center, a system operation center or others.
  • the client device 1000 and the storage device 2400 are connected as communicable via a data network 5000.
  • the data network 5000 is, for example, LAN (Local Area Network), WAN (Wide Area Network), or SAN (Storage Area Network).
  • the storage device 2400 is connected as communicable with the management device 1100 via a management network 5001.
  • the management network 5001 is, for example, LAN or WAN.
  • the storage device 2400 is connected as communicable with the other storage systems installed in the other sites (the second site 7000 and the third site 8000) via an internal network 5002 and an external network 5003.
  • the internal network 5002 is, for example, LAN, WAN, or SAN.
  • the external network 5003 includes LAN, WAN, SAN, the Internet, a public telecommunication network and exclusive lines. Note that it is also possible to achieve the data network 5000, the management network 5001, the internal network 5002, and the external network 5003 by sharing the same physical communication media by a method of logically partitioning the communication bandwidth such as VLAN (Virtual LAN).
  • VLAN Virtual LAN
  • the client device 1000 is the device for accessing the storage device 2400 and transmits data input/output requests (data write requests/data read requests) to the storage device 2400.
  • the client device 1000 transmits data input/output requests in units of blocks or files to the storage device 2400.
  • the client device 1000 is an information processing device (computer) such as a personal computer, an office computer, mainframe or others.
  • the client device 1000 includes at least a processor 1001 (e.g. a CPU (Central Processing Unit) or an MPU (Micro Processing Unit)), a memory 1002 (e.g. a volatile or non-volatile RAM (Random Access Memory) or a ROM (Read Only Memory)), and a communication interface 1003 (e.g. NIC (Network Interface Card) or an HBA (Host Bus Adaptor)).
  • the client device 1000 may also include a storage (e.g. hard disk or a semiconductor storage device (SSD (Solid State Drive))), inputting devices such as a keyboard, a mouse and others, and outputting devices such as liquid crystal monitors and printers.
  • SSD Solid State Drive
  • the communication between the client device 1000 and the storage devices 2400 is performed according to the protocols of, for example, TCP/IP, FICON (Fibre Connection, registered trademark), ESCON (Enterprise System Connection, registered trademark), ACONARC (Advanced Connection Architecture, registered trademark), FIBARC (Fibre Connection Architecture, registered trademark), and others.
  • the management device 1100 is an information processing device (computer) such as a personal computer, an office computer, or others.
  • the management device 1100 includes at least a processor 1101 (e.g. a CPU or an MPU), a memory 1002 (e.g. a volatile or non-volatile RAM or a ROM), and a communication interface 1003 (e.g. NIC or an HBA).
  • a processor 1101 e.g. a CPU or an MPU
  • memory 1002 e.g. a volatile or non-volatile RAM or a ROM
  • a communication interface 1003 e.g. NIC or an HBA
  • the management device 1100 may also include a storage (e.g. a hard disk or a semiconductor storage device (SSD (Solid State Drive))), inputting devices such as a keyboard, a mouse and others, and outputting devices such as liquid crystal monitors and printers.
  • the management device 1100 is connected as communicable with the storage devices 2400 via the management network 5001.
  • the management device 1100 includes a user interface of GUI (Graphical User Interface), CLI (Command Line Interface), or others, and provides the functions for the user or the operator to control or monitor the storage devices 2400. It is also possible for the management device 1100 to be part of the storage device 2400.
  • GUI Graphic User Interface
  • CLI Common Line Interface
  • the storage device 2400 includes a header device 2500, a drive controlling device 2100, and a storage drive 2200 (storage). Each of the header device 2500, the drive controlling device 2100, and the storage drive 2200 may be packed in a separate chassis, or at least some of these may be packed in the same chassis. The functions of the header device 2500 and the drive controlling device 2100 may also be achieved by the common hardware.
  • the storage device 2400 is a Unified Storage corresponding to multiple protocols (such as iSCSI (Internet Small Computer System Interface), NFS/CIFS (NFS: Network File System, CIFS: Common Internet File System), FC (Fibre Channel), etc.) (i.e., capable of responding to the data input/output requests following multiple protocols).
  • protocols such as iSCSI (Internet Small Computer System Interface), NFS/CIFS (NFS: Network File System, CIFS: Common Internet File System), FC (Fibre Channel), etc.
  • the header device 2500 includes external communication interfaces 2504, 2505, 2507 (e.g. NIC and HBA) for the connection with the data network 5000, the management network 5001, and the internal network 5002, and the internal communication interface 2506 (e.g. NIC, HBA, PCI (Peripheral Component Interconnect), and PCI-Express (registered trademark)) for the communication with the processor 2501 (e.g. a CPU, an MPU, a DMA (Direct Memory Access), or a custom LSI (Large Scale Integration)), a memory 2502 (volatile or non-volatile RAM or ROM), a cache memory 2503 (volatile or non-volatile RAM), and the drive controlling device 2100.
  • the processor 2501 e.g. a CPU, an MPU, a DMA (Direct Memory Access), or a custom LSI (Large Scale Integration)
  • a memory 2502 volatile or non-volatile RAM or ROM
  • cache memory 2503 volatile or non
  • the header device 2500 includes functions for performing the control related to the protocols (e.g. NAS, iSCSI, NFS/CIFS, and FC) required for the communication with the client device 1000, functions related to file control (file system), and a function of caching data and data input/output requests exchanged with the client device 1000.
  • the details of the functions included in the header device 2500 are described later.
  • the drive controlling device 2100 includes external communication interfaces 2104 and 2105 (e.g. NIC, HBA, PCI, and PCI-Express) for the connection with the header device 2500 and the management network 5001, a processor 2101 (e.g. a CPU, an MPU, a DMA or a custom LSI), a memory 2102 (volatile or non-volatile RAM or ROM), a cache memory 2103 (volatile or non-volatile RAM), and a drive communication interface 2106 (e.g. SAS (Serial Attached SCSI), SATA (Serial ATA), PATA (Parallel ATA), FC, or SCSI) for the communication with the storage drive.
  • SAS Serial Attached SCSI
  • SATA Serial ATA
  • PATA Parallel ATA
  • FC or SCSI
  • the drive controlling device 2100 reads or writes data from or to the storage drive 2200 according to the data input/output requests (hereinafter referred to as drive access requests) transmitted from the header device 2500.
  • the drive controlling device 2100 includes various functions for safely or efficiently utilizing the storage drive 2200 such as the function of controlling the storage drive 2200 by RAID (Redundant Arrays of Inexpensive (or Independent) Disks), the function of providing logical storage devices (LDEVs (Logical DEVices) to the header device 2500 and the client device), the function of verifying the soundness of the data, the function of obtaining snapshots, and others.
  • RAID Redundant Arrays of Inexpensive (or Independent) Disks
  • LDEVs Logical DEVices
  • the details of the functions included in the drive control device 2100 are described later.
  • the storage drive 2200 is, for example, a hard disk drive conforming to the specified standards (SAS, SATA, FC, PATA, or SCSI), a JBOD (Just a Bunch Of Disks) configured of multiple hard disk drives, or a semiconductor storage device (SSD (Solid State Drive)).
  • Fig. 2 shows the functions of the client device 1000, the management device 1100, and the storage device 2400.
  • application software hereinafter referred to as an application 1011
  • the application 1011 is the software for providing, for example, file sharing, Email, database or others.
  • the communication client 1012 communicates with the storage device 2400 (e.g. transmitting data input/output requests and receiving the responses for the same). For the above-mentioned communication, the communication client 1012 performs the processing (e.g. format conversion and communication control) related to the protocols (e.g. iSCSI, NFS/CIFS, and FC). Note that these functions are achieved by the processor 1001 of the client device 1000 reading the programs stored in the memory 1002.
  • the processing e.g. format conversion and communication control
  • the protocols e.g. iSCSI, NFS/CIFS, and FC.
  • the management device 1100 includes a management unit 1111.
  • the management unit 1111 sets, controls, and monitors the operations of the storage device 2400.
  • the management unit 1111 is achieved by the processor 1101 of the management device 1100 through reading and executing the programs stored in the memory 1102.
  • the functions of the management unit 1111 may be achieved either by a different device from the storage device 2400 or by the storage device 2400.
  • the header device 2500 of the storage device 2400 includes an operating system 2511 (including driver software), a volume management unit 2512, a file system 2513, one or more communication servers 2514 (Protocol Servers) (protocol processing units), and a cluster processing unit 2516. Note that these functions are achieved by the hardware of the header device 2500 or by the processor 2501 reading the programs stored in the memory 2502.
  • the volume management unit 2512 provides the virtual storage area (hereinafter referred to as a virtual volume)based on the logical storage area provided by the storage drive 2200 to the client device 1000.
  • the file system 2513 accepts data input/output requests from the client device 1000 by a file specification method.
  • the header device 2500 operates as the NAS (Network Attached Storage) server in the data network 5000. Note that, though the description of this embodiment assumes the header device 2500 to include the file system 2513, the header device 2500 does not necessarily include the file system 2513.
  • the header device 2500 may accept data input/output requests by an LBA (Logical Block Address) specification method.
  • LBA Logical Block Address
  • the communication server 2514 communicates with the communication client 1012 of the client device 1000 and the management unit 1111 of the management device 1100. For the above-mentioned communication, the communication server 2514 performs the processing related to the protocols (e.g. iSCSI, NFS/CIFS, and FC) (e.g. format conversion and communication control).
  • protocols e.g. iSCSI, NFS/CIFS, and FC
  • FC format conversion and communication control
  • the cluster processing unit 2516 processes the data input/output requests following the previously set cluster definition. For example, if the data input/output request received from the client device 1000 addresses itself, the cluster processing unit 2516 processes the data input/output requests by itself. If the received data input/output request addresses the other storage device 2400, it transmits the relevant data input/output request to the other storage device 2400 handling the processing of the data input/output request.
  • the cluster processing unit 2516 manages the above-mentioned cluster definitions in a cluster management table 2517.
  • the drive device 2000 of the storage device 2400 includes a storage controlling unit 2410.
  • the storage controlling unit 2410 provides the logical volume (hereinafter referred to as an LU 2420 (LU: Logical Unit)) as a logical storage area based on the storage drive 2200 to the header device 2500.
  • the header device 2500 can specify an LU 2420 by specifying an identifier of the LU 2420 (LUN (Logical Unit Number)).
  • LUN Logical Unit Number
  • the function of the storage controlling unit 2410 is achieved, for example, by the LVM (Logical Volume Manager).
  • Unified Storage Fig. 3 is a diagram showing the operations of the storage device 2400.
  • the storage device 2400 is a Unified Storage corresponding to multiple protocols (iSCSI, NFS/CIFS, FC) (i.e. capable of responding to the data input/output requests following multiple protocols).
  • the storage device 2400 shown in the figure corresponds to the both protocols of NFS and iSCSI and includes a communication server 2514 operating as an NFS server and a communication server 2514 operating as an iSCSI target.
  • the above-mentioned communication server 2514 operating as an NFS server accepts data input/output requests transmitted from the communication client 1012 operating as an NFS client of the client device 1000.
  • the above-mentioned communication server 2514 operating as an iSCSI target accepts data input/output requests transmitted from the communication client 1012 operating as an iSCSI initiator of the client device 1000.
  • FIG. 4 is a diagram showing the method of accessing the LU 2420 when newly installing the second storage device 2400 as a Unified Storage in the storage system 1 configured by using the first storage device 2400 as a Unified Storage for the purpose of enhancement of resources (performance, capacity and others) and the like.
  • the user or the operator adds the second storage device 2400 by performing the setting of the LU 2420 to mount on each client device 1000, the setting of the access path from the client device 1000 to the LU 2420, and other settings, by using the user interface provided by the management unit 1111 of the management device 1100.
  • the storage devices 2400 (the first storage device 2400 and the second storage device 2400) are recognized as two independent devices by the client device 1000.
  • Cluster Fig. 5 similarly to Fig. 4, shows the case of newly installing the second storage device 2400. However, it is different from Fig. 4 in that a cluster 2811 is configured by using two storage devices 2400, the first storage device 2400 and the second storage device 2400. If the cluster 2811 is configured by this method, the first storage device 2400 and the second storage device 2400 are recognized as one virtual storage system by the client device 1000. Such a cluster 2811 can achieve the data input/output requests transmitted from the client device 1000, for example, by forwarding or redirecting the requests in the storage device 2400.
  • Fig. 5 is a diagram showing the case of achieving a cluster 2811 by forwarding
  • Fig. 7 is a diagram showing the case of achieving a cluster 2811 by redirection.
  • the cluster processing unit 2516 firstly identifies the storage device 2400 which should process the data input/output request received from the client device 1000. Then, the cluster processing unit 2516 processes the request if the request is the data input/output request which should be processed by itself, and if the request is the data input/output request which should be processed by the other storage device 2400, transfers the received data input/output request to the other storage device 2400.
  • Fig. 6 is information referred to by the cluster processing unit 2516 (hereinafter referred to as the cluster management table 2517) when identifying the storage device 2400 which should process the data input/output request.
  • the cluster management table 2517 includes one or more records consisting of a cluster name 611 and a node 612.
  • a cluster ID an identifier given to each of the configured cluster groups
  • a device ID an identifier of the storage device 2400 as a component of each cluster
  • the cluster processing unit 2516 firstly identifies the storage device 2400 which should process the data input/output request received from the client device 1000 by referring to the cluster management table 2517. Then, the cluster processing unit 2516 processes the request if the request is the data input/output request which should be processed by itself and, if the request is the data input/output request which should be processed by the other storage device 2400, notifies the redirecting address (the other storage device 2400 identified (e.g. network address)) to the client device 1000 which transmitted the received data input/output request. The client device 1000 which has received the notification retransmits the data input/output request to the notified redirecting address.
  • the redirecting address the other storage device 2400 identified (e.g. network address
  • cluster group 2812 Cluster Group in Units of Protocols
  • a group of clusters (hereinafter referred to as a cluster group 2812) can be set in units of protocols by using the characteristics of the Unified Storages (capable of corresponding to multiple protocols).
  • Fig. 8 is a diagram showing the case of setting cluster groups 2812 in units of protocols (each with the NFS server and the iSCSI target shown in the figure).
  • Cluster groups 2812 can also be achieved by preparing the above-mentioned cluster management table 2517 and performing forwarding or redirection.
  • Fig. 9 is an example of the cluster management table 2517 used for managing the cluster group 2812.
  • the cluster management table 2517 includes one or more records consisting of a cluster name 911, a node 912, a role 913, and a node 914.
  • a cluster ID an identifier given to each of the configured clusters
  • a device ID an identifier of the storage device 2400 as a component of each cluster
  • a protocol ID an identifier for identifying the protocol supported by each cluster group 2812
  • a protocol ID an identifier of the storage device 2400 allocated to each role is set.
  • a group of storage devices 2400 with the cluster name 911 of "Cluster 1" and the node 914 of "10.1.1.1-10.1.1.5” configure the cluster group 2812 with the NFS server of the role 913 of "NAS-1".
  • a group of storage devices 2400 with the cluster name 911 of "Cluster 1" and the node 914 of "10.1.1.6-10.1.1.10” configure the cluster group 2812 with the iSCSI server of the role 913 of "iSCSI-1".
  • a group of storage devices 2400 with the cluster name 911 of "Cluster 2" and the node 914 of "10.1.1.11-10.1.1.15" configure the cluster group 2812 with the FC (Fibre Channel) server of the role 913 of "FC-1".
  • a group of storage devices 2400 with the cluster name 911 of "Cluster 2" and the node 914 of "10.1.1.15-10.1.1.20” configure the cluster group 2812 with the NFS server of the role 913 of "NAS-2".
  • a cluster group 2812 for setting a cluster group 2812 in units of protocols, it can be considered to inactivate resources (hardware resources and software resources) for achieving the protocols unused by each storage device 2400.
  • Fig. 8 shows the active resources in full lines and inactive resources in dashed lines. As shown in the figure, by inactivating the resources of the unused protocols, the processing load on the storage device 2400 can be reduced, and the storage device 2400 can be efficiently operated.
  • Initial Setting Fig. 10 is a flowchart showing the processing performed when the user or the operator performs initial setting of a cluster 2811 and a cluster group 2812 by operating the management device 1100 (hereinafter referred to as the cluster setting processing S1000). Note that the letter "S" added to the head of the numerals in the description below indicates a step.
  • the management unit 1111 of the management device 1100 accepts setting information of the cluster 2811 and setting information of the cluster group 2812 from the user or the operator (S1011 to S1012). At this time, the management unit 1111 accepts the setting information, for example, by displaying the setting screen of the cluster management table 2517 shown in Fig. 9.
  • the management unit 1111 transmits the accepted setting information to the storage device 2400 via the management network 5001 (S1013).
  • the cluster processing unit 2516 of each storage device 2400 receives the setting information transmitted from the management device 1100 (S1021), and reflects the received setting information in the cluster management table 2517 (S1022). After reflecting the setting information in the cluster management table 2517, the cluster processing unit 2516 of each storage device 2400 transmits a registration completion report to the management device 1100 (S1023).
  • the management unit 1111 Upon reception of the registration completion report (S1031), the management unit 1111 transmits a resource setting command the (command for setting activation or inactivation) (S1032) to the cluster processing unit 2516 of each storage device 2400.
  • the cluster processing unit 2516 of each storage device 2400 activates the resources related to the protocols which it handles, and inactivates the resources related to the protocols which it does not handle (S1042).
  • This series of processing (S1031, 1032, 1041, and 1042) is not mandatory, but it may also be treated as an option. This may also be applied to the following descriptions.
  • the activation of software resources means starting the process of the software
  • the inactivation of software resources means terminating or deleting the process of the software.
  • the cluster processing unit 2516 according to the interface protocol allocated to the node, performs the operations of starting, terminating and deleting for the interface processing process (nfsd or iSCSI target software).
  • Fig. 12 is a flowchart showing the processing of changing the setting of cluster groups 2812 when clusters 2811 and cluster groups 2812 are already set in the storage system 1 (hereinafter referred to as the setting changing processing S1200).
  • the management unit 1111 of the management device 1100 accepts setting information of the cluster groups 2812 from the user or the operator (S1211).
  • the management unit 1111 accepts the setting information, for example, by displaying the setting screen of the cluster management table 2517 shown in Fig. 9.
  • the management unit 1111 transmits the accepted setting information to each of the storage devices 2400 via the management network 5001 (S1212).
  • the cluster processing unit 2516 of each storage device 2400 receives the setting information transmitted from the management device 1100 (S1221), and reflects the received setting information in the cluster management table 2517 (S1222). After reflecting the setting information in the cluster management table 2517, the cluster processing unit 2516 of each storage device 2400 transmits a registration completion report to the management device 1100 (S1223).
  • the management unit 1111 of the management device 1100 identifies the LU 2420which does not match the newly set setting of the cluster groups 2812 (after the change of the setting) (i.e. the LU not matching the usage of the cluster group 2812 after the change of the setting) (S1232).
  • such an LU 2420 is identified by referring to the information related to the LUs 2420 managed by each of the storage devices 2400.
  • Fig. 13 is a table shown as an example of such information (hereinafter referred to as the volume management table 1300).
  • the current usage 1312 (protocol) of each LU 2420 (LUN 1311) is managed.
  • the management unit 1111 determines the storage device 2400 as the migration destination of the LU 2420 identified at S1232 (hereinafter referred to as the migration destination storage device 2400) (S1233). This determination by the management unit 1111 is made, after the above-mentioned change of the setting, by selecting one of the storage devices 2400 supporting the protocols matching the usage of the LU 2420 identified at S1232 from the cluster management table 2517. Note that, if multiple migration destination storage devices 2400 can be selected at this step, the management unit 1111 selects the most appropriate one in view of, for example, the round-robin method, load distribution, the remaining capacity of the storage area and other factors.
  • Fig. 14 is a flowchart showing the details of the migration processing S1234.
  • the management unit 1111 of the management device 1100 selects one of the identified LUs 2420 (hereinafter referred to as the migration source LU 2420) (S1411).
  • the management unit 1111 transmits a command for obtaining the snapshot of the migration source LU 2420 to the storage device 2400 in which the selected migration source LU 2420 exists (hereinafter referred to as a migration source storage device 2400) (S1412).
  • the migration source storage device 2400 Upon reception of the command for obtaining the snapshot (S1413), the migration source storage device 2400 obtains the snapshot of the migration source LU 2420 (S1414).
  • the management unit 1111 transmits a command for creating the LU as the migration destination of the migration source LU 2420 (hereinafter referred to as a migration destination LU 2420) to the migration destination storage device 2400 determined at S1233 (S1421).
  • a migration destination LU 2420 a command for creating the LU as the migration destination of the migration source LU 2420 (hereinafter referred to as a migration destination LU 2420) to the migration destination storage device 2400 determined at S1233 (S1421).
  • the migration destination storage device 2400 creates the migration destination LU 2420 (S1423).
  • the management unit 1111 transmits a command for replicating the data stored in the migration source LU 2420 to the migration destination LU 2420 to the migration source storage device 2400 and the migration destination storage device 2400 (S1431).
  • the migration source storage device 2400 and the migration destination storage device 2400 transfers the snapshot obtained at S1414 from the migration source LU 2420 to the migration destination LU 2420 (S1434 and S1435).
  • a snapshot replication completion report is transmitted from the migration destination storage device 2400 (or migration source storage device 2400 may also be possible) to the management device 1100 (S1436).
  • the management device 1100 receives the transmitted replication completion report (S1437).
  • the migration source storage device 2400 is implemented with a function of performing the above-mentioned replication without suspending the services for the client device 1000 (hereinafter referred to as the fault-tolerant migration function)
  • differential data while the above-mentioned replication is in process is managed by the cache memory 2503 (which can be replaced by cache memory 2103) and the storage drive 2200, and after the replication is completed, the managed differential data is reflected in the migration destination LU 2420.
  • the management unit 1111 performs the processing for transiting the port connected with the migration source LU 2420 to the port connected with the migration destination LU 2420 (S1461).
  • This processing is performed by, for example, setting the IP address of the iSCSI port connected with the migration source LU 2420 to the IP address of the iSCSI port connected with the migration destination LU 2420. Note that it is preferable to perform this transition without changing the settings of the client device 1000 by, for example, changing the IP address by DNS (Domain Name Server (System)) rather than changing the service name or others before and after the migration.
  • DNS Domain Name Server
  • the management unit 1111 determines whether there are any LUs 2420 not selected at S1411. If there are any (S1462: YES), the processing returns to S1411. If not (S1462: NO), the migration processing S1234 is completed and returns to S1235 in Fig. 12.
  • the above-mentioned description of the migration processing S1234 assumes the use of the data replication function among the storage devices 2400 implemented in the storage devices 2400, but it is also possible to perform the data replication from the migration source LU 2420 to the migration destination LU 2420 by using the replication function implemented in the network switch configuring the data network 5000, the replication function installed in the client device 1000 or others.
  • the management unit 1111 transmits a resource setting command to the cluster processing unit 2516 of each storage device 2400 (S1235).
  • the cluster processing unit 2516 of each storage device 2400 performs the resource setting (activation or inactivation) according to the setting of its cluster group 2812 after the change (S1242).
  • the cluster processing unit 2516 automatically migrates the data to the LU 2420 of the other storage device 2400 matching the protocol corresponding to the LU 2420. Therefore, the configuration of the cluster groups 2812 can be changed easily and flexibly by, for example, changing the cluster management table 2517 from the management device 1100.
  • Fig. 16 is a flowchart showing the processing performed in this case (node addition processing S1600).
  • the node addition processing S1600 is described below by referring to the above-mentioned figure.
  • the management unit 1111 of the management device 1100 accepts setting information of adding a new node (the fifth storage device 2400 in the above-mentioned figure) to a cluster group 2812 from the user or the operator (S1611). At this time, the management unit 1111 accepts the setting information, for example, by displaying the setting screen of the cluster management table 2517 shown in Fig. 9.
  • the management unit 1111 transmits the above-mentioned accepted setting information to each storage device 2400 via the management network 5001 (S1612).
  • the cluster processing unit 2516 of each storage device 2400 receives the setting information transmitted from the management device 1100 (S1621), and reflects the received setting information in the cluster management table 2517 (S1622). After reflecting the setting information in the cluster management table 2517, the cluster processing unit 2516 of each storage device 2400 transmits a registration completion report to the management device 1100 (S1623).
  • the management unit 1111 Upon reception of the registration completion report (S1631), the management unit 1111 determines whether it is necessary to migrate the data (relocate the data) or not due to the addition of the node (S1632). This determination is made with reference to the load information of the LUs 2420 such as the usage status of each LU 2420 in each storage device 2400 or the port performance information connected with each LU 2420. If data migration is determined to be necessary (S1632: YES), the management unit 1111 starts a data migration processing (S1633). This migration processing S1633 is the same as the above-mentioned migration processing S1234 shown in Fig. 14.
  • the management unit 1111 transmits a resource setting command to the cluster processing unit 2516 of each storage device 2400 (S1635).
  • the cluster processing unit 2516 of each storage device 2400 performs the resource setting (activation or inactivation) according to the setting of its cluster group 2812 after the change (S1642).
  • the cluster processing unit 2516 determines whether it is necessary to relocate the data or not according to the load information of the LUs 2420, and if it is determined to be necessary, automatically migrates the data between the LUs 2420.
  • this method enables easy addition of a new storage device 2400 to the already configured cluster group 2812. It is also possible to optimize the performance of the storage system 1 by attempting load distribution at the time of relocation.
  • Fig. 18 is a flowchart showing the processing performed in this case (node deletion processing S1800).
  • the node deletion processing S1800 is described below by referring to Fig. 18.
  • the management unit 1111 of the management device 1100 accepts setting information of deleting a node (the first storage device 2400 in Fig.17) from a cluster group 2812 from the user or the operator (S1811). At this time, the management unit 1111 accepts the setting information, for example, by displaying the setting screen of the cluster management table 2517 shown in Fig. 9.
  • the management unit 1111 transmits the accepted setting information to each storage device 2400 via the management network 5001 (S1812).
  • the cluster processing unit 2516 of each storage device 2400 receives the setting information transmitted from the management device 1100 (S1821), and reflects the received setting information in the cluster management table 2517 (S1822). After reflecting the setting information in the cluster management table 2517, the cluster processing unit 2516 of each storage device 2400 transmits a registration completion report to the management device 1100 (S1823).
  • the management unit 1111 determines the storage device 2400 as the migration destination (hereinafter referred to as the migration destination storage device 2400) of the data stored in the LU 2420 (LU 2420 to be deleted) of the storage device 2400 to be deleted (S1832). This determination by the management unit 1111 is made, after the above-mentioned change of the setting, by selecting one of the storage devices 2400 supporting the protocols matching the usage of the LU 2420 to be deleted from the cluster management table 2517. Note that, if multiple migration destination storage devices 2400 can be selected at this step, the management unit 1111 selects the most appropriate one in view of, for example, the round-robin method, load distribution, the remaining capacity of the storage area and other factors.
  • the management unit 1111 starts to migrate the data stored in the LU 2420 of the first storage device 2400 to be deleted to the LU 2420 of another storage device 2400 determined at S1832 (S1833).
  • This migration processing is the same as the above-mentioned migration processing S1234 shown in Fig. 14.
  • the cluster processing unit 2516 migrates the data to the LU 2420 of another storage device 2400 handling the protocol which used to be handled by the relevant storage device 2400. This enables easy deletion of the storage device 2400 from the already configured cluster group 2812.
  • Fig. 20 is a flowchart showing the processing performed in this case (node transfer processing S2000).
  • the node transfer processing S2000 is described below by referring to Fig. 20.
  • the management unit 1111 of the management device 1100 accepts setting information of transferring a node (Fig. 19 shows the case of transferring the second storage device 2400 belonging to the cluster group 2812 of the NAS clusters to the cluster group 2812 (iSCSI clusters)) from the user or the operator (S2011). At this time, the management unit 1111 accepts the setting information, for example, by displaying the setting screen of the cluster management table 2517 shown in Fig. 9.
  • the management unit 1111 transmits the accepted setting information to each storage device 2400 via the management network 5001 (S2012).
  • the cluster processing unit 2516 of each storage device 2400 receives the setting information transmitted from the management device 1100 (S2021), and reflects the received setting information in the cluster management table 2517 (S2022). After reflecting the setting information in the cluster management table 2517, the cluster processing unit 2516 of each storage device 2400 transmits a registration completion report to the management device 1100 (S2023).
  • the management unit 1111 Upon reception of the registration completion report (S2031), the management unit 1111 determines whether it is necessary to migrate (relocate) the data or not (S2032). This determination is made with reference to the load information of the LUs 2420 such as the usage status of each LU 2420 in each storage device 2400 or the port performance information connected with each LU 2420. If data migration is determined to be necessary (S2032: YES), the management unit 1111 starts a data migration processing (S2033). This processing is the same as the migration processing S1234 shown in Fig. 14.
  • the management unit 1111 transmits a resource setting command to the cluster processing unit 2516 of each storage device 2400 (S2035).
  • the cluster processing unit 2516 of each storage device 2400 performs the resource setting (activation or inactivation) according to the setting of its cluster group 2812 after the change (S2042).
  • the cluster processing unit 2516 determines whether it is necessary to relocate the data or not according to the load information of the LUs 2420, and if it is determined to be necessary, automatically migrates the data between the LUs 2420.
  • this invention enables easy migration of a storage device 2400 configuring a certain cluster group 2812 to another cluster group by changing the contents of the cluster management table 2517. It is also possible to optimize the performance of the storage system by attempting load distribution at the time of relocation.
  • the storage system 1 in this embodiment enables the easy configuration of cluster groups 2812 for each protocol by using a storage device 2400 (Unified Storage) including the communication server 2514 (protocol processing unit) capable of responding to data input/output requests following at least two or more protocols transmitted from the client device 1000.
  • a storage device 2400 Unified Storage
  • the communication server 2514 protocol processing unit

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Human Computer Interaction (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Health & Medical Sciences (AREA)
  • Computing Systems (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

For the purpose of optimizing the performance separation according to the usage status of the protocol and the storage system performance, in a storage system 1 including multiple storage devices 2400 which includes a storage controlling unit 2410 performing data write to or data read from a storage drive 2200 according to data input/output requests from an external device 1000 and a protocol processing unit 2514 that responds to a processing result for the input/output requests to the external device 1000 and is capable of responding to data input/output requests transmitted from the external device 1000 following at least two or more protocols, in which each of the storage devices 2400 includes a cluster processing unit 2516 configuring clusters 2811 with the other storage devices 2400 for the external device 1000 and a cluster processing unit 2516, the cluster processing unit 2516 is set to configure cluster groups 2812 for each protocol.

Description

STORAGE SYSTEM AND CONTROLLING METHODS FOR THE SAME
This invention relates to a storage system and controlling methods for the same, specifically to the technology of optimizing the performance separation according to the usage status of the protocol and the storage system performance.
For achieving the efficient operation of the storage system, there is a technology of configuring clusters by partitioning the storage system into multiple Logical Partitions (LPARs) and providing the clusters as multiple separate storage systems from the user.
For example, PTL 1 discloses that, in a cluster-type storage system in which multiple, relatively small-scale storage systems (cluster) are connected by the interconnection network and used as one system, for the purpose of solving the problem that the logical partitioning in the range of the limited bandwidth of the interconnection network cannot ensure the performance deserving the resources allocated to the Logical Partitions, the resources of the same cluster are allocated to each Logical Partition.
PTL 2 discloses that, for the purpose of efficiently utilizing the unused resources in the storage system, the control processor logically partitions the resources including the host I/F, the drive I/F, the disk drive, the data transfer engine, the cache memory and the control processor as the target of partitioning and configures multiple Logical Partitions, and dynamically changes the partitioning ratio for each Logical Partition depending on the number of accesses from the host computer.
PTL 3 discloses that, when managing Logical Partitions of the subsystem for which storage consolidation has been performed, for preventing the operational errors by the administrator or others when changing the RAID configuration, the function of changing the RAID configuration is allowed to be released in a specified range.
Japanese Patent Application Laid-open Publication No. 2006-285808 Japanese Patent Application Laid-open Publication No. 2008-257572 Japanese Patent Application Laid-open Publication No. 2005-71103
The demand is expected to increase for COS (Cloud Optimized Storages) for the cloud service which, for achieving the low TCO (Total Cost of Ownership), can be started on a small scale with a small initial investment, catch up with the rapid growth (by Scale Out i.e. installing a new storage system while keeping the configuration of the existing storage system), and flexibly change the configuration.
Furthermore, storages capable of independently corresponding to multiple protocols (hereinafter referred to as Unified Storages) such as iSCSI (Internet Small Computer System Interface), NFS/CIFS (NFS: Network File System, CIFS: Common Internet File System), or FC (Fibre Channel) are starting to spread.
It is expected that, in the operation of the storage system for the cloud service using the Unified Storage of the Scale-Out configuration, for optimizing the performance, the demand for efficiently utilizing (partitioning) the resources included in the Unified Storage (such as the CPU and the cache memory) will be evident.
However, as the Unified Storage processes multiple protocols by the common CPU and the cache memory is also shared by the protocols, it is difficult to optimize the performance separation according to the usage status of each protocol and the storage system performance.
This invention is intended in view of the above-mentioned background for the purpose of providing the storage system and the controlling methods for the same which can optimize the performance separation according to the usage status of the protocol and the storage system performance.
An aspect of this invention for solving the above-mentioned and other problems is a storage system comprising multiple storage devices, the storage device including:
a storage controlling unit writing data to a storage and reading data from the storage according to data input/output requests transmitted from an external device; and
a protocol processing unit responding to the processing result for the input/output requests to the external device and being capable of responding to the data input/output requests following at least two or more protocols transmitted from the external device; wherein
each of the storage devices includes a cluster processing unit configuring a cluster along with the other storage devices for the external device, and
the cluster processing unit can configure cluster groups for each of the protocols.
Thus, by configuring cluster groups for each protocol by using the storage system using the storage device (Unified Storage) including the protocol processing unit capable of responding to the data input/output requests following at least two or more protocols transmitted from the external device, it becomes possible to optimize the performance separation according to the usage status of the protocol as well as the entire storage system performance.
Another aspect of this invention is the above-mentioned storage system, wherein
the storage device stores a cluster management table in which the protocols handled by the cluster groups to which the storage devices belong are managed, and
the cluster processing unit configures a cluster group for each of the protocols by forwarding or redirecting the data input/output requests transmitted from the external device to the other storage devices according to the cluster management table.
This invention enables easy configuration of cluster groups for each of the protocols by the cluster management table in which the protocols handled by the cluster group to which the storage devices belong are managed and the forwarding or redirecting function included in the cluster processing unit.
Another aspect of this invention is the above-mentioned storage system, wherein
if cluster groups for each of the protocols are configured, the cluster processing unit inactivates resources for achieving the protocols other than the protocol handled by the cluster group to which the storage device belongs among the resources for processing the protocols in the storage device.
As it is not necessary to activate protocols other than the protocol handled by the cluster group to which the storage device belongs, by inactivating such resources, the processing load on the storage device is reduced and the storage device can be efficiently operated.
Another aspect of this invention is the above-mentioned storage system, wherein
the storage device stores the cluster management table in which the protocols handled by the cluster group to which each of the storage devices belongs are managed,
the storage device provides the storage area of the storage in units of logical volumes which are the logically set storage area to the external device, and
if the contents of the cluster management table are changed when the cluster group for each of the protocols has already been configured and if the protocol to which the logical volumes corresponded do not match the protocol which the storage device to which the relevant logical volume belongs is supposed to handle after the change, the cluster processing unit migrates the data of the logical volume to the logical volume of the storage device of the other storage device which is supposed to handle the protocol after the change with which the relevant logical volume corresponded.
Thus, if the contents of the cluster management table are changed, the cluster processing unit automatically migrates the data to the logical volume of the other storage device matching the protocol to which the logical volume corresponds. Therefore, for example, by changing the cluster management table from a management device, the configuration of the cluster groups can be changed easily and flexibly.
Another aspect of this invention is the above-mentioned storage system, wherein
the storage device stores the cluster management table in which the protocols handled by the cluster group to which each of the storage devices belongs are managed,
the storage device provides the storage area of the storage in units of logical volumes which are the logically set storage area to the external device, and
if the contents of the cluster management table are changed to adding the storage device newly to the already configured cluster group when the cluster groups for each of the protocols have already been configured, the cluster processing unit determines whether it is necessary to relocate the data or not according to load information of the logical volume, and if it is determined to be necessary, migrates the data between the logical volumes.
As mentioned above, if the contents of the cluster management table are changed to adding the storage device newly to the already configured cluster group when the cluster groups for each of the protocols have already been configured, the cluster processing unit determines whether it is necessary to relocate the data or not according to the load information of the logical volume, and if it is determined to be necessary, migrates the data between the logical volumes. Thus, this invention enables easy addition of a new storage device to the already configured cluster group by changing the contents of the cluster management table. It is also possible to optimize the performance of the storage system by attempting load distribution at the time of relocation.
Another aspect of this invention is the above-mentioned storage system, wherein
the storage device stores the cluster management table in which the protocols handled by the cluster group to which each of the storage devices belongs are managed,
the storage device provides the storage area of the storage in units of logical volumes which are the logically set storage area to the external device, and
if the contents of the cluster management table are changed to deleting the storage device from the already configured cluster group when the cluster groups for each of the protocols have already been configured, the cluster processing unit migrates the data of the logical volume of the storage device to be deleted to the logical volume of the other storage device handling the protocol which the relevant storage device used to handle.
As mentioned above, if the contents of the cluster management table are changed to deleting the storage device from the already configured cluster group when the cluster groups for each of the protocols have already been configured, the cluster processing unit migrates the data to the logical volume of the other storage device handling the protocol which the relevant storage device used to handle. Thus, this invention enables easy deletion of a storage device from the already configured cluster group by changing the contents of the cluster management table.
Another aspect of this invention is the above-mentioned storage system, wherein
the storage device stores the cluster management table in which the protocols handled by the cluster group to which each of the storage devices belongs are managed,
the storage device provides the storage area of the storage in units of logical volumes which are the logically set storage area to the external device, and
if the contents of the cluster management table are changed to migrating the storage device configuring a certain cluster group to the other cluster group when the cluster groups for each of the protocols have already been configured, the cluster processing unit determines whether it is necessary to relocate the data or not according to the load information of the logical volume, and if it is determined to be necessary, migrates the data between the logical volumes.
As mentioned above, if the contents of the cluster management table are changed to migrating the storage device configuring a certain cluster group to the other cluster group when the cluster groups for each of the protocols have already been configured, the cluster processing unit determines whether it is necessary to relocate the data or not according to the load information of the logical volume, and if it is determined to be necessary, migrates the data between the logical volumes. Thus, this invention enables easy migration of a storage device configuring a certain cluster group to the other cluster group by changing the contents of the cluster management table. It is also possible to optimize the performance of the storage system by attempting load distribution at the time of relocation.
Note that the protocol is at least one of iSCSI (Internet Small Computer System Interface), NFS/CIFS (NFS: Network File System, CIFS: Common Internet File System), and FC (Fibre Channel).
The other problems and the means for solving for the same disclosed by this application are described in the embodiments and the attached figures.
By this invention, the performance separation according to the usage status of the protocol and the storage system performance can be optimized.
Fig. 1 is a schematic diagram of the configuration of the storage system 1. Fig. 2 is a diagram showing the functions of the client device 1000, the management device 1100, and the storage device 2400. Fig. 3 is a diagram showing the operations of the storage device 2400. Fig. 4 is a diagram showing the method of accessing the LU 2420 when newly installing a Unified Storage. Fig. 5 is a diagram showing the case of achieving a cluster by forwarding. Fig. 6 is a diagram showing an example of the cluster management table 2517. Fig. 7 is a diagram showing the case of achieving a cluster by redirection. Fig. 8 is a diagram showing the case of setting cluster groups 2812 in units of protocols. Fig. 9 is an example of the cluster management table 2517. Fig. 10 is a flowchart showing the cluster group setting processing S1000. Fig. 11 is a diagram showing the case of changing the settings of the cluster groups 2812. Fig. 12 is a flowchart showing the setting changing processing S1200. Fig. 13 is an example of the volume management table 1300. Fig. 14 is a flowchart showing the migration processing 1234. Fig. 15 is a diagram showing the case of adding a new node to the cluster group 2812. Fig. 16 is a flowchart showing the node addition processing S1600. Fig. 17 is a diagram showing the case of deleting a node from the cluster group 2812. Fig. 18 is a flowchart showing the node deletion processing S1800. Fig. 19 is a diagram showing the case of migrating a node between the cluster groups 2812. Fig. 20 is a flowchart showing the node migration processing S2000.
The embodiments are described below. Fig. 1 shows the schematic view of the configuration of the storage system 1 described as an embodiment. As shown in Fig. 1, this storage system 1 includes multiple storage devices 2400, one or more client devices 1000 (external device), and a management device 1100 installed in the first site 6000 such as a data center, a system operation center or others.
The client device 1000 and the storage device 2400 are connected as communicable via a data network 5000. The data network 5000 is, for example, LAN (Local Area Network), WAN (Wide Area Network), or SAN (Storage Area Network). The storage device 2400 is connected as communicable with the management device 1100 via a management network 5001. The management network 5001 is, for example, LAN or WAN. The storage device 2400 is connected as communicable with the other storage systems installed in the other sites (the second site 7000 and the third site 8000) via an internal network 5002 and an external network 5003. The internal network 5002 is, for example, LAN, WAN, or SAN. The external network 5003 includes LAN, WAN, SAN, the Internet, a public telecommunication network and exclusive lines. Note that it is also possible to achieve the data network 5000, the management network 5001, the internal network 5002, and the external network 5003 by sharing the same physical communication media by a method of logically partitioning the communication bandwidth such as VLAN (Virtual LAN).
The client device 1000 is the device for accessing the storage device 2400 and transmits data input/output requests (data write requests/data read requests) to the storage device 2400. The client device 1000 transmits data input/output requests in units of blocks or files to the storage device 2400.
The client device 1000 is an information processing device (computer) such as a personal computer, an office computer, mainframe or others. The client device 1000 includes at least a processor 1001 (e.g. a CPU (Central Processing Unit) or an MPU (Micro Processing Unit)), a memory 1002 (e.g. a volatile or non-volatile RAM (Random Access Memory) or a ROM (Read Only Memory)), and a communication interface 1003 (e.g. NIC (Network Interface Card) or an HBA (Host Bus Adaptor)). The client device 1000 may also include a storage (e.g. hard disk or a semiconductor storage device (SSD (Solid State Drive))), inputting devices such as a keyboard, a mouse and others, and outputting devices such as liquid crystal monitors and printers.
The communication between the client device 1000 and the storage devices 2400 is performed according to the protocols of, for example, TCP/IP, FICON (Fibre Connection, registered trademark), ESCON (Enterprise System Connection, registered trademark), ACONARC (Advanced Connection Architecture, registered trademark), FIBARC (Fibre Connection Architecture, registered trademark), and others.
The management device 1100 is an information processing device (computer) such as a personal computer, an office computer, or others. The management device 1100 includes at least a processor 1101 (e.g. a CPU or an MPU), a memory 1002 (e.g. a volatile or non-volatile RAM or a ROM), and a communication interface 1003 (e.g. NIC or an HBA).
The management device 1100 may also include a storage (e.g. a hard disk or a semiconductor storage device (SSD (Solid State Drive))), inputting devices such as a keyboard, a mouse and others, and outputting devices such as liquid crystal monitors and printers. The management device 1100 is connected as communicable with the storage devices 2400 via the management network 5001. The management device 1100 includes a user interface of GUI (Graphical User Interface), CLI (Command Line Interface), or others, and provides the functions for the user or the operator to control or monitor the storage devices 2400. It is also possible for the management device 1100 to be part of the storage device 2400.
The storage device 2400 includes a header device 2500, a drive controlling device 2100, and a storage drive 2200 (storage). Each of the header device 2500, the drive controlling device 2100, and the storage drive 2200 may be packed in a separate chassis, or at least some of these may be packed in the same chassis. The functions of the header device 2500 and the drive controlling device 2100 may also be achieved by the common hardware.
The storage device 2400 is a Unified Storage corresponding to multiple protocols (such as iSCSI (Internet Small Computer System Interface), NFS/CIFS (NFS: Network File System, CIFS: Common Internet File System), FC (Fibre Channel), etc.) (i.e., capable of responding to the data input/output requests following multiple protocols).
The header device 2500 includes external communication interfaces 2504, 2505, 2507 (e.g. NIC and HBA) for the connection with the data network 5000, the management network 5001, and the internal network 5002, and the internal communication interface 2506 (e.g. NIC, HBA, PCI (Peripheral Component Interconnect), and PCI-Express (registered trademark)) for the communication with the processor 2501 (e.g. a CPU, an MPU, a DMA (Direct Memory Access), or a custom LSI (Large Scale Integration)), a memory 2502 (volatile or non-volatile RAM or ROM), a cache memory 2503 (volatile or non-volatile RAM), and the drive controlling device 2100.
The header device 2500 includes functions for performing the control related to the protocols (e.g. NAS, iSCSI, NFS/CIFS, and FC) required for the communication with the client device 1000, functions related to file control (file system), and a function of caching data and data input/output requests exchanged with the client device 1000. The details of the functions included in the header device 2500 are described later.
The drive controlling device 2100 includes external communication interfaces 2104 and 2105 (e.g. NIC, HBA, PCI, and PCI-Express) for the connection with the header device 2500 and the management network 5001, a processor 2101 (e.g. a CPU, an MPU, a DMA or a custom LSI), a memory 2102 (volatile or non-volatile RAM or ROM), a cache memory 2103 (volatile or non-volatile RAM), and a drive communication interface 2106 (e.g. SAS (Serial Attached SCSI), SATA (Serial ATA), PATA (Parallel ATA), FC, or SCSI) for the communication with the storage drive.
The drive controlling device 2100 reads or writes data from or to the storage drive 2200 according to the data input/output requests (hereinafter referred to as drive access requests) transmitted from the header device 2500. The drive controlling device 2100 includes various functions for safely or efficiently utilizing the storage drive 2200 such as the function of controlling the storage drive 2200 by RAID (Redundant Arrays of Inexpensive (or Independent) Disks), the function of providing logical storage devices (LDEVs (Logical DEVices) to the header device 2500 and the client device), the function of verifying the soundness of the data, the function of obtaining snapshots, and others. The details of the functions included in the drive control device 2100 are described later.
The storage drive 2200 is, for example, a hard disk drive conforming to the specified standards (SAS, SATA, FC, PATA, or SCSI), a JBOD (Just a Bunch Of Disks) configured of multiple hard disk drives, or a semiconductor storage device (SSD (Solid State Drive)).
Fig. 2 shows the functions of the client device 1000, the management device 1100, and the storage device 2400. In the client device 1000, application software (hereinafter referred to as an application 1011) and a communication client 1012 are executed. The application 1011 is the software for providing, for example, file sharing, Email, database or others.
The communication client 1012 (Protocol Client) communicates with the storage device 2400 (e.g. transmitting data input/output requests and receiving the responses for the same). For the above-mentioned communication, the communication client 1012 performs the processing (e.g. format conversion and communication control) related to the protocols (e.g. iSCSI, NFS/CIFS, and FC). Note that these functions are achieved by the processor 1001 of the client device 1000 reading the programs stored in the memory 1002.
The management device 1100 includes a management unit 1111. The management unit 1111 sets, controls, and monitors the operations of the storage device 2400. Note that the management unit 1111 is achieved by the processor 1101 of the management device 1100 through reading and executing the programs stored in the memory 1102. The functions of the management unit 1111 may be achieved either by a different device from the storage device 2400 or by the storage device 2400.
The header device 2500 of the storage device 2400 includes an operating system 2511 (including driver software), a volume management unit 2512, a file system 2513, one or more communication servers 2514 (Protocol Servers) (protocol processing units), and a cluster processing unit 2516. Note that these functions are achieved by the hardware of the header device 2500 or by the processor 2501 reading the programs stored in the memory 2502.
The volume management unit 2512 provides the virtual storage area (hereinafter referred to as a virtual volume)based on the logical storage area provided by the storage drive 2200 to the client device 1000.
The file system 2513 accepts data input/output requests from the client device 1000 by a file specification method. The header device 2500 operates as the NAS (Network Attached Storage) server in the data network 5000. Note that, though the description of this embodiment assumes the header device 2500 to include the file system 2513, the header device 2500 does not necessarily include the file system 2513. The header device 2500, for example, may accept data input/output requests by an LBA (Logical Block Address) specification method.
The communication server 2514 communicates with the communication client 1012 of the client device 1000 and the management unit 1111 of the management device 1100. For the above-mentioned communication, the communication server 2514 performs the processing related to the protocols (e.g. iSCSI, NFS/CIFS, and FC) (e.g. format conversion and communication control).
The cluster processing unit 2516 processes the data input/output requests following the previously set cluster definition. For example, if the data input/output request received from the client device 1000 addresses itself, the cluster processing unit 2516 processes the data input/output requests by itself. If the received data input/output request addresses the other storage device 2400, it transmits the relevant data input/output request to the other storage device 2400 handling the processing of the data input/output request. The cluster processing unit 2516 manages the above-mentioned cluster definitions in a cluster management table 2517.
The drive device 2000 of the storage device 2400 includes a storage controlling unit 2410. The storage controlling unit 2410 provides the logical volume (hereinafter referred to as an LU 2420 (LU: Logical Unit)) as a logical storage area based on the storage drive 2200 to the header device 2500. The header device 2500 can specify an LU 2420 by specifying an identifier of the LU 2420 (LUN (Logical Unit Number)). The function of the storage controlling unit 2410 is achieved, for example, by the LVM (Logical Volume Manager).
Unified Storage
Fig. 3 is a diagram showing the operations of the storage device 2400. As mentioned above, the storage device 2400 is a Unified Storage corresponding to multiple protocols (iSCSI, NFS/CIFS, FC) (i.e. capable of responding to the data input/output requests following multiple protocols). The storage device 2400 shown in the figure corresponds to the both protocols of NFS and iSCSI and includes a communication server 2514 operating as an NFS server and a communication server 2514 operating as an iSCSI target. Among these, the above-mentioned communication server 2514 operating as an NFS server accepts data input/output requests transmitted from the communication client 1012 operating as an NFS client of the client device 1000. Meanwhile, the above-mentioned communication server 2514 operating as an iSCSI target accepts data input/output requests transmitted from the communication client 1012 operating as an iSCSI initiator of the client device 1000.
Resource Allocation
Fig. 4 is a diagram showing the method of accessing the LU 2420 when newly installing the second storage device 2400 as a Unified Storage in the storage system 1 configured by using the first storage device 2400 as a Unified Storage for the purpose of enhancement of resources (performance, capacity and others) and the like. The user or the operator adds the second storage device 2400 by performing the setting of the LU 2420 to mount on each client device 1000, the setting of the access path from the client device 1000 to the LU 2420, and other settings, by using the user interface provided by the management unit 1111 of the management device 1100. Note that, by this method, the storage devices 2400 (the first storage device 2400 and the second storage device 2400) are recognized as two independent devices by the client device 1000.
Cluster
Fig. 5, similarly to Fig. 4, shows the case of newly installing the second storage device 2400. However, it is different from Fig. 4 in that a cluster 2811 is configured by using two storage devices 2400, the first storage device 2400 and the second storage device 2400. If the cluster 2811 is configured by this method, the first storage device 2400 and the second storage device 2400 are recognized as one virtual storage system by the client device 1000. Such a cluster 2811 can achieve the data input/output requests transmitted from the client device 1000, for example, by forwarding or redirecting the requests in the storage device 2400.
Fig. 5 is a diagram showing the case of achieving a cluster 2811 by forwarding, and Fig. 7 is a diagram showing the case of achieving a cluster 2811 by redirection.
As shown in Fig. 5, in the case of forwarding, the cluster processing unit 2516 firstly identifies the storage device 2400 which should process the data input/output request received from the client device 1000. Then, the cluster processing unit 2516 processes the request if the request is the data input/output request which should be processed by itself, and if the request is the data input/output request which should be processed by the other storage device 2400, transfers the received data input/output request to the other storage device 2400.
Fig. 6 is information referred to by the cluster processing unit 2516 (hereinafter referred to as the cluster management table 2517) when identifying the storage device 2400 which should process the data input/output request. As shown in the figure, the cluster management table 2517 includes one or more records consisting of a cluster name 611 and a node 612. In the cluster name 611, an identifier given to each of the configured cluster groups (hereinafter referred to as a cluster ID) is set. In the node 612, an identifier of the storage device 2400 as a component of each cluster (hereinafter referred to as a device ID) is set.
As shown in Fig. 7, in the case of redirection, the cluster processing unit 2516 firstly identifies the storage device 2400 which should process the data input/output request received from the client device 1000 by referring to the cluster management table 2517. Then, the cluster processing unit 2516 processes the request if the request is the data input/output request which should be processed by itself and, if the request is the data input/output request which should be processed by the other storage device 2400, notifies the redirecting address (the other storage device 2400 identified (e.g. network address)) to the client device 1000 which transmitted the received data input/output request. The client device 1000 which has received the notification retransmits the data input/output request to the notified redirecting address.
Cluster Group in Units of Protocols
Though the methods of achieving cluster groups 2811 without depending on the protocols have been described above, a group of clusters (hereinafter referred to as a cluster group 2812) can be set in units of protocols by using the characteristics of the Unified Storages (capable of corresponding to multiple protocols).
Fig. 8 is a diagram showing the case of setting cluster groups 2812 in units of protocols (each with the NFS server and the iSCSI target shown in the figure). Cluster groups 2812 can also be achieved by preparing the above-mentioned cluster management table 2517 and performing forwarding or redirection.
Fig. 9 is an example of the cluster management table 2517 used for managing the cluster group 2812. As shown in the figure, the cluster management table 2517 includes one or more records consisting of a cluster name 911, a node 912, a role 913, and a node 914. In the cluster name 911, an identifier given to each of the configured clusters (hereinafter referred to as a cluster ID) is set. In the node 912, an identifier of the storage device 2400 as a component of each cluster (hereinafter referred to as a device ID) is set. In the role 913, an identifier for identifying the protocol supported by each cluster group 2812 (hereinafter referred to as a protocol ID) is set. In the node 914, an identifier of the storage device 2400 allocated to each role is set.
In the cluster management table 2517 shown in Fig. 9, a group of storage devices 2400 with the cluster name 911 of "Cluster 1" and the node 914 of "10.1.1.1-10.1.1.5" configure the cluster group 2812 with the NFS server of the role 913 of "NAS-1". A group of storage devices 2400 with the cluster name 911 of "Cluster 1" and the node 914 of "10.1.1.6-10.1.1.10" configure the cluster group 2812 with the iSCSI server of the role 913 of "iSCSI-1". A group of storage devices 2400 with the cluster name 911 of "Cluster 2" and the node 914 of "10.1.1.11-10.1.1.15" configure the cluster group 2812 with the FC (Fibre Channel) server of the role 913 of "FC-1". A group of storage devices 2400 with the cluster name 911 of "Cluster 2" and the node 914 of "10.1.1.15-10.1.1.20" configure the cluster group 2812 with the NFS server of the role 913 of "NAS-2".
Note that, for setting a cluster group 2812 in units of protocols, it can be considered to inactivate resources (hardware resources and software resources) for achieving the protocols unused by each storage device 2400. Fig. 8 shows the active resources in full lines and inactive resources in dashed lines. As shown in the figure, by inactivating the resources of the unused protocols, the processing load on the storage device 2400 can be reduced, and the storage device 2400 can be efficiently operated.
Initial Setting
Fig. 10 is a flowchart showing the processing performed when the user or the operator performs initial setting of a cluster 2811 and a cluster group 2812 by operating the management device 1100 (hereinafter referred to as the cluster setting processing S1000). Note that the letter "S" added to the head of the numerals in the description below indicates a step.
Firstly, the management unit 1111 of the management device 1100 accepts setting information of the cluster 2811 and setting information of the cluster group 2812 from the user or the operator (S1011 to S1012). At this time, the management unit 1111 accepts the setting information, for example, by displaying the setting screen of the cluster management table 2517 shown in Fig. 9.
Next, the management unit 1111 transmits the accepted setting information to the storage device 2400 via the management network 5001 (S1013). The cluster processing unit 2516 of each storage device 2400 receives the setting information transmitted from the management device 1100 (S1021), and reflects the received setting information in the cluster management table 2517 (S1022). After reflecting the setting information in the cluster management table 2517, the cluster processing unit 2516 of each storage device 2400 transmits a registration completion report to the management device 1100 (S1023).
Upon reception of the registration completion report (S1031), the management unit 1111 transmits a resource setting command the (command for setting activation or inactivation) (S1032) to the cluster processing unit 2516 of each storage device 2400. Upon reception of the resource setting command (S1041), the cluster processing unit 2516 of each storage device 2400 activates the resources related to the protocols which it handles, and inactivates the resources related to the protocols which it does not handle (S1042). This series of processing (S1031, 1032, 1041, and 1042) is not mandatory, but it may also be treated as an option. This may also be applied to the following descriptions.
Note that the activation of software resources means starting the process of the software, while the inactivation of software resources means terminating or deleting the process of the software.
The cluster processing unit 2516, according to the interface protocol allocated to the node, performs the operations of starting, terminating and deleting for the interface processing process (nfsd or iSCSI target software).
The Case of Changing Cluster Group Setting
Next, the case of changing the setting of cluster groups 2812 when clusters 2811 and cluster groups 2812 are already set in the storage system 1, as shown in Fig. 11, is described below. Fig. 12 is a flowchart showing the processing of changing the setting of cluster groups 2812 when clusters 2811 and cluster groups 2812 are already set in the storage system 1 (hereinafter referred to as the setting changing processing S1200).
Firstly, the management unit 1111 of the management device 1100 accepts setting information of the cluster groups 2812 from the user or the operator (S1211). The management unit 1111 accepts the setting information, for example, by displaying the setting screen of the cluster management table 2517 shown in Fig. 9.
Next, the management unit 1111 transmits the accepted setting information to each of the storage devices 2400 via the management network 5001 (S1212). The cluster processing unit 2516 of each storage device 2400 receives the setting information transmitted from the management device 1100 (S1221), and reflects the received setting information in the cluster management table 2517 (S1222). After reflecting the setting information in the cluster management table 2517, the cluster processing unit 2516 of each storage device 2400 transmits a registration completion report to the management device 1100 (S1223).
Upon reception of the registration completion report (S1231), the management unit 1111 of the management device 1100 identifies the LU 2420which does not match the newly set setting of the cluster groups 2812 (after the change of the setting) (i.e. the LU not matching the usage of the cluster group 2812 after the change of the setting) (S1232). At this step, such an LU 2420 is identified by referring to the information related to the LUs 2420 managed by each of the storage devices 2400. Fig. 13 is a table shown as an example of such information (hereinafter referred to as the volume management table 1300). In the volume management table 1300 shown in the figure, the current usage 1312 (protocol) of each LU 2420 (LUN 1311) is managed.
Next, the management unit 1111 determines the storage device 2400 as the migration destination of the LU 2420 identified at S1232 (hereinafter referred to as the migration destination storage device 2400) (S1233). This determination by the management unit 1111 is made, after the above-mentioned change of the setting, by selecting one of the storage devices 2400 supporting the protocols matching the usage of the LU 2420 identified at S1232 from the cluster management table 2517. Note that, if multiple migration destination storage devices 2400 can be selected at this step, the management unit 1111 selects the most appropriate one in view of, for example, the round-robin method, load distribution, the remaining capacity of the storage area and other factors.
Next, the management unit 1111 starts the processing of migrating the data of the identified LU 2420 to the determined destination (hereinafter referred to as the migration processing S1234) (S1234). Fig. 14 is a flowchart showing the details of the migration processing S1234.
Firstly, the management unit 1111 of the management device 1100 selects one of the identified LUs 2420 (hereinafter referred to as the migration source LU 2420) (S1411). Next, the management unit 1111 transmits a command for obtaining the snapshot of the migration source LU 2420 to the storage device 2400 in which the selected migration source LU 2420 exists (hereinafter referred to as a migration source storage device 2400) (S1412). Upon reception of the command for obtaining the snapshot (S1413), the migration source storage device 2400 obtains the snapshot of the migration source LU 2420 (S1414).
Next, the management unit 1111 transmits a command for creating the LU as the migration destination of the migration source LU 2420 (hereinafter referred to as a migration destination LU 2420) to the migration destination storage device 2400 determined at S1233 (S1421). Upon reception of the above-mentioned creation command (S1422), the migration destination storage device 2400 creates the migration destination LU 2420 (S1423).
Next, the management unit 1111 transmits a command for replicating the data stored in the migration source LU 2420 to the migration destination LU 2420 to the migration source storage device 2400 and the migration destination storage device 2400 (S1431). Upon reception of the above-mentioned replication command (S1432 and S1433), the migration source storage device 2400 and the migration destination storage device 2400 transfers the snapshot obtained at S1414 from the migration source LU 2420 to the migration destination LU 2420 (S1434 and S1435). After the replication is completed, a snapshot replication completion report is transmitted from the migration destination storage device 2400 (or migration source storage device 2400 may also be possible) to the management device 1100 (S1436). The management device 1100 receives the transmitted replication completion report (S1437).
Note that, if the migration source storage device 2400 is implemented with a function of performing the above-mentioned replication without suspending the services for the client device 1000 (hereinafter referred to as the fault-tolerant migration function), differential data while the above-mentioned replication is in process is managed by the cache memory 2503 (which can be replaced by cache memory 2103) and the storage drive 2200, and after the replication is completed, the managed differential data is reflected in the migration destination LU 2420.
Next, the management unit 1111 performs the processing for transiting the port connected with the migration source LU 2420 to the port connected with the migration destination LU 2420 (S1461). This processing is performed by, for example, setting the IP address of the iSCSI port connected with the migration source LU 2420 to the IP address of the iSCSI port connected with the migration destination LU 2420. Note that it is preferable to perform this transition without changing the settings of the client device 1000 by, for example, changing the IP address by DNS (Domain Name Server (System)) rather than changing the service name or others before and after the migration.
At S1462, the management unit 1111 determines whether there are any LUs 2420 not selected at S1411. If there are any (S1462: YES), the processing returns to S1411. If not (S1462: NO), the migration processing S1234 is completed and returns to S1235 in Fig. 12.
Note that the above-mentioned description of the migration processing S1234 assumes the use of the data replication function among the storage devices 2400 implemented in the storage devices 2400, but it is also possible to perform the data replication from the migration source LU 2420 to the migration destination LU 2420 by using the replication function implemented in the network switch configuring the data network 5000, the replication function installed in the client device 1000 or others.
The description returns to Fig. 12 again. At S1235, the management unit 1111 transmits a resource setting command to the cluster processing unit 2516 of each storage device 2400 (S1235). Upon reception of the transmitted resource setting command (S1241), the cluster processing unit 2516 of each storage device 2400 performs the resource setting (activation or inactivation) according to the setting of its cluster group 2812 after the change (S1242).
As mentioned above, if the contents of the cluster management table 2517 are changed, the cluster processing unit 2516 automatically migrates the data to the LU 2420 of the other storage device 2400 matching the protocol corresponding to the LU 2420. Therefore, the configuration of the cluster groups 2812 can be changed easily and flexibly by, for example, changing the cluster management table 2517 from the management device 1100.
The Case of Adding New Node to Existing Cluster Group
Next, as shown in Fig. 15, the case of adding a new node (storage device 2400) to an existing cluster group 2812 is described below. Fig. 16 is a flowchart showing the processing performed in this case (node addition processing S1600). The node addition processing S1600 is described below by referring to the above-mentioned figure.
Firstly, the management unit 1111 of the management device 1100 accepts setting information of adding a new node (the fifth storage device 2400 in the above-mentioned figure) to a cluster group 2812 from the user or the operator (S1611). At this time, the management unit 1111 accepts the setting information, for example, by displaying the setting screen of the cluster management table 2517 shown in Fig. 9.
Next, the management unit 1111 transmits the above-mentioned accepted setting information to each storage device 2400 via the management network 5001 (S1612). The cluster processing unit 2516 of each storage device 2400 receives the setting information transmitted from the management device 1100 (S1621), and reflects the received setting information in the cluster management table 2517 (S1622). After reflecting the setting information in the cluster management table 2517, the cluster processing unit 2516 of each storage device 2400 transmits a registration completion report to the management device 1100 (S1623).
Upon reception of the registration completion report (S1631), the management unit 1111 determines whether it is necessary to migrate the data (relocate the data) or not due to the addition of the node (S1632). This determination is made with reference to the load information of the LUs 2420 such as the usage status of each LU 2420 in each storage device 2400 or the port performance information connected with each LU 2420. If data migration is determined to be necessary (S1632: YES), the management unit 1111 starts a data migration processing (S1633). This migration processing S1633 is the same as the above-mentioned migration processing S1234 shown in Fig. 14.
Next, the management unit 1111 transmits a resource setting command to the cluster processing unit 2516 of each storage device 2400 (S1635). Upon reception of the transmitted resource setting command (S1641), the cluster processing unit 2516 of each storage device 2400 performs the resource setting (activation or inactivation) according to the setting of its cluster group 2812 after the change (S1642).
As mentioned above, if the contents of the cluster management table 2517 are changed to adding a new storage device 2400 to an existing cluster group 2812, the cluster processing unit 2516 determines whether it is necessary to relocate the data or not according to the load information of the LUs 2420, and if it is determined to be necessary, automatically migrates the data between the LUs 2420. As mentioned above, this method enables easy addition of a new storage device 2400 to the already configured cluster group 2812. It is also possible to optimize the performance of the storage system 1 by attempting load distribution at the time of relocation.
The Case of Deleting Node from Cluster Group
Next, as shown in Fig. 17, the case of deleting a node from an existing cluster group 2812 is described below. Fig. 18 is a flowchart showing the processing performed in this case (node deletion processing S1800). The node deletion processing S1800 is described below by referring to Fig. 18.
Firstly, the management unit 1111 of the management device 1100 accepts setting information of deleting a node (the first storage device 2400 in Fig.17) from a cluster group 2812 from the user or the operator (S1811). At this time, the management unit 1111 accepts the setting information, for example, by displaying the setting screen of the cluster management table 2517 shown in Fig. 9.
Next, the management unit 1111 transmits the accepted setting information to each storage device 2400 via the management network 5001 (S1812). The cluster processing unit 2516 of each storage device 2400 receives the setting information transmitted from the management device 1100 (S1821), and reflects the received setting information in the cluster management table 2517 (S1822). After reflecting the setting information in the cluster management table 2517, the cluster processing unit 2516 of each storage device 2400 transmits a registration completion report to the management device 1100 (S1823).
Upon reception of the registration completion report (S1831), the management unit 1111 determines the storage device 2400 as the migration destination (hereinafter referred to as the migration destination storage device 2400) of the data stored in the LU 2420 (LU 2420 to be deleted) of the storage device 2400 to be deleted (S1832). This determination by the management unit 1111 is made, after the above-mentioned change of the setting, by selecting one of the storage devices 2400 supporting the protocols matching the usage of the LU 2420 to be deleted from the cluster management table 2517. Note that, if multiple migration destination storage devices 2400 can be selected at this step, the management unit 1111 selects the most appropriate one in view of, for example, the round-robin method, load distribution, the remaining capacity of the storage area and other factors.
Next, the management unit 1111 starts to migrate the data stored in the LU 2420 of the first storage device 2400 to be deleted to the LU 2420 of another storage device 2400 determined at S1832 (S1833). This migration processing is the same as the above-mentioned migration processing S1234 shown in Fig. 14.
As mentioned above, if the contents of the cluster management table 2517 are changed to deleting a storage device 2400 from an already configured cluster group 2812 when the cluster groups 2812 for each of the protocols have already been configured, the cluster processing unit 2516 migrates the data to the LU 2420 of another storage device 2400 handling the protocol which used to be handled by the relevant storage device 2400. This enables easy deletion of the storage device 2400 from the already configured cluster group 2812.
The Case of Transferring Node between Cluster Groups
Next, as shown in Fig. 19, the case of transferring a node (storage device 2400) belonging to an existing cluster group 2812 to another existing cluster group 2812 is described below. Fig. 20 is a flowchart showing the processing performed in this case (node transfer processing S2000). The node transfer processing S2000 is described below by referring to Fig. 20.
Firstly, the management unit 1111 of the management device 1100 accepts setting information of transferring a node (Fig. 19 shows the case of transferring the second storage device 2400 belonging to the cluster group 2812 of the NAS clusters to the cluster group 2812 (iSCSI clusters)) from the user or the operator (S2011). At this time, the management unit 1111 accepts the setting information, for example, by displaying the setting screen of the cluster management table 2517 shown in Fig. 9.
Next, the management unit 1111 transmits the accepted setting information to each storage device 2400 via the management network 5001 (S2012). The cluster processing unit 2516 of each storage device 2400 receives the setting information transmitted from the management device 1100 (S2021), and reflects the received setting information in the cluster management table 2517 (S2022). After reflecting the setting information in the cluster management table 2517, the cluster processing unit 2516 of each storage device 2400 transmits a registration completion report to the management device 1100 (S2023).
Upon reception of the registration completion report (S2031),the management unit 1111 determines whether it is necessary to migrate (relocate) the data or not (S2032). This determination is made with reference to the load information of the LUs 2420 such as the usage status of each LU 2420 in each storage device 2400 or the port performance information connected with each LU 2420. If data migration is determined to be necessary (S2032: YES), the management unit 1111 starts a data migration processing (S2033). This processing is the same as the migration processing S1234 shown in Fig. 14.
Next, the management unit 1111 transmits a resource setting command to the cluster processing unit 2516 of each storage device 2400 (S2035). Upon reception of the resource setting command (S2041), the cluster processing unit 2516 of each storage device 2400 performs the resource setting (activation or inactivation) according to the setting of its cluster group 2812 after the change (S2042).
As mentioned above, if the contents of the cluster management table 2517 are changed to transferring the storage device 2400 configuring a certain cluster group 2812 to another cluster group 2812 when the cluster groups 2812 for each of the protocols have already been configured, the cluster processing unit 2516 determines whether it is necessary to relocate the data or not according to the load information of the LUs 2420, and if it is determined to be necessary, automatically migrates the data between the LUs 2420. Thus, this invention enables easy migration of a storage device 2400 configuring a certain cluster group 2812 to another cluster group by changing the contents of the cluster management table 2517. It is also possible to optimize the performance of the storage system by attempting load distribution at the time of relocation.
As described so far, the storage system 1 in this embodiment enables the easy configuration of cluster groups 2812 for each protocol by using a storage device 2400 (Unified Storage) including the communication server 2514 (protocol processing unit) capable of responding to data input/output requests following at least two or more protocols transmitted from the client device 1000. By this method, it is possible to optimize the performance separation according to the usage status of the protocol and the storage system performance.
It is to be understood that the above-described embodiments are intended for ease of understanding this invention and by no means limited to the particular constructions herein, but also comprises any changes, modifications or equivalents within the spirit and scope hereof.

Claims (14)

  1. A storage system comprising:
    multiple storage devices, the storage device including:
    a storage controlling unit writing data to a storage and reading data from the storage according to data input/output requests transmitted from an external device; and
    a protocol processing unit responding to the processing result for the input/output requests to the external device and being capable of responding to the data input/output requests following at least two or more protocols transmitted from the external device; wherein
    each of the storage devices includes a cluster processing unit configuring a cluster along with the other storage devices for the external device, and
    the cluster processing unit can configure cluster groups for each of the protocols.
  2. The storage system according to Claim 1, wherein
    the storage device stores a cluster management table in which the protocols handled by the cluster group to which each of the storage devices belongs are managed, and
    the cluster processing unit configures a cluster group for each of the protocols by forwarding or redirecting the data input/output requests transmitted from the external device to the other storage devices according to the cluster management table.
  3. The storage system according to Claim 1, wherein
    if cluster groups for each of the protocols are configured, the cluster processing unit inactivates resources for achieving the protocols other than the protocol handled by the cluster group to which the storage device belongs among the resources for processing the protocols in the storage device.
  4. The storage system according to Claim 1, wherein
    the storage device stores the cluster management table in which the protocols handled by the cluster group to which each of the storage devices belongs are managed,
    the storage device provides the storage area of the storage in units of logical volumes which are the logically set storage area to the external device, and
    if the contents of the cluster management table are changed when the cluster group for each of the protocols has already been configured and if the protocol to which the logical volumes corresponded do not match the protocol which the storage device to which the relevant logical volume belongs is supposed to handle after the change, the cluster processing unit migrates the data of the logical volume to the logical volume of the storage device of the other storage device which is supposed to handle the protocol after the change with which the relevant logical volume corresponded.
  5. The storage system according to Claim 1, wherein
    the storage device stores the cluster management table in which the protocols handled by the cluster group to which each of the storage devices belongs are managed,
    the storage device provides the storage area of the storage in units of logical volumes which are the logically set storage area to the external device, and
    if the contents of the cluster management table are changed to adding the storage device newly to the already configured cluster group when the cluster groups for each of the protocols have already been configured, the cluster processing unit determines whether it is necessary to relocate the data or not according to load information of the logical volume, and if it is determined to be necessary, migrates the data between the logical volumes.
  6. The storage system according to Claim 1, wherein
    the storage device stores the cluster management table in which the protocols handled by the cluster group to which each of the storage devices belongs are managed,
    the storage device provides the storage area of the storage in units of logical volumes which are the logically set storage area to the external device, and
    if the contents of the cluster management table are changed to deleting the storage device from the already configured cluster group when the cluster groups for each of the protocols have already been configured, the cluster processing unit migrates the data of the logical volume of the storage device to be deleted to the logical volume of the other storage device handling the protocol which the relevant storage device used to handle.
  7. The storage system according to Claim 1, wherein
    the storage device stores the cluster management table in which the protocols handled by the cluster group to which each of the storage devices belongs are managed,
    the storage device provides the storage area of the storage in units of logical volumes which are the logically set storage area to the external device, and
    if the contents of the cluster management table are changed to migrating the storage device configuring a certain cluster group to the other cluster group when the cluster groups for each of the protocols have already been configured, the cluster processing unit determines whether it is necessary to relocate the data or not according to the load information of the logical volume, and if it is determined to be necessary, migrates the data between the logical volumes.
  8. The storage system according to Claim 1, wherein
    the protocol is at least one of iSCSI (Internet Small Computer System Interface), NFS/CIFS (NFS: Network File System, CIFS: Common Internet File System), and FC (Fibre Channel).
  9. A method for controlling a storage system including multiple storage devices, the storage device including:
    a storage controlling unit writing data to a storage and reading data from the storage according to data input/output requests transmitted from an external device; and
    a protocol processing unit responding to the processing result for the input/output requests to the external device and being capable of responding to the data input/output requests following at least two or more protocols transmitted from the external device; wherein
    each of the storage devices includes a cluster processing unit configuring a cluster along with the other storage devices for the external device,
    the cluster processing unit can configure cluster groups for each of the protocols, the method comprising:
    the storage system storing a cluster management table in which the protocols handled by the cluster group to which each of the storage devices belongs are managed; and
    the cluster processing unit configuring a cluster group for each of the protocols by forwarding or redirecting the data input/output requests transmitted from the external device to the other storage devices according to the cluster management table.
  10. The method for controlling a storage system according to Claim 9, wherein
    if cluster groups for each of the protocols are configured, the cluster processing unit inactivates resources for achieving the protocols other than the protocol handled by the cluster group to which the storage device belongs among the resources for processing the protocols in the storage device.
  11. The method for controlling a storage system according to Claim 9, wherein
    the storage device provides the storage area of the storage in units of logical volumes which are the logically set storage area to the external device, and
    if the contents of the cluster management table are changed when the cluster group for each of the protocols has already been configured and if the protocol to which the logical volumes corresponded do not match the protocol which the storage device to which the relevant logical volume belongs is supposed to handle after the change, the cluster processing unit migrates the data of the logical volume to the logical volume of the storage device of the other storage device which is supposed to handle the protocol after the change with which the relevant logical volume corresponded.
  12. The method for controlling a storage system according to Claim 9, wherein
    the storage device provides the storage area of the storage in units of logical volumes which are the logically set storage area to the external device, and
    if the contents of the cluster management table are changed to adding the storage device newly to the already configured cluster group when the cluster groups for each of the protocols have already been configured, the cluster processing unit determines whether it is necessary to relocate the data or not according to load information of the logical volume, and if it is determined to be necessary, migrates the data between the logical volumes.
  13. The method for controlling a storage system according to Claim 9, wherein
    the storage device provides the storage area of the storage in units of logical volumes which are the logically set storage area to the external device, and
    if the contents of the cluster management table are changed to deleting the storage device from the already configured cluster group when the cluster groups for each of the protocols have already been configured, the cluster processing unit migrates the data of the logical volume of the storage device to be deleted to the logical volume of the other storage device handling the protocol which the relevant storage device used to handle.
  14. The method for controlling a storage system according to Claim 9, wherein
    the storage device provides the storage area of the storage in units of logical volumes which are the logically set storage area to the external device, and
    if the contents of the cluster management table are changed to migrating the storage device configuring a certain cluster group to the other cluster group when the cluster groups for each of the protocols have already been configured, the cluster processing unit determines whether it is necessary to relocate the data or not according to the load information of the logical volume, and if it is determined to be necessary, migrates the data between the logical volumes.
PCT/JP2009/002947 2009-06-26 2009-06-26 Storage system and controlling methods for the same WO2010150321A1 (en)

Priority Applications (6)

Application Number Priority Date Filing Date Title
EP09787895A EP2446345A1 (en) 2009-06-26 2009-06-26 Storage system and controlling methods for the same
PCT/JP2009/002947 WO2010150321A1 (en) 2009-06-26 2009-06-26 Storage system and controlling methods for the same
CN200980157791.6A CN102341777B (en) 2009-06-26 2009-06-26 Storage system and controlling methods for the same
JP2011547070A JP5255127B2 (en) 2009-06-26 2009-06-26 Storage system and storage system control method
US12/526,664 US8347028B2 (en) 2009-06-26 2009-06-26 Performance separation optimization according to protocol usage status and storage system performance
US13/693,114 US20130097400A1 (en) 2009-06-26 2012-12-04 Storage system and controlling methods for the same

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2009/002947 WO2010150321A1 (en) 2009-06-26 2009-06-26 Storage system and controlling methods for the same

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US13/693,114 Continuation US20130097400A1 (en) 2009-06-26 2012-12-04 Storage system and controlling methods for the same

Publications (1)

Publication Number Publication Date
WO2010150321A1 true WO2010150321A1 (en) 2010-12-29

Family

ID=41559684

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2009/002947 WO2010150321A1 (en) 2009-06-26 2009-06-26 Storage system and controlling methods for the same

Country Status (5)

Country Link
US (2) US8347028B2 (en)
EP (1) EP2446345A1 (en)
JP (1) JP5255127B2 (en)
CN (1) CN102341777B (en)
WO (1) WO2010150321A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TWI467365B (en) * 2011-04-20 2015-01-01 Taejin Infotech Co Ltd Raid controlled semiconductor storage device, method for providing the same, and pci-express type raid controlled semiconductor storage device

Families Citing this family (42)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10157002B2 (en) * 2010-08-26 2018-12-18 International Business Machines Corporation Migrating an encoded data slice based on an end-of-life memory level of a memory device
US8984109B2 (en) 2010-11-02 2015-03-17 International Business Machines Corporation Ensemble having one or more computing systems and a controller thereof
US9253016B2 (en) * 2010-11-02 2016-02-02 International Business Machines Corporation Management of a data network of a computing environment
US8966020B2 (en) 2010-11-02 2015-02-24 International Business Machines Corporation Integration of heterogeneous computing systems into a hybrid computing system
US9081613B2 (en) 2010-11-02 2015-07-14 International Business Machines Corporation Unified resource manager providing a single point of control
US8959220B2 (en) 2010-11-02 2015-02-17 International Business Machines Corporation Managing a workload of a plurality of virtual servers of a computing environment
US9253275B2 (en) * 2012-01-30 2016-02-02 International Business Machines Corporation Cognitive dynamic allocation in caching appliances
JP2013171305A (en) * 2012-02-17 2013-09-02 Fujitsu Ltd Storage device, storage system, storage management method and storage management program
US9063892B1 (en) * 2012-03-31 2015-06-23 Emc Corporation Managing restore operations using data less writes
US8791980B2 (en) 2012-06-05 2014-07-29 Tangome, Inc. Controlling CPU usage to balance fast and slow devices
US8762353B2 (en) 2012-06-13 2014-06-24 Caringo, Inc. Elimination of duplicate objects in storage clusters
US8799746B2 (en) 2012-06-13 2014-08-05 Caringo, Inc. Erasure coding and replication in storage clusters
US9104560B2 (en) 2012-06-13 2015-08-11 Caringo, Inc. Two level addressing in storage clusters
US9232005B1 (en) 2012-06-15 2016-01-05 Qlogic, Corporation Methods and systems for an intelligent storage adapter used for both SAN and local storage access
US9043575B2 (en) * 2013-03-15 2015-05-26 International Business Machines Corporation Managing CPU resources for high availability micro-partitions
US9785356B2 (en) 2013-06-26 2017-10-10 Cnex Labs, Inc. NVM express controller for remote access of memory and I/O over ethernet-type networks
US9430412B2 (en) 2013-06-26 2016-08-30 Cnex Labs, Inc. NVM express controller for remote access of memory and I/O over Ethernet-type networks
US9785355B2 (en) 2013-06-26 2017-10-10 Cnex Labs, Inc. NVM express controller for remote access of memory and I/O over ethernet-type networks
US10063638B2 (en) 2013-06-26 2018-08-28 Cnex Labs, Inc. NVM express controller for remote access of memory and I/O over ethernet-type networks
CN103428290A (en) * 2013-08-19 2013-12-04 北京网秦天下科技有限公司 Method and device for pushing data
KR101547317B1 (en) * 2013-09-30 2015-08-26 주식회사 유니테스트 System for detecting fail block using logic block address and data buffer address in storage test device
CN103546572B (en) * 2013-10-30 2017-04-05 北京荣之联科技股份有限公司 A kind of cloudy storing networking system and method
US9454305B1 (en) 2014-01-27 2016-09-27 Qlogic, Corporation Method and system for managing storage reservation
US9716618B2 (en) * 2014-04-22 2017-07-25 International Business Machines Corporation Script termination
US9423980B1 (en) 2014-06-12 2016-08-23 Qlogic, Corporation Methods and systems for automatically adding intelligent storage adapters to a cluster
US9436654B1 (en) 2014-06-23 2016-09-06 Qlogic, Corporation Methods and systems for processing task management functions in a cluster having an intelligent storage adapter
US9477424B1 (en) 2014-07-23 2016-10-25 Qlogic, Corporation Methods and systems for using an intelligent storage adapter for replication in a clustered environment
JP6394231B2 (en) 2014-09-25 2018-09-26 富士通株式会社 Data arrangement control program, data arrangement control apparatus, and data arrangement control method
US9460017B1 (en) 2014-09-26 2016-10-04 Qlogic, Corporation Methods and systems for efficient cache mirroring
US10554749B2 (en) 2014-12-12 2020-02-04 International Business Machines Corporation Clientless software defined grid
US10469580B2 (en) * 2014-12-12 2019-11-05 International Business Machines Corporation Clientless software defined grid
US9483207B1 (en) 2015-01-09 2016-11-01 Qlogic, Corporation Methods and systems for efficient caching using an intelligent storage adapter
US10372329B1 (en) * 2015-11-09 2019-08-06 Delphix Corp. Managing storage devices in a distributed storage system
US9596135B1 (en) 2016-08-31 2017-03-14 Red Hat, Inc. Configuring new nodes for using a storage system managed by a unified storage manager
CN108228079B (en) * 2016-12-21 2021-01-22 伊姆西Ip控股有限责任公司 Storage management method and device
CN109308163A (en) * 2017-07-26 2019-02-05 英业达科技有限公司 Non-volatility memory magnetic region planing method
US10700711B1 (en) 2017-11-03 2020-06-30 Caringo Inc. Multi-part upload and editing of erasure-coded objects
CN109936611B (en) * 2017-12-19 2021-08-24 中标软件有限公司 Data migration method of mail
KR20200014991A (en) * 2018-08-02 2020-02-12 사단법인 엑시콘산학공동연구소 Storage protocol matching device and method thereof
US11323552B2 (en) * 2019-04-19 2022-05-03 EMC IP Holding Company LLC Automatic security configurations in disaster recovery
US11204886B2 (en) * 2019-06-25 2021-12-21 Western Digital Technologies, Inc. Management of zoned storage drives
CN112783959B (en) * 2020-12-24 2023-06-02 杭州海康威视系统技术有限公司 Data transmission method and device based on heterogeneous storage systems

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060248047A1 (en) 2005-04-29 2006-11-02 Grier James R System and method for proxying data access commands in a storage system cluster
WO2008137047A2 (en) 2007-04-30 2008-11-13 Netapp, Inc. Method and apparatus for offloading network processes in a computer storage system

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2000148651A (en) * 1998-11-10 2000-05-30 Hitachi Ltd Shared disk device
US20040078542A1 (en) * 2002-10-14 2004-04-22 Fuller William Tracy Systems and methods for transparent expansion and management of online electronic storage
JP2004348324A (en) * 2003-05-21 2004-12-09 Nec System Technologies Ltd Storage device and its control method
JP4437650B2 (en) 2003-08-25 2010-03-24 株式会社日立製作所 Storage system
US7886299B2 (en) * 2004-06-01 2011-02-08 Hitachi, Ltd. Method of dynamically balancing workload of a storage system
US7209967B2 (en) * 2004-06-01 2007-04-24 Hitachi, Ltd. Dynamic load balancing of a storage system
JP4484597B2 (en) * 2004-06-28 2010-06-16 株式会社日立製作所 Storage device and exclusive control method for storage device
JP2006285808A (en) 2005-04-04 2006-10-19 Hitachi Ltd Storage system
JP2008257572A (en) 2007-04-06 2008-10-23 Hitachi Ltd Storage system for dynamically assigning resource to logical partition and logical partitioning method for storage system
US20100011368A1 (en) * 2008-07-09 2010-01-14 Hiroshi Arakawa Methods, systems and programs for partitioned storage resources and services in dynamically reorganized storage platforms

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060248047A1 (en) 2005-04-29 2006-11-02 Grier James R System and method for proxying data access commands in a storage system cluster
WO2008137047A2 (en) 2007-04-30 2008-11-13 Netapp, Inc. Method and apparatus for offloading network processes in a computer storage system

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TWI467365B (en) * 2011-04-20 2015-01-01 Taejin Infotech Co Ltd Raid controlled semiconductor storage device, method for providing the same, and pci-express type raid controlled semiconductor storage device

Also Published As

Publication number Publication date
CN102341777A (en) 2012-02-01
CN102341777B (en) 2014-09-10
US20130097400A1 (en) 2013-04-18
JP2012517045A (en) 2012-07-26
JP5255127B2 (en) 2013-08-07
EP2446345A1 (en) 2012-05-02
US8347028B2 (en) 2013-01-01
US20110138136A1 (en) 2011-06-09

Similar Documents

Publication Publication Date Title
WO2010150321A1 (en) Storage system and controlling methods for the same
US8700871B2 (en) Migrating snapshot data according to calculated de-duplication efficiency
US8239584B1 (en) Techniques for automated storage management
US10346360B1 (en) Managing prefetching of data in storage systems
EP1837751B1 (en) Storage system, storage extent release method and storage apparatus
US20130007097A1 (en) Server system and method for controlling information system
US8495331B2 (en) Storage apparatus and storage management method for storing entries in management tables
US20120096059A1 (en) Storage apparatus and file system management method
US7555600B2 (en) Storage apparatus and configuration setting method
US20100100678A1 (en) Volume management system
US9262087B2 (en) Non-disruptive configuration of a virtualization controller in a data storage system
US7809739B2 (en) Application configuration in distributed storage systems
US10855556B2 (en) Methods for facilitating adaptive quality of service in storage networks and devices thereof
US20130218847A1 (en) File server apparatus, information system, and method for controlling file server apparatus
US8713266B2 (en) Storage apparatus and method including page discard processing for primary and secondary volumes configured as a copy pair
US8423713B2 (en) Cluster type storage system and method of controlling the same
US10884622B2 (en) Storage area network having fabric-attached storage drives, SAN agent-executing client devices, and SAN manager that manages logical volume without handling data transfer between client computing device and storage drive that provides drive volume of the logical volume
US20060190550A1 (en) Storage system and controlling method thereof, and device and recording medium in storage system
JP2020533678A (en) A storage system that uses cloud storage as a rank
US10242053B2 (en) Computer and data read method
US11100050B1 (en) Dense file reservation in thinly provisioned file system
US9658803B1 (en) Managing accesses to storage
Liu et al. A fibre channel RAID supporting multiple protocol disk interfaces
JP2009258825A (en) Storage system, virtualization device and computer system

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 200980157791.6

Country of ref document: CN

WWE Wipo information: entry into national phase

Ref document number: 12526664

Country of ref document: US

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 09787895

Country of ref document: EP

Kind code of ref document: A1

REEP Request for entry into the european phase

Ref document number: 2009787895

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2009787895

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2011547070

Country of ref document: JP

NENP Non-entry into the national phase

Ref country code: DE