US20120260055A1

Movatterモバイル変換

Info

Publication number: US20120260055A1
Application number: US13/525,870
Authority: US
Inventors: Atsushi Murase
Original assignee: Hitachi Ltd
Current assignee: Hitachi Ltd
Priority date: 2008-09-29
Filing date: 2012-06-18
Publication date: 2012-10-11
Also published as: US8224782B2; US20100082765A1

Abstract

System and method for reducing costs of moving data between two or more of multi-tiered storage devices. Specifically, the system operates by moving only high tier portion of data and merely remapping the low tier data to migration target device, which eliminates a large amount of data movement (low tier) while maintaining the SLA of high tier data. Specifically, when a command to migrate a thin provisioned volume is received from a source primary storage device to another target primary storage device, the system doesn't copy all of the tier1 and tier2 chunk data that the source thin provisioned volume holds, but copies only tier1 chunk data to the target storage device. The copy operation is performed after the storage system prepared the target thin provisioned volume on the target side. After that, tier2 chunks are remapped from the primary storage device to another target primary storage device without copying.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 12/240,839, filed on Sep. 29, 2008, the entire contents of which are incorporated herein by reference.

FIELD OF THE INVENTION

This invention generally relates to storage systems and more specifically to optimizing operation of tiered storage systems with data migration capability.

DESCRIPTION OF THE RELATED ART

The amount of business information of various types has been growing at a very high rate year over year and will likely continue to do so. Every single piece of this business data has to be kept and protected properly. However, the importance, frequency of access, and required reliability level of the various types of data vary significantly, hence not all types of data need to be stored in high performance and high cost storage devices. In order to reduce the storage costs, each unit of data should be stored in a storage device having appropriate performance characteristics commensurate with the use and importance of the stored data, as determined by various data attributes.

In addition to the dramatic increase in the volume of the stored data, more and more data needs to be moved or copied between storage devise due to various reasons, such as device replacement and business continuity requirements (clustered system, disaster recovery, backup and recovery). In addition, the data needs to be moved as required by the internal operation of the dynamic virtual server platforms.

Tiered Storage systems provide solutions for reducing the cost of storing Service Level Agreement (SLA) data. In this solution, SAN incorporates storage devices of multiple storage tiers. These multiple tiers may include a high reliability, high performance but high cost storage tier, a storage tier with lower access speed and lower storage costs, or a very low storage cost tier for data archiving. Other tiers are also possible. Data will be stored in the storage of appropriate tier according to the data attributes. The data may be also dynamically migrated between tiers based on the current data usage conditions. Thus, as would be appreciated by those of skill in the art, using multiple tiers of storage resources achieves the reduction of the overall storage system cost by optimizing the allocation of the storage for a specific data in accordance with required access speed or reliability for that data.

A thin provisioning technology helps improving the storage space utilization. The thin provisioning technology presents full volume capacity virtually to a host but allocates actual physical storage only when a write command has been received for a specific region of the data volume. Partial capacity, a chunk, is carved from the storage extent called thin provisioning pool, when the storage capacity allocation request is received. In this type of storage system such that allocating storage extent with the small amount of capacity (Chunk) may have ability to manage tier by the granularity of the Chunk instead of the size of whole volume in order to achieve more efficiency of utilization of appropriate characteristics of storage devices. It provisions new capacity from proper tier or controls dynamic data migration between tiers by the Chunk granularity. Furthermore, having plural tier of Chunks may be hidden from host. Host only sees a single Thin Provisioned Volume and doesn't know whether it contains several characteristic of chunks. The system automatically can provision or dynamically migrate chunks within the volume without showing the action to the host.

The technologies enumerated above reduce the cost of storage when the data is statically stored without frequent data transfers. However, because the data relocation or duplication operations have become common in many situations, the costs associated with moving the data started to present a new serious problem that needs to be solved. Unfortunately, the current solutions fail to address this problem. Therefore, what is needed is a solution for minimizing data movement cost, while preserving the benefits of tiered storage systems.

SUMMARY OF THE INVENTION

The inventive methodology is directed to methods and systems that substantially obviate one or more of the above and other problems associated with conventional techniques for deploying multiple server instances.

Additional aspects related to the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. Aspects of the invention may be realized and attained by means of the elements and combinations of various elements and aspects particularly pointed out in the following detailed description and the appended claims.

