Storage system, management method of storage system, and management device of storage system

The storage system optimizes power consumption and environmental impact by moving files between primary and secondary storage based on access frequency and power consumption, using diverse storage devices to minimize energy use and emissions.

JP2024169048AInactive Publication Date: 2024-12-05HITACHI LTD
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
JP2023086228
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-05-25
Publication Date
2024-12-05
Estimated Expiration
Not applicable · inactive patent

AI Technical Summary

Technical Problem

Existing technologies for hierarchical storage management do not adequately consider the power consumption required for data movement between primary and secondary storage devices, which affects overall power consumption and environmental impact.

Method used

A storage system with a management device that tracks file size, access frequency, and power consumption of both primary and secondary storage devices, determining whether to move files to secondary storage based on equations that balance power consumption during holding and movement, using devices like optical disk drives, magnetic tape drives, and public clouds.

Benefits of technology

Reduces overall power consumption and environmental impact by efficiently moving infrequently accessed files to lower-power secondary storage, minimizing CO2 emissions and optimizing power usage across the storage hierarchy.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024169048000001_ABST
    Figure 2024169048000001_ABST
Patent Text Reader

Abstract

To appropriately determine data movement for reducing an environmental load in a hierarchical storage.SOLUTION: A storage system includes an upper-level storage device and a management device. The management device is configured to determine, for each file stored in the upper-level storage device, on the basis of a size of a target file and an access frequency of the target file, and power consumption information, whether power consumption for holding the target file is to be reduced by moving the target file to a lower-level storage device, and output, when it is determined that the power consumption for holding the target file is to be reduced by moving the target file to the lower-level storage device, an instruction to move the target file from the upper-level storage device to the lower-level storage device.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to a control technique for a storage system that focuses on the environmental load. [Background technology]

[0002] One example of a technology related to reducing power consumption in hierarchical storage is described in JP 2018-151815 A (Patent Document 1). Patent Document 1 states that "a storage management system including a computer that manages a hierarchical storage including a primary storage and a secondary storage includes a determination unit and a relocation unit. The determination unit decides whether or not to move a file stored in the primary storage to the secondary storage based on conditions for determining, based on the file size and the access interval time of the file, which of the primary storage and the secondary storage is the better storage destination in terms of power consumption. The relocation unit moves the file stored in the primary storage to the secondary storage in accordance with the above decision." [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2018-151815 A Summary of the Invention [Problem to be solved by the invention]

[0004] In Patent Document 1, a magnetic tape device is cited as an example of secondary storage. However, in reality, a device other than a magnetic tape device can be used as the secondary storage as long as it requires less power consumption to hold data than the primary storage. Furthermore, in order to determine whether or not to move data so as to reduce overall power consumption (i.e., reduce CO2 emissions), it is necessary to consider not only the power consumption required to hold the data, but also the power consumption required to move data between the primary storage and the secondary storage. [Means for solving the problem]

[0005] In order to solve at least one of the above problems, a representative example of the invention disclosed in the present application is a storage system having an upper storage device that holds data, a lower storage device that consumes less power to hold the data than the upper storage device, and a management device connected to the upper storage device and the lower storage device, wherein the management device has a processor and a memory, and the memory holds file information including information indicating a size of each file held in the upper storage device and information regarding an access frequency of each file, and power consumption information including information regarding the power consumption of the upper storage device and the lower storage device, and the processor determines, for each file stored in the upper storage device, whether the power consumption for holding the target file can be reduced by moving the target file to the lower storage device based on the size of the target file and the access frequency of the target file obtained from the file information and the power consumption information, and when it is determined that the power consumption for holding the target file can be reduced by moving the target file to the lower storage device, outputs an instruction to move the target file from the upper storage device to the lower storage device. Effect of the Invention

[0006] According to one aspect of the present invention, when various devices are used as lower-level storage in a hierarchical storage, it is possible to appropriately determine whether or not to migrate data to reduce the environmental load, taking into consideration the amount of power consumption required for data migration. Problems, configurations, and effects other than those described above will become apparent from the description of the following embodiments. [Brief description of the drawings]

[0007] [Figure 1]1 is a block diagram showing the overall configuration of a storage system according to an embodiment of the present invention. [Diagram 2] 2 is a block diagram showing a configuration of a management server included in the storage system according to the embodiment of the present invention. [Diagram 3] 4 is a block diagram showing a configuration of a condition determination unit included in the management server according to the embodiment of the present invention. [Figure 4] 3 is a block diagram showing data held by a management server according to an embodiment of the present invention; [Diagram 5] 1 is a block diagram showing a hardware configuration of a computer system that realizes a management server according to an embodiment of the present invention. [Figure 6] 11 is an explanatory diagram illustrating a lower device management table held by the management server according to the embodiment of this invention. [Figure 7] 11 is an explanatory diagram illustrating a power consumption history table during idle time held by the management server according to the embodiment of the present invention; FIG. [Figure 8] 11 is an explanatory diagram illustrating a migration file path management table held by the management server according to the embodiment of this invention. [Figure 9] 11 is an explanatory diagram showing a file list (all) held by a management server according to an embodiment of the present invention; FIG. [Figure 10] 11 is an explanatory diagram illustrating a file list (to be moved) held by a management server according to an embodiment of the present invention; FIG. [Figure 11] 11 is an explanatory diagram illustrating a threshold table held by the management server according to the embodiment of this invention. [Figure 12] FIG. 11 is an explanatory diagram illustrating a periodic table held by a management server according to an embodiment of the present invention. [Figure 13] 11 is an explanatory diagram illustrating a storage usage transition management table held by the management server according to the embodiment of this invention. [Figure 14] 11 is an explanatory diagram illustrating a power reduction amount transition table held by the management server according to the embodiment of this invention. FIG. [Figure 15] 4 is a sequence diagram showing a process executed in the storage system according to the embodiment of the present invention. [Figure 16]1 is a flowchart showing a process executed in the storage system according to an embodiment of the present invention. [Figure 17] 11 is an explanatory diagram illustrating a screen displayed by the storage system according to the embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] Hereinafter, an embodiment of the present invention will be described with reference to the drawings.

