EP1821188A2 - Dispositif de contrôle de stockage et système de stockage - Google Patents

Dispositif de contrôle de stockage et système de stockage Download PDF

Info

Publication number
EP1821188A2
EP1821188A2 EP06255218A EP06255218A EP1821188A2 EP 1821188 A2 EP1821188 A2 EP 1821188A2 EP 06255218 A EP06255218 A EP 06255218A EP 06255218 A EP06255218 A EP 06255218A EP 1821188 A2 EP1821188 A2 EP 1821188A2
Authority
EP
European Patent Office
Prior art keywords
controller
updating
unit
host
program
Prior art date
Legal status (The legal status 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 status listed.)
Withdrawn
Application number
EP06255218A
Other languages
German (de)
English (en)
Other versions
EP1821188A3 (fr
Inventor
Akihiro Hitachi Ltd. IP Group Mannen
Akira Hitachi Ltd. IP Group Nishimoto
Junji Hitachi Ltd. IP Group Ogawa
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hitachi Ltd
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
Publication of EP1821188A2 publication Critical patent/EP1821188A2/fr
Publication of EP1821188A3 publication Critical patent/EP1821188A3/fr
Withdrawn legal-status Critical Current

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/0655—Vertical data movement, i.e. input-output transfer; data movement between one or more hosts and one or more storage devices
    • G06F3/0659—Command handling arrangements, e.g. command buffers, queues, command scheduling
    • 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
    • G06F3/0607—Improving or facilitating administration, e.g. storage management by facilitating the process of upgrading existing storage systems, e.g. for improving compatibility between host and storage device
    • 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/0632—Configuration or reconfiguration of storage systems by initialisation or re-initialisation of storage systems
    • 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/0662—Virtualisation aspects
    • 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]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/65—Updates
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/65—Updates
    • G06F8/656—Updates while running

