US7330950B2

Storage device

Summary by NHIP

Data migration method

The method defines hierarchical storage classes and life cycle models to manage data objects across coupled storage systems. It detects a second storage system and requests its area characteristics to facilitate migration based on managed stage relations.

Claim Score by NHIP

Read claim 6, the broadest

Abstract

A storage device is provided with a file I/O interface control device and a plurality of disk pools. The file I/O interface control device sets one of a plurality of storage hierarchies defining storage classes, respectively, for each of LUs within the disk pools, thereby forming a file system in each of the LUs. The file I/O interface control device migrates at least one of the files from one of the LUs to another one of the LUs of an optimal storage class, based on static properties and dynamic properties of each file.

US7330950B2, drawing sheet 1 — Sheet 1 of 17

Term

Term ended

Expired 12 April 2025, 1.5 years ago.

10 claims: 2 independent, 8 dependent

1
A data migration method for a system including a first storage system having a first controller and a plurality of first disk devices coupled to the first controller, the method comprising steps of:(a) providing a plurality of storage areas, having various characteristics, by the plurality of first disk devices;(b) defining storage classes, being hierarchical attributes of storage areas, of the plurality of storage areas of the first storage system, based on the characteristics of the plurality of storage areas of the first storage system, by the first controller;(c) defining life cycle models, each having a plurality of stages associated with usage statuses of data and a condition of a stage change, for data objects to be stored in the system, by the first controller;(d) managing, by the first controller, a relation between the stages of the life cycle models and the storage classes;(e) applying a first life cycle model of the life cycle models to a certain data object to be stored in the system;(f) based on the relation managed by the first controller and the first life cycle model, storing the certain data object, by the first controller, in a first storage area of the plurality of storage areas of the first storage system, the first storage area being categorized in a first storage class of the storage classes, the first storage class being related to a first stage included in the first life cycle model, when the certain data object is in the first stage of the first life cycle model;(g) detecting, by the first controller, a second storage system having a second controller and a plurality of second disk devices coupled to the second controller, another plurality of storage areas being provided by the plurality of second disk devices, when the second storage system is coupled to the first storage system;(h) issuing a request to obtain characteristics information of the another plurality of storage areas of the second storage system from the first controller to the second controller;(i) defining, by the first controller, the storage classes of the another plurality of storage areas of the second storage system based on the characteristics information of the another plurality of storage areas of the second storage system obtained from the second controller in response to the request;(j) based on the relation managed by the first controller and the first life cycle model, selecting, by the first controller, a second storage area of the another plurality of storage areas of the second storage system as a migration target, the second storage area being categorized in a second storage class of the storage classes, the second storage class being related to a second stage included in the first life cycle model;(k) controlling, by the first controller, a migration operation of the certain data object from the first storage area to the second storage area, when the certain data object is in the second stage of the first life cycle model.
6
Broadest claimClaim Score 15, narrow(NHIP)A system for storing data in a plurality of storage areas, comprising:a first controller;a plurality of storage areas, having various characteristics, provided by a plurality of first disk devices coupled to the first controller;storage class information, managed by the first controller, defining storage classes of the plurality of storage areas, wherein the storage classes are hierarchical attributes of the plurality of storage areas determined based on the characteristics of the plurality of storage areas;life cycle information, managed by the first controller, defining life cycle models, each including a plurality of stages associated with usage statuses of data, applied to data objects to be stored in the system;and relation information, managed by the first controller, indicating a relation between the stages of the life cycle models and the storage classes, wherein a first life cycle model selected from the life cycle models is applied to a certain data object, wherein when the certain data object is in a first stage of the first life cycle model, the first controller controls to store the certain data object in a first storage area of the plurality of storage areas, the first storage area being categorized in a first storage class defined by the storage class information, the first storage class being related to the first stage of the first life cycle model according to the relation information, wherein when a second storage system including a second controller and a plurality of second disk devices configuring another plurality of storage areas is coupled to the first controller, the first controller detects the second storage system. wherein the first controller issues a request to obtain characteristics information of the another plurality of storage areas of the second storage system from the second controller, wherein the first controller defines the storage classes of the another plurality of storage areas of the second storage system based on the characteristics information of the another plurality of storage areas of the second storage system obtained in response to the request, wherein the first controller selects a second storage area of the another plurality of storage areas of the second storage system as a migration target, the second storage area being categorized in a second stage class according to the storage class information, the second storage class being related to a second stage included in the first life cycle model according to the relation information, wherein when the certain data object is in the second stage of the first life cycle model, the first controller controls a migration operation of the certain data object from the first storage area to the second storage area.

Independent claims2

234 paragraphs in 4 sections, as filed

0001This is a continuation of application Ser. No. 10/775,886 filed Feb. 10, 2004, which application is hereby incorporated by reference in its entirety.

BACKGROUND OF THE INVENTION

00021. Field of the Invention

0003The present invention relates to a storage device used in a computer system.

00042. Related Background Art

0005In a conventional system, a high-speed storage device and a low-speed storage device may be connected to a computer called a hierarchical storage. In the system, files that are frequently used are stored in the high-speed storage device such as a magnetic disk device, while files that are not frequently used are stored in the inexpensive, low-speed storage device such as a tape device. Which files should be placed, i.e., stored, in which storage device is determined by using a table that manages access frequency of each file.

0006In another conventional system, a plurality of logical storage devices having different processing speeds and storage capacities are configured within a storage device that is connected to a computer and used. Such a system may be represented by disk array subsystems. In this system, the storage device manages as statistical information the frequency of accesses from the computer to data stored in the storage device, and, based on the statistical information, transfers data with high access frequency to logical storage devices with higher performance.

0007The first set of problems entailed in the prior art is that there is a high dependency on the computer connected to the storage device, that there is a limitation in the system configuration, and that it is difficult to simplify the system management.

0008In the conventional system described above, a hierarchical storage control is realized through software operating on the computer. The hierarchical storage control refers to a data storage control for controlling a plurality of storage regions having different processing speeds and storage capacities such that the storage regions can be changed according to the frequency of data usage. In other words, the hierarchical storage control refers to controlling to select, based on the property of data such as frequency of data usage, an appropriate storage region from among a plurality of storage regions having different properties in terms of processing speed and/or storage capacity, and to store the data in the storage region selected. However, when the system configuration is altered, such as when an old computer is replaced by a new computer, maintaining the system can be difficult due to such reasons as the system configuration of the new computer not being able to take over the software's control information.

0009Also in the conventional system described above, although a hierarchical storage control is implemented on a per-logical storage device basis, a technology for the storage device to recognize a data structure of data stored in the logical storage device or a technology for executing exclusive control are not disclosed. As a result, it would be difficult for a plurality of computers to share the same logical storage devices, and integrating storage devices used by a plurality of computers in order to reduce the management cost of the computer system would require imposing certain limitations on the configuration of the computer system, such as allocating a logical storage device for each computer.

0010The second problem is that optimal placement of data according to the life cycle or type of data is difficult.

0011According to the conventional technology, data that had high access frequency in the past is assumed to have high access frequency in the future as well, and the storage regions in which the data is stored are determined based on statistical information regarding data access frequency and on used capacity of storage regions that can be accessed at high-speed. The processing efficiency can be improved by increasing the probability with which data with high access frequency can reside in a storage device that can be accessed at high-speed. However, there are no technologies disclosed for determining storage regions in which to store data by taking into consideration differences in data properties that are dependent on the data's life cycle stage, i.e., the time elapsed since the corresponding file was generated, the type of application that generates and uses the data, and the type of data itself.

0012The third problem is that the effect of the hierarchical storage control is small.

0013Although the conventional system described above executes a hierarchical storage control by taking advantage of the difference in capacity and price between magnetic tapes and magnetic disks, the difference in capacity and price between magnetic tapes and magnetic disks have been growing smaller in recent years; consequently, the effect of cost optimization and cost reduction through the use of hierarchical storage control has also been growing smaller. Furthermore, due to the fact that the access speed to magnetic tapes is extremely slow compared to access speed to magnetic disks, it is difficult to use magnetic tapes as storage device for online access.

0014In the conventional system described above, a hierarchical storage control is executed by taking advantage of the difference in price and performance resulting from different RAID configurations of magnetic disks; however, since the price difference results only from the difference in the degree of redundancy in RAID configurations, the only cost reduction that can be hoped for is the cost reduction equivalent only to the difference in the degree of redundancy.

SUMMARY OF THE INVENTION

0015The present invention relates to a control method or a storage device that can execute a hierarchical storage control for file storage positions without being dependent on the OS or applications executed on a host computer.

0016The present invention also relates to a hierarchical storage control method for a plurality of computers to share files, or to provide a storage device that executes such a hierarchical storage control.

0017The present invention also relates to a control method or a storage device that can execute a hierarchical storage control according to file properties.

0018The present invention further relates to a hierarchical storage control method with high cost reduction effect, or to provide a storage device that executes such a hierarchical storage control.

0019In accordance with an embodiment of the present invention, a storage device comprises a plurality of storage regions having different properties, an interface control device that accepts from one or more computers access requests containing file identification information, and an interface control device for accessing storage regions that store data of the file designated by identification information, wherein the interface control device controls storage of file data in one of a plurality of storage regions according to the file property.

0020Other features and advantages of the invention will be apparent from the following detailed description, taken in conjunction with the accompanying drawings that illustrate, by way of example, various features of embodiments of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

0021<figref idref="DRAWINGS">FIG. 1</figref> is a diagram of an example of the configuration of a computer system in accordance with an embodiment of the present invention.

0022<figref idref="DRAWINGS">FIG. 2</figref> is a diagram of an example of the exterior appearance of a storage device.

0023<figref idref="DRAWINGS">FIG. 3</figref> is a diagram of an example of the exterior appearance of an adapter board.

0024<figref idref="DRAWINGS">FIG. 4</figref> is a diagram of an example of the configuration of a NAS channel adapter.

0025<figref idref="DRAWINGS">FIG. 5</figref> is a diagram of an example of programs stored in a file system control memory.

0026<figref idref="DRAWINGS">FIG. 6</figref> is a diagram of an example of programs stored in a disk array control memory.

0027<figref idref="DRAWINGS">FIG. 7</figref> is a diagram of an example of the relationship among disk pools, LUs and file systems.

0028<figref idref="DRAWINGS">FIG. 8</figref> is a diagram of an example of a storage class management table.

0029<figref idref="DRAWINGS">FIG. 9</figref> is a diagram of an example of a filename management table.

0030<figref idref="DRAWINGS">FIG. 10</figref> is a diagram of an example of a file storage management table and a buffer management table.

0031<figref idref="DRAWINGS">FIG. 11</figref> is a diagram of an example of a file property information management table.

0032<figref idref="DRAWINGS">FIG. 12</figref> is a diagram of an example of a file storage management table.

0033<figref idref="DRAWINGS">FIG. 13</figref> is a diagram of an example of the second configuration of a system in accordance with another embodiment of the present invention.

0034<figref idref="DRAWINGS">FIG. 14</figref> is a diagram of an example of the third configuration of the system in accordance with another embodiment the present invention.

0035<figref idref="DRAWINGS">FIG. 15</figref> is a diagram of an example of the fourth configuration of the system in accordance with another embodiment the present invention.

0036<figref idref="DRAWINGS">FIG. 16</figref> is a diagram of a configuration example of a NAS node.

0037<figref idref="DRAWINGS">FIG. 17</figref> is a diagram of a configuration example of a Fibre Channel node.

0038<figref idref="DRAWINGS">FIG. 18</figref> is a diagram of a configuration example of an IP node.

0039<figref idref="DRAWINGS">FIG. 19</figref> is a diagram of a configuration example of a disk array node.