[0009] FIG. 1 is a block diagram showing the overall configuration of a storage system according to an embodiment of the present invention.

[0010] The storage system 100 of this embodiment is made up of a management server 110, a higher-level storage 120, and a lower-level storage 130. The management server 110 is connected to the higher-level storage 120 and the lower-level storage 130 by an interface cable 150.

[0011] The upper storage 120 and the lower storage 130 constitute a hierarchical storage 140. For example, the upper storage 120 stores data written by a host computer (not shown), and among that data, data that satisfies a predetermined condition, such as low access frequency, is moved to the lower storage 130. The management server 110 manages the movement of data between the upper storage 120 and the lower storage 130.

[0012] The upper storage 120 is a storage device that has relatively high performance such as access speed, but consumes relatively large amounts of power to hold data. A typical example of the upper storage 120 is a RAID (Redundant Arrays of Inexpensive Disks) device configured with multiple hard disk drives (HDD) 123 or multiple solid state drives (SSD) 122. Writing and reading of data to and from the multiple HDDs or SSDs is controlled by an upper storage controller 121. When the multiple HDDs or SSDs configure a RAID, the upper storage controller 121 is a RAID controller.

[0013] The lower storage 130 is a storage device that requires relatively little power to hold data, but has relatively low performance. Typical examples of the lower storage 130 include an optical disk drive 131, a magnetic tape drive 132, and a public cloud 133. The lower storage 130 may include two or more of these.

[0014] FIG. 2 is a block diagram showing the configuration of the management server 110 included in the storage system according to the embodiment of the present invention.

[0015] The management server 110 includes a hierarchical storage management unit 200. The hierarchical storage management unit 200 includes a condition determination unit 201, a higher-level storage file access unit 202, a lower-level storage file access unit 203, and a file information management unit 204.

[0016] The condition determination unit 201 determines whether or not to move data stored in the upper storage 120 to the lower storage 130 for each file according to a predetermined condition. Details of this determination will be described later. The upper storage file access unit 202 and the lower storage file access unit 203 control access to files stored in the upper storage 120 and the lower storage 130, respectively. The file information management unit 204 manages information related to files stored in the upper storage 120.

[0017] FIG. 3 is a block diagram showing the configuration of the condition determination unit 201 included in the management server 110 according to the embodiment of the present invention.

[0018] The condition determination unit 201 includes a determination unit 301 and a relocation unit 302. The determination unit 301 determines whether or not to move a file stored in the upper storage 120 to the lower storage 130 based on a predetermined condition. The relocation unit 302 moves the file according to the determination result by the determination unit 301.

[0019] FIG. 4 is a block diagram showing data held by the management server 110 according to the embodiment of the present invention.

[0020] The hierarchical storage management unit 200 in the management server 110 holds a lower device management table 401, an idle power consumption history table 402, a migration file path management table 403, a file list (all) 404, a file list (to be migrated) 405, a threshold table 406, a periodic table 407, a storage usage transition management table 408, and a power reduction amount transition table 409. These will be described in detail later.

[0021] FIG. 5 is a block diagram showing the hardware configuration of a computer system that realizes the management server 110 according to the embodiment of the present invention.

[0022] The management server 110 of this embodiment shown in Fig. 1 to Fig. 4 can be realized by, for example, a computer system 500. The computer system 500 includes a processor 501, a memory (main storage device) 502, an auxiliary storage device 503, an output device 504, an input device 505, and a communication interface (I / F) 506. The above components are connected to each other by a bus. The memory 502 and the auxiliary storage device 503 are storage devices, and store programs and data used by the processor 501.

[0023] The memory 502 is configured, for example, from a semiconductor memory, and is mainly used to hold programs and data being executed. The processor 501 executes various processes according to the programs stored in the memory 502. The processor 501 operates according to the programs to realize various functional units.

[0024] The auxiliary storage device 503 is configured with a large-capacity storage device such as a hard disk drive or a solid state drive, and is used to store programs and data for a long period of time. For example, the tables shown in FIG. 4 may be stored in the auxiliary storage device 503.

[0025] The processor 501 may be comprised of a single processing unit or multiple processing units and may include single or multiple arithmetic units or multiple processing cores. The processor 501 may be implemented as one or more central processing units, microprocessors, microcomputers, microcontrollers, digital signal processors, state machines, logic circuits, graphic processing units, systems on a chip, and / or any device that manipulates signals based on control instructions.

[0026] The programs and data stored in the auxiliary storage device 503 are loaded into the memory 502 at the time of start-up or when necessary, and the programs are executed by the processor 501, thereby executing various processes of the computer system 500. Therefore, in the following explanation, the processes executed by the hierarchical storage management unit 200 of the management server 110 are processes executed by the processor 501 of the computer system 500 in accordance with the programs, controlling each unit in the computer system 500 as necessary. Also, when the information shown in Figures 6 to 14, which will be described later, is referenced in the processes executed by the processor 501, at least the part of the information referenced by the processor 501 is loaded from the auxiliary storage device 503 into the memory 502.

