DATA MIGRATION SYSTEM AND DATA MIGRATION METHOD

• US 20100274825A1
• Filed: 06/23/2009
• Published: 10/28/2010
• Est. Priority Date: 04/23/2009
• Status: Active Grant

• Current Assignee: Hitachi, Ltd.
• Original Assignee: Hitachi, Ltd.
• Inventors: NAKANO, Takahiro, KAMEI, Hitoshi, NEMOTO, Jun, SUTOH, Atsushi
• Granted Patent: US 8,316,065 B2
• Time in Patent Office: Days
• US Class Current: 707/812
• CPC Class Codes: G06F 16/119 Details of migration of file systems migration mechanisms in storage systems G06F3/0647
• CPC Class Codes: G06F 16/185 Hierarchical storage management [HSM] systems, e.g. file migration or policies thereof details of archiving G06F16/11
• CPC Class Codes: G06F 3/0605 by facilitating the interaction with a user or administrator
• CPC Class Codes: G06F 3/0647 Migration mechanisms
• CPC Class Codes: G06F 3/067 Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]

Abstract

When performing migration of data from a migration source file server which is not endowed with any HSM interface, to a migration destination file server which is endowed with HSM, a volume of high capacity is needed for the migration destination file server, and moreover the performance deteriorates directly after the migration. However, with this system, the manager is enabled to set a migration policy using attribute information which can be acquired through a standard file access interface possessed by a file server program, and, when setting the attribute information of the migration destination file, the tier of the file which is to be created is determined, and the migration destination file is created, on the basis of this attribute information and migration policy.

Claims

1. A data migration system, comprising:

a data migration device;

a first file server which is coupled to said data migration device;

a second file server which is coupled to said data migration device;

a first storage device which is coupled to said first file server;

a second storage device which is coupled to said first file server; and

a third storage device which is coupled to said second file server;

wherein;

said first file server creates a first file system upon said first storage device and a second file system upon said second storage device;

said first file server creates a tiered structure in which said first file system, which is taken as being of higher ranking, and said second file system, which is taken as being of lower ranking, are consolidated virtually;

said first file server has a tier movement policy based upon attribute information for, when moving an object having attribute information within the file systems of said first file server, determining the file system which is to be the destination of moving;

said data migration device, when migrating an object which is stored upon said third storage device, acquires attribute information for said object which is stored upon said third storage device; and

said data migration device determines the file system to which said object is to be migrated, and migrates said object, on the basis of said attribute information and said tier movement policy.

2. A data migration system according to claim 1, wherein:

said data migration device has a migration policy based upon attribute information, for determining the file system which is to be the migration destination for said object; and

if said tier movement policy is not to be applied, said data migration device determines the file system which is to be the migration destination for said object, and migrates said object, on the basis of said attribute information and said migration policy.

3. A data migration system according to claim 2, wherein, if priority levels are set for said tier movement policy and said migration policy, said data migration device applies said tier movement policy and said migration policy according to said priority levels.

4. A data migration system according to claim 2, wherein:

said object is a file or a directory; and

;

if said object is a file;

said file has data and attribute information; and

said attribute information of said file is size, creation time, last update time, and last access time of said file;

while, if said object is a directory;

said directory has attribute information; and

said attribute information of said directory is creation time, last update time, and last access time of said directory.

5. A data migration system according to claim 4, wherein said first storage device is a SATA (Serial ATA) disk drive, and said second storage device is a FC (Fiber Channel) disk drive.

6. A data migration system according to claim 1, wherein:

said data migration device is further coupled to a media server, and said media server is coupled to a fourth storage device;

said first file server has a restore policy based upon said attribute information, for determining the file system of the restore destination for said object which is stored upon said fourth storage device;

said first file server, when migrating said object, acquires said object from said media server, and acquires attribute information from said object; and

said first file server determines the file system of the restore destination for said object, and restores said object, on the basis of said attribute information which has been acquired and said restore policy.

7. A data migration system according to claim 4, wherein:

said first file server maintains a correspondence relationship between identifiers of file systems upon which said files are stored, and inode numbers of said files; and

