JP2005084746A - Data management device and its control method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To easily execute the reference or edition of link data in a file system at the time of managing a file system prepared in a plurality of recording media. <P>SOLUTION: At the time of managing a file system prepared in the plurality of recording media, when the link file of a file system prepared in the first recording medium is stored in a freely attachable/detachable second recording medium, the link file is duplicated to the predetermined position of the file system in the file recording medium so that even when the second recording medium is not mounted, the reference or edition of the link file can be easily executed by using the duplicated link file. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention provides a plurality of detachable recordings of link data (for example, office document files, image files, moving image files, audio files, etc.) comprising data and link information indicating the storage location of link destination data related to the data. The present invention relates to a data management apparatus managed by a medium, its control method, and a control program.

  Conventionally, in a data management apparatus that manages data stored in a plurality of recording media (sometimes referred to as storage media), as disclosed in JP-A-4-257742, volume image files of a plurality of recording media are stored. It is created on a fixed disk and managed based on the volume image file (Patent Document 1).

  Also, as disclosed in JP-A-9-293005, directory information on a plurality of recording media is stored as a library file on a fixed disk and managed based on the library file (Patent Document 2).

Further, in JP-A-9-44394, a catalog file is created from each data of a plurality of recording media on a fixed disk, managed based on the catalog file, and read data is cached on the fixed disk ( Patent Document 3). Note that the cache is, for example, that data stored in a low-speed recording medium accessed in advance is stored in a recording medium (for example, a fixed disk) that can be accessed at a higher speed. After that, it means that it can be pulled out quickly.
JP-A-4-257742 JP-A-9-293005 JP-A-9-44394

  However, in the conventional data management apparatus described above, when link data including link information indicating data is present across a plurality of recording media, in order to refer to and edit the link destination data indicated by the link data, In Japanese Laid-Open Patent Publication No. 9-293005, a recording medium in which link data is stored must be inserted, and the link destination recording medium must be inserted after confirming the link destination, which is troublesome. It was. In Japanese Patent Laid-Open No. 4-257942, it is not necessary to repeatedly insert a recording medium. However, since the volume image file increases as the number of recording media increases, an enormous storage area is required in the data management apparatus. There was a problem of becoming.

  In Japanese Patent Laid-Open No. 9-44394, if no data remains on the cache, it is necessary to insert both the link source and link destination recording media as in Japanese Patent Laid-Open No. 9-293005, In order to increase the hit rate of the cache, the data of all the recording media is cached in the fixed disk of the data management apparatus. Therefore, as in JP-A-4-257742, the fixed disk of the data management apparatus has a huge storage capacity. There was a drawback of requiring an area.

  The present invention has been made starting from solving the above-described problems of the prior art, and its purpose is to store a large amount of memory when managing file systems created on a plurality of recording media. It is an object of the present invention to provide a data management apparatus and a control method therefor that can easily refer to and edit link data in a file system without requiring an area.

  In order to achieve the above object, a data management apparatus according to an embodiment of the present invention has the following arrangement. In other words, the data management apparatus manages file systems created on a plurality of recording media, and the link destination file specified by the file system created on the first recording medium is detachable second Determining means for determining whether the file is stored in a recording medium; and when the determining means determines that the linked file is stored in the second recording medium, the linked file is Duplicating means for duplicating to a predetermined position of the file system on the first recording medium.

  Here, for example, when the link destination file specified by the file system created on the first recording medium is read, the link destination file has already been copied to the first recording medium by the duplicating means. Detecting means for detecting whether or not the duplicated link destination file is detected on the first recording medium by the detecting means, and reading means for reading the duplicated file. It is preferable to further provide.

  Here, for example, a recording medium detection unit for detecting whether or not the link destination file can be read from the second recording medium is further provided, and the link medium file can be read by the recording medium detection unit. When it is determined that, the duplicating unit preferably duplicates the link destination file to the predetermined position.

  Here, for example, a link destination file stored in the second recording medium, a comparison unit that compares the update state of the file copied to the predetermined position, and a file that has not been updated by the comparison unit are included. It is preferable to further include an updating unit that updates an unupdated file with an updated file when detected.

  Here, for example, when both the files are updated by the comparison means, it is preferable to further include a selection means for selecting any one of the files.

  Here, for example, the duplicating unit converts the file size of the linked file before creating the duplicated file from the linked file stored in the second recording medium. It is preferable that the duplicating unit duplicates the file changed by the converting unit to the predetermined position.

  Here, for example, it is preferable that the link destination file is an image file, and the changing unit reduces the file size of the image file.

  In order to achieve the above object, a data management apparatus control method according to an embodiment of the present invention has the following arrangement. That is, a control method of a data management apparatus that manages file systems created on a plurality of recording media, wherein a link destination file specified by the file system created on the first recording medium is detachable A determination step of determining whether or not the file is stored in the second recording medium; and if it is determined by the determination step that the file of the link destination is stored in the second recording medium, the link destination And a duplication step of duplicating the file at a predetermined position of the file system on the first recording medium.

  Here, for example, when the link destination file specified by the file system created on the first recording medium is read, the link destination file is already copied to the first recording medium by the duplication step. A detection step for detecting whether or not the duplicated link destination file is detected on the first recording medium by the detection step, and a reading step for reading the duplicated file. It is preferable to further provide.

  In order to achieve the above object, a control program for controlling a data management apparatus according to an embodiment of the present invention has the following arrangement. That is, a control program for controlling a data management apparatus that manages file systems created on a plurality of recording media, and a link destination file specified by the file system created on the first recording medium is attached / detached When it is determined by the determination step that the link destination file is stored in the second recording medium, the program code of the determination step for determining whether or not the file is stored in a free second recording medium. And a program code of a duplication process for duplicating the link destination file to a predetermined position of the file system in the first recording medium.

  Here, for example, when the link destination file specified by the file system created on the first recording medium is read, the link destination file is already copied to the first recording medium by the duplication step. A program code for a detection step for detecting whether or not the file is copied, and reading the duplicated link file when the duplicated link destination file is detected on the first recording medium by the detection step It is preferable to further include program code for the process.

  According to the present invention, when managing file systems created on a plurality of recording media, data that can easily refer to and edit link data in the file system without requiring a huge storage area. A management apparatus and its control method can be provided.

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