[0027] The input device 505 is a hardware device for a user to input instructions and information, etc. The output device 504 is a hardware device that presents various images for input and output, such as a display device or a printing device. The communication I / F 506 is an interface for connection to the network 230.

[0028] The computer system 500 may include two or more processors 501. The functions of the system of this embodiment may be implemented in a plurality of computer systems 500. In this case, the plurality of computer systems 500 communicate with each other via a network 230. For example, some of the functions of the system of this embodiment may be implemented in one computer system 500, and the other parts may be implemented in another computer system.

[0029] Next, the information held by the hierarchical storage management unit 200 of the management server 110 will be described.

[0030] FIG. 6 is an explanatory diagram showing the lower device management table 401 held by the management server 110 according to the embodiment of this invention.

[0031] The lower device management table 401 manages information related to the storage apparatuses included in the lower storage 130. For example, the lower device management table 401 includes a lower device name 601, a product number 602, power consumption during idle 603, power consumption during reading 604, and power consumption during writing 605.

[0032] The lower device name 601 is the name of each storage device (e.g., the optical disk drive 131, the magnetic tape drive 132, and the public cloud 133) included in the lower storage 130. The product number 602 is a number that identifies each storage device. The idle power consumption 603, the read power consumption 604, and the write power consumption 605 indicate the power consumption of each storage device when idle, when reading data, and when writing data, respectively.

[0033] FIG. 7 is an explanatory diagram showing the idle power consumption history table 402 held by the management server 110 according to the embodiment of the present invention.

[0034] The idle power consumption history table 402 manages the history of the amount of power consumption during idle of the upper storage 120. This is generated and held by, for example, the upper storage controller 121, and at least a part of it may be acquired by the management server 110 as necessary.

[0035] The idle power consumption history table 402 includes a date / time 701 and a power consumption amount 702. The measured power consumption amount of the upper storage 120 and the date / time of the measurement are stored in the power consumption amount 702 and the date / time 701, respectively.

[0036] FIG. 8 is an explanatory diagram showing the migration file path management table 403 held by the management server 110 according to the embodiment of this invention.

[0037] The file transfer path management table 403 manages the source and destination file paths of the file to be transferred. For example, the file transfer path management table 403 includes a file name to be transferred 801, a source file path 802, and a destination device path 803. The file name to be transferred 801 is a file name that identifies the file to be transferred. The source file path 802 indicates the file path in the upper storage 120 of the file to be transferred. The destination device path 803 indicates the device and file path of the destination of the file to be transferred, among the storage devices included in the lower storage 130.

[0038] FIG. 9 is an explanatory diagram showing the file list (all) 404 held by the management server 110 according to the embodiment of the present invention.

[0039] The file list (all) 404 is information for managing all files stored in the primary storage 120. For example, the file list (all) 404 includes a file name 901, a file size 902, and a last update date and time 903 for each file stored in the primary storage 120. Note that, while the last update date and time indicating the date and time when the file was last updated is described as an example in this embodiment, the last access date and time indicating the date and time when either the file was last updated or read may also be used.

[0040] FIG. 10 is an explanatory diagram showing the file list (to be moved) 405 held by the management server 110 according to the embodiment of this invention.

[0041] The file list (to be moved) 405 manages files that are determined to be moved to the lower storage 130 after being temporarily stored in the upper storage 120. For example, the file list (to be moved) 405 includes a file name 1001, a file size 1002, and a last update date and time 1003 for each file determined to be moved. Files registered in the file list (to be moved) 405 are stored in the lower storage 130. Information relating to files that have been moved from the lower storage 130 to the upper storage 120 by re-movement, which will be described later, is deleted from the file list (to be moved) 405.

[0042] FIG. 11 is an explanatory diagram showing the threshold table 406 held by the management server 110 according to the embodiment of this invention.

[0043] The threshold table 406 manages thresholds used to determine whether or not to move a file stored in the upper storage 120 to the lower storage 130. For example, the threshold table 406 includes a target file size 1101 and a time elapsed since the last update date and time 1102. The target file size indicates the size of a file that is the subject of the determination as to whether or not to move it. The time elapsed since the last update date and time 1102 indicates the time from when the file was last updated to the current time.

[0044] 11, a different file size range is set in the target file size 1101 of each record in the threshold table 406. Then, in the elapsed time from last update date and time 1102 of each record, the elapsed time from the last update date and time that is the criterion for determining whether or not to move a file is set for each set file size range.

[0045] Normally, the value of the elapsed time since last update date and time 1102 is set to be larger as the value of the target file size 1101 is larger. This reduces power consumption due to frequent movement of large files. Also, when the lower storage 130 includes multiple storage devices (for example, different types of storage devices such as the optical disk drive 131 and the magnetic tape drive 132) as shown in FIG. 1, the threshold table 406 may be generated for each storage device. A specific example of a method for setting the value of the elapsed time since last update date and time 1102 corresponding to the target file size 1101 will be described later.

[0046] FIG. 12 is an explanatory diagram showing the periodic table 407 held by the management server 110 according to the embodiment of the present invention.

[0047] The periodic table 407 manages the execution cycles of various processes by the management server 110. For example, the periodic table 407 includes a process name 1201 and an execution cycle 1202. In the example of Fig. 12, the process names 1201 of each record in the periodic table 407 are stored as process names, such as "get file update information," "threshold judgment / update of migration target list," and "file hierarchical migration," and a predetermined time (e.g., number of days) is stored as the execution cycle 1202 corresponding to each process. Each process is executed at a cycle indicated by the execution cycle 1202.

