US20060248302A1 - Storage unit, installation method thereof and installation program therefore - Google Patents

Storage unit, installation method thereof and installation program therefore Download PDF

Info

Publication number
US20060248302A1
US20060248302A1 US11/476,704 US47670406A US2006248302A1 US 20060248302 A1 US20060248302 A1 US 20060248302A1 US 47670406 A US47670406 A US 47670406A US 2006248302 A1 US2006248302 A1 US 2006248302A1
Authority
US
United States
Prior art keywords
storage unit
storage
logical
host computer
logical device
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.)
Abandoned
Application number
US11/476,704
Inventor
Yasutomo Yamamoto
Yoshiaki Eguchi
Ai Satoyama
Hiroshi Ohno
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.)
Individual
Original Assignee
Individual
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 Individual filed Critical Individual
Priority to US11/476,704 priority Critical patent/US20060248302A1/en
Publication of US20060248302A1 publication Critical patent/US20060248302A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input 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/06Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601Interfaces specially adapted for storage systems
    • G06F3/0602Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
    • G06F3/0604Improving or facilitating administration, e.g. storage management
    • G06F3/0607Improving 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
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input 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/06Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601Interfaces specially adapted for storage systems
    • G06F3/0602Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
    • G06F3/0604Improving or facilitating administration, e.g. storage management
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input 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/06Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601Interfaces specially adapted for storage systems
    • G06F3/0628Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0629Configuration or reconfiguration of storage systems
    • G06F3/0631Configuration or reconfiguration of storage systems by allocating resources to storage systems
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input 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/06Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601Interfaces specially adapted for storage systems
    • G06F3/0628Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0629Configuration or reconfiguration of storage systems
    • G06F3/0632Configuration or reconfiguration of storage systems by initialisation or re-initialisation of storage systems
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input 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/06Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601Interfaces specially adapted for storage systems
    • G06F3/0628Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0629Configuration or reconfiguration of storage systems
    • G06F3/0637Permissions
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input 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/06Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601Interfaces specially adapted for storage systems
    • G06F3/0628Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0646Horizontal data movement in storage systems, i.e. moving data in between storage devices or systems
    • G06F3/0647Migration mechanisms
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input 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/06Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601Interfaces specially adapted for storage systems
    • G06F3/0668Interfaces specially adapted for storage systems adopting a particular infrastructure
    • G06F3/067Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]