<First Embodiment>
[Data management device: Fig. 1]
Hereinafter, the data management apparatus according to the first embodiment of the present invention will be described with reference to FIGS.

  FIG. 1 is a block diagram of a data management apparatus 100 in the present embodiment.

  In FIG. 1, 100 is a data management device, 104 is a control unit such as a CPU, 103 is a display unit such as a CRT display, liquid crystal display, and LED, 105 is an operation unit such as a keyboard, mouse, and buttons, 106 is a hard disk drive, ROM The storage unit 106 stores various programs such as a replication processing control program, which will be described later, and the control unit 104 controls each unit of the data management apparatus 100 based on these programs. However, the replication process described later is performed.

  Reference numerals 101-1 and 101-2 denote removable media (removable recording media: first and second recording media) that are exchangeable recording media such as a removable hard disk drive and a magneto-optical disk, Reference numeral 102-2 denotes a removable media interface (IF) unit which is a physical and electrical interface for the control unit 104 to read and write data stored in the removable media 101-1 and 101-2. The first recording medium is not limited to a removable medium, and a fixed recording medium such as a hard disk may be used, for example.

[Overview of replication: FIGS. 2A and 2B]
2A and 2B are diagrams for explaining an example of an outline of replication by the data management apparatus according to the present embodiment. FIG. 2A shows an example of removable media 101-1 and 101-2 (first and second recording media) before link creation processing (before duplication) in FIG. 4 to be described later. An example of the removable media 101-1 and 101-2 after link creation processing (after copying) in FIG. 4 to be described later is shown.

  In FIG. 2A (before link creation processing: before duplication), 201-1 and 201-2 are root directories of the removable media 101-1 and 101-2, respectively, and 202-1 and 202-2 are root directories 201-, respectively. , 201-2 are the files stored under the root directories 201-1 and 201-2, and 203-1 is the file 202-. 2 (link destination file stored in the second recording medium) is a link file (link source file stored in the first recording medium), and 203-2 is a link file for the directory 204-1. It is.

  In FIG. 2B, the following is added by the link creation processing (duplication) of FIG. That is, 205-1 and 205-2 are copy storage directories for storing a copy, and 206-1 and 206-2 are link destination media directories corresponding to the removable media 101-1 and 101-2, respectively. 207 is a copy of the file 202-2, 208 is a copy of the directory 204-1, and these are added to FIG. 2A by the link creation processing of FIG. Here, the directory 206-1 and the copy 207 are created based on the link file 203-1, and the directory 206-2 and the copy 208 are created based on the link file 203-2. 4 will be described.

