JP2001142648A - Computer system and its method for allocating device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To dynamically perform device setting and allocation to each computer so that a plurality of computers can utilize a device meeting their use if necessary. SOLUTION: A storage device subsystem 3 has a plurality of devices having various configurations and capacities and is connected to a plurality of computers 1. A management computer 3 stores and manages the connection relations between the computers 1 and the system 2 and manages the devices while communicating with the volume managers 11 of the computers 1. When a computer 1 newly requests devices, the computer 1 notifies a management manager 31 of information such as the number, capacities and types of the devices. The manager 31 selects devices meeting the request and instructs the storage device subsystem to perform setting so that the devices can be used from the computer 1. The manager 31 subsequently notifies the computer 1 of information necessary to the access to the new devices, and its manger 11 changes the setting of the computer 1 according to the notification.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

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

[0002]

2. Description of the Related Art In recent years, the amount of information handled by computer systems used in companies and the like has increased exponentially, and 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, Japanese Patent Application Laid-Open No. 9-274544 discloses a technique in which one storage subsystem is constituted by a plurality of types of logical disk devices (hereinafter, also referred to as devices). ing. Specifically, as a device (logical disk) accessed from the host computer, RA
Devices having different RAID levels, such as RAID 5 and RAID 1 in IDs (Redundant Arrays of Inexpensive Disks), or those having different access speeds as actual magnetic disk devices (physical disk devices) for configuring logical disks Are disclosed. 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 a peripheral device such as a disk device, a plurality of host computers and a plurality of storage devices are connected by one fiber channel cable. System configuration has also been performed. 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.

[0004]

According to the above-mentioned prior 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 that can be accessed by the host computers increase, it becomes more difficult for each host computer to manage devices. While one host computer can access many devices, it is difficult for the user to select which device should be used 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 not originally used by the host computer. 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. 10-333839 discloses a method of permitting a storage device connected by a fiber channel 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 is always aware of the device type. There is a need to.

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

[0007]

According to one preferred embodiment of the present invention, a computer system 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 required, 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 means 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, and the device allocated by the computer is changed. Make it available.

In another embodiment of the present invention, a plurality of computers and a plurality of storage subsystems are connected via a network. On any computer, a storage device provided in each storage subsystem and management means for holding information on the connection relationship between each computer and the storage subsystem are provided. Each storage subsystem has control means for permitting access to the computer specified 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 authorizes the storage subsystem to access the storage 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 that 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.

[0009]

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

The computer system comprises a plurality of host computers,
Host computer 1a, host computer 1b,... Host computer 1n (collectively referred to as host 1), storage subsystem 2 connected to host 1, management host computer 3, network 4, and remote location It has a secondary storage device 5 which is a storage device.

The host computers 1a, 1b,...
This is a computer having a memory and the like, and achieves predetermined functions by the CPU reading and executing the operating system and application programs stored in the memory.

The storage subsystem 2 includes 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 connected to the network 4. 25.
The storage subsystem 2 in the present embodiment makes the host computer 1 appear as one or a plurality of logical devices by grouping a plurality of disk units 21 together. of course,
Each disk unit 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, a SCSI (Small Computer System Interface) is used.
An interface such as e) is used. On the other hand, if the host computer 1 is a so-called mainframe,
A channel interface such as ON (Enterprise System Connection) is used. Each port 23
May be the same interface or a mixture of different interfaces. 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 performs access from the host computer 1 and controls the disk unit 21. The processor 221 is especially 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, appear as one or a plurality of logical devices. , Its 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 to be executed by the processor 221 and also stores information for managing the disk unit 21 and a logical device configured by combining a plurality of disk units 21. used.

Each host computer 1a, 1b,... Is provided with software (program) called a volume manager 11. 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 the interface 12
To the port 23 of the storage subsystem 2.

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

As described above, the storage subsystem 2 comprises:
The plurality of disk units 21 appear to the host computer 1 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 more logical devices. Storage subsystem 2
There is no correlation between the number of disk units 21 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 includes a logical device number 61, a size 62, a configuration 63, a state 64,
A set of items of a path 65, a target ID 66, and a LUN 67 is held. 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, the RAI by the disk unit 21.
If D (Redundant Arrays of Inexpensive Disks) is configured and assigned to a logical device,
Information indicating the type of RAID, such as RAID1 and RAID5, 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 is no longer used by the host computer 1 because the device becomes unnecessary. “Not implemented” indicates that the logical device is not defined and cannot be accessed from the host. Also "failure offline"
Indicates that the logical device has failed and cannot be accessed from the host.

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-I used when a device is accessed from the host computer 1 on SCSI is used.
D and LUN are used.