Definitions

  • the present invention relates to a storage unit that is installed newly into a computer system comprising a first storage unit and a host computer accessing the first storage unit, and an installation method thereof and an installation program therefor.
  • a mode of installation namely, a mode in which the old storage unit is used as ever, and the new storage unit is used together with the old storage unit, and a mode in which all the data on the old storage unit are migrated onto the new storage unit.
  • Japanese Patent Publication No. 10-508967 discloses a technique of migrating data of an old storage unit onto a new storage unit.
  • data of a first device in the old storage unit are migrated onto a second device assigned to the new storage unit.
  • a host computer's access destination is changed from the existing first device to the new second device.
  • An input-output request from the host computer to the existing first device is received by the new storage unit.
  • a read request a part whose migration is finished is read from the new second device, while a part that has not been migrated yet is read from the existing first device.
  • dual writing is performed toward both the first and second devices.
  • An object of the present invention is to provide such a storage unit, an installation method thereof and an installation program therefor that can enjoy merits such as high function, high performance and high reliability of a new storage unit at the time of installation of the new storage unit, suppressing cost increase.
  • the present invention follows the below-described procedures to install a new storage unit (referred to as a second storage unit) into a computer system comprising a host computer and an existing first storage unit, wherein the host computer and the first storage unit are connected through a first network such as SAN, LAN, or the like.
  • a new storage unit referred to as a second storage unit
  • a first network such as SAN, LAN, or the like.
  • the new second storage unit is connected to the first network. Then, zoning setting of a switch existing in the first network and access right setting of the first storage unit are changed such that the second storage unit can access a storage device in the first storage unit.
  • a logical device hereinafter, referred to as a first logical device
  • a second logical device a logical device relating to the storage device of the first storage unit
  • the first logical device of the first storage unit is associated with the second logical device of the second storage unit.
  • path definition and device recognition in the host computer are performed such that the host computer can recognize the second logical device of the second storage unit and can access the second logical device of the second storage unit.
  • input-output setting of the host computer is changed such that processing of an input-output from the host computer to the storage device of the first storage unit is requested to the second storage unit.
  • the substance of the second logical device is the storage device in the first storage unit, and a storage device storing the data of the second logical device is not held in the second storage unit.
  • the zoning setting of the switch existing in the first network and the access right setting of the first storage unit are changed such that direct access from the host computer to the storage device of the first storage unit is inhibited.
  • the second storage unit when the second storage unit receives a read request from the host computer to the second logical device, then, the second storage unit converts the read request into a read request to the first logical device, and sends the converted request to the first storage unit. Receiving an input-output processing completion report from the first storage unit, the second storage unit sends the host computer a completion report relating to the input-output request to the second logical device.
  • the second storage unit can process an input-output request to the storage device in the first storage unit. Accordingly, merits of the new storage unit, such as high performance, high reliability and high function, can be applied to the device in the existing first storage unit.
  • the second storage unit can apply a replicating function such as data replication and copy to a remote place, or access right control for each device.
  • the second logical device of the second storage unit is assigned to the first logical device of the first storage unit, and the host computer recognizes the first logical device of the first storage unit as the second logical device of the second storage unit.
  • a physical device that becomes the substance of the second logical device is allocated from an unused storage space in the second storage unit, and a part or all of the data of the storage devices of the first storage unit are migrated.
  • this read request is sent to the first storage unit, as a read request to the first logical device.
  • this read request relates to data that have been migrated already
  • this read request is processed in the second storage unit, as a read request to the above-mentioned physical device as the subject of the second logical device.
  • dual writing is performed toward the first logical device of the first storage unit and toward the physical device of the second storage unit.
  • setting is changed such that the physical device of the second storage unit is seen as the second logical device.
  • the second storage unit When the second storage unit is installed according to the above-described method, then, also with respect to data that are actually stored in the existing first storage unit, the host computer access the new second storage unit.
  • merits of the new second storage unit such as high performance, high functions, and high reliability of the second storage unit, can be enjoyed even when data actually stored in the existing first storage unit are accessed.
  • the merits of the newly-installed storage unit can be applied to all the data including the data in the existing first storage unit.
  • the existing storage unit and the new storage unit are used jointly, and storage capacity of the new storage unit can be smaller, and installation costs can be the smallest.
  • FIG. 1 is a block diagram showing a computer system as an embodiment of the present invention
  • FIG. 2 is a diagram showing an example configuration of a logical device management information table in an embodiment of the present invention
  • FIG. 3 is a diagram showing an example configuration of a RAID management information table in an embodiment of the present invention.
  • FIG. 4 is a diagram showing an example configuration of an external device management information table in an embodiment of the present invention.
  • FIG. 5 is a flowchart showing a procedure of installing a new storage unit in an embodiment of the present invention
  • FIG. 6 is a flowchart showing a migration procedure at the time of migrating data from an existing first storage unit to a new second storage unit in an embodiment of the present invention
  • FIG. 7 is a flowchart showing a procedure of processing an input-output request from a host to a new second storage unit in an embodiment of the present invention
  • FIG. 8 is a flowchart showing a processing procedure at the time of adding a disk unit to a new second storage unit in an embodiment of the present invention.
  • FIG. 9 is a diagram showing an example configuration of a logical device access statistical information table in an embodiment of the present invention.
  • a computer system of the present invention comprises a host computer 11 , a fibre channel switch 18 ; two storage units 12 a and 12 b (referred to as a storage unit 12 , by a general term) and a management server 13 .
  • the host computer 11 is connected with the two storage units 12 a and 12 b through the fibre channel switch 18 and cables. Further, the host computer 11 , the two storage units 12 a and 12 b and the fibre channel switch 18 are connected to the management server 13 through an IP network 142 .
  • the host computer 11 comprises a CPU, a memory, and the like, and performs predetermined functions when the CPU reads and executes an operating system (hereinafter, referred to as OS) and application programs stored in the memory.
  • OS operating system
  • a first storage unit 12 b is an existing storage unit
  • a second storage unit 12 a is a newly installed storage unit.
  • the first storage unit 12 b comprises a disk unit 121 , a disk controller 122 , a port 123 for connecting with the host computer 11 , and a network interface 125 for connecting with the IP network 142 .
  • the first storage unit 12 b may comprise a plurality of disk units and a plurality of ports.
  • the second storage unit 12 a comprises a plurality of disk units 121 , a disk controller 122 , a port 123 a for connecting with the host computer 11 and a plurality of ports 123 b for connecting with the other storage units (referred to as a port 123 , by a general term), and a network interface 125 for connecting with the IP network 142 .
  • a disk unit or units 121 as hardware are defined collectively as one or a plurality of physical devices, and one logical device (i.e., one device from a logical viewpoint) is assigned to one physical device.
  • one logical device i.e., one device from a logical viewpoint
  • a port 123 of a storage unit 12 in the present embodiment it is assumed to use the fibre channel interface whose upper protocol is SCSI (Small Computer System Interface).
  • SCSI Small Computer System Interface
  • another network interface for storage connection such as IP network interface whose upper protocol is SCSI, may be used.
  • a disk controller 122 of a storage unit 12 comprises a processor, a cache memory 124 and a control memory, and communicate with the management server 13 through the network interface 125 and controls the disk unit 121 .
  • the processor controls access from the host computer 11 and controls the disk unit 121 , based on various kinds of information stored in the control memory. In particular, in the case where a plurality of disk units 121 (not a single disk unit 121 ) such as ones in a disk array are presented as one or plurality of logical devices to the host computer 11 , the processor performs processing and management relating to the disk units 121 .
  • the control memory stores programs executed by the processor and various kinds of management information.
  • As one of the programs executed by the processor there may be a disk controller program.
  • This disk controller program includes an installation program for installing the second storage unit 12 a into a computer system.
  • This installation program and the disk controller program including it are executed by the processor to function as a storage installation controller 129 and the disk controller, respectively.
  • logical device management information 126 for management of the logical devices of the second storage unit 12 a ; RAID (Redundant Array of Independent Disk) management information 127 for management of physical devices consisting of the plurality of disk units 121 of the second storage unit 12 a , and external device management information 128 for management of correspondence between the logical devices of the second storage unit 12 a and the logical devices of the first storage unit 12 b.
  • RAID Redundant Array of Independent Disk
  • the cache memory 124 stores data that are frequently read, or temporally stores write data from the host computer 11 .
  • the host computer 11 is connected with the fibre channel switch 18 through an interface (I/F) 112 , and also with the management server through a network interface 113 .
  • software program
  • DLM device link manager
  • the DLM 111 manages correspondence between the logical devices (recognized through the interface 112 ) of the storage unit 12 and device files as device management units of the OS.
  • a logical device is connected with a plurality of interfaces 112 and a plurality of ports 123 , the host computer 11 recognizes that logical device as a plurality of devices having different addresses, and different device files are defined, respectively.
  • a plurality of device files corresponding to one logical device are managed as a group by the DLM 11 , and a virtual device file as a representative of the group is provided to upper levels, so that alternate paths and load distribution can be realized. Further, in the present embodiment, the DLM 111 also adds/deletes a new device file to/from a specific device file group and changes a main path within a device file group, according to an instruction from a storage manager 131 located in the management server 13 .
  • the management server 13 performs operation, maintenance and management of the whole computer system.
  • the management server 13 comprises a network interface 133 , and connects with the host computer 11 , the two storage units 12 a and 12 b , and the fibre channel switch 18 , through the IP network 142 .
  • the management server 13 collects configuration information, resource utilization factors, performance monitoring information from various units 11 , 12 and 18 , presents them to a storage administrator, and sends operation/maintenance instructions to those units.
  • the mentioned processing is performed by the storage manager 131 operating on the management server 13 .
  • the storage manager 131 comprises a processor and a memory.
  • the memory stores a storage manager program executed by the processor.
  • This storage manager program includes an installation program for installing a new storage unit.
  • This installation program and the storage manager program including it are executed by the processor to function as an installation controller 134 and the storage manager 131 , respectively.
  • this installation program is installed onto the existing management server 13 , except the case where a new management server incorporated with the installation program is employed.
  • the fibre channel switch 18 comprises a plurality of ports 181 . Each port 181 is connected with the interface 112 of the host computer 11 or a port 123 of the storage unit 12 a or 12 b , so that each of those devices can communicate with another device.
  • the fibre channel switch 18 comprises a network interface 182 , and is connected with the IP network 142 also. Due to this arrangement, from the physical viewpoint, any host computer 11 can access all the storage units 12 a and 12 b connected to the fibre channel switch 18 . Further, the fibre channel switch 18 has a function called zoning, i.e., a function of limiting communication from a specific port to another specific port.
  • This function is used, for example, when access to a specific port 123 of a specific storage 12 is limited to a specific host 11 .
  • a method of controlling combinations of a sending port and a receiving port may be mentioned a method in which an identifier assigned to a port 181 of the fibre channel switch is used, and a method in which WWN (World Wide Name) held by the interface 112 of each host computer 11 and a port 123 of a storage unit 12 , for example.
  • WWN World Wide Name
  • FIG. 2 is a diagram showing an example configuration of a logical device management information 126 for management of the logical devices within the second storage unit 12 a.
  • Each record of the logical device management information 126 includes a logical device number 21 , a size 22 , a corresponding physical/external device number 23 , a device state 24 , a port ID/target ID/LUN (Logical Unit number) 25 , a connected host name 26 , a migrating physical/external device number 27 , a data migration progress pointer 28 , and a data migration processing flag 29 .
  • the size 22 stores capacity of the logical device, i.e., the logical device specified by the logical device number 21 .
  • the corresponding physical/external device number 23 stores a physical device number of the physical device corresponding to the logical device, in the second storage unit 12 a , or stores an external device number, i.e., a logical device of the first storage unit 12 b corresponding to the logical device. In the case where the corresponding physical/external device number 23 is not assigned with a device number, an invalid value is set in that entry. This device number becomes an entry number in the RAID management information 127 or the external device management information 128 .
  • the device state 24 is set with information indicating a state of the logical device.
  • the device state can be “online”, “offline”, “non-installed”, “fault offline” or “data migration in progress”.
  • the state “online” means that the logical device is operating normally, and can be accessed from an upper host.
  • the state “offline” means that the logical device is defined and is operating normally, but, can not be accessed from an upper host. This state corresponds to a case where the device was used before by an upper host, but now is not used by the upper host since the device is not required.
  • the phrase “the logical device is defined” means that correspondence with a physical device or an external device is set, or, in detail, the physical/external device number 23 is set.
  • the state “non-installed” means that the logical device is not defined and can not be accessed from an upper host.
  • the state “fault offline” means that a fault occurs in the logical device and an upper host can not access that logical device.
  • the state “data migration in progress” means that data migration from or to an external device is in course of processing.
  • an initial value of the device state 24 is “offline” with respect to the available logical devices, and “non-installed” with respect to the other.
  • the port number of the entry 25 is set with information indicating which port the logical device is connected with, among the plurality of ports 123 .
  • As the port number a number uniquely assigned to each port 123 within the storage unit 12 is used.
  • the target ID and LUN are identifiers for identifying the logical device.
  • the target ID and LUN are used as a SCSI-ID and LUN, respectively.
  • the connected host name 26 is information used only by the storage units 12 a and 12 b connected to the fibre channel switch 18 , and shows a host name for identifying a host computer 11 that is permitted to access the logical device.
  • the control memory of the storage 12 a or 12 b holds management information on an attribute of a WWN and the like of each port 123 .
  • the migrating physical/external device number 27 holds a physical/external device number of a migration destination of the physical/external device to which the logical device is assigned.
  • the data migration progress pointer 28 is information indicating the first address of a migration source area for which migration processing is unfinished, and is updated as the data migration progresses.
  • the data migration processing flag 29 has an initial value “Off”. When the flag 29 is set to “On”, it indicates that the physical/external device to which the logical device is assigned is under data migration processing. Only in the case where the data migration processing flag is “On”, the migrating physical/external device number 27 and the data migration progress pointer 28 become effective.
  • FIG. 3 is a diagram showing an example configuration of the RAID management information 127 for management of the physical devices within the storage unit 12 a.
  • Each record of the RAID management information 127 includes a physical device number 31 , a size 32 , a corresponding logical device number 33 , a device state 34 , a RAID configuration 35 , a stripe size 36 , a disk number list 37 , start offset in disk 38 , and size in disk 39 .
  • the size 32 stores capacity of the physical device, i.e., the physical device specified by the physical device number 31 .
  • the corresponding logical device number 33 stores a logical device number of the logical device corresponding to the physical device, within the second storage unit 12 a . In the case where the physical device is not assigned with a logical device, this entry is set with an invalid value.
  • the device state 34 is set with information indicating a state of the physical device.
  • the device state can be “online”, “offline”, “non-installed” or “fault offline”.
  • the state “online” means that the physical device is operating normally, and is assigned to a logical device.
  • the state “offline” means that the physical device is defined and is operating normally, but is not assigned to a logical device.
  • the phrase “the physical device is defined” means that correspondence with the disk unit 121 is set, or, in detail, the below-mentioned disk number list 37 and the start offset in disk 38 are set.
  • the state “non-installed” means that the physical device is not defined on the disk unit 121 .
  • the state “fault offline” means that a fault occurs in the physical device, and the physical device can not be assigned to a logical device.
  • an initial value of the device state 34 is “offline” with respect to the available physical devices, and “non-installed” with respect to the other.
  • the RAID configuration 35 holds information on a RAID configuration, such as a RAID level and the numbers of data disks and parity disks, of the disk unit 121 to which the physical device is assigned.
  • the stripe size 36 holds data partition unit (stripe) length in the RAID.
  • the disk number list 37 holds a number or numbers of one or plurality of disk units 121 constituting the RAID to which the physical device is assigned. These numbers are unique values given to disk units 121 for identifying those disk units 121 within the storage unit 12 .
  • the start offset in disk 38 and the size in disk 39 are information indicating an area to which data of the physical device are assigned in each disk unit 121 . In the present embodiment, for the sake of simplicity, the respective offsets and sizes in the disk units 121 constituting the RAID are unified.
  • Each entry of the above-described RAID management information 127 is set with a value, at the time of shipping the second storage unit 12 a.
  • FIG. 4 is a diagram showing an example configuration of the external device management information 128 of the second storage unit 12 a that manages the logical devices of the first storage unit 12 b as an external device.
  • Each record of the external device management information includes an external device number 41 , a size 42 , a corresponding logical device number 43 , a device state 44 , a storage identification information 45 , a device number in storage 46 , an initiator port number list 47 , and a target port ID/target ID/LUN list 48 .
  • the external device number 41 holds a value assigned to a logical device of the first storage unit 12 b , and this value is unique in the second storage unit 12 a .
  • the size 42 stores capacity of the external device, i.e., the external device specified by the external device number 41 .
  • the corresponding logical device number 43 stores a logical device number of that logical device.
  • this entry is set with an invalid value.
  • the device state 44 is set with information indicating a state of the external device.
  • the device state 44 is “online”, “offline”, “non-installed” or “fault offline”. The meaning of each state is same as the device state 34 in the RAID management information. In the initial state of the second storage unit 12 a , another storage unit is not connected, and the initial value of the device state 44 is “non-installed”.
  • the storage identification information 45 holds identification information of the first storage unit 12 b that carries. the external device.
  • the storage identification information may be considered, for example, a combination of vendor identification information on a vendor of the storage unit 12 b and a manufacturer's serial number assigned uniquely by the vendor.
  • the device number in storage 46 holds a logical device number (in the first storage unit 12 b ) corresponding to the external device.
  • the initiator port number list 47 holds a list of port numbers of ports 123 b (of the second storage unit 12 a ) that can access the external device.
  • the target port ID/target ID/LUN list 48 holds port IDs of those ports and one or plurality of target IDs/LUNs assigned to the external device.
  • the storage administrator connects the second storage unit 12 a to the fibre channel switch 18 (Step 501 ).
  • the port 123 a is connected to a port 181 of the fibre channel switch 18 , for access from the host computer 11 .
  • the port 123 b is connected to a port 181 of the fibre channel switch 18 , for access to other storage units including the first storage unit 12 b .
  • the fibre channel switch 18 detects the established links with the ports 123 a and 123 b of the second storage units 12 a .
  • a login to the interface or the port of the host computer 11 or the second storage unit 12 a is executed according to the fibre channel standard.
  • the second storage unit 12 a holds information such as the WWN or ID of the host computer 11 or the like to which the port 123 a or 123 b has logged in.
  • the installation controller 134 of the storage manager 131 acquires network topology information from the switch 18 again, to detect new registration of the second storage unit 12 a.
  • Processing on and after the step 502 is performed mainly by the installation controller 134 of the storage manager 131 that receives an instruction from the storage administrator to start installation of the second storage unit 12 a , and by the installation controller 129 of the second storage unit 12 a .
  • the installation controller 134 of the storage manager 131 changes zoning setting of the switch 18 , and changes device access right setting of the first storage unit 12 b such that the second storage unit 12 a can access the devices of the first storage unit 12 b.
  • the storage manager 131 assigns the logical devices of the first storage unit 12 b to the logical device of the second storage unit 12 a .
  • the storage manager 131 sends the second storage unit 12 a the port ID list of the first storage unit 12 b as the object of migration to the second storage unit 12 a .
  • the installation controller 129 of the second storage unit 12 a sends a SCSI “Inquiry” command that designates a specific LUN for a port 123 (of the first storage unit 12 b ) existing in the received list, with respect to all such LUNs.
  • the processor of the first storage unit 12 b responds normally to “Inquiry” commands relating to LUNs that are actually set to the port IDs of the first storage unit 12 b .
  • the installation controller 129 of the second storage unit 12 a specifies the logical devices (of the first storage unit 12 b ) that can be accessed and migrated to the second storage unit 12 a .
  • the installation controller 129 generates an external device list (from the viewpoint of the second storage unit 12 a ) of those logical devices.
  • the installation controller 129 utilizes information such as names, types and capacities of devices connected to the second storage unit 12 a .
  • the information such as the names, types and capacities of the devices is acquired from returned information of the response to the above-mentioned “Inquiry” command and returned information of a response to “Read Capacity” command that is sent after the “Inquiry” command.
  • the installation controller 129 registers those logical devices as external devices of the second storage unit 12 a into the external device management information 128 .
  • the installation controller 129 finds an external device whose device state 44 is “non-installed”, and sets information 42 ⁇ 48 into the entries concerned of that external device. Now, the device state 44 is changed to “offline”.
  • the installation controller 129 of the second storage unit 12 a notifies the storage manager 131 of the above-mentioned external device list with respect to the designated port. And, the installation controller 134 of the storage manager 131 instructs the second storage unit 12 a to assign the logical devices of the first storage unit 12 b . Receiving this instruction, the installation controller 129 of the second storage unit 12 a assigns an external device a, i.e., a logical device of the first storage unit 12 b , to a non-installed logical device a of the second storage unit 12 a .
  • the installation controller 129 of the second storage unit 12 a sets the device number 41 of the external device a to which the logical device of the first storage unit 12 b corresponds, into the corresponding physical/external device number 23 of the logical device management information 126 relating to the logical device a. Then, the installation controller 129 of the second storage unit 12 a changes the device state 24 of the logical device management information 126 from “non-installed” to “offline”. In addition, the corresponding logical device number 43 of the external device management information 128 is set to the device number 21 of the logical device a, and the device state 44 is changed to “online”.
  • the installation controller 134 of the storage manager 131 instructs the second storage unit 12 a to define a LUN to the port 123 a such that the host computer 11 can access the logical device a assigned to the second storage unit 12 a .
  • the installation controller 129 of the second storage unit 12 a defines a LUN relating to the above-assigned logical device a, i.e., defines a device path to the port 123 a of the second storage unit 12 a .
  • the port number/target ID/LUN 25 and the host name 26 of the logical device management information 126 are set.
  • the installation controller 134 of the storage manager 131 instructs the DLM 111 of the host computer 11 to recognize the devices again.
  • the DLM 111 of the host computer generates a device file relating to the newly-assigned logical device.
  • a device file relating to the newly-assigned logical device.
  • an “IOSCAN” command is used to recognize a new logical device and to generate a device file.
  • the DLM 111 detect it and manages these device file as a same group. To judge the sameness, it is considered to use the above-mentioned “Inquiry” command or the like to acquire the device number in the storage 12 , for example. However, in the case where a logical device b in the first storage unit 12 b corresponds to a logical device a in the second storage unit 12 a , the DLM 111 sees these logical devices a and b as logical devices of the different storage units 12 a and 12 b , they are not managed in a same group.
  • the installation controller 134 of the storage manager 131 instructs the DLM 111 of the host computer 11 to change the access destination. Receiving this instruction, the DLM 111 changes access to the device in the first storage 12 b to access to the device in the second storage unit 12 a (Step 506 ).
  • the installation controller 134 of the storage manager 131 sends device correspondence information of the first storage unit 12 b and the second storage unit 12 a to the DLM 111 .
  • the device correspondence information is information of the assignment of the logical devices of the second storage unit 12 b .
  • the DLM 111 of the host computer 11 assigns a virtual device file that is assigned to a device file group relating to a logical device b in the first storage unit 12 b to a device file group relating to a logical device a in the second storage unit 12 a .
  • software operating on the host computer 11 can access the logical device a in the second storage unit 12 a according to a same procedure of accessing the logical device b in the first storage unit 12 b.
  • the installation controller 134 of the storage manager 131 makes the switch 18 change the zoning setting and makes the first storage unit 12 b change setting of the device access right, to inhibit the host computer 11 from directly accessing the devices of the first storage unit 12 b.
  • the installation controller 134 of the storage manager 131 instructs the second storage unit 12 a to migrate data.
  • the installation controller 129 of the second storage unit 12 a checks the device state 34 of the RAID management information 127 , to search for a physical device a in the “offline” state, i.e., in an empty state. When a physical device in the “offline” state is found, then, the size 32 is referred to in order to obtain the capacity of the empty device.
  • the installation controller 129 searches for such an external device (hereinafter, referred to as the migration object device) that the device state 44 of the external device management information 128 is “online” and the size 42 of the external device management information 128 can be accommodated by the capacity of the physical device a.
  • the migration object device an external device that the device state 44 of the external device management information 128 is “online” and the size 42 of the external device management information 128 can be accommodated by the capacity of the physical device a.
  • the installation controller 129 assigns an empty physical device to the logical device a of the second storage unit 12 a (Step 603 ).
  • the installation controller 129 registers the number of the logical device a into the corresponding logical device number 33 of the RAID management information 127 corresponding to the physical device a, and changes the device state 34 from “offline” to “online”.
  • the device state 24 is set to “data migration in progress”
  • the data migration processing flag 29 is set to “On”
  • the migrating physical/external device number 27 is set to the device number of the physical device a.
  • the installation controller 129 of the second storage unit 12 a performs processing of data migration from the migration object device to the physical device a.
  • data are read to the cache memory 124 , and then, the data are written onto the physical device a. This operation is repeated to the end of the migration object device. In the course of this operation, each time when writing onto the physical device a is finished, the first address of the next migration object area is set into the data migration progress pointer 28 .
  • the installation controller 129 sets the corresponding physical/external device number 23 of the logical device management information 126 with the physical device number of the physical device a, and the device state 24 is changed from “data migration in progress” to “online”, the data migration flag 29 is set to “Off”, and the migrating physical/external device number 27 is set to the invalid value. Further, the corresponding logical device number 43 of the external device management information 128 corresponding to the migration object device is set to the invalid value, and the device state 44 is set to “offline”.
  • the installation controller 129 of the second storage unit 12 a receives an input-output request from the host computer 11 (Step 701 )
  • the installation controller 129 judges whether the request is read or write (Step 702 ). In the case where the request is read, it is checked whether processing object data are held in the cache memory 124 (hit) (Step 703 ). When the processing object data are not held in the cache memory 124 , data staging to the cache memory 124 is performed. At that time, it is judged whether the data migration is in progress, based on the device state 24 of the logical device in the logical device management information 126 .
  • Step 704 it is judged whether a processing object address of the logical device as the processing object is in a migrated data area, based on the data migration progress pointer 28 relating to the logical device in the logical device management information 126 (Step 704 ).
  • read processing is performed for reading from the migration destination device indicated by the migrating physical/external device number 27 (Step 706 ).
  • read processing is performed for reading from the migration object device indicated by the corresponding physical/external device number 23 (Step 705 ).
  • the installation controller 129 converts the read request from the host computer 11 into a read request to the migration object device indicated by the corresponding physical/external device number 23 , and sends the converted request to the first storage unit 12 b .
  • the first storage unit 12 b performs read processing toward the disk unit 121 corresponding to the above-mentioned migration object device, and sends read contents to the second storage unit 12 a .
  • the read processing is performed toward the migration object device indicated by the migrating physical/external device number 27 .
  • Step 705 or 706 When, after execution of the read processing (Step 705 or 706 ), the data staging to the cache memory 124 is finished, then, the object data held in the cache memory 124 is transferred to the host computer 11 (Step 707 ). And, the disk controller 122 of the second storage unit 12 a sends a completion report to the host computer 11 (Step 708 ).
  • the object data held in the cache memory 124 are immediately transferred to the host computer 11 (Step 707 ).
  • the disk controller 122 of the second storage unit 12 a sends a processing completion report to the host computer 11 (Step 708 ).
  • the disk controller 122 of the second storage unit 12 a assigns a write data storage area to the cache memory 124 , transfers write data from the host computer 11 to the cache memory 124 , and sends a completion report to the host computer 11 (Steps 709 - 711 ). Thereafter, destaging of the write data is performed.
  • Step 712 it is judged whether the logical device is under data migration, based on the device state 24 of the logical device management information 126 (Step 712 ).
  • write processing of the above-mentioned data is performed toward both the migration source (migration object) device and the migration destination device (Step 713 ).
  • write processing of the above-mentioned data is performed toward the device indicated by the corresponding physical/external device number 23 (Step 714 ).
  • Step 801 when the storage administrator adds a disk unit 121 to the second storage unit 12 a , and the installation controller 129 of the second storage unit 12 a detects this addition (Step 801 ), then, the installation controller 129 defines a new empty device, i.e., a physical device of an “offline” state (Step 802 ). At that time, the entries 32 - 39 of the RAID management information 127 are updated.
  • Steps 803 - 806 data migration of an external device whose data are not migrated yet is performed toward the newly-assigned empty device.
  • Steps 803 - 806 are similar to the steps 602 - 605 of FIG. 6 , and not described here again.
  • the port ID list of the first storage unit 12 b as the migration object is sent from the storage manager 131 to the second storage unit 12 a , in the step 503 .
  • information that can specify the first storage unit 12 b for example, identification information list for identifying the unit name obtainable by an “Inquiry” command
  • Identification information of the mentioned list is information required by the storage manager 131 to manage the first storage unit 12 b , and although basically held inside the storage manager 131 , may be obtained by sending an “Inquiry” command to the first storage unit 12 b at the time of sending the list.
  • the second storage unit 12 a sends an “Inquiry” command to all the storage node ports that can be reached from the port 123 b , and compares the above-mentioned identification information list with unit identification information among information obtained from the first storage unit 12 b , so that only coincident ports become migration objects. Further, it is possible that the second storage unit 12 a does not receive an instruction from the storage manager 131 and all the storage node ports reachable from the port 123 b become migration objects.
  • the storage manager 131 is notified of the list of the external devices detected by the second storage unit 12 a , and only the external devices designated by the storage manager become the migration objects.
  • the second storage unit 12 a does not notify the storage manager 131 of the detected external device list, and all the devices shown in the external device list become migration objects.
  • the second storage unit 12 a selects and assigns the non-installed logical device to the external device designated by the storage manager 131 .
  • the storage manager 131 may determine a non-installed logical device as an object of assignment and indicate the determined logical device to the second storage unit 12 a . In that case, the storage manager 131 must obtain information such as the logical device number 21 and the device state 24 out of the logical device management information 126 shown in FIG. 2 , to determine migration objects based on the obtained information.
  • the second storage unit 12 a performs data migration from the external device to all the empty physical devices as the migration destination.
  • migration destination physical devices based on control information that can be used to judge whether a physical device can be a migration object.
  • a data migration target availability flag is provided to each record of the RAID management information shown in FIG. 3 .
  • This flag is set with a flag value indicating whether each physical device can become a data migration destination at the time of initialization or addition of a physical device. Based on this information, the second storage unit 12 a specifies a physical device that can be a migration destination.
  • the mentioned flag value is set by the storage administrator using a configuration management terminal (not shown in FIG. 1 ) of the second storage unit 12 a , or using an input-output unit such as a keyboard and/or a mouse provided to the storage manager 131 .
  • a flag value is automatically set to “unavailable as migration target” as a basic set value given at the time of installation of a physical device, and the storage administrator changes the flag value relating to a specific physical device to “available as migration target”.
  • the storage administrator changes the flag value relating to a specific physical device to “unavailable as migration target”.
  • the storage manager 131 holds physical device information such as the physical device number 31 , the size 32 and the device state 34 out of the RAID management information 127 shown in FIG. 3 , and specifies an empty physical device as the data migration destination, to the second storage unit 12 a .
  • the data migration processing shown in FIG. 6
  • the external device is determined by checking only whether it can be accommodated by the size of the empty physical device selected in the step 601 .
  • the migration object may be determined based on other information of the external device. For example, it is possible that a data migration object possibility flag is provided to each record of the external device management information 128 shown in FIG. 4 , and it is judged whether the external device can be an object of migration.
  • the storage administrator changes the flag value.
  • a configuration management terminal (not shown in FIG. 1 ) of the second storage unit 12 a , or an input-output unit such as a keyboard and/or a mouse provided to the storage manager 131 may be used.
  • data migration object priority information may be provided. In that case, the second storage unit 12 a determines the migration object external device, referring to the migration object priority information set by the storage administrator.
  • the second storage unit 12 a acquires access statistical information for each logical device.
  • FIG. 9 shows an example of the statistical information.
  • an access frequency 91 indicates the number of accesses per time unit to the logical device
  • a read frequency 92 indicates the number of reads per time unit from the logical device.
  • a write frequency can be calculated from the access frequency 91 and the read frequency 92 .
  • a read cache hit rate 93 and a write cache hit rate 94 are hit rates in the cache memory 124 of the second storage unit 12 a at the time of read access and at the time of write access, respectively.
  • the storage manager instructs the second storage unit 12 a to perform data migration.
  • the second storage unit 12 a may automatically perform the data migration processing, as an extension of the processing of associating an external device, i.e., a logical device of the first storage unit 12 b , with a logical device of the second storage unit 12 a .
  • the functions relating to the data migration processing shown in FIG. 6 may be mounted on the second storage unit 12 a.