[Summary of link information: Fig. 3]
FIG. 3 is a diagram illustrating an example of an outline of link information of the data management apparatus according to the present embodiment.

  In FIG. 3, 301 is a media ID which is identification information uniquely assigned to the removable medium 101-1, and 302 is a media type indicating whether or not the removable medium 101-1 is removable (detachable). ID is a medium ID of a link destination of the link file 203-1, 304 is a directory path indicating a position in the link destination medium of the link file 203-1, and 305 is a link file 203. -1 is the name of the link destination file name, directory name, etc., and 306 is the media ID of the media corresponding to the link destination media directory 206-1.

  2A, 2B, and 3 show an example of the directory structure, and the present invention is not limited to this structure.

[Link file creation processing: Fig. 4]
Next, with reference to FIGS. 4 and 5, the link file creation process 400 and the link file read process 500 will be described using the data management apparatus 100 according to the present embodiment described above as an example with reference to FIGS. 4 and 5 are executed by the control unit 104 while controlling each unit based on a control program stored in the storage unit 106.

  First, the link file creation process 400 of FIG. 4 will be described. In step S410, when a link file creation operation is performed from the operation unit 105, link information including a link destination medium ID 303, directory path 304, and name 305 is read based on the operation input.

  Next, in step S420, the read media ID 303 is different from the media ID 301 of the removable media 101-1 in which the link file 203-1 is stored, and the media type ID 302 or the media (not shown) of the removable media 101-2. If the type ID is “removable”, the process proceeds to step S421.

  In step S421, the file 202-2 which is the link destination data indicated by the link information is read. Next, in step S422, based on the media ID 303 and the directory path 304, the duplication position, in this case, the link destination media directory 206-1. Next, in step S423, a copy 207 of the file 202-2 is created. Next, in step S430, the link file 203 having media information including the media ID 303, the directory path 304, and the name 305 is obtained. -1 is created.

  On the other hand, if the media ID 303 is the same as the media ID 301 in step S420, or if the media type ID 302 and the media type ID (not shown) of the removable media 101-2 are not "removable", nothing is done and the process proceeds to step S430. The link file 203-1 is created directly.

[Link file read processing: Fig. 5]
Next, the read process 500 of the link file created by the link file creation process 400 described above will be described with reference to FIG. In the following description, the same reference numerals are assigned to processes common to those in FIG.

  First, when a link file read operation is performed from the operation unit 105 in step S410, link information including a link destination medium ID 303, directory path 304, and name 305 is read based on the operation input. In step S420, the read media ID 303 is different from the media ID 301 of the removable media 101-1 in which the link file 203-1 is stored, and the media type ID 302 or the media type ID (not shown) of the removable media 101-2 is “ If it is “removable”, the process proceeds to step S422.

  In step S422, the copy position, in this case, the path to the link destination media directory 206-1, is derived based on the media ID 303 and the directory path 304. Next, in step S520, the link destination data is copied to the copy position. If 207 exists, the process proceeds to step S530, and after reading the duplicate 207, the process proceeds to step S540, and the series of operations is completed.

  In step S520, if the link destination data copy 207 does not exist at the copy position, the process advances to step S421-2 to read the file 202-2 which is the link destination data indicated by the link information, and then step S423. The process proceeds to step S540 after creating the copy 207 of the file 202-2 at the copy position, and the series of operations is completed.

  On the other hand, in step S420, if the media ID 303 is the same as the media ID 301, or if the media type ID 302 and the media type ID (not shown) of the removable media 101-2 are not "removable", the process proceeds to step S421-1 After reading the file 202-2 which is the link destination data indicated by the information, the process proceeds to step S540, and the series of operations is completed.

  In the present embodiment, as shown in FIG. 1, the case where there are two removable media and two removable media IF units has been described as an example. However, this is an example, and for example, the case where there are three or more each is also described above. The same processing as that described above can be performed. Further, the case where the removable medium is connected via the bus has been described, but the same applies even if the removable medium is connected via the network. Further, the same applies to a mode in which a plurality of removable media are linked with a changer in which a plurality of removable media are automatically replaced.

  In FIG. 1, the case where there are two removable media and two removable media IF units has been described as an example. However, one removable media and one removable media IF unit are used instead of the other removable media and removable media IF units. The configuration may be a fixed disk and a fixed desk IF unit. In this case, the file stored in the fixed disk may be supplied via, for example, a removable medium.