PREFERRED EMBODIMENTS OF THE INVENTION

0040The following is a description of embodiments of the present invention. The following embodiments do not limit the present invention.

Embodiment 1

0000(1) Example of System Configuration (<figref idref="DRAWINGS">FIG. 1</figref>)

0041<figref idref="DRAWINGS">FIG. 1</figref> is a diagram indicating an example of a computer system including a storage device 1 (it is also called a storage system), to which the present invention is applied. In the following, x may be any integer.

0042The storage device 1 is a disk array system comprising a disk controller (hereinafter called “DKC”) 11 and a plurality of magnetic disk devices (hereinafter simply called “disks”) 170x and 171x. In the present embodiment, the storage device 1 is provided with two types of disks 170x and 171x. 170x are Fibre Channel (hereinafter called “FC”) disks with FC-type interface, while 171x are serial AT attached (hereinafter called “SATA”) disks with serial ATA-type (SATA-type) interface. A plurality of FC disks 170x makes up an FC disk pool 0 (170), while a plurality of SATA disks 171x makes up a SATA disk pool 1 (171). The disk pools will be described in detail later.

0043Next, the configuration of the DKC 11 of the storage device 1 will be described. The DKC 11 comprises one or more NAS channel adapters 110x, one or more Fibre Channel adapters 111x, a plurality of disk adapters 12x, a shared memory 13 (hereinafter called “SM”), a shared memory controller 15 (hereinafter called “SMC”), a cache memory 14 (hereinafter called “CM”), and a cache memory controller 16 (hereinafter called “CMC”).

0044The NAS channel adapters (hereinafter called “CHN”) 110x are interface control devices connected by file I/O interfaces to computers 40x (hereinafter called “NAS hosts”), which are connected to a local area network (hereinafter called “LAN”) 20 or a LAN 21.

0045The Fibre Channel adapters (hereinafter called “CHF”) 111x are interface control devices connected by block I/O interfaces to computers (hereinafter called “SAN hosts”) 50x, which are connected to a storage area network (hereinafter called “SAN”) 30. Hereinafter, CHN and CHF are collectively called channel adapters (hereinafter called “CH”).

0046The disks 17x are connected to the disk adapters 12x. Each disk adapter (hereinafter called “DKA”) 12x controls input and output to and from one or more disks 17x connected to itself.

0047The SMC 15 is connected to the CHN 110x, the CHF 111x, the DKA 12x and the SM 13. The SMC 15 controls data transfer among the CHN 110x, the CHF 111x, the DKA 12x and the SM 13. The CMC 16 is connected to the CHN 110x, the CHF 111x, the DKA 12x and the CM 14. The CMC 16 controls data transfer among the CHN 110x, the CHF 111x, the DKA 12x and the CM 14.

0048The SM 13 stores a disk pool management table 131. The disk pool management table 131 is information that is used to manage the configuration of the disk pools.

0049The LANs 20 and 21 connect the CHNs 110x to the NAS hosts 40x. Generally, Ethernet® is used for LAN. The SAN 30 connects the CHFs 111x to the SAN hosts 50x. Generally, Fibre Channel is used for SAN. However, an IP network can be used as the SAN, such that iSCSI, by which SCSI commands according to SCSI protocol are encapsulated into IP packets for sending and receiving, is used among equipment connected to the SAN. The SAN 35 according to the present embodiment is a dedicated SAN for connecting the storage device 1 and no SAN hosts are connected to the SAN 35.

0050In the storage device 1, all CHs can access the CM 14, the SM 13, any DKAs 12x and any disks 17x, via the CMC 16 or the SMC 15.

0051The storage device 1 shown in <figref idref="DRAWINGS">FIG. 1</figref> has both the SAN interfaces (CHFs 111x) for connecting to the SAN hosts 50x and the NAS interfaces (CHNs 110x) for connecting to the NAS hosts 40x, but the present embodiment can be implemented even if the storage device 1 has only the NAS interfaces.

0000(2) Example of Exterior Appearance of Storage Device (<figref idref="DRAWINGS">FIG. 2</figref>)

0052<figref idref="DRAWINGS">FIG. 2</figref> is a diagram of an example of the exterior appearance of the storage device 1.

0053A DKC unit 19 stores the CHNs 110x, the CHFs 111x, the DKAs 12x, the SM 13 and the CM 14, which are components of the DKC 11. The SM 13 actually comprises a plurality of controller boards 13x. The CM 14 also comprises a plurality of cache boards 14x. Users of the storage device 1 can increase or decrease the number of such boards in order to configure the storage device 1 with the CM 14 and the SM 13 having the desired storage capacity. Disk units (hereinafter called “DKU”) 180 and DKUs 181 store the disk pool 170 and the disk pool 171, respectively.

0054Adapter boards built-in with the CHNs 110x, the CHFs 111x, the DKAs 12x, the controller boards 13x and the cache boards 14x are stored in slots 190. According to the present embodiment, the shape of the slots 190, the size of the adapter boards and the shape of connectors are made uniform regardless of the type of adapter boards or the type of interface, which maintains compatibility among various types of boards. As a result, in the DKC unit 19, any adapter board can be mounted into any slot 190 regardless of the type of the adapter board or the type of the interface. Furthermore, users of the storage device 1 can freely select the number of adapter boards for the CHNs 110x and the CHFs 111x in order to mount the number of the CHNs 110x and the CHFs 111x selected into the slots 190 of the DKC unit 19.

0000(3) Example of Exterior Configuration of Adapter Board (Hereinafter Called “NAS Board”) with the CHN 110X Built-In (<figref idref="DRAWINGS">FIG. 3</figref>)

0055<figref idref="DRAWINGS">FIG. 3</figref> is a diagram of an example of the exterior configuration of a NAS board. A connector 11007 is connected to a connector of the DKC unit 19. An interface connector 2001 is Ethernet®-compatible and can be connected to Ethernet®.

0056According to the present embodiment, due to the fact that the shape of the connector on adapter boards is uniform regardless of the type of the adapter board as described earlier, the adapter boards with built-in CHNs 110x and the adapter boards with built-in CHFs 111x have connectors of the same shape. On the adapter boards with the built-in CHFs 111x, the interface connector 2001 is Fibre Channel-compatible and configured to be connected to Fibre Channel.

0000(4) Example of Configuration of NAS Board (or CHN) (<figref idref="DRAWINGS">FIG. 4</figref>)

0057<figref idref="DRAWINGS">FIG. 4</figref> is a diagram of an example of the configuration of the CHN 110x. A file access control CPU 11001 is a processor for controlling file access. A LAN controller 11002 is connected to the LAN 20 via the interface connector 2001 and controls sending and receiving of data to and from the LAN 20. A file access control memory 11004 is connected to the file access control CPU 11001. The file access control memory 11004 stores programs executed by the file access control CPU 11001 and control data.

0058A disk array control CPU 11008 is a processor for controlling a disk array. The disk array refers to a storage device consisting of a plurality of disks. Disk arrays in which at least one of a plurality of disks stores redundant data to provide fault tolerance are called RAIDs. RAIDs are described later. A disk array control memory 11009 is connected to the disk array control CPU 11008 and stores programs executed by the disk array control CPU 11009 and control data. An SM I/F control circuit 11005 is a circuit for controlling access from the CHNs 110x to the SM 13. A CM I/F control circuit 11006 is a circuit for controlling access from the CHNs 110x to the CM 14. An inter-CPU communications circuit 11007 is a communications circuit used when the file access control CPU 11001 communicates with the disk array control CPU 11008 in order to access disks.

0059The present embodiment indicates an example of an asymmetrical multiprocessor configuration in which two processors, the file access control CPU 11001 and the disk array control CPU 11208, are mounted on each CHN 110x; however, each CHN 110x can be configured by mounting a single processor that executes both the file access control and the disk array control, or as a symmetrical multiprocessor configuration in which two or more processors are mounted as equivalents to execute the file access control and the disk array control.

0060The configuration of each CHF 111x is the configuration shown in <figref idref="DRAWINGS">FIG. 4</figref>, except that components shown in top half of <figref idref="DRAWINGS">FIG. 4</figref>, namely the LAN controller 11002, the file access control CPU 11001, the file access control memory 11004 and the inter-CPU communications circuit 11007, are replaced by a Fibre Channel controller.

0000(5) Example of Programs Stored in File Access Control Memory (<figref idref="DRAWINGS">FIG. 5</figref>)

0061<figref idref="DRAWINGS">FIG. 5</figref> is a diagram of an example of programs and control data stored in the file access control memory 11004 of the CHN 110x. An operating system program 110040 is used for the management of programs as a whole and for input/output control. A LAN controller driver program 110041 is used for the control of the LAN controller 11002. A TCP/IP program 110042 is used for the control of TCP/IP, which is the communications protocol for LAN. A file system program 110043 is used for managing files stored in the storage device 1. A network file system program 110044 is used for controlling NFS and/or CIFS, which are protocols for providing files stored in the storage device 1 to the NAS hosts 40x. A volume control program 110045 is used for controlling the configuration of each logical volume by combining a plurality of logical disk units (hereinafter called “LU”), each of which is a unit of storage region set within the disk pools 17x. An inter-CPU communications driver program 110046 is used for controlling the inter-CPU communications circuit 11007, which is used for communication between the file access control CPU 11001 and the disk array control CPU 11008.

0062The file system program 110043 includes the following: <ul id="ul0001" list-style="none"><li id="ul0001-0001" num="0063">1) a file open processing section 1100431 for executing a file open processing when using a file;</li><li id="ul0001-0002" num="0064">2) a request processing section 1100432 for executing a processing according to a file access request when a file access request is received;</li><li id="ul0001-0003" num="0065">3) a file storage management section 1100433 for dividing each file into blocks, determining the storage position on a disk for each block, and managing the storage position of each block;</li><li id="ul0001-0004" num="0066">4) a buffer management section 1100434 for managing correlation between each block and a buffer formed in the memory;</li><li id="ul0001-0005" num="0067">5) a file storage management table 1100435 for managing addresses of storage regions on disks that store blocks that make up each file;</li><li id="ul0001-0006" num="0068">6) a filename management table 1100436 for managing filenames of open files and file handlers used to access the file storage management table 1100435 of each file;</li><li id="ul0001-0007" num="0069">7) a buffer management table 1100437 for managing buffer addresses indicating storage regions within buffers corresponding to blocks that make up a file;</li><li id="ul0001-0008" num="0070">8) a file property information management table 1100438 for storing file static properties, such as the file type, the application that generated the file, the intent of the file generator, and file dynamic properties, such as the value of the file that varies according to the file's life cycle stage and the file's access properties;</li><li id="ul0001-0009" num="0071">9) a migration management section 110043A used when executing a processing to migrate files between LUs; and</li><li id="ul0001-0010" num="0072">10) a storage class management table 1100439 that registers for each LU in the storage pool a storage class, described later, and identification information of the storage device in which an LU resides. (6) Configuration of Disk Array Control Memory (<figref idref="DRAWINGS">FIG. 6</figref>) </li></ul>

0073<figref idref="DRAWINGS">FIG. 6</figref> is a diagram of an example of programs stored in the disk array control memory 11009. An operating system program 110090 is used for managing programs as a whole and for controlling input/output. A disk array control program 110091 is used for constructing LUs within the disk pools 17x and for processing access requests from the file access control CPU 11001. A disk pool management program 110092 is used for managing the configuration of the disk pools 17x by using information in the disk pool management table 131 stored in the SM 13. An inter-CPU communications driver program 110093 is used for controlling the inter-CPU communications circuit 11007, which is used for communication between the file access control CPU 11001 and the disk array control CPU 11008. A cache control program 110094 is used for managing data stored in the CM 14 and for controlling cache hit/miss judgments. A DKA communications driver program 110095 is used when accessing an LU in order to communicate with the DKAs 12x, which control the disks 170x and 171x that make up the LU.

