JP2004355638A - Computer system and device assigning method therefor - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To dynamically set devices and assign them to computers so as to make it possible for a plurality of computers to utilize devices fit for uses when necessary. <P>SOLUTION: A storage subsystem 2 has a plurality of devices having various configurations and capacities and are connected to a plurality of computers 1. A management computer 3 stores/manages the connection relation between computers 1 and the storage device subsystem 2 and manages devices while communicating with volume managers 11 of computers 1. Computers 1 inform an administrative manager 31 of information such as the number of devices, capacities, and types when newly requesting devices. The administrative manager 31 select devices meeting the request and indicates setting to the storage device subsystem so that computers 1 can utilize the devices. Thereafter, the administrative manager 31 informs computers 1 of information required for access to the new devices, and volume managers 11 change setting of computers 1 in accordance with this information. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates to a computer system and a method of allocating storage devices to computers in the computer system, and more particularly, to a method of allocating storage devices to computers in a computer system having a storage subsystem shared by a plurality of computers. On how to do.

  2. Description of the Related Art In recent years, the amount of information handled by computer systems used in companies and the like has dramatically increased, and accordingly, the capacity of disk devices and the like for storing data has been steadily increasing. For example, in magnetic disk devices, devices having a capacity of several TB (terabytes) are not uncommon. Regarding such a disk device, for example, Patent Literature 1 discloses a technology in which one storage subsystem is constituted by a plurality of types of logical disk devices (hereinafter, also referred to as devices). Specifically, as devices (logical disks) accessed from the host computer, devices having different RAID levels, such as RAID5 and RAID1 in RAID (Redundant Arrays of Inexpensive Disks), are mixed, or logical disks are configured. For this purpose, a disk subsystem in which devices having different access speeds are mixed is disclosed as an actual magnetic disk device (physical disk device). The user can use different devices according to the access frequency of each device.

  On the other hand, with the emergence of Fiber Channel technology as an interface between a host computer and peripheral devices such as disk devices, a computer system is configured by connecting a plurality of host computers and a plurality of storage devices with one Fiber Channel cable. Is also being done. In such a computer system, each host computer can directly access any storage device on the Fiber Channel. For this reason, data sharing between the host computers and reduction of the network load can be expected as compared with the conventional case where each host computer has its own storage device.

