File server, file management system and file relocation method

A file management system in which a storage apparatus including a plurality of RAID groups each of which is constituted by one or more volumes, a client for making an access request to a file, and a file server for managing files stored in said plurality of RAID groups by using real file systems and a virtual file system are coupled to each other in a communications-capable manner, said real file systems being created for said RAID groups, said virtual file system being constituted by virtually integrating said real file systems to each other, wherein

• said storage apparatus
• stores therein mapping information in which a one-to-one correspondence is established for each file among file name used when said file is managed in said virtual file system, first file-attribute identification information, and second file-attribute identification information, said first file-attribute identification information being attribute identification information on said file of said virtual file system for managing said file name, said second file-attribute identification information being attribute identification information on said file of said real file system of a RAID group in which said file is actually stored,
• said file server, when said access request to said file is made from said client,
• acquiring a user name concerning said access request, and time-and-date of a coupling request/decoupling request to/from said file server, and creating coupling history information for managing coupling history on coupling time-zone for each user name, and memorizing said coupling history information into said virtual file system of said storage apparatus;
• extracting non-coupling time-zone for each user name based on said coupling history information, applying a grouping to said user names for each similar non-coupling time-zone, establishing a mutual relationship between each grouped group name and each grouped user name, and memorizing said mutual relationship result into said virtual file system of said storage apparatus as similar-access user group management information;
• creating non-coupling time-zone management information, and memorizing said information into said virtual file system of said storage apparatus, said non-coupling time-zone management information being designed for establishing a mutual relationship between each group name in said similar-access user group management information and said non-coupling time-zone to said file server;
• extracting an accessible file by retrieving said file-attribute identification management information on said file system on said RAID group from each user name registered in said similar-access user group management information, establishing a mutual relationship between said extracted file and each group name, and memorizing said mutual relationship result into said virtual file system of said storage apparatus as similar-access file group management information;
• determining a RAID group into which said file belonging to each group is scheduled to be stored, and transferring said file included in said similar-access file group management information so that said file will belong to said RAID group determined, and simultaneously updating said mapping information;
• and, based on said non-coupling time-zone management information,
• issuing an instruction of applying spin-down to said RAID group during said non-coupling time-zone, and issuing an instruction of applying spin-up to said RAID group during a time-zone which is not said non-coupling time-zone.

A file relocation method, comprising the steps of:

• elocating files stored in a plurality of RAID groups;
• and
• anaging operation time-zones of said RAID groups in a file management system in which a storage apparatus including said plurality of RAID groups each of which is constituted by one or more volumes, a client for making an access request to a file, and a file server for managing said files stored in said plurality of RAID groups by using real file systems and a virtual file system are coupled to each other in a communications-capable manner, said real file systems being created for said RAID groups, said virtual file system being constituted by virtually integrating said real file systems to each other, wherein
• said storage apparatus
• stores therein mapping information in which a one-to-one correspondence is established for each file among file name used when said file is managed in said virtual file system, first file-attribute identification information, and second file-attribute identification information, said first file-attribute identification information being attribute identification information on said file of said virtual file system for managing said file name, said second file-attribute identification information being attribute identification information on said file of said real file system of a RAID group in which said file is actually stored,
• said file server, when said access request to said file is made from said client,
• acquiring a user name concerning said access request, and time-and-date of a coupling request/decoupling request to/from said file server, and creating coupling history information for managing coupling history on coupling time-zone for each user name, and memorizing said coupling history information into said virtual file system of said storage apparatus;
• extracting non-coupling time-zone for each user name based on said coupling history information, applying a grouping to said user names for each similar non-coupling time-zone, establishing a mutual relationship between each grouped group name and each grouped user name, and memorizing said mutual relationship result into said virtual file system of said storage apparatus as similar-access user group management information;
• creating non-coupling time-zone management information, and memorizing said information into said virtual file system of said storage apparatus, said non-coupling time-zone management information being designed for establishing a mutual relationship between each group name in said similar-access user group management information and said non-coupling time-zone to said file server;
• extracting an accessible file by retrieving said file-attribute identification management information on said file system on said RAID group from each user name registered in said similar-access user group management information, establishing a mutual relationship between said extracted file and each group name, and memorizing said mutual relationship result into said virtual file system of said storage apparatus as similar-access file group management information;
• determining a RAID group into which said file belonging to each group is scheduled to be stored, and transferring said file in said similar-access file group management information so that said file will belong to said RAID group determined, and simultaneously updating said mapping information;
• and, based on said non-coupling time-zone management information,
• issuing an instruction of applying spin-down to said RAID group during said non-coupling time-zone, and issuing an instruction of applying spin-up to said RAID group during a time-zone which is not said non-coupling time-zone.

A file server which is coupled to a storage apparatus in a communications-capable manner for managing files stored in a plurality of RAID groups, and managing operation time-zones of said RAID groups, said storage apparatus including said plurality of RAID groups each of which is constituted by one or more volumes,

• said file server, comprising:
• a memory device;
• and
• a processing part, wherein
• (1) said memory device includes:
• 1-A:
• file name of a file accessed from a client;
• and
• 1-B:
• predetermined information for allowing a one-to-one correspondence to be established between said file name and one of said plurality of RAID groups in which said file is actually stored,
• (2) said processing part:
• 2-A:
• when an access request to said file is made from said client, acquiring a user name concerning said access request, and time-and-date of a coupling request/decoupling request to/from said file server;
• 2-B:
• creating coupling history information for managing coupling history on coupling time-zone for each user name, and memorizing said coupling history information into said memory device;
• 2-C:
• extracting non-coupling time-zone for each user name based on said coupling history information, and applying a grouping to said user names for each similar non-coupling time-zone;
• 2-D:
• establishing a mutual relationship between each grouped group name and each grouped user name, and memorizing said mutual relationship result into said memory device as similar-access user group management information;
• 2-E:
• creating non-coupling time-zone management information, and memorizing said information into said memory device, said non-coupling time-zone management information being designed for establishing a mutual relationship between each group name in said similar-access user group management information and said non-coupling time-zone to said file server;
• 2-F:
• extracting an accessible file by retrieving information on said RAID group from each user name registered in said similar-access user group management information;
• 2-G:
• establishing a mutual relationship between said extracted file and each group name, and memorizing said mutual relationship result into said memory device as similar-access file group management information;
• 2-H:
• determining a RAID group into which said file belonging to each group is scheduled to be stored;
• 2-I:
• transferring said file included in said similar-access file group management information so that said file will belong to said RAID group determined;
• and
• 2-J:
• based on said non-coupling time-zone management information, issuing an instruction of applying spin-down to said RAID group during said non-coupling time-zone, and issuing an instruction of applying spin-up to said RAID group during a time-zone which is not said non-coupling time-zone.