Storage system operation management method and storage system

Files belonging to a file group are collected at an uppermost tier when a specific action occurs with respect to a key file of the file group. When an action with respect to a keyword occurs while a management processor of a disc adapter is taken as a management server and a host is taken as an agent, and file promotion processing is carried out by the management server by starting management software in accordance with a microprogram. When the content of the specific action satisfies promotion conditions, the other files belonging to the same file group as the key file are promoted to the uppermost tier to be ready for utilization.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application relates to and claims priority from Japanese Patent Application No. 2006-282503, filed on Oct. 17, 2006, the entire disclosure of which is incorporated herein by reference.

BACKGROUND

1. Field of the Invention

The present invention relates to technology for arranging storage regions of storage logically into tiers, distributing file groups through relocation into each tier, and managing the relocation of files belonging to each group into collections of files belonging to any tier as file groups.

2. Description of Related Art

A storage system is equipped, for example, with at least one storage apparatus referred to as a disc array sub-system, etc. In this type of storage apparatus, disc drives such as, for example, hard disc drives or semiconductor memory drives etc. are relocated in an array so as to enable storage regions to be provided based on RAID (Redundant Array of Independent Inexpensive Disks). A host computer then accesses logical storage regions supplied by the storage apparatus and carries out reading and writing of data.

In the related art, a storage system provided with a plurality of storage apparatus having one or more volumes, a virtualizing section for collectively managing volumes in the possession of each storage apparatus in a virtual manner, a storage section for storing volume attribute information for managing attribute information of each volume, and a relocation section for relocating a specified transfer source volume to a specified storage tier between a plurality of storage tiers generated based on a plurality of policies set in advance and volume attribute information is proposed (refer to patent document 1).

With storage environments that are structured in tiers of storage systems of the related art, it is necessary to relocate files to each storage tier in an optimal manner taking into consideration utilization frequency and importance of the data.

Namely, storage systems of the related art adopt a configuration taking access frequency of file group units where a file or plurality of files are collected together as a reference, and relocate files to any one of the tiers every unit. This is therefore not sufficient for relocating files to file groups in an optimum manner.

Specifically, the file group is utilized at irregular intervals, and utilization every one time is for a comparatively short time. However, a state is adopted in the storage system where files within the group are used overall, and if the deciding of the file used first in a one time utilization of the file group is not taken into consideration, the following problem occurs.

For example, in order to promote files belonging to a file group to the uppermost tier, an access of a certain extent is necessary, and a time lag occurs until use at the uppermost tier is possible. Because of this, when a file of the file group is promoted to the uppermost tier, it is common for the operation using this file group to have advanced to a certain extent. However, when the access frequency falls, it is possible for files belonging to this file group to be demoted to a lower tier. Further, it is also possible for the group as a whole to be relocated through interchange at the uppermost tier or a lower tier. There are therefore cases where a comparatively large reduction or increase in capacity occurs with regards to the storage region between the transfer source and transfer destination at the time of file transfer.

It is therefore the object of the present invention to collect files belonging to a file group at the uppermost tier when a specific action occurs with regards to a file group. Moreover, it is a further object of the present invention to always maintain optimum file promotion conditions or file demotion conditions with regards to the file group by dynamically changing the files subject to observation (key files) within the file group.

SUMMARY

In order to resolve the aforementioned problems, the present invention sets files belonging to the uppermost tier of files belonging to a file group as files subject to observation (key files) so that when a specific action occurs with regards to the files subject to observation, files belonging to the same file group as the files subject to observation are promoted to the uppermost tier as files having mutual correlation when the promotion conditions are satisfied. On the other hand, demotion to a lower tier than the uppermost tier is also possible when files of the files of the uppermost tier that satisfy demotion conditions exist.