[0048] FIG. 13 is an explanatory diagram showing the storage usage transition management table 408 held by the management server 110 according to the embodiment of this invention.

[0049] The storage usage transition management table 408 manages the transition of the usage (i.e., the total amount of data stored) of the upper storage 120. For example, the storage usage transition management table 408 includes a date and time 1301 indicating the date and time when the usage was measured, and a storage usage 1302 indicating the usage measured at each date and time.

[0050] FIG. 14 is an explanatory diagram showing the power reduction amount transition table 409 held by the management server 110 according to the embodiment of the present invention.

[0051] The power reduction amount transition table 409 manages the transition of the power reduction amount calculated by a method described later. For example, the power reduction amount transition table 409 includes a date and time 1401 and a power reduction amount 1402 indicating the amount of power reduction calculated at the time indicated by the value of the date and time 1401.

[0052] Next, the processing executed in the storage system 100 of this embodiment will be explained with reference to FIGS.

[0053] FIG. 15 is a sequence diagram showing the processing executed in the storage system 100 according to the embodiment of the present invention.

[0054] FIG. 16 is a flowchart showing the processing executed in the storage system 100 according to the embodiment of the present invention.

[0055] Both Figures 15 and 16 describe the same process. That is, Figure 15 is a sequence diagram that is written to clarify the data exchange between the components of storage system 100 during processing, and Figure 16 is a flowchart that is written to clarify the flow of processing. The correspondence between the steps in both is as follows:

[0056] The controller 1511 of the primary storage 120 periodically acquires a list of all files stored in the drive 1512 of the primary storage 120 and transmits it to the management server 110 (steps S1501, S1601). This process may be executed based on the execution cycle of file update information acquisition stored in the periodic table 407, for example. The controller 1511 is, for example, the primary storage controller 121, and the drive 1512 is, for example, the SSD 122 or the HDD 123. The management server 110 retains the list of files received from the controller 1511 as the file list (all) 404.

[0057] Next, the judgment unit 301 in the condition judgment unit 201 of the management server 110 judges whether the current value of each file included in the file list received from the controller 1511 is equal to or greater than the threshold value (steps S1502, S1602). The judgment unit 301 judges to move a file whose current value is judged to be equal to or greater than the threshold value, and adds information about the file to the file list (to be moved) 405 (steps S1502, S1603). On the other hand, the judgment unit 301 judges not to move a file whose current value is judged to be less than the threshold value (steps S1502, S1604). In this case, information about the file is not added to the file list (to be moved) 405.

[0058] Here, an example of the determination in steps S1502 and S1602 as to whether the current value of each file is equal to or greater than the threshold value will be described.

[0059] For example, the determination unit 301 may calculate the following equation (1) for each file stored in the upper storage 120, and if equation (1) is satisfied, determine to move the file to be calculated (hereinafter also referred to as the target file) to the lower storage 130.

[0060]

number

[0061] Here, PC idle(upper) is the amount of power consumed to hold the target file in the upper storage 120. This can be calculated, for example, by calculating the ratio of the size of the file to the used capacity of the upper storage 120, multiplying this ratio by the power consumption of the upper storage 120 in the idle state, and further multiplying it by the time elapsed since the last update date and time of the target file. Here, the power consumption of the upper storage 120 in the idle state can be obtained from the power consumption history table 402 in idle state (FIG. 7), the used capacity of the upper storage 120 from the storage usage transition management table 408 (FIG. 13), and the size of the target file from the file list (all) 404 (FIG. 9). In addition, the time elapsed since the last update date and time of the target file can be calculated, for example, based on the last update date and time 903 of the target file in the file list (all) 404 shown in FIG. 9 and the current time. Here, the time elapsed since the last update date and time of the target file is an example of an index of the update frequency of the target file, and, for example, when information such as the average value of the past access intervals of each file or the predicted value of the future access intervals is available, such information may be used.

[0062] On the other hand, PC idle (lower) is the amount of power consumed to hold the target file in the lower storage 130. This can be calculated, for example, by multiplying the idle power consumption 603 in the lower device management table 401 (FIG. 6) by the access interval of the target file.

[0063] PC(down) is the amount of power consumed to move a target file from the upper storage 120 to the lower storage 130 when it is determined that the target file should be moved to the lower storage 130. PC(down) can be calculated, for example, by summing up the results of the following equations (2) to (5).

[0064] The determining unit 301 calculates the power consumption of the write process to the lower storage 130 among the processes of writing the target file read from the upper storage 120 to the lower storage 130 by using the formula (2).

[0065]

number

[0066] Here, P write is the power consumed when the lower storage 130 performs a process of writing the target file to a write destination device (for example, any one of the optical disk drive 131, the magnetic tape drive 132, and the public cloud 133). This can be obtained, for example, from the power consumption during writing 605 in the lower device management table 401. write is a predicted time required for the lower storage 130 to write the target file to the destination device. This can be calculated based on, for example, the size of the target file and the data transfer speed of the destination device when writing.

[0067] The determining unit 301 calculates the power consumption of a read process from the upper storage 120 among processes for writing a target file read from the upper storage 120 to the lower storage 130, using the formulas (3) to (5).

[0068]

number