One logical device can be connected to a plurality of ports, and a plurality of host computers 1 can access the same logical device. 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. Therefore, there are two items of the logical device number 2. When one logical device is made accessible from a 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 passed through the network interface 24 at an appropriate timing or when the configuration of the storage subsystem 2 changes due to a failure of the storage subsystem 2 or the like. Sent to For this reason, the management host computer 3
2 also holds a logical device management table similar to 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 is composed of a set of a host name 71, a port number 72, an interface number 73, and a logical device number 74 so that the management host computer 3 manages the assignment of devices to each host computer 1. Holds management information.

Port number 72 and logical device number 74
Is a number defined inside the storage subsystem 2 and is 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 particularly necessary when one host computer 1 has a plurality of interfaces 12. Port number 72 and interface number 7
The set of 3 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 one interface or a line connecting the one interface and the storage subsystem 2 cannot be used due to a failure or the like, the process is continued if the other interface is connected to the logical device. 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 showing the 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 is 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, R
Information regarding device reliability, such as AID0, 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, fire, or the like, the remote mirror can be used.
Since data is stored in the secondary storage device 5, reliability can be improved.

Next, in step 1002, the volume manager 11
2 is searched for a set of unused target IDs and LUNs.

In step 1003, the volume manager 11 manages the capacity, performance condition, reliability level specified in step 1001, and the unused target ID and LUN set retrieved in step 1002 by the management host computer 3. The request is transmitted to the manager 31 to request allocation of a new device. The management manager 31 searches for a device to be assigned based on the received information,
It returns information specifying the host interface number, target ID, and LUN used to access 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 the device file is accessed.
Usually, a 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. Therefore, in step 1004, a device file relating to the newly assigned device is created. Specifically, for example, Sun Microsystems
“Drvconfig” on Solaris Operating System
The command or the “drives” command recognizes a new device and creates a device file, so that the host computer 1 can access a newly assigned 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.

The management manager 31 determines in step 1101
When information such as the device size, performance condition, and reliability level sent from the host computer 1 is received, the information referring to the held logical device management table and the information set in the host management table is referred to. Search for the corresponding device. 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 110).
2). 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 sets the target ID and LUN information received from the host computer 1 and the logical device management table and the host management table. Based on the information, a port number, a target ID, and a LUN used for connecting the device to the host computer 1 are determined (step 1104).

Next, the management manager 31 proceeds to step 1
The device of the logical device number found in 103 is set to the port number determined in step 1104, the target ID,
It instructs the storage subsystem 2 to set it to be accessible by LUN and to bring it online. 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 the management manager 31 receives the result from the storage subsystem 2 (step 1106), the volume manager 11 of the requested host computer 1
, Interface number, target ID, LU
N is returned (step 1107).

On the other hand, in step 1103, "offline"
If there is no device in the status that meets the request, 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 1).
110).

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

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 prevents the host computer 1 from using the device.
The setting of the host computer 1 is changed as needed. 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, the target ID, and the 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 receives the received interface number, target ID, and LUN.
And instruct the storage subsystem 2 to take the device to be returned offline. 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). Storage subsystem 2
When the logical device management table is received from, the processing is completed by holding it (step 1303).

In the above-described first embodiment, the management host computer is provided and the management manager is arranged therein. However, the function of the management manager does not necessarily need to exist in the management host computer. For example, the host computer 1a,
1b,.... Further, 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 showing the configuration of a computer system according to the second embodiment of the present invention.

The computer system according to this embodiment includes a plurality of host computers 1 (host computers 1a, 1b,..., 1n), a plurality of storage subsystems 2a, 2b,. Computer 3, Network 4, and Fiber Channel Switch 6
Is configured.

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,
Fiber Channel switch 8 by interface 12
Connected to