JP-A-9-274544

  According to the above-described related art, the number and types of devices that can be accessed by each host computer can be dramatically increased. However, as the number and types of devices accessible by the host computers increase, it becomes more difficult for each host computer to manage the devices. While one host computer has the advantage of being able to access many devices, it is difficult for the user to select which device to use for a certain task. In particular, in the case of a computer system connected by a fiber channel, a certain host computer can access a device that the host computer does not use. For this reason, unauthorized access to a device used by another host computer may occur, and data may be destroyed.

  In order to solve such a problem, Japanese Patent Application Laid-Open No. H10-333839 discloses a method in which a storage device connected by a fiber channel is permitted to access only from a specific host computer. However, when there are a plurality of storage devices and devices, or when different types of devices are mixed, the processing is still complicated, and each host computer always considers the device type etc. There is a need to.

  An object of the present invention is to facilitate device setting and device assignment to each host computer so that each host computer can use a device suitable for the application when necessary. .

  In a preferred embodiment, a computer system according to the present invention includes a plurality of computers and a storage subsystem connected to the plurality of computers. The storage subsystem has a plurality of storage devices and a plurality of interfaces, and is connected to each computer. One of the plurality of computers has a storage device in the storage subsystem and management means for holding information on the connection relationship between each computer and the storage subsystem. When a new device is needed, each computer notifies the management means of its capacity and type. The management unit receives the notification and selects a storage device that meets the request. Then, it instructs the storage subsystem to set predetermined information so that the selected device can be accessed from the computer. The management unit also returns predetermined information to the computer that has requested the device allocation, and the requested computer changes the setting of the computer based on the information. Make it available.

  In another aspect of the present invention, a plurality of computers and a plurality of storage subsystems are connected via a network. An arbitrary computer is provided with a storage device that each storage subsystem has and a management unit that holds information on a connection relationship between each computer and the storage subsystem. Each storage subsystem has control means for permitting access to the computer designated by the management means. When each computer needs a new storage device, it notifies the management means of its capacity and type. The management unit selects a device that meets the request in response to the notification, and permits the storage subsystem to access the storage device subsystem so that the selected device can be accessed from a computer that requires a new storage device. Instruct The management means also returns predetermined information to the computer which has requested the device allocation. The computer that has requested the device assignment changes the setting of the computer based on the information returned from the management means, so that the device assigned by the computer can be used.

  According to the present invention, storage devices can be dynamically allocated to host computers as needed.

  FIG. 1 is a simplified block diagram showing a configuration example in one embodiment of a computer system to which the present invention is applied.

  The computer system includes a plurality of host computers, host computers 1a, host computers 1b,... Host computers 1n (collectively called hosts 1), storage subsystems 2 connected to the hosts 1, management host computers 3, and networks. 4 and a secondary storage device 5 which is a storage device arranged at a remote place.

  The host computers 1a, 1b,... Are computers having a CPU, a memory, and the like, and achieve predetermined functions by the CPU reading and executing an operating system and application programs stored in the memory.

  The storage subsystem 2 has a plurality of disk units 21, a disk controller 22, a plurality of ports 23 connected to the host computer 1, an interface 24 connected to the secondary storage device 5, and a network interface 25 connected to the network 4. are doing. The storage subsystem 2 according to the present embodiment collectively simulates the plurality of disk units 21 as one or a plurality of logical devices to the host computer 1. Of course, the individual disk units 21 may be shown to the host computer 1 as one logical device.

  As the port 23, for example, if the connected host computer 1 is a so-called open system computer, an interface such as SCSI (Small Computer System Interface) is used. On the other hand, if the host computer 1 is a so-called mainframe, a channel interface such as ESCON (Enterprise System Connection) is used. The ports 23 may have the same interface or different ports. In the present embodiment, a description will be given assuming that SCSI is used as an interface for all the ports 23.

  The disk controller 22 has a processor 221, a cache memory 222, and a control memory 223. The processor 221 controls access from the host computer 1 and control of the disk unit 21. The processor 221 is particularly useful when the storage subsystem 2 is not a single disk unit 21 with respect to the host computer 1 but a plurality of disk units, such as a disk array, appearing as one or a plurality of logical devices. , Processing and management. The disk controller 22 communicates with the management host computer 3 via the network interface 25.

  The cache memory 222 stores frequently read data or temporarily stores write data from the host computer 1 in order to increase the access processing speed from the host computer 1. A part of the cache memory 222 can be made to look like one or more logical disks and used as a device that does not need to access the magnetic disk unit.

  The control memory 223 stores a program executed by the processor 221 and is used to store information for managing the disk unit 21 and a logical device configured by combining a plurality of disk units 21. .

  Software (a program) called a volume manager 11 is arranged in each of the host computers 1a, 1b,... The volume manager 11 operates by communicating with a management manager 31 arranged in the management host computer 3. Each host computer 1 has an interface (I / F) 12, and is connected to the port 23 of the storage subsystem 2 by the interface 12.

  Next, a management form of the logical device in the storage subsystem 2 will be described.

  As described above, the storage subsystem 2 presents the host computer 1 with the plurality of disk units 21 as one or a plurality of logical devices, or each disk unit 21 as one logical device. The storage subsystem 2 also causes the host computer 1 to show a partial area of the cache memory 222 as one or a plurality of logical devices. There is no correlation between the number of disk units 21 in the storage subsystem 2 and the number of logical devices.

  FIG. 2 is a table configuration diagram showing an example of a logical device management table holding information used by the storage subsystem 2 to manage logical devices.

  The logical device management table holds a set of items of size 62, configuration 63, state 64, path 65, target ID 66, and LUN 67 for the logical device number 61. In the size 62, information indicating the capacity of the logical device specified by the logical device number 61 is set.

  The configuration 63 includes information indicating the configuration of the logical device, for example, a RAID (Redundant Arrays of Inexpensive Disks) configured by the disk unit 21 and, when it is assigned to the logical device, a RAID type such as RAID 1 or RAID 5. Is set. If a partial area of the cache memory 222 is allocated as the logical device, information indicating “cache” is set in the configuration 63, and if a single disk unit is allocated, information indicating “single disk unit” is set in the configuration 63. Is done.

  In the state 64, information indicating the state of the logical device is set. The states include “online”, “offline”, “not implemented”, and “failure offline”. “Online” indicates that the relevant logical device operates normally and is accessible from the host computer 1. “Offline” indicates that the logical device is defined and is operating normally, but cannot be accessed from the host computer 1. This state corresponds to a case where the device was previously used by the host computer 1 but the host computer 1 no longer uses the device and is no longer used. “Not implemented” indicates that the logical device is not defined and cannot be accessed from the host. "Failure offline" indicates that a failure has occurred in the logical device and access from the host is not possible.

  In the path 65, information indicating which of the plurality of ports 23 the logical device is connected to is set. Each port 23 is assigned a unique number in the storage subsystem 2, and the “path” column records the number of the port 23 to which the logical device is connected. The target ID 66 and LUN 67 are identifiers for identifying a logical device. Here, as these identifiers, SCSI-ID and LUN used when accessing the device from the host computer 1 on SCSI are used.

  One logical device can be connected to a plurality of ports, and the same logical device can be accessed from a plurality of host computers 1. In this case, a plurality of entries relating to the logical device are created in the logical device management table. For example, in the logical device management table shown in FIG. 2, the device of the logical device number 2 is connected to two ports 23 of port numbers 0 and 1. For this reason, there are two logical device number 2 items. When one logical device can be accessed from the plurality of ports 23 in this way, the target ID and LUN corresponding to each path 65 need not be the same, and may be different as shown in FIG. good.

  The information held in the logical device management table is sent to the management host computer 3 via the network interface 24 at an appropriate timing or when the configuration of the storage subsystem 2 changes due to a failure or the like. . Therefore, the management host computer 3 also holds the same logical device management table as the table shown in FIG.

  FIG. 3 is a table configuration diagram showing an example of a host management table held by the management manager 31 of the management host computer 3.

  The host management table stores management information composed of a set of a host name 71, a port number 72, an interface number 73, and a logical device number 74 in order for the management host computer 3 to manage the assignment of devices to each host computer 1. Hold.

  The port number 72 and the logical device number 74 are numbers defined inside the storage subsystem 2 and are information for identifying each port 23 and the logical device of the storage subsystem 2. The port number 72 and the logical device number 74 include the port number of the port to which the host computer 1 identified by the identifier set in the host name 71 is connected, and the device number of the logical device assigned to the host computer. Is set.

  The interface number 73 is a number assigned to manage the interface 12 of each host computer 1. The interface number 73 is required particularly when one host computer 1 has a plurality of interfaces 12. The set of the port number 72 and the interface number 73 is an important element for indicating the connection relationship between the host computer 1 and the logical device. For example, the host computer 1 b shown in FIG. 1 includes two interfaces 12, each of which is connected to a different port 23. In such a case, even if the interface becomes unavailable due to a failure of one interface or a line connecting the one interface and the storage subsystem 2, if the other interface is connected to the logical device, the processing is continued. And reliability can be improved.

  The management host computer 3 refers to the host management table and the logical device management table sent from the storage subsystem 2 to allocate a logical device to each host computer 1. Hereinafter, the device assignment processing will be described.

  FIG. 4 is a flowchart illustrating a flow of processing performed by the volume manager 11 of each host computer 1. This process is performed when a user using the host computer 1 or an application program running on the host computer 1 needs a new device.

  In step 1001, the volume manager 11 obtains information on the number of required devices and device types from a user or an application program. A user or an application program specifies information such as a capacity, a performance condition, and a reliability level as information on a device. The device capacity refers to the size of the device described above. As the performance condition, for example, information on performance such as a device access speed such as a low-speed disk drive, a high-speed disk drive, and a cache-resident disk drive is specified. As the reliability level, for example, information on the reliability of the device such as RAID0, RAID1, RAID5, dual path, and remote mirror is specified. In the dual path, when the host computer 1 has a plurality of interfaces, a plurality of paths are provided so that the same device can be accessed using the plurality of interfaces. With a dual path, if one path becomes unavailable, the device can be accessed using another path. The remote mirror causes the secondary storage device 5 to have a copy of the device in the storage device subsystem 2. Even when the storage device subsystem 2 itself becomes inoperable due to an earthquake, a fire, or the like, the remote mirror is used. Since data is held in the device 5, reliability can be improved.

  Next, in step 1002, the volume manager 11 searches for a pair of a target ID and LUN that are not used on the interface 12 of the host computer 1.

  In step 1003, the volume manager 11 sends the set of the capacity, performance condition, and reliability level specified in step 1001 and the unused target ID and LUN searched in step 1002 to the management manager 31 of the management host computer 3. Send and request allocation of new device. The management manager 31 searches for a device to be assigned based on the received information, and returns information specifying a host interface number, a target ID, and a LUN used for accessing the device. The processing of the management manager 31 performed here will be described later.

  In step 1004, the volume manager 11 receives information from the management manager 13. In step 1005, the setting of the host computer 1 is changed based on the information received from the management manager 13 so that a new device can be used.

  In the case of a so-called open operating system, a device file is prepared for each device in order for the host computer 1 to access each device, and access to the device file is performed. Usually, the device file is prepared when the device configuration processing of the host computer 1 is performed, and no device file is created for a device that does not exist at the time of the device configuration processing. Thus, in step 1004, a device file for the newly assigned device is created. Specifically, for example, in the Solaris operating system of Sun Microsystems, a new device is recognized and a device file is created by a “drvconfig” command or a “drives” command, and newly assigned from the host computer 1. Access to the device.

  Finally, in step 1006, the volume manager 11 notifies the user or the application program of the information of the assigned device file name, target ID, and LUN, and ends the processing.

  FIG. 5 is a flowchart showing the flow of processing by the management manager 31 of the management host computer 3 when a new device is allocated.

  Upon receiving the information such as the device size, performance condition, and reliability level sent from the host computer 1 in step 1101, the management manager 31 is set in the logical device management table and the host management table held therein. Refer to the information and search for a device that meets the request. Here, the device to be searched is a device for which “Offline” is set in the state 64 of the logical device management table (step 1102). The management manager 31 determines whether a device in the “offline” state that matches the request is found as a result of the search (step 1103).

  When a device in the “offline” state that matches the request is found, the management manager 31 determines based on the information of the target ID and LUN received from the host computer 1 and the information set in the logical device management table and the host management table. Then, a port number, a target ID, and a LUN used to connect the device to the host computer 1 are determined (step 1104).

  Next, the management manager 31 sets the device of the logical device number found in step 1103 to be accessible by the port number, the target ID, and the LUN determined in step 1104, and brings the device into the online state. To instruct. The storage subsystem 2 performs the setting according to the instruction from the management manager 31, and returns the result to the management manager 31 (step 1105).

  When receiving the result from the storage subsystem 2 (step 1106), the management manager 31 returns the interface number, the target ID, and the LUN to the volume manager 11 of the host computer 1 that has requested (step 1107).

  On the other hand, if there is no device that meets the request in the “offline” state in step 1103, the management manager 31 searches for a logical device number whose status 64 in the logical device management table is “not implemented”. (Step 1108). If there is a “not implemented” logical device number, the management manager 31 notifies the storage subsystem 2 of information such as the device size, performance condition, and reliability level requested by the host computer 1. Request a device build. The storage subsystem 2 constructs a device having the device number in accordance with the request from the management manager 31, and returns the result to the management manager 31 (step 1109). Upon receiving the result, the management manager 31 performs the above-described processing after step 1104 (step 1110).

  FIG. 6 is a flowchart showing the flow of processing performed by the volume manager 11 in the processing of returning a device that is no longer needed by the host computer 1.

  In the device return process, the volume manager 11 first receives information on unnecessary devices, for example, device file names from the user or the upper application program (step 1201). The volume manager 11 acquires an interface number, a target ID, and a LUN associated with the device to be returned, based on the received information (step 1202).

  Next, the volume manager 11 changes the setting of the host computer 1 as necessary in order to prevent the host computer 1 from using the device. Here, specifically, processing such as deletion of a device file is performed (step 1203). Subsequently, the volume manager 11 notifies the management manager 31 of the interface number, target ID, and LUN acquired in step 1202, and ends the processing (step 1204).

  FIG. 7 is a flowchart showing the flow of the process performed by the management manager 31 in the process of returning a device that has become unnecessary in the host computer 1.

  The management manager 31 receives an interface number, a target ID, and a LUN from the host computer 1 (step 1301). The management manager 31 instructs the storage subsystem 2 to take the device to be returned offline, based on the received interface number, target ID, and LUN. In response to this instruction, the storage subsystem 2 takes the specified device offline and returns a logical device management table reflecting the result to the management manager 31 (Step 1302). When the logical device management table is received from the storage subsystem 2, it is retained and the processing is completed (step 1303).

  In the first embodiment described above, the management host computer is provided and the management manager is arranged therein, but the function of the management manager does not necessarily need to exist in the management host computer. For example, it is also possible to configure so as to exist in any of the host computers 1a, 1b,. Also, the function of the management manager can be provided in the storage subsystem. In this case, each of the host computers 1a, 1b,... May transmit a request and receive information directly with the storage subsystem via the interface.

  FIG. 8 is a simplified block diagram illustrating a configuration of a computer system according to the second embodiment of this invention.

  The computer system according to the present embodiment includes a plurality of host computers 1 (host computer 1a, host computer 1b,..., Host computer 1n), a plurality of storage subsystems 2a, 2b,. It comprises a network 4 and a fiber channel switch 6.

  The host computer 1 has a volume manager 11 as in the first embodiment. The volume manager 11 operates by communicating with a management manager 31 provided in the management host computer 3. Further, the host computer 1 has an interface (I / F) 12, and is connected to the fiber channel switch 8 by the interface 12.

  Each of the storage subsystems 2a, 2b,..., 2m is, like the storage subsystem 2 in the first embodiment, a disk unit 21, a disk controller 22, a port 23, and a network interface (network I) connected to a network. / F) 25. As in the first embodiment, there may be a plurality of disk units 21 and ports 23, but here, for simplicity of description, the description will be made assuming that there is one disk unit and one port.