said first file server, when a file identifier acquisition request has been received, transmits the identifier of said file, and, when a read request for a file having said identifier has been received, specifies the file system upon which said file is stored, and responds to said read request from said file system, from said correspondence relationship.

8. A data migration method in which an object is migrated by a data migration device in a data migration system comprising:

said data migration device;

a first file server which is coupled to said data migration device;

a second file server which is coupled to said data migration device;

a first storage device which is coupled to said first file server;

a second storage device which is coupled to said first file server; and

a third storage device which is coupled to said second file server;

wherein;

said first file server creates a first file system upon said first storage device and a second file system upon said second storage device;

said first file server creates a tiered structure in which said first file system, which is taken as being of higher ranking, and said second file system, which is taken as being of lower ranking, are consolidated virtually;

said first file server has a tier movement policy based upon attribute information for, when moving an object having attribute information within the file systems of said first file server, determining the file system which is to be the destination of moving;

said data migration device, when migrating an object which is stored upon said third storage device, acquires attribute information for said object which is stored upon said third storage device; and

said data migration device determines the file system to which said object is to be migrated, and migrates said object, on the basis of said attribute information and said tier movement policy.

9. A data migration method according to claim 8, wherein:

said data migration device has a migration policy based upon attribute information, for determining the file system which is to be the migration destination for said object; and

if said tier movement policy is not to be applied, said data migration device determines the file system which is to be the migration destination for said object, and migrates said object, on the basis of said attribute information and said migration policy.

10. A data migration method according to claim 9, wherein, if priority levels are set for said tier movement policy and said migration policy, said data migration device applies said tier movement policy and said migration policy according to said priority levels.

11. A data migration method according to claim 9, wherein:

said object is a file or a directory; and

;

if said object is a file;

said file has data and attribute information; and

said attribute information of said file is size, creation time, last update time, and last access time of said file;

while, if said object is a directory;

said directory has attribute information; and

said attribute information of said directory is creation time, last update time, and last access time of said directory.

12. A data migration method according to claim 11, wherein said first storage device is a SATA (Serial ATA) disk drive, and said second storage device is a FC (Fiber Channel) disk drive.

13. A data migration method according to claim 8, wherein:

said data migration device is further coupled to a media server, and said media server is coupled to a fourth storage device;

said first file server has a restore policy based upon said attribute information, for determining the file system of the restore destination for said object which is stored upon said fourth storage device;

said first file server, when migrating said object, acquires said object from said media server, and acquires attribute information from said object; and

said first file server determines the file system of the restore destination for said object, and restores said object, on the basis of said attribute information which has been acquired and said restore policy.

14. A data migration method according to claim 11, wherein:

said first file server maintains a correspondence relationship between identifiers of file systems upon which said files are stored, and inode numbers of said files; and

said first file server, when a file identifier acquisition request has been received, transmits the identifier of said file, and, when a read request for a file having said identifier has been received, specifies the file system upon which said file is stored, and responds to said read request from said file system, from said correspondence relationship.

15. A data migration system, comprising a data migration device, a first file server which is coupled to said data migration device, a second file server which is coupled to said data migration device, a first storage device which is coupled to said first file server, a second storage device which is coupled to said first file server, and a third storage device which is coupled to said second file server;

and wherein;

said first file server creates a first file system upon said first storage device and a second file system upon said second storage device;

said first file server creates a tiered structure in which said first file system, which is taken as being of higher ranking, and said second file system, which is taken as being of lower ranking, are virtually consolidated;

said first file server has a tier movement policy based upon attribute information for, when moving an object having attribute information and data within the file systems of said first file server, determining the file system which is to be the destination of moving;

said data migration device has a migration policy based upon attribute information, for determining the file system of the migration destination for said object;

said data migration device, when migrating a file which is stored upon said third storage device, acquires attribute information for said object which is stored upon said third storage device;

said data migration device determines the file system to which said object is to be migrated, and migrates said object, on the basis of said attribute information and said tier movement policy or said migration policy;

said first file server creates a file in said file system which has been determined, and sets said attribute information for said file which has been created, and said data migration device reads in the data from the file stored upon said third storage device; and

said first file server writes said data into said file which has been created.