The storage subsystems 2a, 2b,..., 2
m denotes a disk unit 21, a disk controller 22, a port 23, and a network interface (network I / F) connected to a network, similarly to the storage subsystem 2 in the first embodiment.
25. As in the first embodiment, a plurality of disk units 21 and ports 23 may be provided.
Here, for the sake of simplicity, 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. Each port 81 has a host computer 1
, and one of the ports 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 configured such that the host computers 1a, 1b,.
a, 2b,... are freely accessible. In this configuration, basically all the host computers 1 can access all the storage subsystems 2. The management host computer 3
As in the first embodiment, a management manager 31 is provided. 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 this 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 includes, for each device, its size 103, configuration 104, status 105, LUN1
06, WWN (World Wide Name) 102, and connection host name 107 as information.

Size 103, configuration 104, state 105,
The LUN 106 is 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. WWN 107 is N_PORT_N
Also called AME. 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 relating to the security of the system, for example, Japanese Patent Laid-Open No.
Japanese Patent No. 333839 discloses a technique that allows only a specific host computer to access a storage device connected by a fiber channel. Also in the present embodiment, in order to maintain the security of the system, the storage subsystem 2 is disclosed in Japanese Patent Laid-Open No. 10-3338.
It is assumed that there is a means for maintaining safety as disclosed in JP-A-39. However, this is not directly related to the essence of the present invention,
Here, detailed description is omitted.

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.

The operation of the volume manager 11 and the management manager 31 will be described below.

In this embodiment, when allocating a new device to the host computer, the volume manager 11
Is basically performed in the same manner as the processing in the first embodiment shown in FIG. That is, when the volume manager 11 receives information on the number and types of devices required from a user or an application program, the volume manager 11 performs management based on the information.
1 requests allocation of a new device. 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 host computer 1 can use the new device.

FIG. 11 shows a flowchart of a process executed 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 of the management manager in the first embodiment shown in FIG. Note that FIG.
In FIG. 5, 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 in which processing different from that in FIG. 5 is performed, and a description of a portion in which the same processing as in FIG. 5 is performed will be omitted.

In the present embodiment, the storage subsystem 2 is designed to prevent a device from being inadvertently accessed from a host computer that is not assigned to a device.
In the initial state, access from all host computers 1 is prohibited. 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 a device, the storage subsystem 2
Based on the WWN received from the management manager 31,
It is determined whether the access is permitted (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, a case is considered where 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, a certain device can be prevented from being accessed from a host computer to which access is not originally permitted. Further, since the data flow is separated, the performance can be improved (step 2106).

After the above processing, the management manager 31
The processing of steps 1106 and 1107 is performed.

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

In the computer system of this embodiment, a plurality of host computers 1a ', host computers 1b',..., Host computers 1n '(collectively called hosts 1') are composed of a network interface (I / F) 12 ', 4 is connected to a 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, carries out device assignment according to a request. Server program 9
Reference numeral 4 denotes a file server program such as an 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 are so-called NAS (Network Attached S) that each host computer 1 ′ sees them as one storage device.
Some configurations may be torage).

The client program 11 ′ of the host computer 1 ′ is executed by the server program 9 on the file server 9.
4 is a program that enables the file server 9 to use the file system created in the storage subsystem 2 from an application program operating on the host 1 ′ by communicating with the host computer 4. Client program 1
1 '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 converts data existing in a certain logical device into a logical device. It has a function to move to a physical disk unit different from the physical disk unit in which it is located. For specific technical means for realizing such a function, see, for example, Japanese Patent Application Laid-Open No. 9-274.
A known technique disclosed in Japanese Patent Application Publication No. 544-544 can be applied. Therefore, a detailed description thereof will be omitted in this specification.

FIG. 14 is a flowchart showing the 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 the required device capacity, performance conditions, and reliability level, similarly to step 1001 in the first embodiment shown in FIG. 4 (step 2001).

Next, the client program 11 '
Information such as the capacity, performance condition, and reliability level specified in step 2001 is transmitted to the management manager 93, and a new file system area is requested. Based on the information received from the client program 11 ', the management manager 93 searches for and prepares an area of the device to which it can be assigned, 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 from the management manager 93 (Step 2004). Lastly, the client program 11 'notifies the user or the application program of the allocated mount point, and ends the processing (Step 2005).

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

This processing is basically performed in the same manner as the processing 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 showing the flow of processing executed by a server program which has received information about a device from a 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 a request for a new file system shown in FIG. 15 is different in the following points.

When the size of the existing file system is to be changed, the user or the application program instructs the client program 11 'to mount, expand or reduce the size of the file system whose size is to be changed. Issue a request that specifies information such as size. 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 executes the client program 11 '
, The information such as the mount point of the file system to be processed and the size to be expanded are received (step 2301).