The fiber channel switch 8 has a plurality of ports 81. To each port 81, one of the interface 12 of the host computers 1a, 1b,... And the port 23 of the storage subsystems 2a, 2b,. The fiber channel switch 8 has a network interface 82, and is also connected to the network 4. The fiber channel switch 8 is used for enabling the host computers 1a, 1b,... To freely access the storage subsystems 2a, 2b,. In this configuration, basically all the host computers 1 can access all the storage subsystems 2.
The management host computer 3 has a management manager 31 as in the first embodiment. The management manager 31 operates by communicating with the volume manager 11 of each of the host computers 1a, 1b,.

  FIG. 9 is a table configuration diagram showing an example of a logical device management table held by the management host computer 3. The logical device management table according to the present embodiment is used to manage the same information as the logical device management table held by the storage subsystem 2 in the first embodiment. Hereinafter, differences from the logical device management table according to the first embodiment will be mainly described.

  In the present embodiment, the management host computer 3 assigns a unique number to all the devices of all the storage subsystems 2 and manages them. For the purpose of this management, the logical device management table has, for each device, its size 103, configuration 104, state 105, LUN 106, WWN (World Wide Name) 102, and connection host name 107 as information.

  The size 103, configuration 104, status 105, and LUN 106 are the same as the information held by the logical device management table in the first embodiment. The WWN 102 is information set in the port 23 of the storage subsystem 2 and is information uniquely assigned to each fiber channel interface to identify each port. The WWN 107 is also called N_PORT_NAME. The connection host name 107 is a host name for identifying a host computer permitted to connect to the device.

  Basically, if a plurality of host computers 1 connected to the fiber channel switch 8 can freely access an arbitrary storage subsystem 2, a system security problem may occur. In order to solve such a problem related to the security of the system, for example, Japanese Patent Application Laid-Open No. 10-333839 discloses that only a specific host computer is allowed to access a storage device connected by a fiber channel. The technology which makes it possible is disclosed. Also in the present embodiment, in order to maintain the security of the system, the storage subsystem 2 has means for maintaining the security as disclosed in Japanese Patent Laid-Open No. 10-333839. I do. However, this is not directly related to the essence of the present invention, and the detailed description is omitted here.

  In the present embodiment, the WWN 107 is also provided to the interface 12 of each host computer 1. The management host computer 3 manages a set of the host name 108 and the WWN 109 based on the table shown in FIG.

  Hereinafter, the operations of the volume manager 11 and the management manager 31 will be described.

  In the present embodiment, the processing performed by the volume manager 11 when allocating a new device to the host computer is basically performed in the same manner as the processing in the first embodiment shown in FIG. That is, upon receiving information on the number and types of devices required from the user or the application program, the volume manager 11 requests the management manager 31 to allocate a new device based on the information. When the management manager 31 completes the assignment of a new device, the volume manager 11 changes the setting of the device so that the new device can be used from the host computer 1.

  FIG. 11 shows a flowchart of a process performed by the management manager 31 when a new device is allocated in the present embodiment.

  Similarly, the processing performed by the management manager 31 is performed in substantially the same manner as the processing performed by the management manager in the first embodiment illustrated in FIG. Note that, in FIG. 11, the same reference numerals as in FIG. 5 are used for portions where the same processing as that shown in FIG. 5 is performed. In the following, a description will be given mainly of a portion where processing different from that in FIG. 5 is performed, and description of a portion where the same processing as in FIG. 5 is performed will be omitted.

  In the present embodiment, in the initial state, the storage subsystem 2 prohibits access from all host computers 1 to prevent devices from being inadvertently accessed from unassigned host computers. I have. Therefore, when instructing the storage subsystem 2 to bring the device online in step 1105, the management manager 31 also permits the storage subsystem 2 to access the newly allocated device from the host computer 1. To instruct.

  In this instruction, the management manager 31 notifies the storage subsystem 2 of the WWN of the host computer 1 to be permitted to access the device. When the host computer 1 accesses the device, the storage subsystem 2 determines whether or not the access is possible based on the WWN received from the management manager 31 (step 2105).

  Subsequent to the process of step 2105, the management manager 31 changes the setting of the fiber channel switch 8. For example, as shown in FIG. 12, it is assumed that the host computers A and B access the disk units (devices) a and b, but the host computer C accesses only the disk units (devices) c. In this case, the management manager 31 sets a route setting to the fiber channel switch 8 so that the port c connected to the host computer C cannot access the ports (port d and port e) connected to the disk units a and b. Do it. This makes it possible for two switches to exist. Performing such a route setting is called zoning. By performing zoning, it is possible to prevent a certain device from being accessed from a host computer to which access is not originally permitted. In addition, since the data flow is separated, the performance can be improved (step 2106).

  After the above processing, the management manager 31 performs the processing of steps 1106 and 1107.

  FIG. 13 is a simplified block diagram showing a configuration example in a third embodiment of a computer system to which the present invention has been applied.

  In the computer system of this embodiment, a plurality of host computers 1a ', host computers 1b',..., Host computers 1n '(collectively called hosts 1') are connected via a network interface (I / F) 12 'and a network 4. Connected to the file server 9. The file server 9 is connected to the storage subsystem 2 via an interface (I / F) 92. The storage subsystem 2 and the secondary storage 5 which is a storage located at a remote location are the same as those in the first embodiment.

  The file server 9 includes a network interface 91 connected to each host computer 1 ′, a plurality of interfaces 32 connected to the storage subsystem 2, a management manager 93, and a server program 94.

  The management manager 93, like the management manager 31 in the first embodiment, performs device assignment and the like according to a request. The server program 94 is a file server program such as NFS (Network File System) that provides file access via a network. The server program 94 provides a means for accessing the file system created in the storage subsystem 2 by the file server 9 from the host computer 1 '.

  The storage subsystem 2 and the file server 9 may be configured as a so-called NAS (Network Attached Storage) in which they appear as one storage device from each host computer 1 '.

  The client program 11 ′ of the host computer 1 ′ communicates with the server program 94 on the file server 9, and a file system created on the storage subsystem 2 by the file server 9 from an application program running on the host 1 ′. Is a program that allows you to use The client program 11 'may be incorporated in an operating system (not shown) on the host 1' depending on the system configuration. The client program 11 'requests the management manager 93 to create a new file system or change the size of an existing file system.

  In order to make it possible to change the size of an existing file system while the host computer 1 is operating, the storage subsystem of the present embodiment transfers data existing in a certain logical device to the physical device on which the logical device is formed. It has a function to move to another physical disk unit. As a specific technical means for realizing such a function, for example, a known technique disclosed in Japanese Patent Application Laid-Open No. 9-274544 can be applied. Therefore, the detailed description is omitted in this specification.

  FIG. 14 is a flowchart showing a flow of processing performed when the client program 11 'of the host computer 1' newly constructs a file system.

  This process is performed when a user using the host computer 1 'or an application program running on the host computer 1' needs a new file area.

  The client program 11 'receives designation of information on a device required in response to a request from a user or an application program. The information acquired here includes information such as required device capacity, performance conditions, and reliability level, as in step 1001 in the first embodiment shown in FIG. 4 (step 2001).

  Next, the client program 11 'transmits information such as the capacity, performance condition, and reliability level designated in step 2001 to the management manager 93, and requests a new file system area. Based on the information received from the client program 11 ', the management manager 93 retrieves and prepares an area of a device that can be allocated, and returns the result to the client program 11'. The processing performed by the management manager 93 at this time will be described later (step 2002).

  The client program 11 'receives a response from the management manager 93 to a request for a new area. The response received at this time includes the mount point, for example, in the case of NFS, the host name of the file server, or the host IP address and the directory name (step 2003). The client program 11 'mounts the file system based on the information received by the management manager 93 (Step 2004). Finally, the client program 11 'notifies the user or the application program of the allocated mount point, and ends the processing (Step 2005).

  FIG. 15 is a flowchart showing the flow of processing performed by the management manager 93 in response to a request for a new area from the client program 11 '.

  This process is basically performed in the same manner as the process of the management manager 31 in the first embodiment shown in FIG. However, the processing in step 1107 in FIG. 5 is changed to the processing in steps 2107, 2111, and 2112.

  In step 1107 of FIG. 5, information such as a target ID is passed to the host computer that has made the request. In the present embodiment, such information is processed. For this purpose, the management manager 93 passes information about the device such as the target ID to the server program 94 (step 2107), and receives mount point information from the server program 94 (step 2111). Then, the information of the mount point received from the server program 94 is passed to the client program 11 'which has made the request, and the process ends (step 2112).

  FIG. 16 is a flowchart illustrating a flow of a process performed by a server program that has received information about a device from the management manager.

  When information about the device is passed from the management manager 93 (step 2201), the server program 94 performs device reconfiguration of the file server 9. This process is specifically the same as the process of step 1005 in the first embodiment shown in FIG. 4 (step 2202).

  Subsequently, the server program 94 creates a file system in the newly created device (step 2203), and returns information indicating the mount point of the file system to the management manager 93 (step 2204).

  With the above processing, a new file system usable from the host computer 1 'can be added.

  FIG. 17 is a flowchart showing the flow of processing performed by the management manager 93 when changing the size of an existing file system. The processing at the time of requesting a new file system shown in FIG. 15 is different in the following points.

  When attempting to change the size of an existing file system, the user or application program informs the client program 11 'about the mount point of the file system whose size is to be changed, the size of the file system to be expanded or reduced, and the like. Issues a request with information. The client program 11 'requests the management manager 93 to change the size of the file system using information specified by the user or the application program. The management manager 93 receives information such as the mount point of the file system to be processed and the size to be extended, which are sent from the client program 11 '(step 2301).

  The management manager 93 determines the logical device by obtaining information such as the target ID and LUN of the logical device storing the file system to be processed based on the mount point received from the client program 11 '. . Then, the management manager 93 obtains information on the type of the logical device, that is, reliability, performance, and the like (step 2302). Subsequently, based on the information obtained in steps 2301 and 2302, the management manager 93 has a free area of the size of the changed file system in the same manner as when a new file system is added. The same type of logical device is secured (steps 1102 to 1110).

  Thereafter, in step 2304, the management manager 93 instructs the storage subsystem 2 to move data from the logical device in which the file system has been recorded to the newly secured logical device. Movement of data is performed transparently from the file server program 94. Since the host computer 1 'accesses the storage subsystem 2 via the file server program 94, this processing is transparent to the host computer 1'. Therefore, it is not necessary for the host computer 1 'to stop processing during data movement.

  When the data transfer is completed, the management manager 93 instructs the server program 94 to extend the file system. Even if the actual device capacity increases, unless the file system is rebuilt, the file system cannot use all of the expanded capacity. After instructing the server program 94 to extend the file system, the management manager 93 notifies the client program 11 'of the completion of the processing and ends the processing (step 2305).

  Through the above processing, the size of the existing file system can be changed while the host computer 1 'is operating. When changing the size of the existing file system, the client program 11 'can use the expanded file system as it is after receiving the notification from the management manager. Therefore, in this case, it is not necessary to perform the processing of steps 2004 and 2005 in FIG.

  FIG. 18 is a simplified block diagram showing a configuration example of a computer system according to a fourth embodiment of the present invention.

  The computer system according to the present embodiment includes a plurality of host computers 1 ″ (host computers 1a ″, 1b ″,..., 1n ″), a management host computer 3, a storage subsystem 2 ′, and a secondary storage device 5. are doing. Each host computer 1 "and the storage subsystem 2 'are connected via a fiber channel switch 8. The host computer 1", the storage subsystem 2' and the fiber channel switch 8 are connected via a network 4. Interconnected.

  The fiber channel switch 8 has a plurality of ports 81, switches connections between these ports, and realizes data transfer between devices connected to the ports 81. The fiber channel switch 8 further includes a network interface 82 for performing communication via the network 4. Each of the host computers 1 "includes a volume manager 11" and one or a plurality of interfaces 12. The interface 12 of the host computer 1 ″ is connected to one of a plurality of ports 81 of the fiber channel 8.

  The storage subsystem 2 ′ has a plurality of clusters 26 and an inter-controller connection mechanism 27 that connects the clusters 26 to each other. Each cluster 26 includes a channel processor 23 ', a drive processor 22', and a plurality of disk units 21. The channel processor 23 'and the drive processor 22' in the same cluster are connected by a bus 28 which is faster than the inter-controller connection mechanism 27. Each channel processor 23 'has one or a plurality of ports 231 and is connected to the host computer 1 "via the secondary storage device 5 or the fiber channel 8. A plurality of disks are connected to the drive processor 22'. In this embodiment, one or a plurality of logical devices are configured by combining the plurality of disk units 21, or one or a plurality of logical devices are configured by one disk unit 21. It is assumed that it is not possible to combine the disk units 21 included in a plurality of clusters 26 when configuring one logical device.

  The channel processor 23 'shows one or a plurality of logical devices to each host computer 1 "and accepts access from each host 1". In principle, the channel processor 23 'manages a logical device configured by the disk unit 21 connected to the drive processor 22' in the cluster 26 to which the channel processor 23 'belongs. This is because the communication between the channel processor 23 'and the drive processor 22' in the same cluster 26 can be performed at a higher speed than the communication across the clusters. However, when the channel processor 23 'of a certain cluster 26 does not operate due to a failure or the like, the channel processor 23' of another cluster 26 takes over the processing. The channel processor 23 'determines from the host computer 1 "the logical device designated by the disk unit 21 connected to which drive processor 22', and passes the processing request to the appropriate drive processor 22 '. 22 'interprets the request from the channel processor 23', generates a disk access request for each disk unit 21 in which the logical device is placed, and sends the disk access request to the corresponding disk unit 21.

  The host computer 1 "has substantially the same configuration as the host computer 1 in the first embodiment, but there is a slight difference in the function of the volume manager 11" operating thereon. The volume manager 11 ″ has a function of grouping a plurality of logical devices and presenting them as another logical device to a higher-level application program in addition to the logical device assignment and return processing performed by the volume manager 11 in the first embodiment. Hereinafter, the logical device created by the volume manager 11 ″ is referred to as LVOL to distinguish it from the logical device managed by the storage subsystem 2 ′. The volume manager 11 ″ apparently combines a plurality of logical devices to form one larger LVOL, or divides one logical device into a plurality of areas, and uses those areas as LVOLs on the host computer 1 ″. Application programs. In addition, a new logical device can be connected to an existing LVOL to expand the capacity of the LVOL.

  19 is a flowchart showing the flow of processing performed by the volume management 11 ″ when newly allocating a volume in the present embodiment. The processing described here is the same as that in the first embodiment shown in FIG. Step 1002 of the device allocation processing is replaced with step 1002 ', and step 1006 is replaced with steps 1005' and 1006 '. In the other steps, the same processing as the corresponding step in FIG. Hereinafter, the processing performed in steps 1002 ', 1005', and 1006 'will be described.

  In step 1002 ', an unused WWN / LUN pair is retrieved from the LVOL management table managed by the volume manager 11 ". An example of the LVOL management table is shown in Fig. 20. The LVOL management table contains the LVOL name 151. , Device file name 152, size 153, and a set of WWN 154 and LUN 155 of each device are registered.The LVOL name 151 is assigned to identify the LVOL provided to the application program by the volume manager 11 ″. Is the identifier to be used. The device file name 152 is the name of a logical device constituting the LVOL. The volume manager 11 ″ manages the logical devices belonging to each LVOL based on the device file name. The size 153 indicates the capacity of each logical device constituting the LVOL. One LVOL is composed of a plurality of logical devices. In some cases, a plurality of device files may belong to one LVOL name.

  In step 1005 ', the volume manager 11 "creates a new LVOL using the logical device assigned by the management manager 31, and registers the contents in the LVOL management table. In step 1006', the assigned LVOL name Is notified to the user, and the process ends.

  FIG. 21 is a flowchart showing the processing of the volume manager when expanding the capacity of the LVOL in response to a request from a user or an application program.

  When expanding the capacity of the LVOL, a new logical device is prepared, and a new LVOL is constructed by combining the logical device with the logical device constituting the LVOL to expand the logical device. At this time, the newly prepared logical device is usually the same type of logical device as the logical device constructing the LVOL to be expanded. In this embodiment, the volume manager 11 ″ determines the type of the logical device constituting the LVOL to be expanded, and secures the same type of logical device.

  In this process, the volume manager 11 ″ first receives information on the LVOL name of the LVOL to be expanded and the capacity to be expanded from the user or the application program (step 2501). An inquiry is made to the management manager 31 about the type of the logical device constituting the target LVOL (step 2502). The volume manager 11 ″ searches the LVOL management table for a set of unused WWNs and LUNs (step 2503). The volume manager 11 ″ determines the type of the logical device acquired in steps 2502 and 2503, and the unused WWN. The information including the combination of LUNs is transmitted to the management manager 31. (Step 2504). Upon receiving the information about the newly allocated logical device from the management manager 31 (step 2505), the volume manager 11 ″ reconfigures the host computer 1 ″ and replaces the newly allocated logical device with the host computer 1. (Step 2506). Finally, the volume manager 11 "extends the LVOL capacity by adding a newly allocated logical device to the LVOL to be expanded, and ends the process (Step 2506). 2507).

  In step 1003 of FIG. 19 and step 2504 of FIG. 21, when there is a request for allocation of a new logical volume from the volume manager 11 ″, the management manager 31 in any case, the type of device requested by the volume manager 11 ″, Find and allocate devices that match capacity. For this processing, the management manager 31 includes a cluster information table in which information on the cluster 26 in the storage subsystem 2 'is set in addition to the logical device management table as shown in FIG.

  FIG. 22 is a table configuration diagram illustrating an example of the cluster information management table.

  The cluster information management table has an entry corresponding to each cluster 26, and for each cluster 26, a cluster number 161 for identifying the cluster, a port number 162 of a port of the cluster, and a WWN 163 assigned to the port are set. ing. As shown in the figure, when a plurality of ports exist in one cluster 26, each port number and WWN are set in an entry corresponding to the cluster. As described above, when a logical device is constructed in the disk unit 21 connected to a certain drive processor 22 ', the logical device can be made accessible from the port 231 in the same cluster. It is desirable from the viewpoint of performance. The management manager 31 sets the port 231 used for access from the host computer 1 ″ based on the cluster information table and the drive processor 22 ′ to which the disk unit 21 on which the logical device to be newly allocated is constructed, in the same cluster. Configure the device settings.

  FIG. 23 is a flowchart showing a flow of device assignment processing by the management manager 31.

  The device allocation processing according to the present embodiment is performed in substantially the same manner as the processing according to the second embodiment shown in FIG. 11, but part of the processing is performed according to the second embodiment due to the difference in the configuration of the storage subsystem. And different. Specifically, in step 1109, when the management manager 31 requests the storage subsystem 2 'to newly construct a device, the storage subsystem 2' constructs a device according to the request. When a logical device is constructed in the storage subsystem 2 ', the management manager 31 receives information indicating which cluster 26 the logical device has been constructed with respect to the newly constructed logical device (step 2610).

  The management manager 31 refers to the information on the logical device received from the storage subsystem 2 'and the cluster information management table to determine from which port the device can be accessed. The management manager 31 further determines the LUN of the device to be newly assigned based on the information on the unused LUN (step 2604). Finally, the management manager 31 sends information such as WWN and LUN necessary for accessing the newly allocated logical volume to the volume manager 11 ″, and ends the processing (step 2607).

  Processes other than those described here are the same as those of the management manager in the second embodiment shown in FIG. 11, and the same reference numerals as those in FIG. 11 are used in the figure, and detailed description is omitted.

  According to the embodiment described above, it is possible to allocate a device according to a request even when the host computer is operating. Further, even in an environment where a plurality of devices are mixed and configured by a Fiber Channel switch, it is possible to easily allocate a device that meets the demand to the host computer.