It is to be understood that both the foregoing and the following descriptions are exemplary and explanatory only and are not intended to limit the claimed invention or application thereof in any manner whatsoever.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute a part of this specification exemplify the embodiments of the present invention and, together with the description, serve to explain and illustrate principles of the inventive technique. Specifically:

FIG. 1 illustrates an exemplary hardware architecture of the first embodiment of the invention.

FIGS. 2 and 3 show software and logical element structure corresponding to the embodiment shown inFIG. 1.

FIGS. 4,5 and6 illustrate data structure of various tables stored in the Memory of the Controller.

FIGS. 7,8 and9 illustrate an exemplary process for Thin Provisioned Volume migration between the tiered storage systems executed by Tiered Storage Management Module.

FIG. 10 shows an example process for Chunk demotion (Tier1 to Tier2 Chunk) executed by Tiered Storage Management Module.

FIG. 11 illustrates an exemplary embodiment of a computer platform upon which the inventive system may be implemented.

DETAILED DESCRIPTION

In the following detailed description, reference will be made to the accompanying drawing(s), in which identical functional elements are designated with like numerals. The aforementioned accompanying drawings show by way of illustration, and not by way of limitation, specific embodiments and implementations consistent with principles of the present invention. These implementations are described in sufficient detail to enable those skilled in the art to practice the invention and it is to be understood that other implementations may be utilized and that structural changes and/or substitutions of various elements may be made without departing from the scope and spirit of present invention. The following detailed description is, therefore, not to be construed in a limited sense. Additionally, the various embodiments of the invention as described may be implemented in the form of a software running on a general purpose computer, in the form of a specialized hardware, or combination of software and hardware.

Aspects of the present invention provide systems and methods for chunk based tiered storage volume migration. A chunk based tiered storage system disclosed in this invention provides thin provisioned volume (TPV) to the host. The system allocates new chunks upon the receipt of a write operation command. The filesystem on the host is not aware of the tiered structure within the storage system.

Meanwhile, the storage system automatically performs dynamic data tier management based on the granularity of the chunks. The management may be accomplished, for instance, based on the access frequency to the specific chunks. Chunks are carved from the thin provisioning pool to the thin provisioned volume and the pool is composed of high performance tier1 constituent volumes and lower performance tier2 constituent volumes. Therefore, both expensive tier1 chunks and reasonably priced tier2 chunks can be used for the thin provisioned volume in accordance with predetermined condition(s). The above system, as mentioned before, dynamically manages data movement from tier1 to tier2 (or vice versa) chunks automatically based, for instance, on their respective access frequency.

In this invention, it is assumed that the storage system incorporates the tier with high performance primary storage device as tier1 and an externally attached, using storage virtualization technology, lower priced and lower performance secondary storage device as tier2. Therefore, the tier1 constituent volume is located on the primary storage device and the tier2 constituent volume, which typically has much higher storage capacity than the tier1 constituent volume, is located on an externally attached secondary storage device.

When an embodiment of the inventive system receives a command to migrate a thin provisioned volume from a source primary storage device to another target primary storage device, the inventive system doesn't copy all of the tier1 and tier2 chunk data that the source thin provisioned volume holds, but copies only tier1 chunk data to the target storage device. The copy operation is performed after the storage system prepared the target thin provisioned volume on the target side.

After that, the inventive system refers to the pool, which supplied chunks to the migration source thin provisioned volume and finds tier2 constituent volumes that are included in the pool. The found tier2 constituent volumes are located on the externally attached secondary storage device which actually holds the tier2 chunks, which are associated with the thin provisioned volume. The inventive system then refers to the pool on the migration target primary storage device and mounts tier2 constituent volume to that pool.

Finally, the inventive system copies the chunk mapping table, which stores information on the relationships between each of the chunks and the constituent volumes that actually provide the storage extent for those chunks, from the source storage device to the target storage device so that the new thin provisioned volume can be associated to the tier2 chunks on the secondary storage device and the whole tier1 and tier2 chunks are accessible from the host.

By copying only tier1 chunks during the migration operation, the inventive system dramatically reduces the data relocation costs because typically the tier2 data is much larger in size than the tier1 data. At the same time, the tier1 data will be actually copied to the specific migration target primary storage device so that it can deliver high access speed performance after the migration. While the tier2 data is characterized by slower access speed, a high access speed is typically not required from the tier2 data. Performing actual copy only for the data that needs to be accessed at a fast access speed after the migration and merely switching the externally attached path for the less frequently accessed data improves the overall efficiency of the data movement.