Abstract

A new storage unit is installed such that installation costs are suppressed and functions of the new storage unit can be utilized sufficiently. An access right is changed such that the new storage unit (second storage unit) can access an existing first storage unit (S502). A logical device relating to a storage device of the first storage unit is assigned to a logical device of the second storage unit (S503). Path definition and device recognition in a host computer are performed such that the host computer can access the assigned logical device of the second storage unit (S504, 505). Input-output setting of the host computer is changed such that processing of an input-output from the host computer to the device of the first storage unit is requested to the second storage unit (S506).

Description

  • The present application is a continuation application of application Ser. No. 11/178,373, filed Jul. 12, 2005, which is a continuation of application Ser. No. 10/636,758, filed Aug. 8, 2003, the contents of which are incorporated herein by reference.
  • BACKGROUND OF THE INVENTION
  • 1. Field of the Invention
  • The present invention relates to a storage unit that is installed newly into a computer system comprising a first storage unit and a host computer accessing the first storage unit, and an installation method thereof and an installation program therefor.
  • 2. Related Art Statement
  • Recently, an amount of data treated by a computer is increasing by leaps, and accordingly storage capacity of a storage unit for storing data is increasing. As a result, costs of storage management in system management increase, and reduction of management costs becomes an important problem from the viewpoint of system operation.
  • When a new storage unit is installed into an existing computer system that comprises a host computer and a storage unit, two modes can be considered as a mode of installation, namely, a mode in which the old storage unit is used as ever, and the new storage unit is used together with the old storage unit, and a mode in which all the data on the old storage unit are migrated onto the new storage unit.
  • For example, as to the latter mode of installation, Japanese Patent Publication No. 10-508967 discloses a technique of migrating data of an old storage unit onto a new storage unit. According to the technique disclosed in the above document, data of a first device in the old storage unit are migrated onto a second device assigned to the new storage unit. Then, a host computer's access destination is changed from the existing first device to the new second device. An input-output request from the host computer to the existing first device is received by the new storage unit. With respect to a read request, a part whose migration is finished is read from the new second device, while a part that has not been migrated yet is read from the existing first device. Further, with respect to a write request, dual writing is performed toward both the first and second devices.
  • As described above, when a new storage unit is installed, it is possible to migrate data of a first device within an old storage unit to a second device within a new storage unit, without stopping input/output from/to a host computer.
  • However, in the case of the former mode of installation, where the new storage unit and the old storage unit are used side by side, there is a problem that, although generally the new storage unit has high function, high performance and high reliability in comparison with the old storage unit, it is impossible for data stored in the old storage unit to enjoy the merits of the new storage unit.
  • Further, in the case of the latter mode of installation, where all the data of the old storage unit are migrated onto the new storage unit, it is possible to enjoy the merits of the new storage unit by migrating the data stored in the old storage unit. However, there is a problem that, to migrate all the data of the old storage unit onto the new storage unit, the new storage unit must have more storage capacity than the old storage unit, and thus, the system installation cost is raised up.
  • Thus, as a compromise between them, it is possible to consider the following operation. Namely, the number of disk units mounted on a new storage unit is restrained to decrease initial investment, and the minimum data are migrated from an old storage unit to start system operation. At a stage in which a disk unit is added to the new storage unit, data is migrated from the old storage unit by an amount that the added disk unit allows. However, even by this compromise, data that can not be migrated because of storage capacity can not enjoy the merits of the new storage unit, similarly to the case where two storage units are used side by side.
  • SUMMARY OF THE INVENTION
  • An object of the present invention is to provide such a storage unit, an installation method thereof and an installation program therefor that can enjoy merits such as high function, high performance and high reliability of a new storage unit at the time of installation of the new storage unit, suppressing cost increase.
  • To attain the above object, the present invention follows the below-described procedures to install a new storage unit (referred to as a second storage unit) into a computer system comprising a host computer and an existing first storage unit, wherein the host computer and the first storage unit are connected through a first network such as SAN, LAN, or the like.
  • First, the new second storage unit is connected to the first network. Then, zoning setting of a switch existing in the first network and access right setting of the first storage unit are changed such that the second storage unit can access a storage device in the first storage unit. Next, a logical device (hereinafter, referred to as a first logical device) relating to the storage device of the first storage unit is assigned to a logical device (hereinafter, referred to as a second logical device) of the second storage unit. Namely, the first logical device of the first storage unit is associated with the second logical device of the second storage unit. Next, with respect to the second logical device, path definition and device recognition in the host computer are performed such that the host computer can recognize the second logical device of the second storage unit and can access the second logical device of the second storage unit.
  • Next, input-output setting of the host computer is changed such that processing of an input-output from the host computer to the storage device of the first storage unit is requested to the second storage unit. Here, the substance of the second logical device is the storage device in the first storage unit, and a storage device storing the data of the second logical device is not held in the second storage unit.
  • Favorably, the zoning setting of the switch existing in the first network and the access right setting of the first storage unit are changed such that direct access from the host computer to the storage device of the first storage unit is inhibited.
  • In the above-described state, when the second storage unit receives a read request from the host computer to the second logical device, then, the second storage unit converts the read request into a read request to the first logical device, and sends the converted request to the first storage unit. Receiving an input-output processing completion report from the first storage unit, the second storage unit sends the host computer a completion report relating to the input-output request to the second logical device.
  • Thus, in the above-described state, the second storage unit can process an input-output request to the storage device in the first storage unit. Accordingly, merits of the new storage unit, such as high performance, high reliability and high function, can be applied to the device in the existing first storage unit. For example, to the first logical device of the first storage unit, the second storage unit can apply a replicating function such as data replication and copy to a remote place, or access right control for each device.
  • Here, apparently the second logical device of the second storage unit is assigned to the first logical device of the first storage unit, and the host computer recognizes the first logical device of the first storage unit as the second logical device of the second storage unit. In this state, a physical device that becomes the substance of the second logical device is allocated from an unused storage space in the second storage unit, and a part or all of the data of the storage devices of the first storage unit are migrated. In the course of data migration, when a read request from the host computer to the second logical device relates to data that have not been migrated from the first logical device, then, this read request is sent to the first storage unit, as a read request to the first logical device. On the other hand, when this read request relates to data that have been migrated already, this read request is processed in the second storage unit, as a read request to the above-mentioned physical device as the subject of the second logical device. Further, with respect to a write request in the course of data migration, dual writing is performed toward the first logical device of the first storage unit and toward the physical device of the second storage unit. When the data migration from the first storage unit is finished, then setting is changed such that the physical device of the second storage unit is seen as the second logical device.
  • Thereafter, each time when a new storage device is added to the second storage unit, data of the first storage unit are migrated stepwise.
  • When the second storage unit is installed according to the above-described method, then, also with respect to data that are actually stored in the existing first storage unit, the host computer access the new second storage unit. Thus, merits of the new second storage unit, such as high performance, high functions, and high reliability of the second storage unit, can be enjoyed even when data actually stored in the existing first storage unit are accessed. In other words, the merits of the newly-installed storage unit can be applied to all the data including the data in the existing first storage unit. In addition, the existing storage unit and the new storage unit are used jointly, and storage capacity of the new storage unit can be smaller, and installation costs can be the smallest.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1 is a block diagram showing a computer system as an embodiment of the present invention;
  • FIG. 2 is a diagram showing an example configuration of a logical device management information table in an embodiment of the present invention;
  • FIG. 3 is a diagram showing an example configuration of a RAID management information table in an embodiment of the present invention;
  • FIG. 4 is a diagram showing an example configuration of an external device management information table in an embodiment of the present invention;
  • FIG. 5 is a flowchart showing a procedure of installing a new storage unit in an embodiment of the present invention;
  • FIG. 6 is a flowchart showing a migration procedure at the time of migrating data from an existing first storage unit to a new second storage unit in an embodiment of the present invention;
  • FIG. 7 is a flowchart showing a procedure of processing an input-output request from a host to a new second storage unit in an embodiment of the present invention;
  • FIG. 8 is a flowchart showing a processing procedure at the time of adding a disk unit to a new second storage unit in an embodiment of the present invention; and
  • FIG. 9 is a diagram showing an example configuration of a logical device access statistical information table in an embodiment of the present invention.
  • BEST MODE OF PRACTICING THE INVENTION
  • Now, one embodiment of a computer system according to the present invention will be described.
  • As shown in FIG. 1, a computer system of the present invention comprises a host computer 11, a fibre channel switch 18; two storage units 12 a and 12 b (referred to as a storage unit 12, by a general term) and a management server 13. The host computer 11 is connected with the two storage units 12 a and 12 b through the fibre channel switch 18 and cables. Further, the host computer 11, the two storage units 12 a and 12 b and the fibre channel switch 18 are connected to the management server 13 through an IP network 142.
  • The host computer 11 comprises a CPU, a memory, and the like, and performs predetermined functions when the CPU reads and executes an operating system (hereinafter, referred to as OS) and application programs stored in the memory.
  • Among the two storage units 12 a and 12 b, a first storage unit 12 b is an existing storage unit, and a second storage unit 12 a is a newly installed storage unit. The first storage unit 12 b comprises a disk unit 121, a disk controller 122, a port 123 for connecting with the host computer 11, and a network interface 125 for connecting with the IP network 142. Here, the first storage unit 12 b may comprise a plurality of disk units and a plurality of ports. Further, the second storage unit 12 a comprises a plurality of disk units 121, a disk controller 122, a port 123 a for connecting with the host computer 11 and a plurality of ports 123 b for connecting with the other storage units (referred to as a port 123, by a general term), and a network interface 125 for connecting with the IP network 142.
  • In a storage unit 12 of the present embodiment, a disk unit or units 121 as hardware are defined collectively as one or a plurality of physical devices, and one logical device (i.e., one device from a logical viewpoint) is assigned to one physical device. Of course, it is possible to present an individual disk unit 121 as one physical device and one logical device, to the host computer 11.
  • As a port 123 of a storage unit 12 in the present embodiment, it is assumed to use the fibre channel interface whose upper protocol is SCSI (Small Computer System Interface). However, another network interface for storage connection, such as IP network interface whose upper protocol is SCSI, may be used.
  • A disk controller 122 of a storage unit 12 comprises a processor, a cache memory 124 and a control memory, and communicate with the management server 13 through the network interface 125 and controls the disk unit 121. The processor controls access from the host computer 11 and controls the disk unit 121, based on various kinds of information stored in the control memory. In particular, in the case where a plurality of disk units 121 (not a single disk unit 121) such as ones in a disk array are presented as one or plurality of logical devices to the host computer 11, the processor performs processing and management relating to the disk units 121.
  • The control memory stores programs executed by the processor and various kinds of management information. As one of the programs executed by the processor, there may be a disk controller program. This disk controller program includes an installation program for installing the second storage unit 12 a into a computer system. This installation program and the disk controller program including it are executed by the processor to function as a storage installation controller 129 and the disk controller, respectively. Further, as the various kinds of management information stored or to be stored in the control memory, there may be logical device management information 126 for management of the logical devices of the second storage unit 12 a; RAID (Redundant Array of Independent Disk) management information 127 for management of physical devices consisting of the plurality of disk units 121 of the second storage unit 12 a, and external device management information 128 for management of correspondence between the logical devices of the second storage unit 12 a and the logical devices of the first storage unit 12 b.
  • To enhance speed of processing an access from the host computer 11, the cache memory 124 stores data that are frequently read, or temporally stores write data from the host computer 11.
  • The host computer 11 is connected with the fibre channel switch 18 through an interface (I/F) 112, and also with the management server through a network interface 113. On the host computer 11, software (program) called a device link manager (hereinafter, referred to as DLM) 111 operates. The DLM 111 manages correspondence between the logical devices (recognized through the interface 112) of the storage unit 12 and device files as device management units of the OS. Usually, when a logical device is connected with a plurality of interfaces 112 and a plurality of ports 123, the host computer 11 recognizes that logical device as a plurality of devices having different addresses, and different device files are defined, respectively. A plurality of device files corresponding to one logical device are managed as a group by the DLM 11, and a virtual device file as a representative of the group is provided to upper levels, so that alternate paths and load distribution can be realized. Further, in the present embodiment, the DLM 111 also adds/deletes a new device file to/from a specific device file group and changes a main path within a device file group, according to an instruction from a storage manager 131 located in the management server 13.
  • The management server 13 performs operation, maintenance and management of the whole computer system. The management server 13 comprises a network interface 133, and connects with the host computer 11, the two storage units 12 a and 12 b, and the fibre channel switch 18, through the IP network 142. The management server 13 collects configuration information, resource utilization factors, performance monitoring information from various units 11, 12 and 18, presents them to a storage administrator, and sends operation/maintenance instructions to those units. The mentioned processing is performed by the storage manager 131 operating on the management server 13.
  • Similarly to the disk controller 122, also the storage manager 131 comprises a processor and a memory. The memory stores a storage manager program executed by the processor. This storage manager program includes an installation program for installing a new storage unit. This installation program and the storage manager program including it are executed by the processor to function as an installation controller 134 and the storage manager 131, respectively. When a new storage unit is installed, this installation program is installed onto the existing management server 13, except the case where a new management server incorporated with the installation program is employed.
  • The fibre channel switch 18 comprises a plurality of ports 181. Each port 181 is connected with the interface 112 of the host computer 11 or a port 123 of the storage unit 12 a or 12 b, so that each of those devices can communicate with another device. The fibre channel switch 18 comprises a network interface 182, and is connected with the IP network 142 also. Due to this arrangement, from the physical viewpoint, any host computer 11 can access all the storage units 12 a and 12 b connected to the fibre channel switch 18. Further, the fibre channel switch 18 has a function called zoning, i.e., a function of limiting communication from a specific port to another specific port. This function is used, for example, when access to a specific port 123 of a specific storage 12 is limited to a specific host 11. As a method of controlling combinations of a sending port and a receiving port, may be mentioned a method in which an identifier assigned to a port 181 of the fibre channel switch is used, and a method in which WWN (World Wide Name) held by the interface 112 of each host computer 11 and a port 123 of a storage unit 12, for example.
  • Next, there will be described the logical device management information 126, the RAID management information 127 and the external device management information 128 stored or to be stored in the control memory of the disk controller 122 of the second storage unit 12 a.
  • FIG. 2 is a diagram showing an example configuration of a logical device management information 126 for management of the logical devices within the second storage unit 12 a.
  • Each record of the logical device management information 126 includes a logical device number 21, a size 22, a corresponding physical/external device number 23, a device state 24, a port ID/target ID/LUN (Logical Unit number) 25, a connected host name 26, a migrating physical/external device number 27, a data migration progress pointer 28, and a data migration processing flag 29.
  • The size 22 stores capacity of the logical device, i.e., the logical device specified by the logical device number 21. The corresponding physical/external device number 23 stores a physical device number of the physical device corresponding to the logical device, in the second storage unit 12 a, or stores an external device number, i.e., a logical device of the first storage unit 12 b corresponding to the logical device. In the case where the corresponding physical/external device number 23 is not assigned with a device number, an invalid value is set in that entry. This device number becomes an entry number in the RAID management information 127 or the external device management information 128. The device state 24 is set with information indicating a state of the logical device. The device state can be “online”, “offline”, “non-installed”, “fault offline” or “data migration in progress”. The state “online” means that the logical device is operating normally, and can be accessed from an upper host. The state “offline” means that the logical device is defined and is operating normally, but, can not be accessed from an upper host. This state corresponds to a case where the device was used before by an upper host, but now is not used by the upper host since the device is not required. Here, the phrase “the logical device is defined” means that correspondence with a physical device or an external device is set, or, in detail, the physical/external device number 23 is set. The state “non-installed” means that the logical device is not defined and can not be accessed from an upper host. The state “fault offline” means that a fault occurs in the logical device and an upper host can not access that logical device. Further, the state “data migration in progress” means that data migration from or to an external device is in course of processing.
  • For the sake of simplicity, it is assumed in the present embodiment that, at the time of shipping of the product, available logical devices were assigned in advance to physical devices prepared on a disk unit 121. Accordingly, an initial value of the device state 24 is “offline” with respect to the available logical devices, and “non-installed” with respect to the other.
  • The port number of the entry 25 is set with information indicating which port the logical device is connected with, among the plurality of ports 123. As the port number, a number uniquely assigned to each port 123 within the storage unit 12 is used. Further, the target ID and LUN are identifiers for identifying the logical device. Here, when the host computer 11 accesses the device on SCSI, the target ID and LUN are used as a SCSI-ID and LUN, respectively. The connected host name 26 is information used only by the storage units 12 a and 12 b connected to the fibre channel switch 18, and shows a host name for identifying a host computer 11 that is permitted to access the logical device. As the host name, it is sufficient to use a name that can uniquely identify a host computer 11 or its interface 112, such as a WWN (World Wide Name) given to the interface 112 of a host computer 11. In addition, the control memory of the storage 12 a or 12 b holds management information on an attribute of a WWN and the like of each port 123.
  • When the device state 24 is “data migration in progress”, the migrating physical/external device number 27 holds a physical/external device number of a migration destination of the physical/external device to which the logical device is assigned. The data migration progress pointer 28 is information indicating the first address of a migration source area for which migration processing is unfinished, and is updated as the data migration progresses. The data migration processing flag 29 has an initial value “Off”. When the flag 29 is set to “On”, it indicates that the physical/external device to which the logical device is assigned is under data migration processing. Only in the case where the data migration processing flag is “On”, the migrating physical/external device number 27 and the data migration progress pointer 28 become effective.
  • FIG. 3 is a diagram showing an example configuration of the RAID management information 127 for management of the physical devices within the storage unit 12 a.
  • Each record of the RAID management information 127 includes a physical device number 31, a size 32, a corresponding logical device number 33, a device state 34, a RAID configuration 35, a stripe size 36, a disk number list 37, start offset in disk 38, and size in disk 39.
  • The size 32 stores capacity of the physical device, i.e., the physical device specified by the physical device number 31. The corresponding logical device number 33 stores a logical device number of the logical device corresponding to the physical device, within the second storage unit 12 a. In the case where the physical device is not assigned with a logical device, this entry is set with an invalid value. The device state 34 is set with information indicating a state of the physical device. The device state can be “online”, “offline”, “non-installed” or “fault offline”. The state “online” means that the physical device is operating normally, and is assigned to a logical device. The state “offline” means that the physical device is defined and is operating normally, but is not assigned to a logical device. Here, the phrase “the physical device is defined” means that correspondence with the disk unit 121 is set, or, in detail, the below-mentioned disk number list 37 and the start offset in disk 38 are set. The state “non-installed” means that the physical device is not defined on the disk unit 121. The state “fault offline” means that a fault occurs in the physical device, and the physical device can not be assigned to a logical device.
  • For the sake of simplicity, it is assume in the present embodiment that physical devices were prepared in advance on the disk unit 121 at the time of shipping of the product. Accordingly, an initial value of the device state 34 is “offline” with respect to the available physical devices, and “non-installed” with respect to the other.
  • The RAID configuration 35 holds information on a RAID configuration, such as a RAID level and the numbers of data disks and parity disks, of the disk unit 121 to which the physical device is assigned. Similarly, the stripe size 36 holds data partition unit (stripe) length in the RAID. The disk number list 37 holds a number or numbers of one or plurality of disk units 121 constituting the RAID to which the physical device is assigned. These numbers are unique values given to disk units 121 for identifying those disk units 121 within the storage unit 12. The start offset in disk 38 and the size in disk 39 are information indicating an area to which data of the physical device are assigned in each disk unit 121. In the present embodiment, for the sake of simplicity, the respective offsets and sizes in the disk units 121 constituting the RAID are unified.
  • Each entry of the above-described RAID management information 127 is set with a value, at the time of shipping the second storage unit 12 a.
  • FIG. 4 is a diagram showing an example configuration of the external device management information 128 of the second storage unit 12 a that manages the logical devices of the first storage unit 12 b as an external device.
  • Each record of the external device management information includes an external device number 41, a size 42, a corresponding logical device number 43, a device state 44, a storage identification information 45, a device number in storage 46, an initiator port number list 47, and a target port ID/target ID/LUN list 48.
  • The external device number 41 holds a value assigned to a logical device of the first storage unit 12 b, and this value is unique in the second storage unit 12 a. The size 42 stores capacity of the external device, i.e., the external device specified by the external device number 41. When the external device corresponds to a logical device in the second storage unit 12 a, the corresponding logical device number 43 stores a logical device number of that logical device. When the external device is not assigned to a logical device, this entry is set with an invalid value. The device state 44 is set with information indicating a state of the external device. The device state 44 is “online”, “offline”, “non-installed” or “fault offline”. The meaning of each state is same as the device state 34 in the RAID management information. In the initial state of the second storage unit 12 a, another storage unit is not connected, and the initial value of the device state 44 is “non-installed”.
  • The storage identification information 45 holds identification information of the first storage unit 12 b that carries. the external device. As the storage identification information, may be considered, for example, a combination of vendor identification information on a vendor of the storage unit 12 b and a manufacturer's serial number assigned uniquely by the vendor. The device number in storage 46 holds a logical device number (in the first storage unit 12 b) corresponding to the external device. The initiator port number list 47 holds a list of port numbers of ports 123 b (of the second storage unit 12 a) that can access the external device. When, with respect to the external device, LUN is defined for one or more ports 123 of the first storage unit 12 b, the target port ID/target ID/LUN list 48 holds port IDs of those ports and one or plurality of target IDs/LUNs assigned to the external device.
  • Next, operation of the storage administrator and the computer system following installation of the second storage unit 12 a in the present embodiment will be described according to the flowchart shown in FIG. 5.
  • First, the storage administrator connects the second storage unit 12 a to the fibre channel switch 18 (Step 501). In the present embodiment, the port 123 a is connected to a port 181 of the fibre channel switch 18, for access from the host computer 11. And, the port 123 b is connected to a port 181 of the fibre channel switch 18, for access to other storage units including the first storage unit 12 b. When the second storage unit 12 a is activated, the fibre channel switch 18 detects the established links with the ports 123 a and 123 b of the second storage units 12 a. Thereafter, on occurrence of a login from each port 123 a or 123 b to the switch 18, a login to the interface or the port of the host computer 11 or the second storage unit 12 a is executed according to the fibre channel standard. At that time, the second storage unit 12 a holds information such as the WWN or ID of the host computer 11 or the like to which the port 123 a or 123 b has logged in. Receiving a state change notification from the switch 18, the installation controller 134 of the storage manager 131 acquires network topology information from the switch 18 again, to detect new registration of the second storage unit 12 a.
  • Processing on and after the step 502 is performed mainly by the installation controller 134 of the storage manager 131 that receives an instruction from the storage administrator to start installation of the second storage unit 12 a, and by the installation controller 129 of the second storage unit 12 a. In the step 502, the installation controller 134 of the storage manager 131 changes zoning setting of the switch 18, and changes device access right setting of the first storage unit 12 b such that the second storage unit 12 a can access the devices of the first storage unit 12 b.
  • In the step 503, the storage manager 131 assigns the logical devices of the first storage unit 12 b to the logical device of the second storage unit 12 a. In detail, first, the storage manager 131 sends the second storage unit 12 a the port ID list of the first storage unit 12 b as the object of migration to the second storage unit 12 a. From the port 123 b, the installation controller 129 of the second storage unit 12 a sends a SCSI “Inquiry” command that designates a specific LUN for a port 123 (of the first storage unit 12 b) existing in the received list, with respect to all such LUNs. On the other hand, the processor of the first storage unit 12 b responds normally to “Inquiry” commands relating to LUNs that are actually set to the port IDs of the first storage unit 12 b. Based on this response, the installation controller 129 of the second storage unit 12 a specifies the logical devices (of the first storage unit 12 b) that can be accessed and migrated to the second storage unit 12 a. And, the installation controller 129 generates an external device list (from the viewpoint of the second storage unit 12 a) of those logical devices. To judge whether migration is possible or not, the installation controller 129 utilizes information such as names, types and capacities of devices connected to the second storage unit 12 a. The information such as the names, types and capacities of the devices is acquired from returned information of the response to the above-mentioned “Inquiry” command and returned information of a response to “Read Capacity” command that is sent after the “Inquiry” command. With respect to logical devices (of the first storage unit 12 b) whose migration has been judged to be possible, the installation controller 129 registers those logical devices as external devices of the second storage unit 12 a into the external device management information 128. In detail, the installation controller 129 finds an external device whose device state 44 is “non-installed”, and sets information 42˜48 into the entries concerned of that external device. Now, the device state 44 is changed to “offline”.
  • The installation controller 129 of the second storage unit 12 a notifies the storage manager 131 of the above-mentioned external device list with respect to the designated port. And, the installation controller 134 of the storage manager 131 instructs the second storage unit 12 a to assign the logical devices of the first storage unit 12 b. Receiving this instruction, the installation controller 129 of the second storage unit 12 a assigns an external device a, i.e., a logical device of the first storage unit 12 b, to a non-installed logical device a of the second storage unit 12 a. In detail, the installation controller 129 of the second storage unit 12 a sets the device number 41 of the external device a to which the logical device of the first storage unit 12 b corresponds, into the corresponding physical/external device number 23 of the logical device management information 126 relating to the logical device a. Then, the installation controller 129 of the second storage unit 12 a changes the device state 24 of the logical device management information 126 from “non-installed” to “offline”. In addition, the corresponding logical device number 43 of the external device management information 128 is set to the device number 21 of the logical device a, and the device state 44 is changed to “online”.
  • Successively, in the step 504, the installation controller 134 of the storage manager 131 instructs the second storage unit 12 a to define a LUN to the port 123 a such that the host computer 11 can access the logical device a assigned to the second storage unit 12 a. Receiving this instruction, the installation controller 129 of the second storage unit 12 a defines a LUN relating to the above-assigned logical device a, i.e., defines a device path to the port 123 a of the second storage unit 12 a. Then, the port number/target ID/LUN 25 and the host name 26 of the logical device management information 126 are set.
  • When the logical device of the first storage unit 12 b is assigned as the logical device of the second storage unit 12 a, and also the LUN is defined, then, the installation controller 134 of the storage manager 131 instructs the DLM 111 of the host computer 11 to recognize the devices again. Receiving this instruction, the DLM 111 of the host computer generates a device file relating to the newly-assigned logical device. For example, in the case of the UNIX (a registered trademark) operating system of Hewlett-Packard Ltd., an “IOSCAN” command is used to recognize a new logical device and to generate a device file. When the logical device of the storage unit 12 corresponding to the newly-generated device file is same as one corresponding to a previously-generated device file, then, the DLM 111 detect it and manages these device file as a same group. To judge the sameness, it is considered to use the above-mentioned “Inquiry” command or the like to acquire the device number in the storage 12, for example. However, in the case where a logical device b in the first storage unit 12 b corresponds to a logical device a in the second storage unit 12 a, the DLM 111 sees these logical devices a and b as logical devices of the different storage units 12 a and 12 b, they are not managed in a same group.
  • Next, the installation controller 134 of the storage manager 131 instructs the DLM 111 of the host computer 11 to change the access destination. Receiving this instruction, the DLM 111 changes access to the device in the first storage 12 b to access to the device in the second storage unit 12 a (Step 506). In detail, first, the installation controller 134 of the storage manager 131 sends device correspondence information of the first storage unit 12 b and the second storage unit 12 a to the DLM 111. The device correspondence information is information of the assignment of the logical devices of the second storage unit 12 b. The DLM 111 of the host computer 11 assigns a virtual device file that is assigned to a device file group relating to a logical device b in the first storage unit 12 b to a device file group relating to a logical device a in the second storage unit 12 a. As a result, software operating on the host computer 11 can access the logical device a in the second storage unit 12 a according to a same procedure of accessing the logical device b in the first storage unit 12 b.
  • Next, in the step 507, the installation controller 134 of the storage manager 131 makes the switch 18 change the zoning setting and makes the first storage unit 12 b change setting of the device access right, to inhibit the host computer 11 from directly accessing the devices of the first storage unit 12 b.
  • Next, referring to the flowchart shown in FIG. 6, there will be described processing of migrating data stored in the devices in the first storage unit 12 b to an empty device in the second storage unit 12 a, after installation of the second storage unit 12 a into the computer system.
  • First, the installation controller 134 of the storage manager 131 instructs the second storage unit 12 a to migrate data. In the step 601, the installation controller 129 of the second storage unit 12 a checks the device state 34 of the RAID management information 127, to search for a physical device a in the “offline” state, i.e., in an empty state. When a physical device in the “offline” state is found, then, the size 32 is referred to in order to obtain the capacity of the empty device. Next, in the step 602, the installation controller 129 searches for such an external device (hereinafter, referred to as the migration object device) that the device state 44 of the external device management information 128 is “online” and the size 42 of the external device management information 128 can be accommodated by the capacity of the physical device a.
  • When the empty physical device a as the migration destination and the migration object device are determined, then, in the step 603, the installation controller 129 assigns an empty physical device to the logical device a of the second storage unit 12 a (Step 603). In detail, the installation controller 129 registers the number of the logical device a into the corresponding logical device number 33 of the RAID management information 127 corresponding to the physical device a, and changes the device state 34 from “offline” to “online”. Further, after initializing the data migration progress pointer 28 of the logical device management information 126 corresponding to the logical device a, the device state 24 is set to “data migration in progress”, the data migration processing flag 29 is set to “On”, and the migrating physical/external device number 27 is set to the device number of the physical device a.
  • When the device assignment is finished, then, in the step 604, the installation controller 129 of the second storage unit 12 a performs processing of data migration from the migration object device to the physical device a. In detail, from the top of the migration object device, data are read to the cache memory 124, and then, the data are written onto the physical device a. This operation is repeated to the end of the migration object device. In the course of this operation, each time when writing onto the physical device a is finished, the first address of the next migration object area is set into the data migration progress pointer 28.
  • When migration of all the data is finished, then, in the step 605, the installation controller 129 sets the corresponding physical/external device number 23 of the logical device management information 126 with the physical device number of the physical device a, and the device state 24 is changed from “data migration in progress” to “online”, the data migration flag 29 is set to “Off”, and the migrating physical/external device number 27 is set to the invalid value. Further, the corresponding logical device number 43 of the external device management information 128 corresponding to the migration object device is set to the invalid value, and the device state 44 is set to “offline”.
  • Next, referring to the flowchart shown in FIG. 7, there will be described operation of the second storage unit 12 a in response to an input-output request from the host computer 11.
  • When the installation controller 129 of the second storage unit 12 a receives an input-output request from the host computer 11 (Step 701), the installation controller 129 judges whether the request is read or write (Step 702). In the case where the request is read, it is checked whether processing object data are held in the cache memory 124 (hit) (Step 703). When the processing object data are not held in the cache memory 124, data staging to the cache memory 124 is performed. At that time, it is judged whether the data migration is in progress, based on the device state 24 of the logical device in the logical device management information 126. When the data migration is in progress, then, it is judged whether a processing object address of the logical device as the processing object is in a migrated data area, based on the data migration progress pointer 28 relating to the logical device in the logical device management information 126 (Step 704). In the case where the data migration is in progress and data of the processing object area has been migrated already, then, read processing is performed for reading from the migration destination device indicated by the migrating physical/external device number 27 (Step 706). In the other case, read processing is performed for reading from the migration object device indicated by the corresponding physical/external device number 23 (Step 705).
  • In the read processing in the step 705, the installation controller 129 converts the read request from the host computer 11 into a read request to the migration object device indicated by the corresponding physical/external device number 23, and sends the converted request to the first storage unit 12 b. Receiving this read request, the first storage unit 12 b performs read processing toward the disk unit 121 corresponding to the above-mentioned migration object device, and sends read contents to the second storage unit 12 a. Further, in the read processing in the step 706, the read processing is performed toward the migration object device indicated by the migrating physical/external device number 27.
  • When, after execution of the read processing (Step 705 or 706), the data staging to the cache memory 124 is finished, then, the object data held in the cache memory 124 is transferred to the host computer 11 (Step 707). And, the disk controller 122 of the second storage unit 12 a sends a completion report to the host computer 11 (Step 708).
  • When it is judged in the step 703 that cache hit occurs, then, the object data held in the cache memory 124 are immediately transferred to the host computer 11 (Step 707).
  • When the data transfer to the host computer 11 is finished, the disk controller 122 of the second storage unit 12 a sends a processing completion report to the host computer 11 (Step 708).
  • When it is judged in the step 702 that the input-output request from the host computer 11 is write, then, the disk controller 122 of the second storage unit 12 a assigns a write data storage area to the cache memory 124, transfers write data from the host computer 11 to the cache memory 124, and sends a completion report to the host computer 11 (Steps 709-711). Thereafter, destaging of the write data is performed.
  • In the course of the destaging, it is judged whether the logical device is under data migration, based on the device state 24 of the logical device management information 126 (Step 712). When the logical device is under data migration, then, write processing of the above-mentioned data is performed toward both the migration source (migration object) device and the migration destination device (Step 713). On the other hand, when the logical device is not under data migration, write processing of the above-mentioned data is performed toward the device indicated by the corresponding physical/external device number 23 (Step 714).
  • Next, referring to the flowchart shown in FIG. 8, there will be described data migration processing in the case where a disk unit 121 is added to the second storage unit 12 a.
  • First, when the storage administrator adds a disk unit 121 to the second storage unit 12 a, and the installation controller 129 of the second storage unit 12 a detects this addition (Step 801), then, the installation controller 129 defines a new empty device, i.e., a physical device of an “offline” state (Step 802). At that time, the entries 32-39 of the RAID management information 127 are updated.
  • Thereafter, data migration of an external device whose data are not migrated yet is performed toward the newly-assigned empty device (Steps 803-806). These processes (Steps 803-806) are similar to the steps 602-605 of FIG. 6, and not described here again.
  • Hereinabove, an embodiment of the present invention has been described. However, the present invention is not limited to the above-described embodiment, and can be modified variously within the scope of the present invention.
  • For example, in the processing of installing the second storage unit 12 a to the computer system, which has been described referring to FIG. 5, the port ID list of the first storage unit 12 b as the migration object is sent from the storage manager 131 to the second storage unit 12 a, in the step 503. However, instead of the port ID list, information that can specify the first storage unit 12 b (for example, identification information list for identifying the unit name obtainable by an “Inquiry” command) may be sent. Identification information of the mentioned list is information required by the storage manager 131 to manage the first storage unit 12 b, and although basically held inside the storage manager 131, may be obtained by sending an “Inquiry” command to the first storage unit 12 b at the time of sending the list. In that case, the second storage unit 12 a sends an “Inquiry” command to all the storage node ports that can be reached from the port 123 b, and compares the above-mentioned identification information list with unit identification information among information obtained from the first storage unit 12 b, so that only coincident ports become migration objects. Further, it is possible that the second storage unit 12 a does not receive an instruction from the storage manager 131 and all the storage node ports reachable from the port 123 b become migration objects.
  • Further, in the step 503 during installation processing of the second storage unit 12 a, the storage manager 131 is notified of the list of the external devices detected by the second storage unit 12 a, and only the external devices designated by the storage manager become the migration objects. However, it is possible that the second storage unit 12 a does not notify the storage manager 131 of the detected external device list, and all the devices shown in the external device list become migration objects.
  • Further, in the step 503, the second storage unit 12 a selects and assigns the non-installed logical device to the external device designated by the storage manager 131. However, the storage manager 131 may determine a non-installed logical device as an object of assignment and indicate the determined logical device to the second storage unit 12 a. In that case, the storage manager 131 must obtain information such as the logical device number 21 and the device state 24 out of the logical device management information 126 shown in FIG. 2, to determine migration objects based on the obtained information.
  • Further, as described referring to the flowchart of FIG. 6, in the step 601 during the migration processing from an external device, i.e., a logical device of the first storage unit 12 b, which is assigned to a logical device of the second storage unit 12 a, to an empty physical device of the second storage unit 12 a, the second storage unit 12 a performs data migration from the external device to all the empty physical devices as the migration destination. However, it is possible to limit migration destination physical devices, based on control information that can be used to judge whether a physical device can be a migration object. In detail, a data migration target availability flag is provided to each record of the RAID management information shown in FIG. 3. This flag is set with a flag value indicating whether each physical device can become a data migration destination at the time of initialization or addition of a physical device. Based on this information, the second storage unit 12 a specifies a physical device that can be a migration destination. Here, the mentioned flag value is set by the storage administrator using a configuration management terminal (not shown in FIG. 1) of the second storage unit 12 a, or using an input-output unit such as a keyboard and/or a mouse provided to the storage manager 131. For example, it is possible to employ an arrangement in which a flag value is automatically set to “unavailable as migration target” as a basic set value given at the time of installation of a physical device, and the storage administrator changes the flag value relating to a specific physical device to “available as migration target”. Or, it is possible to employ an arrangement in which, as the basic set value, the value “available as migration target” is set automatically, and the storage administrator changes the flag value relating to a specific physical device to “unavailable as migration target”.
  • Further, it is possible that, with respect to a data migration instruction of the storage manager 131, the storage manager 131 holds physical device information such as the physical device number 31, the size 32 and the device state 34 out of the RAID management information 127 shown in FIG. 3, and specifies an empty physical device as the data migration destination, to the second storage unit 12 a. In that case, in the data migration processing (shown in FIG. 6) of the second storage unit 12 a, it is necessary to add a step in which it is checked whether the specified physical device is empty and the data migration request is rejected when the specified physical device is not empty.
  • Further, in the processing of the step 602 shown in FIG. 6, when the second storage unit 12 a determines the migration object external device, the external device is determined by checking only whether it can be accommodated by the size of the empty physical device selected in the step 601. However, the migration object may be determined based on other information of the external device. For example, it is possible that a data migration object possibility flag is provided to each record of the external device management information 128 shown in FIG. 4, and it is judged whether the external device can be an object of migration. In that case, when the external device management information 128 on an external device is registered in the step 503, the above-mentioned flag is initialized to have a value indicating possibility or impossibility of migration, and thereafter, the storage administrator changes the flag value. When the storage administrator changes the flag value, a configuration management terminal (not shown in FIG. 1) of the second storage unit 12 a, or an input-output unit such as a keyboard and/or a mouse provided to the storage manager 131 may be used. Further, instead of the above-mentioned data migration object possibility flag, data migration object priority information may be provided. In that case, the second storage unit 12 a determines the migration object external device, referring to the migration object priority information set by the storage administrator.
  • Further, as a standard for determining a migration object external device, host access statistical information to the external device may be used, for example. In detail, the second storage unit 12 a acquires access statistical information for each logical device. FIG. 9 shows an example of the statistical information. In each record of the access statistical information, an access frequency 91 indicates the number of accesses per time unit to the logical device, and a read frequency 92 indicates the number of reads per time unit from the logical device. A write frequency can be calculated from the access frequency 91 and the read frequency 92. A read cache hit rate 93 and a write cache hit rate 94 are hit rates in the cache memory 124 of the second storage unit 12 a at the time of read access and at the time of write access, respectively. By combining these information items, it is possible to calculate an access frequency of each logical device to the corresponding external device (device of the first storage unit 12 b). Here, as a data migration object, it is possible to select such an external device that has a higher access frequency and can be accommodated by the size of an empty device, based on thus-obtained access frequency for each external device.
  • Further, in the data migration processing shown in FIG. 6, the storage manager instructs the second storage unit 12 a to perform data migration. However, the second storage unit 12 a may automatically perform the data migration processing, as an extension of the processing of associating an external device, i.e., a logical device of the first storage unit 12 b, with a logical device of the second storage unit 12 a. Namely, out of the various functions of the installation controller 134 of the storage manager 131, the functions relating to the data migration processing shown in FIG. 6 may be mounted on the second storage unit 12 a.