0000(7) Configuration of Disk Pools (<figref idref="DRAWINGS">FIG. 7</figref>)

0074<figref idref="DRAWINGS">FIG. 7</figref> is a diagram of an example of the configuration of the disk pools.

0075In the FC disk pool 170 are set two LUs, LU0 (50) and LU1 (51). The LU0 (50) comprises two FC disks, DK000 and DK010, where the DK000 and the DK010 make up RAID 1. The LU1 (51) consists of 5 FC disks, DK001, DK002, DK003, DK004, and DK005, where the five FC disks make up a 4D+1P configuration RAID 5. The RAID 1 and the RAID 5 refer to data placement methods in a disk array and are discussed in detail in “A Case for Redundant Arrays of Inexpensive Disks (RAID)” by D. Patterson, et al., ACM SIGMOD Conference Proceedings, 1988, pp. 109-116. In the LU0 with the RAID 1 configuration, the two FC disks DK000 and DK010 have a mirror relationship with each other. In the meantime, the LU1 having the RAID 5 configuration consists of one or more disks that store data stripes, which store data of files accessed from host computers, and one or more disks that store parity stripes, which are used to retrieve data stored in the data stripes. The LU1 has the 4D+1P configuration RAID 5, which indicates a RAID 5 consisting of four data stripes and one parity stripe. Similar representations will be used hereinafter to indicate the number of data stripes and the number of parity stripes in LUs having the RAID 5 configuration.

0076LU2 (52) is established in the SATA disk pool 171. The LU2 (52) consists of nine SATA disks, DK100, DK101, DK102, DK103, DK104, DK110, DK111, DK112 and DK113, where the nine SATA disks make up an 8D+1P configuration RAID 5.

0077When the capacity of each disk is 140 GB, the LU0 (50) has 140 GB, the LU1 (51) has 560 GB, and the LU2 (52) has 1120 GB in usable storage capacity.

0078Independent local file systems LFS0 (60), LFS1 (61) and LFS2 (62) are established and constructed for the LU0 (50), the LU1 (51) and the LU2 (52), respectively.

0000(8) Storage Class Management Table (<figref idref="DRAWINGS">FIG. 8</figref>)

0079<figref idref="DRAWINGS">FIG. 8</figref> is an example of the configuration of a storage class management table 1100451 stored in the file access control memory 11004 of each CHN 110x. The storage class management table 1100451 is generated by the file access control CPU 11001's executing the file system program 110043 and referring to information stored in the disk pool management table 131 of the SM 13.

0080Although the disk pool management table 131 is not shown, the disk pool management table 131 is stored in the SM 13 and contains information similar to the information in the storage class management table 1100451 for all CHs. In other words, of the information in the disk pool management table 131, the storage class management table 1100451 stored in the file access control memory 11004 of each CHN 110x contains information regarding LUs used by the CHN 110x, but rearranged with the storage class as a key.

0081The following is a description of the configuration of the storage class management table 1100451. A storage class entry (1100451a) stores information indicating storage class. A storage node # entry (1100451b) stores an identification number (called a “storage node number”) of the storage device that makes up each storage class. A disk pool # entry (1100451c) stores a disk pool number that makes up each storage class. An LU # entry (1100451d) stores an LU number set for each disk pool. In an LU type entry (1100451e), information stored indicates whether the corresponding LU is set internally (local) or externally (remote) to the given storage device and whether a file system is set in the LU. In other words, if the LU is within the storage device, “Local” is registered in the LU type entry, while “Remote” is registered if the LU is in a different storage device; if a file system is constructed in that LU, “File” is registered in the LU type entry, while “Block” is registered if no file systems are constructed in the LU. In a RAID Conf. entry (1100451f), information stored indicates the RAID level of the disk array that makes up each LU and the structure of the corresponding disk array, such as data record and parity record number within a parity group. In a usable capacity entry (1100451g) and a used capacity entry (1100451h), information that indicates the total storage capacity of the given LU and information that indicates the storage capacity being used, respectively, are stored.

0082A storage class is a hierarchical attribute provided for each storage region based on the usage of data storage; according to the present embodiment, three attributes of OnLine Storage, NearLine Storage and Archive Storage are defined. In addition, sub-attributes of Premium and Normal are defined for the OnLine Storage. The OnLine Storage is an attribute set for LUs suitable for storing data of files that are frequently accessed, such as files being accessed online and files being generated. Premium indicates an attribute set for LUs suitable for storing data especially requiring fast response. The NearLine Storage is an attribute set for LUs suitable for storing data of files that are not frequently used but are occasionally accessed. The Archive Storage is an attribute set for LUs suitable for storing data of files that are hardly ever accessed and are maintained for long-term storage.

0083<figref idref="DRAWINGS">FIG. 8</figref> indicates that there are the LU0 (50) of the OnLine Storage (Premium) class and the LU1 (51) of the OnLine Storage (Normal) class in the FC disk pool 170 of the storage device 1 (called “STR0”). Further, in the SATA disk pool 171 of the storage device 1 (STR0) is the LU2 (52) of the NearLine Storage class. Moreover, in a different storage device (STR1) is an LU3 (53) of the Archive Storage class in a SATA disk pool. An example of constructing disk pools in different storage devices is described later.

0000(9) Filename Management Table (<figref idref="DRAWINGS">FIG. 9</figref>)

0084<figref idref="DRAWINGS">FIG. 9</figref> shows an example of the filename management table 1100436 that is stored in the file access control memory 11004. The filename management table 1100436 is a table prepared for each file system, where filenames and file handlers are stored in a tree structure for easy searchability. When a file is accessed by one of the NAS hosts 40x, the filename of the file is included in an access request received by the CHN 110x from the NAS host 40x. The CHN 110x uses the filename to search the filename management table 11004 and obtains the file handler that corresponds to the filename, which enables the CHN 110x to refer to the file storage management table 1100435 that corresponds to the file handler.

0085Each filename management table 1100436 is stored in the LU in which the file system that corresponds to the filename management table 1100436 is constructed, and is read to the file access control memory 11004 when necessary and used by the file access control CPU 11001.

0000(10) File Storage Management Table (<figref idref="DRAWINGS">FIG. 10</figref>)

0086<figref idref="DRAWINGS">FIG. 10</figref> is a diagram of an example of the file storage management table 1100435 and the buffer management table 1100437. The file storage management table 1100435 is provided in the file access control memory 11004 for each file and is a table that manages file storage addresses. The file storage management table 1100435 can be referred to by designating a file handler that represents a file.

0087A file property information management table entry stores a pointer for referring to the file property information management table 1100438 for the corresponding file. A size indicates the size of the file in units of bytes. A number of blocks indicates the number of logical blocks used in managing the file, which is done by dividing the file into blocks called logical blocks. Each logical block that stores the file also stores a pointer to the buffer management table 1100437 that corresponds to the logical block.

0088There is one buffer management table 1100437 for each logical block, and each buffer management table 1100437 contains the following. A hash link entry stores a link pointer to a hash table for quickly determining whether a buffer is valid. A queue link entry stores a link pointer for forming a queue. A flag entry stores a flag that indicates the status of the corresponding buffer, i.e. whether valid data is stored in the buffer, whether the buffer is being used, whether the content of the buffer is unreflected on the disk. An equipment number entry stores an identifier of the storage device and an identifier of the LU in which the corresponding logical block is stored. A block number entry stores a disk address number that indicates the storage position of the logical block within the storage device indicated by the equipment number. A number of bytes entry stores the number of bytes of valid data stored in the logical block. A buffer size entry stores the size of the buffer in units of bytes. A buffer pointer entry stores a pointer to the corresponding physical buffer memory.

0089The file storage management table 1100435 is stored in the LU that stores the corresponding file and is read to the memory when necessary for use.

0000(11) File Property Information Management Table (<figref idref="DRAWINGS">FIG. 11</figref>)

0090<figref idref="DRAWINGS">FIG. 11</figref> is an example of the file property information management table 1100438 stored in the file access control memory 11004. The file property information management table 1100438 stores static property information and dynamic property information. The static property information is determined when a file is configured and carries over thereafter. Although the static property information can be intentionally altered, it otherwise remains unaltered. The dynamic property information changes over time after a file is created.

0000(12) Static Property Information

0091The static property information is divided into a file information category and a policy category.

0092The file information category includes basic information of a file. In the file information category, a file type indicates the type of the file, such as a text file, document file, picture file, moving picture file or a voice file. An application indicates the application that generated the file. A date created indicates the date the file was first generated. The time at which the file was generated can be registered in addition to the date the file was created. An owner indicates the name of the user who created the file. An access identifier indicates a range of access authorization for the file.

0093The policy category is information that is set by the user or the application that created the file, and is information that is designated by the user or the application with regard to file storage conditions. An initial storage class is information that indicates the storage class of the LU in which the file is to be stored when the file is stored in a storage device for the first time. An asset value type indicates the asset value of the file. A life cycle model indicates the model applicable to the file from among life cycle models defined in advance. A migration plan indicates the plan applicable to the file from among plans concerning file migration (hereinafter called “migration”) defined in advance.

0094The asset value is an attribute that designates the importance or value attached to the file. An attribute of “extra important,” “important” or “regular,” for example, can be designated as an asset value. The asset value can be used as a supplemental standard for selecting a storage class, i.e., files with an attribute of “important” or higher are stored in LUs that belong to the OnLine Storage class with Premium attribute, or as a standard for selecting a storage class when no life cycle models are designated, for example.

0095In the description of the present embodiment, it will be assumed that files that are “important” or higher are stored in LUs that belong to the OnLine Storage (Premium) class. Needless to say, the present invention is not restricted to such an assumption and different standards may be used to select storage classes of LUs for storing files.

0096The life cycle stages have been named by drawing analogy with life cycle stages of humans to describe how the usage status of a file changes over time, i.e., the period in which data is created is the birth, the period in which the data is updated and/or used is the growth stage, the period in which the data is rarely updated and is mainly referred to is the mature stage, and the period in which the data is no longer used and is archived is the old age. A life cycle model defines the life cycle a file experiences. The most general method of defining a life cycle is to define the stages based on the amount of time that has elapsed since a file was generated. One example is to define the “growth stage,” or the “update stage,” in which there are frequent updates, as one month; the “mature stage,” or the “reference stage,” in which the file is mainly referred to, as one year; and the “old age,” or the “archive stage,” as thereafter. Hereinafter this definition is called a “model 1” and is used in the following description. By varying the time interval of the life cycle model or by defining stages with finer resolution, various life cycle models can be defined and one life cycle model from among a plurality of life cycle models can be selected for use. Furthermore, a specific life cycle model can be applied to a certain type of files, or life cycle models can be applied on a per-application basis such that a specific life cycle model is applied to files created by a certain application. Names of the life cycle stages can be expressed in terms of “growth stage,” “mature stage,” and “old age” that correspond to the life of a person, or in terms of “update stage,” “reference stage,” and “archive stage” based on file behavior. In the present embodiment, the latter expressions are used in order to more clearly indicate the behavior of files.