It is therefore possible to relocate files of a file group containing a file subject to observation to the uppermost tier from the start of utilization by setting files used first of the files belonging to a file group as files subject to observation (key files), and promoting files of the same file group as the file subject to observation to the uppermost tier in response to an action with respect to the file subject to observation. On the other hand, when demotion conditions are satisfied for a file belonging to the uppermost tier, this file is demoted, and it is therefore possible to prevent files from being demoted at an unintended time. It is therefore possible to dynamically change the file subject to observation by designating conditions for files subject to observation (key files), and it is possible to always keep promotion or demotion conditions for the file group optimized.

Effects of the Invention

According to the present invention, it is possible to relocate all of the files of a file group containing a file subject to observation in the uppermost tier from the start of utilization.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The following is a description of an embodiment of the present invention based on the drawings.FIG. 1is a block view of a configuration for a storage system showing a first embodiment of the present invention, andFIG. 2is a configuration view illustrating a tier structure for files for storage. InFIG. 1andFIG. 2, a storage system is comprised of a channel adapter (CHA)10, shared memory12, cache memory14, disc adapter (DKA)16, and internal disc (Fiber) taken as storage apparatus, with a service processor (SVP)20being connected to the disc apparatus. The channel adapter10is connected to a host (upper order computer)24, is connected to the disc adapter16via the shared memory12, and is connected to the disc adapter16via the cache memory14. The disc adapter16is equipped with a management processor (not shown) for carrying out various arithmetic processing in accordance with a microprogram (MP)26. The management processor is connected to an internal disc18and is connected to an external disc28of an external storage system and a tape30of a tape library. Namely, the externally connected disc28and the tape30are capable of being connected to the management processor as a single element of storage. The internal disc18is equipped with a plurality of hard disc drives (HDD)32, so as to constitute a RAID group.

When the internal disc18, externally connected disc28, and tape30are taken as storage, the storage region of the storage is put logically into the form of tiers, so as to give, for example, three tiers of uppermost Tier1, intermediate Tier2, and lowermost Tier3, with relocation taking place in such a manner that files F11to F33are distributed at each tier. In this case, the files F11, F12and F13are set as the files for the internal disc18, the files F21, F22and F23are set as files for externally connected disc28, and the files F31, F32and F33are set as files for the tape30. F11to F33are capable of being processed as a single volume34with respect to the host24.

Further, files F11to F33are classified into file groups every unit such as application units or service units as collections of files belonging to whichever tier. For example, as shown inFIG. 3, file F11is relocated as A file01, file F12as A file02, file F21as A file03, file31as A file04, as files belonging to file group A, and file F13is relocated as B file01, file32as B file02, and file F33as B file03, as files belonging to file group B.

As shown inFIG. 4, the management processor for managing the relocation of these files manages the relocation of each file based on a file group management table T1, key file management table T2, and tier management table T3. At this time, in the event that the management processor is taken to be a management server and the host24is taken to be an agent, as shown inFIG. 4(d), when files on a file group management table T4are taken as the target of observation and an action takes place for a file described in a string of this file name, the management processor taken as the management server is notified of this information.

Information relating to a file group name34, weighting36, file name38, key file40, located tier42, capacity44, and file demotion conditions46is stored in the file group management table T1, and information relating to a file group name48, key file conditions50, promotion conditions52, demotion conditions54, and key file name56is stored in the key file management table T2. Information relating to a tier name58, total tier capacity60, and used tier capacity62is stored in the tier management table T3. Further, information relating to a file group name64, file name66, key file68, located tier70, and file demotion conditions72is stored in the file group management table T4.

The management processor built into the disc adapter16is equipped with a setting section for setting files belonging to each of the file groups A and B belonging to the uppermost Tier1as files to be observed (key files), a promotion condition determination section for determining whether or not promotion conditions are satisfied when a specific action from the host24occurs for files to be observed, a promotion section for promoting files belonging to the same file group as files to be observed that an action is received for when the promotion condition determination section determines that promotion conditions are satisfied, a demotion condition determination section for determining whether or not an item satisfying demotion conditions is present within files that are the subject of demotion based on time relating to processing of files that are the target of demotion of attribute information for files that are the target of demotion other than files subject to observation, and a demotion section for demoting files satisfying the demotion conditions to the lowest storage tier even for the tier at the current time when the demotion condition determining section determines that demotion conditions are satisfied.