Now, exemplary embodiments of the invention will be described in detail.

FIG. 1 illustrates an exemplary hardware architecture of the first embodiment of the invention. The shown system incorporates

Storage Systems

100,110,120 and Client Hosts130. Client Hosts and

Storage Systems

100,110 are connected through aNetwork140. TheNetwork140 can be implemented using a wide variety of technologies and is called a frontend network. Also all Storage Systems are connected through adifferent Network150, which is a backend network.

Now, the

Storage Systems

100,110 and120 will be described.Storage System100 is a primary storage device, which holds the tier1 data and is the source device during the data migration operation. It incorporates aController101 and aStorage Media105. The Storage Media in the primary storage device will be a high quality media such as FC disk drive. TheController101 includes aCPU102, aMemory103, and aNetwork Interface104. Storage Media are connected to theController101 and it could be variety type of device such as hard disk, flash memory, optical disk, tape, and so on. TheStorage System110 also represent as another primary storage device which will holds the tier1 data and will be the target side of device during the data migration. Its components are same asStorage System100. Those two

devices

100 and110 are connected to the Client Hosts.Storage System120 represent as a secondary storage device which holds the tier2 data. Components are similar to the other tier1 primary devices but it composed with morereasonable Storage Mediums125 such as SATA disks. Tier2 secondary device is connected to the tier1 devices through thebackend Network150.

The Client Host (130) will now be described. The Client Host is a generic computer that comprises a CPU131,Memory132, and aNetwork Interface133. It is a terminal computer for the storage service user.

FIGS. 2 and 3 show software and logical element structure corresponding to the embodiment shown inFIG. 1.FIG. 2 shows the initial condition of an embodiment of the inventive system, before the migration operation starts, and theFIG. 3 illustrates the condition of the inventive system during or after the data migration.

InFIG. 2, the Storage Volume Composition of tier2Storage System120 is shown. Specifically, the Array Group210-2 is the logical capacity which is composed of a plurality of Storage Mediums125 (so-called RAID group). For example, it could be composed as a RAID 5 array with 3 disks of data and 1 parity disk. The Constituent Volume220-2 (for tier2 data) is another logical capacity which is carved from the Array Group. A plurality of Constituent Volumes will then be assigned to the Pool to provide the actual capacity for storing the tier2 data. Storage Extent230-2 is storage capacity which is carved from the Constituent Volume as an atom of data stored extent.

Similarly, the Storage Volume Composition of thetier1 Storage System100 will have the same elements as the tier2 device, as shown with the Array Group210-1, the Constituent Volumes220-1 and the Storage Extent230-1. Generally, the Constituent Volumes themselves are not shown directly to the end user in terms of the thin provisioning storage service but rather in terms of the amount of free space provided as Pool240-1. The Thin Provisioning Chunk250 is a unit of capacity allocated from the Pool to the Thin Provisioned Volume260-1. The Pool is associated with both tier levels of Constituent Volumes220-1 and220-2, thus it can provide both tier type of Chunks to the Thin Provisioned Volume. The Thin Provisioned Volume260-1 is the storage volume that is exposed to the Client Hosts130. It is represented as if it has full size capacity, but only the extent to which data has been written by the Client Host will be allocated. When the Client Host writes data to the extent that unallocated capacity needs to be used, the Storage System will generate a new Thin Provisioning Chunk and associate it to the Thin Provisioned Volume to the extent of the data written by the Client Host. The Chunk may be carved from the tier1 device internally or from the externally attached tier2 device.

The software stored and executed by theController101 includes a TieredStorage Management Module200, which uses and manages a Pool Table500, a Thin Provisioned Volume Table600 and a Chunk Table700. The TieredStorage Management Module200 is a key program of this invention for the operation of data migration between the tiered storage devices. The Pool Table500 holds records for Pools which have a respective Constituent Volume ID and tier information. The Thin Provisioned Volume Table600 holds records which have the Pool ID that the volume was carved from and related Chunk Table ID for the volume. The Chunk Table700 holds records of the Chunk attributes and the ID of the Constituent Volume where the actual data was stored for each Chunk. The Chunk Table will be generated for each Thin Provisioned Volume.

FIG. 3 illustrates the condition of the system during the data Migration and specifically it shows Storage Volume composition of

tier1 Storage Systems