The management manager 93 obtains 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 ', and Is determined. Then, the management manager 93 obtains information on the type of the logical device, that is, information such as reliability and performance (step 2302). Subsequently, the management manager 93 performs steps 2301 and 230
Based on the information obtained in step 2, in the same manner as when a new file system is added, a logical device having a free area of the changed file system size and the same type as the original logical device is secured (step 1102) ~ 111
0).

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. The 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, the file system cannot use all of the expanded capacity without rebuilding the file system. 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).

With 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 an existing file system, the client program 1
1 '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 fourth embodiment of a computer system to which the present invention has been applied.

The computer system in this embodiment comprises a plurality of host computers 1 ″ (host computers 1a ″, 1b ″,
.., 1n ″), a management host computer 3, a storage subsystem 2 ′, and a sub-storage 5. Each host computer 1 ″ and storage subsystem 2 ′ is connected to a fiber channel switch 8. Connected via. Further, the host computer 1 ″, the storage subsystem 2 ′, and the fiber channel switch 8 are mutually connected via the network 4.

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 more 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 for interconnecting the clusters 26. 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 to a bus 28 faster than the inter-controller connection mechanism 27.
Are joined by Each channel processor 23 '
One or more ports 231 are provided, and are connected to the host computer 1 ″ via the secondary storage device 5 or the fiber channel 8. A plurality of disk units 21 are connected to the drive processor 22 ′. In the present 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. In configuring a device, it is assumed that the disk units 21 included in a plurality of clusters 26 cannot be combined.

The channel processor 23 'shows one or a plurality of logical devices to each host computer 1 ",
Access from each host 1 "is accepted. In principle, the channel processor 23 'manages a logical device constituted 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 higher speed than the communication across the clusters. When the channel processor 23 'does not operate, the channel processor 23' of the other cluster 26 takes over the processing.The channel processor 23 'is connected to which drive processor 22' a logical device designated by the host computer 1 "is connected. Disk uni Determine is configured to preparative 21 passes the request processing to the appropriate drive processor 22 '. The drive processor 22 'interprets the request from the channel processor 23', generates a disk access request for each disk unit 21 where 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 ′. Volume Manager 1
1 "apparently combines a plurality of logical devices to form one larger LVOL, or divides one logical device into a plurality of regions and divides those regions into LVOLs.
Can be used by an application program on the host computer 1 ″.
A new logical device can be connected to the VOL to expand the capacity of the LVOL.

FIG. 19 is a flowchart showing the flow of processing executed by the volume manager 11 "when newly allocating a volume in this embodiment.

The processing described here is the same as the processing shown in FIG.
Step 1002 of the device assignment processing in the embodiment is replaced with step 1002 ', and step 1006 is replaced with steps 1005' and 1006 '. In other steps, the same processing as the corresponding step in FIG. 4 is performed. Hereinafter, step 10
The processing performed in 02 ', 1005', and 1006 'will be described.

In step 1002 ', the unused WW
A set of N and LUN is searched 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 has an LVOL name 151 and a device file name 15
2, size 153, and WWN 154 of each device,
Information consisting of a set of LUNs 155 is registered. LVOL
The name 151 is an identifier given to identify the LVOL provided to the application program by the volume manager 11 ". The device file name 152 is the name of a logical device constituting the LVOL. The volume manager 11" Manages logical devices belonging to each LVOL based on device file names. The size 153 indicates the capacity of each logical device constituting the LVOL. Since one LVOL may be composed of a plurality of logical devices, one LVOL
A plurality of device files may belong to the L 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.
At 06 ', the user is notified of the assigned LVOL name, and the process ends.

FIG. 21 is a flowchart showing the processing of the volume manager when expanding the capacity of an 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 the LVOL to be expanded.
Is usually the same type of logical device as the logical device that is building the device. 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 processing, the volume manager 1
1 "first receives from the user or the application program information on the LVOL name of the LVOL to be expanded and the capacity to be expanded (step 250).
1). Next, the volume manager 11 ″ inquires of the type of the logical device constituting the LVOL to be extended to the management manager 31 (step 2502). The volume manager 11 ″ determines the unused WWN and LUN pairs from the LVOL management table. Search (Step 250)
3). The volume manager 11 ″ proceeds to step 250
2. The information including the type of the logical device acquired in 2503 and the combination of the unused WWN and LUN 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 "
The logical device newly allocated to the LVOL to be expanded is added to expand the capacity of the LVOL, and the process is terminated (step 2507).