Claims (1)

1. A storage unit installation method for newly installing a second storage unit having one or more storage devices into a computer system comprising a first storage unit having one or more storage devices and a host computer accessing said first storage unit, wherein:
said second storage unit is connected with said host computer and said first storage unit in such a way that input and output of information are possible;
access right setting of said first storage unit is changed such that the second storage unit can access the first storage unit;
a logical device (hereinafter, referred to as a first logical device) relating to said one or more storage devices of the first storage unit is assigned to a logical device (hereinafter, referred to as a second logical device) of the second storage unit;
path definition with respect to said second logical device and device recognition in said host computer are performed such that the host computer can access the second logical device of the second storage unit; and
input-output setting of said host computer is changed such that said second storage unit is requested to processing of input-output from said host computer to said one or more storage devices of said first storage unit.
US11/476,704 2003-01-16 2006-06-29 Storage unit, installation method thereof and installation program therefore Abandoned US20060248302A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US11/476,704 US20060248302A1 (en) 2003-01-16 2006-06-29 Storage unit, installation method thereof and installation program therefore

Applications Claiming Priority (5)

Application Number Priority Date Filing Date Title
JP2003008821A JP2004220450A (en) 2003-01-16 2003-01-16 Storage device, its introduction method and its introduction program
JP2003-008821 2003-01-16
US10/636,758 US7177991B2 (en) 2003-01-16 2003-08-08 Installation method of new storage system into a computer system
US11/178,373 US20050246491A1 (en) 2003-01-16 2005-07-12 Storage unit, installation method thereof and installation program therefore
US11/476,704 US20060248302A1 (en) 2003-01-16 2006-06-29 Storage unit, installation method thereof and installation program therefore

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US11/178,373 Continuation US20050246491A1 (en) 2003-01-16 2005-07-12 Storage unit, installation method thereof and installation program therefore