100,110, and120.Storage System110 represents the migration target tier1 system (whileStorage System100 represents as the migration source storage system in this figure). The components of this system are the same asStorage System100, which was described above. However the relationship of the systems will be changed during or after the migration operation. The Thin Provisioned Volume260-2 is the newly created volume, which is the target of the data copy operation from the source Thin Provisioned Volume260-1. After the completion of the migration, theClient Host130 will unmount Thin Provisioned Volume260-1 from the source side and mount the Thin Provisioned Volume260-2 for the target side. During the migration, in this embodiment of the invention, only the contents of tier1 chunks will be copied to the target storage system and in accordance with the copy new tier1 Thin Provisioning Chunk250-3 will be allocated from the Pool240-2 to the Thin Provisioned Volume260-2. Also, these chunks are originally carved from the tier1 Constituent Volumes220-3.

During the migration, tier2 Constituent Volumes220-2 which were associated with the Pool240-1 on the migration source device will be mounted to the Pool240-2 on the target device side (remapping the related tier2 Constituent Volumes from source device to the target device). Therefore, the existing tier2 Chunks250-4 can be accessed by the client host computer as a part of the Thin Provisioned Volume260-2.

The Pool Table500-2, Thin Provisioned Volume Table600-2 and Chunk Table700-2 are updated or generated during the migration and related information on the source device side will be discarded after the migration.

FIGS. 4,5 and6 illustrate data structure of various tables stored in the Memory of the Controller. Specifically,FIG. 4 shows an exemplary data structure of the Pool Table500. The tables contain information on which Constituent Volumes compose respective Pools.

In the table ofFIG. 4, thePool ID column510 provides an identification of a Pool. The C-Vol ID column520 provides Identification of the Constituent Volume, which composes the Pool.

TheTier column530 provides the information on the Tier of the Constituent Volume.

For instance,line591 in the table represents a record of a Pool which has “PS1” as the ID and one of its Constituent Volume is “T1CV1” and it is Tier “1” type that is placed within the primary storage device.Line592 shows information for another Constituent Volume “T2CV5” of Pool “PS1” and that is Tier “2” type that is placed within the secondary storage device that is externally attached.

This table is referred by the TieredStorage Management Module200 to determine associated Constituent Volumes for specific Pool with Tier type.

FIG. 5 shows an exemplary data structure of Thin Provisioned Volume Table600. Specifically, it shows the relationship between Pools and Thin Provisioned Volumes and the specific Chunk Table ID for the volume.

The TP-Vol ID column610 provides identification information of a Thin Provisioned Volume.

Pool ID column

620 provides identification information of the Pool that the Volume was carved from.

ChunkTable ID column630 provides an identification of a specific Chunk Table for the volume.

For instance,line691 represents a record of a Thin Provisioned Volume, which has “TPVS1” as the ID and it was carved from Pool “PS1” and is related to the Chunk information that is stored in the Chunk Table “CTS1”.

This table is referred by the TieredStorage Management Module200 to determine associated Pool and Chunk Table for the migration volume.

FIG. 6 shows an exemplary data structure of the Chunk Table. The contents of this table illustrates attributes of the Chunks.

Chunk ID column

710 provides identification information of a Chunk.

C-Vol ID column720 provides an identification of Constituent Volume, which the Chunk was carved from.

Tier column

730 provides information on the tier of the Chunk or the Constituent Volume.

StartLBA column740 provides an LBA on the Constituent Volume, which shows the start address of the Chunk.

Number ofBlocks column750 provides information on the number of valid blocks within the Chunk.

For instance,line791 represents a record of a Chunk which has “CS1” as the ID, it is stored from LBA “0” on the Tier “1” Constituent Volume “T1CV1” with the valid “32” blocks from the beginning. During the allocation of Chunks to the specific size of data, it will be break down to Chunks with its maximum size of blocks (I assume 32 blocks for example). But end portion might not to fit this boundary thus it's often be less length than maximum blocks in a Chunk. For instance, Number of Blocks ofline793 shows it has only 25 blocks of valid data within the Chunk.

This table is referred by TieredStorage Management Module200 to obtain the Tier of respective Chunks and also to obtain its attributes during the migration operation.

FIGS. 7,8 and9 illustrate an exemplary process for Thin Provisioned Volume migration between the tiered storage systems executed by TieredStorage Management Module200. Through the steps from1000 to1020, the process creates a new Thin Provisioned Volume on the target tier1 device side.

Step1000: Create new Chunk Table on the target tier1 device, which holds the Chunk information for the new Thin Provisioned Volume of the migration target.