When there is a request for allocation of a new logical volume from the volume manager 11 ″ in step 1003 in FIG. 19 and step 2504 in FIG. 21, the management manager 31 sends the device requested by the volume manager 11 ″ in any case. Search for and assign a device that matches the type and capacity of the device. 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 showing an example of the cluster information management table.

The cluster information management table has an entry corresponding to each cluster 26. 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 provided. Is set. 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 explained earlier,
When a logical device is constructed in the disk unit 21 connected to a certain drive processor 22 ', it is desirable from the viewpoint of performance that the logical device can be accessed from the port 231 in the same cluster. 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 ′ connected to the disk unit 21 on which the logical device to be newly allocated is constructed to the same cluster. Configure the device settings.

FIG. 23 is a flow chart showing the flow of device allocation processing by the management manager 31.

The device assignment processing in this embodiment is performed in substantially the same manner as the processing in the second embodiment shown in FIG. 11, but some of the processing is performed in the second embodiment due to the difference in the configuration of the storage subsystem. Is different from the embodiment. Specifically, in step 1109, the management manager 3
1 requests the storage subsystem 2 'to newly construct a device, the storage subsystem 2'
Builds the device according to the requirements. 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 manager 31 stores the information on the logical device received from the storage subsystem 2 ′,
With reference to the cluster information management table, it is determined 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). In addition, the management manager 31
Finally, the WWN and L required for accessing the newly allocated logical volume are given to the volume manager 11 ″.
Information such as UN is sent, and the process is terminated (step 26).
07).

Processes other than those described here are the same as those of the manager in the second embodiment shown in FIG. 11, and the same reference numerals as those in FIG. Omitted.

According to the above-described embodiment, even when the host computer is operating, the device can be allocated according to the request. Furthermore, even in an environment composed of fiber channel switches in which a plurality of devices coexist, it is possible to easily allocate a device that meets the requirements 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.

[0115]

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

[Brief description of the drawings]

FIG. 1 is a block diagram illustrating a configuration example of a computer system according to a first embodiment of this invention.

FIG. 2 is a table configuration diagram showing 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.

FIG. 4 is a flowchart showing a flow of processing executed by a volume manager of the host computer.

FIG. 5 is a flowchart illustrating a flow of a process performed by a management manager.

FIG. 6 is a flowchart showing a flow of processing by a volume manager in a device return processing.

FIG. 7 is a flowchart showing a flow of a process performed by a management manager in a device return process.

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

FIG. 9 is a table configuration diagram illustrating an example of a logical device management table held by the management manager.

FIG. 10 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.

FIG. 11 is a flowchart showing a flow of processing by a management manager.

FIG. 12 is an explanatory diagram showing a zoning function of the fiber channel switch.

FIG. 13 is a block diagram illustrating a configuration example of a computer system according to a third embodiment of the present invention.

FIG. 14 is a flowchart showing the flow of processing by a client program.

FIG. 15 is a flowchart showing the flow of processing by the management manager of the file server.

FIG. 16 is a flowchart showing the flow of processing by the server program of the file server.

FIG. 17 is a flowchart illustrating a flow of processing performed by a management manager when a file system is extended.

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

FIG. 19 is a flowchart showing the flow of processing by the volume manager.

FIG. 20 is a table configuration diagram illustrating an example of an LVOL management table.

FIG. 21 is a flowchart showing the flow of processing performed by a volume manager when extending an LVOL.

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

FIG. 23 is a flowchart showing the flow of processing performed by the management manager when extending an LVOL.

[Brief description of reference numerals]

 DESCRIPTION OF SYMBOLS 1 ... Host computer, 2 ... Storage device subsystem 3 ... Management host computer 4 ... Network 5 ... Secondary storage device 8 ... Fiber channel switch 11 ... Volume manager 21 ... Disk unit 22 ... Disk controller 23 ... Port 31 ... Management manager 81 …port

Claims (16)