Next, a description is given in accordance with a flowchart ofFIG. 5of processing when the host24is taken as an agent, the management processor of the disc adapter16is taken as a management server, an action satisfying the promotion conditions for the key file is generated, and files of the file group containing this key file are promoted to an uppermost tier. First, the host24awaits an action with respect to a file (key file) that is subject to observation (S1). When an action for a file that is subject to observation is detected (S2), the management server is notified of the generation of an action for a file that is subject to observation (S3). For example, when A file01is set as a key file, when an action such as newly producing, updating, referring or copying occurs as a specific action for the A file01, the host24notifies the management server of the content of this action.

The management server then executes file promotion processing in accordance with the management software. The management software then carries out processing such as deciding tiers for moving files to, deciding a key file, receiving messages from the host24, issuing tier moving instructions for files to the host24, and issuing key file changing instructions to the host24based on the file group management table T1, the key file management table T2, and the tier management table T3.

Specifically, when a file promotion instruction is received from the management software (S5), the management server acquires one file name66and located tier70from the file group management table T4, and determines whether or not the acquired file is present in Tier1(S7). For example, as A file03and A file04of the files belonging to file group A are in Tier2and Tier3, respectively, these files are promoted to Tier1(S8). After this, the management server updates information of the file group management table T4to the effect that the files belonging to file group A are all in Tier1(S9). Next, the management server determines whether or not an unprocessed file is present (S10). When an unprocessed file is present, the processing of step S6is returned to, and when processing of all of the files is complete, the update software is notified of table updating (S11), the processing of this routine is complete.

On the other hand, in file promotion processing of step S4, as shown inFIG. 6, the management server awaits notification from the host24that is the agent (S21). When notification is received from the host24(S22), the management server searches for a file name indicating notification of receipt in accordance with file group management table T1(S23). For example, when an action is generated for A file01, the management server searches the file group management table T1and determines whether or not A file01belonging to file group A is a key file (S24). At this time, the management server searches the file group management table T1, and when A file01is determined to be a key file, the key file management group T2is searched, and it is determined whether or not an action of the notified content satisfies the content of the promotion conditions52(S25). Next, when the action of the notified content satisfies the promotion conditions, the management server issues an instruction to promote all of the files within the file group A that the key file (A file01) belongs to is issued to the host24(S26), and the processing of this routine is complete.

In this way, according to this embodiment, it is possible to relocate all of the files belonging to file group A from the time of starting utilization to Tier1by setting A file01used first of the files belonging to the file group A as the key file.

Next, a description is given of processing at the time of demotion to a lower tier than the tier of the current time when the host24is taken to be an agent, the management processor of the disc adapter16is taken to be a management server, and a file of the file group satisfies the demotion conditions. This processing is executed at fixed time periods by the host24, and the host24then searches the file group management table T4for the demotion conditions for the file group subject to observation and confirms these conditions (S31). After this, the host24searches the file group management table T1for the conditions for the file subject to observation (key file), and confirms these conditions (S32). Next, the host24determines whether or not the file is a key file (S33). For example, the host24searches the file group management table T1and determines whether or not A file03of the files belonging to the file group A is a key file. When it is determined that A file03is not a key file, it is determined whether or not A file03satisfies the demotion conditions (S34). When it is determined that A file03satisfies the demotion conditions, the host24demotes A file03that is the file to a tier that is one level lower (S35). Namely, the host24demotes A file03from Tier2to Tier3, and the processing of this routine is complete.

Here, processing when the file satisfies the demotion conditions is executed at a time where time x weighting coefficient exceeds a threshold value. For example, the time from the time of day of the final update, the time from the time of day of the final reference, the time from the time of day of final promotion to the uppermost tier, or the time from the time of day of final demotion to the lowermost tier can be used as the time in this case, and the weighting of the file group designated by the user, the file size, date of production, or WORM attribute may be used as the weighting coefficient.