Step1010: The system will determine a proper Pool to carve a new Thin Provisioned Volume from the Pools, which exist on the migration target device. This could be determined using a variety of methods, such as choosing a Pool, which has the most free space.

Step1020: Add new record to the Thin Provisioned Volume Table of target tier1 device with new (the system generated) TP-Vol ID, ID for the Pool selected instep1010 and Chunk Table ID of the created new Chunk Table instep1000.

Through the steps from1030 to1070 the system mounts Tier2 Constituent Volumes of the tier2 device to the migration target tier1 device.

Step1030: Select the record corresponding to the migration source volume from Thin Provisioned Volume Table of the source tier1 device. In addition, a corresponding Pool ID is obtained.

Step1040: Select a record from Pool Table of source tier1 device where Pool ID is the value obtained instep1030, which means the Pool related to the migration source volume, and also where the Constituent Volume is on the tier2 device. If all records are processed then proceed to step1100 otherwise proceed to step1050.

Step1050: Get ID of the corresponding Constituent Volume on the record selected instep1040. If the tier2 Constituent Volume has been mounted to the target tier1 device then proceeds back to step1040 or otherwise proceeds to step1060. If any other Thin Provisioned Volume, which originally associated with the Pool, was migrated before to the target tier1 device, related tier2 Constituent Volumes might already be mounted to the target tier1 device. In that case, it doesn't need to mount again.

Step1060: Mount tier2 Constituent Volume obtained instep1050 to the target tier1 device and associate it with the Pool determined in step1010 (the Pool associated to the migration target Thin Provisioned Volume).

Step1070: Add new record to Pool Table of target tier1 device with Pool ID determined instep1010, Tier type of 2 and Constituent Volume ID obtained instep1050. And then proceed back to step1040 for the next tier2 Constituent Volume.

Through the steps from1100 to1150 it copies tier1 Chunk data content.

Step1100: Select the record for the migration source volume from Thin Provisioned Volume Table of source tier1 device and get its Chunk Table ID.

Step1110: Select a record from the selected Chunk Table instep1100 where Tier is 1. If all records are processed then proceed to step1200 otherwise proceed to step1120.

Step1120: Create a new Thin Provisioning Chunk at the target Tier1 device carving from tier1 Constituent Volume.

Step1130: Copy content data of the Chunk selected instep1110 to the created Chunk in the target tier1 device.

Step1140: Add new record to Chunk Table created instep1000 with new Chunk ID, Tier of 1, ID of the Constituent Volume that was used to create new Chunk instep1120, Start LBA of the Chunk within the Constituent Volume and its Number of Blocks.

Step1150: Release the Storage Extent of the Chunk on the source Tier1 device. And then proceed back to step1110 for the next tier1 Chunk copy.

Through the steps from1200 to1210 it copies just records of tier2 data.

Step1200: Select a record from the selected Chunk Table instep1100 where Tier is2. If all records are processed then proceed to step1220 otherwise proceed to step1210.

Step1210: Add new record to the Chunk Table created instep1000 with new Chunk ID, Tier of 2, and copy the rest of columns C-Vol ID/Start LBA/Number of Blocks as on the record selected instep1200. And then proceed back to step1200 for the next tier2 Chunk entry.

Through the steps from1220 to1230 the process deletes Thin Provisioned Volume on the source tier1 device.

Step1220: Drop Chunk Table obtained instep1100, which is the Chunk Table for the migration source Thin Provisioned Volume, from source tier1 device.

Step1230: Delete the record for migration source volume from the Thin Provisioned Volume Table of source tier1 device.

A second embodiment of the inventive system will now be described. In the first embodiment described above only the contents of tier1 Chunks were actually copied during the migration operation. Because the method of the first embodiment did not copy the entire content of tier2 Chunks, it reduced the time of migration. In the second embodiment, to reduce the migration time as much as possible, the inventive system demotes every tier1 Chunk to tier2 Chunk prior to the migration process such that no actual data copy will be performed but only the remapping of the Tier2 Constituent Volume will be performed and hence the migration time will be extremely short. Because the chunk based tiered storage system has automatic/dynamic chunk migration mechanism between tiers within the system, the original tier1 Chunks will be eventually promoted from tier2 to Tier1, if the corresponding data has characteristics corresponding to Tier1. This occurs after the migration has been completed. Of course, in this case, the demotion and promotion process might be considered as an overhead from the perspective of overall migration operation. However, the priority of various operations depends on the usage characteristics of the system and, therefore, this method is described as another embodiment of this invention.