[Claims] A first computer, a storage subsystem having a storage device for holding data accessed from the first computer, device management information on the storage device of the storage subsystem, And a second computer having host management information indicating a status of allocation of the storage device to the first computer, wherein the first computer receives a new user or application program from an application program. A requesting unit for receiving a request for a storage device and requesting the second computer to allocate a new storage device, wherein the second computer responds to a request from the requesting unit,
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; and the storage device determined by the determination means can be accessed from the first computer. Changing means for changing the setting of the storage subsystem as described above. 2. The computer system according to claim 1, wherein said storage device is at least a part of a storage area formed in a physical storage device provided in said storage subsystem. 3. The apparatus according to claim 1, wherein said requesting means sends information specifying a condition of a storage device to be allocated to said second computer together with said request for allocation.
Computer system as described. 4. The storage device according to claim 1, wherein the determination unit refers to the device management information and selects a storage device that satisfies the condition specified by the request unit and that is in an offline state as the assignable storage device. 4. The computer system according to claim 3, wherein 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. 6. 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, wherein the second computer requests the change of the capacity of the existing storage device. A means for selecting a storage device that matches the storage device after the capacity is changed, and a data held in the existing storage device is selected by the selection means for the storage subsystem. 2. The computer system according to claim 1, further comprising: means for instructing to move to a storage device, wherein the storage subsystem comprises means for moving data in response to the instruction. 7. The computer system according to claim 1, wherein said first computer has means for providing a plurality of storage devices as one logical device to said application program. 8. The requesting means, in response to a request to expand the capacity of a device already provided to the application program, requests the second computer to determine the capacity required for the expansion requested by the expansion request. 8. The computer system according to claim 7, wherein the means for requesting and providing a new storage device makes the newly allocated storage device a part of the device requested to be expanded. 9. A first computer, a storage subsystem having a storage device for holding data accessed from the first computer, and the first computer of the storage device included in the storage subsystem. A second computer that manages the state of the allocation of storage devices in the computer system, wherein the first computer requests allocation of a new storage device from the second computer to the second computer. A storage device that can be assigned to the first computer based on the request; and a storage device determined for the storage subsystem from the second computer by the first computer. And instructs the storage subsystem to change the setting so that it can be accessed from the second computer. Transferring the information necessary for accessing the determined storage device to the first computer; and allowing the first computer to use the determined storage device based on the information necessary for the access. A method of allocating a storage device, wherein the setting of the first computer is changed. 10. The method according to claim 9, wherein the step of requesting the assignment includes a step of transmitting a request including information indicating a condition required for the new storage device to the second computer. Storage device allocation method. 11. The storage device allocating method according to claim 10, wherein said required condition includes information for designating at least one of performance and reliability of said new storage device. 12. The storage device according to claim 1, wherein the determining step refers to device management information for managing storage devices in the storage subsystem, and assigns the storage device that satisfies the condition and that is in an offline state to the storage device. The storage device allocation method according to claim 11, further comprising a step of determining the storage device. 13. The storage device allocation method according to claim 9, further comprising, in said first computer, said determined storage device and a logical storage used in said first computer. A method of allocating a storage device, wherein the storage device is combined with an existing storage device to expand the capacity of the logical storage. 14. A computer system having a computer and a storage subsystem having a storage device for holding data accessed from the computer, wherein the computer receives a request for a new storage device from a user or an application program. Receiving means for requesting the storage subsystem to allocate a new storage device to the storage subsystem, wherein the storage subsystem stores the device management information and the host management information in response to a request from the requesting means. Means for determining a storage device that can be allocated to the first computer with reference to the first computer, and setting of the storage subsystem so that the storage device determined by the determination means can be accessed from the first computer. And a changing means for changing. 15. A computer system comprising: a plurality of computers; a file server connected to the plurality of computers via a network; and a storage subsystem connected to the file server and including a plurality of storage devices. The plurality of computers receive a request for a new file area from a user or an application program,
Requesting means for requesting the second computer to allocate a new file area, wherein the file server refers to the device management information and the host management information in response to a request from the requesting means, and Means for determining a storage device having a storage area in which a file area can be set; changing means for changing the setting of the storage subsystem so that the storage device determined by the determination means can be accessed from the file server; A computer system comprising: setting means for changing the settings of the file server so that the determined storage device can be used; and file management means for creating the file area on the determined storage device. 16. The file management means includes means for transmitting the information used for accessing the created file area to the computer that has made the request, and the computer that has made the request contains the information used for the access. 17. The computer system according to claim 16, further comprising an application program for accessing the created file area by using the application program.