When the value of the weighting is made small, the weighting of the file group becomes high, the weighting coefficient becomes small to the extent that the value of the weighting is small, and it becomes difficult to exceed the threshold value. Namely, it is more difficult for files of file groups of a higher importance to be demoted to a lower tier. Further, the threshold value is more easily exceeded for a larger file size. Namely, demotion to a lower tier is easier for a larger size. As a result, it is possible to reduce capacity used at the uppermost tier. Further, demotion to a lower order tier also occurs more easily when the data of production of the weighting coefficient is older. Values are designated, for example, every Read/Write/Execute as a WORM attribute and are combined and calculated. For example, Read is taken as 1, Write as 2, and Execute as 3, and when a coefficient taking the sum of these as a denominator is used, the ease of demotion becomes Read only>Read Write>Read Write Execute.

Next, a description is given of key file determination processing in accordance with the flowchart ofFIG. 8. The determination of this key file may be executed in a manner triggered by a specific action with respect to the file group such as observation in fixed time periods or adding a new file, etc. Specifically, the management processor of the disc adapter16searches the key file conditions50of the key file management table T2and the key file name56, confirms the key file conditions of the file group subject to observation (S41), searches the file group management table T4, and selects one file from within the file group (S42). For example, the management processor selects, for example, A file03as the file within file group A based on the file name66of file group management table T4, key file68, and located tier70, compares A file01that is the key file for the current time and A file03that is the selected file (S43), and determines whether or not the selected file is the same as the key file of the current point (S43). When the selected file A file03is different to A file01that is the key file at the current time, it is determined whether or not the selected A file03satisfies the key file conditions to a greater extent than A file01that is the key file (S45). When this is not satisfied, a determination is made as to whether or not files that have not yet been compared remain (S46), and the processing of step S42is returned to. On the other hand, when it is determined that the conditions are satisfied, the management processor changes key file flags for the A file01that is the key file for the current time and the key file flag for the A file03that is the selected file (S47). Namely, the management processor changes A file01to “False” with respect to the key file68of the file group management table T4, and changes the key file68for the A file03to “True”. Next, the management processor updates the key file name56corresponding to a key file condition A1of the key file conditions50of key file management table T2to “A file03”, update information is issued for the host24(S49), and the processing of this routine is complete.

In this way, it is possible to dynamically change key files by designating conditions for the key files, and it is possible to constantly maintain optimization of promotion/demotion conditions for files belonging to file groups represented by a key file.

While a file is promoted, as shown inFIG. 9(a), for example, a moving method may be adopted where, at the time of file promotion of file F21belonging to Tier2, file F21on Tier2is deleted, and file F21is moved to Tier1as file F11, or as shown inFIG. 9(b), a copying method may be adopted where file F21existing on Tier2is copied to Tier1at the time of file promotion as file F11while file F21′ that is the actual file itself remains on Tier2.

On the other hand, while a file is demoted, as shown inFIG. 10(a), a moving method may be adopted where file F11present at Tier1is moved to Tier2as file F21at the time of file demotion and file F11of Tier1is deleted, or as shown inFIG. 10(b), an updating method may be adopted where file F11′ present at Tier1is changed as file F21of Tier2, and the file F21after changing is updated as the actual file F21′ at Tier2. Further, as shown inFIG. 10(c), it is also possible to adopt a deletion method for demotion corresponding to the copying method for the time of file promotion. In this event, file F11′ present at Tier1is demoted as actual file F21of Tier2after changing as file F21of Tier2. In this event, file F21is deleted after changing, and only the actual file F21on Tier2is taken to be a file that is the target of processing.

Next, a description is given of an embodiment where the present invention is applied to a patient management system for a hospital based onFIG. 11. The storage system of this embodiment divides a file group into file group A for managing patient A information and a file group B for managing patient B information, with information belonging to each of file group A and file group B being stored divided between two tiers of Tier1and Tier2.