[0069] Formula (3) is a calculation formula for the power consumption of the CPU (Central Processing Unit, not shown) of the upper storage controller 121 among the power consumption of the read process from the upper storage 120. In formula (3), P max and P idleare the maximum power consumption and idle power consumption of the CPU of the upper storage controller 121, respectively. n is the CPU usage rate (%) of the upper storage controller 121 during read processing. T_down read is a predicted value of the time required for the lower storage 130 to read the target file from the upper storage 120. This can be calculated, for example, based on the size of the target file and the data transfer speed of the read source device.

[0070] Formula (4) is a formula for calculating the power consumption of the memory (not shown) of the upper storage controller 121 among the power consumption of the read process from the upper storage 120. In formula (4), P max and P idle are the maximum power consumption and idle power consumption of the upper storage controller 121 memory, respectively. n is the memory usage rate (%) of the upper storage controller 121 during a read process. T_down read is the same as in equation (3) above.

[0071] Formula (5) is a formula for calculating the power consumption of the drive (e.g., SSD 122 or HDD 123) of the upper storage 120 among the power consumption of the read process from the upper storage 120. Here, P read is the power consumption for reading data from the drive. read is the same as in equation (3).

[0072] Returning to formula (1), PC(up) is the amount of power consumed when a file is re-accessed, that is, the amount of power consumed to move the target file from the lower storage 130 to the upper storage 120 in response to an access from the host computer after the file has been moved to the lower storage 130. PC(up) can be calculated, for example, by adding up the results of the following formulas (6) to (9).

[0073] The determining unit 301 calculates the amount of power consumption of a read process from the lower storage 130 among processes for writing a target file read from the lower storage 130 to the upper storage 120, using formula (6).

[0074]

number

[0075] Here, P read is the power consumed when the lower storage 130 performs processing to read the target file from the device to which it is written. This can be obtained, for example, from the power consumption during read 604 in the lower device management table 401. read is a predicted time required for the lower storage 130 to read the target file from the write destination device. This can be calculated based on, for example, the size of the target file and the data transfer speed when reading from the write destination device.

[0076] The determining unit 301 calculates the power consumption of the write process to the upper storage 120 among the processes of writing the target file read from the lower storage 130 to the upper storage 120 using the formulas (7) to (9).

[0077]

number

[0078] Formula (7) is a formula for calculating the power consumption of the CPU of the upper storage controller 121 out of the power consumption of the write process to the upper storage 120. In formula (7), P max and P idle is the same as in formula (3). n is the CPU usage rate (%) of the upper storage controller 121 during the write process. T_up writeis a predicted value of the time required for the process of writing the target file to the upper storage 120. This can be calculated, for example, based on the size of the target file and the data transfer speed at the time of reading from the read source device (i.e., the SSD 122 or HDD 123 to which the target file read from the lower storage 130 is written back).

[0079] Formula (8) is a formula for calculating the power consumption of the memory (not shown) of the upper storage controller 121 out of the power consumption of the write process to the upper storage 120. In formula (4), P max and P idle is the same as in formula (4). n is the memory usage rate (%) of the upper storage controller 121 during the write process. T_up write is the same as in equation (7).

[0080] Formula (9) is a formula for calculating the power consumption of the drive (e.g., SSD 122 or HDD 123) of the upper storage 120 among the power consumption of the write process to the upper storage 120. Here, P write is the power consumption for writing data to the drive. write is the same as in equation (7).

[0081] 16, when calculating the above formula (1) for a certain file, the file is actually held in the upper storage 120 from the time the file was last updated to the present. In this case, the left side of formula (1) is an estimate of the power consumed to store the file while the file was stored in the upper storage 120 from the time the file was last updated to the present.

[0082] On the other hand, the right side of equation (1) is an estimate of the power consumed to move the file from the upper storage 120 to the lower storage 130 immediately after it was last updated, and then move it from the lower storage 130 to the upper storage 120 just before the current time, and to store the file in the lower storage 130.

[0083] Therefore, the fact that formula (1) is satisfied means that it is estimated that less power was consumed (i.e., the environmental load associated with power consumption, such as carbon dioxide (CO2) emissions, was also less) by temporarily moving the file to the lower storage 130 after the last update rather than continuing to store the file in the upper storage 120. In this case, the determination unit 301 determines that the file should be moved, and adds information about the file to the file list (to be moved) 405.

[0084] Note that the judgment unit 301 may perform the calculations of the above formulas (1) to (9) each time it executes the processing of steps S1502 and S1602 for each file, but it may also calculate a judgment threshold in advance based on formulas (1) to (9) and make judgment based on that threshold in steps S1502 and S1602.

[0085] For example, the determination unit 301 may calculate in advance the relationship between the size of a file to be moved and the elapsed time from the last update date and time that satisfies the above formula (1) for a file of that size, and store that relationship as the threshold table 406. In the example of Fig. 11, a range of file sizes is set as the target file size 1101. In this case, the value of the elapsed time from the last update date and time 1102 corresponding to each range is set so that the above formula (1) is satisfied for any file size within the corresponding range.

[0086] If the lower storage 130 includes multiple storage devices, the value of the elapsed time since last update date and time 1102 may be set so that the above formula (1) is satisfied for each storage device, or a threshold table 406 may be generated for each storage device.

[0087] By determining whether or not to move each file to the lower storage 130 as described above, files that are updated less frequently can be moved to the lower storage 130, reducing the overall power consumption, including the power consumption required to move the files, and reducing environmental impacts such as CO2 emissions.