0097The migration plan defines to which storage class LU a file is transferred according to the file's life cycle stage. One example is a method for storing “update stage” files in OnLine Storage class LUs, “reference stage” files in the NearLine Storage class LUs, and “archive stage” files in Archive Storage class LUs. Hereinafter, this definition is called a “plan 1” and is used in the following description. In addition to this plan, various plans can be defined, such as a plan that defines “update stage” files to be stored in Online Storage (Premium) class LUs, and “reference stage” files in OnLine Storage (Normal) class LUs, while “archive stage” files remain in the NearLine Storage class LUs, and one plan from among a plurality of plans can be selected for use. Furthermore, a specific migration plan can be applied to a certain type of files, or migration plans can be applied on a per-application basis such that a migration plan is applied to files created by a certain application.

0000(13) Dynamic Property Information

0098The dynamic property information is divided into an access information category and a life cycle information category.

0099The access information category includes access statistical information for each file. In the access information category, a time stamp indicates the date and time a given file was last read or written, or the date and time the file storage management table 1100435 of the file was last updated. An access count indicates the total number of accesses to the file. A read count and a write count indicate the number of reads and the number of writes, respectively, to and from the file. A read size and a write size indicate the average value of the data transfer size when reading and writing, respectively, to and from the file. A read sequential count and a write sequential count indicate the number of times there is address continuity, i.e., sequentiality, between two of multiple consecutive accesses in reading or writing.

0100The life cycle information category includes information related to the life cycle of a file. In the life cycle information category, a current life cycle stage indicates the current positioning of a file within its life cycle, i.e., the update stage, the reference stage, or the archive stage. A current storage class indicates the storage class of a storage pool set for the LU that currently stores the file.

0101<figref idref="DRAWINGS">FIG. 11</figref> indicates one example of the file property information, but various other types of property information can be defined and stored in the file property information management table 1100438. Furthermore, an embodiment may use only a part of the property information as necessary.

0000(14) Initial File Placement: A File Open Processing

0102Next, a description will be made as to a file open processing that takes place in the initial placement processing to store a file in a storage device for the first time.

0103Let us assume that the NAS host 0 (400) generated a file abc.doc.

0104The NAS host 0 (400) issues to the CHN0 (1100) an open request for the file abc.doc. The open request includes a filename as identification information to identify the file. Since the open processing is executed to store the file for the first time, the NAS host 0 (400) sends to the CHN0 (1100) the following information included in the file information category and the policy category as the static property information of the file property information, along with the open request. The information sent includes a file type “document,” an application that generated the file “XYZ Word,” and an access identifier “-rw-rw-rw-” as information included in the file information category, as well as an initial storage class “undesignated,” an asset value type “important,” the life cycle model “model 1,” and the migration plan “plan 1” as information included in the policy category.

0105The CHN0 (1100) receives the open request from the NAS host 0 (400) via the LAN controller 11002, and the file access control CPU 11001 executes the file system program 110043.

0106When the file system program 110043 is executed, the open request received is specified through a control by the file access control CPU 11001 as an access request to access the local file system LFS0 (60) based on the directory information of the filename. The file open processing section 1100431 refers to the filename management table 1100436 of the LFS0 (60) and searches for abc.doc. Since it is determined as a result that abc.doc is a file that does not yet exist in the filename management table 1100436 and is to be stored for the first time, the file open processing section 1100431 registers abc.doc in the filename management table 1100436 and assigns a file handler to abc.doc.

0107Next, the file storage management section 1100433 creates the file storage management table 1100435 to correspond to the file handler assigned to the file abc.doc.

0108Next, the file storage management section 1100433 generates the file property information management table 1100438 and correlates it to the file storage management table 1100435 (i.e., a pointer to the file property information management table 1100438 is stored in the file storage management table 1100435); the file storage management section 1100433 then stores in the file property information management table 1100438 the static property information of the file property information for the file abc.doc obtained from the NAS host 0 (400), as well as the date created and owner of the file. Next, the file storage management table 1100435 and the file property information management table 1100438 are written to the LU in which is constructed the file system the file belongs to.

0109Next, the CHN0 (1100) returns the file handler to the NAS host 0 (400) and the open processing is terminated.

0000(15) Initial File Placement: A Data Write Processing

0110Next, a description will be made as to a data write processing executed in the initial placement processing of a file.

0111Using the file handler obtained in the open processing, the NAS host 0 (400) issues to the CHN0 (1100) a write request to store data of the file abc.doc in the storage device 1.

0112When the write request is received by the CHN0 (1100), the file access control CPU 11001 executes the file system program 110043 and uses a method similar to the method used in the open processing to specify that the write request is an access request to access the local file system LFS0 (60).

0113The request processing section 1100432 of the file system program 110043 interprets the access request as a write request based on the information included in the access request received, and uses the file handler designated in the write request to obtain the file storage management table 1100435 of the file that corresponds to the file handler.

0114Next, the file storage management section 1100433 secures buffers required to store the data and determines the storage positions on disks for the file.

0115To determine the storage positions, the file storage management section 100433 refers to the static property information in the file property information management table 1100438. In this case, due to the fact that the life cycle model of the file abc.doc, which is the subject of the write request, is “model 1,” and to the fact that the write request received is an access taking place within one month of the file generation since it is an access request occurring in an initial file placement, the file storage management section 1100433 specifies the current life cycle stage of the file abc.doc as “growth stage.” Further, since the initial storage class is “undesignated” and the asset value type is “important,” the file storage management section 1100433 selects “OnLine Storage (Premium)” as the storage class of the storage pool in which to store the file abc.doc.

0116Next, the file storage management section 1100433 refers to the storage class management table 1100439 and decides to store the file abc.doc in an LU whose storage class is “OnLine Storage (Premium)” and that is specified by “STR0 (i.e., the primary storage device 1)” as the storage node, “FC disk pool 1700” as the disk pool #, and “LU0 (i.e., the local file system LFS0)” as the LU #. The file storage management section 1100433 divides the data of the file into one or more logical blocks based on an appropriate algorithm, determines storage addresses of the logical blocks in the LU0, generates buffer management tables 1100437 to register the storage addresses determined, and stores in the buffer management table entry of the file storage management table 1100435 pointers to the buffer management tables 1100437 generated. Furthermore, the file storage management section 1100433 stores information in the remaining entries of the file storage management table 1100435. In the present embodiment, NULL is registered for all entries for link destinations in the file storage management table 1100435.

0117The file storage management section 1100433 sets the current life cycle stage as “update stage” and the current storage class as “OnLine Storage (Premium)” in the life cycle information category of the dynamic property information of the file property information management table 1100438. The file storage management section 1100433 performs appropriate calculations for information included in the access information category of the dynamic property information before registering the results into the file property information management table 1100438.

0118The request processing section 1100432 executes a processing according to the write request received; and the LAN controller driver program 110041, the TCP/IP program 110042, and the network file system program 110044 are executed by the file access control CPU 11001; as a result, the write data is transferred from the NAS host 0 (400) to the CHN0 (1100) and temporarily stored in the buffer of the file access control memory 11004. Next, the inter-CPU communications driver program 110046 is executed by the file access control CPU 11001, and this causes the write request to be transferred to the disk array control CPU 11008 at proper timing. Upon receiving the write request, the disk array control CPU 11008 caches the write data temporarily in the CM 14 and sends a reply of completion with regard to the write request from the NAS host 0 (400).

0119Next, under the control of the DKA 120 that controls disks that make up the LU0, the write data is stored at proper timing on appropriate disks.

0120As described above, files can be initially placed in storage regions that belong to the appropriate storage class based on the static property information of the file.

0000(16) File Migration Processing (<figref idref="DRAWINGS">FIG. 12</figref>)

0121Next, a migration processing of a file will be described.

0122The migration management section 110043A of the file system program 110043 is activated by the file access control CPU 11001 based on a preset timing.

0123The migration management section 110043A refers to the file property information management table 1100438 of a file included in the local file system set in advance as the subject of the migration processing, and checks whether the file that is the subject of migration exists. The following is a detailed description of a situation in which the file abc.doc is the subject of the migration processing.

0124The migration management section 110043A refers to the file property information management table 1100438 of the file abc.doc and compares the date created to the current date and time. If one month has elapsed since the date created, the migration management section 110043A recognizes that the current life cycle stage has shifted from the “update stage” to the “reference stage” due to the fact that the life cycle model in the static property information indicates “model 1” and that one month, which is the period of the “update stage,” has already passed.

0125Further, due to the fact that the migration plan is “plan 1,” the migration management section 110043A recognizes that the file must be migrated from the LU whose storage class is the “OnLine Storage (Premium)” to an LU whose storage class is the “NearLine Storage.”

0126The migration management section 110043A refers to the storage class management table 1100439 and decides to transfer the file to an LU whose storage class is the “NearLine Storage” and that is designated by “STR0 (i.e., the primary storage device 1)” as the storage node, “SATA disk pool 1710” as the disk pool #, and “LU2 (i.e., a local file system LFS2)” as the LU #.

0127Next, the migration management section 110043A changes the current life cycle stage to “reference stage” and the current storage class to “NearLine Storage” in the dynamic property information of the file property information management table 1100438.

0128The migration management section 110043A defines a unique filename (in this case FILE00001) that is used to manage the file abc.doc within the storage device STR0 (1).

0129The file open processing section 1100431 refers to the filename management table 1100436 of the LFS2 (60) and checks whether the filename FILE00001 is registered in the filename management table 1100436; if it is not registered, the file open processing section 1100431 registers the filename FILE00001 in the filename management table 1100436 and assigns a file handler to the filename FILE00001.

0130Next, the file storage management section 1100433 generates the file storage management table 1100435 and the file property information management table 1100438 to correspond to the file handler assigned to the filename FILE00001. Contents identical to the contents registered in the file property information management table of the file abc.doc are stored in the file property information management table 1100438 generated. The file storage management section 1100433 writes in the LU, which stores FILE00001, the file storage management table 1100435 and the file property information management table 110438 of FILE00001.

0131Next, the file storage management section 1100433 secures buffer regions required to store the data of FILE00001 and determines the storage regions (or the storage positions) within the LU2 for storing the file. Using a method similar to the method used in the data write processing, the file storage management section 1100433 generates the buffer management tables 1100437 to register the storage positions determined, and stores in the buffer management table entry of the file storage management table 1100435 pointers to the buffer management tables 1100437 generated. NULL is registered for all entries for link destinations in the file storage management table 1100435 of the FILE00001 stored in the LFS2.

0132As indicated in <figref idref="DRAWINGS">FIG. 12</figref>, the file storage management section 1100433 changes the link destination node name to STR0, the link destination FS name to LFS2, and the link destination filename to FILE00001 in the file storage management table 1100435 of abc.doc in the LFS0.

0133Next, the request processing section 1100432 reads data of the abc.doc from disks that make up the LU0 to buffers in the file access control memory 11004. The file storage management section 1100433 determines the data read to the buffers in the file access control memory 11004 as data of the FILE00001 to be written to the disks that make up the LU2, and the request processing section 1100432 writes the data to storage regions in the buffers registered in the buffer management tables 1100437.

0134The file storage management section 1100433 clears all buffer management tables 1100437 that can be referred to from pointers registered in the file storage management table 1100435 of the file abc.doc in the LFS0, and registers NULL in entries of these buffer management tables 1100437.

0135The data of the FILE00001 stored in the buffers is stored at proper timing in the LU2 via the CM 14 of the storage device 1 through a procedure similar to the procedure that took place in the data write processing of the initial placement processing. This completes the migration processing.

0136As described above, according to the present embodiment, files can be migrated to storage regions of an appropriate storage class by taking into consideration the life cycle stage of the file based on the migration plan of the file.

0137According to the present embodiment, LUs for storing files can be selected based on a concept of storage classes, and LUs for storing files can be changed, without being dependent on host computers or applications executed on the host computers. As a result, a storage device with storage hierarchy, i.e., a plurality of storage regions with varying properties, having high cost effectiveness can be realized without being dependent on host computers.

0138Further, due to the fact that data is migrated on a per-file basis, same files can be accessed from a plurality of host computers using a file I/O interface, even after the files are migrated.

0139Moreover, a file-based hierarchy storage control can be executed based on static properties of the file, such as the file type, the type of application that generated the file, the intent (policy) of the-file generator, and on dynamic properties of the file, such as changes in the life cycle stage, value and access property of the file.

Embodiment 2

0000(1) Example of System Configuration (<figref idref="DRAWINGS">FIG. 13</figref>)

0140Next, referring to <figref idref="DRAWINGS">FIG. 13</figref>, an example of the system configuration of the second embodiment will be described. In the present embodiment, a hierarchical storage control is executed between storage devices in a system in which a storage device 1 (hereinafter called “STR0”) described in the first embodiment and another storage device 1a (hereinafter called “STR1”) are connected via a network.

0141In <figref idref="DRAWINGS">FIG. 13</figref>, the storage device STRL (1a) is the other storage device connected to the storage device STR0 (1) via a LAN 20; otherwise, the system configuration components are the same as in <figref idref="DRAWINGS">FIG. 1</figref>.

0142In the STR1 (1a), an NCTL0 (1100a) and an NCTL1 (1101a) are NAS controllers, and a disk pool 0 (170a) is a disk pool connected to the NCTL0 and NCTL1.

0143Instead of the SM I/F control circuit 11005 and the CM I/F control circuit 11006 in the configuration of the CHN 1100 according to the first embodiment shown in <figref idref="DRAWINGS">FIG. 4</figref>, the NAS controller NCTLx is provided with an FC controller 11010a for connecting with the disk pool 01700a. The NAS controller NCTLx also has a cache memory CM 14a within the NAS controller, as well as a data transfer control circuit 11011a, which is a control circuit for the cache memory CM 14a. Further, the data transfer control circuit 11011a serves to connect the NAS controller 1100a and the NAS controller 1101a to each other. Although details of the configuration of the NAS controller NCTL1 (1101a) are not shown in <figref idref="DRAWINGS">FIG. 13</figref>, the NAS controller 1101a has a configuration similar to that of the NAS controller 1100a. Components that are assigned the same numbers as components of the CHN 1100 in the first embodiment have the same configuration and the same function as the corresponding components of the CHN 1100.

0144Let us assume that the STR1 is a storage device that is smaller and cheaper than the STR0. Also, as shown in <figref idref="DRAWINGS">FIG. 13</figref>, a CHN0 of the STR0 and the NCTL0 of the STR1 are connected via the LAN 20.

0000(2) Migration Processing of File to the Other Storage Device

0145The following is a description of the operation according to the present embodiment.

0146The CHN0 (1100) of the storage device 1 (STR0) recognizes that the storage device 1a (STR1) of a different type is connected to the LAN 20. The different storage device can be recognized using a method based on information designated in advance by an administrator or a method based on whether or not there is a device that reacts to a broadcast of a command for recognition to network segments of the LAN 20. In order to ascertain the configuration of the STR1, the CHN0 of the STR0 becomes an initiator and issues to the STR1 a command to collect information. The response from the STR1 to the command includes the type of the disk pool and the configuration of LUs that the STR1 has; as a result, by referring to the response, the CHN0 can recognize that the STR1 has the SATA disk pool 170a and that there is a low-cost file type LU having a 15D+1P configuration RAID 5 and with a large capacity of 2100 GB in the disk pool 170a. The CHN0 of the STR0 decides to manage the STR1's LU as a remote LU, i.e., as an LU that is in the other storage device STR1 (1a) but as one of the LUs that are managed by the primary storage device STR0 (1).

0147The CHN0 assigns a number LU3 to the LU that the STR1 has and assigns a remote file system number RFS3 to the file system constructed within the LU. Due to the fact that the LU is in a large capacity, low-cost disk pool, the storage class of the LU is set as “Archive Storage.” Based on a control by a disk array control CPU 11008 of the CHN0, information regarding the LU3 in the STR1, such as the type of the disk pool, the configuration of the LU, the LU number and the storage class, is stored in a disk pool management table 131 of an SM 13 of the storage device 1 (STR0). The CHN of the storage device 1 refers to the disk pool management table. 131 by having a file access control CPU 11001 execute a file system program 110043, and can register information regarding the LU3 in a storage class management table 1100451 in a file access control memory 11004 by copying the information regarding the LU3 from the disk pool management table 131.

0148As described in the first embodiment, let us assume that the NAS host 0 (400) stored the file abc.doc in the LU0 of the STR0 via the CHN0 and that subsequently the file abc.doc was migrated to the LU2 of the STR0 based on a control by the CHN0; in the following, only those parts that differ from the first embodiment in the processing executed to migrate the file abc.doc further to the LU3 in the other storage device STR1 are described.

0149As described in the first embodiment, the file abc.doc's current life cycle stage is “reference stage,” its current storage class is “NearLine Storage,” and its data section is stored under the name FILE00001 in the LFS2 of the LU2 constructed in the SATA disk pool of the STR0, as shown in <figref idref="DRAWINGS">FIGS. 11 and 12</figref>. The filename management table 1100436 in which the filename “abc.doc” is registered and the file storage management table 1100435 for the file abc.doc are in the LFS0. In other words, information regarding the abc.doc is stored in the filename management table 1100436 for the LFS0 and in the file storage management table 1100435 for the file abc.doc in the LFS0. In the meantime, the file property information management table 1100438 is in both the LFS0 and the LFS2. The data section of the file abc.doc has already been migrated to the LU2 in which is constructed the LFS2, which means that the data section of the abc.doc does not reside in the LU0, in which is constructed the LFS0.

0150The migration management section 110043A of the STR0 refers to the file property information management table 1100438 of the abc.doc and compares the date created to the current date and time. If one year has elapsed since the migration, the migration management section 110043A recognizes that the current life cycle stage has shifted from the “reference stage” to the “archive stage” due to the fact that the life cycle model in the static property information for abc.doc indicates “model 1” and that one year, which is the period of the “reference stage,” has already passed. Further, due to the fact that the migration plan is “plan 1,” the migration management section 110043A recognizes that the file must be migrated from an LU whose storage class is “NearLine Storage” to an LU whose storage class is “Archive Storage”.

0151Next, the migration management section 110043A refers to the storage class management table 1100439, selects the LU3 that belongs to the “Archive Storage” class, and decides to transfer the file abc.doc to the LU3. The LU3 has attributes of “STR1 (i.e., the other storage device 1a)” as the storage node, “SATA disk poor” as the disk pool #, and “remote file” as the LU type.

0152Next, the migration management section 110043A changes the current life cycle stage to “archive stage” and the current storage class to “Archive Storage” in the dynamic property information of the file property information management table 1100438 for the abc.doc.

0153Next, the migration management section 110043A defines a unique filename (in this case STR1-FILE00001) that is used to manage the file abc.doc within the storage device STR0 (1).

0154The migration management section 110043A behaves as it were a NAS host and issues to the STR1 an open request for the file STR1-FILE00001. This open processing is an open processing executed in order to store the file for the first time from the perspective of the STR1. For this reason, the STR0 includes in the open request sent to the STR1 the information that the STR0 has in the file property information management table 1100438 as the static property information of the file abc.doc. However, by changing only the initial storage class in the static property information to “Archive Storage” in the information sent, the STR0 expressly designates to the STR1 to store the file STR1-FILE00001 in the Archive Storage class from the beginning.

0155The NCTL0 of the STR1 receives the open request via a LAN controller 11002a, and a file access control CPU 11001a executes a file system program 110043a.

0156When the file system program 110043a is executed, the open request received is specified in a manner similar to the first embodiment as an access request to access the remote file system RFS3; the STR1-FILE00001 is registered in a filename management table 1100436a in a file access control memory 11004a and a file handler is assigned to the STR1-FILE00001 based on a control by the file access control CPU 11001a; a file storage management table 1100435a and a file property information management table 1100438a are created within the file access control memory 11004a and information to be registered in the tables is set. The NCTL0 sends to the migration management section 110043A of the CHN0 the file handler assigned to the STR1-FILE00001, and the open processing is terminated.

0157Next, like the NAS host 0 (400) in the data write processing according to the first embodiment, the migration management section 110043A of the STR0 issues to the STR1 a write request containing the file handler obtained from the NCTL0 of the STR1 in the open processing, and requests to write actual data of abc.doc (i.e., data that is also actual data of FILE00001) as actual data of the file STR1-FILE00001.

0158The file storage management section 1100433a of the STR1 secures buffer regions required to store the write data, determines storage positions on disks of the actual data of the file, and stores the write data received from the STR0 in the buffers.

0159To determine the storage positions, the file storage management section 1100433a refers to the static property information in the file property information management table 1100438a. The file storage management section 1100433a specifies the current life cycle stage of the file STR1-FILE00001 as “archive stage” due to the fact that the life cycle model of the file STR1-FILE00001 is “model 1” and to the fact that more than one year and one month have passed since the file was generated. Further, the file storage management section 1100433a specifies “Archive Storage” as the initial storage class as designated by the STR0.

0160The file storage management section 1100433a sets the current life cycle stage as “archive stage” and the current storage class as “Archive Storage” in the life cycle information category of the dynamic property information of the file property information management table 1100438a. The file storage management section 1100433a further performs appropriate calculations for access information regarding the file STR1-FILE00001 and updates the information in the access information category of the file property information management table 1100438a. NULL is registered for all entries for link destinations in the file storage management table. 100435a of the file STR1-FILE00001.

0161Next, under the control of the NCTL0, the data section of the file STR1-FILE00001 is stored at proper timing on disks that make up the LU3.

0162This concludes the write processing in the STR1 and the processing returns to STR0.

0163The file storage management section 1100433 of the STR0 changes the link destination node name to STR1, the link destination FS name to LFS3, and the link destination filename to STR1-FILE00001 in the file storage management table 1100435 of the FILE00001 in the LFS2. The file storage management section 1100433 then clears all buffer management tables 1100437 that can be referred to from pointers registered in the file storage management table 1100435 of the FILE00001 and enters NULL in all buffer management table entries of the file storage management table 1100435.

0164The preceding transfers the substance of the data section of the file abc.doc from the FILE00001 in the LFS2 of the STR0 to STR1-FILE00001 in the RFS3 of the STR1.

0165After this, whenever an access request is issued by any of the NAS hosts to access the file abc.doc, the CHN of the STR0 refers to the file storage management table 1100435 of the abc.doc in the LFS0 and obtains its link destination node name, FS name and filename, and refers to the file storage management table 1100435 of the FILE00001 in the LFS2 based on the identification information of the link destination obtained (i.e., STR0, LFS2, FILE00001). The CHN of the STR0 further obtains the link destination node name, the FS name and the filename from the file storage management table 1100435 of the FILE00001 in the LFS2 and issues to the NCTL of the STR1 an access request designating identification information of the link destination obtained (i.e., STR1, LFS3, STR1-FILE00001), which allows the CHN of the STR0 to reach STR1-FILE00001 in the RFS3 of the STR1 and access the data section of the abc.doc via the NCTL of the STR1.

0166Due to the fact that a plurality of file storage management tables 1100435 must be referred to in order to access a file that has been migrated to the LU3 of the STR1 according to the present embodiment, the access speed does suffer slightly. However, since files that are stored in the LU3 of the STR1 are files whose current life cycle stage is “archive stage” and therefore files that are rarely subjects of access requests, this poses no problem in practical terms. Even if an access request were to be issued from a host computer for data of a file in “archive stage,” the data can be retrieved in real-time from its storage positions on disks since it is stored on magnetic disks, even though it is a file that belongs to the Archive Storage class; unlike conventional situations in which such files are stored on tapes, neither enormous access time for tape control nor transferring the data from the tape to a disk is required according to the present embodiment.