Publications (1)

Publication Number Publication Date
US20060248302A1 true US20060248302A1 (en) 2006-11-02

Family

ID=32588549

Family Applications (3)

Application Number Title Priority Date Filing Date
US10/636,758 Active 2024-07-03 US7177991B2 (en) 2003-01-16 2003-08-08 Installation method of new storage system into a computer system
US11/178,373 Abandoned US20050246491A1 (en) 2003-01-16 2005-07-12 Storage unit, installation method thereof and installation program therefore
US11/476,704 Abandoned US20060248302A1 (en) 2003-01-16 2006-06-29 Storage unit, installation method thereof and installation program therefore

Family Applications Before (2)

Application Number Title Priority Date Filing Date
US10/636,758 Active 2024-07-03 US7177991B2 (en) 2003-01-16 2003-08-08 Installation method of new storage system into a computer system
US11/178,373 Abandoned US20050246491A1 (en) 2003-01-16 2005-07-12 Storage unit, installation method thereof and installation program therefore

Country Status (4)

Country Link
US (3) US7177991B2 (en)
EP (2) EP1439452A3 (en)
JP (1) JP2004220450A (en)
DE (1) DE07000607T1 (en)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060200634A1 (en) * 2005-03-03 2006-09-07 Fujitsu Limited Data storage system and data storage control apparatus
US20090019271A1 (en) * 2007-07-11 2009-01-15 Canon Kabushiki Kaisha Information processing apparatus, information processing method, and storage medium
US20090240898A1 (en) * 2008-03-21 2009-09-24 Hitachi, Ltd. Storage System and Method of Taking Over Logical Unit in Storage System
US20110302280A1 (en) * 2008-07-02 2011-12-08 Hewlett-Packard Development Company Lp Performing Administrative Tasks Associated with a Network-Attached Storage System at a Client
US8443160B2 (en) 2010-08-06 2013-05-14 Hitachi, Ltd. Computer system and data migration method
WO2014113816A1 (en) * 2013-01-21 2014-07-24 Western Digital Technologies, Inc. Initialization of a storage device
US9213490B2 (en) 2012-06-18 2015-12-15 Hitachi, Ltd. Computer system and data migration method
US9292211B2 (en) 2011-03-02 2016-03-22 Hitachi, Ltd. Computer system and data migration method