[0088] Next, the relocation unit 302 in the condition determination unit 201 transmits a list of files (i.e., a move list) added to the file list (movement target) 405 to the controller 1511 (steps S1503, 1605). The controller 1511 saves the paths of the files to be moved included in the move list (steps S1504, S1606) and instructs the movement of the files to be moved between tiers (steps S1505, S1607). In accordance with this instruction, the files to be moved are moved from the drive 1512 of the upper storage 120 to the drive 1514 of the lower storage 130 (steps S1506, S1608).

[0089] Thereafter, the file that was moved to the lower storage 130 is re-accessed. For example, when the upper storage 120 receives a request to access a file from a host computer, if that file is included in the file list (to be moved) 405, that file is stored in the lower storage 130 rather than the upper storage 120.

[0090] In this case, the controller 1511 transmits a file transfer instruction to the controller 1513 of the lower storage 130 (steps S1507, S1609). In accordance with this instruction, the file to be transferred is transferred from the drive 1514 of the lower storage 130 to the drive 1512 of the upper storage 120 (steps S1508, S1610). At this time, the original file path of the file to be transferred (i.e., before it was transferred to the lower storage 130) is reproduced in accordance with the transfer file path management table 403.

[0091] This completes the process.

[0092] FIG. 17 is an explanatory diagram showing a screen displayed by the storage system 100 according to the embodiment of the present invention.

[0093] 17 is an example of a screen displayed by the output device 504 of the computer system 500 that realizes the management server 110. The display screen 1700 includes a CO2 emission amount display section 1701, a power consumption amount display section 1702, a maximum temperature display section 1703, and a CO2 emission reduction amount display section 1704.

[0094] The CO2 emission amount display section 1701 displays, for example, the actual amount of CO2 emission calculated from the actual amount of power consumption of the storage system 100. In the example of Fig. 17, a graph showing the amount of CO2 emission per month is displayed.

[0095] The power consumption display section 1702 displays, for example, the actual power consumption of the storage system 100. In the example of Fig. 17, a graph showing the change in the average power consumption for each time slot in September 2022 is displayed as a graph showing the power consumption for each time slot in a certain month.

[0096] The maximum temperature display section 1703 displays, for example, the actual temperature measured within the storage system 100. In the example of Fig. 17, a graph showing the temperature within the storage system 100 for each time period in a certain month is displayed, which shows the trend in the average temperature for each time period in September 2022. In this example, the temperature is measured at multiple locations in the storage system 100, the average temperature value is calculated for each location, and the maximum of the calculated average temperatures for each location is displayed as a solid line, and the average values ​​are displayed as dashed lines.

[0097] In addition to a graph similar to that displayed in the CO2 emission display section 1701, the CO2 emission reduction amount display section 1704 displays the CO2 emission reduction amount due to the transfer of data between tiers (i.e., from the upper storage 120 to the lower storage 130) shown in this embodiment. In the example of Fig. 17, the CO2 emission reduction amount due to the transfer of data between tiers is displayed by a dashed line. In other words, the sum of the solid line portion and the dashed line portion of the graph displayed in the CO2 emission reduction display section 1704 indicates the CO2 emission amount if data is not transferred between tiers.

[0098] For example, in step S1602 in Fig. 16, formula (1) is calculated for each file stored in the upper storage 120, and the differences between the right and left sides of formula (1) for files determined to be moved between tiers as a result are summed up, and the sum is stored in the power reduction amount transition table 409 (Fig. 14), and the CO2 emissions calculated based on the sum may be displayed as the dashed line portion of the graph in the CO2 emission reduction amount display section 1704. Note that the calculation of the CO2 emissions based on the amount of power consumption can be performed based on, for example, the CO2 emission coefficient published by the power company. By displaying in this manner, the effect of reducing the environmental load by moving data between tiers can be easily grasped.

[0099] Furthermore, the system according to the embodiment of the present invention may be configured as follows.

[0100] (1) A storage system (e.g., storage system 100) having an upper storage device (e.g., upper storage 120) that holds data, a lower storage device (e.g., lower storage 130) that consumes less power to hold the data than the upper storage device, and a management device (e.g., management server 110) that is connected to the upper storage device and the lower storage device, the management device having a processor (e.g., processor 501) and a memory (e.g., memory 502), the memory including file information (e.g., file list (entire) 404) including information indicating the size of each file held in the upper storage device and information regarding the access frequency of each file, and information regarding the power consumption of the upper storage device and the lower storage device. The processor holds power consumption information including the size and access frequency of the target file acquired from the file information and the power consumption information for each file stored in the higher-level storage device, and determines whether the power consumption for holding the target file can be reduced by moving the target file to the lower-level storage device based on the size and access frequency of the target file acquired from the file information and the power consumption information (e.g., steps S1502, S1602).If it determines that the power consumption for holding the target file can be reduced by moving the target file to the lower-level storage device, it outputs an instruction to move the target file from the higher-level storage device to the lower-level storage device (e.g., steps S1505, S1607).

[0101] This makes it possible, when a variety of devices are used as lower-level storage in a hierarchical storage system, to appropriately determine whether or not to move data to reduce the environmental impact, taking into account the amount of power consumption required to move the data.

[0102] (2) In (1) above, if the total power consumption of the power consumption when a lower storage device holds the target file during an access interval period of the target file, which is determined based on the access frequency of the target file, plus the power consumption to move the target file from the higher storage device to the lower storage device, and the power consumption to move the target file from the lower storage device to the higher storage device is smaller than the power consumption when a higher storage device holds the target file during an access interval period of the target file, which is determined based on the access frequency of the target file (e.g., equation (1)), the processor determines that the power consumption for holding the target file can be reduced by moving the target file to the lower storage device.