0167As described above, according to the present embodiment, due to the fact that the storage positions of a file are determined based on the life cycle stage of the file, the Archive Storage class suitable for archiving is selected for files in “archive stage,” or the old age, in its life cycle.

0168Furthermore, other storage devices can be connected to the primary storage device, so that a storage hierarchy that takes advantage of differences in features of various storage devices can be constructed. Files can be migrated to LUs of the other storage devices, instead of migrating only within the primary storage device, according to the migration plan of each file; this further optimizes cost for storage devices compared to situations in which a hierarchical storage control is realized using only one storage device.

0169In addition, drives on disk devices that make up LUs whose storage class is “Archive Storage” can be halted to realize low power consumption and to extend the life of the disks.

0170Moreover, due to the fact that even cheaper storage devices can be connected to the storage device STR1 according to the present embodiment, a storage hierarchy that is even more extensive can be established among a plurality of storage devices; by executing a hierarchical storage control using such a configuration, cost can be further optimized.

Embodiment 3

0000(1) Example of System Configuration (<figref idref="DRAWINGS">FIG. 14</figref>)

0171Next, with reference to <figref idref="DRAWINGS">FIG. 14</figref>, an example of the system configuration according to the third embodiment will be described. In the present embodiment, as in the second embodiment, a hierarchical storage control is executed among storage devices in a system in which another storage device STR2 (1b) is connected to a storage device STR0 (1) via a network. The third embodiment differs from the second embodiment in that while the network that connects the storage devices was the LAN 20 and file I/O interfaces were used between storage devices in the second embodiment, the network that connects the storage devices is a SAN 35, which is a dedicated network for connection between the storage devices, and a block I/O interface is used between storage devices in the third embodiment.

0172In <figref idref="DRAWINGS">FIG. 14</figref>, the storage device STR2 (1b) is a storage device with a small-scale configuration similar to the storage device STR1 (1a) in the second embodiment, but instead of the NAS controller NCTL0 of the storage device STR1 (1a) in the second embodiment, the storage device STR2 (1b) has SAN controllers FCTLx. Each FCTLx is provided with an FC controller 11012b to connect with the SAN 35, but it does not have the file access control CPU 11001a or its peripheral circuits as the STR1 does and does not perform file control. Otherwise, the storage device STR2 (1b) according to the present embodiment has a configuration similar to that of the storage device STR1 (1a) according to the second embodiment.

0173The SAN 35 is a dedicated network for connecting the storage device STR0 (1) to the storage device STR2 (1b), and SAN hosts are not connected to the SAN 35. For the sake of simplification, let us assume that in the present embodiment no SAN hosts are connected to the SAN 35, which is the network to connect the storage devices, and that there is only one network that connects the storage devices. However, SAN hosts can be connected to the SAN 35 and a plurality of networks for connecting the storage devices can be provided to improve fault tolerance.

0174In the present embodiment, the storage device STR2 (1b) is under the control of the storage device STR0 (1), and file accesses from a NAS host 0 (400) reaches the storage device STR2 (1b) via the storage device STR0 (1). Such a configuration is hereinafter called a “connection of diverse storage devices.”

0000(2) Migration Processing of File to the Other Storage Device

0175Next, a description will be made as to the processing for migrating a file stored in the STR0 to the STR2, with emphasis on the difference between this processing and the processing according to the second embodiment.

0176A CHF1 (1111) of the storage device STR0 (1) recognizes that the storage device STR2 (1b), which is a divergent storage device, is connected to the SAN 35. The CHF1 (1111) acts as an initiator and issues a command to collect information and thereby recognizes that the STR2 (1b) is connected to the SAN 35. The CHF1 (1111) treats storage regions of the STR2 as if they were a disk pool within the primary storage device according to the first embodiment. A CHN0 (1110) can use the disk pool via the CHF1 (1111). The management method of the disk pool is described later. In order to ascertain the configuration of the STR2, the CHN0 (1100) of the STR0 (1) becomes an initiator and issues a command to collect information via the CHF1 (1111) to the STR2. The CHN0 (1100) of the STR0 (1) receives a response from the STR2 to the command via the CHF1 (1111) and recognizes from the information included in the response that the STR2 has a SATA disk pool and a low-cost, block type LU having a 15D+1P configuration RAID 5 and with a large capacity of 2100 GB; based on this, the CHN0 (1100) of the STR0 decides to manage the LU as a remote LU. Furthermore, due to the fact that the disk pool that the STR2 has is a large capacity, low-cost disk pool, the CHN0 (1100) of the STR0 determines the storage class of the disk pool as “Archive Storage.” The CHN0 (1100) of the STR0 assigns the number LU4 to the LU inside the STR2 and stores in a disk pool management table 131 of an SM 13 information concerning the LU, i.e., “Archive Storage” as the storage class #, “STR2” as the storage node #, “SATA poor” as the disk pool #, “LU4” as the LU #, “remote block” as the LU type, “RAID 5, 15D+1P” as the RAID Conf., and “2100 GB” as the usable capacity. When the CHN (1100) of the STR0 executes a file system program, the disk pool management table 131 is referred to and the information concerning the LU is copied from the disk pool management table 131 to a storage class management table 1100451 in a file access control memory.

0177As in the second embodiment, it is assumed that a migration management section 110043A of the CHN0 (1100) of the STR0 has decided to migrate a file abc.doc from a NearLine Storage class to the Archive Storage class, and the following is a description of the migration processing of the file executed based on this assumption.

0178The migration management section 110043A of the STR0 refers to a storage class management table 1100439, selects the LU4 that belongs to the “Archive Storage” class, and decides to transfer the file abc.doc to the LU4. The LU4 has attributes of “STR2 (i.e., the other storage device 1b)” as its storage node, “SATA disk poor” as its disk pool #, and “remote block” as its LU type.

0179Unlike the second embodiment, since the LU type of the LU4 is “block” type, there is no file system in the LU4. For this reason, the file system program stored in the CHN0 (1100) constructs a local file system LFS4 in the LU4. Due to the fact that the disk pool in which the LU4 is set resides in the other storage device STR2 from the perspective of the STR0, it is therefore a “remote” disk pool and the LU4 is a remote LU; however, since the file system LFS4 set in the LU4 is to be controlled by the CHN0 (1100), the file system LFS4 is managed as a local file system.

0180Due to the fact that the LFS4 is to be managed as a local file system and the LU4 in which the LFS4 is constructed is an LU that is in the block type, divergent storage device, a file storage management table is treated differently in the present embodiment compared to its treatment in the first and the second embodiments. In other words, a file storage management section 1100433 of the CHN0 (1100) of the STR0 assigns. “STR2” as the link destination node name, “LFS4” as the link destination FS name, and a STR2-FILE00001 as the link destination filename, and sets these in a file storage management table for the file abc.doc. Since the file abc.doc has already being migrated to the LU2 under the filename FILE00001, the CHN0 (1100) can alternatively set the assigned link destination node name, the link destination FS name and the link destination filename in the file storage management table for the file FILE00001 in the LFS2. Since the STR2, in which the LU4 actually exists, does not execute the file access control as described earlier, a file storage management table for the STR2-FILE00001 is not created in the STR2.

0181The processing that takes place when the file system program 110043 of the CHN0 (1100) is executed is the same as the processing that takes place on the local file system according to the first embodiment in terms of the file open processing, write processing and migration processing, except for the fact that the processing is executed with the awareness that the link destination node of the file abc.doc (i.e., the storage device in which the actual data of the file abc.doc is stored) is the STR2.

0182However, unlike the first embodiment in which a file is transferred to an LU that is in the primary storage device STR0, data of a file is transferred to an LU that is in the other storage device STR2 according to the present embodiment, which results in input/output processing to and from disks that is different from the first embodiment. While the DKA 12x of the STR0 controlled the input/output processing to and from disks in the first embodiment, the CHF1 (1111) of the STR0 controls the processing according to the configuration of the present embodiment. For this reason, a CHF communications driver program 110096 is stored in a disk array control memory 11009 of the CHN0. A CHF communications driver section is realized by having a disk array control CPU 11008 execute the CHF, communications driver program 110096. The CHF communications driver section sends a disk input/output command (hereinafter called an “I/O command”) to the SM 13. Address information representing storage positions of the data is included in the I/O command. The CHF1 (1111) receives the I/O command via the SM 13 and based on the I/O command received issues an I/O command to the storage device 1b (STR2) via the SAN 35. The I/O command issued by the CHF1 (1111) includes address information representing the data storage positions within the storage device 1b (STR2). The storage device 1b (STR2) processes the I/O command received from the CHF1 (1111) according to the same procedure applied when a disk I/O command is received from a normal host. In other words, the CHF1 of the STR0 is recognized as a host from the perspective of the STR2.

0183According to the present embodiment, the disk pool of the divergent storage device STR2 provided with the block I/O interface can be treated as one of the disk pools of the storage device STR0, and a file system managed by the STR0 can be constructed on the LU that is in the disk pool of the STR2. Furthermore, due to the fact that files stored in the LU of the STR0 can be migrated to the LU within the STR2, a flexible storage hierarchy with superior cost effectiveness can be constructed.

Embodiment 4

0000(1) Example of System Configuration (<figref idref="DRAWINGS">FIG. 15</figref>),

0184The following is a description of the fourth embodiment. The present embodiment differs from preceding embodiments in its configuration.

0185<figref idref="DRAWINGS">FIG. 15</figref> is a diagram of an example of the system configuration according to the present embodiment. A storage device STR3 (1c) is provided with a DKC 70 and disk pools. In the DKC 70, an SW 71 is a switch, NNODEs (72x) are NAS nodes each provided with a file I/O control mechanism to connect with a LAN, FNODEs (73x) are FC nodes each provided with a block I/O control mechanism to connect with a SAN, INODEs (74x) are IP nodes each provided with an IP network control mechanism to connect with an IP network, and DNODEs (75x) are disk controller nodes each provided with a disk control mechanism to connect with a disk pool. To the switch SW 71 are connected one or more NNODEs 72x, one or more FNODEs 73x, one or more INODEs 74x and one or more DNODEs 75x. A node to control iSCSI can be connected to the switch SW 71 to form an IP SAN. The node to control the iSCSI would have functions and a configuration similar to those of the FNODE.

0186The DNODE0 and the DNODE1 are connected to and control two types of disk pools, a disk pool 0 and a disk pool 1, which are an FC disk pool 170 and a SATA disk pool 171.

0187The INODE2 and the INODE3 are connected to a NAS-type divergent storage device STR1 (1a), which is external to the storage device STR3 and is a storage device provided with file I/O interfaces described in the second embodiment. The FNODE2 and the FNODE3 are connected to a SAN-type divergent storage device STR2 (1b), which is external to the storage device STR3 and is a storage device provided with block I/O interfaces described in the third embodiment.

0000(2) Example of Configuration of the NNODE (<figref idref="DRAWINGS">FIG. 16</figref>)

0188<figref idref="DRAWINGS">FIG. 16</figref> is a diagram of an example of the configuration of the NNODE. The NNODE 720 is equivalent to the CHN 1100 shown in <figref idref="DRAWINGS">FIG. 4</figref> with the inter-CPU communications circuit 11007 and components below it removed and replaced by an SW node controller 7204. Other components are the same as in the CHN 1100 in terms of configuration and function.

0189The SW node controller 7204 is a controller circuit for connecting with the SW 71; it forms commands, data and controller information in internal frame formats that are sent and received within the storage device STR3 (1c) and sent as disk I/O to other nodes such as the DNODEs.