Families Citing this family (67)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4704659B2 (en) * 2002-04-26 2011-06-15 株式会社日立製作所 Storage system control method and storage control device
JP2004110367A (en) * 2002-09-18 2004-04-08 Hitachi Ltd Storage system control method, storage control device, and storage system
US7263593B2 (en) * 2002-11-25 2007-08-28 Hitachi, Ltd. Virtualization controller and data transfer control method
JP2004220450A (en) * 2003-01-16 2004-08-05 Hitachi Ltd Storage device, its introduction method and its introduction program
JP4283004B2 (en) 2003-02-04 2009-06-24 株式会社日立製作所 Disk control device and control method of disk control device
JP2005018193A (en) * 2003-06-24 2005-01-20 Hitachi Ltd Interface command control method for disk device, and computer system
JP4253224B2 (en) * 2003-07-02 2009-04-08 株式会社日立製作所 Address management method and apparatus
GB0320388D0 (en) * 2003-08-30 2003-10-01 Ibm Method and apparatus for improved error avoidance in a redundant data path system
JP4598387B2 (en) * 2003-09-17 2010-12-15 株式会社日立製作所 Storage system
US7219201B2 (en) 2003-09-17 2007-05-15 Hitachi, Ltd. Remote storage disk control device and method for controlling the same
JP4307202B2 (en) * 2003-09-29 2009-08-05 株式会社日立製作所 Storage system and storage control device
JP4307964B2 (en) 2003-11-26 2009-08-05 株式会社日立製作所 Access restriction information setting method and apparatus
JP4463042B2 (en) 2003-12-26 2010-05-12 株式会社日立製作所 Storage system having volume dynamic allocation function
JP4500057B2 (en) * 2004-01-13 2010-07-14 株式会社日立製作所 Data migration method
JP2005202893A (en) * 2004-01-19 2005-07-28 Hitachi Ltd Storage device controller, storage system, recording medium recording program, information processor, and method for controlling storage system
JP4520755B2 (en) * 2004-02-26 2010-08-11 株式会社日立製作所 Data migration method and data migration apparatus
JP4391265B2 (en) 2004-02-26 2009-12-24 株式会社日立製作所 Storage subsystem and performance tuning method
JP2005275829A (en) * 2004-03-25 2005-10-06 Hitachi Ltd Storage system
US20050228659A1 (en) * 2004-04-06 2005-10-13 Vlad Mitlin Stealth communication method
JP4452557B2 (en) * 2004-05-27 2010-04-21 株式会社日立製作所 Remote copy with WORM guarantee
JP4485875B2 (en) * 2004-07-28 2010-06-23 株式会社日立製作所 Storage connection changing method, storage management system and program
US7171532B2 (en) * 2004-08-30 2007-01-30 Hitachi, Ltd. Method and system for data lifecycle management in an external storage linkage environment
JP4646574B2 (en) * 2004-08-30 2011-03-09 株式会社日立製作所 Data processing system
JP4624746B2 (en) * 2004-09-10 2011-02-02 株式会社日立製作所 Compound computer apparatus and management method thereof
JP4549787B2 (en) * 2004-09-10 2010-09-22 株式会社日立製作所 Storage device
JP4568574B2 (en) * 2004-10-15 2010-10-27 株式会社日立製作所 Storage device introduction method, program, and management computer
JP2006127028A (en) 2004-10-27 2006-05-18 Hitachi Ltd Memory system and storage controller
JP4341072B2 (en) * 2004-12-16 2009-10-07 日本電気株式会社 Data arrangement management method, system, apparatus and program
US7698704B2 (en) * 2005-02-17 2010-04-13 International Business Machines Corporation Method for installing operating system on remote storage: flash deploy and install zone
US7290108B2 (en) 2005-03-25 2007-10-30 Hitachi, Ltd. Information processing system having volume guard function
JP2006285464A (en) * 2005-03-31 2006-10-19 Hitachi Ltd Computer system, storage, and device control method
JP5057656B2 (en) 2005-05-24 2012-10-24 株式会社日立製作所 Storage system and storage system operation method
JP4741304B2 (en) 2005-07-11 2011-08-03 株式会社日立製作所 Data migration method or data migration system
JP4963808B2 (en) 2005-08-05 2012-06-27 株式会社日立製作所 Storage control system
JP4842593B2 (en) 2005-09-05 2011-12-21 株式会社日立製作所 Device control takeover method for storage virtualization apparatus
JP2007072571A (en) * 2005-09-05 2007-03-22 Hitachi Ltd Computer system, management computer and access path management method
JP4955996B2 (en) * 2005-09-20 2012-06-20 株式会社日立製作所 Volume migration method and storage network system
US7702851B2 (en) 2005-09-20 2010-04-20 Hitachi, Ltd. Logical volume transfer method and storage network system
JP4790372B2 (en) * 2005-10-20 2011-10-12 株式会社日立製作所 Computer system for distributing storage access load and control method thereof
JP4852298B2 (en) * 2005-10-28 2012-01-11 株式会社日立製作所 Method for taking over information for identifying virtual volume and storage system using the method
JP2007133807A (en) * 2005-11-14 2007-05-31 Hitachi Ltd Data processing system, storage device, and management unit
JP4757038B2 (en) 2006-01-25 2011-08-24 株式会社日立製作所 Storage system and storage control device
JP4800059B2 (en) 2006-02-13 2011-10-26 株式会社日立製作所 Virtual storage system and control method thereof
JP4331742B2 (en) 2006-10-25 2009-09-16 株式会社日立製作所 Computer system, computer and method for managing performance based on I / O allocation ratio
JP4897499B2 (en) 2007-01-19 2012-03-14 株式会社日立製作所 Storage system or storage migration method
US8990527B1 (en) * 2007-06-29 2015-03-24 Emc Corporation Data migration with source device reuse
JP2009026255A (en) 2007-07-24 2009-02-05 Hitachi Ltd Data migration method, data migration system, and data migration program
US20100235592A1 (en) * 2009-03-10 2010-09-16 Yasunori Kaneda Date volume migration with migration log confirmation
JP5438827B2 (en) * 2009-10-09 2014-03-12 株式会社日立製作所 Storage control device and virtual volume control method
JP5335848B2 (en) * 2011-04-18 2013-11-06 株式会社日立製作所 Storage system and storage system operation method
US20120278796A1 (en) * 2011-04-26 2012-11-01 Microsoft Corporation Automatically installing device drivers
US20130007726A1 (en) * 2011-06-30 2013-01-03 Indrajit Poddar Virtual machine disk image installation
US8601473B1 (en) 2011-08-10 2013-12-03 Nutanix, Inc. Architecture for managing I/O and storage for a virtualization environment
US8549519B2 (en) 2011-08-19 2013-10-01 Hitachi, Ltd. Method and apparatus to improve efficiency in the use of resources in data center
JP5883743B2 (en) * 2012-08-20 2016-03-15 株式会社日立製作所 Method for reducing communication interruption time in packet communication networks
JP6005566B2 (en) 2013-03-18 2016-10-12 株式会社東芝 Information processing system, control program, and information processing apparatus
US9665386B2 (en) 2013-06-14 2017-05-30 Nutanix, Inc. Method for leveraging hypervisor functionality for maintaining application consistent snapshots in a virtualization environment
US9740514B1 (en) 2013-06-26 2017-08-22 Nutanix, Inc. Method and system to share data with snapshots in a virtualization environment
US11243707B2 (en) 2014-03-12 2022-02-08 Nutanix, Inc. Method and system for implementing virtual machine images
WO2015167432A1 (en) * 2014-04-28 2015-11-05 Hewlett-Packard Development Company, L.P. Storage management
JP6019169B2 (en) * 2015-05-14 2016-11-02 株式会社日立製作所 Information storage system
US10613947B2 (en) 2016-06-09 2020-04-07 Nutanix, Inc. Saving and restoring storage devices using application-consistent snapshots
JP2018010507A (en) * 2016-07-14 2018-01-18 富士通株式会社 Memory management program, memory management method and memory management device
US10979133B2 (en) 2017-06-12 2021-04-13 Ast & Science, Llc System and method for high throughput fractionated satellites (HTFS) for direct connectivity to and from end user devices and terminals using flight formations of small or very small satellites
US10824522B2 (en) 2017-11-27 2020-11-03 Nutanix, Inc. Method, apparatus, and computer program product for generating consistent snapshots without quiescing applications
US20230082032A1 (en) * 2020-02-25 2023-03-16 Nippon Telegraph And Telephone Corporation Transmission device interconnection registration device, transmission device interconnection registration method, and program
CN114080596A (en) * 2021-09-29 2022-02-22 长江存储科技有限责任公司 Data protection method for memory and memory device thereof

