# Patent

## Title
Management computer for calculating effective total volume of storage apparatus

## Abstract

In a computer system having a storage system in which storage units are hierarchically configured, a management method for accurately grasping the capacity available to the computer is disclosed.
In a computer system in which a management computer manages the capacities of storage units for storing data used by the computer, the management method is typically realized by a storage management system comprising a group of first-level storage units each containing volumes for storing data used by the computer, a group of second-level storage units each of which is hierarchically linked to, and physically connected through a communication path to, one of the first-level storage units and contains volumes for storing data used by the computer, a means for collecting volume information from the first-level and the second-level storage units, a means for collecting inter-volume hierarchy information, and a means for calculating the total effective capacity to the computer based on the volume information and the inter-volume information thus collected.

## Background
This application is a continuation of U.S. patent application Ser. No. 11/484,592, filed Jul. 12, 2006, now U.S. Pat. No. 7,174,425, which is a continuation of 10/786,108, filed Feb. 26, 2004, now U.S. Pat. No. 7,089,359, the entirety of which are incorporated herein by reference.


BACKGROUND OF THE INVENTION
The present invention relates to a storage management method, and more specifically to a method for managing the capacities of volumes contained in storage units in a computer system having a hierarchically arranged group of storage units.
DESCRIPTION OF THE PRIOR ART
In a large-scale storage system such as a disk array system, each storage unit is divided into a number of virtual storage areas called volumes. Stored in each such volume are programs to be executed by the computer to which the storage unit is connected and their associated data that is necessary for executing them. The information concerning the volumes such as the number of volumes allocated to each storage unit and the capacity of each volume (typically expressed in bytes) can be obtained through the management interface to which the storage units are connected.
Another system according to the prior art allows a volume with a desired capacity to be created in a storage unit through a management interface. For example, the Storage Networking Industry Association (SNIA; http://www.snia.org) is working on the establishment of a storage management interface based on the Common Information Model (CIM) and Web-Based Enterprise Management (WBEM), the standardization of which is being promoted by the Distributed Management Taskforce (DMTF). More specifically, SNIA has published the Storage Management Initiative Specification (SMI-S), which sets forth a set of specifications for how to check the capacity of a given volume in a given storage unit and for how to create a volume in a given storage unit.
Furthermore, Publication of Japanese translation of a PCT application Heisei 10-508967 (WO97/09676) (reference #1) discloses a storage system which allows online data transfer between two storage units that are situated in different levels of storage hierarchy.
[Reference #1]


    Publication of Japanese translation of a PCT application Heisei 10-508967 (WO97/09676)

[Reference #2]

    SMI-S Specification PUBLIC REVIEW DRAFT (pp. 103-114, pp. 146-182) [online], Storage Networking Industry Association (SNIA), Apr. 15, 2003 (accessed on Jun. 4, 2003)

(Internet URL:

    http://www.snia.org/smi/tech_activities/smi_spec_pr/spec/SMIS—1615a.pdf)


SUMMARY OF THE INVENTION
The invention disclosed in Publication of Japanese translation of a PCT application Heisei 10-508967, assuming that a first-level storage unit and a second-level storage unit belonging to different levels of hierarchy support a management interface of the type described above, allows a management computer having the same management interface to detect, and communicate with, both of these storage units through anetwork. For example, by interrogating any storage unit, the management computer can obtain the number of volumes contained in it or information on the capacities of the volumes contained in it.
In a configuration where a second-level storage unit is hierarchically connected to a first-level storage unit, data migration involves making a volume in the second-level storage unit available for use as a volume in the first-level storage unit. The management computer then needs to realize that certain volumes in the second-level storage unit are in fact used as volumes belonging to the first-level storage unit and also to know the total effective capacity in the system.
It is an object of the present invention to provide, in a storage system in which storage units are hierarchically configured into multiple levels, a storage management system and a storage management method for realizing the hierarchical structure of the storage units and accurately grasping and displaying the total available storage capacity.
In a computer system comprising a computer, a plurality of storage units each containing one or more volumes for storing data used by the computer, and a management computer for managing the status of the storage units, the invention relates to a storage management system comprising one or more first-level storage units each containing one or more volumes for storing data used by the computer, one or more second-level storage units each of which is connected to one of the first-level storage units through a communication path in a hierarchical configuration and contains one or more volumes for storing data used by the computer, means for collecting from the first and the second-level storage units volume information on the volumes contained in them, means for collecting inter-volume hierarchy information on the hierarchical relationships between volumes contained in the first storage units and volumes contained in the second-level storage units, and means for calculating the total effective capacity to the computer based on the volume information and the inter-volume hierarchy information thus collected.
In a preferred embodiment of the invention, the first and the second-level storage units each contain one or more virtual storage areas called volumes. The means for collecting volume information, the means for collecting inter-volume hierarchy information, and the means for calculating the total effective capacity are all provided by each program, which is executed in the management computer.
In the preferred embodiment, the information on the hierarchical relationships between the volumes contained in a first-level storage unit and the volumes contained in a second-level storage unit is held in the first-level storage unit, which is the higher in the hierarchy. This is accomplished, for example, by providing each first-level storage unit with a program for processing hierarchy information requests, which collects information from the storage units connected to it.
The management computer is equipped with a display unit (hereinafter simply called “display”) to display the storage capacities of the volumes contained in each storage unit and the inter-volume hierarchical relationships. In the preferred embodiment, the display has at least two display sections: one for displaying the information on the volumes contained in the second-level storage units that are used by the first-level storage units, and the other for displaying the information on the other volumes.
The process of managing the storage capacities of volumes using the management computer according to the preferred embodiment of the invention comprises a step for allocating a volume in a first-level storage unit for storing data used by the computer, a step for establishing a hierarchical relationship between a first-level storage unit and a second-level storage unit so that a volume is shared between the two, a step for collecting information on the volumes contained in the first-level storage units, a step for collecting information on the volumes contained in the second-level storage units, a step for collecting information on the hierarchical relationships between the volumes in the first-level storage units and those in the second-level storage units, and a step for calculating the total effective capacity in the computer system based on the information on the volumes and the information on the hierarchical relationships thus collected. This process is carried out by a program for managing the storage capacities of the volumes running on the management computer.
The invention makes it possible to accurately grasp, in a computer system having a hierarchically arranged group of storage units, the storage capacity available to the computer. Furthermore, it displays on the display of the management computer information on the real capacities of the volumes considering the hierarchical relationships between them, thereby providing the user with accurate information on the capacities of the volumes that are hierarchically configured.



BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 illustrates the general configuration of a computer system according to a preferred embodiment of the invention.
FIG. 2 shows the format of volume information according to a preferred embodiment.
FIG. 3 shows the format of information on the hierarchical relationship according to a preferred embodiment.
FIG. 4 shows an example of a computer system according to a preferred embodiment.
FIG. 5 shows the format of the identifier according to a preferred embodiment.
FIG. 6 shows the format of the consolidated information table according to a preferred embodiment.
FIG. 7 illustrates the process flow of creating the consolidated information table in a management computer 501 according to a preferred embodiment.
FIG. 8 illustrates the flow of process carried out in the storage unit (e.g., 201) according to a preferred embodiment.
FIG. 9 shows an example of the display according to a preferred embodiment.
FIG. 10 shows the format of volume information according to another embodiment of the invention.
FIG. 11 shows an example of the display according to another embodiment.
FIG. 12 shows an example of the display according to still another embodiment.



DESCRIPTION OF THE PREFERRED EMBODIMENTS
Preferred embodiments of the invention will now be described by way of example and with reference to the accompanying drawings.
FIG. 1 shows a computer system comprising four computers 301 through 304, a first-level storage unit 201, and two second-level storage units 101 and 102, and a management computer 501. The first-level storage unit 201 and the second-level storage units 101 and 102 each contain at least one virtual storage area called a volume. The second-level storage units 201 and 202 are connected to the first-level storage unit 201 through a communication path in a hierarchical configuration. It should be noted that more than one volume may be allocated within one storage unit or one volume may span more than one storage unit.
The computer 301 is connected to a volume 211, the communication with which is controlled by the first-level storage unit 201. Stored in the volume 211 are programs used by the computer 301, their input data, and their output data. Similarly, the computer 302 is connected to a volume 212, the communication with which is controlled by the first-level storage unit 201. Further, the volume 212 is connected to a volume 111, the communication with which is controlled by the second-level storage unit 101. The volume 212 and the volume 111 are configured hierarchically and each can hold data.
The computer 303 is connected to a volume 213, the communication with which is controlled by the first-level storage unit 201. The volume 213 is connected to a volume 161 situated in the second-level storage unit 102. The volume 213 cannot hold data; instead, the data for the volume 213 is actually held in the volume 161. When the computer 303 sends a write request directed to the volume 213, the first-level storage unit 201 asks the computer 303 to send the write data and, upon receiving it, sends a write request to the volume 161. The second-level storage unit 102 then stores the data into the volume 161. When the computer 303 sends a read request directed to the volume 213, the first-level storage unit 201 passes it to the volume 161. It then obtains the read data through the second-level storage unit 102 to which the volume 161 belongs and passes it to the computer 303. Alternatively, it can be so arranged that the volume 213 represents the volume 161 either for read or for write operation only. In effect, the volume 213 does not exist in the first-level storage unit 201 but instead acts just as a phantom area, and therefore is shown in dotted lines in the diagram. Thus, the volume 161 situated in the second-level storage unit 102 appears to the computer 303 as if it is situated in the first-level storage unit 102.
The computer 304 is connected to the volume 162, the communication with which is controlled by the second-level storage unit 102. Stored in the volume 162 are programs used by the computer 304, their input data, and their output data.
The storage units 201, 101, and 102 are each equipped with a management interface unit (I/F) 220, 120, and 170, respectively, for connection to the management computer 501.
While the configuration and operation of the management computer 501 will be described in detail later with reference to FIG. 4, an overview will be presented here.
In a computer system comprising one or more computers and a hierarchically arranged group of storage units, the management computer 501 is designed to grasp the storage capacity actually available to each computer and for that purpose is equipped with a volume information collecting program 520, a hierarchy information collecting program 540, an effective capacity calculating program 550, and a display 590 for displaying the effective capacities calculated by the effective capacity calculating program 550 for the system administrator.
The volume information collecting program 520 issues volume information requests to the storage units 201, 101, and 102 and obtains information (248, 148, and 198, respectively) on the number of volumes and the capacity of each volume in each storage unit. FIG. 2 shows examples of the volume information.
The hierarchy information collecting program 540 obtains hierarchy information 245 held by the first-level storage unit 201. The effective capacity calculating program 550 calculates, based on the volume information and the hierarchy information thus collected, the effective capacities actually available to the computers 301 through 304.
FIG. 3 shows an example of the format of the hierarchy information obtained through the hierarchy information 245. Each volume is assigned an identifier. For example, the identifier of the upper-level (first-level) volume 212, “ABC.XX200.0123.212,” is associated with the identifier of the lower-level (second-level) volume 111, “DEF.YY100.0456.111.” This relationship is held in an internal memory (not indicated in the diagram) of the first-level storage unit 201. When there is a change to the hierarchical relationship between a volume in a first-level storage unit and a volume in a second-level storage unit, this hierarchy information is revised accordingly.
Assuming that the volumes 111, 161, 162, 211, 212, and 213 each have a storage capacity of 100 G bytes (hereinafter abbreviated to “GB”), FIG. 2 shows the volume information collected by the management computer 501. (A) represents the volume information 248, which lists all the volumes allocated to the storage unit 201 and which indicates that the total number of volumes is 3 and each volume has a capacity of 100 GB. Similarly, (B) represents the volume information 148 corresponding to the storage unit 101, and (C) represents the volume information 198 corresponding to the storage unit 102.
If the management computer 501 were not to recognize the hierarchical relationships between volumes in the first-level storage units and the second-level storage units, then it would assume, by simply adding up the capacity of each volume, that a total of 600 GB were available in this computer system. The preferred embodiment of the invention described here, however, allows the management computer to calculate the total available capacity considering the hierarchical relationships, thereby preventing such misjudgments. Thus, the management computer 501, realizing that the volume 111 is subordinate to the volume 212 and the volume 161 is subordinate to the volume 213, making the number of real volumes four, calculates the total effective storage capacity to be 400 GB.
FIG. 4 shows an example of the configuration of a computer system according to the preferred embodiment being described.
The computers 301 through 303 are connected to the storage unit 201 through a fibre channel switch (hereinafter abbreviated to “FC switch”) 401. Each of the computers 301 through 304 comprises a CPU 310, a memory 320, and a fibre channel interface unit (hereinafter abbreviated to “FC interface unit”) 330. The FC interface unit 330 handles the interface operation between the computer and the FC switch. The memory 320 stores programs to be executed by the CPU 310, their input data, and their output data.
The storage unit 201 is connected through three FC interface units 230 inside it to the FC switch 401. The storage unit 201 includes a read/write request processing module 232, which receives read/write requests from the computers through the FC interface units 230, reads the requested data from the specified volumes and sends it to the computers, or writes the data sent from the computers to the specified volumes.
The storage unit 201 contains volumes 211 and 212, each having a capacity of 100 GB, for storing data to be used by the computers. The storage unit 201 further contains two FC interface units 235 for connection to other storage units 101 and 102, which serve as lower-level or subordinate storage units. The storage unit 201 also contains a data synchronization control module 238 inserted between the volume 212 and the FC interface unit 235 to establish data synchronization between the volume 212 and the volume 111 which is connected to the volume 212 through the FC interface unit 235. The data synchronization module 238 ensures that data consistency is maintained all the time between the two volumes (in this example, the volume 111 and the volume 212).
The storage unit 201 is also connected to two storage units 101 and 102 through an FC switch 402. Each of the storage units 101 and 102 comprises an FC interface unit 130 for connection to the FC switch 402 and a read/write request processing module 132. Further, the storage unit 101 comprises the volume 111 which stores data to be used by the storage unit 201. The storage unit 102 further comprises a volume 161 that stores data to be used by the storage unit 201 and a volume 162 that stores data to be used by the computer 304.
Whereas in the example described here a fibre channel network is assumed for connection between storage units and computers as well as between storage units, different types of network may be used instead, in which case appropriate devices or units need to be installed in place of FC switches and FC interface units. The FC switch 401 and the FC switch 402 may be used separately or may be connected in a cascade configuration.
A description of the management computer 501 and the management interface unit is now in order.
In the computer system depicted in FIG. 4, a management interface unit 410 is provided for grasping the configurations and capacities of the volumes. The storage units 101, 102, and 201 are each equipped with a management interface unit 120, 170, and 220, a CPU 121, 171, and 221, and a memory 123, 173, and 223, respectively. The memories 123, 173, and 223 each store programs to be executed by the CPU, data received through the management interface unit, and data to be sent through the management interface unit.
More specifically, the memory 223 in the storage unit 201 stores a volume information request processing program 225 for processing volume information requests from the management computer 501, a hierarchy information request processing program 226 for processing hierarchy information requests, and an identifier format inquiring program 227 for obtaining an identifier format from an identifier management computer 601 (to be described later).
The memories 123 and 173, which are situated in the storage units 101 and 102, each store a volume information request processing program 125 and 175 for processing volume information requests and an identifier format inquiring program 127 and 177, respectively, for obtaining an identifier format from the identifier management computer 601. The storage units 101 and 102 are connected through a management network 410 to the management computer 501.
The management computer 501 comprises a network interface unit 510 for connection to the management network 410, a CPU 511 for performing information processing inside it, a display 590 for displaying the results of the processing performed by the CPU 511, a memory 513 for storing programs to be executed on the CPU 511, data received or to be sent through the network interface unit 510, and data to be displayed on the display 590, and an input device 592 for receiving instructions from the administrator. Stored in the memory 513 are a volume information collecting program 520 for issuing volume information requests to storage units, a hierarchy information collecting program 540 for issuing hierarchy information requests, an effective capacity calculating program 550 for calculating the effective capacity, and an identifier format collecting program 527 for obtaining an identifier format from the identifier management computer 601.
The above-mentioned programs are originally stored in a nonvolatile storage medium such as a magnetic disk provided inside the management computer 501 and are loaded into the memory 513 for execution each time the management computer is started up. Other types of nonvolatile storage medium such as a CD-ROM and a floppy disk may also be used. Whereas in the example described here these programs are loaded from a nonvolatile storage medium held inside the management computer, they may also be loaded from an outside source through a network.
Next, the function and operation of the identifier management computer 601 will be described.
The computer system further comprises, in addition to a number of storage units, an identifier management computer 601. Each storage unit has an identifier. The identifiers of storage units, however, do not have a standardized format. Each storage unit manufacturer has its own identifier format. The identifier management computer 601 introduces a standardized identifier format, thereby registering and managing all the storage units in the system using a standard format.
It should be noted that if all the storage units have a standardized identifier format, there is no need for an identifier management computer.
The identifier management computer 601 comprises a network interface unit 610 for connecting to the management network 410, a CPU 611 for performing information processing, and a memory 613 for storing programs to be executed by the CPU 611, data received or to be sent through the network interface unit 610, and identifier formats, which are organized and held in an identifier format table 650. Further, the memory 613 stores an identifier format request processing program 620 for processing identifier format requests sent from the storage unit 201, 101, or 102 (hereinafter abbreviated to “201, etc.”) or the management computer 501.
When the identifier management computer 601 receives a request (inquiry) for the identifier format from an identifier format inquiring program 227, 127, 177, or 527 (hereinafter abbreviated to “227, etc.”) residing in the storage unit 201, 102, or 102 or the management computer 501, the identifier format request processing program 620 returns the identifier format taken from the identifier format table 650 shown in FIG. 5. The identifier format specified by the identifier management computer 601 sets forth the organization of the characters and fields making up the identifier that must be followed by all the storage units in the computer system and the volumes held in them. As shown in FIG. 5, the identifier format 650 comprises a string of characters, which is divided into several fields by delimiters 659 (dot “.”). More specifically, it comprises a vendor name 651, a model name 652, a manufacturing number 653, and a volume number 654. As the volume number 654, any of the numbers in the blocks shown in FIG. 1 or FIG. 4 may be used, for example, “ABC.XX200.0123.211.” If the identifier format is not standardized, it would be difficult to grasp the total available capacity in the computer system, since the volume information and the hierarchy information obtained from different storage units cannot be compared with each other. Therefore, if the identifier format is not standardized, it would be necessary to equip the management computer 501 with a format conversion program that converts the formats of the identifiers of the volume information and the hierarchy information between different storage units.
The storage unit 201, etc. executes, each time it is started up, the identifier format inquiring program 227, etc. and sends a request for the identifier format to the identifier management computer 601. In response, the identifier management computer 601 sends the identifier format 650 to the storage unit 201, etc. The storage unit 201, etc. saves this identifier format 650 in its internal memory, and later when requested, composes volume information and hierarchy information in accordance with it.
The management computer 501 executes, each time it is started up, the identifier format inquiring program 527 and sends a request for the identifier format to the identifier management computer 601. In response, the identifier management computer 601 sends the identifier format 650 to the management computer 501. The management computer 501 saves this identifier format 650 in its internal memory and later uses it when reading the volume information or hierarchy information sent from the storage unit 201, etc. In this manner, matching in identifier format can be maintained between the storage units 201, etc. and the management computer 501.
Now, the way the management computer 501 grasps the capacities of the volumes held in the hierarchically configured group of storage units will be described with reference to FIGS. 7 and 8.
When started up, when requested through the input device 592, or when notified by the storage unit 201, etc. of a change to the configuration, the management computer 501 initiates the process of grasping the storage capacities.
First, the CPU 511 in the management computer 501 executes the volume information collecting program 520 and issues a volume information request to every storage unit connected to it (1101).
In the storage unit 201, 101, or 102, the CPU 221, 121, or 171 receives this request, recognizes the type of the request (1201), executes the volume information request processing program 225, 125, or 175, consults the identifier format table 650 stored in the memory 223, 123, or 173 (1203), prepares the requested volume information in the memory (1205), and finally sends it to the management computer 501 (1207).
The management computer 501 thus collects the volume information 248, 148, and 198 shown in FIG. 2 from the storage units 201, 101, and 102, respectively (1103, 1105). In this case, although the storage unit 201 has only two volumes 211 and 212, it responds to the request from the management computer 501 as if it also owns the volumes that are not contained in it but that are connected to it through the FC interface unit 235.
Next, the CPU 511 in the management computer 501 executes the hierarchy information collecting program 540 and sends a hierarchy information request to every storage unit connected to it (1107). In the storage unit, the CPU receives this request, recognizes the type of the request (1211), executes the hierarchy information request processing program, consults the identifier format table 650 stored in the memory (1215), prepares the hierarchy information in the memory (1217), and finally sends it to the management computer 501 (1219).
Since the storage unit 201 has the hierarchy information request processing program 226 (1213), it can process this request properly. Thus, the management computer receives the hierarchy information 245. shown in FIG. 3 (1109, 1111). On the other hand, the storage units 101 and 102, which do not have the hierarchy information request processing program 226 (1213), their CPUs 121 and 171 send an “error” response (1299).
The management computer 501 then composes a consolidated information table 570 shown in FIG. 6 based on the volume information and the hierarchy information thus collected, and stores it in its memory 513. The consolidated information table 570 consists of an upper-volume column 571 holding information on the higher-level volumes and a lower-volume column 572 holding information on the lower-level volumes.
The algorithm for composing the consolidated information table 570 is as follows.
First, the CPU 511 of the management computer 501 fetches the hierarchy information, and for each pair of volumes having a hierarchical relationship, registers their identifiers under their respective columns in the same row (1113). Further, in the icon number field of the column 571 of the same row, it puts “901,” which means an icon indicating that the volume has a subordinate volume connected to it (1114); in the icon field of the column 572 of the same row, it puts “902,” which means that the volume is subordinate to the upper-level volume (1114).
Next, the CPU 511 fetches the volume information and checks it row by row (1115). If the identifier corresponding to the selected row is already registered (1117), then it registers the capacity in the field next to the registered identifier (1121); otherwise (1117), it registers under the column 571 for a new row, the identifier, capacity, and icon number, which in this case is “903,” meaning that it does not have any subordinate volume (1119).
The CPU 511 repeats the above process for all the volumes whose information has been obtained and for all the rows of the volume information table (1123, 1125, 1126, and 1127). If more than one piece of hierarchy information has been obtained, it will be reflected on the consolidated information table 570. FIG. 6 shows an example of the consolidated information table 570 which is composed of the volume information shown in FIG. 2 and the hierarchy information shown in FIG. 3. The total effective capacity to the computers in the system can therefore be calculated by adding up the values in the capacity column corresponding to upper-level volumes, which is 400 GB in this example (573).
The process of displaying the calculated capacity is now described below, with reference to FIG. 9.
On the display 590 in the management computer 501, volume information and hierarchical information are displayed as shown in FIG. 9. The screen 700 is divided into three display sections 701 through 703. In the display section 701, the information in the upper-volume column 571 of the consolidated information table 570 is displayed. In the display section 702, the information in the lower-volume column 572 of the consolidated information table 570 is displayed. The hierarchical relationships are indicated by icons corresponding to the icon numbers registered in the icon number column (“901” through “903” in FIG. 6). In the display sections 701 and 702, the information displayed consists of, from left to right, the icon, the identifier, and the storage capacity. The display section 703 indicates the total effective capacity to the computers in the computer system. Use of characteristic icons with visually distinct figures and colors allows the system administrator to easily grasp on this screen the status of the volumes in the system at a glance.
To facilitate the viewing of volume and hierarchy information in a system having a large number of volumes, each display section may be provided with a scrolling feature.
By clicking the icon for a volume in the display section 701, it is possible to check whether there exists a volume hierarchically linked with that volume and, if yes, to locate the hierarchically linked volume. The CPU 511 consults the consolidated information table 570 and, if it finds a valid identifier registered in the corresponding row under the lower-volume column 572, highlights the corresponding entry in the display section 702, for example, by changing the color of the icon or the background of the identifier or framing the identifier. Similarly, when the icon for a volume in the display section 702 is clicked, the CPU 511 consults the consolidated information table 570 and, if it finds a valid identifier registered in the corresponding row under the upper-volume column 571, highlights the corresponding entry in the display section 701.
The present embodiment thus makes it possible, in a computer system in which volumes are hierarchically configured, to grasp the total effective capacity to a computer. Further, by dividing the screen on the display into two sections, i.e., one display section 701 for displaying information on the volumes used by the first-level storage unit 201 and the other display section 702 for displaying information on the other volumes, providing icons to represent the rank in hierarchy, and highlighting hierarchical relationships between pairs of volumes spanning the two display sections, it allows the system administrator to easily grasp the hierarchical relationships between volumes and the total effective capacity even when there exist hierarchical relationships between volumes.
Next, another preferred embodiment of the invention will be described with reference to diagrams.
This embodiment uses the same system configuration shown in FIG. 4 but uses formats of volume information and hierarchy information, as well as the display format on the display 590, different from those in the previous embodiment described so far.
The volume information has the format shown in FIG. 10. In response to a volume information request issued by the management computer 501, the storage unit 201, to which other storage units can be connected through the FC interface units 235, sends volume information of the format 247 shown in FIG. 10. The storage unit 101 and the storage unit 102 send volume information of the format 148 shown in FIG. 2(B) and the format 198 shown in FIG. 2(C), respectively, to the management computer 501. As in the previous preferred embodiment described above, the management computer 501 creates the consolidated information table 570 based on the volume information and the hierarchy information thus collected. In doing so, it relies on the lower volume flag shown in FIG. 10. The lower-volume flag indicates the hierarchical relationship between the pair of volumes in its row with three values. The value of “0” means that there is no subordinate volume (i.e., the real volume is contained solely in the first-level storage unit 201); the value of “1” means that the real volume is contained both the first-level storage unit and the second-level storage unit (i.e., they are synchronized by the data synchronization control module 238); the value of “2” means that the real volume is contained solely in the second-level storage unit. Thus, this embodiment is considered an expansion of the first preferred embodiment.
On the display 590 in the management computer 501, a screen 800 shown in FIG. 11 is displayed. The screen 800 has two display sections 801 and 802 which are mutually exclusive. At any given time, either the display section 801 or the display section 802 is displayed. They are switched alternately by a tab 811 and a tab 812: when the tab 811 is clicked, the display section 801 appears on the screen 800; when the tab 812 is clicked, the display section 802 appears. Displayed in the display section 801 is the information in the column 571 of the consolidated information table 570 as shown in FIG. 11(A). The icon number in the consolidated information table 570 is replaced with the real icon corresponding to it.
Displayed in the display section 802 is the information in the column 572 of the consolidated information table 570 as shown in FIG. 11(B). The icon number in the consolidated information table 570 is replaced with the real icon corresponding to it. It is also possible to add a hiding feature such that the tab 812, and hence the display section 802, is hidden from certain administrators registered in the management computer. Such a feature can be used when certain administrators should be made unaware of the hierarchical relationships between volumes.
Other ways of volume information display can also be envisaged. For example, by clicking an icon in the display section 801 it is possible to check whether a subordinate volume exists. If a lookup of the consolidated information table 570 indicates that a valid identifier is found in the same row in the lower-volume column 572, then a subordinate window 820 appears on the display 590, displaying the information on the corresponding subordinate volume, as shown in FIG. 12(A). Alternatively, the information on the corresponding subordinate volume is displayed in a separate display area 803 of the screen 800 as shown in FIG. 12(B). In FIG. 12(B), the two areas that are hierarchically linked are highlighted using shading. In a display area 804, the total effective capacity to the computers in the system is indicated.
A number of other variations of embodiments can also be envisioned. For example, whereas FIG. 4 assumed that the identifier management computer 601 is independent of the management computer 501, these two computers may also be consolidated in one computer, in which case the identifier format request processing program 620 and the identifier format table 650 are stored in the memory 513 in the management computer 501.
A number of embodiments of the present invention have been described. Nevertheless, it should be understood that various modifications may be made without departing from the spirit and scope of the invention, and accordingly that the invention is not limited by the specific illustrated embodiments but only by the scope of the appended claims.

## Claims

1. A management computer for managing, via a management network, capacities of volumes of a storage system, comprising:
a network interface arranged to be coupled to the management network;
a processor coupled to the network interface; and
a memory coupled to the processor;
wherein the processor collects from the storage system, via the network interface, capacity information representing the capacities of volumes of the storage system;
the processor collects, via the network interface, relationship information which defines relationships between the volumes;
the processor sums the capacities of the volumes to obtain a value of a total capacity of the volumes of the storage system;
the processor subtracts from the value of the total capacity, a value of the capacity of any real data volume indicated by the relationship information and accessible by addressing a virtual volume related thereto; and
the processor outputs the result of the subtraction as an effective total capacity of the volumes of the storage system.

2. A management computer according to claim 1,
wherein a first storage apparatus of the storage system has a virtual volume; and
a second storage apparatus of the storage system has a real data volume indicated by the relationship information and accessible by addressing a virtual volume related thereto.

3. A management computer according to claim 2,
wherein the first storage apparatus further has another real data volume not being indicated by the relationship information;
the processor sums the capacities of the virtual volume, the real data volume, and the other real data volume to obtain a value of a total capacity of the volumes of the storage system;
the processor subtracts from the value of the total capacity, a value of the capacity of the real data volume indicated by the relationship information and accessible by addressing the virtual volume related thereto; and
the processor outputs the result of the subtraction as an effective total capacity of the volumes of the storage system.

4. The management computer of claim 2, wherein the relationship information collected by the processor includes virtualization information on the relationship between the virtual volume contained in the first storage apparatus and at least one volume contained in the second storage apparatus.

5. The management computer of claim 2, wherein the processor collects, via the network interface, an identifier of each volume contained in the first and second storage apparatus, each said identifier being formatted according to an identifier format provided by said management computer.

6. The management computer of claim 2, wherein the relationship information collected by the processor includes virtualization information indicating the relationship between an identifier of each virtual volume contained in the first storage system and an identifier of at least one volume contained in the second storage apparatus and hierarchically-linked thereto.

7. The management computer of claim 2, wherein the memory stores an identifier format, and the processor is arranged to control output of the identifier format to each of the first and second storage apparatus in response to an inquiry therefrom for the identifier format stored in the memory, and wherein the capacity and relationship information collected by the processor is composed in accordance with the identifier format stored in the memory.

8. A management method for managing, using a management computer connected to a management network, capacities of volumes of a storage system, comprising the steps of:
collecting, from the storage system via the network interface, capacity information representing the capacities of volumes of the storage system;
collecting, via the network interface, relationship information which defines relationships between the volumes;
summing the capacities of the volumes to obtain a value of a total capacity of the volumes of the storage system;
subtracting from the value of the total capacity, a value of the capacity of any real data volume indicated by the relationship information and accessible by addressing a virtual volume related thereto; and
outputting the result of the subtraction as an effective total capacity of the volumes of the storage system.

9. A management method according to claim 8,
wherein the storage system has first and second storage apparatus; and
the second storage apparatus has a real data volume indicated by the relationship information and accessible by addressing a virtual volume related thereto.

10. A management method according to claim 9,
wherein the first storage apparatus has a virtual volume;
the first storage apparatus further has a real data volume not being indicated by the relationship information;
the summing step sums the capacities of the virtual volume of the first storage apparatus, the real data volume of the first storage apparatus, and the real data volume of the second storage apparatus to obtain a value of a total capacity of the volumes of the storage system;
the subtracting step subtracts from the value of the total capacity, a value of the capacity of the real data volume indicated by the relationship information and accessible by addressing the virtual volume related thereto; and
the outputting step outputs the result of the subtraction as an effective total capacity of the volumes of the storage system.

11. The management method of claim 9, wherein the collected relationship information includes virtualization information on the relationship between the virtual volume contained in the first storage apparatus and at least one volume contained in the second storage apparatus.

12. The management method of claim 9, further comprising the steps of:
providing an identifier format to the storage system; and
collecting from the storage system, via the network interface, an identifier of each volume contained in the first and second storage apparatus, each said identifier being formatted according to the identifier format provided in the providing step.

13. The management method of claim 9, wherein the collected relationship information includes virtualization information indicating the relationship between an identifier of each virtual volume contained in the first storage system and an identifier of at least one volume contained in the second storage apparatus and hierarchically-linked thereto.

14. The management method of claim 9, further comprising the step of:
sending an identifier format to each of the first and second storage apparatus in response to an inquiry therefrom for the identifier format;
wherein the collected capacity and relationship information accords with the identifier format sent in the sending step.