[0103] This makes it possible to appropriately determine whether or not to transfer data to reduce the environmental load, taking into consideration the amount of power consumption required for the data transfer.

[0104] (3) In (2) above, the amount of power consumption when the upper storage device holds the target file during the access interval of the target file is calculated based on the ratio of the size of the target file to the used capacity of the upper storage device, the idle power consumption of the upper storage device obtained from the power consumption information, and the length of the access interval of the target file. The amount of power consumption to move the target file from the upper storage device to the lower storage device is calculated based on the time required to read the target file from the upper storage device and the time required to write the target file to the lower storage device, which are predicted from the size of the target file, and the power consumption information (e.g., formulas (2) to (5)). The amount of power consumption to move the target file from the lower storage device to the upper storage device is calculated based on the time required to read the target file from the lower storage device and the time required to write the target file to the upper storage device, which are predicted from the size of the target file, and the power consumption information (e.g., formulas (6) to (9)).

[0105] This makes it possible to appropriately determine whether or not to transfer data to reduce the environmental load, taking into consideration the amount of power consumption required for the data transfer.

[0106] (4) In (3) above, the file information includes information indicating the last access date and time of each file (e.g., the last update date and time 903) as information regarding the access frequency of each file, and the access interval period of each file is the period from the last access date and time of each file to the current date and time.

[0107] This allows an appropriate decision to be made as to whether or not to move data in order to reduce the environmental load.

[0108] (5) In the above (4), the memory holds threshold information (e.g., threshold table 406) that corresponds the size of a file stored in a higher-level storage device to the elapsed time from the last access date and time, and in the threshold information, the elapsed time from the last access date and time is set so that the total power consumption of the power consumption when a file of the corresponding size is held by a lower-level storage device during a period indicated by the elapsed time from the last access date and time, the power consumption to move the file of the corresponding size from the higher-level storage device to the lower-level storage device, and the power consumption to move the file of the corresponding size from the lower-level storage device to the higher-level storage device is smaller than the power consumption when the higher-level storage device holds a file of the corresponding size during the period indicated by the elapsed time from the last access date and time. The processor determines, based on the threshold information, that the power consumption for holding the target file can be reduced by moving the target file to the lower-level storage device when the elapsed time from the last access date and time to the current date and time is longer than the elapsed time from the last access date and time corresponding to the size of the target file.

[0109] This makes it possible to easily and appropriately determine whether or not to transfer data in order to reduce the environmental load.

[0110] (6) In the above (1), the processor calculates the amount of power consumption reduction that would be achieved by moving a file, among the files stored in the higher-level storage device, that is determined to be able to reduce the power consumption required to hold the file by moving it to the lower-level storage device, and outputs at least one of the calculated amount of power consumption reduction and the amount of reduction in environmental load estimated from the amount of power consumption reduction (e.g., CO2 emission reduction display unit 1704).

[0111] This makes it easy to grasp the effect of reducing the environmental load by moving data between hierarchical levels.

[0112] (7) In (6) above, the reduction in environmental impact is the reduction in carbon dioxide emissions estimated from the reduction in power consumption.

[0113] This makes it easy to grasp the effect of reducing the environmental load by moving data between hierarchical levels.

[0114] (8) In the above (1), the upper storage device includes at least one of a hard disk drive (e.g., HDD 123) and a solid state drive (e.g., SSD 122), and the lower storage device includes at least one of an optical disk drive (e.g., optical disk drive 131), a magnetic tape drive (e.g., magnetic tape drive 132), and a public cloud (e.g., public cloud 133).

[0115] This makes it possible, when a variety of devices are used as lower-level storage in a hierarchical storage system, to appropriately determine whether or not to move data to reduce the environmental impact, taking into account the amount of power consumption required to move the data.

[0116] The present invention is not limited to the above-mentioned embodiment, and various modifications are included. For example, the above-mentioned embodiment has been described in detail for better understanding of the present invention, and is not necessarily limited to those having all the configurations described. Also, it is possible to replace a part of the configuration of one embodiment with the configuration of another embodiment, and it is also possible to add the configuration of another embodiment to the configuration of one embodiment. Also, it is possible to add, delete, or replace a part of the configuration of each embodiment with another configuration.

[0117] In addition, the above-mentioned configurations, functions, processing units, processing means, etc. may be realized in part or in whole by hardware, for example, by designing them as integrated circuits. In addition, the above-mentioned configurations, functions, etc. may be realized in software by a processor interpreting and executing a program that realizes each function. Information such as a program, table, file, etc. that realizes each function can be stored in a storage device such as a non-volatile semiconductor memory, a hard disk drive, or an SSD (Solid State Drive), or in a computer-readable non-transitory data storage medium such as an IC card, an SD card, or a DVD.

[0118] In addition, the control lines and information lines are shown as those considered necessary for the explanation, and not all control lines and information lines in the product are shown. In reality, it can be considered that almost all components are connected to each other. [Explanation of symbols]

[0119] 100 Storage Systems 110 Management Server 120 Top Storage 121 Upper Storage Controller 122 Solid State Drive (SSD) 123 Hard Disk Drive (HDD) 130 Lower Storage 131 Optical disk drive 132 Magnetic Tape Drive 133 Public Cloud 140 Tiered Storage

Claims