Citations (38)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5459957A (en) * 1994-06-09 1995-10-24 Winer; Guy T. Gun security and safety system
US5504982A (en) * 1994-06-27 1996-04-09 Sharp; Jason W. Embedded arrowhead removing tool
US5680590A (en) * 1990-09-21 1997-10-21 Parti; Michael Simulation system and method of using same
US5809285A (en) * 1995-12-21 1998-09-15 Compaq Computer Corporation Computer system having a virtual drive array controller
US5895495A (en) * 1997-03-13 1999-04-20 International Business Machines Corporation Demand-based larx-reserve protocol for SMP system buses
US6044444A (en) * 1996-05-28 2000-03-28 Emc Corporation Remote data mirroring having preselection of automatic recovery or intervention required when a disruption is detected
US6101497A (en) * 1996-05-31 2000-08-08 Emc Corporation Method and apparatus for independent and simultaneous access to a common data set
US6108748A (en) * 1995-09-01 2000-08-22 Emc Corporation System and method for on-line, real time, data migration
US6209002B1 (en) * 1999-02-17 2001-03-27 Emc Corporation Method and apparatus for cascading data through redundant data storage units
US6240494B1 (en) * 1997-12-24 2001-05-29 Hitachi, Ltd. Subsystem replacement method
US6363462B1 (en) * 1997-03-31 2002-03-26 Lsi Logic Corporation Storage controller providing automatic retention and deletion of synchronous back-up data
US20020087751A1 (en) * 1999-03-04 2002-07-04 Advanced Micro Devices, Inc. Switch based scalable preformance storage architecture
US6453354B1 (en) * 1999-03-03 2002-09-17 Emc Corporation File server system using connection-oriented protocol and sharing data sets among data movers
US6457109B1 (en) * 2000-08-18 2002-09-24 Storage Technology Corporation Method and apparatus for copying data from one storage system to another storage system
US6480934B1 (en) * 1998-09-28 2002-11-12 Hitachi, Ltd. Storage control unit and method for handling data storage system using thereof
US20020178328A1 (en) * 2001-05-23 2002-11-28 Kiyoshi Honda Storage subsystem
US20020194428A1 (en) * 2001-03-30 2002-12-19 Intransa, Inc., A Delaware Corporation Method and apparatus for distributing raid processing over a network link
US20030033494A1 (en) * 2001-08-10 2003-02-13 Akira Fujibayashi Apparatus and method for online data migration with remote copy
US6560673B2 (en) * 2001-01-31 2003-05-06 Hewlett Packard Development Company, L.P. Fibre channel upgrade path
US20030105931A1 (en) * 2001-11-30 2003-06-05 Weber Bret S. Architecture for transparent mirroring
US6587935B2 (en) * 1996-05-31 2003-07-01 Emc Corporation Method and apparatus for mirroring data in a remote data storage system
US20030126388A1 (en) * 2001-12-27 2003-07-03 Hitachi, Ltd. Method and apparatus for managing storage based replication
US20030163553A1 (en) * 2002-02-26 2003-08-28 Hitachi, Ltd. Storage system and method of copying data
US6647414B1 (en) * 1998-08-26 2003-11-11 Telefonaktiebolaget Lm Ericsson (Publ) Method for automatic information transmission in an IP network
US20030229764A1 (en) * 2002-06-05 2003-12-11 Hitachi, Ltd. Data storage subsystem
US6675268B1 (en) * 2000-12-11 2004-01-06 Lsi Logic Corporation Method and apparatus for handling transfers of data volumes between controllers in a storage environment having multiple paths to the data volumes
US6697367B1 (en) * 2000-06-12 2004-02-24 Emc Corporation Multihop system calls
US20040073831A1 (en) * 1993-04-23 2004-04-15 Moshe Yanai Remote data mirroring
US20040098547A1 (en) * 1998-12-31 2004-05-20 Yuval Ofek Apparatus and methods for transferring, backing up, and restoring data in a computer system
US20040158673A1 (en) * 1998-12-22 2004-08-12 Hitachi, Ltd. Disk storage system including a switch
US20040158652A1 (en) * 2000-06-29 2004-08-12 Kiyohiro Obara Data migration method, protocol converter and switching apparatus using it
US20050010743A1 (en) * 1998-12-03 2005-01-13 Sun Microsystems, Inc. Multiple-thread processor for threaded software applications
US20050055501A1 (en) * 2003-09-08 2005-03-10 Copan Systems, Inc. High-density storage systems using hierarchical interconnect
US6876656B2 (en) * 2001-06-15 2005-04-05 Broadcom Corporation Switch assisted frame aliasing for storage virtualization
US6912643B2 (en) * 2002-08-19 2005-06-28 Aristos Logic Corporation Method of flexibly mapping a number of storage elements into a virtual storage element
US6922761B2 (en) * 2002-03-25 2005-07-26 Emc Corporation Method and system for migrating data
US6976103B1 (en) * 2000-03-03 2005-12-13 Hitachi, Ltd. Data migration method using storage area network
US6976134B1 (en) * 2001-09-28 2005-12-13 Emc Corporation Pooling and provisioning storage resources in a storage network

Family Cites Families (98)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3771137A (en) 1971-09-10 1973-11-06 Ibm Memory control in a multipurpose system utilizing a broadcast
US4025904A (en) * 1973-10-19 1977-05-24 Texas Instruments Incorporated Programmed allocation of computer memory workspace
US4638426A (en) * 1982-12-30 1987-01-20 International Business Machines Corporation Virtual memory address translation mechanism with controlled data persistence
US4710868A (en) 1984-06-29 1987-12-01 International Business Machines Corporation Interconnect scheme for shared memory local networks
US5155845A (en) * 1990-06-15 1992-10-13 Storage Technology Corporation Data storage system for providing redundant copies of data on different disk drives
US5459857A (en) * 1992-05-15 1995-10-17 Storage Technology Corporation Fault tolerant disk array data storage subsystem
US5408465A (en) * 1993-06-21 1995-04-18 Hewlett-Packard Company Flexible scheme for admission control of multimedia streams on integrated networks
US5504882A (en) * 1994-06-20 1996-04-02 International Business Machines Corporation Fault tolerant data storage subsystem employing hierarchically arranged controllers
US5548712A (en) * 1995-01-19 1996-08-20 Hewlett-Packard Company Data storage system and method for managing asynchronous attachment and detachment of storage disks
US5680580A (en) * 1995-02-28 1997-10-21 International Business Machines Corporation Remote copy system for setting request interconnect bit in each adapter within storage controller and initiating request connect frame in response to the setting bit
US5917723A (en) * 1995-05-22 1999-06-29 Lsi Logic Corporation Method and apparatus for transferring data between two devices with reduced microprocessor overhead
US5758118A (en) * 1995-12-08 1998-05-26 International Business Machines Corporation Methods and data storage devices for RAID expansion by on-line addition of new DASDs
JP3287203B2 (en) 1996-01-10 2002-06-04 株式会社日立製作所 External storage controller and data transfer method between external storage controllers
US5870537A (en) * 1996-03-13 1999-02-09 International Business Machines Corporation Concurrent switch to shadowed device for storage controller and device errors
JP3641872B2 (en) * 1996-04-08 2005-04-27 株式会社日立製作所 Storage system
GB2312319B (en) * 1996-04-15 1998-12-09 Discreet Logic Inc Video storage
US5835954A (en) * 1996-09-12 1998-11-10 International Business Machines Corporation Target DASD controlled data migration move
JP3193880B2 (en) * 1996-12-11 2001-07-30 株式会社日立製作所 Data migration method
US5895485A (en) * 1997-02-24 1999-04-20 Eccs, Inc. Method and device using a redundant cache for preventing the loss of dirty data
JP3671595B2 (en) * 1997-04-01 2005-07-13 株式会社日立製作所 Compound computer system and compound I / O system
JP3228182B2 (en) * 1997-05-29 2001-11-12 株式会社日立製作所 Storage system and method for accessing storage system
US6012123A (en) * 1997-06-10 2000-01-04 Adaptec Inc External I/O controller system for an independent access parity disk array
US6247103B1 (en) * 1998-01-06 2001-06-12 International Business Machines Corporation Host storage management control of outboard data movement using push-pull operations
US6173374B1 (en) * 1998-02-11 2001-01-09 Lsi Logic Corporation System and method for peer-to-peer accelerated I/O shipping between host bus adapters in clustered computer network
US6070224A (en) * 1998-04-02 2000-05-30 Emc Corporation Virtual tape system
US6260120B1 (en) * 1998-06-29 2001-07-10 Emc Corporation Storage mapping and partitioning among multiple host processors in the presence of login state changes and host controller replacement
US6421711B1 (en) * 1998-06-29 2002-07-16 Emc Corporation Virtual ports for data transferring of a data storage system
US6195730B1 (en) * 1998-07-24 2001-02-27 Storage Technology Corporation Computer system with storage device mapping input/output processor
EP0981091B1 (en) * 1998-08-20 2008-03-19 Hitachi, Ltd. Data copying in storage systems
US6457139B1 (en) * 1998-12-30 2002-09-24 Emc Corporation Method and apparatus for providing a host computer with information relating to the mapping of logical volumes within an intelligent storage system
US6640278B1 (en) 1999-03-25 2003-10-28 Dell Products L.P. Method for configuration and management of storage resources in a storage network
US6654830B1 (en) 1999-03-25 2003-11-25 Dell Products L.P. Method and system for managing data migration for a storage system
US6553408B1 (en) * 1999-03-25 2003-04-22 Dell Products L.P. Virtual device architecture having memory for storing lists of driver modules
US6446141B1 (en) * 1999-03-25 2002-09-03 Dell Products, L.P. Storage server system including ranking of data source
US6247099B1 (en) * 1999-06-03 2001-06-12 International Business Machines Corporation System and method for maintaining cache coherency and data synchronization in a computer system having multiple active controllers
US6219753B1 (en) * 1999-06-04 2001-04-17 International Business Machines Corporation Fiber channel topological structure and method including structure and method for raid devices and controllers
JP3853540B2 (en) * 1999-06-30 2006-12-06 日本電気株式会社 Fiber channel-connected magnetic disk device and fiber channel-connected magnetic disk controller
US6446175B1 (en) * 1999-07-28 2002-09-03 Storage Technology Corporation Storing and retrieving data on tape backup system located at remote storage system site
US6484173B1 (en) 2000-02-07 2002-11-19 Emc Corporation Controlling access to a storage device
US20020103889A1 (en) * 2000-02-11 2002-08-01 Thomas Markson Virtual storage layer approach for dynamically associating computer storage with processing hosts
US20020065864A1 (en) * 2000-03-03 2002-05-30 Hartsell Neal D. Systems and method for resource tracking in information management environments
US6654831B1 (en) 2000-03-07 2003-11-25 International Business Machine Corporation Using multiple controllers together to create data spans
US6490659B1 (en) 2000-03-31 2002-12-03 International Business Machines Corporation Warm start cache recovery in a dual active controller with cache coherency using stripe locks for implied storage volume reservations
US6647387B1 (en) 2000-04-27 2003-11-11 International Business Machine Corporation System, apparatus, and method for enhancing storage management in a storage area network
US6596113B2 (en) * 2000-05-16 2003-07-22 Kimberly-Clark Worldwide, Inc. Presentation and bonding of garment side panels
JP2001337790A (en) 2000-05-24 2001-12-07 Hitachi Ltd Storage unit and its hierarchical management control method
JP4719957B2 (en) * 2000-05-24 2011-07-06 株式会社日立製作所 Storage control device, storage system, and storage system security setting method
US6745207B2 (en) * 2000-06-02 2004-06-01 Hewlett-Packard Development Company, L.P. System and method for managing virtual storage
US7720928B2 (en) * 2000-06-02 2010-05-18 Hewlett-Packard Development Company, L.P. Centralized fine-grained enhancements for distributed table driven I/O mapping
JP4776804B2 (en) 2000-06-12 2011-09-21 キヤノン株式会社 Network device, control method therefor, and computer program
US6804755B2 (en) 2000-06-19 2004-10-12 Storage Technology Corporation Apparatus and method for performing an instant copy of data based on a dynamically changeable virtual mapping scheme
US6912537B2 (en) * 2000-06-20 2005-06-28 Storage Technology Corporation Dynamically changeable virtual mapping scheme
US6675258B1 (en) * 2000-06-30 2004-01-06 Lsi Logic Corporation Methods and apparatus for seamless firmware update and propagation in a dual raid controller system
US6766430B2 (en) * 2000-07-06 2004-07-20 Hitachi, Ltd. Data reallocation among storage systems
JP3998405B2 (en) * 2000-07-28 2007-10-24 富士通株式会社 Access control method and storage device using the same
US6976174B2 (en) * 2001-01-04 2005-12-13 Troika Networks, Inc. Secure multiprotocol interface
WO2002065275A1 (en) * 2001-01-11 2002-08-22 Yottayotta, Inc. Storage virtualization system and methods
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
US6990547B2 (en) * 2001-01-29 2006-01-24 Adaptec, Inc. Replacing file system processors by hot swapping
AU2002306495A1 (en) * 2001-02-13 2002-08-28 Candera, Inc. Storage virtualization and storage management to provide higher level storage services
US6606690B2 (en) * 2001-02-20 2003-08-12 Hewlett-Packard Development Company, L.P. System and method for accessing a storage area network as network attached storage
JP4041656B2 (en) * 2001-03-02 2008-01-30 株式会社日立製作所 Storage system and data transmission / reception method in storage system
US6622220B2 (en) * 2001-03-15 2003-09-16 Hewlett-Packard Development Company, L.P. Security-enhanced network attached storage device
JP4009434B2 (en) * 2001-04-18 2007-11-14 株式会社日立製作所 Magnetic disk unit coupling device
US6772315B1 (en) * 2001-05-24 2004-08-03 Rambus Inc Translation lookaside buffer extended to provide physical and main-memory addresses
US20020188592A1 (en) 2001-06-11 2002-12-12 Storage Technology Corporation Outboard data storage management system and method
JP4032670B2 (en) * 2001-06-21 2008-01-16 株式会社日立製作所 Storage device system for authenticating host computer
US6735637B2 (en) * 2001-06-28 2004-05-11 Hewlett-Packard Development Company, L.P. Method and system for providing advanced warning to a data stage device in order to decrease the time for a mirror split operation without starving host I/O request processsing
US6718447B2 (en) * 2001-06-28 2004-04-06 Hewlett-Packard Development Company, L.P. Method and system for providing logically consistent logical unit backup snapshots within one or more data storage devices
US6647460B2 (en) * 2001-07-13 2003-11-11 Hitachi, Ltd. Storage device with I/O counter for partial data reallocation
US6816945B2 (en) * 2001-08-03 2004-11-09 International Business Machines Corporation Quiesce system storage device and method in a dual active controller with cache coherency using stripe locks for implied storage volume reservations
US7185062B2 (en) * 2001-09-28 2007-02-27 Emc Corporation Switch-based storage services
US6910098B2 (en) * 2001-10-16 2005-06-21 Emc Corporation Method and apparatus for maintaining data coherency
US7200144B2 (en) * 2001-10-18 2007-04-03 Qlogic, Corp. Router and methods using network addresses for virtualization
JP2003140837A (en) * 2001-10-30 2003-05-16 Hitachi Ltd Disk array control device
US7107320B2 (en) * 2001-11-02 2006-09-12 Dot Hill Systems Corp. Data mirroring between controllers in an active-active controller pair
US7055056B2 (en) * 2001-11-21 2006-05-30 Hewlett-Packard Development Company, L.P. System and method for ensuring the availability of a storage system
US6973549B1 (en) 2001-12-10 2005-12-06 Incipient, Inc. Locking technique for control and synchronization
US6948039B2 (en) * 2001-12-14 2005-09-20 Voom Technologies, Inc. Data backup and restoration using dynamic virtual storage
US7024427B2 (en) * 2001-12-19 2006-04-04 Emc Corporation Virtual file system
US7007152B2 (en) * 2001-12-28 2006-02-28 Storage Technology Corporation Volume translation apparatus and method
US6912669B2 (en) * 2002-02-21 2005-06-28 International Business Machines Corporation Method and apparatus for maintaining cache coherency in a storage system
US20040003022A1 (en) * 2002-06-27 2004-01-01 International Business Machines Corporation Method and system for using modulo arithmetic to distribute processing over multiple processors
US7353305B2 (en) * 2002-06-28 2008-04-01 Brocade Communications Systems, Inc. Apparatus and method for data virtualization in a storage processing device
US7752361B2 (en) * 2002-06-28 2010-07-06 Brocade Communications Systems, Inc. Apparatus and method for data migration in a storage processing device
US20040028043A1 (en) * 2002-07-31 2004-02-12 Brocade Communications Systems, Inc. Method and apparatus for virtualizing storage devices inside a storage area network fabric
JP2004102374A (en) * 2002-09-05 2004-04-02 Hitachi Ltd Information processing system having data transition device
US7020758B2 (en) * 2002-09-18 2006-03-28 Ortera Inc. Context sensitive storage management
US6857057B2 (en) * 2002-10-03 2005-02-15 Hewlett-Packard Development Company, L.P. Virtual storage systems and virtual storage system operational methods
US7945669B2 (en) * 2002-10-30 2011-05-17 Emc Corporation Method and apparatus for provisioning storage resources
JP2004192105A (en) * 2002-12-09 2004-07-08 Hitachi Ltd Connection device of storage device and computer system including it
JP4325843B2 (en) * 2002-12-20 2009-09-02 株式会社日立製作所 Logical volume copy destination performance adjustment method and apparatus
JP2004220450A (en) * 2003-01-16 2004-08-05 Hitachi Ltd Storage device, its introduction method and its introduction program
JP4322511B2 (en) * 2003-01-27 2009-09-02 株式会社日立製作所 Information processing system control method and information processing system
JP4387116B2 (en) * 2003-02-28 2009-12-16 株式会社日立製作所 Storage system control method and storage system
JP4537022B2 (en) * 2003-07-09 2010-09-01 株式会社日立製作所 A data processing method, a storage area control method, and a data processing system that limit data arrangement.
US8788764B2 (en) * 2003-10-08 2014-07-22 Oracle International Corporation Access controller for storage devices
US20050138184A1 (en) * 2003-12-19 2005-06-23 Sanrad Ltd. Efficient method for sharing data between independent clusters of virtualization switches

