Data migration system and data migration method

• US 8,316,065 B2
• Filed: 06/23/2009
• Issued: 11/20/2012
• Est. Priority Date: 04/23/2009
• Status: Expired due to Fees

• Current Assignee: Hitachi, Ltd.
• Original Assignee: Hitachi, Ltd.
• Inventors: Nemoto, Jun, Sutoh, Atsushi, Kamei, Hitoshi, Nakano, Takahiro
• Primary Examiner(s): Smith, Brannon W
• Application Number:
  US12/490,047
• Publication Number:
  US 20100274825A1
• Time in Patent Office: 1,246 Days
• Field of Search: 707/640, 707/999.101, 707/827
• US Class Current: 707/827
• 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 that includes a processor;

a first file server that includes a processor, which is coupled to said data migration device;

a second file server that includes a processor, 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 second 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;

said first file system has a first file;

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

said first file server creates a tiered structure in which said second file system, and said third file system, are consolidated virtually;

when migrating said first file, said second file server;

receives file creation instruction from said data migration device;

creates a second file where a first inode number is imparted to said second file system, wherein the second file is in a temporary state in a pseudo file system;

receives attribute information of said first file;

when said second file is determined to be in the temporary state in the pseudo file system as determined by referring to an object management table, refers to said attribute information of said first file to assign attribute information to said second file;

determines which file system said first file is migrated to, said second file system or said third file system,

when migration to said third file system is determined;

creates a third file where a second inode number signifying said third file being a real file in a real file system is imparted to said third file system;

receives and stores data of said first file as data of said third file; and

sets attribute information of said second file to correspond to said attribute information of said third file,

wherein said object management table includes a plurality of entries each assigning a pseudo inode number of a virtual file in a pseudo file system with a real inode number of a real file in a real file system.

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

said second file server has a migration policy for determining the file system which is to be the migration destination for said object; and

determines the migration destination of said first file, on the basis of said attribute information and said migration policy.

3. A data migration system according to claim 2, wherein, said second 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 second file server, determining the file system which is to be the destination of moving;

if priority levels are set for said tier movement policy and said migration policy, applies said tier movement policy and said migration policy according to said priority levels.

4. A data migration method according to claim 3 wherein,

said second 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 second file server, determining the file system which is to be the destination of moving;

if priority levels are set for said tier movement policy and said migration policy, applies said tier movement policy and said migration policy according to said priority levels.

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

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.

6. A data migration system according to claim 5, wherein said second storage device is a disk drive, and said third storage device is SATA (Serial ATA) disk drive.

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

said second 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 second file server, determining the file system which is to be the destination of moving;

said migration policy and said tier movement policy are different.

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

said second file server has a migration policy for determining the file system which is to be the migration destination for said object; and

determines the migration destination of said first file, on the basis of said attribute information and said migration policy.

9. 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 second file server has a restore policy based upon said attribute information, for determining the file system of the restore destination for said file which is stored upon said fourth storage device;

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

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

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

if migration of said first file to said second file is determined, the system stores data of said first file as data of said second file.

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

in a tiered structure of said second file system and said third file system, said second file system is a higher ranking tier and said third system is a lower ranking tier.

13. A data migration system according, to claim 1, comprising a fourth storage device which is coupled to said second file server, wherein:

said second file server

creates a fourth file system upon said fourth storage device;

creates a tiered structure in which said third file system and said fourth file system are consolidated virtually;

determines which file system said first file is migrated to, said third file system or said fourth file system, and

said second file system is a pseudo file system and said second file is a virtual file.

14. A data migration system according to claim 13, comprising a fourth storage device which is coupled to said second file server, wherein:

said second file server

creates a fourth file system upon said fourth storage device;

creates a tiered structure in which said third file system and said fourth file system are consolidated virtually;

determines which file system said first file is migrated to, said third file system or said fourth file system, and

said second file system is a pseudo file system and said second file is a virtual file.

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

said first file server, when receiving attribute information acquisition request from said data migration device, transmits attribute information of said first file, and when receiving data transmission request from said data migration device, transmits data of said first file.

10. 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 that includes a processor;

a first file server that includes a processor, which is coupled to said data migration device;

a second file server that includes a processor, 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 second 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;

said first file system has a first file;

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

said first file server creates a tiered structure in which said second file system, and said third file system, are consolidated virtually;

when migrating said first file, said processor of said second file server;

receives file creation instruction from said data migration device;

creates a second file where a first inode number is imparted to said second file system, wherein the second file is in a temporary state in a pseudo file system;

receives attribute information of said first file;

when said second file is determined to be in the temporary state in the pseudo file system as determined by referring to an object management table, refers to said attribute information of said first file to assign attribute information to said second file;

determines which file system said first file is migrated to, said second file system or said third file system, when migration to said third file system is determined;

creates a third file where a second inode number signifying said third file being a real file in a real file system is imparted to said third file system;

receives and stores data of said first file as data of said third file; and

sets attribute information of said second file to correspond to said attribute information of said third file,

wherein said object management table includes a plurality of entries each assigning a pseudo inode number of a virtual file in a pseudo file system with a real inode number of a real file in a real file system.