WO2018047349A1 - Computer system and method of managing resource - Google Patents

Abstract

A computer system including a plurality of provision systems that provide resources to be allocated to a user resource and a management computer that manages a resource use state and a resource use fee, wherein the management computer includes a review module for specifying a candidate user resource that requires the alteration of a resource to be allocated thereto and holds fee management information for managing a resource fee determined by a type of resource and a storage location; the review module specifies a use resource that is a resource allocated to the user resource and a first provision system that provides the use resource, calculates the unit cost of a resource provided by the first provision system on the basis of the use state of the use resource and the fee management information, and generates display information for the presentation of a candidate user resource on the basis of the result of comparison of the calculated unit cost and a reference unit cost.

Description

Computer system and resource management method

The field of the present invention relates to optimization of TCO (Total Cost of Ownership) in a system that pays a cost according to the amount of resource used.

In recent years, with the increase of backup data for business systems operated by users and archive data for the purpose of complying with laws and regulations, the need for cold storage devices has increased. Here, the cold storage device refers to a low-cost storage device that stores data with high security and reliability and low access frequency.

As a cold storage device, a library device employing a magnetic tape recording medium and an optical disk recording medium is known (for example, see Patent Document 1). There is also a cold storage device that employs a hard disk drive (HDD). There is also a cold storage system that handles a plurality of types of recording media (see, for example, Patent Document 2). The user needs to appropriately select and operate a different type of recording medium according to the type of data and the data capacity.

In the cold storage device, with the change of technology generation of the recording medium, the next generation drive device cannot access the recording medium of the old technology generation. Generally, the capacity and access speed of the next generation recording medium are improved compared to the old generation recording medium. The bit cost of the next generation recording medium is lower than that of the old generation recording medium, but the price of one storage medium tends to increase in proportion to the amount of increase in capacity.

In addition, the operating cost of the business system, especially the cost for storing data, varies depending on the type and number of recording media used and the usage status such as the amount of data stored on the recording media. For example, when the amount of data stored in a recording medium is small, the operation cost of the business system is lower when data is managed using a cold storage device using HDD instead of a cold storage device using magnetic tape. It is also conceivable to use a cloud service that can be used as a cold storage device.

Estimating operational system operating costs is important not only for users but also for cloud service providers. In a system environment in which a cost calculation method is different for each system that provides a resource, it is required to use the resource in consideration of the operation cost of the business system. On the other hand, the technique described in Patent Document 3 is known.

Patent Document 3 states that “determination of whether or not the archive control system can cause a first archive device having a plurality of resource units (RU) to execute a process that satisfies a request schedule received from a user interface unit. An estimation process including a determination process performed based on one or more registered confirmation schedules is performed, and the request schedule represents a requested process and a requested execution period of each process. This indicates one or more RUs used for processing corresponding to the schedule, each usage period of the one or more RUs, and the usage amount of each of the one or more RUs. The system is based on a comparison between the usage period of each of the one or more RUs to be requested and the requested execution period. Request schedule performs registration processing for newly registering a deterministic schedule for the process to meet the "that have been described.

US Patent Application Publication No. 2013/0290261 JP 2001-34422 A International Publication No. 2016/027370

Costs for cloud services, that is, operating costs for business systems that use systems that provide resources such as storage media vary greatly depending on resource usage.

A system that provides resources to be allocated to a business system is generally composed of a library device, a server device, and a network device. At this time, a rental fee for facilities for installing each device, a rental fee for a warehouse for storing a portable recording medium, and the like are generated. In other words, the operation cost of the business system includes the maintenance cost of the equipment and the warehouse in addition to the purchase cost of the hardware.

Therefore, the operating cost cannot be estimated correctly considering only the hardware price. For example, even if the storage medium has the same purchase cost, the operation cost of the business system varies depending on the storage medium storage cost.

Provide a system and method for grasping the resources to be used so that the operation cost is reduced in consideration of the type of hardware, the amount of resources to be used, and the cost of equipment.

A typical example of the invention disclosed in the present application is as follows. That is, a computer system including a plurality of providing systems that provide resources to be allocated to user resources constituting a user system, and a management computer that manages resource usage status and resource usage charges, the management computer including a processor A review module that has a memory connected to the processor, an interface connected to the processor, and identifies a candidate user resource that needs to be changed among resources allocated from the user resource, The fee management information for managing the fee of the resource determined by the storage location of the resource is held, and when the review module receives a review request from the user, the resource used and the resource to be allocated to the user resource A first providing system that provides a resource for use is specified, and a charge per unit resource amount of the resource provided by the first providing system based on a use state of the used resource and the charge management information And generating display information for presenting the candidate user resource based on a comparison result between the first unit price and the reference unit price.

According to the present invention, the user can specify the user resource to which the expensive resource is allocated based on the display based on the display information. Further, since the user can select an appropriate resource, that is, a providing system based on the display information, the operation cost can be kept low. Problems, configurations, and effects other than those described above will become apparent from the following description of embodiments.

1 is a diagram illustrating a configuration example of a computer system according to a first embodiment. FIG. 2 is a diagram illustrating an example of a hardware configuration and a software configuration of an AP server according to the first embodiment. FIG. 2 is a diagram illustrating an example of a hardware configuration and a software configuration of a VTL server according to the first embodiment. 2 is a diagram illustrating an example of a hardware configuration and a software configuration of a terminal according to Embodiment 1. FIG. FIG. 3 is a diagram illustrating an example of a hardware configuration and a software configuration of a management server according to the first embodiment. FIG. 2 is a diagram illustrating an example of a hardware configuration and a software configuration of the tape library apparatus according to the first embodiment. 3 is a diagram illustrating a logical configuration of a virtual tape library device provided by a VTL server according to the first embodiment and a relationship between the virtual tape library device and a shared storage device. FIG. 3 is a diagram illustrating an example of storage medium management information included in an Inventory management database according to Embodiment 1. FIG. It is a figure which shows an example of the expense management information contained in the Inventory management database of Example 1. FIG. 6 is a diagram illustrating an example of migration management information included in an Inventory management database according to Embodiment 1. FIG. It is a figure which shows an example of the budget management information contained in the Inventory management database of Example 1. It is a figure which shows an example of the fee information of Example 1. It is a figure which shows an example of the operation screen displayed by the browser of Example 1. FIG. It is a figure which shows an example of the operation screen displayed by the browser of Example 1. FIG. 6 is a flowchart illustrating an example of processing executed by an AP server according to the first embodiment. 6 is a flowchart illustrating an example of processing executed by the VTL server according to the first embodiment. 6 is a flowchart illustrating an example of processing executed by the terminal according to the first embodiment. 6 is a flowchart illustrating processing executed by the management server according to the first embodiment. 6 is a flowchart illustrating an example of processing executed by the management server according to the first embodiment. It is a figure which shows an example of the result display screen displayed by the display data which the management server of Example 1 produces | generates. It is a figure which shows an example of the result display screen displayed by the display data which the management server of Example 1 produces | generates. It is a figure which shows an example of the comparison model of the capacity unit price of Example 1. FIG. 6 is a flowchart illustrating an example of processing executed by the management server according to the first embodiment. 6 is a flowchart illustrating an example of processing executed by the physical tape library apparatus according to the first embodiment. It is a figure which shows the structural example of the computer system of Example 2. FIG.