Patent Citations (40)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5680590A (en) * 1990-09-21 1997-10-21 Parti; Michael Simulation system and method of using same
US20040073831A1 (en) * 1993-04-23 2004-04-15 Moshe Yanai Remote data mirroring
US5459957A (en) * 1994-06-09 1995-10-24 Winer; Guy T. Gun security and safety system
US5504982A (en) * 1994-06-27 1996-04-09 Sharp; Jason W. Embedded arrowhead removing tool
US20020004890A1 (en) * 1995-09-01 2002-01-10 Yuval Ofek System and method for on-line, real time, data migration
US6108748A (en) * 1995-09-01 2000-08-22 Emc Corporation System and method for on-line, real time, data migration
US5809285A (en) * 1995-12-21 1998-09-15 Compaq Computer Corporation Computer system having a virtual drive array controller
US6044444A (en) * 1996-05-28 2000-03-28 Emc Corporation Remote data mirroring having preselection of automatic recovery or intervention required when a disruption is detected
US6587935B2 (en) * 1996-05-31 2003-07-01 Emc Corporation Method and apparatus for mirroring data in a remote data storage system
US6101497A (en) * 1996-05-31 2000-08-08 Emc Corporation Method and apparatus for independent and simultaneous access to a common data set
US5895495A (en) * 1997-03-13 1999-04-20 International Business Machines Corporation Demand-based larx-reserve protocol for SMP system buses
US6363462B1 (en) * 1997-03-31 2002-03-26 Lsi Logic Corporation Storage controller providing automatic retention and deletion of synchronous back-up data
US6240494B1 (en) * 1997-12-24 2001-05-29 Hitachi, Ltd. Subsystem replacement method
US6647414B1 (en) * 1998-08-26 2003-11-11 Telefonaktiebolaget Lm Ericsson (Publ) Method for automatic information transmission in an IP network
US6480934B1 (en) * 1998-09-28 2002-11-12 Hitachi, Ltd. Storage control unit and method for handling data storage system using thereof
US20050010743A1 (en) * 1998-12-03 2005-01-13 Sun Microsystems, Inc. Multiple-thread processor for threaded software applications
US20040158673A1 (en) * 1998-12-22 2004-08-12 Hitachi, Ltd. Disk storage system including a switch
US20040098547A1 (en) * 1998-12-31 2004-05-20 Yuval Ofek Apparatus and methods for transferring, backing up, and restoring data in a computer system
US6209002B1 (en) * 1999-02-17 2001-03-27 Emc Corporation Method and apparatus for cascading data through redundant data storage units
US6453354B1 (en) * 1999-03-03 2002-09-17 Emc Corporation File server system using connection-oriented protocol and sharing data sets among data movers
US20020087751A1 (en) * 1999-03-04 2002-07-04 Advanced Micro Devices, Inc. Switch based scalable preformance storage architecture
US6976103B1 (en) * 2000-03-03 2005-12-13 Hitachi, Ltd. Data migration method using storage area network
US6697367B1 (en) * 2000-06-12 2004-02-24 Emc Corporation Multihop system calls
US20040158652A1 (en) * 2000-06-29 2004-08-12 Kiyohiro Obara Data migration method, protocol converter and switching apparatus using it
US7130954B2 (en) * 2000-06-29 2006-10-31 Hitachi, Ltd. Data migration method, protocol converter and switching apparatus using it
US6457109B1 (en) * 2000-08-18 2002-09-24 Storage Technology Corporation Method and apparatus for copying data from one storage system to another storage system
US6675268B1 (en) * 2000-12-11 2004-01-06 Lsi Logic Corporation Method and apparatus for handling transfers of data volumes between controllers in a storage environment having multiple paths to the data volumes
US6560673B2 (en) * 2001-01-31 2003-05-06 Hewlett Packard Development Company, L.P. Fibre channel upgrade path
US20020194428A1 (en) * 2001-03-30 2002-12-19 Intransa, Inc., A Delaware Corporation Method and apparatus for distributing raid processing over a network link
US20020178328A1 (en) * 2001-05-23 2002-11-28 Kiyoshi Honda Storage subsystem
US6876656B2 (en) * 2001-06-15 2005-04-05 Broadcom Corporation Switch assisted frame aliasing for storage virtualization
US20030033494A1 (en) * 2001-08-10 2003-02-13 Akira Fujibayashi Apparatus and method for online data migration with remote copy
US6976134B1 (en) * 2001-09-28 2005-12-13 Emc Corporation Pooling and provisioning storage resources in a storage network
US20030105931A1 (en) * 2001-11-30 2003-06-05 Weber Bret S. Architecture for transparent mirroring
US20030126388A1 (en) * 2001-12-27 2003-07-03 Hitachi, Ltd. Method and apparatus for managing storage based replication
US20030163553A1 (en) * 2002-02-26 2003-08-28 Hitachi, Ltd. Storage system and method of copying data
US6922761B2 (en) * 2002-03-25 2005-07-26 Emc Corporation Method and system for migrating data
US20030229764A1 (en) * 2002-06-05 2003-12-11 Hitachi, Ltd. Data storage subsystem
US6912643B2 (en) * 2002-08-19 2005-06-28 Aristos Logic Corporation Method of flexibly mapping a number of storage elements into a virtual storage element
US20050055501A1 (en) * 2003-09-08 2005-03-10 Copan Systems, Inc. High-density storage systems using hierarchical interconnect

Cited By (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060200634A1 (en) * 2005-03-03 2006-09-07 Fujitsu Limited Data storage system and data storage control apparatus
US20090019271A1 (en) * 2007-07-11 2009-01-15 Canon Kabushiki Kaisha Information processing apparatus, information processing method, and storage medium
US8347308B2 (en) * 2007-07-11 2013-01-01 Canon Kabushiki Kaisha Information processing apparatus, information processing method, and storage medium
US20090240898A1 (en) * 2008-03-21 2009-09-24 Hitachi, Ltd. Storage System and Method of Taking Over Logical Unit in Storage System
US7934068B2 (en) 2008-03-21 2011-04-26 Hitachi, Ltd. Storage system and method of taking over logical unit in storage system
US8209505B2 (en) 2008-03-21 2012-06-26 Hitachi, Ltd. Storage system and method of taking over logical unit in storage system
US20110302280A1 (en) * 2008-07-02 2011-12-08 Hewlett-Packard Development Company Lp Performing Administrative Tasks Associated with a Network-Attached Storage System at a Client
US9891902B2 (en) 2008-07-02 2018-02-13 Hewlett-Packard Development Company, L.P. Performing administrative tasks associated with a network-attached storage system at a client
US9354853B2 (en) * 2008-07-02 2016-05-31 Hewlett-Packard Development Company, L.P. Performing administrative tasks associated with a network-attached storage system at a client
US8443160B2 (en) 2010-08-06 2013-05-14 Hitachi, Ltd. Computer system and data migration method
US8892840B2 (en) 2010-08-06 2014-11-18 Hitachi, Ltd. Computer system and data migration method
US9292211B2 (en) 2011-03-02 2016-03-22 Hitachi, Ltd. Computer system and data migration method
US9213490B2 (en) 2012-06-18 2015-12-15 Hitachi, Ltd. Computer system and data migration method
CN104956350A (en) * 2013-01-21 2015-09-30 西部数据技术公司 Initialization of a storage device
US8972655B2 (en) 2013-01-21 2015-03-03 Western Digital Technolgies, Inc. Initialization of a storage device
WO2014113816A1 (en) * 2013-01-21 2014-07-24 Western Digital Technologies, Inc. Initialization of a storage device

Also Published As

Publication number Publication date
US7177991B2 (en) 2007-02-13
DE07000607T1 (en) 2007-10-11
US20040143832A1 (en) 2004-07-22
EP1770502A2 (en) 2007-04-04
EP1439452A2 (en) 2004-07-21
US20050246491A1 (en) 2005-11-03
EP1439452A3 (en) 2007-09-05
JP2004220450A (en) 2004-08-05
EP1770502A3 (en) 2007-09-05

Similar Documents

Publication Publication Date Title
US7177991B2 (en) Installation method of new storage system into a computer system
JP4568574B2 (en) Storage device introduction method, program, and management computer
US8937965B2 (en) Storage system comprising function for migrating virtual communication port added to physical communication port
JP4188602B2 (en) Cluster type disk control apparatus and control method thereof
US7519696B2 (en) Method and apparatus for dynamically modifying a computer system configuration
US7711896B2 (en) Storage system that is connected to external storage
US8694749B2 (en) Control method of device in storage system for virtualization
US8103826B2 (en) Volume management for network-type storage devices
US8161262B2 (en) Storage area dynamic assignment method
US7802251B2 (en) System for resource allocation to an active virtual machine using switch and controller to associate resource groups
JP3837953B2 (en) Computer system
US20080184000A1 (en) Storage module and capacity pool free capacity adjustment method
US8301812B1 (en) Techniques for performing host path detection verification
US20120311256A1 (en) Computer system for controlling allocation of physical links and method thereof
US20030236884A1 (en) Computer system and a method for storage area allocation
US20070079098A1 (en) Automatic allocation of volumes in storage area networks
US7139871B2 (en) Method of managing storage system to be managed by multiple managers
JP4643456B2 (en) How to set up access
US6842810B1 (en) Restricted access devices
US20190149423A1 (en) Storage apparatus, storage system, and storage apparatus management method

Legal Events

Date Code Title Description
STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION