JP2008040699A - Hsm control program, hsm control unit, and hsm control method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an HSM control program, an HSM control unit, and an HSM control method for managing the generation of the backup of name space in HSM efficiently. <P>SOLUTION: The HSM control program for allowing a computer to execute the control of HSM having a primary storage 1 and a secondary storage 2 allows the computer to execute a generation information creation step for creating generation information that is information including the generation number of backup for each backup of HSM, and a history management step for managing name space information that is information related to the name space for each file in HSM and an effective generation number range for showing the range of the generation number where information related to the name space is effective using the generation number created by the generation information creation step as a name space information history. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to an HSM control program, an HSM control apparatus, and an HSM control method for performing backup generation management in HSM.

  HSM (Hierarchical Storage Management) builds an inexpensive large-capacity file system by combining a low-speed storage device (secondary storage) such as a tape library with a high-speed storage device (primary storage) such as a hard disk. To do.

  In the HSM control device, it is necessary to identify a file that has not been accessed for a long time in the primary storage, write the file to the secondary storage, and move it to the primary storage when access is requested. Conventionally, in order to realize this, the conventional HSM control device summarizes the name space of the file system having a hierarchical structure, and writes it to the secondary storage by referring to the access time that the file system holds for each file. A method for identifying files is used.

As a related art related to the present invention, for example, Patent Document 1 shown below is known. This data processing apparatus collects a log when the content of metadata data is updated, and corrects inconsistency of the file system using this log.
JP 2000-48495 A

  However, the above-described HSM control apparatus that licks the name space has the following problems.

  First, there is a problem of total file system licking overhead. In the conventional HSM control apparatus, since the file name space having a hierarchical structure is periodically totaled, the overhead becomes large.

  Second, there is a namespace exclusion problem. If a file name change operation such as a rename operation is performed while the HSM control device licks the name space, the path name obtained in the licking process is invalid and does not actually exist. For this reason, the HSM control device may perform a data movement operation inconsistent with the policy set by the customer. For example, if the upper directory is moved to the trash box during the search, the entire trash box may be moved. In order to prevent these problems, the HSM controller must check the contradiction frequently during the lumping process, and if there is a contradiction, it is necessary to start the licking again, which makes the logic very complex and greatly increases the overhead. .

  Third, there is flexibility in HSM policy control. In general, a hierarchical name space represents the nature of a stored file group, so it is natural to set an HSM policy based on the name space (all files under a certain directory, etc.). However, there is a problem that it is difficult to realize complicated policy control based on the name space due to the above-described name space exclusion problem.

  Fourth, there is a problem of insufficient attribute information of data saved in the secondary storage. In addition, due to the above-described namespace exclusion problem, it is difficult to add a correct path name to the data stored in the secondary storage. For this reason, the data stored in the secondary storage can only be accessed from the file system metadata. If the file system metadata is corrupted, the data remains on the secondary storage. There is a problem that the file data cannot be recovered because it cannot be associated with the path name.

  The present invention has been made to solve the above-described problems, and an object of the present invention is to provide an HSM control program, an HSM control apparatus, and an HSM control method for efficiently performing name space backup generation management in HSM. To do.

  In order to solve the above-described problem, the present invention is an HSM control program that causes a computer to execute control of an HSM having a primary storage and a secondary storage, and includes information including a generation number of the backup for each backup of the HSM. Generation information creation step for creating generation information, name space information that is information on the name space for each file in the HSM, and information on the name space using the generation number created in the generation information creation step. The computer executes a history management step for managing a valid generation number range indicating a valid generation number range as a namespace information history.

  In addition, in the HSM control program according to the present invention, when the update of the namespace information in the HSM file system is detected, the history management step includes an update target file that is a target file for updating the namespace information. The name space information history corresponding to is updated.

  In the HSM control program according to the present invention, when the update of the namespace information is creation of the update target file, the history management step newly creates a current generation namespace information history of the update target file. The effective generation number range is set to the current generation or later.

  In the HSM control program according to the present invention, when the update of the namespace information is the first update after the backup of the update target file, the history management step includes the current generation namespace information of the update target file. Change the end point of the valid generation number range in the history to the generation number of the last backup, create a new name space information history for the file to be updated, and set the valid generation number range of the name space information history to the current generation or later It is characterized by.

  In the HSM control program according to the present invention, the history management step further extracts the name space information history in which the generation number designated from outside falls within the valid generation number range, and the name obtained by the extraction A file corresponding to the spatial information history is output as a file to be restored.

  In the HSM control program according to the present invention, the generation information creation step further includes copying a file updated after the previous backup from the primary storage to the secondary storage.

  In the HSM control program according to the present invention, the backup is a snapshot.

  Further, the present invention is an HSM control device that controls an HSM having a primary storage and a secondary storage, and generates generation information that is information including a generation number of the backup for each backup of the HSM. A range of generation numbers in which the information on the name space is valid using the creation unit, the name space information that is information on the name space for each file in the HSM, and the generation number created by the generation information creation unit And a history management unit that manages the valid generation number range as a namespace information history.

  In the HSM control device according to the present invention, when the update of the namespace information in the HSM file system is detected, the history management unit updates the update target file that is a target file of the update of the namespace information. The name space information history corresponding to is updated.

  In the HSM control device according to the present invention, when the update of the namespace information is creation of the update target file, the history management unit newly creates a current generation namespace information history of the update target file. The effective generation number range is set to the current generation or later.

  Further, in the HSM control device according to the present invention, when the update of the namespace information is the first update after the backup of the update target file, the history management unit stores the current generation namespace information of the update target file. Change the end point of the valid generation number range in the history to the generation number of the last backup, create a new name space information history for the file to be updated, and set the valid generation number range of the name space information history to the current generation or later It is characterized by.

  In the HSM control device according to the present invention, the history management unit further extracts the name space information history whose generation number designated from the outside falls within the valid generation number range, and the name obtained by the extraction A file corresponding to the spatial information history is output as a file to be restored.

  In the HSM control device according to the present invention, the generation information creating unit further copies a file updated after the previous backup from the primary storage to the secondary storage.

  In the HSM control device according to the present invention, the backup is a snapshot.

  In addition, the present invention is an HSM control method for controlling an HSM having a primary storage and a secondary storage, and for each generation of the HSM, generation information that creates generation information that is information including a generation number of the backup A range of generation numbers in which the information about the name space is valid is shown using the creation step, the name space information that is information about the name space for each file in the HSM, and the generation number created by the generation information creation step. A history management step for managing the valid generation number range as a namespace information history is executed.

  According to the present invention, generation management of name space backup in HSM can be performed efficiently.

  Hereinafter, in order to describe an embodiment of the present invention, a premise technique will be described with reference to the drawings.

(Prerequisite technology 1)
In the base technology 1, a server that is an HSM control device will be described.

  First, the configuration of the HSM device having the server according to the base technology 1 will be described.

  FIG. 1 is a block diagram illustrating an example of a configuration of an HSM apparatus according to the base technology 1. Primary storage 1 that is a high-speed storage device such as a disk device that stores recently accessed files, and secondary storage 2 that is a low-speed storage device such as a tape library device that stores file data that has not been accessed for a long time. And an HSM control device according to the base technology 1, and is composed of a server 3 on which an application for accessing file data operates.

  The server 3 includes an application unit 11, a file system control unit 12, a namespace replication unit 13, a namespace tracking unit 14, a namespace replication DB (Database) 15, and a migration determination unit 16. Further, the file system control unit 12 includes an event data recording unit 21.

  Next, each part of the server 3 will be described.

  The event data recording unit 21 is a program arranged in the file system control unit 12 that accumulates the history of file operation requests issued by the application program as event data. The event data recording unit 21 converts the contents of the file operation request issued by the application unit 11 into event data and accumulates it in the memory. When a certain amount is accumulated, the event data recording unit 21 sends the information to the namespace replication unit 13 and the namespace tracking unit 14. hand over. Event data may be transferred using communication or via a dedicated file.

  The name space replicating unit 13 is a program for replicating the name space of the file system in parallel with the operation of the application unit 11. The name space replication unit 13 follows the name space of the file system and acquires file information of an existing file. This file information and the event data received from the event data recording unit 21 during the file information acquisition are combined to complete the initial namespace replication as the namespace replication DB 15.

  The namespace follower 14 has a function of updating the replica according to the event data received from the event data recording unit 21 after the initial replication of the namespace is completed, and maintaining the namespace replica DB 15 in the latest state. The namespace follower 14 also plays a role of reflecting the notified file access and archive state in the namespace replication DB 15.

  As an example of policy control, the migration determination unit 16 drives out files that have not been accessed for a long time in the primary storage 1 to the secondary storage 2 in accordance with the file access record set by the namespace replication unit 13 and the policy set by the user. Therefore, this is a program that issues an instruction to the file system control unit 12. Normally, a file system controller 12 returns a file that has been evicted (migrated) to the secondary storage 2 from the secondary storage 2 to the primary storage 1 when the application unit 11 accesses the file (recall). . In addition, at the timing when the file is updated, the data (archive data) on the secondary storage 2 is invalidated by the file system control unit 12. Data on the secondary storage 2 does not disappear at this timing, and remains as backup data until the secondary storage 2 runs short, and is used for recovery in the event of a file system failure or the like.

  Next, details of event data, file information, and namespace replication DB 15 will be described.

  First, event data will be described.

  The event data (event) created by the event data recording unit 21 represents the contents of file operations such as file and directory creation and deletion, file name change, file access, and archive state change. In addition to the time taken, each contains the following data: Here, the archive state change includes events such as validation / invalidation of archive data, migration, and recall.

(1) Creation of file or directory event. recttype = create
event. m_inode # = parent directory inode number event. ftype =
dir (during mkdir) or file (during create)
event. fname = name of created file event. inode # =
Inode number event. Of the created file or directory. time = time when this event occurred

(2) Delete file or directory event. recttype = delete
event. m_inode # = parent directory inode number event. ftype = dir (during rmdir) or file (during remove)
event. inode # = inode number of deleted file or directory event. time = time when this event occurred

(3) File name change event. recttype = rename
event. m_inode # = parent directory inode number event. ftype =
dir (when the target is a directory)
Or file (if the target is a file)
event. inode # =
Inode number event. Of the target file or directory. target. m_inode # =
Inode number event. Of the destination directory. target. fname =
Changed file or directory name event. time = time when this event occurred

(4) File access (application program reads / writes file)
event. recttype = access
event. inode # = file inode number event. time = time when this event occurred

(5) Archive state change event. recttype = archive
event. inode # = file inode number event. migrate =
On (becomes migrated)
Or off (recall is activated and no longer migrated)
event. archive =
ON (Export of file data to secondary storage is complete, and archive data becomes valid)
Or off (archive data became invalid as a result of file update)
event. time = time when this event occurred

  Next, file information will be described.

The file information (fstat) acquired from the file system during namespace replication restoration includes the following.
fstat. m_inode # = parent directory inode number fstat. ftype = dir (when the target is a directory)
Or file (if the target is a file)
fstat. fname = name of directory or file fstat. inode # =
File or directory inode number fstat. archive = on (when archive data is valid)
Or off (when archive data is invalid)
fstat. migrate = on (when migrating)
Or off (when not migrated)
fstat. atime = time when the file was last accessed fstat. time = file information acquisition time

  Next, the configuration of the namespace replication DB 15 will be described.

  The namespace replication DB 15 is a relational DB having the following column (dbe) and having a tuple for each file or directory element set in the directory.

dbe. m_inode # = parent directory inode number dbe. ftype = dir (when this tuple represents a directory) or file (when this tuple represents a file)
dbe. fname = name of file or directory dbe. inode # = file or directory inode number dbe. archive = on (when archive data is valid)
Or off (when archive data is invalid)
dbe. migrate = on (when migrating)
Or off (when not migrated)
dbe. atime = time when file was last accessed dbe. active = ON (when file information has been acquired)
Or off (when file information has not been acquired yet)

  Next, the operation of the server 3 will be described.

  FIG. 2 is a flowchart showing an example of the operation of the file information acquisition process according to the base technology 1. The server 3 executes a namespace replication process (S11), a namespace tracking process (S12), and a migration process (S13).

  Next, details of the operation in the server 3 will be described.

  First, the namespace replication process will be described.

  The namespace replication process is a process in which the namespace replication unit 13 creates an initial replica of the namespace, and includes a file information acquisition process and an event data reflection process. In the namespace replication processing, when the event data stored in the memory is lost, such as when the server is restarted after the failure occurs, the contents of the namespace replication DB 15 cannot reflect the latest state of the file system. In addition, it operates for the purpose of re-creating the namespace replication DB 15. In the configuration in which the namespace replication DB 15 is dynamically recreated in this way, it is not necessary to make event data non-volatile when an event occurs, and it is only necessary to store it in a small capacity memory. Overhead can be reduced.

  The name space replication unit 13 first obtains the file information acquisition process by opening the parent directory, specifying the child file name or child directory name as an argument, and issuing a file system information acquisition function (getinfo). Further, the name space duplicating unit 13 obtains information on directories and files existing in the file system without omission by following the name space in the ascending order (or descending order) of the path name. What was missed in this process is recorded as event data, and will be corrected later.

  FIG. 3 is a diagram illustrating an example of a hierarchical structure of directories in the name space. This name space has a hierarchical structure of directories, and directory names and file names are sorted from left to right in ascending order. FIG. 4 is a flowchart showing an example of the operation of the file information acquisition process according to the base technology 1.

  First, the name space duplication unit 13 finds the directory at the bottom left by tracing the directories in the lower left direction (in ascending order of the directory name) with the root directory of the target file system as a base point. The found lower left directory is set as the target directory, and the path name of the target directory obtained in the search process is set as the target directory path name (S201). Next, the namespace replication unit 13 obtains the file information of the target directory and the file information of all the files existing in the target directory one by one in the ascending order of the file names, and sequentially writes them at the end of the file information recording file (S202). Next, the namespace replication unit 13 determines whether or not the target directory is a root directory (S203). If the target directory is the root directory (S203, Y), it means that all files have been processed, and the file information acquisition process is terminated.

  On the other hand, if the target directory is not the root directory (S203, N), the namespace replication unit 13 obtains the directory path name one level above the target directory from the target directory path name, that is, the final configuration directory that constitutes the path name. The path name with the name removed is taken as the new path name. Next, the name space replicating unit 13 sequentially searches the obtained directory path name downward from the root directory again, and sets the final directory whose existence has been confirmed by this search as the base directory (S205). If the directory in the middle of the path is moved to another location in the namespace, such as in rename, it will not be found in the middle, but this part will be found in the subsequent file information acquisition process, or it will be notified by event data, and later Since it is corrected, it can be ignored.

  Next, the namespace replication unit 13 reads the contents of the base directory and determines whether there is an unprocessed directory in the base directory (S206). When there is an unprocessed directory (S206, Y), the namespace replication unit 13 obtains an unprocessed lower left directory, sets this as a target directory (S207), and proceeds to process S202. If an unprocessed directory does not exist, that is, if a directory having a file name larger than that indicated by the target directory path name does not exist in the base directory (S206, N), the target directory path name is set as the path name of the base directory. (S208), the process proceeds to S203.

  Next, when all the file information acquisition processing of the target file system is completed, the namespace replication unit 13 performs event data reflection processing for reflecting event data generated during that time to the file information. When the file information recording file is read in order from the top and all the file information recorded in the file information recording file has been processed, the event data reflection processing ends.

  FIG. 5 is a flowchart showing an example of the operation of the event data reflection process according to the base technology 1. First, the namespace replication unit 13 extracts unprocessed file information (S302), sequentially extracts event data having times before the information acquisition time set in the file information, and reflects them in the namespace replication DB 15 ( S303).

  Here, with respect to the reflection to the namespace replication DB 15, a case where the event data is a deletion system, a generation system, a file name change, a file access, and an archive state change will be described.

  When the event data is a deletion system (file deletion, directory deletion), the namespace replication unit 13 deletes the file or directory to be deleted if it has already been registered in the namespace replication DB 15. Otherwise it does nothing. Here, if there is an entry that satisfies all of the following conditions, it is regarded as registered.

dbe. inode # == event. inode #
dbe. m_inode # == event. m_inode #
dbe. fname == event. fname

  When the event data is a generation system (file generation, directory generation), the namespace replication unit 13 registers the acquired file or directory if the information has been acquired unless the created file or directory has been registered in the namespace replication DB 15. If registered, ignore this event data and do nothing. Here, if there is an entry that satisfies all of the following conditions, it is regarded as registered.

dbe. inode # == event. inode #
dbe. m_inode # == event. m_inode #
dbe. fname == event. fname

  The setting contents when not registered are shown below.

dbe. m_inode # = event. m_inode #
dbe. ftype = event. ftype
dbe. fname = event. fname
dbe. inode # = event. inode #
dbe. archive = off dbe. migrate = off dbe. atime = event. time
dbe. active = on

  When the event data is a file name change (event.recttype == rename), the name space duplication unit 13 has already registered a file or directory having the same name as after the rename (with the file name and parent inode number). Evaluation), the entry is deleted from the namespace replication DB 15. Here, if there is an entry that satisfies all of the following conditions, it is regarded as registered.

dbe. name == event. target. fname
dbe. m_inode # ==
event. target. m_inode #
dbe. fname == event. target. fname

  Here, if the target file is already registered in the namespace replication DB 15, the parent information and the file name of the entry are changed. Here, if there is an entry that satisfies all of the following conditions, it is regarded as registered.

dbe. inode # == event. inode #
dbe. m_inode # == event. m_inode #
dbe. fname == event. fname

  The contents of the change at this time are shown below.

dbe. m_inode # = event. target. m_inode #
dbe. name = event. target. fname

  If the target file is not registered, the renamed file is registered as a new entry in the namespace replication DB 15.

dbe. inode # = event. inode #
dbe. m_inode # = event. target. m_inode #
dbe. name = event. target. fname
dbe. active = off

  When the event data is file access (event.recttype == access), the namespace replication unit 13 ignores the event data if the target inode is not registered. If registered, the file last access time, archive information, and recall information of all registered entries are updated (because there is a hard link). Here, if there is an entry that satisfies all of the following conditions, it is regarded as registered.

dbe. inode # == event. inode #

  The contents of the change at this time are shown below.

dbe. atime = event. time

  If the event data is an archive state change (event.recttype == archive), this event data is ignored if the target inode is not registered. If registered, update the archive information of all entries (because there are hard links). Here, if there is an entry that satisfies all of the following conditions, it is regarded as registered.

dbe. inode # == event. inode #

  The contents of the change at this time are shown below.

dbe. archive = event. archive
dbe. migrate = event. migrate

  Next, the name space replication unit 13 registers the content of the file information as information acquisition if it is not registered in the name space replication DB 15 (S305). When tuples having the same inode number are registered, the contents of all registered entries are changed. Here, when there is an entry that satisfies all of the following conditions, it is regarded as registered.

dbe. inode # == fstat. inode #
dbe. fname == fstat. fname
dbe. m_inode # == fstat. m_inode #

  The setting contents when not registered are shown below.

dbe. m_inode # = fstat. m_inode #
dbe. ftype = fstat. ftype
dbe. fname = fstat. fname
dbe. inode # = fstat. inode #
dbe. archive = fstat. archive
dbe. migrate = fstat. migrate
dbe. atime = fstat. atime
dbe. active = on

  In addition, the setting contents when the same inode number has already been registered (that is, when dbe.inode # = fstat.inode #) are shown below.

dbe. archive = fstat. archive
dbe. migrate = fstat. migrate
dbe. atime = fstat. atime
dbe. active = on

  Next, when the namespace replication unit 13 finishes processing all recorded file information, the namespace segment missed in the information acquisition due to a conflict with the name space change (information acquisition completed is not displayed). It is determined whether or not (directory) exists (S311). If it does not exist (S311, N), this flow ends. On the other hand, if it exists (S311, Y), the file information acquisition process with the directory as the root and the event data reflection process that occurred in the meantime are performed (S312), and the process returns to process S311 to display the next information acquisition completed Find a directory that doesn't exist and repeat this process.

  Next, the name space tracking process will be described.

  The namespace follower 14 receives event data generated after the namespace replication processing is completed from the event data recording unit 21 and sequentially reflects it in the namespace replication DB 15. The event data reflection process is almost the same as the namespace replication process, but is simple because it does not use file information.

  When the event data is a deletion type file operation event (file deletion, directory deletion), the namespace tracking unit 14 stores an entry including all of the inode number, the parent inode number, and the file name indicated by the event data on the namespace replication DB 15. Delete from.

  When the event data is a generation system file operation event (file generation, directory generation), the namespace tracking unit 14 registers an entry including the inode number indicated by the event data on the namespace replication DB 15 and conveys it by event data. Set attribute (type) and parent inode number.

  If the event data is a file name change (rename) and the same file as the target exists, the namespace follower 14 deletes it. Further, the namespace follower 14 changes the parent attribute of the source.

  When the event data is a file access event, the namespace follower 14 specifies the access time conveyed by the event data by the inode number and sets it in the namespace replication DB 15.

  If the event data is an archive state change, the namespace follower 14 updates the archive information.

  Next, the migration process will be described.

  The migration determining unit 16 periodically checks the free space status of the primary storage 1 using a command provided by the file system, and when the free space amount is equal to or less than the amount specified by the user, the namespace replication DB 15 The file to be migrated is determined using the information set in, and the file system control unit 12 is requested for migration. At this time, the migration determining unit 16 passes the path name of the file obtained from the namespace replication DB 15 to the file system control unit 12 and writes it to the secondary storage 2 together with the file data. The migration determination process can be implemented in various ways depending on the user policy. An example is shown below.

  FIG. 6 is a flowchart showing an example of the operation of the migration determination process according to the base technology 1. First, the migration determining unit 16 determines whether the shortage of the primary storage 1 is serious (S401).

  When the shortage of the primary storage 1 is serious (S401, Y), the migration determining unit 16 searches the namespace replication DB 15, finds files that have been archived and not migrated (S411), and all found The following release processing (release of the primary storage area) is performed for the file. Next, the migration determining unit 16 determines whether there is an unprocessed file among the found files (S412).

  If there is no unprocessed file (S412, N), this flow ends. On the other hand, if there is an unprocessed file (S412, Y), the migration determination unit 16 releases the target file (releases the primary storage) to the file system control unit 12 using the inode number set in the namespace replication DB 15 as an argument. ) Is requested (S413). Next, upon obtaining a response from the file system control unit 12, the migration determining unit 16 returns to the process S412 and processes the next target file.

  Here, the migration determination unit 16 follows the name space replication DB 15 with a delay in the file system, so there may be cases where the file actually does not exist or the archive is invalid. The file system control unit 12 returns an error response. If the file has been archived, the file system control unit 12 releases the primary storage area allocated to the file and returns a normal response.

  On the other hand, when the primary storage 1 is insufficient but not so serious (N in S401), the migration determining unit 16 is configured to perform a certain period of time in order to improve the situation immediately when a serious shortage occurs. Archive files that have not been accessed. For this reason, the migration determining unit 16 searches the namespace replication DB 15 and finds one whose last access time is before a predetermined time (for example, current time—one day) and whose archive is invalid (not archived) (S421). ). Next, the migration determining unit 16 determines whether there is an unprocessed file among the found files (S422).

  If there is no unprocessed file (S422, N), this flow ends. On the other hand, if there is an unprocessed file (S422, Y), the migration determination unit 16 repeatedly searches the namespace replication DB 15 using the parent inode number set in the namespace replication DB 15 as a key. Is obtained (S423). Next, the migration determining unit 16 issues an archive request with the inode number and the file path name as arguments to the file system control unit 12 (S424). Here, the file system control unit 12 collectively writes the specified file data, file path name, and inode number on the secondary storage, returns to the process S422, and processes the next target file. If the requested file no longer exists, the file system control unit 12 responds with an error and ignores the request.

  Next, the operation of other units will be described.

  First, the file system control unit 12 will be described.

  First, when there is a release request from the migration determining unit 16, the file system control unit 12 processes the release request, and if there is a copy of file data in the secondary storage (archived), the primary storage is returned. And migrated. At this time, the event data recording unit 21 creates an archive state change event.

event. recttype = archive
event. archive = on event. migrate = on

  When there is an archive request from the migration determination unit 16, the file system control unit 12 processes the archive request, starts writing the file data to the secondary storage 2, and returns to the migration determination unit 16. To do. At this time, the file path name notified from the file migration determining unit 16 is added to the header portion of the data to be written to the secondary storage 2 and written. When the writing to the secondary storage 2 is completed, the event data recording unit 21 creates an archive state change event.

event. recttype = archive
event. archive = on event. migrate = off

  When the application unit 11 tries to access the migrated file, the file system control unit 12 newly allocates an area on the primary storage 1 at the timing when the application unit 11 tries to access the secondary storage 2. Load the above data into the area. Thereafter, the event data recording unit 21 creates an archive state change event indicating the completion of the recall.

event. recttype = archive
event. archive = on event. migrate = off

  When the application unit 11 requests a file operation (file generation / deletion, directory generation / deletion, file read / write), the file system control unit 12 processes the request and records the event data when it completes normally. The unit 21 creates corresponding event data.

  When file information is requested by getinfo from the namespace replication unit 13, the file system control unit 12 confirms that the specified file exists in the parent directory, and then returns the file information of the specified file. If it does not exist, respond with an error. When an error is returned, the namespace replication unit 13 continues the processing assuming that the file does not exist.

  Next, the event data recording unit 21 will be described.

  The event data recording unit 21 is a part that exists in the file system control unit 12, creates event data at the timing described in the description of the file system control unit 12, and accumulates it in the memory. In addition, the event data recording unit 21 stores the event data accumulated in the memory when the event data accumulated in the memory exceeds a certain amount or when a certain time has elapsed since the last notification. Collectively, the namespace follower 14 or the namespace replica 13 is notified. Further, even when the system is stopped, the event data stored in the event data recording unit 21 is notified to the name space tracking unit 14, and the name space tracking unit 14 stores the event data stored in the memory in the name space replication DB 15. Perform system stop processing that reflects everything.

  Further, the event data recording unit 21 performs the following optimization in order to reduce the amount of data to be notified. First, when the event data recording unit 21 creates a file access event, if a file access event for the same file is included in unreported event data stored in the memory, the subsequent file access event is throw away. That is, it does not accumulate on the memory. Further, when the event data recording unit 21 is requested to create a file deletion event, if the corresponding file generation event is included as unreported event data, the file generation event is invalidated on the memory, and the event data notification Remove from target.

  Next, system startup processing in the server 3 will be described.

  When the system is normally terminated, as described above, the namespace tracking unit 14 performs the normal termination process of reflecting the event data staying in the memory to the namespace replication DB 15 at a time. There is no need to operate the duplication unit 13. On the other hand, in the event of a failure, at the time of subsequent restart, the namespace replication unit 13 is operated to perform a startup process after abnormal termination of the system to reinitialize the namespace replication DB 15. Even in this case, the namespace information immediately before the failure remains, so if the migration target needs to be determined before the re-initialization of the namespace replication is completed, the migration decision unit Uses the old replica for processing.

  In the base technology 1, the migration determining unit 16 has been described as an example of policy control based on the namespace replication DB 15. However, another policy control in HSM control may be performed based on the namespace replication DB 15.

  In the HSM device such as the base technology 1 described above, when a file in the primary storage 1 is updated, data is newly stored in the secondary storage 2 at an arbitrary timing, so that past data is accumulated. store. When creating a backup as a snapshot of the HSM system at a certain time, it is also necessary to create a backup of the namespace replication DB 15 at that time. Further, in the restoration, it is necessary to restore the namespace replication DB 15 from the backup of the namespace replication DB 15, extract a file based on the information, and restore the primary storage 1. Here, the load of the backup processing of the namespace replication DB 15, the restoration processing of the namespace replication DB 15, and the extraction processing of the files to be restored is heavy.

  In addition, in the backup in the conventional HSM apparatus realized only by the file system, it is necessary to save information in the file system at that time on another medium, and the processing load is large.

  Embodiments of the present invention will be described below with reference to the drawings.

Embodiment 1 FIG.
In the present embodiment, a description will be given of an HSM system that efficiently performs generation management of name space backup in an HSM system that creates and updates a replica of a name space in the same manner as in the base technology 1.

  First, the configuration of the HSM system according to the present embodiment will be described.

  FIG. 7 is a block diagram showing an example of the configuration of the HSM system according to the present embodiment. In this figure, the same reference numerals as those in FIG. 1 denote the same or corresponding parts as those in FIG. 1, and the description thereof is omitted here. The HSM system includes a primary storage 1, a secondary storage 2, an operation server 102, and an HSM control server 103 (HSM control device).

  The operation server 102 includes a file system control unit 12. The HSM control server 103 includes a storage management unit 131, a storage management DB 132, and a storage management DB backup 133. The storage management unit 131 includes a generation management table 141 and a name space information table 142. Note that the namespace replication unit 13, the namespace tracking unit 14, and the migration determination unit 16 in the base technology 1 correspond to the storage management unit 131 in the present embodiment.

  The generation information creation step corresponds to the management of the generation management table 141 by the storage management unit 131 in the present embodiment. The history management step corresponds to the management of the name space information table 142 by the storage management unit 131 in the present embodiment. The generation information creation unit corresponds to the management function of the generation management table 141 in the storage management unit 131 in the present embodiment. The history management unit corresponds to the management function of the name space information table 142 in the storage management unit 131 in the present embodiment.

  The storage management DB backup 133 is a backup created for recovery of the entire storage management DB 132, such as when a disk failure occurs in the storage management DB 132, and only the latest backup is created, and generation management is unnecessary.

  Next, the storage management DB 132 will be described.

  FIG. 8 is a table showing a first example of the contents of the generation management table 141 according to the present embodiment. The generation management table 141 is a table for managing backup generation information. One record is generation information of one backup generation, and has backup acquisition date and time stamp and generation number gen. The generation number is a number assigned in order every time backup is acquired.

  FIG. 9 is a table showing a first example of the contents of the namespace information table 142 according to the present embodiment. The name space information table 142 is a table for managing records having a difference in name space information for each generation in addition to the current generation records having the same name space information as the records in the name space replication DB 15. Each record (namespace information history) includes, in addition to the namespace information, a valid generation number range indicating a generation number range in which the namespace information is valid. Each record in the namespace information table 142 includes a file name (including a path name) name, other file attribute information (user name user, group name group, inode update time ctime, data update time mtime), and secondary storage data identifier. It has an archived and valid generation number range gen (from-to). The valid generation number range represents a generation number range in which the record is valid by a start generation number and an end generation number. In the current generation record, the valid generation number range includes only the start generation number and no end generation number (the end generation number “-” represents ∞).

  Next, snapshot creation processing by the storage management unit 131 will be described. In the snapshot creation process, the storage management unit 131 performs a data snapshot creation process for creating a snapshot of file data, and performs a namespace snapshot creation process for creating a namespace snapshot. Here, the storage management unit 131 saves file data that has not been archived among the file data of the primary storage 1 to the secondary storage 2 as data snapshot creation processing. In addition, as a namespace snapshot creation process, the storage management unit 131 adds a new record to the generation management table 141, and sets the date and time when the snapshot was created and a new generation number. This process alone completes the namespace snapshot creation process.

  Next, the namespace information table update process by the storage management unit 131 will be described.

  FIG. 10 is a flowchart showing an example of a first operation of the namespace information table update process according to the present embodiment. FIG. 11 is a flowchart showing an example of the second operation of the namespace information table update processing according to the present embodiment. When the storage management unit 131 receives event data indicating the update contents of the name space from the file system control unit 12, this flow starts. First, the storage management unit 131 acquires the last backup generation number and the current generation number from the generation management table 141 (S511). Next, the storage management unit 131 determines the type of the received event data (S512).

  When the event data indicates file creation in process S512 (S512, file creation), the storage management unit 131 creates a new file record in the namespace information table 142, and within the effective generation number range of the record, the start generation number = Current generation number and end generation number = ∞ are set (S513), and this flow ends.

  If the event data indicates file deletion in step S512 (S512, file deletion), the storage management unit 131 determines whether the deletion target file is a backup target (S521). Here, if the valid generation number range of the current generation record of the target file in the namespace information table 142 satisfies the condition of start generation number <current generation number and end generation number = ∞, the first after snapshot creation processing Therefore, it is determined that the target file is a backup target. If the above-mentioned conditions are not satisfied, it is determined that the deletion target file is not a backup target because the snapshot creation processing has not been performed after the file creation or file change.

  If it is a backup target (S521, Y), the storage management unit 131 does not change the start generation number and changes the end generation number within the valid generation number range of the current generation record of the deletion target file in the name space information table 142. By setting the last backup generation number, it is saved as a record of the past generation (S522), and this flow ends. On the other hand, when it is not a backup target (S521, N), the storage management unit 131 deletes the record of the deletion target file (S524), and this flow ends.

  When the event data indicates a file change in step S512 (S512, file change), the storage management unit 131 determines whether the change target file is a backup target (S531 in FIG. 11). Similarly to the processing S521, when the valid generation number range of the current generation record of the target file in the name space information table 142 satisfies the condition of start generation number <current generation number and end generation number = ∞, the snapshot creation processing Since this is the first update after that, it is determined that the target file is a backup target. If the above-described conditions are not satisfied, it is determined that the file to be changed is not a backup target because the snapshot creation process has not been performed after the file creation or file modification.

  If it is a backup target (S531, Y), the storage management unit 131 does not change the start generation number and changes the end generation number within the valid generation number range of the current generation record of the change target file in the name space information table 142. By setting the last backup generation number, it is saved as a record of the previous generation (S532). Next, the storage management unit 131 newly creates a record of the target file in the namespace information table 142, and sets the effective generation number range of the record to start generation number = current generation number, end generation number = ∞. (S533), this flow ends. On the other hand, if it is not the backup target (S531, N), the storage management unit 131 updates the record of the change target file according to the event data (S534), and this flow ends.

  Next, a specific example of the generation management operation by the storage management unit 131 will be described.

  FIG. 12 is a sequence diagram showing a specific example of the generation management operation according to the present embodiment. This figure shows the state of the namespace information table update processing for file A, file B, file C, and file D. The downward direction represents the passage of time. At time t (6), a snapshot creation process with generation number 206 is performed, and at time t (7), a snapshot creation process with generation number 207 is performed. The generation number (current generation number) is 208 at the current time t (8).

  The contents until the file A is created or changed and then changed or deleted are represented by a (1), a (2), a (3), and a (4) in this order. Similarly, the contents of the file data of the file B are represented by b (1) and b (2) in order. Similarly, the contents of the file data of file C are represented in order by c (1). Similarly, the contents of the file data of the file D are represented by d (1) and d (2) in order. The contents of the files a (1), a (2), a (3), a (4), b (1), b (2), c (1), d (1), d (2) The lifetime of is represented by a line segment. Of the snapshot creation processing, processing for saving file data is represented by S611, S612, S613, and S614. Of the namespace information table update processing, the processing for saving the namespace information is represented by S711, S712, S713, and S714.

  Next, the namespace information table update process when the file A is created as the content a (1) will be described. At this time, the final backup generation number = 205 and the current generation number = 206 (S511). Next, since the event data is file creation (S512), the storage management unit 131 creates a new file A record in the name space information table 142, and within the valid generation number range, start generation number = current generation number. (206), the end generation number = ∞ is set (S513).

  Next, the namespace information table update process when the file B is created as the content b (1) will be described. At this time, the final backup generation number = 205 and the current generation number = 206 (S511). Next, since the event data is file creation (S512), the storage management unit 131 creates a new file B record in the name space information table 142, and within the valid generation number range, start generation number = current generation number. (206), the end generation number = ∞ is set (S513).

  Next, at time t (6), the storage management unit 131 performs a snapshot creation process for the generation number (206). Here, the storage management unit 131 creates a new record in the generation management table 141, and sets the time t (6) and the generation number (206) to perform a namespace snapshot creation process. In addition, the storage management unit 131 performs data snapshot creation processing (S611) of a (1) and data snapshot creation processing (S612) of b (1).

  Next, the namespace information table update process when the file C is created as the content c (1) will be described. At this time, the final backup generation number = 206 and the current generation number = 207 (S511). Next, since the event data is file creation (S512), the storage management unit 131 newly creates a record of file C in the namespace information table 142, and within the valid generation number range, start generation number = current generation number. (207), the end generation number = ∞ is set (S513).

  Next, the namespace information table update process when the file A is changed from content a (1) to a (2) will be described. At this time, the final backup generation number = 206 and the current generation number = 207 (S511). Next, since the event data is a file change (S512), the storage management unit 131 indicates that the current generation record of the file A in the namespace information table 142 is the start generation number (206) <the current generation number (207), and the end. Since generation number = ∞ is satisfied, it is determined as a save target (S531). Next, the storage management unit 131 does not change the start generation number in the effective generation number range of the current generation record, and sets a last generation number = the last backup generation number (206), whereby a (1) is past Saved as a generation record (S532) (S711). Next, the storage management unit 131 creates a new current generation record of the file A, and sets the valid generation number range to start generation number = current generation number (207) and end generation number = ∞ (S533). .

  At this point, it is assumed that the generation management table 141 has the contents shown in FIG.

  Next, at time t (7), the storage management unit 131 performs a snapshot creation process for the generation number (207). Here, the storage management unit 131 creates a new record in the generation management table 141, and sets the time t (7) and the generation number (207) to perform a namespace snapshot creation process. In addition, the storage management unit 131 performs the data snapshot creation process (S613) of a (2) and the data snapshot creation process (S614) of c (1).

  FIG. 13 is a table showing a second example of the contents of the generation management table 141 according to this embodiment. At this point, the generation management table 141 is added with the record of the generation number (207) to the contents of FIG.

  Next, the namespace information table update process when the file D is created as the content d (1) will be described. At this time, the final backup generation number = 207 and the current generation number = 208 (S511). Next, since the event data is file creation (S512), the storage management unit 131 newly creates a record of file D in the name space information table 142, and within the valid generation number range, start generation number = current generation number. (208), the end generation number = ∞ is set (S513).

  Next, the namespace information table update process when the file A is changed from content a (2) to a (3) will be described. At this time, the final backup generation number = 207 and the current generation number = 208 (S511). Next, since the event data is a file change (S512), the storage management unit 131 ends the record of the current generation of the file A in the name space information table 142 with the start generation number (207) <the current generation number (208). Since generation number = ∞ is satisfied, it is determined as a save target (S531). Next, the storage management unit 131 does not change the start generation number in the valid generation number range of the current generation record, and sets a (2) in the past by setting the end generation number = the last backup generation number (207). Saved as a generation record (S532) (S712). Next, the storage management unit 131 creates a new current generation record of file A, and sets the valid generation number range to start generation number = current generation number (208) and end generation number = ∞ (S533). .

  At this time, it is assumed that the name space information table 142 has the contents of FIG. 9, and the record of the file name “x001” in FIG. 9 indicates b (1).

  Next, the namespace information table update process when the file B is changed from content b (1) to b (2) will be described. The change from b (1) to b (2) assumes that the file name has been changed from “x001” to “YY01”.

  At this time, the final backup generation number = 207 and the current generation number = 208 (S511). Next, since the event data is a file change (S512), the storage management unit 131 indicates that the current generation record of the file B in the name space information table 142 is the start generation number (206) <the current generation number (208), and the end. Since generation number = ∞ is satisfied, it is determined as a save target (S531). Next, the storage management unit 131 does not change the start generation number in the valid generation number range of the current generation record, and sets b (1) in the past by setting end generation number = last backup generation number (207). Saved as a generation record (S532) (S713). Next, the storage management unit 131 creates a new current generation record of file B, and sets the valid generation number range to start generation number = current generation number (208) and end generation number = ∞ (S533). .

  FIG. 14 is a table showing a second example of the contents of the namespace information table 142 according to the present embodiment. At this point, the name space information table 142 has the contents shown in FIG. That is, the end generation number (207) is set to the record with the file name “x001” by the above-described processing S532 (third record including the underlined portion). Further, through the above-described processing S533, a record with the file name “YY01” is added (the fifth record indicated by an underline), and a start generation number (208) and an end generation number (∞) are set.

  Next, the namespace information table update process when the file A is changed from the contents a (3) to a (4) will be described. At this time, the final backup generation number = 207 and the current generation number = 208 (S511). Next, since the event data is a file change (S512), the storage management unit 131 satisfies that the current generation record of the file A in the name space information table 142 satisfies start generation number <current generation number, end generation number = ∞. Since it is not, it is determined that it is not a save target (S531). Next, the storage management unit 131 updates the information of the current generation record according to the event data, but does not update the valid generation number range (S534).

  Next, the namespace information table update process when the file D is changed from content d (1) to d (2) will be described. At this time, the final backup generation number = 207 and the current generation number = 208 (S511). Next, since the event data is a file change (S512), the storage management unit 131 satisfies that the current generation record of the file D in the namespace information table 142 satisfies start generation number <current generation number, end generation number = ∞. Since it is not, it is determined that it is not a save target (S531). Next, the storage management unit 131 updates the information of the current generation record according to the event data, but does not update the valid generation number range (S534).

  Next, the namespace information table update process when file C is deleted will be described. At this time, the final backup generation number = 207 and the current generation number = 208 (S511). Next, since the event data is file deletion (S512), the storage management unit 131 indicates that the current generation record of the file C in the name space information table 142 is the start generation number (207) <the current generation number (208), and the end. Since generation number = ∞ is satisfied, it is determined as a save target (S531). Next, the storage management unit 131 does not change the start generation number in the effective generation number range of the current generation record, and sets c (1) in the past by setting the end generation number = the last backup generation number (207). Saved as a generation record (S532) (S714).

  Next, restore processing for restoring from backup will be described.

  A case where restoration is performed from a backup of a specific generation number in the generation management table 141 will be described. FIG. 15 is a table showing a third example of the contents of the generation management table 141 according to this embodiment. In this figure, it is assumed that the generation number 218 (the fifth record indicated by the underline) is designated as the target generation number that is the generation number to be restored. At this time, the storage management unit 131 extracts a record whose target generation number is included in the valid generation number range from the records in the namespace information table 142, and sets a file corresponding to the extracted record as a restore target file. . FIG. 16 is a table showing a third example of the contents of the namespace information table 142 according to the present embodiment. In this figure, the second and third records (indicated by underline) are extracted as records in which the effective generation number range includes the target generation number (218).

  According to the present embodiment, it is possible to create a backup as a snapshot of the HSM system at a certain point in time and perform generation management. Further, since the creation of the namespace snapshot is only the process of adding the generation information to the generation management table, the creation of the namespace snapshot can be completed instantaneously. Further, by including the valid generation number range in the name space information table 142 and centrally managing all generations, it is possible to easily and quickly specify the target generation and target file for restoration.

  Further, the HSM control device according to the present embodiment can be easily applied to a server, and the performance of the server can be further improved.

  Furthermore, it is possible to provide a program for executing the above steps in a computer constituting the HSM control apparatus as an HSM control program. The above-described program can be executed by a computer constituting the HSM control device by storing the program in a computer-readable recording medium. Here, examples of the recording medium readable by the computer include an internal storage device such as a ROM and a RAM, a portable storage such as a CD-ROM, a flexible disk, a DVD disk, a magneto-optical disk, and an IC card. It includes a medium, a database holding a computer program, another computer and its database, and a transmission medium on a line.

(Supplementary note 1) An HSM control program for causing a computer to execute control of an HSM having a primary storage and a secondary storage,
A generation information creation step for creating generation information that is information including the generation number of the backup for each backup of the HSM;
An effective generation number range indicating a range of generation numbers in which the information on the name space is valid using the name space information which is information on the name space for each file in the HSM and the generation number created in the generation information creating step A history management step for managing a name space information history as an HSM control program.
(Appendix 2) In the HSM control program described in Appendix 1,
When an update of the namespace information in the HSM file system is detected, the history management step updates the namespace information history corresponding to the update target file that is a file for which the namespace information is updated. An HSM control program characterized by the above.
(Appendix 3) In the HSM control program described in Appendix 2,
When the update of the namespace information is creation of the update target file, the history management step newly creates a current generation namespace information history of the update target file, and sets the valid generation number range to the current generation and later. An HSM control program.
(Appendix 4) In the HSM control program described in Appendix 2 or Appendix 3,
When the update of the namespace information is the first update after the backup of the update target file, the history management step performs the final backup of the end point of the valid generation number range in the current generation namespace information history of the update target file. An HSM control program, wherein a new name space information history is created for the file to be updated, and the valid generation number range of the name space information history is set to the current generation or later.
(Supplementary note 5) In the HSM control program according to any one of supplementary notes 1 to 4,
The history management step further extracts the namespace information history in which the generation number designated from the outside is within the valid generation number range, and a file corresponding to the namespace information history obtained by the extraction is restored. An HSM control program which is output as a file.
(Supplementary note 6) In the HSM control program according to any one of supplementary notes 1 to 5,
The generation information creating step further copies a file updated after the previous backup from the primary storage to the secondary storage.
(Supplementary note 7) In the HSM control program according to any one of supplementary notes 1 to 6,
The HSM control program, wherein the backup is a snapshot.
(Supplementary note 8) An HSM control device for controlling an HSM having a primary storage and a secondary storage,
A generation information creation unit that creates generation information that is information including the generation number of the backup for each backup of the HSM;
An effective generation number range indicating a range of generation numbers in which the information on the name space is valid using the name space information that is information on the name space for each file in the HSM and the generation number created by the generation information creating unit And a history management unit that manages the information as a namespace information history.
(Supplementary note 9) In the HSM control device according to supplementary note 8,
When the update of the namespace information in the HSM file system is detected, the history management unit updates the namespace information history corresponding to the update target file that is the target file of the namespace information update. An HSM control device characterized by the above.
(Supplementary note 10) In the HSM control device according to supplementary note 9,
When the update of the namespace information is creation of the update target file, the history management unit newly creates a current generation namespace information history of the update target file, and sets the valid generation number range to the current generation and later. An HSM control device.
(Supplementary Note 11) In the HSM control device according to Supplementary Note 9 or Supplementary Note 10,
When the update of the namespace information is the first update after the backup of the update target file, the history management unit performs the final backup of the end point of the valid generation number range in the current generation namespace information history of the update target file An HSM control apparatus, wherein a new name space information history is created for the update target file, and a valid generation number range of the name space information history is set to the current generation or later.
(Supplementary note 12) In the HSM control device according to any one of supplementary notes 8 to 11,
The history management unit further extracts the namespace information history whose generation number designated from the outside is within the valid generation number range, and restores a file corresponding to the namespace information history obtained by the extraction to be restored. An HSM control device that outputs as a file.
(Supplementary note 13) In the HSM control device according to any one of supplementary notes 8 to 12,
The generation information creating unit further copies a file updated after the previous backup from the primary storage to the secondary storage.
(Supplementary note 14) In the HSM control device according to any one of supplementary notes 8 to 13,
The HSM control apparatus, wherein the backup is a snapshot.
(Supplementary note 15) An HSM control method for controlling an HSM having a primary storage and a secondary storage,
A generation information creation step for creating generation information that is information including the generation number of the backup for each backup of the HSM;
An effective generation number range indicating a range of generation numbers in which the information on the name space is valid using the name space information which is information on the name space for each file in the HSM and the generation number created in the generation information creating step And a history management step for managing as a namespace information history.
(Supplementary Note 16) In the HSM control method according to Supplementary Note 15,
When an update of the namespace information in the HSM file system is detected, the history management step updates the namespace information history corresponding to the update target file that is a file for which the namespace information is updated. An HSM control method characterized by the above.
(Supplementary note 17) In the HSM control method according to supplementary note 16,
When the update of the namespace information is creation of the update target file, the history management step newly creates a current generation namespace information history of the update target file, and sets the valid generation number range to the current generation and later. An HSM control method characterized by:
(Supplementary note 18) In the HSM control method according to supplementary note 16 or supplementary note 17,
When the update of the namespace information is the first update after the backup of the update target file, the history management step performs the final backup of the end point of the valid generation number range in the current generation namespace information history of the update target file. The HSM control method is characterized in that a new name space information history is created for the update target file and the effective generation number range of the name space information history is set to the current generation or later.
(Supplementary note 19) In the HSM control method according to any one of supplementary note 15 to supplementary note 18,
The history management step further extracts the namespace information history in which the generation number designated from the outside is within the valid generation number range, and a file corresponding to the namespace information history obtained by the extraction is restored. An HSM control method characterized by outputting as a file.
(Supplementary note 20) In the HSM control method according to any one of supplementary note 15 to supplementary note 19,
The generation information creating step further includes copying a file updated after the previous backup from the primary storage to the secondary storage.

It is a block diagram which shows an example of a structure of the HSM apparatus which concerns on the base technology 1. FIG. 10 is a flowchart showing an example of an operation of a file information acquisition process according to the base technology 1. It is a figure which shows an example of the hierarchical structure of the directory in the name space which concerns on the base technology 1. FIG. 10 is a flowchart showing an example of an operation of a file information acquisition process according to the base technology 1. 7 is a flowchart illustrating an example of an operation of event data reflection processing according to the base technology 1. 10 is a flowchart showing an example of an operation of a migration determination process according to the base technology 1. It is a block diagram which shows an example of a structure of the HSM system which concerns on this Embodiment. It is a table | surface which shows the 1st example of the content of the generation management table 141 which concerns on this Embodiment. It is a table | surface which shows the 1st example of the content of the name space information table 142 which concerns on this Embodiment. It is a flowchart which shows an example of the 1st operation | movement of the name space information table update process which concerns on this Embodiment. It is a flowchart which shows an example of the 2nd operation | movement of the namespace information table update process which concerns on this Embodiment. It is a sequence diagram which shows the specific example of the generation management which concerns on this Embodiment. It is a table | surface which shows the 2nd example of the content of the generation management table 141 which concerns on this Embodiment. It is a table | surface which shows the 2nd example of the content of the name space information table 142 which concerns on this Embodiment. It is a table | surface which shows the 3rd example of the content of the generation management table 141 which concerns on this Embodiment. It is a table | surface which shows the 3rd example of the content of the name space information table 142 which concerns on this Embodiment.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Primary storage, 2 Secondary storage, 3 Server, 11 Application part, 12 File system control part, 13 Name space replication part, 14 Name space tracking part, 15 Name space replication DB, 16 Migration determination part, 21 Event data recording Part, 102 operation server, 103 HSM control server, 131 storage management part, 132 storage management DB, 133 storage management DB backup, 141 generation management table, 142 namespace information table.

Claims (5)

An HSM control program for causing a computer to execute control of an HSM having a primary storage and a secondary storage,
A generation information creation step for creating generation information that is information including the generation number of the backup for each backup of the HSM;
An effective generation number range indicating a range of generation numbers in which the information on the name space is valid using the name space information which is information on the name space for each file in the HSM and the generation number created in the generation information creating step A history management step for managing a name space information history as an HSM control program. The HSM control program according to claim 1,
When an update of the namespace information in the HSM file system is detected, the history management step updates the namespace information history corresponding to the update target file that is a file for which the namespace information is updated. An HSM control program characterized by the above. In the HSM control program according to claim 1 or 2,
The history management step further extracts the namespace information history in which the generation number designated from the outside is within the valid generation number range, and a file corresponding to the namespace information history obtained by the extraction is restored. An HSM control program which is output as a file. An HSM controller for controlling an HSM having a primary storage and a secondary storage,
A generation information creation unit that creates generation information that is information including the generation number of the backup for each backup of the HSM;
An effective generation number range indicating a range of generation numbers in which the information on the name space is valid using the name space information that is information on the name space for each file in the HSM and the generation number created by the generation information creating unit And a history management unit that manages the information as a namespace information history. An HSM control method for controlling an HSM having a primary storage and a secondary storage,
A generation information creation step for creating generation information that is information including the generation number of the backup for each backup of the HSM;
An effective generation number range indicating a range of generation numbers in which the information on the name space is valid using the name space information which is information on the name space for each file in the HSM and the generation number created in the generation information creating step And a history management step for managing as a namespace information history.

Images