Embodiments of the present invention will be described with reference to the drawings. In each figure, the same reference numerals are given to common configurations.

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

The computer system includes a management server 100, a terminal 101, an application (AP) server 102, a physical tape library device 103, a virtual tape library (VTL) server 104, a shared storage device 105, and a storage device 106.

Management server 100, terminal 101, AP server 102, and VTL server 104 are connected to network 110. Further, the physical tape library device 103 and the storage device 106 are connected to the management server 100.

The terminal 101 is a computer that operates the management server 100 and the like.

The AP server 102 is a computer on which an application for operating stored data operates. The AP server 102 is a computer that constitutes a user-side system. Note that the user-side system may include another computer such as a Web server. The AP server 102 executes data write processing and read processing on a physical tape recognized by the AP server 102. Here, the physical tape recognized by the AP server 102 is realized by using resources provided by the physical tape library apparatus 103 and the shared storage apparatus 105. In the following description, a physical tape recognized by the AP server 102 is referred to as a user tape (user resource).

The physical tape library device 103 is a storage device that manages a physical tape 611 (see FIG. 6) that stores data. The physical tape library apparatus 103 is a system that provides physical resources themselves. The physical tape 611 is a portable storage medium. Therefore, as indicated by the arrows in FIG. 1, the physical tape 611 is loaded into a warehouse (not shown) or the physical tape 611 is unloaded from the warehouse as necessary. It should be noted that the physical tape 611 may be entered and exited automatically using a mechanical mechanism or manually.

The VTL server 104 is a computer that implements the virtual tape library device 700 (see FIG. 7). The shared storage device 105 is a storage device that stores data serving as a substance of a virtual tape 711 (see FIG. 7) managed by the virtual tape library device 700. The shared storage device 105 includes a controller and a plurality of storage media such as HDDs or SSDs. In this embodiment, the shared storage device 105 includes an HDD. The VTL server 104 and the shared storage device 105 are systems that provide virtual resources.

In this embodiment, a tape is used as an example of a portable storage medium, but an optical disk, a removable HDD, or the like may be used.

In the following description, when the physical tape 611 and the virtual tape 711 are not distinguished, they are simply described as tapes. The tape is a resource that is actually allocated to the user tape. Therefore, in Example 1, tape is synonymous with resource.

The configuration of each device included in the computer system will be described with reference to FIGS.

FIG. 2 is a diagram illustrating an example of a hardware configuration and a software configuration of the AP server 102 according to the first embodiment.

The AP server 102 includes a processor 201, a memory 202, an input / output interface (IF) 203, and a network interface card (NIC) 204. Each hardware configuration is connected to each other via a data bus 210.

The processor 201 executes a program stored in the memory 202. The functions of the AP server 102 can be realized by the processor 201 executing the program. In the following description, when a process is described with a module and a function unit as a subject, it indicates that a program for realizing the module and the function unit is being executed by the processor 201.

The memory 202 stores a program executed by the processor 201 and information necessary for the program. The memory 202 includes a work area that is temporarily used by the program. The memory 202 of this embodiment stores a program that realizes an application (AP) 211 and data 212 that the AP 211 uses. Data 212 is stored on the tape at a predetermined timing. The memory 202 may store a program such as an operating system (OS) and other information.

The AP 211 accesses the virtual tape 711 managed by the shared storage device 105 via the virtual tape library device 700 by issuing a command to the VTL server 104.

As the commands issued by the AP 211, mtx commands and mt commands used in Linux can be considered. The mt command is a command for instructing the tape library apparatus to write and read data. The mtx command is an instruction for inserting a storage medium into the tape drive to the tape library apparatus. Or it is a command which instruct | indicates taking out of the storage medium from a tape drive. It may be a dedicated command issued by a general backup module and archive module.

The input / output IF 203 is an interface for connecting to the display device 205 and the input device 206. The display device 205 is a device that displays an operation screen, a processing result, and the like of the AP server 102. For example, a display and a touch panel are conceivable. The input device 206 is a device that inputs commands and data to the AP server 102. For example, a keyboard, a mouse, a touch panel, and the like are conceivable.

The NIC 204 is an interface for connecting to the network 110.

FIG. 3 is a diagram illustrating an example of a hardware configuration and a software configuration of the VTL server 104 according to the first embodiment.

The VTL server 104 includes a processor 301, a memory 302, an input / output IF 303, and a NIC 304. Each hardware configuration is connected to each other via a data bus 310. Further, the display device 305 and the input device 306 are connected to the VTL server 104 via the input / output IF 303.

Since the processor 301, the memory 302, the input / output IF 303, and the NIC 304 are the same as the processor 201, the memory 202, the input / output IF 203, and the NIC 204, description thereof is omitted.

The memory 302 stores a program for realizing the VTL control module 311. The VTL control module 311 provides the virtual tape library device 700 to the AP 211 and controls access between the AP 211 and the shared storage device 105.

FIG. 4 is a diagram illustrating an example of a hardware configuration and a software configuration of the terminal 101 according to the first embodiment.

The terminal 101 includes a processor 401, a memory 402, an input / output IF 403, and a NIC 404. Each hardware configuration is connected to each other via a data bus 410. A display device 405 and an input device 406 are connected to the terminal 101 via the input / output IF 403.

Since the processor 401, the memory 402, the input / output IF 403, and the NIC 404 are the same as the processor 201, the memory 202, the input / output IF 203, and the NIC 204, description thereof is omitted.

The memory 402 stores a program for realizing the browser 411. In this embodiment, the management server 100 is operated using the browser 411. The browser 411 may be a program built in the OS.

FIG. 5 is a diagram illustrating an example of a hardware configuration and a software configuration of the management server 100 according to the first embodiment.

The management server 100 includes a processor 501, a memory 502, an input / output IF 503, a NIC 404, and an HBA 505. Each hardware configuration is connected to each other via a data bus 510. A display device 506 and an input device 507 are connected to the management server 100 via the input / output IF 503.

Since the processor 501, the memory 502, the input / output IF 503, and the NIC 504 are the same as the processor 201, the memory 202, the input / output IF 203, and the NIC 204, description thereof is omitted. The HBA 505 is an interface for connecting to the physical tape library device 103 and the storage device 106. The HBA 505 may be an interface compliant with, for example, a SCSI (Small Computer System Interface) standard.

The memory 502 stores a program for realizing the management module 511, the review module 512, and the transfer module 513, and fee information 521.

The management module 511 controls the entire management server 100. The review module 512 presents user resources that need to be changed according to instructions from the user. Here, the transfer module 513 controls data transfer between resources.

In addition, the management module 511, the review module 512, and the transfer module 513 may implement the functions of each module as one module, or may divide one module into a plurality of modules. For example, the review module 512 may have the function of the transfer module 513.

The fee information 521 is information indicating the usage fee of the resource currently allocated to the user resource, and is generated by the review module 512. The fee information 521 may be deleted after the review module 512 finishes the process.

FIG. 6 is a diagram illustrating an example of a hardware configuration and a software configuration of the physical tape library apparatus 103 according to the first embodiment.

The physical tape library apparatus 103 includes a controller 601, a tape drive 602, and a storage space 603. The protocol applied to the physical tape library apparatus 103 may be any protocol such as a SCSI protocol and a file sharing protocol. Note that NFS, CIFS, REST, and the like are known as file sharing protocols.

The controller 601 controls the entire physical tape library apparatus 103 and also controls the transport of the physical tape 611 between the tape drive 602 and the storage space 603. The controller 601 includes a CPU, a memory, and an interface (not shown). The memory stores a program that realizes a module that controls the physical tape library apparatus 103.

Note that the controller 601 may be divided into a transport controller and a HUB. In this case, the HUB is used as an interface for connecting to the outside, and the transport controller and the tape drive 602 are connected to the HUB. When the HUB receives a request from the management server 100, the HUB transfers the request to the tape drive 602 or the transport controller. As the transport controller, a controller corresponding to SCSI Media Changer Commands (SMC) can be considered. Note that the physical tape library device 103 may be connected to other devices via an interface dedicated to SCSI, or may be connected to other devices via a network such as a SAN or a LAN.

The tape drive 602 inserts the physical tape 611 and writes / reads data to / from the physical tape 611. The tape drive 602 can be a tape drive compatible with SCSI Stream Commands (SSC).

The storage space 603 is a space in which the physical tape 611 is stored. As shown by the arrows in FIG. 6, the physical tape 611 stored in the storage space 603 is loaded by the controller 601 and inserted into the tape drive 602. Further, as indicated by the arrow in FIG. 6, the physical tape 611 inserted into the tape drive 602 is unloaded by the controller 601 and stored in the storage space 603 from the tape drive 602.

FIG. 7 is a diagram illustrating a logical configuration of the virtual tape library apparatus 700 provided by the VTL server 104 according to the first embodiment and a relationship between the virtual tape library apparatus 700 and the shared storage apparatus 105.

The virtual tape library apparatus 700 includes a virtual controller 701, a virtual tape drive 702, and a virtual storage space 703. The virtual controller 701, the virtual tape drive 702, and the virtual storage space 703 correspond to the virtual controller 601, the tape drive 602, and the storage space 603. In this embodiment, the virtual controller 701 connects to other devices based on the iSCSI protocol. In addition, it is not limited to the protocol used.

As shown in FIG. 7, the data that is the substance of the virtual tape 711 managed by the virtual tape library apparatus 700 is stored in the shared storage apparatus 105.

The shared storage device 105 has a controller (not shown) and a plurality of HDDs. In this embodiment, the shared storage device 105 manages the virtual tape 711 by dividing the storage area into two, an On-Load directory 721 and an Off-Load directory 722.

The On-Load directory 721 is a directory for storing data of the virtual tape 711 inserted into the virtual tape drive 702. The Off-Load directory 722 is a directory for storing data of the virtual tape 711 stored in the virtual storage space 703.

The loading of the virtual tape 711 between the virtual tape drive 702 and the virtual storage space 703 corresponds to the loading of the virtual tape 711 between the On-Load directory 721 and the Off-Load directory 722. The unloading of the virtual tape 711 between the virtual tape drive 702 and the virtual storage space 703 corresponds to the unloading of the virtual tape 711 between the On-Load directory 721 and the Off-Load directory 722.

Note that the storage area of the shared storage device 105 does not have to be divided into two directories, but only needs to be able to manage the state (storage location) of the virtual tape 711.

The storage device 106 connected to the management server 100 has the same hardware configuration as that of the shared storage device 105, and a description thereof will be omitted.

Next, information included in the Inventory management database managed by the storage apparatus 106 will be described with reference to FIGS.

FIG. 8 is a diagram illustrating an example of the storage medium management information 800 included in the inventory management database according to the first embodiment.

Storage medium management information 800 is information for managing tapes (physical tape 611 and virtual tape 711) that are resources. The storage medium management information 800 includes a record including a storage medium ID 801, a storage medium type 802, a physical storage medium type 803, a used capacity 804, a department ID 805, a use start date 806, and a storage location type 808.

Storage medium ID 801 stores identification information for uniquely identifying a tape in the computer system. For example, a volume tag or the like is stored in the storage medium ID 801.

Storage medium type 802 stores the type of storage medium (user resource) handled by the AP server 102. For example, tape identification information recognized by the AP server 102 is stored in the storage medium type 802.

The physical storage medium type 803 stores information indicating whether the tape is a physical tape 611 or a virtual tape 711. When the tape is the physical tape 611, the same identification information as the storage medium type 802 is stored in the physical storage medium type 803, and “HDD” is stored in the physical storage medium type 803 when the tape is the virtual tape 711. .

The used capacity 804 stores the capacity of data stored on the tape.

The department ID 805 stores identification information of a user who operates the AP server 102, that is, a user who uses the tape.

The use start date 806 stores the use start date of the tape. When the use start date 806 is blank, it indicates that the tape is not used.

The storage location type 808 stores a location (storage location) where the tape exists. In this embodiment, the storage location type 808 includes “on-site” indicating that a tape exists in the device that provides the resource, and “off-site” that indicates that no tape exists in the device that provides the resource. "Is stored. The storage location type 808 may store information indicating a specific tape location.

FIG. 9 is a diagram illustrating an example of the expense management information 900 included in the inventory management database according to the first embodiment.

Cost management information 900 is information for managing resource usage charges. The cost management information 900 includes a record including a storage medium type 901, a storage location type 902, a charging unit capacity 903, a charge 904, a storage capacity 905, a maximum usage period 906, and an expiration date 907.

The storage medium type 901 is the same as the storage medium type 802. The storage location type 902 is the same as the storage location type 808. Since the fee varies depending on the storage location of the storage medium, the record of the expense management information 900 includes not only the storage medium type 901 but also the storage location type 902.

The charging unit capacity 903 stores the usage amount of the resource that is a charging unit. When the storage medium is a physical tape 611, the charge is made for each physical tape. Therefore, the storage capacity of one physical tape 611 is stored in the charging unit capacity 903 of the second and third records in FIG.

The charge 904 stores a charge that is a reference for calculating the capacity unit price. In the fee 904, an amount including a storage medium purchase fee, a facility location cost, a storage medium storage location cost, and the like is registered. Therefore, when the storage location is different, the charge is different even for the same type of storage medium.

The cost of the location of the facility and the storage location of the storage medium is, for example, the depreciation of the server device, library device, and network device included in the data center, the rent of the data center, and the warehouse that stores the storage medium. Indicates the rent. However, since the above-described cost depends on the total number of hardware such as storage media and periodically varies, the policy may be set so that the average value or the maximum value of the cost is used.

The storage capacity 905 stores the storage capacity of one storage medium, that is, the capacity of data that can be stored in one storage medium.

The maximum usage period 906 stores the life of the storage medium. The maximum use period 906 is used when depreciation is calculated from the purchase amount of the storage medium.

The validity period 907 stores the validity period of the information registered in the record. Since the purchase amount of the storage medium varies depending on the purchase time, the expiration date for using the information registered in the record is managed using the expiration date 907.

FIG. 10 is a diagram illustrating an example of the migration management information 1000 included in the inventory management database according to the first embodiment.

The migration management information 1000 is information for managing the relationship of resources to which data has been migrated, and is used to specify a physical tape 611 necessary for recovery of data stored in the virtual tape 711. The migration management information 1000 includes a record including a migration source storage medium ID 1001, a migration destination storage medium ID 1002, and an offset 1003.

The migration source storage medium ID 1001 is identification information of the migration source storage medium. The migration source storage medium ID 1001 stores the same identification information as the storage medium ID 801.

The migration destination storage medium ID 1002 is identification information of the migration destination storage medium. The migration destination storage medium ID 1002 stores the same identification information as the storage medium ID 801.

The offset 1003 is an offset indicating a start position when data is written to the migration destination storage medium. Writing data to the tape starts from the end of the data stored on the tape. That is, data is written sequentially. Position information when the tape drive 602 installs the tape head at the end position of the data is registered in the offset 1003. Note that the location information can be acquired using a command provided by the OS or an API (Application Programming Interface).

FIG. 11 is a diagram illustrating an example of the budget management information 1100 included in the inventory management database according to the first embodiment.

Budget management information 1100 is information for managing a user's budget. The budget management information 1100 includes a record including a department ID 1101, a budget 1102, an actual record 1103, a capacity unit price budget 1104, and a target year / month 1105.

The department ID 1101 is the same as the department ID 805.

The budget 1102 stores the total amount of the budget. In this embodiment, the budget 1102 stores the budget amount per month. In addition, not only a monthly amount but also a daily amount or an annual amount, etc.

The result 1103 stores the amount used.

The capacity unit price budget 1104 stores a capacity unit price set as a budget.

Target year / month 1105 stores the year, month, etc. to which the budget is applied. If the target year / month 1105 is blank, it indicates that the budget corresponding to the record is applied throughout the year.

Next, fee information 521 generated by the review module 512 will be described with reference to FIG.

FIG. 12 is a diagram illustrating an example of fee information 521 according to the first embodiment.

The fee information 521 is information indicating the capacity unit price of each resource. The fee information 521 includes a record including a storage medium ID 1201, a used capacity 1202, a capacity unit price 1203, a department ID 1204, a storage medium type 1205, and a physical storage medium type 1206.

Storage medium ID 1201, department ID 1204, storage medium type 1205, and physical storage medium type 1206 are the same as storage medium ID 801, department ID 805, storage medium type 802, and physical storage medium type 803.

The used capacity 1202 stores the capacity of data currently stored on the tape corresponding to the storage medium ID 1201.

The capacity unit price 1203 stores the capacity unit price of the tape. Generally, the capacity unit price of a storage medium indicates a bit cost calculated by dividing the purchase price of the storage medium by the capacity. However, the capacity unit price of the present embodiment is a value calculated based on a charge 904 including a storage medium purchase fee, facility cost, storage medium storage cost, and the like. Therefore, the capacity unit price of this embodiment is a value different from general bit cost.

Next, an operation screen displayed by the browser 411 will be described with reference to FIGS.

FIG. 13 is a diagram illustrating an example of an operation screen 1300 displayed by the browser 411 according to the first embodiment.

The operation screen 1300 shown in FIG. 13 includes a first operation area and a second operation area. In FIG. 13, the respective operation areas are shown separated by dotted lines.

The first operation area is an area for registering a record in the budget management information 1100, and includes an input field 1301 and a registration button 1302. The user sets a value in the input field 1301 and presses a registration button 1302. In this case, a budget registration request is transmitted to the management server 100 via the browser 411.

The second operation area is an area for registering a record in the expense management information 900, and includes an input field 1311 and a registration button 1312. The user sets a value in the input field 1311 and presses the registration button 1312. In this case, a cost registration request is transmitted to the management server 100 via the browser 411.

FIG. 14 is a diagram illustrating an example of an operation screen 1400 displayed by the browser 411 according to the first embodiment.

The operation screen 1400 shown in FIG. 14 includes a third operation area, a fourth operation area, and a fifth operation area. In FIG. 14, the respective operation areas are shown separated by dotted lines.

The third operation area is an area for registering values necessary for processing executed by the review module 512, and includes an input field 1401, a status display button 1402, and a capacity unit price display button 1403. The “range” included in the input field 1401 is an input field for designating the number of tapes to be displayed. An “assessment standard” included in the input field 1401 is an input field for designating an assessment standard for evaluating the unit price of a resource. In this embodiment, “budget unit price” and “storage medium type” can be selected. When “storage medium type” is selected, a “setting value” for inputting a storage medium type and a storage location type for designating a storage medium (tape) to be compared is validated. The user sets a value in the input field 1401 and presses the status display button 1402 or the capacity unit price display button 1403. In this case, a review request is transmitted to the management server 100 via the browser 411. Note that the review request includes information indicating the type of the operated button. The review request includes the value input in the “set value” as comparison information.

The fourth operation area is an area for registering values necessary for data migration processing between resources, and includes an input field 1411 and a migration button 1412. The user sets a value in the input field 1411 and presses the transition button 1412. In this case, a migration request is transmitted to the management server 100 via the browser 411.

The fifth operation area is an area for updating the storage medium management information 800 and includes an input field 1421 and an update button 1422. The user sets a value in the input field 1421 and presses the update button 1422. In this case, an update request is transmitted to the management server 100 via the browser 411.

Note that the browser 411 may display one operation area in one window or may display a plurality of operation areas in one window.

Next, processing of the devices constituting the computer system will be described.

FIG. 15 is a flowchart illustrating an example of processing executed by the AP server 102 according to the first embodiment.

The AP 211 of the AP server 102 executes processing described below.

When the AP 211 receives an input from the user (step S1501), the AP 211 determines whether the input is a load instruction for the virtual tape 711 (step S1502).

When it is determined that the input is a load instruction for the virtual tape 711, the AP 211 transmits a load command to the virtual tape library apparatus 700 (step S1505). Thereafter, the AP 211 ends the process.

When it is determined that the input is not a load instruction for the virtual tape 711, the AP 211 determines whether the input is a write instruction for the virtual tape 711 (step S1503).

When it is determined that the input is a write instruction for the virtual tape 711, the AP 211 transmits data 212 to be written and a write command to the virtual tape library device 700 (step S1504). Thereafter, the AP 211 ends the process.

If it is determined that the input is not a write instruction for the virtual tape 711, the AP 211 determines whether the input is a read instruction for the virtual tape 711 (step S1504).

When it is determined that the input is a read instruction for the virtual tape 711, the AP 211 transmits a read command to the virtual tape library apparatus 700 (step S1507). Thereafter, the AP 211 ends the process.

If it is determined that the input is not a read instruction for the virtual tape 711, the AP 211 determines that the input is an unload instruction for the virtual tape 711, and transmits an unload instruction to the virtual tape library apparatus 700 (step S1508). ). Thereafter, the AP 211 ends the process.

FIG. 16 is a flowchart illustrating an example of processing executed by the VTL server 104 according to the first embodiment.

The VTL control module 311 of the VTL server 104 executes processing described below.

When the VTL control module 311 receives an instruction from the AP server 102 (step S1601), the VTL control module 311 determines whether the instruction is a load instruction (step S1602).

If it is determined that the instruction is a load instruction, the VTL control module 311 moves the designated virtual tape 711 to the On-Load directory 721 (step S1605). Thereafter, the VTL control module 311 ends the process.

If it is determined that the instruction is not a load instruction, the VTL control module 311 determines whether or not the instruction is a write instruction (step S1603).

If it is determined that the command is a write command, the VTL control module 311 writes the data 212 to the designated virtual tape 711 (step S1606). Thereafter, the VTL control module 311 ends the process.

Specifically, the VTL control module 311 transfers data to the storage area of the shared storage device 105 corresponding to the designated virtual tape 711.

If it is determined that the command is not a write command, the VTL control module 311 determines whether the command is a read command (step S1604).

If it is determined that the command is a read command, the VTL control module 311 reads data from the designated virtual tape 711 (step S1607). Thereafter, the VTL control module 311 ends the process.

Specifically, the VTL control module 311 reads data from the storage area of the shared storage device 105 corresponding to the designated virtual tape 711 and transmits the read data to the AP server 102.

If it is determined that the command is not a read command, the VTL control module 311 determines that the command is an unload command, and moves the designated virtual tape 711 to the Off-Load directory 722 (step S1608). Thereafter, the VTL control module 311 ends the process.

FIG. 17 is a flowchart illustrating an example of processing executed by the terminal 101 according to the first embodiment.

The browser 411 of the terminal 101 executes processing described below.

When the browser 411 receives display data for displaying the operation screens 1300 and 1400 from the management server 100 (step S1701), the browser 411 displays the operation screens 1300 and 1400 on the display device 205 based on the display data. Wait for input.

When the browser 411 receives an operation from the user via the input device 206 (step S1702), the browser 411 transmits a request to the management server 100 (step S1703).

In this embodiment, any of a budget registration request, a cost registration request, a migration request, an update request, and a review request is transmitted as a request. For example, when the status display button 1402 on the operation screen 1400 is pressed, the browser 411 transmits a review request to the management server 100.

When the browser 411 receives a result for the request from the management server 100 (step S1704), the browser 411 displays the result on the display device 205 (step S1705). Thereafter, the browser 411 ends the process. The result includes display data for displaying a screen as shown in FIG.

FIG. 18 is a flowchart illustrating processing executed by the management server 100 according to the first embodiment.

The management module 511 executes processing described below.

The management module 511 transmits display data for displaying the operation screen 1300 or the operation screen 1400 to the terminal 101 (step S1801). The management module 511 waits for a request from the terminal 101.

When the management module 511 receives a request from the terminal 101 (step S1802), the management module 511 determines whether the request is a budget registration request, a cost registration request, or an update request (step S1803).

If it is determined that the request is a budget registration request or an expense registration request, the management module 511 updates the Inventory management database (step S1806). Thereafter, the management module 511 ends the process.

Specifically, when the request is a budget registration request, the management module 511 accesses the storage apparatus 106 and adds a record to the budget management information 1100. The value input in the input field 1301 is set in the added record. If the request is an expense registration request, the management module 511 accesses the storage device 106 and adds a record to the expense management information 900. The value input in the input field 1311 is set in the added record.

If it is determined that the request is neither a budget registration request nor an expense registration request, the management module 511 determines whether the request is a review request (step S1804).

When it is determined that the request is a review request, the management module 511 calls the review module 512 (step S1807). Thereafter, the management module 511 ends the process.

If it is determined that the request is not a review request, the management module 511 determines whether the request is a migration request (step S1805).

If it is determined that the request is a migration request, the management module 511 calls the transfer module 513 (step S1808). Thereafter, the management module 511 ends the process.

If it is determined that the request is not a migration request, the management module 511 determines that the request is an update request, and updates the Inventory management database (step S1809). Thereafter, the management module 511 ends the process.

For example, in the case of an update request instructing addition of the virtual tape 711, the management module 511 accesses the storage device 106 and adds a record to the storage medium management information 800. In the record, the value input in the input field 1421 is set. When the physical storage medium type is HDD, the management module 511 generates a virtual tape 711 in the Off-Load directory 722 of the shared storage device 105.

For example, in the case of an update request instructing deletion of the virtual tape 711, the management module 511 accesses the storage device 106 and deletes the record from the storage medium management information 800 based on the value input in the input field 1421. In addition, the management module 511 releases the storage area corresponding to the virtual tape 711 from the shared storage device 105.

FIG. 19 is a flowchart illustrating an example of processing executed by the management server 100 according to the first embodiment. FIG. 20 is a diagram illustrating an example of a result display screen 2000 displayed by display data generated by the management server 100 according to the first embodiment. FIG. 21 is a diagram illustrating an example of a result display screen 2100 displayed by display data generated by the management server 100 according to the first embodiment. FIG. 22 is a diagram illustrating an example of a capacity unit price comparison model according to the first embodiment.

The review module 512 of the management server 100 executes processing described below.

The review module 512 starts processing when called from the management module 511. First, the review module 512 generates fee information 521 (step S1901). Specifically, the following processing is executed.

The review module 512 acquires the department ID included in the review request. The review module 512 refers to the storage medium management information 800 and identifies a record in which the department ID 805 matches the acquired department ID.

The review module 512 selects one target record from the identified records. The review module 512 refers to the cost management information 900 and searches for a record that matches the storage medium type 802 and the storage location type 808 of the record in which the storage medium type 901 and the storage location type 902 are selected.

The review module 512 uses the record selected from the storage medium management information 800 and the record retrieved from the expense management information 900 to calculate the capacity unit price. In this embodiment, when the equation (1) is satisfied, the unit capacity price is calculated using the equation (3), and when the equation (2) is satisfied, the unit capacity price is calculated using the equation (4).

The review module 512 generates empty fee information 521 in the work area of the memory 502 when the fee information 521 does not exist. The review module 512 adds a record to the charge information 521, and selects from the storage medium management information 800 for the storage medium ID 1201, used capacity 1202, department ID 1204, storage medium type 1205, and physical storage medium type 1206 of the added record. Set the value of the recorded record. Also, the review module 512 sets the calculated capacity unit price in the capacity unit price 1203 of the added record.

The review module 512 executes the same processing for all the specified records. Through the above processing, fee information 521 as shown in FIG. 12 is generated. The above is the description of the process in step S1901.

Next, the review module 512 determines whether or not the status display button 1402 has been operated (step S1902).

If it is determined that the status display button 1402 has been operated, the review module 512 generates display data based on the fee information 521 (step S1905). The review module 512 ends the process after transmitting the display data to the terminal 101.

For example, the review module 512 groups the tapes allocated to the user tape based on the storage medium type 1205, the physical storage medium type 1206, and the like, and generates display data for displaying the grouping result. A result display screen 2000 as shown in FIG. 20 is displayed on the display device 405 of the terminal 101 based on the display data.

In the result display screen 2000, the tapes are divided into three groups. Specifically, a group in which data exists only on the physical tape 611 (group 1), a group in which data exists on the physical tape 611 and the virtual tape 711 (group 2), and a group in which data exists only on the virtual tape 711 (group) 3) Three groups. Note that the used capacity or the like may be displayed on the tape displayed on the result display screen 2000.

The review module 512 refers to the migration management information 1000, searches the migration source storage medium ID 1001 for a record that matches the storage medium ID 1201 of the record included in the charge information 521, and includes the search result in the display data. Good.

If it is determined that the status display button 1402 has not been operated, the review module 512 determines that the capacity unit price display button 1403 has been operated, and sorts the records of the charge information 521 in descending order of the capacity unit price (step S1903). ).

The review module 512 generates display data using the charge information 521 in which the records are sorted (step S1904). The review module 512 ends the process after transmitting the display data to the terminal 101. For example, the following processing is executed.

When the “assessment type” included in the input field 1401 is a storage medium type, the processing from (1) to (5) is executed.

(1) The review module 512 refers to the cost management information 900, and the storage medium type 901 and the storage location type 902 match the storage medium type and storage location type input in the “setting value” included in the input field 1401. Search for records.

(2) The review module 512 selects records for the “range” value included in the input field 1401 from the charge information 521. Here, it is assumed that the records are selected in order from the top record. The review module 512 selects one target record.

(3) The review module 512 calculates the capacity unit price of the comparison target storage medium for the target record using the formulas (1) to (4). Note that the value of the used capacity 1202 of the target record is used for (used capacity) in the expressions (1) to (4). The review module 512 compares the capacity unit price 1203 of the target record with the capacity unit price (reference unit price) of the comparison target storage medium.

(4) The review module 512 executes the same processing for all the records selected from the charge information 521.

(5) The review module 512 generates display data based on the selected record and the comparison result.

When a value is set for “budget unit price” included in the input field 1401, the processing from (6) to (10) is executed.

(6) The review module 512 refers to the budget management information 1100 and searches for a record in which the department ID 1101 matches the value entered in the “department ID” of the input field 1401.

(7) The review module 512 selects records for the “range” value included in the input field 1401 from the charge information 521. Here, it is assumed that the records are selected in order from the top record. The review module 512 selects one target record.

(8) The review module 512 compares the capacity unit price 1203 of the target record with the capacity unit price budget 1104 (reference unit price) of the retrieved record.

(9) The review module 512 executes the same processing for all the records selected from the charge information 521.

(10) The review module 512 generates display data based on the selected record and the comparison result.

Through the above processing, a result display screen 2100 as shown in FIG. 21 is displayed on the display device 405 of the terminal 101 based on the display data.

The result display screen 2100 is divided into a group of in-use tapes recommended to be changed (group 1) and a group of in-use tapes recommended to be maintained (group 2).

When the capacity unit price 1203 of the target record is equal to or greater than the capacity unit price (or capacity unit price budget 1104) of the comparison target storage medium, the user tape to which the tape corresponding to the record is assigned is classified into group 1. When the capacity unit price 1203 of the target record is lower than the capacity unit price (or capacity unit price budget 1104) of the comparison target storage medium, the user tape to which the tape corresponding to the record is assigned is classified into group 2. Group 1 displays the total used capacity of user tapes included in group 1. The result display screen 2100 displays the user tape identifier and usage status, and a message for the user tape. Note that the message may be displayed only for the tape that satisfies the condition.

Note that the screens shown in FIGS. 20 and 21 are examples, and the present invention is not limited thereto. For example, a screen for displaying a message for a group as shown in FIG. 20 may be used.

As shown in FIG. 22, physical tapes and virtual tapes have different bit costs. The HDD that realizes the virtual tape has a constant bit unit price because the setting of the storage area is flexible. On the other hand, in the case of a physical tape, the storage area cannot be set flexibly as in the case of an HDD, and costs for one tape are required. Therefore, the capacity unit price decreases as the used capacity increases. Thus, there is a cross point where the capacity unit price is reversed depending on the resource type.

The capacity unit price of this example also shows the same characteristics as in FIG. In the present embodiment, it is possible to give advice focusing on the characteristics. The user can appropriately select the resource without being aware of the relationship as shown in FIG.

FIG. 23 is a flowchart illustrating an example of processing executed by the management server 100 according to the first embodiment.

The transfer module 513 of the management server 100 executes processing described below.

The transfer module 513 starts processing when called from the management module 511. At this time, the review module 512 acquires the migration source storage medium ID and the migration destination storage medium ID included in the migration request.

The transfer module 513 determines whether the migration source storage medium is the virtual tape 711 and the migration destination storage medium is the virtual tape 711 (step S2301).

Specifically, the transfer module 513 refers to the storage medium management information 800 and searches for a record in which the storage medium ID 801 matches the source storage medium ID and a record in which the storage medium ID 801 matches the destination storage medium ID. The transfer module 513 determines the type of the storage medium based on the physical storage medium type 803 of each retrieved record. The same processing is executed also in step S2302 and step S2303 described later.

If it is determined that the condition of step S2301 is satisfied, the transfer module 513 stores the data stored in the migration source virtual tape 711 in the migration destination virtual tape 711 (step S2304). Thereafter, the transfer module 513 ends the process. Specifically, the following processing is executed.

The transfer module 513 transmits a read command and a write command to the shared storage device 105. The read command and the write command include commands such as mt command and mtx command. The read command includes identification information of a tape from which data is read, and the write command includes identification information of a tape from which data is to be written.

The transfer module 513 adds a record to the migration management information 1000, sets the migration source storage medium ID in the migration source storage medium ID 1001 of the added record, and sets the migration destination storage medium ID in the migration destination storage medium ID 1002. In addition, the transfer module 513 sets a predetermined value for the offset 1003 of the added record.

The transfer module 513 searches the storage medium management information 800 for a record corresponding to the migration destination virtual tape 711 and acquires the storage location type 808 of the searched record. Also, the transfer module 513 searches for a record corresponding to the migration source virtual tape 711, sets the migration destination storage medium ID in the storage medium ID 801 of the record, and sets the migration destination in the storage location type 808 of the record. The storage location type 808 of the record corresponding to the virtual tape 711 is set. Note that the method of updating the storage medium management information 800 is an example and is not limited to this.

When it is determined that the condition of step S2301 is not satisfied, the transfer module 513 determines whether the migration source storage medium is the virtual tape 711 and the migration destination storage medium is the physical tape 611 ( Step S2302).

If it is determined that the condition of step S2302 is satisfied, the transfer module 513 transmits a load instruction for the migration destination physical tape 611 to the physical tape library device 103, and transfers the data stored in the migration source virtual tape 711 to the migration destination. Is stored in the physical tape 611 (step S2504). Thereafter, the transfer module 513 ends the process. Note that the data migration process, the migration management information 1000 update process, and the storage medium management information 800 update process are the same as in step S2304, and a description thereof will be omitted.

If it is determined that the condition of step S2302 is not satisfied, the transfer module 513 determines whether the migration source storage medium is the physical tape 611 and the migration destination storage medium is the virtual tape 711 ( Step S2303).

If it is determined that the condition of step S2303 is satisfied, the transfer module 513 transmits a load instruction for the migration source physical tape 611 to the physical tape library device 103, and transfers the data stored in the migration source physical tape 611 to the migration destination. Is stored in the virtual tape 711 (step S2306). Thereafter, the transfer module 513 ends the process. Note that the data migration process, the migration management information 1000 update process, and the storage medium management information 800 update process are the same as in step S2304, and a description thereof will be omitted.

If it is determined that the condition in step S2303 is not satisfied, the transfer module 513 transmits a load instruction for the migration source physical tape 611 to the physical tape library device 103, and migrates the data stored in the migration source physical tape 611. The data is stored in the previous physical tape 611 (step S2307). Thereafter, the transfer module 513 ends the process. Note that the data migration process, the migration management information 1000 update process, and the storage medium management information 800 update process are the same as in step S2304, and a description thereof will be omitted.

In this embodiment, when the user refers to the result display screen 2100 and inputs the identification information of the storage medium in the input field 1411, the data migration between tapes, that is, the resource allocated to the user resource is changed. . In addition to the processing described above, the review module 512 transmits a migration instruction including resource identification information whose capacity unit price 1203 is larger than the reference unit price and identification information of the storage medium to be compared, and the transfer module 513 is based on the migration instruction. Data migration processing between resources may be executed.

FIG. 24 is a flowchart for explaining an example of processing executed by the physical tape library apparatus 103 according to the first embodiment.

The module of the physical tape library apparatus 103 executes processing described below.

When the module receives an instruction from the management server 100 (step S2401), the module determines whether the instruction is a load instruction (step S2402).

If it is determined that the command is a load command, the module controls the controller 601 to move the physical tape 611 designated by the tape drive 602 (step S2405). Thereafter, the module ends the process.

If it is determined that the instruction is not a load instruction, the module determines whether the instruction is a write instruction (step S2403).

If it is determined that the command is a write command, the module controls the tape drive 602 to write data to the designated physical tape 611 (step S2406). Thereafter, the module ends the process.

If it is determined that the command is not a write command, the module determines whether the command is a read command (step S2404).

If it is determined that the command is a read command, the module controls the tape drive 602 to read data from the designated physical tape 611 and transmit it to the management server 100 (step S2407). Thereafter, the module ends the process. Note that in the case of a data read command that accompanies data migration, the module may transmit data to the migration destination tape.

If it is determined that the instruction is not a read instruction, the module determines that the instruction is an unload instruction and controls the controller 601 to move the designated physical tape 611 from the tape drive 602 to the storage space 603 ( Step S2408). Thereafter, the module ends the process.

According to the first embodiment, when resources provided by a plurality of systems having different types of hardware and storage locations of storage media are allocated to user resources, the resource needs to be changed according to the resource usage state. User resources can be specified. That is, it is possible to specify user resources to which expensive resources are allocated. Thus, the user can easily grasp the user resource to be changed, and can change the resource allocated to the user resource, that is, the system to be used. Therefore, the operation cost can be kept low.

Example 2 is different from Example 1 in that the computer system provides a server as a resource instead of a storage medium. Hereinafter, the second embodiment will be described focusing on differences from the first embodiment.

When operating a business server that constitutes a business system using resources provided by the system, as in the first embodiment, the price per resource usage amount (resource unit price) of the virtual server and the physical server is shown in FIG. There is a relationship as shown. A business server corresponds to a user resource.

For example, when a physical server is used as a business server that executes a process that uses a small amount of resources, the charge for the amount of resources used increases. Similarly, when a virtual server is used as a business server that executes a process with a large amount of resources to be used, the fee is similarly increased.

FIG. 25 is a diagram illustrating a configuration example of a computer system according to the second embodiment.

The computer system includes a management server 100, a terminal 101, a storage device 106, a data center 2500, and a data center 2501.

The hardware and software configurations of the management server 100 and the terminal 101 are the same as those in the first embodiment.

Note that the charge information 521 held by the management server 100 is partially different in column. Specifically, the storage medium ID 1201 is replaced with the server ID, the used capacity 1202 is replaced with the used resource quantity, the capacity unit price 1203 is replaced with the resource unit price, the storage medium type 1205 is replaced with the server output, and the physical storage medium The type 1206 is replaced with a physical server type. Here, the used resource amount indicates the number of cores of the processor being used, the memory capacity, and the like.

In the storage device 106 of the second embodiment, server management information is stored instead of the storage medium management information 800. The server management information is information in which the storage medium ID 801 is replaced with the server ID, the storage medium type 802 is replaced with the server type, and the used capacity 804 is replaced with the used resource amount.