<Second Embodiment>
Next, a data management apparatus 1000 according to the second embodiment of the present invention will be described with reference to FIGS. The configuration of the data management device 1000 is the same as that of the data management device 100 described in the first embodiment except for the link file read processing 600 described below. Therefore, in the following description, since the description of FIGS. 1 to 4 is the same as that of the first embodiment, the description thereof will be omitted, and the link file read processing 600 in which the second embodiment is different from the first embodiment. Only explained.

  First, in step S410 of the link reading process 600 of FIG. 6, when a link file reading operation is performed from the operation unit 105, link information including a link destination medium ID 303, directory path 304, and name 305 is obtained based on the operation input. Next, the process proceeds to step S420, where the read media ID 303 is different from the media ID 301 of the removable medium 101-1 in which the link file 203-1 is stored, and the media type ID 302 or the removable medium 101- is stored. If the media type ID (not shown) of 2 is “removable”, the process proceeds to step S422.

  In step S422, when the copy position, in this case the path to the link destination media directory 206-1, is derived based on the media ID 303 and the directory path 304, the process proceeds to step S520, and the link destination data is transferred to the copy position. If the copy 207 exists, the process proceeds to step S610. If the copy destination data copy 207 does not exist at the copy position in step S520, the process proceeds to step S421-2.

  If it is determined in step S610 that the removable medium 101-2 that is the link destination medium is not readable, the process proceeds to step S530, the duplicate 207 is read, the process proceeds to step S540, and the series of operations is terminated. If the removable medium 101-2 as the link destination medium is readable, the process proceeds to step S421-2.

  Next, in step S421-2, the file 202-2 which is the link destination data indicated by the link information is read. Next, in step S423, a duplicate 207 of the file 202-2 is created at the duplication position, and then the process proceeds to step S540. Proceed and finish a series of work.

  On the other hand, in step S420, if the media ID 303 is the same as the media ID 301, or if the media type ID 302 and the media type ID (not shown) of the removable media 101-2 are not "removable", the process proceeds to step S421-1 After reading the file 202-2 which is the link destination data indicated by the information, the process proceeds to step S540, and a series of work is completed.

  In this embodiment, as shown in FIG. 1, the case where there are two removable media and two removable media IF units has been described as an example. However, this is an example, and for example, the case where there are three or more each is also described above. Processing similar to the processing can be performed. Further, the case where the removable medium is connected via the bus has been described, but the same applies even if the removable medium is connected via the network. Further, the same applies to a mode in which a plurality of removable media are linked with a changer in which a plurality of removable media are automatically replaced.

  In FIG. 1, the case where there are two removable media and two removable media IF units has been described as an example. However, one removable media and one removable media IF unit are used instead of the other removable media and removable media IF units. The configuration may be a fixed disk and a fixed desk IF unit. In this case, the file stored in the fixed disk may be supplied via, for example, a removable medium.