Most of the components and processes of the second embodiment are the same as the corresponding components and methods of the first embodiment. Thus, only the differences will be described below.

FIG. 10 illustrates an exemplary process for Chunk demotion (tier1 to tier2 Chunk) executed by the TieredStorage Management Module200. This process will be performed prior to the Volume Migration process shown in the first embodiment fromstep1000 to1230, when the migration operation has triggered.

Step1300: Select the record for the migration source volume from Thin Provisioned Volume Table of source tier1 device and get its Chunk Table ID.

Step1310: Select a record from the selected Chunk Table instep1300 where Tier is 1. If all records are processed, then proceed to step1000 and start actual volume migration process. Otherwise proceed to step1320.

Step1320: Create a new Thin Provisioning Chunk at the source Tier1 device carving from tier2 Constituent Volume.

Step1330: Copy content data of the Chunk selected instep1310 to the Chunk created instep1320.

Step1340: Update the record of the Chunk Table selected instep1310, changing the Tier from “1” to “2” and C-Vol ID as the Constituent Volume ID that was used to create new Chunk instep1320 and its Start LBA.

Step1350: Release the Storage Extent of the tier1 Chunk. After that, proceed back to step1310 for the next tier1 Chunk demotion.

After the completion of tier1 Chunk demotion process above, the Volume Migration process, shown in the first embodiment starts from thestep1000. During the process, fromstep1110 to step1150, which copy tier1 Chunk data between Tier1 devices will be skipped due to the fact that no tier1 Chunks are left on the source Tier1 device after the demotion process. Therefore, the process of the Volume Migration is exactly the same as shown in the first embodiment and can be used in the second embodiment as well.

FIG. 11 is a block diagram that illustrates an embodiment of a computer/server system1400 upon which an embodiment of the inventive methodology may be implemented. Thesystem1400 includes a computer/server platform1401,peripheral devices1402 andnetwork resources1403.

Thecomputer platform1401 may include adata bus1404 or other communication mechanism for communicating information across and among various parts of thecomputer platform1401, and aprocessor1405 coupled withbus1401 for processing information and performing other computational and control tasks.Computer platform1401 also includes avolatile storage1406, such as a random access memory (RAM) or other dynamic storage device, coupled tobus1404 for storing various information as well as instructions to be executed byprocessor1405. Thevolatile storage1406 also may be used for storing temporary variables or other intermediate information during execution of instructions byprocessor1405.Computer platform1401 may further include a read only memory (ROM or EPROM)1407 or other static storage device coupled tobus1404 for storing static information and instructions forprocessor1405, such as basic input-output system (BIOS), as well as various system configuration parameters. Apersistent storage device1408, such as a magnetic disk, optical disk, or solid-state flash memory device is provided and coupled to bus1101 for storing information and instructions.

Computer platform

1401 may be coupled viabus1404 to adisplay1409, such as a cathode ray tube (CRT), plasma display, or a liquid crystal display (LCD), for displaying information to a system administrator or user of thecomputer platform1401. Aninput device1410, including alphanumeric and other keys, is coupled tobus1401 for communicating information and command selections toprocessor1405. Another type of user input device iscursor control device1411, such as a mouse, a trackball, or cursor direction keys for communicating direction information and command selections toprocessor1404 and for controlling cursor movement ondisplay1409. This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allows the device to specify positions in a plane.

Anexternal storage device1412 may be coupled to thecomputer platform1401 viabus1404 to provide an extra or removable storage capacity for thecomputer platform1401. In an embodiment of thecomputer system1400, the externalremovable storage device1412 may be used to facilitate exchange of data with other computer systems.

The invention is related to the use ofcomputer system1400 for implementing the techniques described herein. In an embodiment, the inventive system may reside on a machine such ascomputer platform1401. According to one embodiment of the invention, the techniques described herein are performed bycomputer system1400 in response toprocessor1405 executing one or more sequences of one or more instructions contained in thevolatile memory1406. Such instructions may be read intovolatile memory1406 from another computer-readable medium, such aspersistent storage device1408. Execution of the sequences of instructions contained in thevolatile memory1406 causesprocessor1405 to perform the process steps described herein. In alternative embodiments, hard-wired circuitry may be used in place of or in combination with software instructions to implement the invention. Thus, embodiments of the invention are not limited to any specific combination of hardware circuitry and software.