For example, a reception ledger A file F11that is a key file and a set of accounts file F12are relocated at Tier1of the files belonging to file group A, and a clinical chart Al file F21, clinical chart A2file F22, clinical chart A3file F23, examination record A file F24and admission record A file F25are relocated at Tier2. a reception ledger B file F13that is a key file, clinical chart B1file F14, clinical chart B2file F15, and set of accounts B file F16are relocated at Tier1of files belonging to file group B.

A configuration for the file group management table T1used by the management server at this time is shown inFIG. 12(a), a configuration for the key file management table T2is shown inFIG. 12(b), a configuration for the Tier management table T3is shown inFIG. 12(c), and a configuration for the file group management table T4at the host is shown inFIG. 12(d). Information relating to a file group name34, weighting36, file name38, key file40, located tier42, capacity44, and file demotion conditions46is stored in the file group management table T1, and information relating to a file group name48, key file conditions50, promotion conditions52, demotion conditions54, and key file name56is stored in the key file management table T2. Information relating to a tier name58, total tier capacity60, and used tier capacity62is stored in the tier management table T3. Further, information relating to a file group name64, file name66, key file68, located tier70, and file demotion conditions72is stored in the file group management table T4. In this case, patient A information and patient B information is described at file group names34,48and64, the reception ledger A, clinical chart A1, clinical chart A2, clinical chart A3, examination record A, admission record A, and set of accounts A are described at the file name38corresponding to patient A information for file group names34and64, and the reception ledger B, clinical chart B1, clinical chart B2, and set of accounts B are described in file names38and66corresponding to the patient information B for file group names34and64.

Here, when an update action occurs with respect to reception ledger A file F11that is a key file, the host24that is an agent notifies the management server (management processor) that an update action has occurred at the reception ledger A file F11. The management server then confirms that an update action satisfying the promotion conditions has occurred at the key file belonging to the file group A. The management server then confirms the capacity of Tier1using the Tier management table T3(the used capacity of Tier1is 49 GB with regards to the total capacity of Tier1of 50 GB) and it is determined that all of files F21, F22, F23and F24present in Tier2cannot be promoted to Tier1with the current situation remaining as is. In order to ensure the capacity of Tier1, the management server determines the demotion of files for patient B information of a light (low) weighting to Tier2from patient A information, and determines the promotion of all of the files F21, F22, F23, F24and F25to Tier1, and issues an instruction to demote files for patient B information to the host24.

The host24demotes the clinical chart B1file F14, clinical trial B2file F15, and set of accounts B file F16to Tier2as files for patient B information. At this time, host24assigns WORM attributes to the clinical chart B1file F14and the clinical trial B2file F15. The clinical chart B1file F14and clinical chart B2file F15are then demoted to Tier2using the deletion method, and the set of accounts B file F16is demoted to Tier2using the updating method. The host24then notifies the management server of this when all of the files for patient B information are demoted to Tier2. The management server receiving this notification then issues an instruction to promote files of the patient A information to Tier1to the host24. The host24executes processing to promote all of the files F21, F22, F23, F24and F25present in Tier2of the files belonging to the file group A to Tier1using the copying method. When moving of all of the files is complete, the host24notifies the management server that promotion of all of the files is complete, and file promotion processing is carried out.

The state of the files of the storage system when file promotion processing finishes is shown inFIG. 13. The clinical chart B1file F14, clinical chart B2file F15, and set of accounts B file F16are demoted to Tier2, in place of which clinical chart A1file F21, clinical chart A2file F22, clinical chart A3file F23, examination record A file F24and admission record A file F25are promoted to Tier1. At this time, the column “Tier 2” of the clinical chart A1, clinical chart A2, clinical chart A3, examination record A, and admission record A of located Tier42of the file group management table T1is changed to “Tier 1”, and the column “Tier 2” of the clinical chart A1, clinical chart A2, clinical chart A3, examination record A, and admission record A of located Tier70of file group management table T4for host use is changed to “Tier 1”.

According to this embodiment, when an action relating to patient A occurs, it is possible for all of the files relating to patient A to be relocated to Tier1, and the information relating to patient A can therefore be rapidly extracted from Tier1and utilized.