<Third Embodiment>
Next, a data management apparatus 2000 according to the third embodiment of the present invention will be described with reference to FIGS. 1 to 4 and FIGS. The data management apparatus 2000 is the same as the data management apparatus 100 described in the first embodiment except for a link file read process 700 and a link update process 800 described below. Therefore, in the following description, since the description of FIGS. 1 to 4 is the same as that of the first embodiment, the description is omitted, and the third embodiment is different from the first embodiment in the link file read processing 700 and Only the link update process 800 will be described.

  First, in step S410 of the link reading process 700 in FIG. 7, when a link file reading operation is performed from the operation unit 105, link information including a link destination medium ID 303, directory path 304, and name 305 is obtained based on the operation input. Next, the process proceeds to step S420, where the read media ID 303 is different from the media ID 301 of the removable medium 101-1 in which the link file 203-1 is stored, and the media type ID 302 or the removable medium 101- is stored. If the media type ID (not shown) of 2 is “removable”, the process proceeds to step S422.

  In step S422, when the copy position, in this case the path to the link destination media directory 206-1, is derived based on the media ID 303 and the directory path 304, the process proceeds to step S520, and the link destination data is transferred to the copy position. If the copy 207 exists, the process proceeds to step S610. If the copy destination data copy 207 does not exist at the copy position in step S520, the process proceeds to step S421-2.

  If it is determined in step S610 that the removable medium 101-2 that is the link destination medium is not readable, the process proceeds to step S530, the duplicate 207 is read, the process proceeds to step S540, and the series of operations is terminated. If the removable medium 101-2 as the link destination medium is readable, the process proceeds to the link update process 800 shown in FIG.

  On the other hand, in step S421-2, the file 202-2 which is the link destination data indicated by the link information is read. Next, in step S423, a copy 207 of the file 202-2 is created at the copy position, and then the process proceeds to step S540. A series of work is completed.

  On the other hand, in step S420, if the media ID 303 is the same as the media ID 301, or if the media type ID 302 and the media type ID (not shown) of the removable media 101-2 are not "removable", the process proceeds to step S421-1 After reading the file 202-2 which is the link destination data indicated by the information, the process proceeds to step S540, and a series of work is completed.

  In this embodiment, as shown in FIG. 1, the case where there are two removable media and two removable media IF units has been described as an example. However, this is an example, and for example, the case where there are three or more each is also described above. Processing similar to the processing can be performed. Further, the case where the removable medium is connected via the bus has been described, but the same applies even if the removable medium is connected via the network. Further, the same applies to a mode in which a plurality of removable media are linked with a changer in which a plurality of removable media are automatically replaced.

  In FIG. 1, the case where there are two removable media and two removable media IF units has been described as an example. However, one removable media and one removable media IF unit are used instead of the other removable media and removable media IF units. The configuration may be a fixed disk and a fixed desk IF unit. In this case, the file stored in the fixed disk may be supplied via, for example, a removable medium.

[Link update processing: FIG. 8]
FIG. 8 is a flow diagram of the link file update process of the data management apparatus 2000 in the present embodiment.

  First, in the link update processing 800, in step S810, the update status of the file 202-2 and the copy 207 as link destination data, for example, the update date and time of the file system, archive information, etc. are read, and then the process proceeds to step S820. If only 202-2 has been updated, the process proceeds to step S421, the file 202-2 is read, and then the process proceeds to step S821, where the copy 207 is updated with the contents of the file 202-2, and then a series of operations is performed. finish.

  On the other hand, if only the file 202-2 has not been updated in step S820, the process proceeds to step S830. If only the copy 207 has been updated, the process proceeds to step S530-2, and the copy 207 is read from the copy position. In step S831, the file 202-2 is updated with the contents of the copy 207, and the series of operations is terminated.

  In step S830, if only the copy 207 has not been updated, the process proceeds to step S840. If both have been updated, the process proceeds to step S841, and either one is displayed by the user via the display unit 103 or the operation unit 105. Upon receiving an input as to whether to select data, the process proceeds to step S842, where the selected data is read out, and then proceeds to step S843, the other is updated with the read data, and the series of operations is terminated.

  On the other hand, if neither the file 202-2 nor the copy 207 has been updated in step S840 (No in steps S820, 830, and 840), the process proceeds to step S530-1 and the copy 207 is read from the copy position. A series of work is completed.

    In this embodiment, as shown in FIG. 1, the case where there are two removable media and two removable media IF units has been described as an example. However, this is an example, and for example, the case where there are three or more each is also described above. Processing similar to the processing can be performed. Further, the case where the removable medium is connected via the bus has been described, but the same applies even if the removable medium is connected via the network. Further, the same applies to a mode in which a plurality of removable media are linked with a changer in which a plurality of removable media are automatically replaced.

  In FIG. 1, the case where there are two removable media and two removable media IF units has been described as an example. However, one removable media and one removable media IF unit are used instead of the other removable media and removable media IF units. The configuration may be a fixed disk and a fixed desk IF unit. In this case, the file stored in the fixed disk may be supplied via, for example, a removable medium.

<Fourth Embodiment>
Next, a data management device 3000 according to the fourth embodiment of the present invention will be described with reference to FIGS. In the following description, only the differences of the fourth embodiment from the data management apparatus 100 of the first embodiment will be described, and descriptions of the overlapping points will be omitted.

  FIG. 9 is a block diagram of the data management device 3000 in the present embodiment. In FIG. 9, reference numeral 901 denotes a data conversion unit that performs data conversion processing, and other configurations are the same as the configuration of the data management apparatus 100 shown in FIG. I will omit it.

  FIG. 10 is a diagram illustrating an outline of replication of the data management device 3000 according to this embodiment. In FIG. 10, reference numeral 1007 denotes a copy obtained by converting the file 202-2 by the data conversion unit 901. Since the other configuration is the same as that in FIG. 2B, the same reference numerals are given and description thereof will be omitted. .

  FIG. 11 is a diagram for explaining the outline of the operation of the data conversion unit 901. In FIG. 11, when the file 202-2 has, for example, 2048 × 1536 pixels, the data conversion unit 901 has, for example, 640 × 480 pixels in advance before copying the file 202-2 as necessary. A conversion process for reducing the size of the file 1007 is performed, and the reduced file 1007 is copied and stored in a predetermined storage position of the copy storage directory 1 shown in FIG. Here, FIG. 10 shows an example of the directory structure, and the present invention is not limited to this structure.

  The file size is not limited to the above example, and for example, known compression / conversion may be used. For example, a bitmap image file may be converted to JPEG format, a digital video (DV) format or a moving image file in MPEG2 format may be converted into MPEG4 format, or other general files may be compressed in ZIP or LZH format. Good.

  In the present embodiment, as shown in FIG. 9, the case where there are two removable media and two removable media IF units has been described as an example. However, this is an example, and for example, the case where there are three or more each is also described above. Processing similar to the processing can be performed. Further, the case where the removable medium is connected via the bus has been described, but the same applies even if the removable medium is connected via the network. Further, the same applies to a mode in which a plurality of removable media are linked with a changer in which a plurality of removable media are automatically replaced.

  In FIG. 9, the case where there are two removable media and two removable media IF units has been described as an example. However, one removable media and one removable media IF unit are used instead of the other removable media and removable media IF units. The configuration may be a fixed disk and a fixed desk IF unit. In this case, the file stored in the fixed disk may be supplied via, for example, a removable medium.

  The present invention can take the form of, for example, an apparatus, a method, a program, or a recording medium. Specifically, a plurality of devices (for example, a host computer, an interface device, a reader, a printer, etc.) The present invention may be applied to a system configured from the above, or may be applied to an apparatus (for example, a copier, a facsimile machine, etc.) including one device.

  Also, an object of the present invention is to supply a recording medium (or storage medium) in which a program code of software that realizes the functions of the above-described embodiments is recorded to a system or apparatus, and a computer (or CPU or CPU) of the system or apparatus. Needless to say, this can also be achieved when the MPU) reads and executes the program code stored in the recording medium.

  In this case, the program code itself read from the recording medium realizes the functions of the above-described embodiment, and the recording medium storing the program code constitutes the present invention.

  Further, by executing the program code read by the computer, not only the functions of the above-described embodiments are realized, but also an operating system (OS) running on the computer based on the instruction of the program code. It goes without saying that a case where the function of the above-described embodiment is realized by performing part or all of the actual processing and the processing is included.

  Furthermore, after the program code read from the recording medium is written into a memory provided in a function expansion card inserted into the computer or a function expansion unit connected to the computer, the function is based on the instruction of the program code. It goes without saying that the CPU or the like provided in the expansion card or the function expansion unit performs part or all of the actual processing and the functions of the above-described embodiments are realized by the processing.

  When the present invention is applied to the above recording medium, the recording medium stores a program that realizes the processes shown in FIGS. 4 to 8 described above.

  As described above, in the data management device of the present invention, when the link file of the file system is not on the same recording medium, for example, the link file in the file system created on the first recording medium can be attached and detached. 2 is stored in the data management apparatus by copying the link file to a predetermined position in the file system of the first recording medium. Even if there is no link file, the link file in the file system can be easily referenced and edited by referring to the copied link file.

  Further, by comparing the update state of the link file stored in the detachable second recording medium and the link file copied to the first recording medium, if the update state is different, the link file is updated. You can easily update missing files. In addition, since the link file can be reduced before the duplication process, the link file can be stored in a small storage area.

It is a block diagram explaining the structure of the data management apparatus of 1st Embodiment. It is a figure explaining an example (before duplication) in the data management apparatus of 1st Embodiment. It is a figure explaining an example (after replication) in the data management apparatus of 1st Embodiment. It is a figure explaining the outline | summary of the link information in the 1st removable media in the data management apparatus of 1st Embodiment. It is a flowchart which shows the creation process of the link file of the data management apparatus in 1st Embodiment. It is a flowchart which shows the read process of the link file of the data management apparatus in 1st Embodiment. It is a flowchart which shows the read process of the link file of the data management apparatus in 2nd Embodiment. It is a flowchart which shows the read process of the link file of the data management apparatus in 3rd Embodiment. It is a flowchart which shows the detail of the link update process shown in FIG. It is a block diagram explaining the structure of the data management apparatus of 4th Embodiment. It is a figure explaining an example (after replication) in the data management apparatus of 4th Embodiment. It is a figure explaining the process of the data conversion part in the data management apparatus of 4th Embodiment.

Explanation of symbols

100: Data management device
101-1, 101-2 ... Removable media 102-1, 102-2 ... Removable media IF unit 202-1, 203-2 ... Link files 205-1, 205-2 ... Copy storage Directories 206-1, 206-2 ... Link destination media directory 207 ... Link destination file copy 208 ... Link destination directory copy 301 ... Media ID in removable media
302 ... Media type ID in removable media
303 ... Linked media ID in the link file
304: Link destination directory path in the link file 305 ... Link destination name in the link file 306 ... Link destination media ID in the link destination media directory
901: Data conversion unit 1007: Reduced image file

Claims (11)

A data management device for managing file systems created on a plurality of recording media,
Determining means for determining whether or not the link destination file specified by the file system created on the first recording medium is stored in the detachable second recording medium;
When the determination unit determines that the linked file is stored in the second recording medium, the copying unit copies the linked file to a predetermined position of the file system on the first recording medium. When,
A data management apparatus comprising: When the link destination file specified by the file system created on the first recording medium is read, whether or not the link destination file has already been duplicated on the first recording medium by the duplication unit. Detecting means for detecting;
Reading means for reading the duplicated file when the duplicated link destination file is detected on the first recording medium by the detection means;
The data management apparatus according to claim 1, further comprising: Recording medium detecting means for detecting whether the linked file can be read from the second recording medium;
The copy unit copies the link destination file to the predetermined position when the recording medium detection unit determines that the link destination file can be read. 2. The data management device according to 2. Comparing means for comparing the update status of the linked file stored in the second recording medium and the file copied to the predetermined position;
An update means for updating an unupdated file with an updated file when a file not updated by the comparison means is detected;
The data management device according to any one of claims 1 to 3, further comprising:   5. The data management apparatus according to claim 4, further comprising selection means for selecting one of the files when both files have been updated by the comparison means. The duplicating means further includes conversion means for changing the file size of the linked file before creating the duplicated file from the linked file stored in the second recording medium,
6. The data management apparatus according to claim 1, wherein the duplicating unit duplicates the file changed by the converting unit to the predetermined position.   The data management apparatus according to claim 6, wherein the link destination file is an image file, and the changing unit reduces a file size of the image file. A control method of a data management apparatus that manages file systems created on a plurality of recording media,
A determination step of determining whether a link destination file specified by the file system created on the first recording medium is stored in the detachable second recording medium;
When the determination step determines that the link destination file is stored in the second recording medium, the duplication step copies the link destination file to a predetermined position of the file system on the first recording medium. When,
A method for controlling a data management apparatus, comprising: When the link destination file specified by the file system created on the first recording medium is read, whether or not the link destination file has already been copied to the first recording medium by the duplication step. A detection process to detect;
A reading step of reading the duplicated file when the duplicated link destination file is detected on the first recording medium by the detection step;
The data management apparatus control method according to claim 8, further comprising: A control program for controlling a data management apparatus that manages file systems created on a plurality of recording media,
A program code of a determining step for determining whether or not a link destination file specified by the file system created on the first recording medium is stored in the detachable second recording medium;
When the determination step determines that the link destination file is stored in the second recording medium, the duplication step copies the link destination file to a predetermined position of the file system on the first recording medium. Program code,
A control program for controlling a data management apparatus comprising: When the link destination file specified by the file system created on the first recording medium is read, whether or not the link destination file has already been copied to the first recording medium by the duplication step. A detection process program code to be detected;
A program code of a reading step of reading the copied link file when the copied link destination file is detected on the first recording medium by the detection step;
The control program for controlling the data management device according to claim 10, further comprising:

Images