0000(3) Example of Configuration of the FNODE (<figref idref="DRAWINGS">FIG. 17</figref>)

0190<figref idref="DRAWINGS">FIG. 17</figref> is a diagram of an example of the configuration of the FNODE. The FNODE 730 has a configuration in which an SW node controller 7302 is connected to the FC controller 11012b of the FCTL 1100b in <figref idref="DRAWINGS">FIG. 14</figref>, which makes the FNODE 730 capable of connecting with the SW 71 via the SW node controller 7302. An FC controller 7301 operates as a target device and sends and receives frames of commands, data and controller information to and from the SAN. The SW node controller 7302 converts frames sent or received by the FC controller 7301 into internal frame configurations of the storage device STR3 (1c) and sends or receives the converted frames to and from other nodes, such as the DNODEs.

0191The FNODE 73x operates as an initiator device and based on disk I/O commands received from the NNODEs or other FNODEs can send I/O commands to other storage devices connected externally to the storage device STR3. For example, based on commands received from the NNODEs or other FNODEs of the storage device STR3, the FNODE2 and the FNODE3 in <figref idref="DRAWINGS">FIG. 15</figref> can send I/O commands to the divergent storage device STR2 (1b) externally connected to the storage device STR3. In this case, the FNODE2 and the FNODE3 appear to be operating as host computers from the perspective of the STR2.

0192Although only the FC controller 7301 and the SW node controller 7302 are shown in <figref idref="DRAWINGS">FIG. 17</figref> for the sake of simplification, a CPU can be mounted on the FNODEs in order to perform target processing, initiator processing or internal frame generation processing.

0193By installing an iSCSI controller instead of the FC controller 7301, a node that controls iSCSI can be configured; by connecting such a node to the SW 71, an IP SAN can be configured.

0000(4) Example of Configuration of INODE (<figref idref="DRAWINGS">FIG. 18</figref>)

0194<figref idref="DRAWINGS">FIG. 18</figref> is a diagram of an example of the configuration of the INODE. The INODE 740 has a configuration in which an SW node controller 7402 is connected to a LAN controller 7401, which is similar to the LAN controller 11002a of the NCTL0 (1100a) in <figref idref="DRAWINGS">FIG. 13</figref>; this configuration makes the INODE 740 capable of connecting with the SW 71 via the SW node controller 7402. The INODEs are provided on the storage device STR3 (1c) in order to connect the external NAS-type storage device STR1a to the STR3.

0000(5) Example of Configuration of DNODE (<figref idref="DRAWINGS">FIG. 19</figref>)

0195<figref idref="DRAWINGS">FIG. 19</figref> is a diagram of an example of the configuration of the DNODE. The DNODE 750 is similar to the FCTL 1100b in <figref idref="DRAWINGS">FIG. 14</figref>, but with the FC controller 11012b removed and replaced with an SW node controller 7501. The DNODE 750 goes into operation when it receives a disk I/O command from one of the NNODEs or FNODEs via the SW 71; as a result, a section 1d outlined by a broken line in <figref idref="DRAWINGS">FIG. 15</figref> operates as if it were the independent storage device STR2 in <figref idref="DRAWINGS">FIG. 14</figref>. In the present embodiment, the DNODE0 (750) and the DNODE1 (751) form a pair of redundant controllers. Having redundant DNODEs is similar to the configuration of the storage device STR2 in <figref idref="DRAWINGS">FIG. 14</figref>, where there are also redundant FCTLs.

0000(6) Migration Processing of Files

0196The present embodiment only differs from the first, second and third embodiments in its configuration of the storage device, and its processing procedure for executing a hierarchical storage control is similar to that in the first, second and third embodiments; accordingly, only those parts that differ in the operation as a result of differences in the configuration of the storage device are described below.

0197In the present embodiment, a hierarchical storage control inside the storage device STR3 can be executed using a procedure similar to that in the first embodiment. A file system program 110043 stored in a file access control memory of the NNODE 72x is equipped with a storage class management table 1100439 for managing usable LUs, and can recognize disk pools and LUs managed by the DNODEs 75x by referring to the storage class management table 1100439. However, unlike the first embodiment, there is no SM 13 for storing shared information; consequently, the NNODE 72x must query all DNODEs 75x in advance to specify a usable LU and register it in the storage class management table 1100439. Of course, an SM node for connecting with an SM can be provided for connection with the SW 71 in the present embodiment, so that the storage class management table 1100439 can consist of information stored in the SM, as in the first embodiment.

0198When the NNODE 72x specifies a usable disk pool and an LU, creates the storage class management table 1100439, and defines a storage class, a processing similar to that in the first embodiment can be applied subsequently to execute a hierarchical storage control within the storage device STR3 (1c), i.e., a hierarchical storage control using LUs set in the disk pool 0 and the disk pool 1.

0199To issue a disk I/O command, an SW node driver program stored in the file access control memory 7203 of the NNODE is executed by the file access control CPU 7202, which causes a disk I/O command to be issued via the SW node to the DNODE 750 that manages the LU that is the subject of access.

0200Through the configuration and processing described above, a system in which a file-based storage hierarchy is constructed within the storage device STR3, as in the first embodiment, can be realized.

0201Furthermore, the NAS-type divergent storage device STR1 (1a) provided with file I/O interfaces can be connected externally to the storage device STR3, which would result in a configuration of a storage hierarchy as in the second embodiment. When the file system program 110043 stored in the file access control memory 7203 of the NNODE 72x is executed by the file access control CPU 7202, the file system program 110043 queries the INODE 74x whether there is a NAS-type divergent storage device connected to the INODE 74x; if there is a divergent storage device connected, the file system program 110043 obtains from the divergent storage device the information for identifying remote LUs and remote file systems that are in the divergent storage device. Through a control by the file access control CPU 7202, a storage class is defined for each of the remote LUs and the remote file systems, and information concerning the LUs is registered and managed in the storage class management table 1100439. Subsequent steps are the same as in the processing procedure in the second embodiment.

0202To issue a disk I/O command, the SW node driver program stored in the file access control memory 7203 of the NNODE is executed by the file access control CPU 7202, which causes a disk I/O command to be issued from the NNODE via the SW node to the INODE 740 connected to the storage device STR1 (1a) that is provided with the LU that is the subject of access. Based on the I/O command received, the INODE 740 issues to the storage device STR1 (1a) a disk I/O command for a file access, as well as sends and receives actual data of the file and control information to and from the STR1 (1a).

0203The INODEs 74x have no involvement whatsoever in the file control information and operate simply as gateways of an IP network. In such a case, a hierarchical storage configuration without any interference from other devices, such as NAS hosts, can be realized. Of course, the divergent storage device STR1 (1a) can be connected to the LAN 20, to which the NNODE 720 is connected, as in the second embodiment.

0204Through the configuration and processing described above, a file-based storage hierarchy that utilizes storage pools of an external divergent storage device, as in the second embodiment, can be realized.

0205Furthermore, the SAN-type divergent storage device STR2 (1b), which is a storage device provided with block I/O interfaces, could be connected externally to the storage device STR3, which would result in a configuration of a storage hierarchy as in the third embodiment. When the file system program 110043 stored in the file access control memory 7203 of the NNODE 72x is executed by the file access control CPU 7202, the NNODE queries the FNODEs 73x whether there is a SAN-type divergent storage device connected to the FNODEs 73x. If there is a divergent storage device connected, the NNODE recognizes remote LUs of the divergent storage device based on the contents of the response from the FNODEs 73x to the query and constructs local file systems in the remote LUs. The NNODE then defines a storage class for each of the remote LUs and the local file systems, and registers and manages information concerning the LUs in the storage class management table 1100439. Subsequent steps are the same as in the third embodiment.

0206To issue a disk I/O command, the SW node driver program is executed by the file access control CPU 7202, which causes a disk I/O command to be issued from the NNODE via the SW node to the FNODE 732 connected to the storage device STR2 (1b), which is provided with the LU that is the subject of access. The FNODE 732 issues to the storage device STR2 a disk I/O command, as well as sends and receives data and control information to and from the STR2. Through the configuration and processing procedure described above, a file-based storage hierarchy that utilizes a file system that is constructed in an external storage device STR2 as in the third embodiment and managed by the STR3 can be realized.

0207According to the present embodiment, the storage device STR3 behaves as if it were a central control controller for constructing a hierarchy storage system and various types of storage devices can be connected internally and externally to the storage device STR3; consequently, an extremely flexible, scalable and large-scale hierarchical storage system can be constructed. Furthermore, due to the fact that disks and other storage devices can be connected internally and externally to the storage device STR3 as nodes on the SW 71 of the storage device STR3, high-speed data transfer becomes possible.

0000(7) Other Applications

0208Although file transfer methods and storage devices that execute hierarchical migration processing of files based on file's data life cycle stages have been described in the first through fourth embodiments, files can be transferred based on other standards and a plurality of standards can be combined. Possible standards other than the data life cycle stage include a file's access property and an LU's used capacity. In such cases, transfer of files can be controlled by providing a migration plan based on the file's access property or the LU's used capacity.

0209Examples of migration plans based on a file's access property include a plan to re-transfer a file into a storage class one class higher in the hierarchy when the access frequency of the file exceeds a certain level, or a plan that provides a storage class specialized for sequential accesses and that transfers a file into the specialized storage class once the sequential access frequency to the file exceeds a certain level.

0210Examples of migration plans based on an LU's used capacity include a plan to transfer a file to a storage class one class lower in the hierarchy even if its current life cycle stage has not shifted, if the file that is stored in an LU has low access frequency or if a long time has elapsed since its date of creation, once the used capacity of the LU exceeds a certain level.

0211The file property information management table 1100438 in the above embodiments manages dynamic properties for each file as access information. The storage class management table 1100439 manages the total capacity and used capacity of each LU. By utilizing such information, migration plans described above can be readily realized.

0212A hierarchical storage control according to the property of a file can be realized through a processing within a storage device and without being dependent on host computers.

0213While the description above refers to particular embodiments of the present invention, it will be understood that many modifications may be made without departing from the spirit thereof. The accompanying claims are intended to cover such modifications as would fall within the true scope and spirit of the present invention.

0214The presently disclosed embodiments are therefore to be considered in all respects as illustrative and not restrictive, the scope of the invention being indicated by the appended claims, rather than the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein.

Contents4

Every citation, both ways