It is needless to say that the present invention is not limited to the above-described embodiment, but can take various forms within the scope of the present invention.

FIG. 1 is a block diagram illustrating a configuration example of a computer system according to a first embodiment of the present invention. FIG. 3 is a table configuration diagram illustrating an example of a logical device management table held by a storage subsystem. FIG. 3 is a table configuration diagram illustrating an example of a host management table held by a management manager. 6 is a flowchart illustrating a flow of processing performed by a volume manager of the host computer. It is a flowchart which shows the flow of the process implemented by a management manager. 10 is a flowchart illustrating a flow of a process performed by a volume manager in a device return process. It is a flowchart which shows the flow of the process by the management manager in the device return process. It is a block diagram showing an example of composition of a computer system in a 2nd embodiment of the present invention. FIG. 3 is a table configuration diagram illustrating an example of a logical device management table held by a management manager. FIG. 4 is a table configuration diagram showing an example of a table for managing the correspondence between host computers and WWNs held by the management manager. 9 is a flowchart illustrating a flow of a process performed by a management manager. FIG. 3 is an explanatory diagram showing a zoning function of a fiber channel switch. It is a block diagram showing the example of composition of the computer system in a 3rd embodiment of the present invention. 6 is a flowchart illustrating a flow of a process performed by a client program. 9 is a flowchart illustrating a flow of a process performed by a management manager of the file server. It is a flowchart which shows the flow of a process by the server program of a file server. 9 is a flowchart illustrating a flow of a process performed by a management manager when a file system is extended. It is a block diagram showing the example of composition of the computer system in a 4th embodiment of the present invention. 5 is a flowchart illustrating a flow of a process performed by a volume manager. FIG. 4 is a table configuration diagram illustrating an example of an LVOL management table. 11 is a flowchart illustrating a flow of a process performed by a volume manager when extending an LVOL. FIG. 3 is a table configuration diagram illustrating an example of a cluster information table. 11 is a flowchart illustrating a flow of a process performed by a management manager when extending an LVOL.