1. A storage system comprising: an upper storage device that holds data; a lower storage device that consumes less power for holding data than the upper storage device; and a management device that is connected to the upper storage device and the lower storage device, The management device includes a processor and a memory. The memory includes: file information including information indicating the size of each file held in the higher-level storage device and information regarding the access frequency of each file; power consumption information including information regarding the power consumption of the upper storage device and the lower storage device; The processor, for each file stored in the higher-level storage device, determining whether or not power consumption for holding the target file can be reduced by moving the target file to the lower-level storage device based on the size of the target file and the access frequency of the target file acquired from the file information and the power consumption information; A storage system characterized by outputting an instruction to move the target file from the higher-level storage device to the lower-level storage device when it is determined that the power consumption required to hold the target file can be reduced by moving the target file to the lower-level storage device.

2. 2. The storage system according to claim 1, A storage system characterized in that the processor determines that the power consumption for holding the target file can be reduced by moving the target file to the lower storage device when the total power consumption of the power consumption when the lower storage device holds the target file during the access interval period of the target file, which is determined based on the access interval period of the target file, is smaller than the power consumption when the higher-level storage device holds the target file during the access interval period of the target file, which is determined based on the access frequency of the target file.

3. 3. The storage system according to claim 2, the amount of power consumption when the higher-level storage device holds the target file during the access interval of the target file is calculated based on a ratio of the size of the target file to the used capacity of the higher-level storage device, the power consumption of the higher-level storage device during idle time acquired from the power consumption information, and the length of the access interval of the target file; the amount of power consumption required to move the target file from the higher-level storage device to the lower-level storage device is calculated based on a required time to read the target file from the higher-level storage device and a required time to write the target file to the lower-level storage device, which are predicted from a size of the target file, and on the power consumption information; A storage system characterized in that the amount of power consumption required to move the target file from the lower storage device to the higher storage device is calculated based on the time required to read the target file from the lower storage device, predicted from the size of the target file, and the time required to write the target file to the higher storage device, and the power consumption information.

4. 4. The storage system according to claim 3, the file information includes information indicating the last access date and time of each of the files as information regarding the access frequency of each of the files; A storage system according to claim 1, wherein the access interval of each of the files is a period from the last access date and time of each of the files to a current date and time.

5. 5. The storage system according to claim 4, the memory holds threshold information that associates a size of a file stored in the higher-level storage device with an elapsed time from a last access date and time; In the threshold information, the elapsed time from the last access date and time is set so that the total power consumption of the power consumption when the lower storage device holds a file of the corresponding size during a period indicated by the elapsed time from the last access date and time, the power consumption to move the file of the corresponding size from the higher storage device to the lower storage device, and the power consumption to move the file of the corresponding size from the lower storage device to the higher storage device is smaller than the power consumption when the higher storage device holds a file of the corresponding size during the period indicated by the elapsed time from the last access date and time, A storage system characterized in that the processor determines, based on the threshold information, that the power consumption required to store the target file can be reduced by moving the target file to the lower-level storage device when the elapsed time from the last access date and time of the target file to the current date and time is longer than the elapsed time from the last access date and time corresponding to the size of the target file.

6. 2. The storage system according to claim 1, The processor, A storage system characterized by calculating an amount of power consumption reduction that would be achieved by moving a file, among the files stored in the higher-level storage device, that is determined to be able to reduce the power consumption required to hold the file by moving it to the lower-level storage device, and outputting at least one of the calculated amount of power consumption reduction and an amount of reduction in environmental load estimated from the amount of power consumption reduction.

7. 7. The storage system according to claim 6, A storage system, wherein the reduction in the environmental load is a reduction in carbon dioxide emissions estimated from the reduction in the power consumption.

8. 2. The storage system according to claim 1, the higher-level storage device includes at least one of a hard disk drive and a solid-state drive; A storage system characterized in that the lower-level storage device includes at least one of an optical disk drive, a magnetic tape drive, and a public cloud.

9. A method for managing a storage system, comprising: the storage system includes a higher-level storage device that holds data, a lower-level storage device that consumes less power for holding data than the higher-level storage device, and a management device that is connected to the higher-level storage device and the lower-level storage device; The management device includes a processor and a memory. The memory includes: file information including information indicating the size of each file held in the higher-level storage device and information regarding the access frequency of each file; power consumption information including information regarding the power consumption of the upper storage device and the lower storage device; The method for managing a storage system includes: a step of the processor determining, for each file stored in the higher-level storage device, whether or not power consumption for holding the target file can be reduced by moving the target file to the lower-level storage device, based on the size of the target file and the access frequency of the target file obtained from the file information, and the power consumption information; a step of outputting an instruction to move the target file from the higher-level storage device to the lower-level storage device when the processor determines that the power consumption required to hold the target file can be reduced by moving the target file to the lower-level storage device.

10. A management device for a storage system, comprising: The storage system includes a higher-level storage device for storing data, and a lower-level storage device that consumes less power for storing data than the higher-level storage device, The management device includes a processor and a memory. The memory includes: file information including information indicating the size of each file held in the higher-level storage device and information regarding the access frequency of each file; power consumption information including information regarding the power consumption of the upper storage device and the lower storage device; The processor, for each file stored in the higher-level storage device, determining whether or not power consumption for holding the target file can be reduced by moving the target file to the lower-level storage device based on the size of the target file and the access frequency of the target file acquired from the file information and the power consumption information; A storage system management device characterized by outputting an instruction to move the target file from the higher-level storage device to the lower-level storage device when it is determined that the power consumption required to hold the target file can be reduced by moving the target file to the lower-level storage device.

Citation Information

Patent Citations

  • Storage management system

    JP2018151815A