Citations
Document	Relation	Office	Cited during
US2006242312A1	Cited by	United States of America	Pre-grant
US8423727B2	Cited by	United States of America	Applicant
US9454532B2	Cited by	United States of America	Applicant
US2013132681A1	Cited by	United States of America	Pre-grant
US8683174B2	Cited by	United States of America	Applicant
US2010299547A1	Cited by	United States of America	Pre-grant
JP2011150681A	Cited by	Japan	Search report
US8438138B2	Cited by	United States of America	Applicant
US9734082B2	Cited by	United States of America	Applicant
US2012150799A1	Cited by	United States of America	Pre-grant
US2014379768A1	Cited by	United States of America	Pre-grant
US8281105B2	Cited by	United States of America	Applicant
US9460106B2	Cited by	United States of America	Search report
US2007083482A1	Cited by	United States of America	Pre-grant
US7853741B2	Cited by	United States of America	Search report
US9460112B2	Cited by	United States of America	Applicant
US9460097B2	Cited by	United States of America	Applicant
US9104606B2	Cited by	United States of America	Search report
US9191464B2	Cited by	United States of America	Applicant
US8645737B2	Cited by	United States of America	Search report
US8812677B2	Cited by	United States of America	Applicant
US8566550B2	Cited by	United States of America	Applicant
US2011072225A1	Cited by	United States of America	Pre-grant
US8856073B2	Cited by	United States of America	Search report
US2011231631A1	Cited by	United States of America	Pre-grant
US2009228535A1	Cited by	United States of America	Pre-grant
US2011179250A1	Cited by	United States of America	Pre-grant
US8131783B2	Cited by	United States of America	Applicant
US9460111B2	Cited by	United States of America	Applicant
EP2348425A1	Cited by	European Patent Office (EPO)	Applicant
WO02069159A1	Cites	World Intellectual Property Organization (WIPO)	Applicant
US2001054133A1	Cites	United States of America	Applicant
US2002062387A1	Cites	United States of America	Applicant
US2002161855A1	Cites	United States of America	Applicant
JP2002229740A	Cites	Japan	Applicant
US2003046270A1	Cites	United States of America	Applicant
US2003061440A1	Cites	United States of America	Applicant
US2003065898A1	Cites	United States of America	Search report
US2003074523A1	Cites	United States of America	Applicant
US2003154220A1	Cites	United States of America	Search report
US2003182288A1	Cites	United States of America	Applicant
US2003182525A1	Cites	United States of America	Applicant
US2003225801A1	Cites	United States of America	Applicant
US2004010660A1	Cites	United States of America	Search report
US2004044854A1	Cites	United States of America	Applicant
US2004083202A1	Cites	United States of America	Applicant
US2004098394A1	Cites	United States of America	Applicant
US2004107315A1	Cites	United States of America	Applicant
US2004139167A1	Cites	United States of America	Applicant
US2004143563A1	Cites	United States of America	Applicant
US2004143648A1	Cites	United States of America	Applicant
US2004162940A1	Cites	United States of America	Applicant
US2004199515A1	Cites	United States of America	Applicant
US2004210724A1	Cites	United States of America	Applicant
US2004260862A1	Cites	United States of America	Applicant
US2005097126A1	Cites	United States of America	Applicant
US2005120189A1	Cites	United States of America	Applicant
US2005149528A1	Cites	United States of America	Applicant
US2005149671A1	Cites	United States of America	Applicant
US2005172097A1	Cites	United States of America	Applicant
US5379423A	Cites	United States of America	Applicant
US5537585A	Cites	United States of America	Applicant
US5619690A	Cites	United States of America	Applicant
US5941972A	Cites	United States of America	Applicant
US5956750A	Cites	United States of America	Applicant
US6041381A	Cites	United States of America	Applicant
US6065087A	Cites	United States of America	Applicant
US6098129A	Cites	United States of America	Applicant
US6209023B1	Cites	United States of America	Applicant
US6275898B1	Cites	United States of America	Applicant
US6327614B1	Cites	United States of America	Applicant
US6446141B1	Cites	United States of America	Applicant
US6598174B1	Cites	United States of America	Applicant
US6647474B2	Cites	United States of America	Applicant
US6654830B1	Cites	United States of America	Applicant
US6757695B1	Cites	United States of America	Applicant
US6810462B2	Cites	United States of America	Applicant
US6922761B2	Cites	United States of America	Applicant
US6938039B1	Cites	United States of America	Applicant
US6947940B2	Cites	United States of America	Applicant
US6983039B2	Cites	United States of America	Applicant
JPH09259037A	Cites	Japan	Applicant
JPH09274544A	Cites	Japan	Applicant
JPH09297699A	Cites	Japan	Applicant
JPH10301720A	Cites	Japan	Applicant
US20010054133A1	Cites	United States of America	Third party observation
US20020062387A1	Cites	United States of America	Third party observation
US20020161855A1	Cites	United States of America	Third party observation
US20030046270A1	Cites	United States of America	Third party observation
US20030061440A1	Cites	United States of America	Third party observation
US20030065898A1	Cites	United States of America	Search report
US20030074523A1	Cites	United States of America	Third party observation
US20030154220A1	Cites	United States of America	Search report
US20030182288A1	Cites	United States of America	Third party observation
US20030182525A1	Cites	United States of America	Third party observation
US20030225801A1	Cites	United States of America	Third party observation
US20040010660A1	Cites	United States of America	Search report
US20040044854A1	Cites	United States of America	Third party observation
US20040083202A1	Cites	United States of America	Third party observation
US20040098394A1	Cites	United States of America	Third party observation

Showing 100 of 145

17 members in 4 offices

This recordMember, by publication datePriority claim

Priority claims11

Priority claims
Document	Office	Kind	Date
2003086828	Japan	–	2003-03-27
2003086828	Japan	A	2003-03-27
2003086828	Japan	A	2003-03-27
77588604	United States of America	A	2004-02-10
77588604	United States of America	A	2004-02-10
3060805	United States of America	A	2005-01-06
10775886	–	–	–
2003086828	–	–	–
JP20030086828	–	–	–
US20040775886	–	–	–
US20050030608	–	–	–

Members17

Family members, oldest first
Document	Office	Kind
EP1462927A2	European Patent Office (EPO)	A2	2004-09-29
US2004193760A1	United States of America	A1	2004-09-30
JP2004295457A	Japan	A	2004-10-21
CN1570842A	China	A	2005-01-26
US2005119994A1	United States of America	A1	2005-06-02
US2005203964A1	United States of America	A1	2005-09-15
CN1311328C	China	C	2007-04-18
CN101034340A	China	A	2007-09-12
US7330950B2This record	United States of America	B2	2008-02-12
US7356660B2	United States of America	B2	2008-04-08
EP1462927A3	European Patent Office (EPO)	A3	2008-09-24
US2008263277A1	United States of America	A1	2008-10-23
CN100520696C	China	C	2009-07-29
JP4322031B2	Japan	B2	2009-08-26
US7925851B2	United States of America	B2	2011-04-12
US2011185123A1	United States of America	A1	2011-07-28
US8230194B2	United States of America	B2	2012-07-24

68 transactions on the USPTO file

Allowed after 1 non-final rejection.

Non-final rejections: 1
Final rejections: 0
RCEs: 0
Appeals: 0

Over time

Point at a mark for the transaction

Transactions

Prosecution transactions, newest first
	Event	Code
2010-04-13	Correspondence Address ChangeC.AD	C.AD
2009-03-12	Correspondence Address ChangeC.ADB	C.ADB
2009-03-12	Correspondence Address ChangeC.ADB	C.ADB
2008-02-12	Recordation of Patent Grant MailedPGM/	PGM/
2008-02-12	Patent Issue Date Used in PTA CalculationAllowedPTAC	PTAC
2008-01-23	Issue Notification MailedAllowedWPIR	WPIR
2008-01-11	Dispatch to FDCD1935	D1935
2008-01-09	Application Is Considered Ready for IssuePILS	PILS
2007-12-18	Issue Fee Payment VerifiedN084	N084
2007-12-18	Issue Fee Payment ReceivedIFEE	IFEE
2007-09-20	Mail Notice of AllowanceAllowedMN/=.	MN/=.
2007-09-20	Mail Examiner's AmendmentMEX.A	MEX.A
2007-09-17	Notice of Allowance Data Verification CompletedAllowedN/=.	N/=.
2007-09-17	Examiner's Amendment CommunicationEX.A	EX.A
2007-08-15	Date Forwarded to ExaminerFWDX	FWDX
2007-08-07	Response after Non-Final ActionA...	A...
2007-05-07	Mail Non-Final RejectionNon-final rejectionMCTNF	MCTNF
2007-04-30	Non-Final RejectionNon-final rejectionCTNF	CTNF
2007-04-12	Information Disclosure Statement consideredIDSC	IDSC
2007-04-12	Reference capture on IDSRCAP	RCAP
2007-04-12	Information Disclosure Statement (IDS) FiledM844	M844
2007-04-12	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2007-04-09	Case Docketed to Examiner in GAUDOCK	DOCK
2007-03-29	Case Docketed to Examiner in GAUDOCK	DOCK
2007-01-10	Preliminary AmendmentA.PE	A.PE
2006-06-01	Preliminary AmendmentA.PE	A.PE
2006-03-28	Information Disclosure Statement consideredIDSC	IDSC
2006-03-28	Reference capture on IDSRCAP	RCAP
2006-03-28	Information Disclosure Statement (IDS) FiledM844	M844
2006-03-28	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2006-03-15	Change in Power of Attorney (May Include Associate POA)PA..	PA..
2006-03-14	Correspondence Address ChangeC.AD	C.AD
2006-03-06	Preliminary AmendmentA.PE	A.PE
2006-02-28	Case Docketed to Examiner in GAUDOCK	DOCK
2006-01-26	Information Disclosure Statement consideredIDSC	IDSC
2006-01-26	Reference capture on IDSRCAP	RCAP
2006-01-26	Information Disclosure Statement (IDS) FiledM844	M844
2006-01-26	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2006-01-18	Information Disclosure Statement consideredIDSC	IDSC
2006-01-18	Reference capture on IDSRCAP	RCAP
2006-01-18	Information Disclosure Statement (IDS) FiledM844	M844
2006-01-18	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2005-12-28	Information Disclosure Statement consideredIDSC	IDSC
2005-12-28	Reference capture on IDSRCAP	RCAP
2005-12-28	Information Disclosure Statement (IDS) FiledM844	M844
2005-12-28	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2005-10-21	IFW TSS Processing by Tech Center CompleteTSSCOMP	TSSCOMP
2005-10-21	Case Docketed to Examiner in GAUDOCK	DOCK
2005-10-07	Information Disclosure Statement consideredIDSC	IDSC
2005-10-07	Reference capture on IDSRCAP	RCAP
2005-10-07	Information Disclosure Statement (IDS) FiledM844	M844
2005-10-07	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2005-07-29	Information Disclosure Statement consideredIDSC	IDSC
2005-07-29	Information Disclosure Statement (IDS) FiledM844	M844
2005-07-29	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2005-07-29	Reference capture on IDSRCAP	RCAP
2005-02-24	Application Is Now CompleteCOMP	COMP
2005-02-23	Application Return from OIPEWROIPE	WROIPE
2005-02-23	Application Return TO OIPEROIPE	ROIPE
2005-02-23	Application Dispatched from OIPEOIPE	OIPE
2005-02-02	Cleared by OIPE CSRL194	L194
2005-01-30	IFW Scan & PACR Auto Security ReviewSCAN	SCAN
2005-01-06	Information Disclosure Statement consideredIDSC	IDSC
2005-01-06	Preliminary AmendmentA.PE	A.PE
2005-01-06	Reference capture on IDSRCAP	RCAP
2005-01-06	Information Disclosure Statement (IDS) FiledM844	M844
2005-01-06	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2005-01-06	Initial Exam Team nnIEXX	IEXX

10 legal events, as the office reported them to INPADOC

Over the term

Point at a mark for the event

Events

Legal events, newest first
	Event	Code
2020-04-07	Lapsed due to failure to pay maintenance feeLapsedFP	FP
2020-03-16	Lapse for failure to pay maintenance feesLapsedPATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYLAPS	LAPS
2020-03-16	Information on status: patent discontinuationPATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362STCH	STCH
2019-09-30	Fee payment procedureMAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP	FEPP
2015-07-29	Fee paymentFPAY	FPAY
2011-07-13	Fee paymentFPAY	FPAY
2009-11-01	Fee payment procedurePAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP	FEPP
2009-10-31	Fee payment procedurePAYER NUMBER DE-ASSIGNED (ORIGINAL EVENT CODE: RMPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP	FEPP
2008-12-01	Fee payment procedurePAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP	FEPP
2008-01-23	Information on status: patent grantGrantedPATENTED CASESTCF	STCF