Explanation of reference numerals

1 ... host computer,
2 ... Storage subsystem 3 ... Management host computer 4 ... Network 5 ... Secondary storage 8 ... Fibre channel switch 11 ... Volume manager 21 ... Disk unit 22 ... Disk controller 23 ... Port 31 ... Management manager 81 ... Port

Claims (16)

A first calculator;
A storage subsystem having a storage device for holding data accessed from the first computer;
A computer system comprising: a second computer having device management information on the storage device of the storage subsystem and host management information indicating a state of allocation of the storage device to the first computer. ,
The first computer has a request unit that receives a request for a new storage device from a user or an application program, and requests the second computer to allocate a new storage device.
The second computer, in response to a request from the request unit, referring to the device management information and the host management information to determine a storage device that can be assigned to the first computer, and the determination unit Changing means for changing the setting of the storage subsystem so that the storage device determined by the above can be accessed from the first computer.   2. The computer system according to claim 1, wherein the storage device is at least a part of a storage area formed in a physical storage device included in the storage subsystem.   2. The computer system according to claim 1, wherein the request unit sends information specifying a condition of a storage device to be allocated to the second computer together with the request for allocation.   The determining unit refers to the device management information and selects a storage device that satisfies the condition specified by the requesting unit and that is in an offline state as the assignable storage device. 4. The computer system according to claim 3,   5. The computer system according to claim 4, wherein the condition includes information for designating at least one of the required performance and reliability of the storage device. The requesting means has means for receiving a request for changing the capacity of an existing storage device and transmitting the request to the second computer,
The second computer, in response to the change request, selects a storage device that matches the storage device after the change of the capacity, and the storage subsystem stores the storage device in the existing storage device. Means for instructing to move the data to the storage device selected by the selecting means,
2. The computer system according to claim 1, wherein said storage subsystem includes means for moving data in response to said instruction.   2. The computer system according to claim 1, wherein the first computer has means for providing a plurality of storage devices as one logical device to the application program. The request means, in response to a request to expand the capacity of a device already provided to the application program, requests the second computer to generate a new storage device having a capacity required for the expansion requested by the expansion request. Request quota,
8. The computer system according to claim 7, wherein the providing unit makes the newly allocated storage device a part of the device requested to be expanded. The first calculator,
A storage subsystem having a storage device for holding data accessed from the first computer;
And a second computer that manages the state of allocation of the storage devices of the storage subsystem to the first computer, and a method of allocating storage devices in a computer system comprising:
Requesting the second computer to allocate a new storage device from the first computer,
In the second computer, a storage device that can be assigned to the first computer is determined based on the request,
Instructing the storage subsystem to change the setting so that the storage device determined from the second computer to the storage subsystem is accessible from the first computer;
Transferring information necessary for accessing the determined storage device from the second computer to the first computer;
A storage device allocation method, wherein the first computer changes settings of the first computer so that the determined storage device can be used based on the information necessary for the access. 10. The storage device allocation method according to claim 9, wherein the step of requesting the allocation includes a step of transmitting a request including information indicating a condition required for the new storage device to the second computer.   The storage device allocation method according to claim 10, wherein the required condition includes information for designating at least one of performance and reliability of the new storage device.   The determining step refers to device management information for managing storage devices in the storage subsystem, and determines a storage device that satisfies the condition and is in an offline state as the assignable storage device. The method according to claim 11, further comprising the step of:   10. The storage device allocating method according to claim 9, further comprising, in the first computer, the determined storage device and an existing storage device constituting a logical storage used in the first computer. And expanding a capacity of the logical storage. A calculator,
A storage subsystem having a storage device for holding data accessed from the computer.
The computer has a request unit that receives a request for a new storage device from a user or an application program and requests the storage subsystem to allocate a new storage device.
Means for determining a storage device that can be assigned to the first computer by referring to the device management information and the host management information in response to a request from the requesting means; and Changing means for changing the setting of the storage subsystem so that the storage device determined by the above can be accessed from the first computer. Multiple calculators,
A file server to which the plurality of computers are connected via a network;
A computer system having a storage subsystem connected to the file server and having a plurality of storage devices,
The plurality of computers include a request unit that receives a request for a new file area from a user or an application program, and requests the second computer to allocate a new file area,
Means for determining a storage device having a storage area in which the file area can be set by referring to the device management information and the host management information in response to a request from the requesting means;
Changing means for changing the setting of the storage subsystem so that the storage device determined by the determining means can be accessed from the file server;
Setting means for changing the settings of the file server so that the determined storage device can be used;
A computer system comprising file management means for creating the file area on the determined storage device. The file management means includes means for transmitting information used for accessing the created file area to the computer that made the request,
17. The computer system according to claim 16, wherein the computer that has made the request has an application program that accesses the created file area using the information used for the access.

Images