The term “computer-readable medium” as used herein refers to any medium that participates in providing instructions toprocessor1405 for execution. The computer-readable medium is just one example of a machine-readable medium, which may carry instructions for implementing any of the methods and/or techniques described herein. Such a medium may take many forms, including but not limited to, non-volatile media and volatile media. Non-volatile media includes, for example, optical or magnetic disks, such asstorage device1408. Volatile media includes dynamic memory, such asvolatile storage1406.

Common forms of computer-readable media include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, or any other magnetic medium, a CD-ROM, any other optical medium, punchcards, papertape, any other physical medium with patterns of holes, a RAM, a PROM, an EPROM, a FLASH-EPROM, a flash drive, a memory card, any other memory chip or cartridge, a carrier wave as described hereinafter, or any other medium from which a computer can read.

Various forms of computer readable media may be involved in carrying one or more sequences of one or more instructions toprocessor1405 for execution. For example, the instructions may initially be carried on a magnetic disk from a remote computer. Alternatively, a remote computer can load the instructions into its dynamic memory and send the instructions over a telephone line using a modem. A modem local tocomputer system1400 can receive the data on the telephone line and use an infra-red transmitter to convert the data to an infra-red signal. An infra-red detector can receive the data carried in the infra-red signal and appropriate circuitry can place the data on thedata bus1404. Thebus1404 carries the data to thevolatile storage1406, from whichprocessor1405 retrieves and executes the instructions. The instructions received by thevolatile memory1406 may optionally be stored onpersistent storage device1408 either before or after execution byprocessor1405. The instructions may also be downloaded into thecomputer platform1401 via Internet using a variety of network data communication protocols well known in the art.

Thecomputer platform1401 also includes a communication interface, such asnetwork interface card1413 coupled to thedata bus1404.Communication interface1413 provides a two-way data communication coupling to anetwork link1414 that is coupled to alocal network1415. For example,communication interface1413 may be an integrated services digital network (ISDN) card or a modem to provide a data communication connection to a corresponding type of telephone line. As another example,communication interface1413 may be a local area network interface card (LAN NIC) to provide a data communication connection to a compatible LAN. Wireless links, such as well-known 802.11a, 802.11b, 802.11g and Bluetooth may also used for network implementation. In any such implementation,communication interface1413 sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.

Network link

1413 typically provides data communication through one or more networks to other network resources. For example,network link1414 may provide a connection throughlocal network1415 to ahost computer1416, or a network storage/server1417. Additionally or alternatively, thenetwork link1413 may connect through gateway/firewall1417 to the wide-area orglobal network1418, such as an Internet. Thus, thecomputer platform1401 can access network resources located anywhere on theInternet1418, such as a remote network storage/server1419. On the other hand, thecomputer platform1401 may also be accessed by clients located anywhere on thelocal area network1415 and/or theInternet1418. The

network clients

1420 and1421 may themselves be implemented based on the computer platform similar to theplatform1401.

Local network

1415 and theInternet1418 both use electrical, electromagnetic or optical signals that carry digital data streams. The signals through the various networks and the signals onnetwork link1414 and throughcommunication interface1413, which carry the digital data to and fromcomputer platform1401, are exemplary forms of carrier waves transporting the information.

Computer platform

1401 can send messages and receive data, including program code, through the variety of network(s) includingInternet1418 andLAN1415,network link1414 andcommunication interface1413. In the Internet example, when thesystem1401 acts as a network server, it might transmit a requested code or data for an application program running on client(s)1420 and/or1421 throughInternet1418, gateway/firewall1417,local area network1415 andcommunication interface1413. Similarly, it may receive code from other network resources.

The received code may be executed byprocessor1405 as it is received, and/or stored in persistent or

volatile storage devices

1408 and1406, respectively, or other non-volatile storage for later execution. In this manner,computer system1401 may obtain application code in the form of a carrier wave.

It should be noted that the present invention is not limited to any specific firewall system. The inventive policy-based content processing system may be used in any of the three firewall operating modes and specifically NAT, routed and transparent.

Finally, it should be understood that processes and techniques described herein are not inherently related to any particular apparatus and may be implemented by any suitable combination of components. Further, various types of general purpose devices may be used in accordance with the teachings described herein. It may also prove advantageous to construct specialized apparatus to perform the method steps described herein. The present invention has been described in relation to particular examples, which are intended in all respects to be illustrative rather than restrictive. Those skilled in the art will appreciate that many different combinations of hardware, software, and firmware will be suitable for practicing the present invention. For example, the described software may be implemented in a wide variety of programming or scripting languages, such as Assembler, C/C++, perl, shell, PHP, Java, etc.

Moreover, other implementations of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. Various aspects and/or components of the described embodiments may be used singly or in any combination in the computerized tiered storage systems with data migration functionality. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the invention being indicated by the following claims.

Claims

1. A system comprising:

a first storage system configured to:

manage a volume, a first type of tier storage area and a second type of tier storage area,

allocate a storage area of the first type of tier storage area and the second type of tier storage area to a first logical area of a plurality of logical areas of the volume, if the first storage system receives a first write data from a computer to the volume;

and a second storage system configured to:

manage the volume, another first type of tier storage area and another second type of tier storage area;

wherein the volume is configured to be migrated from the first storage system to the second storage system in a status of:

(i) an allocation of the another first type of tier storage area to the first logical area of the volume, if the first type of tier storage area is allocated to the first logical area of the volume, and

(ii) an allocation of the another second type of tier storage area to the first logical area of the volume, if the second type of tier storage area is allocated to the first logical area of the volume.

2. The system according toclaim 1, wherein the second storage system is further configured to:

allocate a storage area of the another first type of tier storage area and the another second type of tier storage area to a second logical area of the plurality of logical areas of the volume, if the second storage system receives a second write data from the computer to the volume after the migration.

3. The system according toclaim 1, wherein the first storage system and the second storage system are further configured to manage a type of tier storage area attribute for the first logical area of the volume.

4. The system according toclaim 3, wherein the first storage system and the second storage system are further configured to manage a type of tier storage area attribute for each of the plurality of logical areas of the volume.

5. The system according toclaim 1, wherein the volume is a thin provisioned volume.

6. The system according toclaim 1, wherein the type of tier storage area is defined based on at least a type of disk interface.

7. The system according toclaim 1 wherein the type of tier storage area is defined based on whether the logical area corresponds to another volume of an external storage system.

8. A storage system, comprising:

a central processing unit (CPU) that is configured to:

manage a volume, a first type of tier storage area and a second type of tier storage area; and

process a migration of the volume to the storage system in a status of:

(i) an allocation of the first type of tier storage area to a first logical area of the volume, if a first type of tier storage area of another storage system is allocated to the first logical area of the volume, and

(ii) an allocation of the second type of tier storage area to the first logical area of the volume, if a second type of tier storage area of the another storage system is allocated to the first logical area of the volume.

9. The system according toclaim 8, wherein the CPU is further configured to:

allocate a storage area of the first type of tier storage area and the second type of tier storage area to a second logical area of the volume, if a second write data from the computer to the volume is received after the migration.

10. The storage system according toclaim 8, wherein the CPU is further configured to manage a type of tier storage area attribute for the first logical area of the volume.

11. The storage system according toclaim 10, wherein the CPU is further configured to manage a type of tier storage area attribute for each of a plurality of logical areas of the volume.

12. The storage system according toclaim 8, wherein the volume is a thin provisioned volume.

13. The storage system according toclaim 8, wherein the type of tier storage area is defined based on at least a type of disk interface.

14. The storage system according toclaim 8, wherein the type of tier storage area is defined based on whether the logical area corresponds to another volume of an external storage system.

15. A non-transitory computer readable medium storing instructions for executing a process for a storage system, the instructions comprising:

managing a volume, a first type of tier storage area and a second type of tier storage area;

processing a migration of the volume to the storage system in a status of:

16. The non-transitory computer readable medium according toclaim 15, wherein the instructions further comprise:

allocating a storage area of the first type of tier storage area and the second type of tier storage area to a second logical area of the volume, if a second write data from the computer to the volume is received after the migration.

17. The non-transitory computer readable medium according toclaim 15, wherein the instructions further comprise:

managing a type of tier storage area attribute for each of a plurality of logical areas of the volume.

18. The non-transitory computer readable medium according toclaim 15, wherein the volume is a thin provisioned volume.

19. The non-transitory computer readable medium according toclaim 15, wherein the type of tier storage area is defined based on at least a type of disk interface.

20. The non-transitory computer readable medium according toclaim 15, wherein the type of tier storage area is defined based on whether the logical area corresponds to another volume of an external storage system.