Definitions

  • the present invention relates to a storage control device and to a storage system.
  • a storage control device is a computer device which employs a micro computer, sometimes it becomes necessary to update its program. It is possible to update the program simply if it is possible temporarily to stop access requests from a host computers (hereinafter termed "hosts"). However, sometimes it is the case that it is not possible to stop the storage control device, in order to obtain continuous 24-hour 365-day operation therefrom.
  • hosts a host computers
  • the present invention has been conceived in the light of the above described problems, and an object is to provide a storage control device and a storage system, with which it is possible to update the program without informing any host device, and moreover preferably using a simpler structure than in the prior art. Further objectives of the present invention will become clear from the subsequent description of its embodiments.
  • the storage control device is a storage control device which includes a plurality of controllers, with each of controller including: a host communication control unit for performing communication with a host device; a subordinate communication control unit for performing communication with a storage device; a program storage unit which stores a predetermined program; an access request processing unit which, when an access request has been received from the host device via the host communication control unit, processes the access request by accessing the storage device via the subordinate communication control unit, and by executing predetermined data processing based on the predetermined program; and a data storage unit which stores data which is used in the predetermined data processing; and the storage device further including: a mutual communication path for connecting the controllers; an update control unit for updating the predetermined program which is stored in the program storage unit; and a processing path changeover unit which, based on a command from the update control unit, processes an access request received by the host communication control unit of one of the controllers by means of the access request processing unit of another one of
  • the processing path changeover unit is capable of changing over between: (1) a normal mode in which, during normal operation, the host communication control unit and the access request processing unit are connected in each controller; and (2) an updating mode in which, during updating of the predetermined program, the host communication control unit of the one controller is connected via the mutual communication path to the access request processing unit of the other controller.
  • a data synchronization unit which synchronizes the stored contents in the data storage unit of the one controller and the stored contents in the data storage unit of the other controller.
  • the update control unit when the stored contents in the data storage unit of the one controller and the stored contents in the data storage unit of the other controller have been synchronized, the update control unit connects the host communication control unit of the one controller to the access request processing unit of the other controller via the mutual communication path by the processing path changeover unit.
  • the update control unit updates the predetermined program which is stored in the program storage unit of the one controller, when the host communication control unit of the one controller is connected, by the processing path changeover unit, to the access request processing unit of the other controller via the mutual communication path.
  • the update control unit reconnects the host communication control unit of the one controller to the access request processing unit of the one controller by the processing path changeover unit, after re-synchronizing the stored contents in the data storage unit of the one controller and the stored contents in the data storage unit of the other controller.
  • processing path changeover unit and the update control unit operate within the one controller in which the updating of the predetermined program is performed.
  • an update program storage unit for storing a program for updating, which is used for updating the predetermined program.
  • the update control unit updates the predetermined program when execution of updating has been commanded.
  • the update control unit when the execution of updating has been commanded, receives and stores a program for updating which is used for updating the predetermined program, after connecting, by the processing path changeover unit, the host communication control unit of the one controller to the access request processing unit of the other controller via the mutual communication path.
  • the update control unit when the execution of updating has been commanded, receives and stores a program for updating which is used for updating the predetermined program, before connecting, by the processing path changeover unit, the host communication control unit of the one controller to the access request processing unit of the other controller via the mutual communication path.
  • the update control unit updates the predetermined program immediately, if the priority level set for a program for updating to update the predetermined program is higher than a predetermined threshold value, while updating the predetermined program based on the states of the controllers, if the priority level set for the program for updating is equal to or less than the predetermined threshold value.
  • the update control unit is commanded to execute updating from the host device, or from a management device which is different from the host device.
  • the mutual communication path is provided within a casing in which the controllers are provided.
  • the storage system is a storage system which includes a host device which issues access requests, a storage control device which is connected to the host device via a network for data input and output, and a management device which is connected to the storage control device via a network for management, and this storage control device includes a plurality of controllers which are connected by a mutual communication path, and a storage device which is connected to the plurality of controllers.
  • Each of the controllers includes: a host communication circuit for performing communication with the host device; a subordinate communication circuit for performing communication with the storage device; a processor which, when an access request has been received via the host communication circuit from the host device, accesses the storage device via the subordinate communication circuit, and performs predetermined data processing; a data memory which stores data used in the predetermined data processing; a bus for connecting together the host communication circuit, the subordinate communication circuit, the data memory, and the processor; and a bus changeover switch which is provided on the bus and is positioned between the host communication circuit and the processor, for, when the normal mode has been commanded, connecting the host communication circuit to the processor within the same controller, and, when the updating mode has been commanded, connecting the host communication circuit within the controller which is the origin of changing over via the mutual communication path to the processor within the controller which is the destination of changing over.
  • the update control unit executes: (3-1) a step of synchronizing stored contents in the data memory of the controller which is the origin of changing over and stored contents in the data memory of the controller which is the destination of changing over; (3-2) a step of changing over the bus changeover switch from the normal mode to the updating mode; (3-3) a step of updating the predetermined program by a program for updating which has been received from the management device or the host device; (3-4) a step of, when updating of the predetermined program has been completed, copying the stored contents of the data memory of the controller which is the destination of changing over to the data memory of the controller which is the origin of changing over, thus re-synchronizing both the stored contents; and (3-5) a step of, when the re-synchronizing has been completed, changing over the bus changeover switch from the updating mode to the normal mode.
  • At least a portion of the various means, units, and steps of the present invention may be implemented by a computer program. And such a computer program may be distributed in the state of being fixed on some type of recording medium; or, alternatively, it may also be transmitted via a communication medium.
  • Fig. 1 is an explanatory figure schematically showing the overall structure of a storage system according to this embodiment.
  • This storage system may, for example, comprise a storage control device 1, a storage unit 3, a host 5, and a management terminal 6.
  • the storage control device 1 stores data which is utilized by the host 5.
  • the storage control device 1 is connected to the host 5 via a communication network CN1.
  • a LAN Local Area Network
  • a SAN Storage Area Network
  • IP_SAN IP/IP
  • FC_SAN Fiber Channel Protocol
  • DAS Direct Attached Storage
  • the storage control device 1 is connected to the storage unit 3 via a network CN2.An FC (Fibre Channel) or an SAS (Serial Attached SCSI) or the like may be employed as this communication network CN2.
  • the storage unit 3, for example, may comprise a plurality of disk drives 4A, 4B which are disposed in an array format. These disk drives 4A, 4B, for example, may be made as hard disk drives or semiconductor memory drives or the like.
  • a program such as, for example, an OS (Operating System) or a microprogram for controlling the storage control device 1 or the like is stored in the boot disk 4A.
  • a program for updating may be stored in the disk 4B, which is a disk for updating.
  • a physical storage device is constituted by one or a plurality of disk drives, and a logical volume is established over storage regions on this physical storage device.
  • This logical volume constitutes an object of access by the host 5.
  • a logical volume may be termed a logical storage device. User data which is used by the host 5 is stored in such a logical volume.
  • the host 5 is a computer device which, for example, may be a personal computer or a server computer or the like. This host 5 comprises an application program for using a group of data managed by the storage control device.
  • the management terminal 6 is a computer device which, for example, may be constituted by a personal computer or a portable information terminal or the like. This management terminal 6 is connected to each of the host 5 and the storage control device 1 by a communication network CN3 for management.
  • the management terminal 6 comprises a update command unit 6A for commanding the storage control device 1 to update its program.
  • This storage control device 1 comprises a plurality of controllers 2A, 2B. Each of the controllers 2A, 2B has the same structure.
  • the storage control device 1 is constituted by the redundant structure made up of the plurality of controllers 2A and 2B. However, for the convenience of explanation, in Fig. 1, in order to explain the method of program updating, an update control unit 8 is only shown in one of the controllers 2A.
  • the one controller 2A may comprise a host interface (hereinafter abbreviated as "I/F") unit 2A1, a subordinate I/F unit 2A2, an access request processing unit 2A3, a program memory 2A4, a data memory 2A5, and the update control unit 8.
  • I/F host interface
  • the host I/F unit 2A1 corresponds to the "host communication control unit” or a "host communication circuit" of the Claims.
  • This host I/F unit 2A1 is connected to the host 5 via the communication network CN1. And this host I/F unit 2A1 performs communication with the host 5.
  • the subordinate I/F unit 2A2 corresponds to the "subordinate communication control unit” or the "subordinate communication circuit” of the Claims.
  • This subordinate I/F unit 2A2 is connected to the storage unit 3 via the communication network CN2. And this subordinate I/F unit 2A2 performs communication with the storage unit 3.
  • the access request processing unit 2A3 may comprise a CPU (Central Processing Unit) and the like, and performs predetermined data processing according to access requests from the host 5. For example, read requests and write requests may be included in these access requests.
  • the access request processing unit 2A3 reads out the data requested by the host 5 from the storage unit 3, and transmits this data to the host 5.
  • the access request processing unit 2A3 stores the write data which it has received from the host 5 in the storage unit 3.
  • the access request processing unit 2A3 performs conversions between the logical block addresses and the physical addresses on the disk drives, and the like.
  • the program memory 2A4 may consist of a flash memory, a RAM (Read Only Memory), a ROM (Read Only Memory), or the like.
  • This program memory 2A4 may be classified, by itself or along with the disk for updating 4B, as a "program storage unit”. And, for example, a program like a BIOS (Basic Input/Output System), an OS, or a program like a microprogram for controlling the storage control device 1, may be stored in this program memory 2A4.
  • BIOS Basic Input/Output System
  • the data memory 2A5 corresponds to the "data storage unit" of the Claims.
  • This data memory 2A5 may be made from a RAM or the like.
  • data which has been read out from the host 5 or data which has been written from the host 5 (this is termed "user data") is stored in this data memory 2A5.
  • control information such as, for example, information for managing connection relationships between the host 5 and logical volumes, information for managing logical volumes, information for managing the disk drives, and the like.
  • the other controller 2B may comprise a host I/F unit 2B1, a subordinate I/F unit 2B2, an access request processing unit 2B3, a program memory 2B4, and a data memory 2B5.
  • These elements 2B1 through 2B5 are the same as the above described elements 2A1 through 2A5 of the controller 2A, and accordingly duplicated explanation thereof will be curtailed.
  • a connection control unit 7 is a device which controls the state of connection between the controllers 2A and 2B.
  • This connection control unit 7, for example, may comprise changeover switches 7A and 7B one of which is provided within each of the controllers 2A and 2B, and mutual connection paths 7C and 7D which are connected between these changeover switches 7A and 7B.
  • These changeover switches 7A and 7B, and the connection control unit 7, correspond to the "processing path changeover unit" of the Claims.
  • the connection control unit 7 has a plurality of modes: a normal mode and an updating mode.
  • the connection control unit 7 connects the host I/F unit and the access request processing unit within the same controller together.
  • the host I/F unit 2A1 and the access request processing unit 2A3 are respectively connected together, and the host I/F unit 2B1 and the access request processing unit 2B3 are respectively connected together.
  • the host I/F unit 2A1 and the access request processing unit 2A3 are connected together by connecting together the port C1 and the port B1, and, in a similar manner, the host I/F unit 2B1 and the access request processing unit 2B3 are connected together by connecting together the port C2 and the port B2.
  • the structure of the connection control unit 7 is shown schematically by way of example, so as to facilitate easy explanation of the situation in which the processing paths are changed over during program updating.
  • the connection control unit 7 connects the host I/F unit within one of the controllers to the access request processing unit within the other controller.
  • the connection control unit 7 connects the host I/F unit 2A1 within the controller 2A which is the object of updating to the access request processing unit 2B3 within the controller 2B.
  • the connection control unit 7 connects the host I/F unit 2B1 within the controller 2B which is the object of updating to the access request processing unit 2A3 within the controller 2A.
  • the connection control unit 7 connects the host I/F unit 2B1 within the controller 2B which is the object of updating to the access request processing unit 2A3 within the controller 2A.
  • the update control unit 8 within the controller which is the subject of updating starts when updating execution of its program is commanded from the management terminal 6.
  • this update control unit 8 updates the program which is stored in the program memory 2A4 or the boot disk 4A, after it has connected the host I/F unit 2A1 to the access request processing unit 2B3 within the other controller 2B.
  • Which program is updated depends on a command from the management terminal 6.
  • this update control unit 8 returns the connection control unit 7 from the updating mode to the normal mode, and again connects the host I/F unit 2A1 to the access request processing unit 2A3 after updating.
  • the update control unit 8 makes the contents which are stored in the data memories 2A5 and 2B5 agree with one another.
  • the host I/F unit 2A1 of the controller 2A before connecting the host I/F unit 2A1 of the controller 2A to the access request processing unit 2B3 of the controller 2B, it copies the stored contents of the data memory 2A5 to the data memory 2B5.
  • the access processing unit 2B3 it is possible for the access processing unit 2B3 to continue processing access requests from the host 5, instead of the access request processing unit 2A3.
  • processing for making the stored contents of the data memories 2A5 and 2B5 agree with one another may already be performed. That is to say, if the data memories 2A5 and 2B5 are operating in synchronous mode, then the stored contents of the data memories 2A5 and 2B5 agree with one another.
  • the updating of the program within the controller 2A is completed during the time that the access request processing unit 2B3 is performing the processing of access requests as a delegate.
  • the update control unit 8 copies the stored contents of the data memory 2B5 into the data memory 2A5. By doing this, it is possible for the access request processing unit 2A3 again to perform processing of access requests from the host 5.
  • this preferred embodiment of the present invention has the above described structure, it is possible to update the program without any interruption of the provision of storage service, comparatively simply and moreover at a low cost.
  • this embodiment it is not necessary to establish any redundant path between the host 5 and the storage control device 1 as with the prior art, and it is not necessary to implement any path changeover software in the host 5.
  • this embodiment of the present invention it is possible to update the program of the storage control device 1 without imposing any burden on the host 5, and moreover the convenience of use is enhanced.
  • several preferred embodiments of the present invention will be described in detail.
  • Fig. 2 is an explanatory figure showing the overall structure of a storage system according to this first embodiment.
  • This storage system may comprise a storage device 100, a host 10, and a management terminal 20.
  • the storage control device 100 corresponds to the storage control device 1 in Fig. 1.
  • the host 10 corresponds to the host 5 in Fig. 1
  • the management terminal 20 corresponds to the management terminal 6 in Fig. 1.
  • the host 10 is a computer device such as, for example, a personal computer, a server computer, a main frame, an engineering work station, or the like.
  • This host 10 may comprise a communication I/F 11 which consists of a HBA (Host Bus Adapter) or a network card or the like, and an application program 12. Although, apart from these elements, there may also be included an OS or a user interface or the like, description thereof will here be omitted.
  • the I/F 11 is connected to the storage control device 100 via a communication network CN11 such as, for example, a SAN or the like.
  • the application program 12 accesses the storage control device 100 via the I/F 11, and uses data (user data) which is stored in the storage control device 100.
  • the management terminal 20 manages the overall structure of the storage system and so on.
  • This management terminal 20 is connected to both the host 10 and also the storage control device 100 via a network for management CN13, such as for example a LAN or the like.
  • the management terminal 20 is connected to the controllers 200A and 200B within the storage control device 100.
  • This management terminal 20 comprises a new program storage unit 21 and an update command unit 22.
  • the new program storage unit 21 is a device for storing a program for updating.
  • this program for updating will sometimes be termed the "new program”
  • the program which is being updated will sometimes be termed the "old program”.
  • This new program storage unit 21 may, for example, consist of a semiconductor memory device or a hard disk device.
  • the update command unit 22 is a device for commanding updating of the program in the storage control device 100. As will be described hereinafter, this update command unit 22, along with commanding the execution of updating, also transfers the program for updating which has been read out from the new program storage unit 21 to the storage control device 100.
  • This storage control device 100 comprises a plurality of controllers 200A, 200B which stand in the mutual relationship of being able to back up one another, and a storage unit 300.
  • controllers 200A and 200B fundamentally have the same structure, this explanation will focus on the one controller 200A.
  • controllers 200A and 200B correspond to the controllers 2A and 2B in Fig. 1. It should be understood that, although both of the controllers 200A, 200B can be connected to the host 10, for this explanation of the present invention, only the controller 200A will be shown as being connected to the host 10.
  • the controller 200A (CTL#0 in the figure) comprises, for example, a host side I/F unit 210A, a disk side I/F unit 220A, a processor 230A ("CPU” in the figure), a memory 240A, a cache memory 250A ("CM” in the figure), and a data transfer control circuit 260A ("D_CTL” in the figure).
  • the host side I/F unit 210A corresponds to the host I/F unit 2A1 in Fig. 1.
  • This host side I/F unit 210A is connected to the I/F 11 of the host 10 via a communication network CN11. And the host side I/F unit 210A receives access requests which have been issued from the host 10, and transmits the results of data processing to the host 10.
  • the disk side I/F unit 220A corresponds to the subordinate I/F unit 2A2 in Fig. 1.
  • This disk side I/F unit 220A is connected to each of the disk drives 310 of the storage unit 300 via a communication network CN12 such as a FC or a SAS or the like. And the disk side I/F unit 220A reads out data from the storage unit 300, and writes data into the storage unit 300.
  • the processor 230A corresponds to the access request processing unit 2A3 in Fig. 1. Furthermore, this processor 230A implements at least a portion of the update control unit 8 and the connection control unit 7 in Fig. 1. By reading in and executing a program which is stored in the memory 240A, the processor 230A performs data processing according to access requests. Furthermore, the processor 230A performs an updating control procedure and so on as will be described hereinafter.
  • the memory 240A corresponds to the program memory 2A4 in Fig. 1.
  • This memory 240A may consist of a flash memory, a ROM, a RAM, or the like.
  • Various programs are stored in this memory 240A, such as, for example, a BIOS, an OS, a microprogram for control, or the like.
  • the cache memory 250A corresponds to the data memory 2A5 in Fig. 1.
  • This cache memory 250A may consist of semiconductor memorys.
  • this cache memory 250A is backed up by electrical power from a battery power source. Accordingly, even if the main power supply for the storage control device 100 is interrupted for some time, the stored contents of the cache memory 250A are not lost during this time period, because they are backed up by the battery power source. For example, if the main power source is interrupted, it is possible to read the contents stored in the cache memory 250A into the storage unit 300 during the period while the cache memory 250A is being backed up by the battery power source.
  • the cache memory 250A using non-volatile semiconductor memory, it is also possible to preserve the contents stored in the cache memory 250A, even if the main power source has been interrupted. As will be described hereinafter, user data and control information are stored in this cache memory 250A. Furthermore, the cache memory 250A also keeps the same stored contents as the cache memory 250B of the other controller 200B. In other words, the stored contents of the cache memories 250A and 250B are synchronized.
  • the data transfer control circuit 260A controls data transfer between the I/F units 210A and 220A, the processor 230A, and the cache memory 250A. The detailed operation of this data transfer control circuit 260A will be further described hereinafter.
  • the other controller 200B (CTL#1 in the figure) comprises a host side I/F unit 210B, a disk side I/F unit 220B, a processor 230B, a memory 240B, a cache memory 250B, and a data transfer control circuit 260B.
  • a mutual communication path 400 is provided between the one data transfer control circuit 260A and the other data transfer control circuit 260B.
  • This mutual communication path 400 may consist of a bus which connects between the controllers 200A and 200B. Exchange of data between the data transfer control circuits 260A and 260B is accordingly possible via this mutual communication path 400.
  • the mutual communication path 400 may be constituted as an internal bus within the memory control device 100 as described above, alternatively, it may also be constituted as an externally fitted cable which connects from the outside of the casing of the storage control device 100 between the controllers 200A and 200B.
  • the storage unit 300 corresponds to the storage unit 3 of Fig. 1.
  • This storage unit 300 may consist of a plurality of disk drives 310 disposed in an array.
  • disk drives 310 there may be used, for example, hard disk drives, semiconductor memory drives, optical disk drives, opto-magnetic disk drives, magnetic disk drives, or the like.
  • hard disk drives of various types; for example, disks such as FC (Fiber Channel) disks, SATA (Serial AT Attachment) disks, SCSI (Small Computer System Interface) disks, SAS (Serial Attached SCSI) disks or the like may be utilized. Furthermore, it is also possible to mix storage devices of various different types within the storage unit 300.
  • FC Fiber Channel
  • SATA Serial AT Attachment
  • SCSI Serial Computer System Interface
  • SAS Serial Attached SCSI
  • Fig. 3 schematically shows the storage structure of the cache memories 250A and 250B.
  • this storage control device 100 a dual controller construction is utilized, and moreover, due to the employment of the plurality of cache memories 250A and 250B, it is arranged for redundant storage of user data and control information to be possible.
  • the one cache memory 250A there are stored both the user data which are managed by the controller 200A and also the user data which are managed by the controller 200B.
  • the other cache memory 250B there are likewise stored both the user data which are managed by the controller 200B and also the user data which are managed by the controller 200A. It should be understood that, according to requirements, it is possible either to perform synchronization processing between the cache memories 250A and 250B, or to cancel such synchronization processing.
  • the cache memories 250A and 250B Since the user data and the control information are stored redundantly by the cache memories 250A and 250B in this manner, accordingly if, for example, exceptionally the stored contents in one of these cache memories come to be lost, then it is possible to continue data processing in a seamlessly matched manner by using the stored contents of the other cache memory. Furthermore, it is also possible to restore the stored contents of the one cache memory by copying the stored contents of the other cache memory into the one cache memory.
  • Fig. 4 shows an example of the storage structure of the memories 240A and 240B and the storage unit 300. It should be understood that, in the following explanation, the cases of the controllers 200A and 200B are not particularly distinguished, and accordingly the appended reference symbols "A" and “B” will be omitted. Thus, in Fig. 4, the memory is referred to by the symbol "240".
  • the memory 240 comprises, for example, a program memory 241 and a RAM 242.
  • the program memory 241 consists of non-volatile semiconductor memory which can be rewritten, such as, for example, flash memory or the like.
  • a basic control program P10 such as, for example, a BIOS or an IPL (Initial Program Loader) or the like is stored in this program memory 241.
  • the RAM 242 consists of, for example, volatile semiconductor memory.
  • An OS (P20) which is read in from a boot disk 311 is stored in this RAM 242.
  • the storage unit 300 comprises a plurality of disk drives 310.
  • one of these disk drives, among the disk drives 310, on which the OS is stored, will be termed the boot disk 311.
  • the disk drives which is empty will be termed an empty disk 312.
  • New programs P11, P21 which are used for program updating may be stored in the empty disk 312. Furthermore, by setting the empty disk 312 as a new boot disk, it is also possible to read into the RAM 242 an OS (P21) which has been stored on this empty disk 312.
  • a single group may be made up from a fixed number, like four or eight, of the disk drives 310.
  • a group is termed a RAID group (a parity group) 320.
  • Each of the disk drives 310 which make up such a RAID group 320 supplies its respective physical storage region, and thereby an ensemble of these physical storage regions is formed.
  • the RAID group 320 may be termed a physical storage device.
  • the disk drives 310 which are members of the group 320 one or a plurality thereof may be used for storage of parity data, although this may differ according to the RAID level.
  • One or a plurality of logical volumes 330 may be set up in the physical storage region of the RAID group 320. Such a logical volume 330 is allocated to a communication port on the host I/F unit 210, and constitutes an object for access from the host 10.
  • a logical volume 330 may be termed a logical storage device.
  • the above described boot disk 311 and empty disk 312 may each be made as a physical disk drive 310, or, alternatively, they may be made as logical volumes 330. It should be understood that one or a plurality of logical volumes 330 may also be provided within a single disk drive 310.
  • Fig. 5 is a block diagram showing the details of the data transfer control circuit 260.
  • Both of the data transfer control circuits 260A and 260B have the same structure.
  • this data transfer control circuit 260A comprises a host side interior bus buffer 261, a disk side interior bus buffer 262, a processor side interior bus buffer 263, a mutual communication path control unit 264, a cache control unit 265, a bus switch 266, and buses 401, 402, 403, and 404.
  • the host side interior bus buffer 261 and the bus switch 266 are connected together by the host side interior bus 401, while the disk side interior bus buffer 262 and the bus switch 266 are connected together by the disk side interior bus 402.
  • the bus switch 266 is provided on the interior bus buffer 262 which connects together the host side interior bus buffer 261 and the disk side interior bus buffer 262.
  • the mutual communication path control unit 264 is a device for performing data transfer via the mutual communication path 400.
  • This mutual communication path control unit 264 is connected to both the bus switch 266 and the cache control unit 265.
  • the cache control unit 265 is connected to the cache memory 250A via the cache bus 403.
  • the cache control unit 265 is a device for controlling input and output of data to and from the cache memory 250A. This cache control unit 265 is able to exchange data with the cache control unit 265 of the other controller 200B via the mutual communication path control unit 264 and the mutual communication path 400. By doing this, the stored contents are synchronized between the cache memories 250A and 250B.
  • the bus switch 266 is a device for, on a command to change over the path, cutting off the interior bus 401 from the controller 200A, and connecting that interior bus 401 to the other controller 200B via the mutual communication path control unit 264 and the mutual communication path 400.
  • Fig. 6 shows the state of the bus switch 266 ("B_SW" in the figure) in the normal state (the normal mode).
  • the bus switch 266 connects the host side interior bus 401 and the disk side interior bus 402.
  • the host side I/F unit 210 is connected to the processor 230.
  • each of the host side I/F unit 210 and the host side interior bus buffer 261 and the host side interior bus 401 is placed by the bus switch 266 under the control of the controller provided thereto.
  • Fig. 7 is a block diagram showing the case when the bus switch 266 of the one controller 200A is changed over to the updating mode.
  • the updating mode is meant that the procedure of program updating is being performed.
  • This updating mode may also, for example, be termed the connected unit changeover mode.
  • the processor 230A When updating the program on the side of the controller 200A, the processor 230A issues a command to the bus switch 266 within the controller 200A to proceed with program updating.
  • This command is one which requests the controller 200A to shift from the normal mode to the updating mode. Based on this command, the bus switch 266 changes over the destination of connection for the host side interior bus 401 from the disk side interior bus 402 to the mutual communication path 400.
  • the host side interior bus 401 connects together the interior buses 401 and 402 within the other controller 200B via the mutual communication path 400 and so on. Accordingly, the host side I/F unit 210A within the controller 200A is connected to the processor 250B within the controller 200B via the bus switch 266 within the controller 200A, the communication path 400, and the bus switch 266 within the controller 200B. Or, to express this in another manner, when the bus switch 266 is in the updating mode, each of the host side I/F unit 210 and the host side interior bus buffer 261 and the host side interior bus 401 comes to be placed thereby under the control of the other controller from the one which is provided thereto.
  • Fig. 8 is a flow chart showing the flow of control for processing an access request (a command) which has been issued from the host 10. This processing is performed by the controller 200A within the storage control device 100. This is because, in this embodiment, the controller 200A is built to perform receipt and processing of commands from the host 10.
  • the controller 200A monitors (in a step S11) whether or not an access request has been issued from the host 10. When an access request has been issued from the host 10 (S11: YES), then the controller 200A decides on the type of command of this access request (in a step S12).
  • the controller 200A decides (in a step S13) whether or not the data which has been requested from the host 10 is stored in the cache memory 250A. If the data which has been requested is stored in the cache memory 250A (S13: YES), then the controller 200A reads out this data from the cache memory 250A, and transmits it to the host 10 (in a step S15). On the other hand, if the data which has been requested from the host 10 is not stored in the cache memory 250A (S13: NO), then the controller 200A reads out the data which has been requested from the storage unit 300, and stores it in the cache memory 250A (in a step S14). And the controller 200A then transmits this data which has been read out from the storage unit 300 to the host 10 (in the step S15).
  • the controller 200A receives the write data which has been transmitted from the host 10 and stores this write data in the cache memory 250A (in a step S16). And the controller 200A updates the control information which is stored in the cache memory 250A (in a step S17).
  • the address for storage of the write data and the status of the write data are updated.
  • the controller 200A notifies (in a step S18) the host 10 to the effect that the processing of the write command has been completed. Subsequently, the controller 200A writes (in a step S19) the write data which has been stored in the cache memory 250A to the predetermined disk drive 310 within the storage unit 300, at a suitable timing which it determines appropriately by itself.
  • the predetermined disk drive 310 is meant that disk drive which includes the logical volume 330 which is the destination for writing as specified by the host 10. It should be understood that, if parity data is generated as for example according to RAID5 or RAID6 or the like, then the controller 200A calculates and stores such parity data.
  • the processing for writing data into the disk drive 310 is termed "destage processing".
  • the status of the write data which has thus been de-staged is changed from the dirty status to the clean status.
  • the controller 200A updates the status and so on of the write data (in a step S20).
  • this method is employed, in which the host 10 is notified that the processing has been completed at the time point that the write data has been stored in the cache memory 250A - this is termed the write after method or the non-synchronized write method - this is not intended to be limitative of the present invention; it would also be acceptable to notify the host 10 of the completion of processing after having written the write data into the disk drive 310.
  • the controller 200A performs other command processing (in a step S21).
  • this other command processing there may be cited, for example, an enquiry command for querying the empty capacity or the status of a logical volume 330, or the like.
  • Fig. 9 is a flow chart showing the synchronization processing for sharing information between the cache memories 250A and 250B. This synchronization processing may be performed, for example, if the user has set the system in advance to a synchronization mode.
  • the controller 200A decides (in a step S31) whether or not the user data has been updated. If the user data has been updated (S31: YES), then the controller 200A copies (in a step S32) this user data which has been updated into the cache memory 250B of the other system. In other words, the new user data which has been stored in the cache memory 250A is transferred from the cache control unit 265 to the other controller 200B via the mutual communication path control unit 264 and the mutual communication path 400, and is stored in its cache memory 250B.
  • the controller 200A decides (in a step S33) whether or not the control information has been updated. If the control information has been updated (S33: YES), then, in the same manner as in the case when the user data has been updated, the controller 200A copies (in a step S34) this control information which has been updated into the cache memory 250B of the other system. And the controller 200A decides whether or not the synchronization mode has been terminated (in a step S35). The stored contents of the cache memories 250A and 250B are synchronized until the synchronization mode terminates.
  • Fig. 10 is a flow chart showing the update control procedure.
  • the user commands in a step S41) updating of the program in the controller 200A (CTL#0) using the update command unit 22 of the management terminal 20.
  • the controller 200A When the controller 200A receives (in a step S42) an update command, it transmits the common information to the controller 200B (CTL#1).
  • the common information is the stored contents of the cache memory 250A.
  • the controller 200B stores (in a step S43) the common information which it has received from the controller 200A in the cache memory 250B.
  • the controller 200A connects the host side interior bus 401 within the data transfer control circuit 260A to the interior bus of the data transfer control circuit 260B by changing over (in a step S44) the bus switch 266 from the normal mode to the updating mode.
  • the host side I/F unit 210A of the controller 200A is connected to the processor 230B of the controller 200B via the mutual communication path 400.
  • the controller 200A requests (in a step S46) the management terminal 20 to transfer the new program.
  • the management terminal 20 transmits (in a step S47) the program for updating which is stored in the new program storage unit 21 via the network for management CN13 to the controller 200A.
  • the processor 230A of the controller 200A is separated from the host side I/F unit 210A, it is connected to the network for management CN13, so that it is able to perform communication in both directions with the management terminal 20.
  • the controller 200A stores (in a step S48) the new program which it has received from the management terminal 20 in, for example, the empty disk 312. And the controller 200A updates (in a step S49) the old program to the new program. This updating progressing will be described in greater detail hereinafter.
  • the controller 200A When the controller 200A has completed the updating of the program, it performs self-checking processing (in a step S50), and restarts (in a step S51). After the restart has been completed, the controller 200A requests (in a step S52) the controller 200B to transfer the command information. During the period while the program is being updated on the side of the controller 200A, access requests from the host 10 are processed (in the step S45) by the controller 200B. Accordingly, the newest user data and control information are stored by the cache memory 250B of the controller 200B.
  • the controller 200B transmits (in a step S53) the common information which is stored in the cache memory 250B to the controller 200A. And the controller 200A stores (in a step S54) this common information which it has received from the controller 200B in its cache memory 250A. It should be understood that the steps S52, S53, and S54 may be omitted, if the cache memory 250A and the cache memory 250B are already operating in the synchronized mode at the time point that a command is issued for updating execution of the program.
  • the controller 200A notifies (in a step S56) the management terminal 20 of the fact that the program updating on the side of the controller 200A has been completed normally.
  • the management terminal checks this notification of updating completion from the controller 200A (in a step S57), it commands the controller 200B to perform program updating (in a step S58). Thereafter, the same procedures as in the above steps S42 through S57 for the controller 200A are repeated for the controller 200B.
  • the storage control device 100 is able to update the programs of the plurality of controllers 200A and 200B alternatingly. Access requests during the period of program updating are processed by the other controller from the one which processes them before program updating or after program updating. Accordingly the host 10 does not notice either that the destination for processing of access requests has been changed over, or that program updating has been performed, and it is able to continue issuing access requests as per normal, and to receive the results of processing them.
  • Fig. 11 is a flow chart showing the flow of control for the update processing shown in S49 of Fig. 10.
  • the controller 200A decides (in a step S491) whether or not to update a program P10 within the program memory 241.
  • the controller 200A If a new program P11 which should replace the program P10 (the old program) in the program memory 241 is included in the new programs which have been received from the management terminal 20 (S491: YES), then the controller 200A reads out the new program P11 from the empty disk 312 (in a step S492). And the controller 200A replaces the old program P10 in the program memory 241 with the new program P11 (in a step S493). And the controller 200A decides (in a step S494) whether or not the updating of the program has been completed normally.
  • the controller 200A decides whether or not the program P20 within the boot disk 311 is to be updated (in a step S495). If, instead of the program P20, a new program P21 has been received from the management terminal 20 (S495: YES), then the controller 200A reads out this new program P21 from the empty disk 312 (in a step S496), and replaces the program P20 (in a step S497).
  • the controller 200A decides (in a step S498) whether or not the program updating has been completed normally, and, if it has been completed normally (S498: YES), then this processing is terminated. On the other hand, if due to some cause an error has occurred in the program updating (S494: NO or S498: NO), then the controller 200A notifies this error to the management terminal 20 (S499). On receipt of this error notification, the management terminal 20 is able to re-issue the update command.
  • program updating means updating of all of the programs, or of only a part thereof.
  • This embodiment having a structure like that described above, furnishes the following beneficial effects.
  • the host side I/F unit 210A of the controller 200A which is the object of updating to be connected to the interior bus of the controller 200B which is the destination of processing delegation via the mutual communication path 400. Accordingly, there is no stoppage of access requests from the host 10 during the updating the program of the controller 200A, and it is possible to continue processing. Due to this, there is no requirement to provide any redundant path between the host 10 and the storage control device 100, and it is not necessary to perform any path changeover control or the like on the side of the host 10, so that it is possible to perform updating of the programs while continuing so-called non-stop operation. Accordingly, no burden is imposed on the host 10, and, without the host 10 being conscious thereof, it is possible to perform smooth program updating in a comparatively simple manner and moreover at a low cost, so that the convenience of use is enhanced.
  • the cache memories 250A and 250B are synchronized before connecting the host side interior bus 401 to the controller 200B which is the processing delegate. Accordingly, the controller 200B which is entrusted with the delegation of processing is able to perform matching data processing, based on the common information within the cache memory 250B.
  • the program on the side of the controller 200A is updated after the access request processing on the side of the controller 200A has been delegated to the controller 200B. Accordingly, it is possible to update the program without stopping the storage control device 100.
  • the bus switches 266 is arranged for the bus switches 266 to be provided within the data transfer control circuits 260A and 260B, and to change over the destination of connection of the host side I/F unit 210A. Accordingly, there is no increase of the number of components of the controllers 200A and 200B, and it is possible to perform program updating during operation, without stopping.
  • the execution of program updating from the host 10A is commanded by a so-called inband method.
  • notification of update commands and the like was provided from the management terminal 20 to the storage control device 100 via the network for management CN13.
  • Such a method is termed an "out-of-band" method.
  • the updating of programs is commanded using the network CN11 for data input and output.
  • Fig. 12 is an explanatory figure showing the overall structure of a storage system according to this second embodiment.
  • all or a portion of the functions of the management terminal 20 are provided within the host 10A.
  • This host 10A comprises at least a new program storage unit 13 and an update command unit 14.
  • the new program storage unit 13 corresponds to the above described new program storage unit 21 of the first embodiment, while the update command unit 14 corresponds to the above described update command unit 22 of the first embodiment.
  • This new program storage unit 13 is a means for storing a program for updating.
  • this update command unit 14 is a means for commanding the storage control device 100 to update the program.
  • the functions of the management terminal 20 are provided in the host 10A, and the network for management CN13 for commanding the updating of programs from the host 10A is eliminated.
  • Fig. 13 is a flow chart showing the update control procedure.
  • the host 10A transmits (in a step S61) an update execution command along with a new program to the controller 200A which is the initial object of program updating (S61). And the controller 200A receives this new program and stores it (in a step S62) in the empty disk 311.
  • the controller 200A transfers (in a step S63) the common information which is stored in the cache memory 250A to the cache memory 250B, and makes the stored contents of both of the cache memories 250A and 250B agree with one another (in a step S64). It should be understood that, as described above, if the synchronization mode is already operating, the steps S63 and S64 may be omitted. Furthermore, it would also be possible not to transmit the entire contents of the common information stored in the cache memory 250A to the cache memory 250B, but instead to transmit only the differences with the cache memory 250B thereto.
  • the controller 200A updates the program (in a step S67).
  • the controller 200B processes the access request from the host 10A (in a step S66).
  • the controller 200A performs self-checking processing (in a step S68) and restarts (in a step S69).
  • the controller 200A requests (in a step S70) the controller 200B to transfer the common information which is stored in the cache memory 250B. And the controller 200B transmits to the controller 200A (in a step S71) the common information, in which the results of data processing during the period that the processing of access requests was delegated is reflected.
  • the controller 200A reconnects (in a step S73) the host side interior bus 401 to the interior bus of the data transfer control circuit 260A, after the stored contents of the cache memories 250A and 250B have been made to agree with one another. And the controller 200A notifies (in a step S74) the host 10A to the effect that the updating of the program has been completed normally. After the host 10A has checked the completion of updating of the program on the side of the controller 200A (in a step S75), next, it commands program updating (in a step S76) to the controller 200B, which should be updated. And, subsequently, the same processes as in the steps S62 through S75 above are performed.
  • This embodiment with this type of structure also furnishes the same beneficial operational effects as the first embodiment described above.
  • the updating execution is commanded with the inband method, accordingly it is possible to eliminate the management terminal 20 and the network for management CN13, so that it is possible to simplify the entire structure.
  • FIG. 14 A third embodiment of the present invention will now be explained with reference to Fig. 14.
  • the management function 15 for managing the updating of the program is provided to the host 10B.
  • the point of difference from the second embodiment described above, is that the updating commands and so on are transmitted to the storage control device 100 via the network for management CN13.
  • Fig. 14 is an explanatory figure showing the overall structure of a storage system according to this third embodiment.
  • the host 10B is provided with a management function 15.
  • a management function 15 To this management function 15, there are provided a new program storage unit 16 for storing the new program, and an update command unit 17 for commanding the updating of the program.
  • this management function 15 is connected to the network for management CN13 via a LAN I/F 18.
  • the operation of this embodiment is the same as that of the first embodiment. However, the exchange of information related to program updating is performed between the management function 15 and each of the controllers 200A and 200B.
  • This embodiment with this type of structure also furnishes the same beneficial operational effects as the first embodiment described above.
  • the management function 15 is provided within the host 10B, accordingly it is possible to eliminate the management terminal 20, so that it is possible to simplify the entire structure.
  • the commands related to updating are performed using the network for management CN13, accordingly the transfer of the update command and of the program for updating does not exert any influence on normal data input and output.
  • the updating period for the program is controlled based on the priority level for updating the program, and on the state of the storage control device 100.
  • Fig. 15 is an explanatory figure showing the overall structure of a storage system according to this fourth embodiment.
  • this storage system further comprises a management center 30.
  • This management center 30 is a computer device for managing program output of the storage control device 100 in a unified manner.
  • the management center 30 is connected to the management terminal 20 via a communication network CN14 such as, for example, a WAN (Wide Area Network).
  • a communication network CN14 such as, for example, a WAN (Wide Area Network).
  • the management center 30 is only shown as being connected to a single management terminal 20, actually it could be connected to each of a plurality of management terminals.
  • the communication network CN13 can serve as the communication network CN14.
  • the management center 30 may comprise a new program storage unit 31 and a program update notification unit 32.
  • the new program storage unit 31 stores a new program for updating.
  • the program notification unit 32 notifies the management terminal 20 to the effect that it is necessary to update to the new program.
  • Fig. 16 is a flow chart showing the flow of control of an updating execution period decision process for controlling the execution timing of the update control procedure. If it has been decided that a requirement for program updating has occurred (S81: YES), then the management center 30 notifies the management terminal 20 (in a step S82) to the effect that the program ought to be updated, and of the priority level of the update. If, for example, the program update relates to an improvement of security, then a comparatively high priority level will be set. However, if the program update relates to an improvement in data processing performance, then a comparatively low priority level will be set.
  • the management terminal 20 checks that a requirement for program updating has occurred, and stores the priority level of this program update (in a step S83). And the management center 30 reads out the new program from the new program storage unit 31, and transmits it (in a step S84) to the management terminal 20. The management terminal 20 stores the new program which it has received from the management center 30 in the new program storage unit 21 (in a step S85).
  • the management terminal 20 compares together the priority level of the program update which has been notified from the management center 30 and a predetermined threshold value which is set in advance, and decides whether or not this priority level is greater than a predetermined threshold value (in a step S86). If the priority level is greater than the predetermined threshold value (S86: YES), then the management terminal 20 commands (in a step S87) program updating execution to the storage control device 100 (the controller 200A which is initially upgraded). Due to this, the storage control device 100 executes (in a step S88) the update control procedure described in Fig. 10.
  • the management terminal 20 requests the storage control device 100 to transfer the state of the storage control device 100 (in a step S89).
  • the state of the storage control device 100 is meant, for example, the load state of the storage control device 100. It is possible to decide on the load state, for example, from the number of access requests per unit time (IOPS), from the usage ratios of the cache memories 250A and 250B, or from the usage ratios of the processors 230A and 230B or the like.
  • the storage control device 100 transmits its own state to the management terminal 20 (in a step S90).
  • the management terminal 20 stores this state of the storage control device 100 (in a step S91).
  • the management terminal 20 decides (in a step S92), based on the state of the storage control device 100, whether or not this is an appropriate time to execute program updating.
  • the load state of the storage control device 100 becomes heavy in a case such as when the storage control device 100 is processing a large number of access requests, or when it is executing backup processing to a tape device. In this case, it is not appropriate to perform a program update whose urgency is low. By contrast, if the load state of the storage control device 100 is light, then there will be no inconvenience even if program updating is performed.
  • the management terminal 20 commands the storage control device 100 to perform updating of the program (in a step S93). Due to this, the storage control device 100 performs program updating (in a step S94).
  • the management terminal 20 acquires the state of the storage control device 100 again (in a step S89), after having, for example, waited until a predetermined time period has elapsed. In this manner, the management terminal 20 issues the updating command to the storage control device 100 by deciding for itself the most appropriate timing for updating the program.
  • This fourth embodiment with this type of structure furnishes the same beneficial effects as the first embodiment.
  • the update period is selected based on the priority level of the program update and the state of the storage control device 100, accordingly it is possible to update the program when the load on the storage control device 100 is light, and thus it is possible to update the program smoothly while preventing decrease of performance of the storage system.
  • FIG. 17 A fifth embodiment of the present invention will now be explained with reference to Fig. 17.
  • the bus switches 266 are eliminated from the data transfer control circuits 260A and 260B, and path changeover switches 270A and 270B are provided exterior to the data transfer control circuits 260A and 260B.
  • path changeover switches 270A and 270B are each connected to the mutual communication path control unit 264 via the bus 405.
  • the path changeover switches 270A and 270B are endowed with a normal mode and an updating mode, just as the bus switches 266 were.
  • the host side I/F unit 210A is connected to the data transfer control circuit 260A
  • the host side I/F unit 210B is connected to the data transfer control circuit 260B.
  • the path changeover switch 270A is in the updating mode
  • the host side I/F unit 210A is connected via the bus 405 and the mutual communication path 400 to the data transfer control circuit 260B.
EP06255218A 2006-02-14 2006-10-11 Dispositif de contrôle de stockage et système de stockage Withdrawn EP1821188A3 (fr)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
JP2006035953A JP2007219571A (ja) 2006-02-14 2006-02-14 記憶制御装置及びストレージシステム

Publications (2)

Publication Number Publication Date
EP1821188A2 true EP1821188A2 (fr) 2007-08-22
EP1821188A3 EP1821188A3 (fr) 2009-09-30

Family

ID=37600755

Family Applications (1)

Application Number Title Priority Date Filing Date
EP06255218A Withdrawn EP1821188A3 (fr) 2006-02-14 2006-10-11 Dispositif de contrôle de stockage et système de stockage

Country Status (3)

Country Link
US (1) US8089487B2 (fr)
EP (1) EP1821188A3 (fr)
JP (1) JP2007219571A (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2010146629A1 (fr) * 2009-06-18 2010-12-23 Hitachi, Ltd. Appareil de commande de stockage et procédé permettant de commander la commande de stockage
EP2316194A2 (fr) * 2008-08-18 2011-05-04 F5 Networks, Inc Mise à niveau de dispositifs de gestion de trafic de réseau tout en maintenant la disponibilité

Families Citing this family (27)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007096956A1 (fr) * 2006-02-22 2007-08-30 Fujitsu Limited Unite centrale
JP5034790B2 (ja) * 2007-08-31 2012-09-26 富士ゼロックス株式会社 データ処理システム
WO2009050761A1 (fr) * 2007-10-15 2009-04-23 Fujitsu Limited Système de mémorisation, contrôleur de mémorisation et procédé et programme pour contrôler le système de mémorisation
US20090213129A1 (en) * 2008-02-25 2009-08-27 Kuo-Yang Li Storage Unit and Storage Module for Storing EDID
US8924947B2 (en) * 2008-03-05 2014-12-30 Sap Se Direct deployment of static content
JP2009230484A (ja) * 2008-03-24 2009-10-08 Nec Corp ストレージサブシステム、ストレージシステム、ファームウェア置換方法、及びプログラム
JP4413976B2 (ja) * 2008-05-23 2010-02-10 株式会社東芝 情報処理装置及び情報処理装置のバージョンアップ方法
JP5223612B2 (ja) * 2008-11-14 2013-06-26 日本電気株式会社 ディスク制御装置およびファームウェアの更新方法
JP5371095B2 (ja) * 2009-04-20 2013-12-18 株式会社日立ソリューションズ パッチ適用システム
JP5358736B2 (ja) * 2009-11-10 2013-12-04 株式会社日立製作所 複数のコントローラを備えたストレージシステム
WO2011058821A1 (fr) * 2009-11-11 2011-05-19 日本電気株式会社 Système de stockage, procédé de mise à jour de système de stockage et programme
JP5152603B2 (ja) 2010-10-04 2013-02-27 日本電気株式会社 ディスクアレイ装置及びそのファームウェア更新方法
JP2012128697A (ja) * 2010-12-16 2012-07-05 Hitachi Ltd 情報処理装置
US8375385B1 (en) * 2011-12-19 2013-02-12 Emc Corporation Techniques for parallel drive upgrade while maintaining host accessibility
JP5928707B2 (ja) * 2012-05-01 2016-06-01 株式会社日立製作所 セキュリティポリシ配布実行システムおよびセキュリティポリシ実行方法
JP6056424B2 (ja) * 2012-11-29 2017-01-11 株式会社デンソー 車載プログラム更新装置
JP5907105B2 (ja) * 2013-03-26 2016-04-20 日本電気株式会社 ストレージ装置、方法、及び、プログラム。
WO2014188537A1 (fr) * 2013-05-22 2014-11-27 株式会社日立製作所 Système de contrôle de charge de client virtuel et procédé de contrôle de charge de client virtuel
US9959107B2 (en) * 2013-06-28 2018-05-01 Samsung Electronics Co., Ltd. Method and apparatus for updating application
JP2017010390A (ja) * 2015-06-24 2017-01-12 富士通株式会社 ストレージ制御装置、ストレージ制御プログラム、およびストレージ制御方法
JP6797588B2 (ja) * 2016-07-22 2020-12-09 株式会社東芝 検証システム
DE102016114805A1 (de) * 2016-08-10 2018-02-15 Kriwan Industrie-Elektronik Gmbh Verfahren sowie eingebettetes System zur Überwachung, Steuerung oder Regelung einer Maschine
JP6812900B2 (ja) * 2017-05-17 2021-01-13 富士通株式会社 ストレージ装置、ストレージ制御装置、およびストレージ制御プログラム
JP2019125292A (ja) * 2018-01-19 2019-07-25 Ｎｅｃプラットフォームズ株式会社 制御装置
JP6835414B2 (ja) * 2018-07-20 2021-02-24 Ｎｅｃプラットフォームズ株式会社 通信制御装置、通信制御システム、通信システム、通信制御方法、及び制御プログラム
JP2021002108A (ja) * 2019-06-20 2021-01-07 株式会社日立製作所 ストレージシステム
WO2023084567A1 (fr) * 2021-11-09 2023-05-19 三菱電機株式会社 Dispositif de commande pour véhicule

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040143829A1 (en) 2002-10-28 2004-07-22 Hitachi, Ltd. Control apparatus of storage unit, and method of controlling the control apparatus of storage unit
EP1569084A1 (fr) 2004-02-25 2005-08-31 Hitachi, Ltd. Système et procédé de traitement d'information

Family Cites Families (31)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4137565A (en) * 1977-01-10 1979-01-30 Xerox Corporation Direct memory access module for a controller
JP2567922B2 (ja) * 1988-08-30 1996-12-25 株式会社日立製作所 パス制御方式
JP3732869B2 (ja) * 1995-06-07 2006-01-11 株式会社日立製作所 外部記憶装置
AU2521297A (en) * 1996-04-11 1997-10-29 Hitachi Limited Disk drive and computer
US5750028A (en) * 1996-09-18 1998-05-12 Envirogen, Inc. Biomass separation apparatus and method with media return
US6014730A (en) * 1996-12-26 2000-01-11 Nec Corporation Dynamic adding system for memory files shared among hosts, dynamic adding method for memory files shared among hosts, and computer-readable medium recording dynamic adding program for memory files shared among hosts
KR100258966B1 (ko) * 1997-05-02 2000-06-15 윤종용 시리얼 통신을 이용한 바이오스 업그레이드 방법
US6571324B1 (en) 1997-06-26 2003-05-27 Hewlett-Packard Development Company, L.P. Warmswap of failed memory modules and data reconstruction in a mirrored writeback cache system
JPH11282779A (ja) * 1998-03-27 1999-10-15 Matsushita Electric Ind Co Ltd ファイル配信システム
JP3950589B2 (ja) * 1998-08-28 2007-08-01 キヤノン株式会社 情報処理装置、プログラム更新方法および記憶媒体
WO2000077606A2 (fr) * 1999-06-11 2000-12-21 Storage Technology Corporation Reseau a zones de memoire intelligentes
JP3853540B2 (ja) * 1999-06-30 2006-12-06 日本電気株式会社 ファイバチャネル接続磁気ディスク装置およびファイバチャネル接続磁気ディスク制御装置
US6343324B1 (en) * 1999-09-13 2002-01-29 International Business Machines Corporation Method and system for controlling access share storage devices in a network environment by configuring host-to-volume mapping data structures in the controller memory for granting and denying access to the devices
JP2001306412A (ja) * 2000-04-27 2001-11-02 Fuji Electric Co Ltd Ｓｃｓｉバス制御装置
US7228538B1 (en) * 2000-05-02 2007-06-05 International Business Machines Corporation Method, system, and program for updating firmware to a storage system comprised of multiple controllers
JP2002123479A (ja) * 2000-10-17 2002-04-26 Hitachi Ltd ディスク制御装置およびそのキャッシュ制御方法
US6681339B2 (en) * 2001-01-16 2004-01-20 International Business Machines Corporation System and method for efficient failover/failback techniques for fault-tolerant data storage system
US20020112043A1 (en) * 2001-02-13 2002-08-15 Akira Kagami Method and apparatus for storage on demand service
JP4083505B2 (ja) * 2001-08-27 2008-04-30 株式会社リコー 画像形成装置，プログラム更新方法および記録媒体
US6912669B2 (en) * 2002-02-21 2005-06-28 International Business Machines Corporation Method and apparatus for maintaining cache coherency in a storage system
JP4128516B2 (ja) * 2002-11-18 2008-07-30 株式会社リコー 画像形成装置、プログラム更新方法
JP4330889B2 (ja) * 2003-01-20 2009-09-16 株式会社日立製作所 記憶デバイス制御装置にソフトウエアをインストールする方法、記憶デバイス制御装置の制御方法、及び記憶デバイス制御装置
US7555657B2 (en) * 2003-03-28 2009-06-30 Ricoh Company, Ltd. Communication device, software update device, software update system, software update method, and program
JP2005115603A (ja) * 2003-10-07 2005-04-28 Hitachi Ltd 記憶デバイス制御装置及びその制御方法
US7117310B2 (en) * 2004-02-18 2006-10-03 Lsi Logic Corporation Systems and methods for cache synchronization between redundant storage controllers
JP2005309818A (ja) * 2004-04-22 2005-11-04 Hitachi Ltd ストレージ装置、そのデータ読出方法、及びそのデータ読出プログラム
US20050288800A1 (en) * 2004-06-28 2005-12-29 Smith William D Accelerating computational algorithms using reconfigurable computing technologies
JP4870915B2 (ja) * 2004-07-15 2012-02-08 株式会社日立製作所 ストレージ装置
US7418557B2 (en) * 2004-11-30 2008-08-26 International Business Machines Corporation Managing multiprocessor operations
JP2006252031A (ja) * 2005-03-09 2006-09-21 Nec Corp ディスクアレイコントローラ
US7328324B2 (en) * 2005-04-27 2008-02-05 Dot Hill Systems Corp. Multiple mode controller method and apparatus

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040143829A1 (en) 2002-10-28 2004-07-22 Hitachi, Ltd. Control apparatus of storage unit, and method of controlling the control apparatus of storage unit
EP1569084A1 (fr) 2004-02-25 2005-08-31 Hitachi, Ltd. Système et procédé de traitement d'information
JP2005242574A (ja) 2004-02-25 2005-09-08 Hitachi Ltd 情報処理システム、および情報処理方法

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2316194A2 (fr) * 2008-08-18 2011-05-04 F5 Networks, Inc Mise à niveau de dispositifs de gestion de trafic de réseau tout en maintenant la disponibilité
EP2316194A4 (fr) * 2008-08-18 2013-08-28 F5 Networks Inc Mise à niveau de dispositifs de gestion de trafic de réseau tout en maintenant la disponibilité
WO2010146629A1 (fr) * 2009-06-18 2010-12-23 Hitachi, Ltd. Appareil de commande de stockage et procédé permettant de commander la commande de stockage
US8285943B2 (en) 2009-06-18 2012-10-09 Hitachi, Ltd. Storage control apparatus and method of controlling storage control apparatus

Also Published As

Publication number Publication date
EP1821188A3 (fr) 2009-09-30
US20070188507A1 (en) 2007-08-16
JP2007219571A (ja) 2007-08-30
US8089487B2 (en) 2012-01-03

Similar Documents

Publication Publication Date Title
EP1821188A2 (fr) Dispositif de contrôle de stockage et système de stockage
JP4723290B2 (ja) ディスクアレイ装置及びその制御方法
JP3732869B2 (ja) 外部記憶装置
US7028177B2 (en) Array controller ROM cloning in redundant controllers
US8209505B2 (en) Storage system and method of taking over logical unit in storage system
JP3772369B2 (ja) 記憶サブシステム
US7360047B2 (en) Storage system, redundancy control method, and program
EP1026575A2 (fr) Système de réseau de disques et méthode pour changer sa configuration
US20080098183A1 (en) Disk array system and method for migrating from one storage system to another
EP1758018A2 (fr) Système de stockage et procédé de contrôle de stockage
JP2004021989A (ja) データをバックアップする方法
JP5286212B2 (ja) ストレージクラスタ環境でのリモートコピー制御方法及びシステム
US11573737B2 (en) Method and apparatus for performing disk management of all flash array server
JP2004199277A (ja) Ｂｉｏｓの冗長管理方法、データ処理装置及びストレージシステム
US9342418B2 (en) Storage system, storage control device and data transfer method
JP5314731B2 (ja) データ処理装置間の基本入出力プログラムの同期化方法及びコンピュータシステム
JP4456121B2 (ja) コンピュータ・クラスタ、コンピュータ・ユニット、および、コンピュータ・ユニット間における記憶アクセス制御方法
JP2005174178A (ja) ディスクアレイ装置及びディスクアレイ装置の保守方法
JP2006260141A (ja) 記憶システムの制御方法、記憶システム、記憶制御装置、記憶システムの制御プログラム、情報処理システム
JP2006114064A (ja) 記憶サブシステム
US20200319977A1 (en) Method for backing up and restoring digital data stored on a solid-state storage device and a highly secure solid-state storage device
US20220066889A1 (en) Method and apparatus for performing node information exchange management of all flash array server
JP2005122763A (ja) 記憶装置
JP5345655B2 (ja) 基本入出力プログラムの冗長管理方法及びデータ処理装置
TWM592626U (zh) 用於儲存區域網路的節點裝置

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20061031

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR

AX Request for extension of the european patent

Extension state: AL BA HR MK YU

PUAL Search report despatched

Free format text: ORIGINAL CODE: 0009013

AK Designated contracting states

Kind code of ref document: A3

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR

AX Request for extension of the european patent

Extension state: AL BA HR MK RS

RIC1 Information provided on ipc code assigned before grant

Ipc: G06F 9/445 20060101ALI20090824BHEP

Ipc: G06F 3/06 20060101AFI20070507BHEP

AKX Designation fees paid

Designated state(s): DE FR GB IE

17Q First examination report despatched

Effective date: 20100526

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN WITHDRAWN

18W Application withdrawn

Effective date: 20121113