The cost management information 900 stored in the storage device 106 of the second embodiment is partially different in column. Specifically, the storage medium type 901 is replaced with a server type, and the storage capacity 905 is replaced with a resource amount. Further, the unit of the charging unit capacity 903 is different.

The migration management information 1000 stored in the storage device 106 according to the second embodiment is partially different in column. Specifically, the migration source storage medium ID 1001 is replaced with the migration source server ID, and the migration destination storage medium ID 1002 is replaced with the migration destination server ID. Further, the migration management information 1000 according to the second embodiment does not include the offset 1003.

The budget management information 1100 stored in the storage device 106 according to the second embodiment is partially different in column. Specifically, the capacity unit price budget 1104 is replaced with a resource unit price.

The data center 2500 is a system composed of a plurality of physical servers 2510 and provides the VM 2520 as a resource. The hardware configuration of the physical server 2510 is the same as that of the AP server 102 and the like. The memory of the physical server 2510 stores a program that implements a virtualization control module that manages the VM 2520.

The data center 2501 is a system composed of a plurality of physical servers 2530, and provides the physical servers 2530 as resources.

Since the processing executed by the management server 100 and the terminal 101 is the same as that in the first embodiment, description thereof is omitted.

According to the second embodiment, even for a server with a complicated cost calculation method, it is possible to easily grasp the used resources that need to be changed and change the system that secures the resources according to the usage state of the resources.

In addition, this invention is not limited to the above-mentioned Example, Various modifications are included. Further, for example, the above-described embodiments are described in detail for easy understanding of the present invention, and are not necessarily limited to those provided with all the described configurations. In addition, a part of the configuration of the embodiment can be added to, deleted from, or replaced with another configuration.

In addition, each of the above-described configurations, functions, processing units, processing means, and the like may be realized by hardware by designing a part or all of them with, for example, an integrated circuit. The present invention can also be realized by software program codes that implement the functions of the embodiments. In this case, a storage medium in which the program code is recorded is provided to the computer, and a CPU included in the computer reads the program code stored in the storage medium. In this case, the program code itself read from the storage medium realizes the functions of the above-described embodiments, and the program code itself and the storage medium storing it constitute the present invention. Examples of storage media for supplying such program codes include flexible disks, CD-ROMs, DVD-ROMs, hard disks, SSDs (Solid State Drives), optical disks, magneto-optical disks, CD-Rs, magnetic tapes, A non-volatile memory card, ROM, or the like is used.

Further, the program code for realizing the functions described in this embodiment can be implemented by a wide range of programs or script languages such as assembler, C / C ++, Perl, Shell, PHP, Java, and the like.

Furthermore, by distributing the program code of the software that realizes the functions of the embodiments via a network, the program code is stored in a storage means such as a hard disk or memory of a computer or a storage medium such as a CD-RW or CD-R. The CPU included in the computer may read and execute the program code stored in the storage unit or the storage medium.

In the above-described embodiments, the control lines and information lines indicate those that are considered necessary for the explanation, and do not necessarily indicate all the control lines and information lines on the product. All the components may be connected to each other.

Claims (12)

1. A computer system including a plurality of providing systems that provide resources to be allocated to user resources constituting a user system, and a management computer that manages resource usage status and resource usage charges,
   The management computer is
   A processor, a memory connected to the processor, an interface connected to the processor;
   Including a review module that identifies candidate user resources that need to be changed from among the user resources allocated;
   Holds charge management information for managing the charge of the resource determined by the type of the resource and the storage location of the resource,
   The review module
   When a review request is received from the user, a used resource that is a resource allocated to the user resource and a first providing system that provides the used resource are specified,
   Based on the usage state of the used resource and the fee management information, a first unit price that is a fee per unit resource amount of the resource provided by the first providing system is calculated,
   A computer system that generates display information for presenting the candidate user resource based on a comparison result between the first unit price and a reference unit price.
2. The computer system according to claim 1,
   The computer system, wherein the review module generates the display information for presenting, as the candidate user resource, the user resource to which a use resource whose first unit price is larger than the reference unit price is assigned.
3. The computer system according to claim 2,
   The review request includes information for comparison that specifies a resource type for specifying a comparison resource and a storage location of the resource,
   The review module calculates, as the reference unit price, a usage fee per unit resource amount when the comparison resource is used, based on a usage state of the usage resource, the comparison information, and the fee management information. A computer system characterized by
4. The computer system according to claim 3,
   The computer system according to claim 1, wherein the review module changes the used resource whose first unit price is higher than the reference unit price to the comparison resource.
5. The computer system according to claim 2,
   The management computer holds budget management information for managing the budget of the user,
   The computer system according to claim 1, wherein the budget management information includes the reference unit price.
6. The computer system according to claim 2,
   The computer system is characterized in that the display information includes information for displaying the user resources in descending order of the first unit price and for displaying a usage state of the candidate user resources and a total value of the resource amounts. .
7. A resource management method for a computer system including a plurality of providing systems that provide resources to be allocated to user resources constituting a user system, and a management computer that manages a resource usage state and a resource usage fee,
   The management computer is
   A processor, a memory connected to the processor, an interface connected to the processor;
   Including a review module that identifies candidate user resources that need to be changed from among the user resources allocated;
   Holds charge management information for managing the charge of the resource determined by the type of the resource and the storage location of the resource,
   The resource management method is:
   When the review module receives a review request from the user, a first step of identifying a used resource that is a resource allocated to the user resource and a first providing system that provides the used resource;
   A second step in which the review module calculates a first unit price, which is a charge per unit resource amount of the resource provided by the first providing system, based on a use state of the used resource and the charge management information; When,
   The review module includes a third step of generating display information for presenting the candidate user resource based on a comparison result between the first unit price and a reference unit price. Method.
8. The resource management method according to claim 7, comprising:
   The third step includes a step in which the review module generates the display information for presenting the user resource to which a use resource having the first unit price larger than the reference unit price is assigned as the candidate user resource. A resource management method characterized by the above.
9. The resource management method according to claim 8, comprising:
   The review request includes information for comparison that specifies a resource type for specifying a comparison resource and a storage location of the resource,
   In the second step, the review module calculates a usage fee per unit resource amount when the comparison resource is used based on the usage state of the used resource, the comparison information, and the fee management information. A resource management method comprising the step of calculating the reference unit price.
10. The resource management method according to claim 9, comprising:
    The resource management method, wherein the review module includes a step of changing the used resource having the first unit price larger than the reference unit price to the comparison resource.
11. The resource management method according to claim 8, comprising:
    The management computer holds budget management information for managing the budget of the user,
    The resource management method, wherein the budget management information includes the reference unit price.
12. The resource management method according to claim 8, comprising:
    The display information includes information for displaying the user resources in descending order of the first unit price, and for displaying a usage value of the candidate user resources and a total value of the resource amounts. Management method.

Images