JP2007200306A - Recording device, recording method and recording program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To back up data from a first recording medium present in a casing to a second recording medium at higher speed. <P>SOLUTION: An index file uses a recording order showing a file recording order as an identifier to manage files in a hard disk incorporated in a device. When backing up data from the hard disk to a recording medium of a backup destination, a maximum recording order in backed up files is stored as the final recording order into the backup destination. During the next backup, the maximum recording order of the files in the hard disk is compared with the final recording order stored in the backup destination, a file having a recording order whose value is larger than that of the final recording order is read from the hard disk and recorded at the backup destination. It is possible to efficiently perform backup processing with simple control. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a recording apparatus, a recording apparatus having at least a first recording medium and a second recording medium in one casing, and backing up the recorded contents of the first recording medium to the second recording medium. The present invention relates to a method and a recording program.

  Conventionally, in a recording / reproducing apparatus that records moving images and still images as digital data on a recording medium, such as a portable digital video camera, it is common to record moving image data and still image data as files on the recording medium. Has been done. Such content recorded on a recording medium as a file is conventionally managed using a file system such as a FAT (File Allocation Table) system. As is well known, the FAT file system can manage recording files with a tree-type directory structure. In this case, file management is realized by using directory entries and table information as FAT.

  On the other hand, in recent years, the amount of data that can be recorded has increased with the increase in storage capacity of recording media, and more related information has been efficiently used in addition to file-related information (for example, file name information) that the file system has. In addition to the management by the file system described above, content is managed by using dedicated management information in response to a request to manage the content.

  For example, when playing back a moving image, an index screen using a thumbnail image that is a reduced image of a representative image of each content file recorded on a recording medium may be displayed. Corresponding to this index display, it can be considered that the management information has a configuration in which thumbnail images of the respective content files can be embedded in advance. That is, the thumbnail images are stored on the management information side in this way, so that index display can be performed efficiently. In addition, for example, by using such dedicated management information, it is possible to realize a management form that does not exist in a general-purpose file system, such as managing each content file by dividing it into folders according to a predetermined division such as the order of creation date and time. it can.

In addition, about the related prior art, the following patent documents can be mentioned.
JP 2004-227630 A

  Incidentally, in recent years, the capacity and size of hard disks have been remarkably increased, and products incorporating a hard disk have been developed as recording media for the above-described portable digital video camera. In such a digital video camera, the digital video camera and an information device such as a personal computer are connected with a cable corresponding to a predetermined communication standard such as IEEE (Institute Electrical and Electronics Engineers) 1394 or USB (Universal Serial Bus), A product has been developed that can transfer video data and still image data recorded on a hard disk to an information device via this cable and back it up to a larger capacity recording medium of the information device. Yes.

  On the other hand, in a digital video camera having a hard disk as a first recording medium, a product in which another second recording medium is built in the same housing has been proposed. For example, a hard disk and a recordable DVD (Digital Versatile Disc) drive device are built in a housing of a digital video camera. Movie data and still image data obtained by normal imaging are recorded on a hard disk. With this configuration, for example, even a user who does not have an information device such as a personal computer can record data recorded on the hard disk, which is the first recording medium, as a second recording medium. It can be backed up to a DVD for convenience.

  However, as a method for performing backup in such a configuration, if data recorded on the first recording medium is simply overwritten and copied to the second recording medium in the housing, it is recorded on the first recording medium. There is a problem that the copy process is performed for all data, and the time required for the backup is increased accordingly.

  Further, assuming that a backup data group at a certain point in time is recorded on the backup destination second recording medium, a restoration process is performed so that the data storage state at that point is restored on the first recording medium. think of. In this case, if the data group backed up on the second recording medium is simply overwritten and copied on the first recording medium as it is, then all data backed up on the second recording medium is copied. There is a problem in that processing is performed and much time is required.

  In particular, in the case of the digital video camera described above, it is considered that the main data recorded on the recording medium is moving image data. The moving image data has a very large data size compared to other data such as still image data, and a long time is required for the copy processing, and the above-described problems become conspicuous.

  Accordingly, an object of the present invention is to provide a recording apparatus, a recording method, and a recording program capable of performing backup of data from a first recording medium in a housing to a second recording medium at a higher speed. There is to do.

  In order to solve the above-described problem, the present invention provides a first recording unit that records data on a first recording medium, a second recording unit that records data on a second recording medium, The data recording on the first recording medium by the first recording unit and the data recording on the second recording medium by the second recording unit are controlled, and the data recorded on the first recording medium is uniquely Recording in which first management information for managing data, including identifiable identification information, is generated and recorded on the first recording medium at least every time data is recorded on the first recording medium. A first control information recorded on the first recording medium in the process of reflecting the recording state of the data on the first recording medium on the second recording medium. The information corresponding to is predetermined as second management information Processing to reflect the recording state of the data on the first recording medium to the second recording medium based on the difference information obtained by comparing the first management information and the second management information It is a recording apparatus characterized by controlling.

  In addition, the present invention records at least first management information for managing data, including identification information capable of uniquely identifying data recorded on the first recording medium, on at least the first recording medium. Generated and recorded on the first recording medium, and recorded on the first recording medium during the process of reflecting the recording state of the data on the first recording medium on the second recording medium. Information corresponding to the first management information is stored as predetermined second management information. Based on the difference information obtained by comparing the first management information and the second management information, A recording method characterized by performing a process of reflecting a recording state of data on one recording medium on a second recording medium.

  In addition, the present invention records at least first management information for managing data, including identification information capable of uniquely identifying data recorded on the first recording medium, on at least the first recording medium. Generated and recorded on the first recording medium, and recorded on the first recording medium during the process of reflecting the recording state of the data on the first recording medium on the second recording medium. Information corresponding to the first management information is stored as predetermined second management information. Based on the difference information obtained by comparing the first management information and the second management information, A recording program for causing a computer device to execute a recording method for performing processing for reflecting a recording state of data on one recording medium to a second recording medium.

  As described above, the present invention provides at least first management information for managing data, including identification information that can uniquely identify data recorded on the first recording medium, to at least the first recording medium. When the data is recorded and recorded on the first recording medium every time data is recorded, the first recording is performed in the process of reflecting the recording state of the data on the first recording medium on the second recording medium. Information corresponding to the first management information recorded on the medium is preliminarily held as second management information, and the difference information obtained by comparing the first management information with the second management information Based on this, since the process of reflecting the recording state of the data on the first recording medium is performed on the second recording medium, the data recorded on the first recording medium is backed up to the second recording medium. Less data movement during backup, The flop processing can be efficiently performed.

  As described above, according to the present invention, as described above, the present invention includes first management information for managing data, including identification information capable of uniquely identifying data recorded on the first recording medium. At least every time data is recorded on the first recording medium, the data is generated and recorded on the first recording medium, and the recording state of the data on the first recording medium is reflected on the second recording medium. During the processing, information corresponding to the first management information recorded on the first recording medium is stored as predetermined second management information, and the first management information, the second management information, Since the process of reflecting the recording state of the data on the first recording medium to the second recording medium is performed based on the difference information obtained by comparing the two, the data recorded on the first recording medium Data when backing up to a second recording medium Fewer, there is an effect that can perform backup operations efficiently.

Hereinafter, embodiments of the present invention will be described in the following order.
1. 1. System applied to each embodiment of the invention 1-1. Usage example of recording apparatus or recording / reproducing apparatus applicable to each embodiment of the invention 1-2. Configuration of an example of a video camera device applicable to each embodiment of the invention 1-3. File system applicable to each embodiment of the invention 1-4. 1. File management mode applicable to each embodiment of the invention 2. Embodiment of the Invention 2-1. First Embodiment of the Invention 2-1-1. Backup process according to first embodiment 2-1-2. Difference Information Detection Method Applied to First Embodiment and Other Embodiments 2-1-3. More detailed description of the backup processing according to the first embodiment 2-2. Second Embodiment of the Invention 2-2-1. Backup processing and restoration processing according to second embodiment 2-2-2. More detailed description of the restoration process according to the second embodiment 2-3. Third embodiment of the invention 2-3-1. Backup processing according to the third embodiment 2-3-2. More detailed description of backup processing according to the third embodiment 2-4. Fourth Embodiment of the Invention 2-4-1. Backup processing according to the fourth embodiment 2-4-2. More detailed description of backup processing according to the fourth embodiment 2-5. Fifth Embodiment of the Invention 2-5-1. Backup processing and restoration processing according to fifth embodiment 2-5-2. More detailed description of the restoration process according to the fifth embodiment 2-6. Sixth Embodiment of the Invention 2-6-1. Backup processing according to sixth embodiment 2-6-2. More detailed description of backup processing according to the sixth embodiment 2-6-3. 2. Modification of the sixth embodiment Modifications to each embodiment of the invention

1. 1. System applied to each embodiment of the invention 1-1. First, a recording apparatus or a recording / reproducing apparatus that can be applied to each embodiment of the invention will be described. First, in order to facilitate understanding, a recording apparatus or a recording / reproducing apparatus that can be applied to each embodiment of the present invention will be schematically described. Explained. A usage pattern of an example of a video camera apparatus 100 as a recording apparatus or recording / reproducing apparatus to which the present invention is applied will be described with reference to FIG.

  In FIG. 1, a video camera apparatus 100 includes a drive device 14 for loading a removable recording medium 15 while incorporating a recording medium 13 in a housing 12. The recording medium 13 is composed of, for example, a hard disk. The recording medium 15 is a recordable type DVD (Digital Versatile Disc) or Blu-ray Disc (registered trademark) optical disc, magneto-optical disc, non-volatile semiconductor memory, removable type, and the like. Various hard disks are considered. It is also conceivable to use a magnetic tape as the recording medium 15.

  Note that the types of the recording medium 13 and the recording medium 15 are not limited to those described above. In the above description, the recording medium 13 is built in the housing 12, but the recording medium 13 may be detachable together with the recording medium 15.

  In this video camera apparatus 100, light from a subject is incident on an optical system 11, and this light is received by an image sensor such as a charge coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) image sensor. Light is converted into an electrical signal by photoelectric conversion and subjected to predetermined processing to obtain digital video data. This digital video data is recorded on the recording medium 13, for example. The digital video data recorded on the recording medium 13 can be output to the outside via an output terminal (not shown) or can be displayed on a display element (not shown) included in the video camera device 100.

  The video camera device 100 is configured to transfer digital video data recorded on a recording medium 13 to a drive device 14 and record it on a recording medium 15 loaded in the drive device 14. Further, the video camera apparatus 100 is configured to be able to record data recorded on the recording medium 15 loaded in the drive apparatus 14 on the recording medium 13. By using this function, the video camera apparatus 100 can back up the digital video data recorded on the recording medium 13 and also uses the digital video data backed up on the recording medium 15 to record the recording medium 13. Can be restored.

  For example, when the recording medium 13 is a hard disk and the recording medium 15 is a recordable DVD, a backup of the digital video data recorded on the recording medium 13 is saved in the recording medium 15 and the recording medium 15 is stored separately. For example, even if a strong impact or vibration is applied to the video camera apparatus 100 and the digital video data recorded on the recording medium 13 is lost due to the impact or vibration, the backup data recorded on the recording medium 15 is used. The recorded contents of the recording medium 13 can be restored up to the point when backup is performed.

1-2. FIG. 2 shows an example of the configuration of a video camera device 100 applicable to each embodiment of the invention. A CPU (Central Processing Unit) 120 controls the entire video camera apparatus 100 using the RAM 121 as a work memory based on program data stored in advance in the ROM 123. The CPU 120 reads program data from the ROM 123 and develops it on the RAM 121 to execute the program. In FIG. 2, the CPU 120 and each part constituting the video camera device 100 are shown to be directly connected. However, this is not limited to this example, and each part is connected to a bus via the bus. It is also possible to exchange commands and data.

  The optical lens unit 110 constitutes the optical system 11 described above, and includes a lens system, an aperture adjustment mechanism, a focus adjustment mechanism, a zoom mechanism, a shutter mechanism, and the like for guiding light from a subject to an image pickup device included in the photoelectric conversion unit 111. The light from the subject is collected and incident on the photoelectric conversion unit 111. The aperture adjustment mechanism, focus adjustment mechanism, zoom mechanism, and shutter mechanism are controlled by the camera function unit 115 based on the control of the CPU 120. The photoelectric conversion unit 111 has an imaging element such as a CCD or a CMOS image sensor, converts light incident through the optical lens unit 110 into an electrical signal by photoelectric conversion, and performs predetermined signal processing as an imaging signal. Output.

  The image signal processing unit 112 is, for example, an imaging signal processing unit that converts an imaging signal output from the photoelectric conversion unit 111 into a digital signal, and a predetermined signal for the digital signal obtained by converting the imaging signal by the imaging signal processing unit. A video signal processing unit that performs processing and converts into baseband digital video data, and a compression encoding unit that compresses and encodes baseband digital video data obtained by the video signal processing unit by a predetermined method.

  The imaging signal processing unit, for example, samples only a signal having image information by a CDS (Correlated Double Sampling) circuit with respect to the imaging signal output from the photoelectric conversion unit 111, removes noise, and performs AGC (Auto Gain Control). ) Adjust the gain with the circuit. And it converts into a digital signal by A / D conversion. In addition, the imaging signal processing unit sends information on the imaging signal output from the photoelectric conversion unit 111 to the CPU 120. The CPU 120 generates a control signal for controlling the optical lens unit 110 based on this information, and controls the focus adjustment mechanism, the aperture adjustment mechanism, and the like.

  The video signal processing unit performs predetermined signal processing on the digital signal obtained by the imaging signal processing unit. For example, the video signal processing unit performs detection type signal processing on the digital signal, and extracts components of each color of R (red), G (green), and B (blue). Then, processing such as γ correction and white balance correction is performed based on each extracted color component, and finally, it is output as one baseband digital video data.

  The compression encoding unit compresses and encodes the baseband digital video data output from the video signal processing unit in accordance with, for example, MPEG2 (Moving Pictures Experts Group 2) system. The present invention is not limited to this example. H.264 | AV, ie, ITU-T (International Telecommunication Union-Telecommunication Standardization Sector) recommendation H.264. It is also conceivable to use a compression encoding method conforming to H.264 or ISO (International Organization for Standarization) / IEC (International Electrotechnical Commission) International Standard 14496-10 (MPEG-4 Part 10) Advanced Video Coding.

  The display unit 114 can perform display based on digital video data supplied from the image signal processing unit 112 using, for example, an LCD (Liquid Crystal Display) as a display element. The display unit 114 is used as a monitor of a captured image during shooting, and can display a playback image during playback.

  The image input / output unit 113 outputs the digital video data output from the image signal processing unit 112 to the outside. Digital video data supplied from outside can also be supplied to the image signal processing unit 112. Further, the image input / output unit 113 includes an A / D conversion unit and a D / A conversion unit, and the digital video data output from the image signal processing unit 112 is converted into an analog video signal for output or supplied from the outside. The analog video signal thus converted may be converted into digital video data and supplied to the image signal processing unit 112.

  The audio input / output unit 116 has audio input / output means such as a microphone and a speaker, and converts external audio into an audio signal or converts an audio signal into audio. The audio input / output unit 116 also includes an audio signal input / output unit. The audio processing unit 117 A / D converts the analog audio signal supplied from the audio input / output unit 116 into digital audio data, performs predetermined audio signal processing such as noise removal and sound quality correction, and baseband digital audio data Output as. The baseband digital audio data may be compressed and encoded by a predetermined method. The audio signal processing unit 117 performs predetermined audio signal processing such as sound quality correction and volume adjustment on the supplied digital audio data, D / A converts it to an analog audio signal, performs amplification processing, etc. This is supplied to the input / output unit 116.

  The operation input unit 124 is provided with a predetermined operation element for the user to operate the operation of the video camera apparatus 100, and this control signal for outputting a control signal corresponding to the operation on the operation element is supplied to the CPU 120. . The CPU 120 controls the operation of each unit of the video camera device 100 by processing a program based on a control signal supplied from the operation input unit 124 in response to a user operation. Further, a simple display unit may be provided in the operation input unit 124 to perform a predetermined display regarding the operation of the video camera device 100.

  The controller unit 126 is connected to at least a hard disk 127 corresponding to the recording medium 13 and a drive apparatus 128 corresponding to the drive apparatus 14 described above, and records data by the hard disk 127 and the drive apparatus 128 based on a command from the CPU 120. Control playback.

  For example, based on a command from the CPU 120, the controller unit 126 performs control so that digital video data captured by the image sensor of the photoelectric conversion unit 111 and compressed and encoded by the image signal processing unit 112 is recorded on the hard disk 127. . Further, for example, the controller unit 126 performs control so as to read data from the hard disk 127 based on a command from the CPU 120 and record the read data on the recording medium 130 loaded in the drive device 128.

  The recording medium 130 applicable to the drive device 128 is not particularly limited as long as digital data can be recorded. However, a recordable type DVD (Digital Versatile Disc), CD (Compact Disc), Blu- A disc-shaped recording medium such as an optical disc such as ray disc (registered trademark) or a magneto-optical disc, or a rewritable nonvolatile semiconductor memory is suitable. A removable hard disk can also be used as the recording medium 130 applicable to the drive device 128.

  The communication unit 125 communicates with an external device by wire and / or wireless using a predetermined protocol based on the control of the CPU 120. The wired and / or wireless communication interface is not particularly limited as long as digital communication is possible, but as the wired communication, a LAN (Local Area Network) by USB, IEEE 1394, Ethernet (registered trademark), or the like can be considered. . In addition, IEEE802.11a / b / g, Bluetooth, etc. can be considered as wireless communication. Further, by connecting an external device having a host function such as a personal computer and the video camera device 100 with an interface such as USB or IEEE1394, the hard disk 127 or drive device connected to the controller unit 126 of the video camera device 100 is connected. The recording medium loaded in 128 can be mounted on an external device.

  The power supply unit 131 is made of, for example, a battery, and supplies power to each unit of the video camera device 100. ON / OFF of power supply by the power supply unit 131 is controlled by the CPU 120 in accordance with, for example, a predetermined operation on the operation input unit 124.

  The CPU 120 is connected to a nonvolatile memory 129 capable of holding stored contents even when power is not supplied. The CPU 120 can store and hold setting information for the video camera device 100 and predetermined management information in the nonvolatile memory 129.

1-3. 2. File System Applicable to Each Embodiment of the Invention The video camera apparatus 100 illustrated in FIG. 2 as a recording apparatus applicable to each embodiment of the present invention is mainly composed of digital video data and digital data obtained by imaging and sound collection. The content file Fct composed of audio data is recorded on the HDD 127 as described above.

  Here, in the video camera apparatus 100, the content file Fct is managed and recorded on the hard disk 127 by a FAT (File Allocation Table) file system. As is well known, the FAT file system manages files using a tree-type directory structure. Data writing and reading are performed by a logical minimum data management unit called a cluster. A cluster is a unit obtained by collecting a predetermined number of sectors, which are the minimum units of physical data writing and reading on a recording medium.

  FIG. 3 shows a general system configuration of the FAT file system by a hierarchical model. First, the hierarchical model is roughly divided into a software layer and a hardware layer as a lower layer. The software layer corresponds to software processing realized by a program executed by a CPU (CPU 120 in the example of FIG. 2) on the host side with respect to the recording medium, various firmware, middleware, and the like. The software layer in this case is configured such that the application 50 is positioned above the application 50 and the file system 51 as shown in the figure. It can be considered that a physical recording area of the recording medium itself is located in the hardware layer.

  The application 50 corresponds to, for example, application software that has a file recording / playback function and uses the recording medium 52, and issues an access request at the file level to the file system 51.

  The file system 51 corresponds to software that realizes a function as a file system. In this example, since the FAT file system is used as the file system, the software that provides the function of the file system 51 is also configured corresponding to the FAT file system. In the file system 51, an access request to the recording medium 52 is made according to the access request from the application 50.

  The recording medium 52 is logically formatted (initialized) according to the FAT file system. In FIG. 2, the hard disk 127 corresponds to the recording medium 52.

  In FIG. 2, the recording medium 130 loaded in the drive device 128 also corresponds to the recording medium 52. When the recording medium 130 is a recordable DVD or Blu-ray Disc, the file system applied to the recording medium 130 is UDF (Universal Disk Format). UDF includes a format according to ISO (International Organization for Standarization) 9660, and can be accessed by various file systems used in computer devices, and includes a FAT file system. In this case, the CPU 120 needs to further have a configuration corresponding to UDF as software that provides the function of the file system 51.

  In response to the access request from the file system 51, the recording medium 52 reads out data from the specified address and returns it to the file system 51 to execute an access response. The file system 51 receives data as an access response from the recording medium 52 and delivers the received data to the application 50. The application 50 executes a required process at the application level for the received data file according to, for example, an operation input by the user.

  Further, the FAT file system manages files by a tree-type directory structure, and manages files as a cluster unit set. Such file management and data management are realized by providing directory entries and table information (management information) as FAT as is well known. The directory entry is information indicating the location of files, directories, and subdirectories on the recording medium 52 at the cluster level, and the FAT is information indicating a link at the cluster level forming the directory and the file.

  FIG. 4 shows an exemplary management structure of files recorded on the hard disk 127. Files are managed hierarchically by a directory structure. On the hard disk 127, at least two directories, an index file directory and a content file directory, are formed. A content file Fct is stored under the content file directory. An index file Findex is stored under the index file directory.

  The index file Findex stores management information for managing the content file Fct by a method different from the FAT. In this case, the index file Findex stores management information dedicated to content such as a still image or a moving image for efficient management. As described above, by using the management information dedicated to the content file Fct separately from the FAT file system, the number of contents that can be recorded has increased in recent years as the storage capacity of the recording medium has increased. In addition to the content related information (for example, information on the file name and update date, etc.) that the file system has, it is possible to respond to requests such as more efficient management of related information.

  For example, when playing back a moving image, an index display using thumbnail images representing each content file may be performed. In such a case, it is possible to embed a thumbnail image corresponding to each content file in advance so as to correspond to the index display by using dedicated management information. That is, by storing thumbnail images on the management information side in this way, index display can be performed efficiently.

  Further, by separately using management information specialized for content file management in this way, a directory is created under the content file directory in a predetermined division such as the order of file creation date, and the corresponding content file is stored in the directory. Management such as storage is also possible. By separately performing management using dedicated management information in this way, it is possible to realize a management mode that was not found in a general-purpose file system.

1-4. Next, a file management mode applicable to each embodiment of the present invention will be described. FIG. 5 shows an example of a file management form using an index file Findex as dedicated management information applicable to each embodiment of the present invention. As described with reference to FIG. 4, the index file Findex is stored under the index file directory. The index file Findex stores a plurality of management file slots Sm as shown in the figure. Each management file slot Sm includes a file name portion 60, a file update date / time portion 61, an entry ID portion 62, an entry update date / time portion 63, a content ID portion 64, a content update date / time portion 65, a file path portion 66, and the like. Hereinafter, the data stored in each management file slot Sm is referred to as entry data.

  In FIG. 5, the file name portion 60 stores information on the file name of the content file Fct associated with the management file slot Sm. The file update date / time portion 61 stores information indicating the date / time when the content file Fct associated with the management file slot Sm is created and / or updated.

  The entry ID section 62 stores identification information (referred to as an entry ID) for uniquely identifying entry data for the management file slot Sm. The entry ID is assigned every time new entry data is entered into the management file slot Sm in response to the generation of a new content file Fct. The entry update date / time portion 63 stores information indicating the date / time when entry data for the management file slot Sm was entered or updated. The information stored in the entry update date / time portion 63 is changed according to the update of entry data regardless of whether or not the content file Fct is updated. An example in which the information stored in the entry update date / time portion 63 is updated includes, for example, a case where metadata (not shown) to be associated with the content file Fct is updated.

  The content ID portion 64 stores a content ID assigned to uniquely identify the content file Fct associated with the management file slot Sm, in other words, associated with the entry ID. The content ID can be generated by combining, for example, file path information indicating the location of the content file Fct corresponding to the content ID and the file generation date and time. This content ID corresponds to the file identifier in the present invention.

  The content update date / time portion 65 stores information indicating the date / time when the content file Fct was created and / or updated. The information stored in the content update date / time portion 65 does not change by copying or moving the corresponding content file Fct. On the other hand, the information stored in the file update date / time portion 61 is different from the information stored in the content update date / time portion 65 in that the information is updated when the content file Fct is copied or moved.

  The file path unit 66 stores information on the path to the content file Fct associated with the management file slot Sm. That is, in this case, information indicating the location of the content file Fct under the FAT file system management is stored.

  Here, new entry data is added to the management file slot Sm in the index file Findex in accordance with the generation of the content file Fct on the hard disk 127 by the file system 51. In the added entry data, information indicating the location of the generated content file Fct under the FAT file system management is stored in the file path 66. As a result, the management file slot Sm is associated with the content file Fct generated under the content file directory. In this case, the content file Fct generated under the content file directory can also be specified by the content ID stored in the content ID portion 64, as indicated by the dashed arrow in FIG.

2. BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, a data backup method and a backed-up data restoration method as embodiments of the present invention will be described with reference to the first to sixth embodiments.

  As an embodiment of the present invention, as described above, in the video camera device 100, the content file Fct recorded on the hard disk 127 is to be backed up to the recording medium 130 loaded in the drive device 128. . In addition, the content file Fct backed up on the recording medium 130 is written back to the hard disk 127 in the video camera apparatus 100, and the recorded content of the hard disk 127 is to be restored to a certain point.

  At this time, as such a backup, if the content file Fct recorded on the hard disk 127 is simply overwritten and copied to the recording medium 130 loaded in the drive device 128, all the content files Fct recorded on the hard disk 127 are used. Need to be copied, and the time required for backup becomes longer. In particular, in the case of the video camera apparatus 100, the content file Fct is mainly composed of moving image data, and compared with a case where other data such as still image data is recorded as the content file Fct, the copy process has a larger amount. It takes time and is inefficient.

  Therefore, in each embodiment of the present invention, during the backup process, the video camera apparatus 100 has backed up management information indicating the current file management state on the hard disk 127 and the past held in the recording medium 130. Compare with management information. Based on the comparison result, difference information between the current file storage state of the hard disk 127 and the file storage state of the hard disk 127 at the time of the previous backup is detected, and the content file Fct is backed up based on the difference information. To do.

  More specifically, the index file Findex recorded on the hard disk 127 during the backup process is compared with the index file Findex recorded on the recording medium 130 during the past backup process, and the difference information is based on the comparison result. Is detected.

2-1. First Embodiment of the Invention First, a first embodiment of the present invention will be described. In the first embodiment of the present invention, as a backup process, a synchronization process for synchronizing the file storage state on the hard disk 127 and the file storage state on the recording medium 130 as the backup destination is performed.

2-1-1. Backup Process According to First Embodiment of the Invention FIG. 6 schematically shows an example of synchronization processing in the video camera apparatus 100 according to the first embodiment of the present invention. In the first embodiment, the content file Fct recorded on the hard disk 127 is backed up to the recording medium 130 loaded in the drive device 128 by this synchronization processing. FIG. 6A shows an example of state transition along the time axis t for the index file Findex and the content file Fct recorded on the hard disk 127. FIG. 6B shows an example of state transition along the time axis t for the index file Findex, the content file Fct, and the management information 30b recorded on the recording medium 130 by the drive device 128.

  As illustrated in FIG. 6A, in the initial state, the content file Fct “A”, the content file Fct “B”, and the content file Fct “C” are recorded on the hard disk 127 that is the backup source as the content file Fct. As the file Findex, a file having the content “1” corresponding to the storage state is recorded. Further, it is assumed that a predetermined recording medium 130 is loaded in the drive device 128 as a file backup destination.

  At a time point t1 after the initial state, for example, a predetermined operation is performed on the operation unit 124 of the video camera apparatus 100, and the first synchronization processing of the recorded content of the hard disk 127 and the recorded content of the recording medium 130 is performed.

  At the time of the first synchronization processing at time t1, the content file Fct on the hard disk 127 is not backed up on the recording medium 130 on the recording medium 130. For example, the CPU 120 can detect that the content file Fct backed up from the hard disk 127 does not exist on the recording medium 130 based on whether or not the index file Findex is backed up on the recording medium 130. That is, as will be described later, if the synchronization process is performed, the index file Findex is stored on the recording medium 130.

  When the CPU 120 detects that the content file Fct does not exist on the recording medium 130, all the content files Fct (content files Fct “A”, “B”, and “C”) recorded on the hard disk 127, and these The index file Findex having the content “1” managing the content file Fct on the hard disk 127 is read from the hard disk 127, transferred to the drive device 128, and recorded on the recording medium 130. Thereby, the storage state of the content file Fct in the hard disk 127 and the storage state of the content file Fct in the recording medium 130 are synchronized.

  Next, the CPU 120 updates the content of the management information 30b in order to manage the content file Fct recorded on the recording medium 130. That is, the CPU 120 updates the content of the management information 30b to the content “α” for managing the content files Fct “A”, “B”, and “C” stored on the recording medium 130. . File management by the management information 30b can be performed by, for example, a content ID attached to the content file Fct.

  Subsequently, at time t2 after the first synchronization processing at time t1, for example, a new moving image is shot on the video camera device 100 side, and a content file Fct “D” based on the shooting is generated and recorded on the hard disk 127. Shall be. In response to the generation and recording of the content file Fct “D”, the index file Findex has a content “1” at the time t1 and a content “2” describing information indicating that the content file Fct “D” has been recorded. Is updated.

  At this time point t2, the file storage state of the recording medium 130 has not changed from the time point t1. Therefore, as can be seen by comparing FIG. 6A and FIG. 6B, the addition of the content file Fct “D” makes the file storage state on the hard disk 127 different from the file storage state on the recording medium 130. .

  It is assumed that at a subsequent time t3, a synchronization instruction is given to the CPU 120 by a predetermined operation on the operation unit 124, for example. At time t3, the backed up content file Fct already exists on the recording medium 130. In such a case, the CPU 120 compares the index file Findex on the hard disk 127 and the index file Findex on the recording medium 130 according to the synchronization instruction, and the storage state of the content file Fct on the hard disk 127 and the recording medium 130 is compared. Detect differences.

  In the example of FIG. 6, at time t3, the index file Findex having the content “1” stored in the recording medium 130 by the synchronization processing at time t1 and the content file Fct “D” are recorded and updated at time t2. The index file Findex having the content “2” is compared. By this comparison, it is detected that the content file Fct “D” that does not exist on the recording medium 130 is recorded on the hard disk 127 side, and the presence of the content file Fct “D” on the hard disk 127 side is detected as difference information. Detected.

  The CPU 120 performs a backup process of the content file Fct on the hard disk 127 based on the detected difference information. In the first embodiment, since the backup process is performed as a synchronous process, the CPU 120 controls the content file Fct “D” indicated by the difference information to be read from the hard disk 127 and recorded on the recording medium 130. . The CPU 120 records the index file Findex having the content “2” recorded on the hard disk 127 together with the recording of the content file Fct “D” over the index file Findex already recorded on the recording medium 130. To control. Further, the management information 30b is changed from the content “α” at the time point t1 to the content “β” managed so that the content file Fct “D” is added to the recording medium 130. Information 30b is updated.

  After the synchronization processing at time t3, it is assumed that the content file Fct “B” is deleted from the hard disk 127 as illustrated in FIG. 6A at the next time t4. In response to this deletion, the index file Findex is updated from the content “2” to the content “3” reflecting the deletion of the content file Fct “B”.

  At this time t4, the file storage state on the hard disk 127 side is the state in which the content files Fct “A”, “C”, and “D” are stored, and the index file Findex corresponds to the storage state of the content file. “3”. On the other hand, in the backup destination recording medium 130, the storage state of the content file Fct is a state in which the content files Fct “A”, “B”, “C”, and “D” are stored, and the corresponding index file Findex is stored. Is the same as the content “2” of the previous synchronization process.

  Assume that a synchronization instruction is given to the CPU 120 by a predetermined operation on the operation unit 124 at a subsequent time t5, for example. At time t5, the backed-up content file Fct already exists on the recording medium 130, similarly to the above-described time t3. Therefore, the CPU 120 compares the index file Findex on the hard disk 127 and the index file Findex on the recording medium 130 according to the synchronization instruction, and detects the difference in the storage state of the content file Fct between the hard disk 127 and the recording medium 130. To do.

  In the example of FIG. 6, at time t5, the index file Findex having the content “2” stored in the recording medium 130 by the synchronization processing at time t3 and the content file Fct “B” are deleted and updated at time t4. The index file Findex on the hard disk 127 having the content “3” is compared. By this comparison, it is detected that the content file Fct “B” that does not exist on the hard disk 127 is stored on the recording medium 130 side. Detected as information.

  In this way, for the difference information indicating that the content file Fct “B” that does not exist on the hard disk 127 side exists on the recording medium 130 side, the CPU 120 indicates the difference information that exists on the recording medium 130. Control is performed to delete the content file Fct “B”. At the same time, the index file Findex having the content “3” recorded on the hard disk 127 is controlled to be overwritten on the index file Findex already recorded on the recording medium 130. Further, the management information 30b is changed from the content “β” at the time point t3 to the content “γ” reflecting that the content file Fct “B” on the recording medium 130 is deleted, and the management information 30b is updated.

  At the next time point t6, the content file Fct “C” recorded on the hard disk 127 is modified according to a predetermined operation on the operation unit 124, and the content file Fct is updated to the content file Fct “C ′”. Shall be. With the update of the content file Fct, the content of the index file Findex on the hard disk 127 is changed from the content “3” to the content “4” reflecting the update of the content file Fct.

  It is assumed that a synchronization instruction is given to the CPU 120 by a predetermined operation on the operation unit 124 at a subsequent time t7. At time t7, the backed up content file Fct already exists on the recording medium 130. Therefore, the CPU 120 compares the index file Findex on the hard disk 127 and the index file Findex on the recording medium 130 according to the synchronization instruction, and detects the difference in the storage state of the content file Fct between the hard disk 127 and the recording medium 130. To do.

  In the example of FIG. 6, at time t7, the index file Findex having the content “3” and the content file Fct “C” modified at time t4 are stored in the recording medium 130 by the synchronization processing at time t5. The index file Findex on the hard disk 127 having the content “4” including the information indicating the file Fct “C ′” is compared. By this comparison, it is detected that the content file Fct “C ′” on the hard disk 127 is a corrected file. Whether or not the content file Fct has been updated due to correction or the like is determined based on information stored in the content update date / time portion 65 in the corresponding management file slot Sm in the index file Findex between the hard disk 127 and the recording medium 130. You can know by comparing. When the content file Fct is updated due to correction or the like, the content ID corresponding to the content file Fct does not change.

  As described above, the content file Fct “C” on the hard disk 127 side is updated. This means that the content file Fct “C ′” that does not exist on the recording medium 130 side exists on the hard disk 127 side, and the hard disk 127. The content file Fct “C” that does not exist on the recording medium 130 exists on the recording medium 130 side. That is, the difference information in this case includes information on the content file Fct “C” and the content file Fct “C ′”.

  The CPU 120 stores the index file Findex having the content “3” stored in the recording medium 130 by the synchronization process at the time t5, and the content “4” including information indicating the content file Fct “C ′” modified at the time t4. Control is performed so as to delete the content file Fct (in this example, the content file Fct “C”) corresponding to the content ID indicated by the difference information as a result of the comparison with the index file Findex on the hard disk 127 having To do.

  Further, in this case, the CPU 120 controls to record the content file Fct “C ′” corresponding to the content ID indicated by the difference information stored in the hard disk 127 on the recording medium 130. At the same time, the CPU 120 controls the recording medium 130 to record the index file Findex having the content “4” on the hard disk 127. Further, the management information 30b reflects that the content file Fct “C ′” is stored in the recording medium 130 by deleting the content file Fct “C” from the recording medium 130 from the content “γ” at the time t5. Change to “δ” and update the management information 30b. That is, the management information of the content “δ” is content indicating that the content files Fct “A”, “C ′”, and “D” are stored in the recording medium 130.

  According to the first embodiment of the present invention, by performing the processing as described above, the storage state of the content file Fct in the backup source hard disk 127 and the content in the backup destination recording medium 130 for each backup processing. The storage state of the file Fct can be synchronized.

  In this way, if the backup process is performed based on the difference information, only the difference file can be actually recorded on the recording medium 130, and the backup is performed in comparison with the case where all contents are overwritten. Processing can be further accelerated. Further, the processing load can be reduced by reducing the number of content files to be recorded.

  In the above description, the storage state of the content file Fct in the hard disk 127 and the recording medium 130 are compared by comparing the current index file Findex at the backup source with the index file Findex saved at the previous backup processing at the backup destination. The difference from the storage state of the content file Fct is detected. Thus, by comparing the contents of the index file Findex of the backup source and the backup destination and obtaining the difference information, for example, the header information (content ID and content) for all the content files Findex that are actually stored. The difference information can be obtained at a higher speed than the method of obtaining the difference information by detecting the update date and time and comparing them, and in this respect also, the backup process can be speeded up.

  In this embodiment, in the index file Findex that manages each content file Fct, in addition to the content ID (file identifier), other file related information such as the content update date / time and entry update date / time is stored in the content file Fct. Are associated with each other.

  On the other hand, in the index file Findex, it is also conceivable to perform management by associating only the content ID for identifying the content file Fct. In this case, the management information on the hard disk 127 side and the recording medium 130 side, that is, the index file Findex are compared, so that the addition and deletion of the content file Fct from the previous backup process on the hard disk 127 side is performed. It is possible to make a determination.

  In order to perform a backup process for discriminating differences other than addition and deletion of the content file Fct, for example, it is necessary to separately acquire necessary related information associated with the content file Fct, and it is necessary to acquire the difference information. As time increases, a time until backup processing based on the difference information is completed is imaged.

  In this embodiment, file related information other than the file identifier, such as the content update date and time, is also entered as entry data for the index file Findex, so that “content update”, “entry update”, etc. Other difference types can also be acquired simply by comparing the management information. As a result, even when the difference type other than the addition and deletion of content is determined, the difference type can be determined by comparing the management information, and the difference type other than the addition and deletion of such content can be determined. The corresponding backup processing is also speeded up.

2-1-2. Difference Information Detection Method Applied to First Embodiment and Other Embodiments Here, a difference detection method for index file Findex performed in the first embodiment and other embodiments described later. Will be described. FIG. 7 shows an example of the structure of the difference detection information list LDd for performing difference detection. In the difference detection information list LDd, the difference detection information Dd is listed as illustrated. One piece of difference detection information Dd corresponds to one piece of entry data (that is, one content file Fct) entered in the index file Findex.

  That is, one piece of difference detection information Dd includes a content ID portion 64, an entry update date / time portion 63, a content update date / time portion 65, an entry ID in the management file slot Sm for each entry data entered in the index file Findex. It consists of information obtained by extracting information stored in each of the units 62. The difference detection information list LDd is information obtained by listing the difference detection information Dd generated for all entry data entered in the index file Findex. In the difference detection information list LDd illustrated in FIG. 7, the difference detection information Dd is sorted and listed in ascending order of the content ID.

  The difference detection information list LDd illustrated in FIG. 7 is stored in the hard disk 127 and the index file Findex stored in the backup destination recording medium 130 by the CPU 120 when performing a new backup process. Both are generated for both the index file Findex.

  Actually, the index file Findex stored in the backup destination recording medium 130 is stored in the previous backup process. In the case of the first embodiment, backup processing is synonymous with synchronization processing.

  FIG. 8 shows a comparison between two difference detection information lists LDd generated by the CPU 120 during backup processing. In FIG. 8, the difference detection information list LDp generated based on the index file Findex saved in the backup destination recording medium 130 is shown as a difference detection information list LDd-ps. Further, the difference detection information list LDp generated based on the index file Findex held in the hard disk 127 is shown as a difference detection information list LDd-pr.

  Hereinafter, the difference detection information list LDd-ps generated based on the index file Findex stored in the backup destination recording medium 130 will be referred to as the difference detection information list LDd at the time of the previous backup and stored in the hard disk 127 as appropriate. The difference detection information list LDd-pr generated based on the index file Findex is called the difference detection information list LDd at the time of the current backup.

  In the example of FIG. 8, the content ID values are “4”, “23”, and “34” in the index file Findex on the recording medium 130, that is, the difference detection information list LDd-ps at the previous backup. , Difference detection information Dd having values “35”, “50”, and “56” is listed. This is because the content file Fct having the value “4”, the value “23”, the value “34”, the value “35”, the value “50”, and the value “56” is stored in the hard disk 127 at the time of the previous backup. It has been shown.

  On the other hand, in FIG. 8, in the index file Findex on the hard disk 127, that is, the difference detection information list LDd-pr at the time of the current backup, the content ID values are “4”, “23”, “35”, An example is shown in which difference detection information Dd having values “47”, “50”, “56”, and “64” is listed. This is because at the time of this backup, the content ID values of the hard disk 127 are the value “4”, the value “23”, the value “35”, the value “47”, the value “50”, the value “56”, and the value “64”. It shows that the content file Fct is stored.

  The CPU 120 holds the difference detection information list LDd-ps and the difference detection information list LDd-pr as difference information generation information Rdy as illustrated in FIG. For example, when the CPU 120 is instructed to back up the content file Fct recorded in the hard disk 127 by a predetermined operation on the operation unit 124, the index file Findex recorded in the hard disk 127 and the backup destination are stored. Each of the index files Findex recorded on the recording medium 130 is read, difference information generation information Rdy is generated based on the read information, and stored in the RAM 121.

  The CPU 120 detects actual difference information using the difference information generation information Rdy. FIG. 9 schematically shows the difference information detection operation using the difference information generation information Rdy. 9 shows difference information generation information Rdy based on the difference detection information list LDd-ps and the difference detection information list LDd-pr shown in FIG. In FIG. 9, items in the difference detection information Dd having different contents in the difference detection information list LDd-ps and the difference detection information list LDd-pr are shown with shadows.

  In the difference information generation information Rdy, the content ID is included as an item of the difference detection information Dd. As a result, the content IDs of the difference detection information Dd in the difference detection information list LDd-ps at the time of the previous backup and the difference detection information Dd in the difference detection information list LDd-pr at the time of the current backup are set to the respective content IDs. By comparison, content addition and content deletion in the hard disk 127 can be detected.

  In other words, in the example of FIG. 9, the difference detection information list LDd-ps at the previous backup includes the difference detection information Dd with the content ID = “34”, and the difference detection information list LDd− at the current backup is present. This does not exist in pr. Therefore, it is possible to detect that the content file Fct having the content ID value “34” has been deleted in the hard disk 127.

  Further, referring to FIG. 9, for example, the difference detection information list LDd-pr at the current backup includes the difference detection information Dd with the content ID = “64”, and the difference detection information list LDd− at the previous backup is present. This does not exist in ps. Accordingly, it is possible to detect that the content file Fct having the value of the content ID “64” has been added to the hard disk 127.

  Further, the entry update date and time is included as an item of the difference detection information Dd. As a result, the content file Fct whose entry has been updated among the content files Fct recorded on the hard disk 127 can be detected. For example, in the example of FIG. 9, in the difference detection information list LDd-ps at the time of the previous backup and the difference detection information list LDd-pr at the time of the current backup, the difference detection information Dd with content ID = “23”. Indicates that the information contents of the entry update date and time are different. Thereby, it is possible to detect that the entry is updated in the hard disk 127 for the content file Fct having the content ID = “23”.

  Furthermore, information on the content update date / time is included as an item of the difference detection information Dd. Thereby, the updated content file Fct can be detected among the content files Fct recorded on the hard disk 127. That is, in the example of FIG. 9, the difference detection information Dd with the content ID = “50” in the difference detection information list LDd-ps at the previous backup and the difference detection information list LDd-pr at the current backup is It is shown that the information contents of the content update date and time are different. Thereby, it can be detected that the content file Fct with the content ID = “50” has been updated on the hard disk 127.

  Further, an entry ID item is included as an item of the difference detection information Dd. By including the item of entry ID as the item of difference detection information Dd, it is possible to specify which content file Fct is the content file Fct that is the target of difference detection. In this sense, the entry ID information in the difference detection information Dd plays the same role as the content ID item provided in the difference detection information Dd. According to this, the entry ID item in the difference detection information Dd can be made unnecessary for the purpose of the backup process.

  For example, the entry ID may be used when an application in the video camera device 100 or an external application accesses entry data when the content file Fct is transferred from the hard disk 127 to the outside. Therefore, an entry ID item is added to the difference detection information Dd.

  Further, as understood from this description, the entry ID in the difference detection information Dd is not an item provided for detecting the difference. Therefore, even when the entry IDs are different between the difference detection information list LDd-ps and the difference detection information list LDd-pr as in the content ID = “56” in FIG. 09, these differences are not detected. Has been.

  In FIG. 9, the difference information list LSB is generated from the comparison result of the information content of each difference detection information Dd using the difference information generation information Rdy. The difference information list LSB is information in which the difference information SB is listed as illustrated on the right side of FIG. Each difference information SB is provided with three items of an item “difference type”, an item “previous entry ID”, and an item “current entry ID”.

  The item “previous entry ID” and the item “current entry ID” are information of the difference detection information list LDd-ps at the previous backup and the difference detection information list LDd-pr at the current backup in the difference information generation information Rdy. From the comparison results of the contents, the entry ID of the difference detection information Dd in the difference detection information list LDd-ps determined to be different from each other, and the entry ID of the difference detection information Dd in the difference detection information list LDd-pr And are stored.

  The item “difference type” stores information indicating the type of difference. In this case, there are four types of difference, “content addition”, “content deletion”, “content update”, and “entry update”.

  The difference information SB is generated as follows, for example. First, for the difference detection information Dd in the difference detection information list LDd-ps at the previous backup and the difference detection information Dd in the difference detection information list LDd-pr at the current backup, the first difference detection information The information contents are compared in order from Dd.

  At this time, if the content IDs in the difference detection information Dd are the same, it is understood that no content is added or deleted. In this case, the entry update date / time and the content update date / time corresponding to the content ID are compared.

  As a result of the comparison, if the entry update date / time is different, the difference type is “entry update”. In response to this, information indicating “entry update” as the difference type is stored in the difference information list LSB. At the same time, the entry ID in the difference detection information Dd in the difference detection information list LDd-ps is the previous entry ID, and the entry ID in the difference detection information Dd in the difference detection information list LDd-pr is the current entry ID. Are listed in the difference information SB.

  If the content update date / time is different as a result of comparison, the difference type is “content update”. In response to this, information indicating the difference type “content update” is stored in the difference information list LSB. At the same time, the entry ID in the difference detection information Dd in the difference detection information list LDd-ps is the previous entry ID, and the entry ID in the difference detection information Dd in the difference detection information list LDd-pr is the current entry ID. Are listed in the difference information SB, respectively.

  On the other hand, if the content IDs are different as a result of the comparison, it is determined whether content addition or content deletion has been performed.

  For example, each content ID value of the difference detection information Dd in the difference detection information list LDd-ps at the previous backup time and the content of the difference detection information Dd in the difference detection information list LDd-pr at the current backup time Compare each of the ID values.

  As a result of the comparison, the content file Fct corresponding to the value of the content ID that is in the difference detection information list LDd-ps at the time of the previous backup and not in the difference detection information list LDd-pr at the time of the current backup is It can be determined that it has been deleted from the hard disk 127 between the backup time and the current backup time. On the other hand, the content file Fct corresponding to the value of the content ID that is in the difference detection information list LDd-pr at the time of the current backup but not in the difference detection information list LDd-ps at the time of the previous backup is From this, it can be determined that it was added to the hard disk 127 during the current backup.

  More specifically, for the difference detection information Dd in the difference detection information list LDd-ps at the previous backup and the difference detection information Dd in the difference detection information list LDd-pr at the current backup, As a result of comparison in order from the difference detection information Dd, if the value of the content ID of the difference detection information Dd in the difference detection information list LDd-ps at the time of the previous backup is smaller, it is recorded on the hard disk 127. It can be seen that the content file Fct corresponding to the content ID of the difference detection information Dd at the time of the previous backup has been deleted.

  Therefore, the difference type in this case is “content deletion”. In response to this, information indicating “content deletion” is stored in the difference information list LSB. At the same time, the difference information SB in which the entry ID of the difference detection information Dd in the difference detection information list LDd-ps at the previous backup is stored as the previous entry ID is listed. When the difference type is “content deletion”, the current entry ID does not exist, so no information is stored in the item of the current entry ID.

  In the example of FIG. 9, the content ID value of the third difference detection information Dd in the difference detection information list LDd-ps is the value “34”, whereas the difference detection information list LDd-pr The value of the content ID of the third difference detection information Dd is “35”, and the content ID of the difference detection information Dd in the difference detection information list LDd-ps at the time of the previous backup is better. The value is small. As a result, it can be seen that the content file Fct corresponding to the content ID value “34” shown in the difference detection information list LDd-ps has been deleted.

  In the comparison processing after this “content deletion” is detected, the difference detection information Dd compared this time in the difference detection information list LDd-pr at the time of the current backup is again targeted, and the difference detection information at the time of the previous backup. This is done by comparing with the difference detection information Dd having the next content ID in the list LDd-ps.

  As a more specific example, referring to FIG. 9, for example, the difference detection information Dd with content ID = “34” in the difference detection information list LDd-ps at the previous backup, and the difference detection information at the current backup After the comparison with the difference detection information Dd with the content ID = “35” in the list LDd-pr is performed and “content deletion” is detected, the content in the difference detection information list LDd-pr at the time of the current backup The difference detection information Dd with ID = “35” is again targeted and compared with the difference detection information Dd with content ID = “35” in the difference detection information list LDd-ps at the previous backup. In this way, even after “content deletion” is detected, the difference type can be properly detected.

  Contrary to the above, regarding the difference detection information Dd in the difference detection information list LDd-ps at the time of the previous backup and the difference detection information Dd in the difference detection information list LDd-pr at the time of the current backup, If the content ID of the difference detection information Dd in the difference detection information list LDd-pr at the time of the current backup has a smaller value as a result of comparison in order from the top difference detection information Dd, the hard disk 127 is loaded. It can be seen that the content file Fct corresponding to the content ID is added to the recorded content file Fct.

  Therefore, the difference type in this case is “content addition”. In response to this, information indicating “content addition” is stored in the difference information list LSB. At the same time, the difference information SB in which the entry ID of the difference detection information Dd in the difference detection information list LDd-ps at the time of the current backup is stored as the current entry ID is listed. In the case of content addition, since the previous entry ID does not exist, no information is stored in the item of the previous entry ID.

  Regarding the comparison processing after this “content addition” is detected, the difference detection information in the difference detection information list LDd-ps at the time of the previous backup compared this time is contrary to the case of the above “content deletion”. This is done by comparing Dd again with the difference detection information Dd having the next content ID in the difference detection information list LDd-pr at the time of this backup.

  As a more specific example, referring to FIG. 9, for example, the difference detection information Dd with content ID = “50” in the difference detection information list LDd-ps at the previous backup, and the difference detection information at the current backup After the comparison with the difference detection information Dd of the content ID = “47” in the list LDd-pr is performed and “content addition” is detected, the content ID in the difference detection information list LDd-ps at the previous backup time = Difference detection information Dd with "50" is again targeted, and comparison is made with the difference detection information Dd with content ID = "50" in the difference detection information list LDd-pr at the time of the current backup. By doing so, it is possible to appropriately detect the difference type even after “content addition” is detected.

  In addition, in the difference detection information list LDd when the content file Fct is added or deleted, there may be cases where there is difference detection information Dd that is not compared. That is, when the number of differences detection information Dd listed on the difference detection information list LDd-ps at the time of the previous backup is different from that on the difference detection information list LDd-ps at the time of the current backup, There is difference detection information Dd that does not have a comparison target. In the example of FIG. 9, the difference detection information Dd with content ID = “64” in the difference detection information list LDd-pr at the time of the current backup corresponds to this.

  In this case, whether the difference detection information Dd that is not subject to comparison exists on the difference detection information list LDd-ps side at the time of the previous backup or the difference detection information list LDd-ps side at the time of the current backup. Can be identified as content addition or content deletion.

  For example, as described above, regarding the difference detection information Dd in the difference detection information list LDd-ps at the previous backup and the difference detection information Dd in the difference detection information list LDd-pr at the current backup, As a result of comparison in order from the first difference detection information Dd, if there is no difference detection information Dd to be compared first on the difference detection information list LDd-ps at the time of the previous backup, the difference at the time of the current backup thereafter The difference detection information Dd remaining on the detection information list LDd-pr side represents the added content file Fct. Therefore, in this case, for each of the difference detection information Dd remaining on the difference detection information list LDd-pr side at the time of the current backup, the difference type is set to “content addition” as the difference information SB, and the current entry ID includes that difference. Information storing the content ID is listed in the difference information list LSB.

  On the contrary, as a result of comparison between the difference detection information Dd in the difference detection information list LDd-ps and the difference detection information Dd in the difference detection information list LDd-pr, the difference detection information list LDd at the current backup time If the difference detection information Dd on the -pr side disappears first, the difference detection information Dd remaining on the difference detection information list ldd-ps side at the time of the previous backup thereafter is the content file Fct that has been deleted. It will be what you represent. Therefore, in this case, for each of the difference detection information Dd remaining on the difference detection information list LDd-ps side at the time of the previous backup, the difference type is “content deletion” as the difference information SB, and the content is set as the previous entry ID. The information storing the ID is listed in the difference information list LSB.

  By the operation as described above, it is possible to detect the difference information by matching the index file Findex. If the difference information SB as described above is obtained, then the synchronization is performed by performing processing such as addition or deletion of the content file Fct with respect to the hard disk 127 or the backup destination recording medium 130 according to the contents of the difference information SB. Processing can be realized.

  That is, for the difference information SB whose difference type is “content addition”, the content file Fct specified by the value of the entry ID stored in the current entry ID is read from the hard disk 127 and recorded on the recording medium 130. For the difference information SB whose difference type is “content deletion”, the content file Fct specified by the entry ID stored in the previous entry ID is deleted from the recording medium 130.

  In addition, regarding the difference information SB whose difference type is “content update”, the content file Fct specified by the value stored in the previous entry ID is modified on the hard disk 127, so that the content at the time of this backup is It is the updated content file Fct. Therefore, the content file Fct specified by the previous entry ID value is deleted from the recording medium 130, and the content file Fct specified by the current entry ID value is copied from the hard disk 127 to the recording medium 130. Thereby, the storage state of the content file Fct can be synchronized between the hard disk 127 as the backup source and the recording medium 130 as the backup destination.

  Note that when the difference information SB having the difference type “entry update” is obtained, no special corresponding operation is performed in the first embodiment. However, “entry update” indicates that the entry data has been updated, and specifically indicates that, for example, metadata attached to the content file Fct has been updated. Therefore, for example, when the management of the metadata of each content file Fct recorded on the recording medium 130 is performed in the same manner as the hard disk 127 side using the management information 30b, the management is performed according to this “entry update”. The metadata managed in association with the content file Fct by the information 30b may be configured to update based on the metadata in the index file Findex on the hard disk 127 side.

2-1-3. Next, a more detailed operation of the backup process according to the first embodiment will be described with reference to the flowcharts of FIGS. 10 to 12. FIG. 10 is a flowchart illustrating an example of the overall operation of the backup processing, that is, the synchronization processing according to the first embodiment. Prior to the processing of FIG. 10, it is assumed that the backup destination recording medium 130 is loaded in the drive device 128 and is accessible. Each control and determination process shown in FIG. 10 is performed by the CPU 120 according to a predetermined program.

  In the first step S101, the CPU 120 waits for an instruction to perform a synchronization process for synchronizing the content file Fct recorded on the hard disk 127 as the backup source and the recorded contents of the backup destination recording medium 130. For example, the CPU 120 monitors whether or not a predetermined operation that instructs the operation unit 124 to perform the synchronization processing has been performed. If it is determined that an instruction to perform the synchronization process is given, the process proceeds to step S102.

  In step S102, it is determined whether or not the index file Findex created by the backup exists on the backup destination recording medium 130. If it is determined that the index file Findex does not exist on the recording medium 130, the process proceeds to step S107.

  In step S107 and subsequent step S108, processing for recording all of the content files Fct recorded on the hard disk 127 and the index file Findex on the recording medium 130 is performed. For example, in the CPU 120, the application 50 requests the file system 51 to record all the content files Fct and index files Findex recorded on the hard disk 127 on the recording medium 130 (step S107). . In response to this request, the file system 51 reads all the recorded content files Fct and index file Findex from the hard disk 127, and records and stores them in the recording medium 130 (step S108). When the process in step S108 is completed, the process proceeds to step S109.

  In step S109, the management information 30b is updated according to the storage state of the content file Fct on the recording medium 130. In this case, the management information 30b is updated so that the information of the content file Fct recorded in the recording medium 130 in the previous step S108 is reflected.

  Note that the management information 30b is recorded and held in, for example, a recording medium 130 that is a backup destination recording medium. Not limited to this, the management information 30b may be once created on the RAM 121 and recorded on the recording medium 130 when the recording medium 130 is ejected or when the video camera apparatus 100 is powered off.

  By performing the processing in the order of the above steps S101, S102, S107, S108, and S109, all the content files Fct recorded on the hard disk 127 that is the backup source and the corresponding content during the first synchronization processing The index file Findex indicating the management state of the file Fct is backed up to the recording medium 130 as the backup destination (see time t1 in FIG. 6).

  On the other hand, if it is determined in step S102 described above that the index file Findex already exists on the recording medium 130, the process proceeds to step S103. In step S103, the difference information generation information Rby described with reference to FIG. 8 is generated.

  For example, the CPU 120 reads the index file Findex from the hard disk 127 and temporarily stores it in the RAM 121. Similarly, the CPU 120 reads the index file Findex from the recording medium 130 and temporarily stores it in the RAM 121. The CPU 120 extracts predetermined items (for example, content ID, entry update date / time, content update date / time and entry ID) for the index file Findex from the hard disk 127 and the index file Findex from the recording medium 130. Then, the difference detection information Dd is generated based on the extracted information of each item, and the generated difference detection information Dd is listed, so that at the time of the current backup as shown in FIG. Difference detection information list LDd-pr and a difference detection information list LDd-ps at the time of the previous backup are generated. The difference information generation information Rdy is formed by the difference detection information list LDd-pr and the difference detection information list LDd-ps.

  As described above, in generating each difference detection information list LDd, the difference detection information Dd is sorted and listed in ascending order of the value of the content ID. Thereby, the difference type can be appropriately detected by the method described with reference to FIG.

  In the next step S104, the difference information SB is generated based on the difference information generation information Rdy obtained in step S103, and the generated difference information SB is listed to generate the difference information list LSB. Details of the process of generating the difference information list LSB will be described later. When the difference information list LSB is generated, the process proceeds to the next step S105.

  In step S105, difference file group processing is performed. In this step S105, the content file Fct is added and / or deleted in accordance with the difference type of the difference information SB as described above, so that the backup source hard disk 127 and the backup destination recording medium 130 are connected. The storage state of the content file Fct is synchronized. Details of the difference file group processing in step S105 will be described later.

  In the next step S106, the index file Findex recorded on the hard disk 127 as the backup source is recorded on the recording medium 130 as the backup destination. In this way, by recording the index file Findex recorded on the hard disk 127 on the recording medium 130, “the index file Findex at the time of the previous backup has been saved in the next synchronization processing.

  When the storage of the index file Findex ends, the process proceeds to step S109, and the management information 30b is updated according to the storage state of the content file Fct as described above. When step S109 is reached through step S103 to step S106, the information of the content file Fct recorded on the recording medium 130 is reflected as a result of the difference file group processing in step S105 described above. In addition, the information content of the management information 30b is updated.

  FIG. 11 is a flowchart illustrating an example of the generation process of the difference information SB described as step S104 in FIG. First, in step S201, the pointer value [i] and the pointer value [j] are reset, and each value is set to “0”.

  The pointer value [i] is used as a pointer that points to the difference detection information Dd to be compared with respect to the difference detection information Dd listed in the difference detection information list LDd-ps at the time of the previous backup. Each time this pointer value [i] is incremented, the difference detection information Dd to be compared is sequentially shifted in the difference detection information list LDd-ps at the previous backup. Similarly, the pointer value [j] is used as a pointer indicating the difference detection information Dd to be compared with respect to the difference detection information Dd listed in the difference detection information list LDd-pr at the time of the current backup. Each time this pointer value [j] is incremented, the difference detection information Dd to be compared in the difference detection information list LDd-pr at the time of the current backup is sequentially shifted.

  In step S202, it is determined whether or not the pointer value [i] matches the list number of difference detection information Dd in the difference detection information list LDd-ps at the time of the previous backup. This corresponds to determining whether or not the comparison has been completed for all the difference detection information Dd in the difference detection information list LDd-ps at the time of the previous backup. If it is determined that they do not match, the process proceeds to step S203.

  In step S203, it is determined whether or not the pointer value [j] matches the number of differences listed in the difference detection information Dd in the difference detection information list LDd-pr at the time of the current backup. This corresponds to determining whether or not the comparison has been completed for all the difference detection information Dd in the difference detection information list LDd-pr at the time of the current backup. If it is determined that they do not match, the process proceeds to step S204.

  In step S204, the difference detection information Dd indicated by the pointer value [i] in the difference detection information list LDd-ps at the time of the previous backup and the pointer value [j in the difference detection information list LDd-pr at the time of the current backup are displayed. ] Is equal to the difference detection information Dd. By the determination process in S204, it is determined whether or not the content file Fct recorded on the hard disk 127 has been added and / or deleted between the previous backup process and the current backup process. If it is determined in step S204 that both content IDs are equal, the process proceeds to step S205.

  Hereinafter, in order to avoid complexity, “difference detection information Dd pointed to by pointer value [i] in difference detection information list LDd-ps at the time of previous backup” is referred to as “previous information [i]”. The “difference detection information Dd pointed to by the pointer value [j] in the difference detection information list LDd-pr during the current backup” is referred to as “current information [j]”. Also, the “number of differences detection information Dd in the difference detection information list LDd-ps at the time of the previous backup” is referred to as the “number of previous listings”, and the “difference detection information list at the current backup LDd-pr The number of difference detection information Dd in the list is referred to as “current list number”.

  In step S205, it is determined whether the entry update date and time of the previous information [i] and the current information [j] are equal. That is, it is determined whether or not the entry has been updated. If it is determined that the entry update dates and times are equal, the process proceeds to step S206.

  In step S206, it is determined whether or not the content update date and time of the previous information [i] and the current information [j] are equal. That is, it is determined whether or not the content has been updated. If it is determined that the content update date and time are equal, it can be determined that the content has not been updated, and the process proceeds to step S214.

  In step S214, the pointer value [i] and the pointer value [j] are each incremented by 1, and then the process returns to step S202. That is, if it is determined in step S206 that the content has not been updated, the content file Fct recorded on the hard disk 127 is deleted and / or added between the previous backup process and the current backup process. It can be determined that neither entry update nor content update is performed. Therefore, in step S214, the pointer value [i] and the pointer value [j] are respectively incremented, and both the difference detection information list LDd-ps at the previous backup and the difference detection information list LDd-pr at the current backup both The difference detection information Dd to be compared is shifted, and the process is returned to step S202 to compare each item (content ID, entry update date / time, content update date / time) of the difference detection information Dd. To be done.

  As described above, when it is determined that there is no difference with respect to the content file Fct to be compared, the processes of step S202, step S203, step S204, step S205, and step S206 are repeated cyclically. From this, it can be seen that when there is no difference between the content files Fct that are compared with the pointer values [i] and j, the difference information SB is not added to the difference information list LSB.

  On the other hand, if it is determined in step S204 described above that the content IDs of the previous information [i] and the current information [i] are equal, the process proceeds to step S207. In step S207, it is determined whether or not the current information [j] has a larger content ID than the previous information [i]. That is, in this step S207, it is determined whether the difference type is “content addition” or “content deletion”. If it is determined that the current information [j] has a larger content ID value than the previous information [i], the difference type is “content deletion” as already described with reference to FIG. The process proceeds to step S208.

  In step S208, a process of adding difference information with the difference type “content deletion” to the difference information list SB is performed. When the difference type is “content delete”, since the current entry ID does not exist in the difference information list LSB, information indicating “content delete” is stored as the difference type, and the previous entry [i] is stored in the previous entry ID. The difference information SB storing the entry ID is added to the difference information list LSB.

  In next S209, only the pointer value [i] is incremented by 1, and the process returns to step S202.

  By the processing in step S209, the difference detection information Dd with the content ID = “34” in the difference detection information list LDd-ps at the previous backup described with reference to FIG. After the comparison with the difference detection information Dd of the content ID = “35” in the information list LDd-pr is performed and “content deletion” is detected, the difference detection information list LDd-pr at the time of the current backup The difference detection information Dd with the content ID = “35” is again targeted, and compared with the difference detection information Dd with the content ID = 35 in the difference detection information list LDd-ps at the time of the previous backup. Difference type detection after “content deletion” is detected can be appropriately executed.

  On the other hand, if it is determined in step S207 described above that the previous information [i] has a larger content ID than the current information [j], the difference type is determined to be “content addition”, and the process proceeds to step S210. To be migrated.

  In step S210, a process of adding the difference information SB with the difference type “content addition” to the difference information list LSB is performed. When the difference type is “content addition”, the previous entry ID does not exist. Therefore, here, information indicating “content addition” is stored as the difference type, and the entry ID of the current information [j] is stored in the current entry ID. The difference information SB thus added is added to the difference information list LSB.

  When the process of step S210 is completed, in the next step S211, only the pointer value [j] is incremented by 1, and the process returns to step S202.

  By the processing in step S211, the difference detection information Dd with the content ID = “50” in the difference detection information list LDd-ps at the previous backup described with reference to FIG. Content ID in the difference detection information list LDd-ps at the previous backup after “addition of content” is detected by comparison with the difference detection information Dd of the content ID = “47” in the information list LDd-pr The difference detection information Dd with “= 50” is again targeted, and the comparison process with the difference detection information Dd with the content ID = “50” in the difference detection information list LDd-pr at the time of the current backup becomes possible. . Thereby, detection of the difference type after “content addition” is detected can be appropriately executed.

  On the other hand, if it is determined in step S205 described above that the entry update dates and times are not equal, the difference type is determined to be “entry update”, and the process proceeds to step S212.

  When the difference type is “entry update”, as described with reference to FIG. 9, both the previous entry ID and the current entry ID exist in the difference information list LSB. Therefore, in this step S212, information indicating “entry update” is stored as the difference type, the entry ID of the previous information [i] is set as the previous entry ID, and the entry ID of the current information [j] is set as the current entry ID. Are added to the difference information list LSB.

  When the process of step S212 ends, the process proceeds to step S214 described above, and after incrementing the pointer value [i] and the pointer value [j] by 1, respectively, the process returns to step S202. In other words, this compares the next comparison target difference detection information Dd.

  On the other hand, if it is determined in step S206 described above that the content update dates and times are not equal, the difference type is set to “content update”, and the process proceeds to step S213.

  When the difference type is “content update”, as described with reference to FIG. 9, both the previous entry ID and the current entry ID exist in the difference information list LSB. Accordingly, in this step S213, information indicating “content update” is stored as the difference type, the entry ID of the previous information [i] is set as the previous entry ID, and the entry ID of the current information [j] is set as the current entry ID. Are added to the difference information list LSB.

  Then, the process proceeds to step S214 described above, and after incrementing pointer value [i] and pointer value [j] by 1, respectively, the process returns to step S202.

  Here, as described with reference to FIG. 9, when content is added or deleted, the difference detection information list LDd-ps at the previous backup and the difference detection information list LDd at the current backup are displayed. There is a case where the difference detection information Dd to be compared first is lost in any of -pr. As a detection operation corresponding to such a case, a determination process in steps S202 and S203 described above and a determination process in step S215 described later are provided.

  If it is determined in step S202 that the pointer value [i] matches the previous list number, the process proceeds to step S215. In step S215, determination processing is performed as to whether or not the pointer value [j] matches the current list number. That is, step S215 determines whether or not the pointer value [j] matches the list count of the difference detection information Dd in the difference detection information list LDd-pr at the time of the current backup.

  When the difference detection information Dd to be compared in the difference detection information list LDd-ps at the time of the previous backup disappears by the determination processing at steps S202 and S215, the difference detection information list at the current backup LDd-pr It is determined whether or not the difference detection information Dd to be compared still remains.

  As described with reference to FIG. 9, the difference detection information Dd to be compared is not present in the difference detection information list LDd-ps at the time of the previous backup, and the difference detection information list LDd-pr at the time of the current backup is lost. When the difference detection information Dd to be compared remains, the contents indicated by the content IDs of the difference detection information Dd remaining in the difference detection information list LDd-pr at the time of the current backup are all added contents. It will be.

  Therefore, if it is determined in step S215 that the pointer value [j] does not match the current list number, the process proceeds to step S216, and the difference information type is set to “content” in the same manner as in step S210 described above. The difference information SB that is “added” is added to the difference information list LSB. Then, the process proceeds to step S217, where only the pointer value [j] is incremented by 1, and the process returns to step S202.

  When the difference detection information Dd to be compared is lost in the difference detection information list LDd-ps at the time of the previous backup by the cyclic processing of step S202, step S215, step S216, step S217, and step S202. In addition, “add content” is detected for all the difference detection information Dd remaining in the difference detection information list LDd-pr at the time of this backup, and the corresponding difference information SB is added to the difference information list LSB. Become.

  On the other hand, if it is determined in step S203 described above that the pointer value [j] matches the current list number, contrary to the above, in the difference detection information list LDd-pr during the current backup. The difference detection information Dd to be compared is lost, and the difference detection information Dd to be compared still remains in the difference detection information list LDd-ps at the time of the previous backup. As described with reference to FIG. 9, in this case, all the contents indicated by the content ID of the difference detection information remaining in the difference detection information list LDd-ps at the time of the previous backup are all deleted. .

  Therefore, if it is determined in step S203 that the pointer value [j] matches the current list number, the process proceeds to step S218, and the difference type is set to “content deletion” as in step S208 described above. "Is added to the difference information list LSB. Then, the process proceeds to step S219, only the pointer value [i] is incremented, and the process returns to step S202.

  When the difference detection information Dd to be compared is lost in the difference detection information list LDd-pr at the time of the current backup by the cyclic processing of step S203, step S218, step S219, step S202, and step S203. In the difference detection information list LDd-ps at the time of the previous backup, “content deletion” is detected for all the difference detection information Dd remaining, and the corresponding difference information SB is added to the difference information list LSB. become.

  When the difference information SB is detected for all the difference detection information Dd of the difference detection information list LDd-ps at the previous backup and the difference detection information list LDd-pr at the current backup. In step S215 described above, it is determined that the pointer value [j] matches the current list number. As a result, a series of processes according to the flowchart illustrated in FIG. 11 is terminated, and the process proceeds to step S105 in FIG. 10 described above.

  FIG. 12 is a flowchart illustrating an example of the difference file group process in step S105 of FIG. 10 described above in more detail. First, in step S301, the pointer value [k] is reset to a value “0”. This pointer value [k] serves as a pointer for pointing to target difference information SB among the difference information SB listed in the difference information list LSB.

  In the next step S302, it is determined whether or not the pointer value [k] matches the list number of the difference information SB in the difference information list LSB. If it is determined that they do not match, the process proceeds to step S303, and the [k] -th difference information SB in the difference information list LSB is acquired. That is, the difference information SB indicated by the pointer value [k] in the difference information list LSB is acquired.

  In the next step S304, the difference type is determined based on the acquired difference information SB. That is, in step S304, based on the acquired difference information SB, it is determined whether the difference type is “content addition”, “content deletion”, “content update”, or “entry update”. The process is branched accordingly.

  If it is determined in step S304 that the difference type is “content addition”, the process proceeds to step S305. Through step S305 and the next step S306, the content file Fct corresponding to the entry of “current entry ID” on the hard disk 127 is recorded on the recording medium 130.

  For example, in step S 305, the CPU 120 requests the file system 51 to read the content file Fct from the hard disk 127 and record it on the recording medium 130. In response to this request, the content file Fct is read from the hard disk 127 and recorded in the recording medium 130 in step S306. When the recording of the content file Fct corresponding to the entry “current entry ID” on the recording medium 130 is completed, the process proceeds to step S311.

  In step S311, the pointer value [k] is incremented by 1, and the process returns to step S302.

  If it is determined in step S304 that the difference type is “content update”, the process proceeds to step S307. In step S307, the content file Fct corresponding to the entry of “previous entry ID” is deleted from the recording medium 130. Then, the process proceeds to step S308, and the content file Fct corresponding to the entry of “current entry ID” on the hard disk 127 is recorded on the recording medium 130 by step S308 and the next step S309.

  For example, in step S 308, the CPU 120 requests the file system 51 to read the content file Fct from the hard disk 127 and record it on the recording medium 130. In response to this request, the content file Fct is read from the hard disk 127 and recorded on the recording medium 130 in step S309. When the recording of the content file Fct corresponding to the entry “current entry ID” on the recording medium 130 is completed, the process proceeds to step S311 where the pointer value [k] is incremented by 1, and the process returns to step S302. .

  If it is determined in step S304 that the difference type is “content deletion”, the process proceeds to step S310. In step S310, the content file corresponding to the “previous entry ID” entry recorded in the recording medium 130 is deleted. When the content file Fct is deleted from the recording medium 130, the process returns to step S311, the pointer value [k] is incremented by 1, and the process returns to step S302.

  In the first embodiment, if it is determined in step S304 that the difference type is “entry update”, the process proceeds to step S311 as it is, and the pointer value [k] is incremented by 1. The process returns to step S302. That is, when the difference type is “entry update”, the process based on the next difference information SB is executed without executing any special process.

  However, as described above, for example, when the management of the metadata of each content file Fct recorded on the recording medium 130 is performed in the same manner as the hard disk 127 side using the management information 30b, this “entry update” is performed. Accordingly, the metadata managed in association with the content file Fct by the management information 30b may be configured to be updated based on the metadata in the index file Findex on the hard disk 127 side. .

  Specifically, the content of metadata managed in association with the content file Fct specified by the “previous entry ID” by the management information 30b is newly read from the hard disk 127 and recorded on the recording medium 130. Update processing is performed so that the content of the metadata in the entry data (in the management file slot Sm) in which “current entry ID” is stored in the index file Findex is obtained.

  If it is determined in step S302 described above that the pointer value [k] matches the list number, the series of processes in the flowchart of FIG. 12 is terminated, and the process proceeds to step S106 in FIG. 10 described above. Is done.

  In addition, according to the process demonstrated using the flowchart of the above-mentioned FIGS. 10-12, after producing | generating the difference information list LSB once by listing the difference information SB, the content file Fct based on the difference information SB is sequentially Although it has been described that processing such as addition and deletion is performed, this is not limited to this method. For example, each time the difference information SB is generated, the content file Fct based on the difference information SB may be processed.

  In the above description, when the index file Findex is stored for the next backup process in step S106 in FIG. 10, the file is stored in the recording medium 130 as the backup destination as described above. However, this is not limited to this example. The index file Findex can be temporarily stored in the RAM 121, for example. The index file Findex held in the RAM 121 is written to the recording medium 130 when the recording medium 130 is ejected from the video camera apparatus 100 or when the video camera apparatus 100 is turned off. It is possible to do. Not limited to this, the index file Findex can be stored in the nonvolatile memory 129. In this case, the correspondence relationship between the index file Findex stored in the nonvolatile memory 129 and the recording medium 130 may be further stored in the nonvolatile memory 129 or the like.

2-2. Second Embodiment of the Invention Next, a second embodiment of the present invention will be described. In the second embodiment, in addition to the backup process by the synchronization process according to the first embodiment described above, the backed up content file Fct is restored to the backup source.

  Here, the restoration process refers to a process for returning the storage state of the content file Fct in the hard disk 127 as the backup source to the storage state of the past content file Fct backed up to the recording medium 130 as the backup destination. In particular, in the second embodiment, it is assumed that the restoration process restores the previous synchronization state, that is, the process returns to the storage state of the content file Fct at the time of the previous backup.

  Here, if such a restoration process is performed by simply overwriting and copying the content file Fct group backed up on the recording medium 130 to the hard disk 127, all content files Fct recorded on the recording medium 130 are copied. It is necessary to perform processing, and much time will be required. Therefore, in the second embodiment, similarly to the backup process, the restoration process is performed based on the result of detecting the difference in the storage state of the content file Fct between the hard disk 127 side and the recording medium 130 side. I am doing so.

2-2-1. Backup Process and Restoration Process According to Second Embodiment FIG. 13 schematically shows an example of a synchronization process and a restoration process according to the second embodiment of the present invention. FIG. 13A shows an example of state transition along the time axis t for the content file Fct recorded on the hard disk 127 as the backup source. FIG. 13B similarly shows an example of state transition along the time axis t for the index file Findex, the content file Fct, and the management information 30b recorded on the recording medium 130 by the drive device 128.

  As illustrated in FIG. 13A, content files Fct “A”, “B”, and “C” are recorded as content files Fct in the initial state on the hard disk 127 that is the backup source, and the index file Findex includes It is assumed that a file having content “1” corresponding to the storage state is recorded. Further, it is assumed that a predetermined recording medium 130 is loaded in the drive device 128 as a file backup destination.

  At a time point t1 after the initial state, for example, a predetermined operation is performed on the operation unit 124 of the video camera apparatus 100, and the first synchronization processing of the recorded content of the hard disk 127 and the recorded content of the recording medium 130 is performed. The first synchronization process at time point t1 is the same as that described in the first embodiment, and a detailed description thereof is omitted here.

  After the initial synchronization processing at time t1, the content file Fct “D” is newly added to the hard disk 127 at time t2, and the content file Fct “B” is deleted from the hard disk 127 at time t3. Next, at time t4, it is assumed that the content file Fct “C” is modified and updated to the content file Fct “C ′”. Accordingly, the hard disk 127 at the time point t4 is in a state where the content files Fct “A”, “C ′”, and “D” are stored. Along with this, the contents of the index file Findex transition to contents “2”, contents “3”, and contents “4” in accordance with transitions at time t1, time t2, and time t3.

  Here, at a time point t5 after the above-described time point t4, for example, by a predetermined operation on the operation unit 124 of the video camera apparatus 100, the CPU 120 is instructed to restore based on the recorded contents backed up on the recording medium And

  In response to this restoration instruction, the CPU 120, in the same way as in the case of the synchronization processing described above, the index file Findex recorded on the hard disk 127 as the backup source and the index file Findex recorded on the recording medium 130 as the backup destination. Based on the above, the difference detection information list LDd-ps at the previous backup and the difference detection information list LDd-ps at the current backup are generated. The difference detection information Dd is compared between the difference detection information list LDd-ps at the time of the previous backup and the difference detection information list LDd-ps at the time of the current backup. Based on the comparison result, the difference information list LSB is compared. Is generated. The generated difference information list LSB is temporarily stored in the RAM 121, for example.

  Also in the second embodiment, processing of the difference file group is performed based on each difference information SB in the difference information list LSB. In the second embodiment, the storage state of the content file Fct on the recording medium 130 side is reflected on the hard disk 127 side as the restoration process, as opposed to the synchronization process, and therefore based on the difference information SB. The processing is performed in the reverse manner to the synchronization processing according to the first embodiment described above.

  This will be described more specifically with reference to FIG. Immediately before the restoration process is performed at time t5 in FIG. 13, the hard disk 127 is in a state in which the content files Fct “A”, “C ′”, and “D” are stored. On the other hand, the storage state of the content file Fct on the recording medium 130 remains unchanged as it was during the synchronization process at the time point t1, and the content files Fct “A”, “B”, and “ “C” is recorded.

  According to this, for the content file Fct “B”, the difference type is “content delete”, for the content files Fct “C” and “C ′”, the difference type is “content update”, and for the content file Fct “D”, the difference is Each difference information SB whose type indicates “content addition” is listed in the difference information list LSB.

  In this case, the difference file group processing is performed as follows. First, for a content file Fct whose difference type is “content deletion”, the content file Fct is read from the recording medium 130 and recorded on the hard disk 127. In the example of FIG. 13, the content file Fct “B” whose difference type is “content deleted” is read from the recording medium 130 and recorded on the hard disk 127, thereby deleting the content file Fct “B” on the hard disk 127 side. Can be restored.

  For the content file Fct whose difference type is “content update”, the content file Fct specified by “current entry ID” is deleted from the hard disk 127 and recorded on the recording medium 130 and specified by “previous entry ID”. Content file Fct to be read from the recording medium 130 and recorded on the hard disk 127.

  In the example of FIG. 13, for the content file Fct “C” and the content file Fct “C ′” whose difference type is “content update”, the content file Fct “C ′” is deleted on the hard disk 127 side, and the recording medium The content file Fct “C” recorded on 130 is read from the recording medium 130 and recorded on the hard disk 127. Thereby, the content file Fct “C” held at the time point t1 on the hard disk 127 side can be restored.

  For the content file Fct whose difference type is “content addition”, the content file Fct is deleted from the hard disk 127. In the example of FIG. 13, the content file Fct “D” whose difference type is “content addition” is deleted from the hard disk 127 so that the content file Fct “D” does not exist on the hard disk 127. The state at the time of synchronization processing at time t1 can be restored.

  When the processing of the content file group is performed as described above, the index file Findex on the hard disk 127 side is replaced with the index file Findex backed up on the recording medium 130 during the previous synchronization processing. That is, as shown at time t5 in FIG. 13, the index file Findex on the hard disk 127 side is the index of the content “1” read from the hard disk 127 and recorded on the recording medium 130 at time t1, which is the previous synchronization time. Replaced with the file Findex.

  As a result, the index file Findex having the information content that matches the storage state of the restored content file Fct can be recorded on the hard disk 127, and the restored content file group is properly recorded as being recorded on the hard disk 127. Be able to manage.

  In the example of FIG. 13, since the storage state of the content file Fct on the recording medium 130 has not changed from the time after the synchronization processing at the time t1 to the time when the restoration processing is performed at the time t5, the management is performed. The information content of the information 30b does not change from the content “α”.

  As described above, in the second embodiment of the present invention, the restoration process is performed by the difference file group process based on the difference information SB. As a result, only the differential content file Fct can be actually transferred, and all the content files Fct stored on the backup destination recording medium 130 are overwritten on the hard disk 127 and restored. The restoration process can be further accelerated compared to the case where the process is performed. Further, the processing load can be reduced by reducing the content files Fct to be transferred in this way.

  Furthermore, also in the second embodiment, by comparing the current index file Findex at the backup source with the index file Findex saved at the previous backup processing at the backup destination, the content file Fct of the hard disk 127 is compared. A difference between the storage state and the storage state of the content file Fct of the recording medium 130 is detected. Thus, by comparing the contents of the index file Findex of the backup source and the backup destination and obtaining the difference information, for example, the header information (content ID and content) for all the content files Findex that are actually stored. The difference information can be obtained at a higher speed than the method of obtaining the difference information by detecting the update date and time and comparing them, and in this respect, the restoration process can be speeded up.

  Furthermore, in the second embodiment, since the file related information other than the file identifier such as the content update date and time is also entered as entry data for the index file Findex, Other difference types such as “update” and “entry update” can also be acquired simply by comparing the management information. As a result, even when the difference type other than the addition and deletion of content is determined, the difference type can be determined by comparing the management information, and the difference type other than the addition and deletion of such content can be determined. A corresponding process (in this case, a restoration process for a file that is “content update”) is also accelerated.

  For the content file Fct whose difference type is “entry update”, no special processing is performed in the second embodiment. However, when the restoration process as in the second embodiment is performed, the difference type “entry update” is performed on the hard disk 127 between the previous synchronization process and the current synchronization process. This is information indicating that the metadata of the file Fct has been updated.

  Considering this, when the metadata is updated on the hard disk 127 side in this way, it may be possible to restore it to the previous synchronization state. Therefore, for example, when metadata is managed also on the recording medium 130 side, and such metadata is also restored, the corresponding metadata on the hard disk 127 side is held on the recording medium 130 side. It can also be configured to update the contents of the metadata at the time of the previous synchronization.

2-2-2. Next, a more detailed operation of the restoration process according to the second embodiment will be described with reference to the flowcharts of FIGS. 14 and 15. FIG. 14 is a flowchart illustrating an example of the overall operation of the restoration process according to the second embodiment. Prior to the processing of FIG. 14, the drive device 128 is loaded with a recording medium 130 as a backup destination, and the recording contents of the hard disk 127 as the backup source are stored in the recording medium 130 in the first embodiment described above. It is assumed that backup has already been performed in accordance with the processing according to the form.

  In the first step S401, the CPU 120 waits for an instruction to perform a restoration process for restoring the recorded contents of the hard disk 127 based on the recorded contents backed up on the recording medium 130. For example, the CPU 120 monitors whether or not a predetermined operation for instructing the operation unit 124 to perform the restoration process has been performed. If it is determined that an instruction to perform the restoration process has been given, the process proceeds to step S402.

  In step S402, the difference information generation information Rdy is generated. This process is performed in the same manner as the process of step S103 in the flowchart of FIG.

  That is, the CPU 120 reads the index file Findex from the hard disk 127 and also reads the index file Findex from the recording medium 130 and temporarily holds them in the RAM 121. The CPU 120 extracts the content ID, the entry update date / time, the content update date / time, and the entry ID for each of these index files Findex held in the RAM 121, and generates difference detection information Dd based on the information of each item. Then, by listing each of the generated difference detection information Dd, a difference detection information list LDd-pr at the current backup time and a difference detection information list LDd-ps at the previous backup time are generated. Difference information generation information Rdy is formed by the difference detection information list LDd-pr and the difference detection information list LDd-ps.

  When difference information generation information Rdy is generated in step S402, the process proceeds to step S403, difference information SB is generated based on difference information generation information Rdy, difference information SB is listed, and difference information list LSB is generated. Is generated.

  This processing in step S403 is performed in the same manner as step S104 in the flowchart of FIG. 10 described above, that is, the processing of the flowchart shown in FIG. That is, the processing in step S403 is performed by changing the content ID while shifting the difference detection information Dd to a predetermined value for each of the difference detection information list LDd-pr and the difference detection information list LDd-ps in the difference information generation information Rdy. Then, a comparison based on the entry update date and time and the content update date is performed to obtain a difference type, a previous entry ID, and a current entry ID.

  In the next step S404, a difference file group process is performed based on the difference information list LSB generated in step S403. That is, in step S404, in order to restore the state at the time of the previous synchronization, the content file Fct is added to the hard disk 127 and / or the recording medium 130 based on the difference information list LSB, and the hard disk 127 and / or the recording medium 130 The content file Fct is deleted.

  When the difference file group is processed in step S404 and the state at the time of the previous synchronization is restored, in step S405, the index file Findex backed up at the time of the previous synchronization recorded on the recording medium 130 as the backup destination is The data is recorded on the hard disk 127 that is the backup source, and the index file Findex on the hard disk 127 is replaced with the index file Findex on the recording medium 130.

  As a result, the index file Findex having information content that matches the storage state of the restored content file Fct can be recorded on the hard disk 127. On the hard disk 127 side, the restored content group can be properly managed as being recorded on the hard disk 127.

  FIG. 15 is a flowchart illustrating an example of the difference file group process in step S404 described above in more detail. First, in step S501, the pointer value [k] is reset to a value “0”. This pointer value [k] serves as a pointer for pointing to target difference information SB among the difference information SB listed in the difference information list LSB.

  In the next step S502, it is determined whether or not the pointer value [k] matches the list number of the difference information SB in the difference information list LSB. If it is determined that they do not match, the process proceeds to step S503 to acquire the [k] -th difference information SB in the difference information list LSB. That is, the difference information SB indicated by the pointer value [k] in the difference information list LSB is acquired.

  In the next step S504, the difference type is determined based on the acquired difference information SB. That is, in step S504, based on the acquired difference information SB, it is determined whether the difference type is “content addition”, “content deletion”, “content update”, or “entry update”. The process is branched accordingly. Note that each of the processes branched according to the difference type is the reverse of the process of the first embodiment described above, except when the difference type is “entry update”.

  If it is determined in step S504 that the difference type is “content addition”, the process proceeds to step S505. In step S505, the content file Fct corresponding to the “current entry ID” entry on the hard disk 127 is deleted. As a result, the content file Fct that did not exist on the hard disk 127 during the previous synchronization process is deleted from the hard disk 127, and the state of the previous synchronization process on the hard disk 127 is restored. When the process of step S504 ends, the process proceeds to step S509.

  In step S509, the pointer value [k] is incremented by 1, and the process returns to step S502.

  If it is determined in step S504 that the difference type is “content update”, the process proceeds to step S506. In step S506, the content file Fct corresponding to the entry of “current entry ID” is deleted from the hard disk 127. Then, the process proceeds to step S507, where the content file Fct corresponding to the entry of “previous entry ID” is read from the recording medium 130 and recorded on the hard disk 127. With this process, the content file Fct recorded on the hard disk 127 updated between the previous synchronization process and the current restoration process is restored to the contents of the previous synchronization process. When the process of step S507 ends, the process proceeds to step S509, the pointer value [k] is incremented by 1, and the process returns to step S502.

  If it is determined in step S504 that the difference type is “content deletion”, the process proceeds to step S508. In step S508, the content file Fct corresponding to the “previous entry ID” is read from the recording medium 130 and recorded in the hard disk 127. As a result, the content file Fct deleted from the hard disk 127 between the previous synchronization process and the current restoration process is restored. When the process of step S508 ends, the process proceeds to step S509, the pointer value [k] is incremented by 1, and the process returns to step S502.

  If it is determined in step S504 that the difference type is “entry update”, the process proceeds to step S509 as it is, the pointer value [k] is incremented by 1, and the process returns to step S502. That is, when the difference type is “entry update”, the process based on the next difference information SB is executed without executing any special process.

  However, as described above, for example, when the management of the metadata of each content file Fct recorded on the recording medium 130 is performed in the same manner as the hard disk 127 side using the management information 30b, this “entry update” is performed. Accordingly, the metadata in the index file Findex on the hard disk 127 side may be configured to be updated based on the metadata managed in association with the content file Fct by the management information 30b. .

  If it is determined in step S502 that the pointer value [k] matches the number of lists, the series of processes in the flowchart of FIG. 15 is terminated, and the process proceeds to step S405 in FIG. Is done.

2-3. Third Embodiment of the Invention Next, a third embodiment of the present invention will be described. The backup process according to the third embodiment differs from the first embodiment described above in that all the data recorded on the hard disk 127 side and previously stored in the recording medium 130 as the backup destination are recorded. The content file Fct is stored in the recording medium 130. Hereinafter, such a storage format is referred to as all content file storage.

2-3-1. Backup Process According to Third Embodiment FIG. 16 schematically shows an example backup process according to the third embodiment. FIG. 16A shows an example of state transition along the time axis t for the content file Fct recorded on the hard disk 127 as the backup source. FIG. 16B similarly shows an example of state transition along the time axis t for the index file Findex, the content file Fct, and the management information 30b recorded on the recording medium 130 by the drive device 128.

  Note that the processing on the hard disk 127 side illustrated in FIG. 16A is the same as that of the backup processing according to the first embodiment described with reference to FIG. 6A, and therefore, detailed description of overlapping portions is omitted. .

  That is, as illustrated in FIG. 16A, content files Fct “A”, “B”, and “C” are recorded as content files Fct in the initial state on the hard disk 127 that is the backup source, and the index file Findex is the index file Findex. Assume that a file having the content “1” corresponding to the storage state is recorded. After the initial state, the content file Fct “D” is added at time t2, and the content of the index file Findex is updated from the content “1” to the content “2”. At time t4, the content file Fct “B” is deleted and the content of the index file Findex is updated from the content “2” to the content “3”. Further, at time t6, the content file Fct “C” is modified and updated to the content file Fct “C ′”, and the content of the index file Findex is updated from the content “3” to the content “4”.

  On the other hand, in the example of FIG. 16, the backup process is performed at a time point t1, a time point t3, a time point t5, and a time point t7, for example, according to a predetermined operation performed on the operation unit 124 of the video camera device 100.

  When the CPU 120 detects that the content file Fct backed up from the hard disk 127 does not exist on the recording medium 130 due to, for example, the presence or absence of the backup of the index file Findex in the recording medium 130 at the time of the first backup processing at the time t1, Backup of each file recorded on the recording medium 130 is performed. That is, all the content files Fct “A”, “B”, and “C” recorded on the hard disk 127 are read from the hard disk 127 and recorded on the recording medium 130. Further, the index file Findex having the content “1” for managing the content file Fct on the hard disk 127 is read from the hard disk 127 and recorded on the recording medium 130.

  Further, in order to manage the content file Fct recorded on the recording medium 130, the CPU 120 stores the contents of the management information 30b on the recording medium 130 so that these content files Fct “A”, “B”, and “C” are stored. The content is updated to “α” for management as stored.

  The backup process at time t3 is an example of the process after the addition of the content file Fct. At time t3, since the index file Findex already exists on the recording medium 130 that is the backup destination, the CPU 120 records the index file Findex that is recorded on the hard disk 127 that is the backup source and the recording medium 130 that is the backup destination. The difference information list LSB is generated based on the index file Findex. Based on the difference information list LSB, the difference type of the content file Fct “D” on the hard disk 127 is determined as “content addition”, and the content file Fct “D” is a storage target file to be stored in the recording medium 130. Judge that there is.

  Therefore, in the backup process at this time point t3, the content file Fct “D” is read from the hard disk 127, and these read files are recorded in the recording medium 130, respectively. Further, the index file Findex is read from the hard disk 127 and overwritten on the index file Findex already recorded on the recording medium 130.

  At the same time, the management information 30b is changed from the content “α” described above to the content “β” corresponding to the storage state of the content files Fct “A”, “B”, “C”, and “D”.

  The backup process at time t5 is an example of the process after the content file Fct is deleted. Since the index file Findex already exists on the recording medium 130 that is the backup destination at time t5, as in the case of time 3 described above, the CPU 120 first determines the contents of the index file Findex on the hard disk 127 and the recording medium 130. The difference information list LSB is generated based on the contents of the index file Findex, and it is determined that the difference type of the content file Fct “B” is “content deletion” based on the generated difference information list LSB. When the difference type is only “content deletion”, the CPU 120 reads the index file Findex of the content “3” recorded on the hard disk 127 and overwrites the index file Findex already recorded on the recording medium 130. Process. The addition or deletion of the content file Fct in the recording medium 130 is not performed.

  That is, according to the difference type “content deletion”, only the backup process of the index file Findex to be compared as the previous information in the next all content saving process is performed. As a result, the content file Fct “B” that was previously stored in the recording medium 130 can be continuously stored in the recording medium 130.

  If the difference type is only “content deletion”, the content file Fct is not added or deleted from the recording medium 130 as described above, so the content of the management information 30b is also the content of the previous backup process. No change from “β”.

  The backup process at time t7 is an example of the process after updating the content file Fct. At time t7, when an instruction to perform backup processing is given, the CPU 120 generates the difference information list LSB as described above, and based on the generated difference information list LSB, the content file Fct “C ′” It is determined that the difference type is “content update”. In this case, the CPU 120 reads the updated content file Fct “C ′” on the hard disk 127 and records it on the recording medium 130. At the same time, the index file Findex having the content “4” recorded on the hard disk 127 is read, and the index file Findex already recorded on the recording medium 130 is overwritten and recorded.

  That is, when the difference type is “content update”, the updated content file Fct “C ′” and the index file Findex of the content “4” to be compared as the previous information in the next all content storage processing Is backed up to the recording medium 130. Further, the pre-update content file Fct “C” already recorded in the recording medium 130 is not deleted. As a result, the content file Fct “C” that was previously stored in the recording medium 130 can also be continuously stored in the recording medium 130.

  At this time t7, the content of the management information 30b is changed from the content “β” in the previous backup process to the content files Fct “A”, “B”, “C”, “C ′” on the recording medium 130 side. And the content “ε” corresponding to the storage state of “D”.

  Note that the processing when the difference type in the all content file saving processing is “entry update” is based on the case of the first embodiment described above.

  With the all content file saving process described with reference to FIG. 16, all the content files Fct that were previously saved on the recording medium 130 side can be saved in the recording medium 130. Even in this case, only the difference file can be actually read from the hard disk 127 and recorded on the recording medium 130, as compared with the case where it is realized by overwriting the entire content file Fct. The entire content file saving process can be further accelerated.

  Furthermore, since the content files Fct to be recorded on the recording medium 130 are reduced in this way, the processing load can be reduced. Furthermore, even in this case, the difference information SB is generated by matching the index file Findex at the time of the previous backup and the index file Findex at the time of the current backup, so that the difference information SB can be acquired at a higher speed accordingly. In this respect as well, the speed of the entire content storage process has been increased.

  Also in this case, file related information other than the file identifier such as the content update date and time is also entered in the index file Findex, and the contents of the index files Findex are compared to obtain the difference information SB. Difference types other than the addition and deletion of the content file Fct such as “content update” and “entry update” can also be acquired by simply comparing the management information. As a result, even when the difference type other than the addition or deletion of the content file Fct is determined, the difference type can be determined by comparing the management information with each other. The processing according to the type (in this case, backup processing for a file that is “content update”) is also accelerated.

2-3-2. Next, a more detailed description of the backup process according to the third embodiment will be described with reference to the flowcharts of FIG. 17 and FIG. To do. FIG. 17 is a flowchart illustrating an example of the overall operation of the backup process by saving all content files according to the third embodiment. Prior to the processing of FIG. 17, it is assumed that the backup destination recording medium 130 is loaded in the drive device 128 and is accessible. Further, each control and determination process shown in FIG. 17 is performed by the CPU 120 according to a predetermined program.

  In first step S <b> 601, the CPU 120 waits for an instruction to perform backup processing by saving all content files on the backup destination recording medium 130 of the content file Fct recorded on the hard disk 127 that is the backup source. For example, the CPU 120 monitors whether or not a predetermined operation that instructs the operation unit 124 to perform the synchronization processing has been performed. If it is determined that an instruction to perform the backup process is given, the process proceeds to step S602.

  In step S602, it is determined whether or not the index file Findex created by the backup exists on the backup destination recording medium 130. If it is determined that the index file Findex does not exist on the recording medium 130, the process proceeds to step S607.

  In step S607 and subsequent step S608, processing for recording all of the content files Fct recorded on the hard disk 127 and the index file Findex on the recording medium 130 is performed. When the process in step S608 is completed, the process proceeds to step S609.

  In step S609, the management information 30b is updated according to the storage state of the content file Fct on the recording medium 130. In this case, the management information 30b is updated so that the information of the content file Fct recorded in the recording medium 130 in the previous step S608 is reflected.

  By performing the processing in the order of the above steps S601, S602, S607, S608, and S609, all the content files Fct recorded on the hard disk 127 that is the backup source and the corresponding content during the initial backup processing The index file Findex indicating the management state of the file Fct is backed up to the recording medium 130 as the backup destination (see time t1 in FIG. 16).

  On the other hand, if it is determined in step S602 described above that the index file Findex already exists on the recording medium 130, the process proceeds to step S603 to generate the difference information generation information Rby as described above. To do.

  In the next step S604, difference information SB is generated based on the difference information generation information Rdy obtained in step S603, and the generated difference information SB is listed to generate a difference information list LSB. When the difference information list LSB is generated, the process proceeds to the next step S605, and difference file group processing is performed. In step S605, the content file Fct is added and / or deleted according to the difference type of the difference information SB as described above, and backup processing is performed by saving all content files. Details of the difference file group processing in step S605 will be described later.

  In the next step S606, the index file Findex recorded on the hard disk 127 as the backup source is recorded on the recording medium 130 as the backup destination.

  When the storage of the index file Findex ends, the process proceeds to step S609, and the management information 30b is updated according to the storage state of the content file Fct as described above. When step S609 is reached through step S603 to step S606, the information on the content file Fct recorded on the recording medium 130 is reflected as a result of the difference file group processing in step S605 described above. In addition, the information content of the management information 30b is updated.

  FIG. 18 is a flowchart illustrating an example of the difference file group process in step S605 of FIG. 17 described above in more detail. First, in step S701, among the difference information SB listed in the difference information list LSB, the pointer value [k] for indicating the target difference information SB is reset to a value “0”. In the next step S702, it is determined whether or not the pointer value [k] matches the list number of difference information SB in the difference information list LSB. If it is determined that they do not match, the process proceeds to step S703, and the [k] -th difference information SB in the difference information list LSB is acquired.

  In the next step S704, based on the acquired difference information SB, it is determined whether the difference type is “content addition”, “content deletion”, “content update”, or “entry update”. The process is branched accordingly.

  If it is determined in step S704 that the difference type is “content addition”, the process proceeds to step S705. In step S705 and the next step S706, the content file Fct corresponding to the entry of “current entry ID” on the hard disk 127 is recorded on the recording medium 130. When the recording of the content file Fct corresponding to the entry of “current entry ID” on the recording medium 130 is completed, the process proceeds to step S709, the pointer value [k] is incremented by 1, and the process returns to step S702. .

  If it is determined in step S704 that the difference type is “content update”, the process proceeds to step S707. Through step S707 and the next step S708, the content file Fct corresponding to the entry of “current entry ID” on the hard disk 127 is recorded on the recording medium 130.

  As described above, in the all content file storage according to the third embodiment, unlike the synchronization processing according to the first embodiment described above, the pre-update content file Fct stored in the recording medium 130 is not deleted. Therefore, the pre-update content file Fct that has been stored in the past can be continuously stored in the recording medium 130.

  When the recording of the content file Fct corresponding to the entry “current entry ID” on the recording medium 130 is completed, the process proceeds to step S709, the pointer value [k] is incremented by 1, and the process returns to step S702. .

  If it is determined in step S704 that the difference type is “content deletion”, the process proceeds to step S709 as it is, the pointer value [k] is incremented by 1, and the process returns to step S702. Thus, when the difference type is “content deletion”, the content file Fct deleted on the hard disk 127 side can be continuously stored on the recording medium 130 side by not performing special processing. it can.

  If it is determined in step S704 that the difference type is “entry update”, the process proceeds to step S709 as it is, the pointer value [k] is incremented by 1, and the process returns to step S702. That is, when the difference type is “entry update”, the process based on the next difference information SB is executed without executing any special process.

  If it is determined in step S702 described above that the pointer value [k] matches the list number, the series of processes in the flowchart of FIG. 18 is terminated, and the process proceeds to step S606 in FIG. 17 described above. Is done.

2-4. Next, a fourth embodiment of the invention will be described. The backup processing according to the fourth embodiment is a combination of the synchronization processing according to the first embodiment and the all content file saving processing according to the third embodiment. That is, all the content files Fct recorded on the hard disk 127 side and previously stored in the recording medium 130 as the backup destination are stored in the recording medium 130 and at the time of the backup process. The content file Fct recorded on the recording medium 130 is managed so as to be synchronized with the recorded content of the hard disk 127.

  The backup process according to the fourth embodiment can be added as an optional function of the backup process by the synchronization process according to the first embodiment described above, for example. For example, in the video camera device 100, the backup process is performed by the synchronization process according to the first embodiment by a predetermined operation on the operation unit 124, or the synchronization process and the all content file storage process according to the fourth embodiment. It may be possible to selectively set whether to perform the method by combining the methods.

2-4-1. About Backup Processing According to Fourth Embodiment FIG. 19 schematically shows an example of backup processing according to the fourth embodiment. FIG. 19A shows an example of state transition along the time axis t for the content file Fct recorded on the hard disk 127 as the backup source. FIG. 19B shows an example of state transition along the time axis t for the index file Findex, the content file Fct, and the management information 30b recorded on the recording medium 130 by the drive device 128.

  The process on the hard disk 127 side illustrated in FIG. 19A is the same as that in the case of the backup process according to the first embodiment described with reference to FIG. 6A. .

  That is, as illustrated in FIG. 19A, content files Fct “A”, “B”, and “C” are recorded as content files Fct in the initial state on the hard disk 127 that is the backup source, and the index file Findex is the index file Findex. Assume that a file having the content “1” corresponding to the storage state is recorded. After the initial state, the content file Fct “D” is added at time t2, and the content of the index file Findex is updated from the content “1” to the content “2”. At time t4, the content file Fct “B” is deleted and the content of the index file Findex is updated from the content “2” to the content “3”. Further, at time t6, the content file Fct “C” is modified and updated to the content file Fct “C ′”, and the content of the index file Findex is updated from the content “3” to the content “4”.

  On the other hand, as exemplified in FIG. 19, the backup process is performed at time t1, time t3, time t5, and time t7 in accordance with a predetermined operation performed on the operation unit 124 of the video camera device 100, for example. .

  Here, in the fourth embodiment, the management information 30b is configured such that the synchronization content file Fct and the content file Fct for storing all content files can be identified. For example, for the management information 30b, it is possible to logically provide an area for storing information on the content file Fct for synchronization and an area for storing information on the content file Fct for saving all content files. Not limited to this, in the management information 30b, a predetermined identifier is assigned to each of the file managed as the content file Fct for synchronization and the file managed as the content file Fct for storing all content files. Also good.

  In the management information 30b according to the fourth embodiment, the content file Fct managed for synchronization processing is recorded on the recording medium 130 by the backup processing based on the synchronization processing described in the first embodiment. Matches the stored state of the content file Fct. On the other hand, the management information of the content file Fct deleted from the recording medium 130 in the first embodiment at the time of the backup processing based on the synchronization processing is the storage information for all content files in the fourth embodiment. It is managed as a content file Fct and is not deleted from the recording medium 130.

  Thus, by managing the content file Fct for storing all content files separately from the content file Fct for synchronization, for example, it becomes easy to check the content file Fct that has been deleted from the hard disk 127.

  In the following, “managed as identifiable content file Fct for synchronization” will be referred to as “managed as“ for synchronization ”” as appropriate, and “identified as content file Fct for storing all content files” "Is managed as" to be stored for all content files "" as appropriate.

  When the CPU 120 detects that the content file Fct backed up from the hard disk 127 does not exist on the recording medium 130 due to, for example, the presence or absence of the backup of the index file Findex in the recording medium 130 at the time of the first backup processing at the time t1, Backup of each file recorded on the recording medium 130 is performed. That is, all the content files Fct “A”, “B”, and “C” recorded on the hard disk 127 are read from the hard disk 127 and recorded on the recording medium 130. Further, the index file Findex having the content “1” for managing the content file Fct on the hard disk 127 is read from the hard disk 127 and recorded on the recording medium 130.

  Further, the CPU 120 updates the content of the management information 30b in order to manage the content file Fct recorded on the recording medium 130. That is, the CPU 120 updates the content of the management information 30b to the content “M1” for managing the content files Fct “A”, “B”, and “C” stored on the recording medium 130. . In the content “M1”, these content files Fct “A”, “B”, and “C” are managed as “for synchronization”.

  The backup process at time t3 is an example of the process after the addition of the content file Fct. At time t3, since the index file Findex already exists on the recording medium 130, the CPU 120, the index file Findex recorded on the hard disk 127 as the backup source, and the index file Findex recorded on the recording medium 130 as the backup destination. Based on the above, a predetermined difference information list LSB is generated. Based on the difference information list LSB, the CPU 120 determines that the difference type of the content file Fct “D” on the hard disk 127 is “content addition”, and saves the content file Fct “D” in the recording medium 130. Judged to be the target file.

  Therefore, in the backup process at time t3, the content file Fct “D” is read from the hard disk 127 and recorded in the recording medium 130. Also, the index file Findex having the content “2” is read from the hard disk 127 and overwritten on the index file Findex already recorded on the recording medium 130.

  At the same time, the management information 30b is changed from the above-described content “M1” to the content “M2” corresponding to the storage state of the content files Fct “A”, “B”, “C”, and “D”.

  Here, when the state in which the content file Fct is added to the hard disk 127 side is backed up to the recording medium 130, the storage state of the content file Fct on the hard disk 127 side and the storage state of the content file Fct on the recording medium 130 side Are in a synchronized state. Therefore, in the management information 30b of the content “M2”, the content file Fct “A”, the content file Fct “B”, the content file Fct “C”, and the content file Fct “D” are managed for synchronization.

  That is, in the backup processing according to the fourth embodiment, all the content files Fct whose difference type is “content addition” may be managed for synchronization in the management information 30b. As a result, the content file Fct stored and synchronized on both the hard disk 127 side and the recording medium 130 side is appropriately managed as the “synchronization content file Fct”.

  The backup process at time t5 is an example of the process after the content file Fct is deleted. Since the index file Findex already exists on the recording medium 130 that is the backup destination at time t5, as in the case of time 3 described above, the CPU 120 first determines the contents of the index file Findex on the hard disk 127 and the recording medium 130. The difference information list LSB is generated based on the contents of the index file Findex, and it is determined that the difference type of the content file Fct “B” is “content deletion” based on the generated difference information list LSB.

  When the difference type is “content deletion”, the entire content file storage process needs to be stored continuously without deleting the corresponding content file Fct “B” recorded on the recording medium 130. is there. On the other hand, if the content file Fct “B” on the recording medium 130 is not deleted, the recorded contents differ between the hard disk 127 side and the recording medium 130 side.

  Therefore, in the fourth embodiment, the content file Fct “B” deleted on the hard disk 127 side is managed in the management information 30b as “for saving all content files”. For example, the CPU 120 moves the information of the content file Fct “B” managed as “for synchronization” at the above-described time t3 to the storage side for all content files, and changes the content of the management information 30b to the content of the time t3. The content is changed from “M2” to the content “M3” reflecting the information of the content file Fct “B”, and the management information 30b is updated.

  Also, the index file Findex having the content “3” is read from the hard disk 127 and overwritten on the index file Findex already recorded on the recording medium 130.

  The backup process at time t7 is an example of the process after updating the content file Fct. At time t7, when an instruction to perform backup processing is given, the CPU 120 generates the difference information list LSB as described above, and based on the generated difference information list LSB, the content file Fct “C ′” It is determined that the difference type is “content update”. In response to this, the CPU 120 reads the updated content file Fct “C ′” on the hard disk 127 and records it on the recording medium 130.

  When the difference type is “content update”, as in the case of the difference type “content deletion” described above, the content file Fct “C before update” recorded on the recording medium 130 is stored as the entire content file storage process. ”Must be saved continuously without being deleted. On the other hand, if the content file Fct “C” on the recording medium 130 is not deleted, the recorded contents differ between the hard disk 127 side and the recording medium 130 side.

  Therefore, in the fourth embodiment, the content file Fct “C” before update for the content file Fct “C ′” recorded on the recording medium 130 and updated on the hard disk 127 side is changed to “all”. Management information 30b is used for “content file storage”. For example, the CPU 120 manages the information of the updated content file Fct “C ′” as “for synchronization” in the management information 30b, and also manages the content file Fct “C” managed as “for synchronization” at time t5. Is managed as “for saving all content files”, the content of the management information 30b is changed from the content “M3” at the time point t5 to the content “M4” reflecting the change of the information, and the management information 30b is updated.

  Also, the index file Findex having the content “4” is read from the hard disk 127 and overwritten on the index file Findex already recorded on the recording medium 130.

  Note that the processing when the difference type in the all content file saving processing is “entry update” is based on the case of the first embodiment described above.

  By the backup processing as described with reference to FIG. 19, all the content files Fct that have been stored in the recording medium 130 in the past can be stored in the recording medium 130. In addition, in the recording medium 130, the content information Fct synchronized with the recording content on the hard disk 127 side by the management information 30b and the content file Fct for non-synchronization stored along with the all content file storage processing, Each can be managed.

  Even in this case, only the difference file can be actually read from the hard disk 127 and recorded on the recording medium 130, and the backup process can be further speeded up.

  Furthermore, since the content files Fct to be recorded on the recording medium 130 are reduced in this way, the processing load can be reduced. Furthermore, even in this case, the difference information SB is generated by matching the index file Findex at the time of the previous backup and the index file Findex at the time of the current backup, so that the difference information SB can be acquired at a higher speed accordingly. In this respect as well, the speed of the entire content storage process has been increased.

  Also in this case, file related information other than the file identifier such as the content update date and time is also entered in the index file Findex, and the contents of the index files Findex are compared to obtain the difference information SB. Difference types other than the addition and deletion of the content file Fct such as “content update” and “entry update” can also be acquired by simply comparing the management information. As a result, even when the difference type other than the addition or deletion of the content file Fct is determined, the difference type can be determined by comparing the management information with each other. The processing according to the type (in this case, backup processing for a file that is “content update”) is also accelerated.

2-4-2. Next, a more detailed description of the backup processing according to the fourth embodiment. FIG. 20 and FIG. 21 are flowcharts showing more detailed operations of the synchronization processing and backup processing by storing all content files according to the fourth embodiment. Will be described. FIG. 20 is a flowchart illustrating an example of the overall operation of the backup processing by the synchronization processing and the all content file storage processing according to the fourth embodiment. Prior to the processing of FIG. 20, it is assumed that the recording medium 130 of the backup destination is loaded in the drive device 128 and is accessible. Further, each control and determination process shown in FIG. 20 is performed by the CPU 120 according to a predetermined program.

  If it is determined in the first step S801 that an instruction to perform the backup process is given, the process proceeds to step S802, and whether or not the index file Findex created by the backup exists on the backup destination recording medium 130. Is judged. If it is determined that the index file Findex does not exist on the recording medium 130, the process proceeds to step S808.

  In step S808 and subsequent step S809, processing for recording all the content files Fct recorded on the hard disk 127 and the index file Findex on the recording medium 130 is performed. When the process in step S808 is completed, the process proceeds to step S810, and the management information 30b is updated according to the storage state of the content file Fct on the recording medium 130. In this case, the management information 30b is updated so that the information of the content file Fct recorded in the recording medium 130 in the previous step S809 is reflected.

  By performing the processing in the order of the above steps S801, S802, S808, S809, and S810, all the content files Fct recorded on the hard disk 127 that is the backup source and the corresponding content during the initial backup processing The index file Findex indicating the management state of the file Fct is backed up to the recording medium 130 as the backup destination (see time t1 in FIG. 19).

  On the other hand, if it is determined in step S802 above that the index file Findex already exists on the recording medium 130, the process proceeds to step S803, and the difference information generation information Rby is generated as described above. The difference information list LSB is generated based on the difference information generation information Rdy.

  In the next step S805, difference file group processing is performed. In step S805, the content file Fct is added and / or deleted according to the difference type of the difference information SB as described above, and the backup by the synchronization processing and all content file storage processing according to the fourth embodiment is performed. Process. Details of the difference file group processing in step S805 will be described later.

  In the next step S806, the index file Findex recorded on the hard disk 127 as the backup source is recorded on the recording medium 130 as the backup destination. In the next step S807, the management information 30b is updated so that the content file Fct is managed for “synchronization” and “for storing all content files”, respectively. For example, the management information 30b is updated so that the attribute for synchronization or for storing all content files is set to a predetermined value for each content file Fct recorded on the recording medium 130. A method of setting the attributes “for synchronization” and “for saving all content files” with respect to the pre-update Fct of the content file Fct will be described later with reference to FIG.

  In the fourth embodiment, the management information 30b is updated so that each of the “synchronization” content file Fct and “all content file storage” can be managed. That is, the management information 30b is updated so that the attribute of each content file Fct held on the recording medium 130 becomes the attribute set by the processing described later with reference to FIG. Accordingly, each content file Fct held on the recording medium 130 can be appropriately managed separately for “synchronizing” and “for storing all contents”.

  FIG. 21 is a flowchart showing an example of the difference file group process in step S805 of FIG. 20 described above in more detail. First, among the difference information SB listed in the difference information list LSB in step S901, the pointer value [k] for pointing to the target difference information SB is reset to the value “0”, and in the next step S902. Then, it is determined whether or not the pointer value [k] matches the number of list of difference information SB in the difference information list LSB. If it is determined that they do not match, the process proceeds to step S903, and the [k] -th difference information SB in the difference information list LSB is acquired.

  The next step S904 determines whether the difference type is “content addition”, “content deletion”, “content update”, or “entry update” based on the acquired difference information SB. The process is branched accordingly.

  If it is determined in step S904 that the difference type is “content addition”, the process proceeds to step S905. Through step S905 and the next step S906, the content file Fct corresponding to the entry of “current entry ID” on the hard disk 127 is recorded on the recording medium 130.

  In the next step S907, processing is performed so that the content file Fct recorded on the recording medium 130 is managed for synchronization in the management information 30b. For example, by setting the attribute of the content file Fct to “for synchronization”, the content file Fct is managed for synchronization in the management information 30b. When the process in step S907 ends, the process proceeds to step S913, the pointer value [k] is incremented by 1, and the process returns to step S902.

  If it is determined in step S904 that the difference type is “content update”, the process proceeds to step S908. In step S908, processing is performed so that the content file Fct corresponding to the entry of “previous entry ID” is managed as “for storing all content files” in the management information 30b. For example, by setting the attribute of the content file Fct to “for saving all content files”, the content file Fct is managed for saving all content files in the management information 30b.

  By the next step S909 and step S910, the content file Fct corresponding to the entry of “current entry ID” on the hard disk 127 is recorded on the recording medium 130.

  In the next step S911, when the process in step S911 for processing the content file Fct recorded in the recording medium 130 to be managed as “for synchronization” in the management information 30b is completed, the process proceeds to step S913. The pointer value [k] is incremented by 1, and the process returns to step S902.

  If it is determined in step S904 that the difference type is “content deletion”, the process proceeds to step S912. In step S912, processing is performed so that the content file corresponding to the entry of “previous entry ID” recorded in the recording medium 130 is managed as “for storing all content files” in the management information 30b. When the process of step S912 is completed, the process proceeds to step S913, the pointer value [k] is incremented by 1, and the process returns to step S902.

  In the fourth embodiment, if it is determined in step S904 that the difference type is “entry update”, the process proceeds to step S913 as it is, and the pointer value [k] is incremented by 1. The process returns to step S902. That is, when the difference type is “entry update”, the process based on the next difference information SB is executed without executing any special process.

  If it is determined in step S902 that the pointer value [k] matches the list number, the series of processes in the flowchart of FIG. 21 is terminated, and the process proceeds to step S806 in FIG. Is done.

2-5. Fifth Embodiment of the Invention Next, a fifth embodiment of the present invention will be described. In the fifth embodiment, the backup process combining the synchronization process and the entire content file storage process according to the fourth embodiment described above is performed, and the content file in the hard disk 127 at each time point when the backup is performed is performed. The storage state of Fct can be restored.

  More specifically, in the backup process according to the fourth embodiment described above, when the index file Findex on the hard disk 127 side is recorded on the recording medium 130 side at each time point when the backup process is executed, on the recording medium 130. The index file Findex at each time point during the backup process is stored in association with the time point when the backup process is performed, without overwriting the index file Findex already existing in the file. That is, the index file Findex is stored on the recording medium 130 in an associated manner for each backup process.

  At the time of restoration, recording of the content file Fct on the hard disk 127 and deletion of the content file Fct on the hard disk 127 are performed based on the index file Findex associated with the point in time when the restoration is desired. Thereby, it is possible to restore the storage state of the content file Fct at the time of the restoration to the hard disk 127 side.

2-5-1. About Backup Process and Restore Process According to Fifth Embodiment FIG. 22 schematically shows an example backup process and restore process according to the fifth embodiment. FIG. 22A shows an example of state transition along the time axis t for the content file Fct recorded on the hard disk 127 as the backup source. FIG. 22B similarly shows an example of state transition along the time axis t for the index file Findex, the content file Fct, and the management information 30b recorded on the recording medium 130 by the drive device 128.

  The process on the hard disk 127 side illustrated in FIG. 22A is the same as that of the backup process according to the first embodiment described with reference to FIG. 6A, and therefore, detailed description of overlapping parts is omitted. . Also in the fifth embodiment, as in the fourth embodiment described above, the management information 30b can identify the content file Fct for synchronization processing and the content file Fct for storing all content files. It is configured as follows.

  As illustrated in FIG. 22A, content files Fct “A”, “B”, and “C” are recorded as content files Fct in the initial state on the hard disk 127 that is the backup source, and the index file Findex includes It is assumed that a file having content “1” corresponding to the storage state is recorded.

  On the hard disk 127 side, after the initial state, the content file Fct “D” is added at the time t2, and the content of the index file Findex is updated from the content “1” to the content “2”. At time t4, the content file Fct “B” is deleted and the content of the index file Findex is updated from the content “2” to the content “3”. Further, at time t6, the content file Fct “C” is modified and updated to the content file Fct “C ′”, and the content of the index file Findex is updated from the content “3” to the content “4”.

  On the other hand, in the example of FIG. 22, the backup process is performed at time t1, time t3, and time t5. At time t1, the initial storage state of the hard disk 127 is backed up to the recording medium 130, and management information of the content “M1” is generated. At time t3, the content file Fct “D” added to the hard disk 127 at time t2 is recorded on the recording medium 130, backed up, and the contents of the management information 30b reflect the content from the content “M1”. The content is updated to “M2”. Also, at time t5, the content file Fct “B” is managed and stored in the management information 30b for storing all content files so that the content file Fct “B” is deleted from the hard disk 127 at time t4. The content “M3” is updated to the content “M4” so that the content of the information 30b reflects the fact.

  Here, in the fifth embodiment, the index file Findex read from the hard disk 127 side and recorded on the recording medium 130 at the time t1, the time t3, and the time t5 is associated with the time of each backup process. Thus, all the data is stored on the recording medium 130.

  Here, a case is considered in which, after the content file Fct “C” is corrected on the hard disk 127 side at time t6 to be the content file Fct “C ′”, restoration to an arbitrary backup time is instructed at time t7. As an example, a case will be described in which the recorded contents of the hard disk 127 at the time point when the backup process was performed at time point t3 are restored at time point t7.

  For example, the CPU 120 acquires an index file Findex associated with the designated restoration target time from among the index files Findex stored in the recording medium 130 in response to an arbitrary time restoration instruction given to the operation unit 124, for example. The difference information list LSB is created based on the acquired index file Findex and the index file Findex currently recorded on the hard disk 127. Then, the CPU 120 records and / or deletes the content file Fct on the hard disk 127 based on the difference type obtained based on the difference information list LSB, and stores the content file Fct on the hard disk 127 in the recording medium 130. The management information 30b is changed according to the state.

  In the example of FIG. 22, the index file Findex having the content “2” stored in the recording medium 130 in association with the time point 3 and the content recorded on the hard disk 127 at the time point t7 when the arbitrary time point restoration instruction is given. The index file Findex of “4” is compared, and a difference information list LSB is generated based on the comparison result. According to the difference information list LSB, the content file Fct “B” has a difference type “content delete”, and the content file Fct “C” and the content file Fct “C ′” have a difference type “content change”. Can be obtained.

  In accordance with the difference type “content deletion”, the CPU 120 determines the content file Fct specified by the “previous entry ID” (content in the example of FIG. 22) as in the case of the restoration process according to the second embodiment described above. File Fct “B”) is read from the recording medium 130 and recorded on the hard disk 127.

  Further, the CPU 120 determines the content file Fct specified by the “previous entry ID” (example in FIG. 22) in the same manner as the restoration process according to the second embodiment described above in accordance with the difference type “content update”. The content file Fct “C”) is read from the recording medium 130 and recorded on the hard disk 127, and the content file Fct specified by “current entry ID” (the content file Fct “C ′” in the example of FIG. 22) is stored in the hard disk. Delete from 127.

  By such processing, as illustrated at time t7 in FIG. 22A, the storage state of the content file Fct on the hard disk 127 side is restored to the storage state at time t3.

  Furthermore, the CPU 120 overwrites and records the index file Findex on the recording medium 130 designated at the restoration target time with respect to the index file Findex already existing on the hard disk 127. Further, the index file Findex replaced on the hard disk 127 side is further stored in the recording medium 130 in association with the time t7 that is the restoration target time.

  In the example of FIG. 22, the index file Findex having the content “2” is read from the recording medium 130 and is overwritten and recorded on the index file Findex having the content “4” on the hard disk 127.

  Further, the index file Findex having the content “2” is stored in the recording medium 130 in association with the time point t7 that is the restoration target time point. That is, on the recording medium 130, in the example of FIG. 22, each index file Findex indicating the storage state of the content file Fct on the hard disk 127 at each time point t1, time point t3, time point t5, and time point t7 is stored. It will be.

  It is necessary to update the management information 30b in accordance with the storage state of the content file Fct on the hard disk 127 side that has been changed by the restoration process at the time t7. In the example of FIG. 22, the management information 30b is updated so that the content file Fct “B” that has been managed for storing all content files at the time of the previous management information 30b update is managed as the synchronization content file Fct. (Management information 30b of content “M2” in FIG. 22B).

  As described above, in the restoration process according to the fifth embodiment, the content file Fct whose difference type is “content deletion” is managed so as to be synchronized in the management information 30b. Therefore, regarding the content file Fct whose difference type is “content deletion”, the management information 30b is updated so that it is managed for synchronization from the storage of all content files before the restoration processing.

  If the content file Fct is deleted on the hard disk 127 side between the time when the restoration instruction is given and the backup processing time immediately before the restoration instruction time, the content file is deleted for the content file Fct. It is not reflected on the recording medium 130. In the example of FIG. 22, when the content file Fct “D” is deleted from the hard disk 127 at time t6, the deletion is reflected to the recording medium 130 and the management information 30b at time t7 when the restoration process is instructed. Not. In such a case, the content file Fct is managed as it is for synchronization in the management information 30b. Therefore, in this case, even if the content file Fct is restored on the hard disk 127 side according to the restoration process, it is not necessary to update the information in the management information 30b.

  In addition, for the content file Fct whose difference type is determined to be “content update” when the restoration instruction is given, the corresponding content file Fct before update corresponding to the above-described difference type “content deletion”. Is read from the recording medium 130 and recorded on the hard disk 127 side (in the example of FIG. 22, the content file Fct “C” is moved at time t7). That is, the corresponding content file Fct before update when the difference type is determined to be “content update” (that is, the content file Fct specified by the “previous entry ID”) is also synchronized in the recording medium 130 in the same manner. The management information 30b is updated so that it can be managed.

  Note that regarding the updated content file Fct corresponding to the content file Fct whose difference type is determined to be “content update” (that is, the content file Fct specified by the “current entry ID”), the content file Fct “ As illustrated as “C ′”, when the content file Fct is not reflected on the recording medium 130, no special processing is required in the management information 30b.

  Of course, when the content file Fct “C ′” is corrected and updated to the content file Fct “C ′” and then backed up, the content file Fct “C ′” is recorded on the recording medium 130. Thus, the content file Fct is managed for synchronization in the management information 30b. In this state, when the content file Fct “C ′” is restored to a point before correction, the management of the content file Fct “C ′” is saved from the synchronization for all content files in the management information 30b. Needless to say, it needs to be changed.

  Although not shown in FIG. 22, the content file whose difference type is “content addition” is the content file Fct (added on the hard disk 127 side as in the case of the second embodiment described above. That is, the content file Fct) specified by “current entry ID” may be deleted on the hard disk 127 side.

  The processing of the content file Fct whose difference type is “content addition” is also different depending on whether or not the content file Fct is backed up on the recording medium 130 when the restoration processing is instructed.

  That is, for example, the content file Fct added to the hard disk 127 side between the backup process immediately before the restore process is instructed and the restore process instruction is not backed up to the recording medium 130 at the time of the restore process instruction. In addition, the information of the content file Fct is not reflected in the management information 30b. Therefore, for the content file Fct, no special process is required when performing the restoration process.

  On the other hand, when the backup process is performed after the content file Fct is added to the hard disk 127 side and then the restoration process is performed, the content file Fct is already recorded on the recording medium 130 and managed. The information 30b is managed for synchronization. Thereafter, when the time point before the recording of the content file Fct on the hard disk 127 side is designated as the restoration target time point, the content file Fct is managed as “for storing all content files” by the management information 30b. It should be.

  For example, when the content file “E” is added between time points t4 and t5, the content file “E” is held on the recording medium 130 side as “for synchronization” at the time of backup at time point t5. Become. In this case, when the restoration to the state at the time point t3 is performed by the arbitrary time point restoration process at the time point t7, it is understood that the content file “E” should be managed as “for storing all contents”.

  Note that the handling of the content file Fct whose difference type is “entry update” in the arbitrary time point restoration process is the same as the case of the restoration process described in the second embodiment.

  As described above, according to the fifth embodiment of the present invention, it is possible to restore the recording state of the backup source at an arbitrary time among the backup processing times performed in the past.

  At the same time, even when such a restoration process is performed on the recording medium 130 that is the backup destination, the content file Fct that is synchronized with the hard disk 127 side and the synchronization that is saved with the entire content file saving process It is possible to manage the content files Fct other than those for use.

  Further, according to the fifth embodiment, only the difference file can be actually transferred, and in this respect, the arbitrary point of time restoration process can be further accelerated. Further, the processing load can be reduced by reducing the number of content files Fct to be transferred. In addition, the difference information SB is generated by matching the contents of the index file Findex at the time of restoration and the index file Findex at the time of the current backup, so that it can be acquired at a higher speed. As a result, the speed is increased.

  Furthermore, according to the fifth embodiment, other file related information other than the file identifier such as the content update date and time is also entered in the index file Findex, and the index file Findex is recorded on the hard disk 127 side and the recording medium. The difference information SB is obtained by comparison with the 130 side. Therefore, the difference information SB can be acquired only by comparing the management information for the difference types other than the addition or deletion of the contents such as “content update” or “entry update” as the difference type. The processing according to the type of difference other than the addition or deletion of data (in this case, the restoration processing for a file that is “content update”) is also accelerated.

2-5-2. More Detailed Description of Restoration Processing According to Fifth Embodiment Next, more detailed operations of backup processing and restoration processing according to the fifth embodiment will be described with reference to the flowcharts of FIGS. FIG. 23 is a flowchart illustrating an example of the overall operation of the backup processing according to the fifth embodiment. Prior to the processing of FIG. 23, it is assumed that the backup destination recording medium 130 is loaded in the drive device 128 and is accessible. Each control and determination process shown in FIG. 23 is performed by the CPU 120 according to a predetermined program.

  In the flowchart of FIG. 23, processes other than step S1006 are the same as those described with reference to FIG. 20 in the fourth embodiment described above, and thus description thereof is omitted. That is, Steps S1001 to S1005 in FIG. 23 are the same as Steps S801 to S805 in FIG. 20, respectively, and Steps S1008 to S1010 in FIG. 23 are the same as Steps S808 to S810 in FIG. It is the same as each process. Also, the processing in step S1007 in FIG. 23 is the same as the processing in step S807 in FIG.

  In FIG. 23, in step S1006, the index file Findex recorded on the hard disk 127 as the backup source is recorded on the recording medium 130 as the backup destination, as in the process of step S806 described in FIG. To do. At this time, in the fifth embodiment, in step S1006, the index file Findex recorded on the hard disk 127 side is stored in the recording medium 130 in association with the time point when the current backup processing is performed.

  That is, as described with reference to FIG. 22, in order to be able to restore the storage state of the content file Fct in the hard disk 127 at the time of an arbitrary backup process, in step S1003 shown in FIG. An index file Findex that is read from the hard disk 127 side to generate the information Rdy and is temporarily stored in the RAM 121, for example, is stored in association with the time of the current backup process. The storage location of the index file Findex read from the hard disk 127 may be the recording medium 130, for example.

  FIG. 24 is a flowchart showing an example of the operation of restoration processing at an arbitrary time point according to the fifth embodiment. Prior to the processing of FIG. 24, the drive device 128 is loaded with a recording medium 130 as a backup destination, and the recording medium 130 at each time point when the backup instruction is given to the hard disk 127 as the backup source. It is assumed that the recorded contents have already been backed up as described with reference to FIGS.

  In the first step S1101, the CPU 120 waits for an instruction to perform processing for restoring the recording content of the hard disk 127 to the recording state at any time when the backup processing was performed. For example, if it is determined that the operation unit 124 has been instructed to perform the restoration process, the process proceeds to the next step S1102.

  In step S1102, a point in time at which the recorded content of the hard disk 127 is restored is selected. For example, the CPU 120 refers to the index file Findex at each time point stored on the recording medium 130, and acquires information indicating the time point when the backup process is performed, which is associated with each index file Findex. . The acquired information is displayed on a display device provided in the video camera device 100, for example. Based on this display, the operation unit 124 is operated to select at which time point the state is to be restored.

  In the next step S1103, the CPU 120 generates difference information generating information Rdy based on the selected information at the time of restoration. That is, the CPU 120 reads out the index file Findex corresponding to the information indicating the restoration point selected in step S1102 from the index file Findex at each point stored in the recording medium 130, and stores the index file Findex in the RAM 121, for example. From 127, the index file Findex currently recorded is read and stored in the RAM 121. Then, the CPU 120 generates a difference detection information list LDd-ps at the time of the previous backup based on the index file Findex corresponding to the information indicating the restoration time, and at the time of the current backup based on the current index file Findex of the hard disk 127. A difference detection information list LDd-pr is generated. Then, the difference information generation information Rdy is generated from the generated difference detection information list LDd-ps and the difference detection information list LDd-pr.

  In step S1104, the difference information list LSB is generated based on the difference information generation information Rdy generated in step S1103 in the same manner as described with reference to FIG.

  In the next step S1105, difference file group processing is performed based on the difference information list LSB generated in step S1104. That is, in step S1105, in order to restore the storage state of the hard disk 127 at the time of restoration selected in step S1102, recording the content file Fct on the recording medium 130 on the hard disk 127 based on the difference information list LSB, The content file Fct from 127 is deleted.

  When the difference file group is processed in step S1104 and the selected storage state at the time of restoration is restored on the hard disk 127, the process proceeds to step S1106. In step S1106, the index file Findex on the hard disk 127 that is the backup source is replaced with the index file Findex that is recorded on the recording medium 130 that is the backup destination and is backed up at the selected restoration point.

  As a result, the index file Findex having information content that matches the storage state of the restored content file Fct can be recorded on the hard disk 127. On the hard disk 127 side, the restored content group can be properly managed as being recorded on the hard disk 127.

  In the next step S1107, the management information 30b is updated by the method described with reference to FIG. 22 so that the content file Fct is managed for synchronization and for storing all content files. As a result, even when restoration processing to an arbitrary point in time is performed, each content file Fct recorded on the recording medium 130 can be managed separately for synchronization and for storing all content files.

  FIG. 25 is a flowchart illustrating an example of the difference file group process in step S1105 described above in more detail. First, in step S1201, the pointer value [k] for indicating the target difference information SB in the difference information list LSB is reset to a value “0”. The next step S1202 determines whether or not the pointer value [k] matches the number of differences information SB listed in the difference information list LSB. If it is determined that they do not match, the process proceeds to step S1203, and the [k] -th difference information SB in the difference information list LSB is acquired.

  In the next step S1204, based on the acquired difference information SB, it is determined whether the difference type is “content addition”, “content deletion”, “content update”, or “entry update”. The process is branched accordingly.

  If it is determined in step S1204 that the difference type is “content addition”, the process proceeds to step S1205. In step S1205, the content file Fct corresponding to the entry “current entry ID” on the hard disk 127 is deleted. Then, the process proceeds to the next step S1206.

  If the content file Fct corresponding to “current entry ID” has already been backed up, in step S1206, the attribute of the content file Fct is set to “for storing all content files” in the management information 30b. This is because the management information 30b manages the content files Fct for synchronization and for storing all content files, respectively, so that the content file Fct with the difference type “add content” has already been backed up to the recording medium 130. This is because the attribute of the content file Fct needs to be changed from “for synchronization” to “for storing all content files”.

  When the process of step S1206 ends, the process proceeds to step S1213. In step S1213, the pointer value [k] is incremented by 1, and the process returns to step S1202.

  If it is determined in step S1204 that the difference type is “content update”, the process proceeds to step S1207. In step S 1207, the content file Fct corresponding to the entry “current entry ID” is deleted from the hard disk 127. Then, the process proceeds to step S1208, and the content file Fct corresponding to the entry of “previous entry ID” is read from the recording medium 130 and recorded on the hard disk 127.

  In the next step S1209, the attribute of the content file Fct corresponding to the entry of “previous entry ID” is set to “for synchronization” in the management information 30b. Further, if the content file corresponding to the entry of “current entry ID” has already been backed up, the attribute of the file is set to “for storing all content” in the next step S1210. When the process of step S1210 ends, the process proceeds to step S1213, the pointer value [k] is incremented by 1, and the process returns to step S1202.

  If it is determined in step S1204 that the difference type is “content deletion”, the process proceeds to step S1211. In step S1211, the content file Fct corresponding to the “previous entry ID” is read from the recording medium 130 and recorded in the hard disk 127. In the next step S1212, the attribute of the content file corresponding to the entry of “previous entry ID” is set to “for synchronization” in the management information 30b.

  When the process of step S1212 ends, the process proceeds to step S1213, the pointer value [k] is incremented by 1, and the process returns to step S1202.

  If it is determined in step S1204 that the difference type is “entry update”, the process proceeds to step S1213, the pointer value [k] is incremented by 1, and the process returns to step S1202. That is, when the difference type is “entry update”, the process based on the next difference information SB is executed without executing any special process.

  If it is determined in step S1202 that the pointer value [k] matches the list number, the series of processes in the flowchart of FIG. 25 is terminated, and the process proceeds to step S1106 in FIG. Is done.

  In the arbitrary time point restoration process described so far, the storage state of the content file Fct on the hard disk 127 side at the time point when the restoration process is performed is not reflected on the recording medium 130 side. This is not limited to this example. For example, before executing the arbitrary time point restoration process described with reference to FIG. 24, the backup process by the synchronization process and the entire content file storage process shown in FIG. 23 is performed. The storage state of the content file Fct that has been changed on the hard disk 127 between the time of the previous backup and the time when the restoration process is viewed from the arbitrary point of time restoration process may be reflected on the recording medium 130 side. it can.

  In the above description, in order to realize a restoration process at an arbitrary time point when the backup was performed, the backup process by the synchronization process of the first embodiment and the backup process by the storage of all content files of the fourth embodiment However, this is not limited to this example. That is, in order to realize restoration to an arbitrary time point when the backup is performed, the index file Findex at each time point when the backup is performed and the recording medium 130 that is recorded on the hard disk 127 side and is the backup destination in the past. It is sufficient that all content files Fct that are to be stored are stored in the recording medium 13. Therefore, even in the backup method by storing all content files according to the third embodiment described above, the index file Findex for each backup point is stored in the recording medium 130, thereby realizing the restoration process for any point in time when the backup was performed. Is possible.

  Further, when the arbitrary time point restoration process is performed, the storage position of the content file Fct restored on the hard disk 127 side, for example, the storage position on the directory structure, is not necessarily the same position between the backup point and the restoration point. It does not always become. On the other hand, the index file Findex that is replaced on the hard disk 127 side by the arbitrary time restoration process reflects the file storage state at the time of backup.

  Therefore, there is a possibility that the storage position of the content file Fct restored on the hard disk 127 side by the restoration process does not coincide with the position indicated by the file path in the index file Findex replaced by the restoration process. Therefore, there is a possibility that the restored content file Fct cannot be accessed from the index file Findex replaced on the hard disk 127.

  Here, based on the file path when the content file Fct read from the recording medium 130 by the restoration process is recorded on the hard disk 127, the corresponding content file Fct in the index file Findex on the hard disk 127 replaced by the restoration process. If the file path in the entry data is updated, each content file Fct can be properly identified by referring to the file path thereafter.

  As another method, as the index file Findex, each content file Fct can be specified also by the content ID. Therefore, after the arbitrary time point restoration process is performed, the above-described problem can be avoided by changing the content file Fct so as to specify the content ID in the index file Findex.

  In addition, when the arbitrary point-in-time restoration process according to the fifth embodiment is performed, if the content ID is realized by a recording order to be described later, the newly created (added) content file Fct is created after the restoration process. A separate process is required to ensure that the allocated recording order does not overlap with the allocated recording order from the restoration target time point until the restoration process is performed. Note that such processing is not necessary when the content ID is realized by a combination of a file path and a file update date and time as in the previous embodiments.

2-6. Next, a sixth embodiment of the present invention will be described. In the sixth embodiment, the backup processing of the recorded contents in the hard disk 127 is performed by the method based on the entire content file storage process as already described in the third embodiment. On the other hand, in the sixth embodiment, a value called a recording order that is incremented each time a new content file Fct is added to the hard disk 127 that is the backup source is defined, and this recording order is used. The backup process is controlled easily.

  The recording order is incremented by a predetermined value, for example, 1 when a new content file Fct is added to the hard disk 127. The recording order is also incremented by a predetermined value, for example 1, even when the content file Fct already recorded on the hard disk 127 is updated. That is, the recording order is information indicating the recording order of the content file Fct with respect to the hard disk 127.

  This recording order is stored in each management file slot Sm in the index file Findex described with reference to FIG. 5, that is, in the content ID portion 64 in each entry data. That is, the recording order is handled as a content ID that uniquely identifies the content file Fct associated with the entry ID.

  In the sixth embodiment, the difference between the storage state of the content file Fct in the hard disk 127 as the backup source and the storage state of the content file Fct in the recording medium 130 as the backup destination is used using this recording order. I want to ask. That is, the difference detection is performed by comparing only the content IDs stored in the index files Findex of the hard disk 127 and the recording medium 130, respectively.

  The content file Fct is updated by, for example, temporarily storing all or a part of the target content file Fct in the RAM 121 or the like, and the content file Fct modified on the RAM 121 by the CPU 120 is stored on the hard disk 127. This is done by writing back to the original position. Therefore, the update of the content file Fct can also be regarded as a new content file Fct recorded on the hard disk 127.

  Also, the recording order having the maximum value among the recording orders corresponding to each content file Fct subjected to the backup processing corresponds to the content file Fct recorded or updated most recently at the time. In other words, the recording order having the maximum value at the time of performing the backup process corresponds to the content file Fct recorded or updated last on the hard disk 127 retroactively from the time. Hereinafter, the recording order having the maximum value when this backup is performed will be referred to as the final recording order.

  When backup is performed by all content file storage processing, only the content file Fct added or updated between the time of the previous backup processing and the time of the current backup processing needs to be specified on the hard disk 127 side.

  Therefore, in the sixth embodiment, the index file Findex on the hard disk 127 is recorded on the recording medium 130 when the recorded content of the hard disk 127 is backed up to the recording medium 130 at a certain point in time by all content file storage processing. Only the final recording order on the hard disk 127 at that time point is recorded on the recording medium 130 and held without processing.

  In the next backup process, the final recording order held on the recording medium 130 is compared with the content ID corresponding to each content file Fct stored in the index file Findex recorded on the hard disk 127. As a result of the comparison, it can be understood that the content file Fct corresponding to the recording order having a value larger than the final recording order held in the recording medium 130 is the added or updated content file Fct.

2-6-1. About Backup Process According to Sixth Embodiment FIG. 26 schematically illustrates an example backup process according to the sixth embodiment. FIG. 26A shows an example of state transition along the time axis t for the content file Fct recorded on the hard disk 127 as the backup source. FIG. 26B similarly shows an example of state transition along the time axis t for the index file Findex, the content file Fct, and the management information 30b recorded on the recording medium 130 by the drive device 128.

  The process on the hard disk 127 side illustrated in FIG. 26A is the same as that of the backup process according to the first embodiment described with reference to FIG. 6A, and thus detailed description of the overlapping parts is omitted. .

  As illustrated in FIG. 26A, the content file Fct “A”, the content file Fct “B”, and the content file Fct “C” are recorded as the content file Fct in the initial state on the hard disk 127 that is the backup source, and the index As the file Findex, a file having the content “1” corresponding to the storage state is recorded.

  Here, the content files Fct “A”, Fct “B”, and Fct “C” are given recording orders according to their recording order, and the values of the recording orders are in the corresponding management file slot Sm in the index file Findex. It is stored in the content ID section 64, respectively. As an example, the values of the recording orders of the content files Fct “A”, Fct “B”, and Fct “C” are a value “1”, a value “2”, and a value “3”, respectively. In this case, the value of the final recording order is “3”.

  Furthermore, in the example of FIG. 26A, on the hard disk 127 side, after the initial state, the content file Fct “D” is added at time t2, and the recording order value “4” of the content file Fct “D” is the final recording order. At the same time, the content of the index file Findex is updated from the content “1” in the initial state to the content “2” reflecting the recording order value “4”. At time t4, the content file Fct “B” is deleted and the content of the index file Findex is updated from the content “2” to the content “3”. In the case of file deletion, since the recording order value does not increase, there is no change in the final recording order. Further, at time t6, the content file Fct “C” is modified and updated to the content file Fct “C ′”, and the recording order value “5” of the content file Fct “C ′” is set as the final recording order. The content of the index file Findex is updated from the content “3” at time t4 to the content “4” reflecting the recording order value “5”.

  On the other hand, in the example of FIG. 26, the backup process is performed at a time point t1, a time point t3, a time point t5, and a time point t7, for example, according to a predetermined operation performed on the operation unit 124 of the video camera apparatus 100.

  In the first backup process at time t1, the CPU 120 reads the content files Fct “A”, “B”, and “C” from the hard disk 127, records them on the recording medium 130, and records the recording order value (the last recording order) ( For example, the value “3”) is recorded and held in the recording medium 130. Thus, in the sixth embodiment, it is not necessary to record the index file Findex on the recording medium 130 as in the first to fifth embodiments described above.

  The backup process at time t3 is an example of the process after the addition of the content file Fct. At the time t3, the recording order value that is stored in the recording medium 130 during the previous backup process, that is, the final recording order at the time t1, and each recording order stored in the index file Findex recorded on the hard disk 127 at the time t3. The content file Fct associated with a recording order having a value larger than the final recording order is identified.

  In the example of FIG. 26, the value of the final recording order held on the recording medium 130 at time t1 is “3”, while the content files Fct “A”, “B”, It is assumed that the recording orders of “C” and “D” have a value “1”, a value “2”, a value “3”, and a value “4”, respectively. As a result, the recording order larger than the last recording order held in the recording medium 130 has the value “4”, and the content file Fct “D” associated with the recording order is added from the time of the previous backup process. Specified as a content file Fct.

  Here, in the sixth embodiment, among the content files Fct recorded on the hard disk 127, content files having a recording order value larger than the recording order value that is the final recording order held on the recording medium 130. Information for specifying Fct is generated as a simple difference information list LSB-e as shown in FIG. In the simple difference information list LSB-e, access information for the content file Fct having a recording order with a value larger than the final recording order is listed in this way. Specifically, the file path information of each corresponding content file Fct stored in the file path section 66 stored in the index file Findex recorded in the hard disk 127 is listed.

  Note that the configuration of the simple difference information list LSB-e is not limited to the above, and a configuration in which content IDs are listed instead of file path information, for example, can be considered.

  Returning to FIG. 26, when the content file Fct added from the time of the previous backup process is specified based on the simple difference information list LSB-e as described above at the time t3, the CPU 120 specifies the identification from the hard disk 127. The read content file Fct is read and processed so as to be recorded on the recording medium 130.

  In the example of FIG. 26, the CPU 120 reads the content file Fct “D” recorded on the hard disk 127 and records it on the recording medium 130. At the same time, the CPU 120 searches for the recording order with the largest value based on the contents of the index file Findex recorded on the hard disk 127, and records and holds the searched recording order in the recording medium 130 as the final recording order. In this example, the recording order value “4” corresponding to the content file Fct “D” is held in the recording medium 130 as the final recording order.

  The backup process at time t5 is an example of the process after the content file Fct is deleted. The last recording order held in the recording medium 130 at the time t5 is the recording order value “4” held in the recording medium 130 during the backup process at the time t3 when the previous backup process was performed. On the other hand, in the hard disk 127, since the content file Fct is not added or updated from the time point t3 to the time point t5, the maximum recording order value is the value “4” corresponding to the content file Fct “D”. It remains unchanged. Since the value of the last recording order held in the recording medium 130 is equal to the maximum value of the recording order value corresponding to the content file Fct on the hard disk 127, the simple difference information list LSB-e becomes empty and is stored on the hard disk 127. Recording of the content file recorded on the recording medium 130 is not performed.

  In this case, the CPU 120 records and holds the recording order value “4” in the recording medium 130 as the final recording order based on the index file Findex recorded on the hard disk 127.

  The backup process at time t7 is an example of the process after updating the content file Fct. In this case, processing differs depending on whether or not a new recording order is assigned to the updated content file Fct.

  In the case where a new recording order is not assigned to the updated content file Fct, as a matter of course, the recording order value stored in the index file Findex recorded on the hard disk 127 does not change due to this update. Therefore, as the backup process, it is considered that the storage state of the content file Fct in the hard disk 127 has not changed between the previous backup process and the current process.

  On the other hand, when a new recording order is assigned to the updated content file Fct, the newly assigned recording order value is the maximum value for each recording order value stored in the index file Findex. It is said. Therefore, when the final recording order held in the recording medium 130 is compared with each recording order value stored in the index file Findex on the hard disk 127, the recording order value corresponding to the updated content file Fct is obtained. The recording order value is larger than the final recording order, and the corresponding content file Fct is specified as the backup target.

  In the example of FIG. 26, the content file Fct “C ′” updated at time t6 is set to the recording order value “5”, which is larger than the recording order value “4” held as the final recording order on the recording medium 130. It is a value. Therefore, the file path information of the content file Fct “C ′” is added to the simple difference information list LSB-e. Then, based on the simple difference information list LSB-e, the content file Fct “C ′” is read from the hard disk 127 and recorded on the recording medium 130. Further, based on the index file Findex recorded on the hard disk 127, the recording order value “5” having the largest value is recorded and held in the recording medium 130 as the final recording order.

  In the following, it is assumed that a new recording order is given to the updated content file Fct.

  As described above, according to the backup process using the final recording order according to the sixth embodiment of the present invention, as in the case of the third embodiment described above, it is stored in the recording medium 130 in the past. All of the target content files Fct can be stored on the recording medium 130 side. In this case, only the difference file can be actually read from the hard disk 127 and recorded on the recording medium 130. Compared to the case where all contents are overwritten and copied, the entire contents storing process is performed. Further, the processing load can be reduced by reducing the number of content files Fct to be transferred in this way.

  Furthermore, according to the backup processing according to the sixth embodiment, when generating the difference information, it is only necessary to compare the recording orders, and the hard disk 127 side as in the third embodiment described above. The difference information can be acquired at a higher speed than the case of comparing the index file Findex and the index file Findex on the recording medium 130 side, and the entire content file saving process can be further speeded up.

2-6-2. Next, a more detailed operation of the backup process according to the sixth embodiment will be described with reference to the flowcharts of FIGS. 28 to 30. FIG. 28 is a flowchart of an example showing the overall operation of the backup process using the final recording order according to the sixth embodiment. Prior to the processing in FIG. 28, it is assumed that the backup destination recording medium 130 is loaded in the drive device 128 and is accessible. Each control and determination process shown in FIG. 28 is performed by the CPU 120 according to a predetermined program.

  In the first step S1301, the CPU 120 waits for an instruction to back up the content file Fct recorded on the hard disk 127 that is the backup source to the backup destination recording medium 130 by all content file storage processing, If it is determined that an instruction has been given, the process proceeds to step S1302.

  In step S1302, it is determined whether or not the final recording order is backed up and recorded on the backup destination recording medium. If it is determined that the final recording order does not exist on the recording medium 130, the process proceeds to step S1307.

  In step S1307 and subsequent step S1308, processing for recording all of the content files Fct recorded on the hard disk 127 on the recording medium 130 is performed. Thereafter, the process proceeds to step S1309, and the final recording order is stored in the recording medium 130. That is, in step S1309, the CPU 120 sets the largest value based on each entry data in the index file Findex recorded on the hard disk 127, that is, information stored in the content ID portion 64 included in each management file slot Sm. Search for recording orders you have. The retrieved recording order is stored in the recording medium 130 as the final recording order.

  When the final recording order is stored in the recording medium 130 in step S1309, the process proceeds to step S1310, and the management information 30b is updated according to the storage state of the content file in the recording medium 130. The method for updating the management information 30b according to the sixth embodiment is the same as that in the third embodiment described above, and a detailed description thereof will be omitted.

  On the other hand, if it is determined in step S1302 that the final recording order has already been stored on the recording medium 130, the process proceeds to step S1303.

  In step S1303, the CPU 120 reads the index file Findex from the recording on the hard disk 127 that is the backup source, and in the next step S1304, based on each entry data in the read index file Findex, that is, each management file slot Sm, the simplified difference information. A list LSB-e is generated.

  In the next step S1305, difference file group processing is performed based on the simple difference information list LSB-e generated in step S1304. By this differential file group processing, the content file Fct added or updated in the hard disk 127 is recorded on the recording medium 130 between the time of the previous backup and the time of the current backup.

  Details of the method for generating the simple difference information list LSB-e in step S1304 and the difference file group processing in step S1305 will be described later.

  When the difference file processing in step S1305 is completed, the process proceeds to step S1306, and the final recording order stored on the recording medium 130 is updated. For example, the CPU 120 refers to the content ID in each entry data in the index file Findex on the hard disk 127, and acquires the recording order having the largest value as a new final recording order. The acquired new final recording order is replaced with the final recording order already stored in the recording medium 130 and stored in the recording medium 130.

  When the update of the final recording order is completed, the process proceeds to step S1310, and the management information 30b is updated according to the storage state of the content file Fct as described above.

  FIG. 29 is a flowchart showing in more detail the generation processing of an example of the simple difference information list LSB-e in step S1304 described above. In the first step S1401, the CPU 120 obtains the final recording order backed up on the recording medium 130.

  In the next step S1402, the pointer value [j] is reset to a value “0”. This pointer value [j] is used as a pointer for pointing the target entry data from each entry data entered in the index file Findex acquired from the hard disk 127 in step S1303, that is, the management file slot Sm. Play a role. In this sense, the same sign as the pointer value [j] for the difference detection information list LDd-ps at the time of the current backup as described above is given.

  In the next step S1403, it is determined whether or not the pointer value [j] matches the total number of content files recorded on the hard disk 127. That is, it is determined whether or not the pointer value [j] matches the number of entry data entered in the acquired index file Findex. If it is determined that the pointer value [j] does not match the total number of content files recorded on the hard disk 127, the process proceeds to step S1404.

  In step S1404, a recording order is acquired from the entry data of the [j] -th content file Fct. That is, the content ID stored in the content ID portion 64 in the entry data indicated by the pointer value [j] is acquired. Then, in the next step S1405, it is determined whether or not the value of the recording order acquired in step S1404 is larger than the value of the last recording order backed up acquired in step S1401.

  If it is determined in step S1405 that the value of the recording order acquired in step S1404 is larger than the value of the last recorded recording order acquired in step S1401, the process proceeds to step S1406. In other words, this means that a content file Fct recorded after the content file Fct backed up on the recording medium 130 exists on the hard disk 127.

  In step S1406, the CPU 120 refers to the file path unit 66 in the entry data indicated by the pointer value [j], and acquires the file path from the entry data of the [j] -th content. In the next step S1407, the acquired file path information is listed in the simple difference information list LSB-e described with reference to FIG. The simple difference information list LSB-e is temporarily stored in the RAM 121, for example.

  When the file path is added to the simple difference information list LSB-e in step S1407, the process proceeds to step S1408, the pointer value [j] is incremented by 1, and the process returns to step S1403.

  On the other hand, if it is determined in step S1405 that the value of the recording order acquired in step S1404 is smaller than the value of the last recorded recording order acquired in step S1401, the process proceeds to step S1408. The pointer value [j] is incremented by 1, and the process returns to step S1403.

  In other words, the content files Fct existing on the hard disk 127 are all content files Fct recorded before the content file Fct backed up on the recording medium 130, and therefore exist on the hard disk 127. This means that the file path information corresponding to the content file Fct is not added to the simple difference information list LSB-e.

  If it is determined in step S1403 that the pointer value [j] matches the total number of content files recorded on the hard disk 127, the series of processes in this flowchart is terminated, and the process proceeds to step S1305 in FIG. To be migrated.

  FIG. 30 is a flowchart showing in more detail an example of processing for the difference file group in step S1305 in FIG. 28 described above. In the first step S1501, the pointer value [m] is reset to a value “0”. This pointer value [m] serves as a pointer for indicating the target file path from the file paths listed in the simple difference information list LSB-e.

  In the next step S1502, it is determined whether or not the pointer value [m] matches the number of file path listings in the simple difference information list LSB-e. If it is determined in step S1502 that the pointer value [m] does not match the list number in the simple difference information list LSB-e, the process proceeds to step S1503.

  In step S1503, the CPU 120 obtains the [m] -th file path shown in the simple difference information list LSB-e. When the [m] -th file path is acquired, a request to read the content file Fct indicated by the acquired file path from the hard disk 127 and record it in the recording medium 130 is made in the next step S1504. This request is made to the file system 51 by the CPU 120, for example. In response to this request, the content file Fct read from the hard disk 127 is stored in the recording medium 130 in the next step S1505.

  When the storage process in step S1505 is executed, the pointer value [m] is incremented by 1 in step S1506, and the process returns to step S1502.

  On the other hand, if it is determined in step S1502 that the pointer value [m] matches the number of file paths listed in the simple difference information list LSB-e, the series of processes according to this flowchart is terminated. , The process proceeds to step S1306 in FIG. 28 described above.

  In the sixth embodiment, as illustrated in the flowcharts of FIGS. 28 to 30 described above, after the simple difference information list LSB-e is generated, the file paths are sequentially listed in the list. The content file Fct is read from the hard disk 127 and stored in the recording medium 130 every time, but this is not limited to this example. That is, even in this case, each time a difference content file Fct is specified without generating the simple difference information list LSB-e, the content file Fct is read from the hard disk 127 and stored in the recording medium 130. You can also do it. In this case, the content file Fct can be stored in the recording medium 130 collectively for all the file paths listed in the simple difference information list LSB-e.

  Further, in the sixth embodiment, information indicating the recording order in which the content file Fct is recorded on the hard disk 127 is realized by using a recording order whose value is incremented by 1 every time a new content file Fct is recorded. However, this is not limited to this example. For example, the content ID based on the combination of the file path and the file update date / time described in the first to fifth embodiments can be used as information indicating the recording order.

2-6-3. About Modification of Sixth Embodiment Next, a modification of the sixth embodiment of the present invention will be described. The sixth embodiment described above is particularly effective when the recording capacity of the recording medium 130 as the backup destination is equal to or larger than the recording capacity of the hard disk 127 as the backup source. . In the modification of the sixth embodiment, a backup processing method suitable for use when the recording capacity of the recording medium 130 as the backup destination is very small compared to the recording capacity of the hard disk 127 as the backup destination. It is to provide.

  As an example, it is assumed that the hard disk 127 built in the video camera device 100 has a recording capacity of 60 GB (Giga Byte). On the other hand, it is assumed that the backup destination recording medium 130 is a recordable DVD having a diameter of 8 cm, for example. This DVD with a diameter of 8 cm is small and excellent in portability, but has a recording capacity of about 1.5 GB. When such a recording medium 130 is used as a backup destination, as illustrated in FIG. 31, the recording contents of the hard disk 127 are sequentially and distributedly recorded on a plurality of recording media 130A, 130B,. The hard disk 127 is backed up.

  In practice, such a backup process is often performed intermittently, for example, when the user's hands are free. In this case, if the user does not remember how far the content data Fct recorded on the hard disk 127 in the video camera device 100 has been backed up at the time of the previous backup process, the user duplicates the content file Fct that has been previously backed up. Then, there is a possibility that a situation occurs in which backup is performed or forgetting which content file Fct should be backed up.

  Therefore, in the modification of the sixth embodiment of the present invention, such a situation is solved by storing the final recording order on the video camera apparatus 100 side. For example, in the sixth embodiment, the final recording order is stored in the hard disk 127 or the nonvolatile memory 129. In the following description, it is assumed that the final recording order is stored in the hard disk 127.

  A backup process according to a modification of the sixth embodiment will be schematically described with reference to FIG. The left side of FIG. 32 shows an example of the storage state of the content file Fct in the hard disk 127 that is the backup source. The content file Fct corresponding to the content ID, that is, the recording order marked with “X (X)” indicates the content file Fct deleted from the hard disk 127. 32 shows the recording media 130A, 130B,... That are backup destinations. In FIG. 32, the recording order is described as “RO”, and the final recording order is described as “LRO”.

  Here, consider a case where the recorded contents of the hard disk 127 are backed up to the recording medium 130 at the time point u1 when the content file Fct up to the recording order value “5” is recorded on the hard disk 127. At this point, it is assumed that the content file Fct having the recording order value “4” has already been deleted from the hard disk 127. In the initial state, the final recording order is not recorded on the hard disk 127. Further, when performing the backup process, the user loads a recording medium 130 </ b> A serving as a backup destination into a drive device 128 built in the video camera device 100 in advance.

  In this case, in accordance with the above-described processing of FIG. 28, when an instruction is given to perform a backup storage process for all the content file storage processes on the recording medium 130A for the content file Fct recorded on the hard disk 127 (step S1301). The CPU 120 determines whether or not the final recording order is stored in the hard disk 127 (step S1302). At this time, since the final recording order is not yet stored in the hard disk 127, the CPU 120 records all the content files Fct recorded in the hard disk 127 in the recording medium 130A for the file system 51. (Step S1307).

  In accordance with this request, the file system 51 sequentially reads the content file Fct from the hard disk 127 and records it on the recording medium 130A (step S1308). At this time, the reading order is controlled so that the reading order of the content file Fct from the hard disk 127 is in the order of recording order.

  When the recording is finished, the final recording order is stored in the hard disk 127 (step S1309). In this case, since all the content files Fct recorded on the hard disk 127 at the time point u1 are recorded on the recording medium 130A, the maximum recording order value “5” among the recording order values of the content file Fct recorded on the hard disk 127. "Is the final recording order.

  In the modification of the sixth embodiment, the management information for managing the storage state of the content file Fct in the recording medium 130A is not particularly used. Therefore, the management information update process in step SS1310 in FIG. Can be omitted. Of course, the present invention is not limited to this, and the management information may be generated or updated according to the storage state of the content file Fct in the recording medium 130A.

  Next, when the content file Fct is further recorded on the hard disk 127 and the content file Fct up to the recording order value “11” is recorded, the recorded content of the hard disk 127 is backed up to the recording medium 130. Think. At this point, it is assumed that the content file Fct having the recording order value “6” and the value “10” has already been deleted from the hard disk 127.

  First, the user loads the recording medium 130 </ b> B as a backup destination into the drive device 128. In response to an instruction to back up the content file Fct recorded on the hard disk 127 to the backup destination recording medium 130B, the CPU 120 determines whether or not the final recording order is stored in the hard disk 127. In this case, since the recording order value “5” is stored as the final recording order, the CPU 120 acquires the index file Findex recorded on the hard disk 127 (step S1303).

  The CPU 120 generates a simple difference information list LSB-e based on the acquired index file Findex (step S1304). In the example of FIG. 32, since the recording order value “5” is the final recording order, the recording order value larger than the recording order value “5”, that is, the recording order value “6” to the recording order value “11”. Are listed in the simple difference information list LSB-e.

  Then, based on the file paths listed in the simple difference information list LSB-e, the content files Fct are sequentially read from the hard disk 127 in the order of recording order and recorded on the recording medium 130B (step S1305). When the content file Fct corresponding to the recording order value “11” is recorded on the recording medium 130B, the recording order value “11” is stored in the hard disk 127 as the final recording order (step S1306).

  As described above, it can be understood that the backup process according to the sixth embodiment described above can be performed without any problem even if the final recording order is recorded on the hard disk 127 side as the backup source.

  Here, when the recording capacity of the recording medium 130 as the backup destination is much smaller than the recording capacity of the hard disk 127 as the backup source, the recordable capacity in the recording medium 130 during the backup processing is the data of the content file Fct. It can be considered that the backup processing is interrupted because the size becomes smaller than the size.

  In the modification of the sixth embodiment, the backup process can be executed without any problem even in such a case. As an example, in the difference file group processing in step S1305 of FIG. 28, the file system 51 controls recording while checking the file size of the content file Fct to be recorded and the free capacity of the recording medium 130A, for example, and then recording. If it is determined that the content file Fct to be recorded cannot be recorded on the recording medium 130A, the recording of the content file Fct may be terminated. For example, when the recording is completed, the process is forcibly shifted from step S1305 to step S1306, and the largest recording order value of the content file Fct for which backup has been completed is stored in the hard disk 127 as the final recording order. Like that.

  In the example of FIG. 32, when the content file Fct with the recording order value “8” is completely recorded during the backup process at the time point u2, the content file Fct with the next recording order value “9” is stored. Consider a case where there is not enough free space on the recording medium 130B to record. In this case, when the recording of the content file Fct having the recording order value “8” is completed, the backup processing is interrupted, and the recording order value “8” is stored in the hard disk 127 as the final recording order. The next backup process can be started from the content file Fct having the next recording order value “9” based on the final recording order.

  Furthermore, by applying this method, it is possible to easily perform a process for distributing and backing up content files Fct accumulated in a large amount on the hard disk 127 to the recording media 130A, 130B,. be able to.

  That is, while performing the backup process as described above, the file system 51 constantly monitors the free capacity of the backup destination recording medium 130, and the recording medium 130 has enough free capacity to record the next content file Fct. If not, recording is terminated at that time, and the maximum recording order value among the recording order values corresponding to the content file Fct for which recording has been completed is stored in the hard disk 127 as the final recording order. Then, when the recording medium 130 is replaced and the next backup is resumed, the backup process is controlled based on the final recording order.

  As described above, by controlling the backup of the content file Fct recorded on the hard disk 127 based on the final recording order stored on the hard disk 127 side as the backup source, the backup having a smaller recording capacity than the backup source. Even when backup is performed in a distributed manner, backup processing without omission or duplication can be easily realized.

3. Modifications to Embodiments of the Invention Although the embodiments of the present invention have been described above, the present invention should not be limited to the above-described embodiments. For example, in the above description, the index file Findex, which is management information for managing the content file Fct recorded at the backup source, includes file related information other than the content ID, which is an identifier for identifying the managed content file Fct. However, this is not limited to this example. For example, the present invention can also be suitably applied when the index file Findex is configured as management information in which file related information other than these file identifiers is not entered.

  In each of the above-described embodiments, the content file Fct backed up from the hard disk 127 as the backup source is managed by the management information 30b different from the index file Findex in the recording medium 130 as the backup destination. This is not limited to this example.

  For example, without using such separate management information, each content file Fct stored in the backup destination can be managed by the index file Findex backed up from the hard disk 127 as the backup source. For example, when synchronization processing is performed as in the first embodiment described above, it may be configured to store each content file Fct with the same directory structure on the hard disk 127 side and the recording medium 130 side. It is done.

  Further, the above-described synchronization processing according to the fourth embodiment and the backup processing based on the entire content file storage processing can be combined with the previous synchronization state restoration processing according to the second embodiment. In this case, if it is a restoration process in the previous synchronization state, the process of saving the index file Findex in association with each backup time can be omitted. For example, the backup process by the all content file storage process according to the third embodiment and the restoration process of the previous synchronization state according to the second embodiment can be combined.

  Further, in the above description, the recording medium 130 as the backup destination is described as being loaded into the drive device 128 built in the video camera device 100, but this is not limited to this example. For example, a recording device that is recognized as an external storage device of the video camera device 100 by being connected to the CPU 120 through a predetermined interface via the communication unit 125 is used as the backup destination recording medium 130. be able to.

  Furthermore, in the above description, the present invention has been described as applied to a portable video camera device, but this is not limited to this example. That is, the present invention can be applied to other types of electronic devices as long as two or more different recording media can be used in parallel in one housing.

  For example, the present invention can be applied to a digital still camera in which a still image is mainly captured using an image sensor and recorded on a recording medium. In addition, for example, in recent years, products in which an imaging element and a recording or storage medium are provided in a mobile phone terminal and a still image and a moving image can be captured and recorded have become widespread. As a recording or storage medium, a model incorporating a small hard disk has appeared. The present invention can also be applied to such a mobile phone terminal with an imaging function.

It is a basic diagram for demonstrating the usage type of an example of the video camera apparatus as a recording device or recording / reproducing apparatus to which this invention was applied. It is a block diagram which shows the structure of an example of the video camera apparatus applicable to each embodiment of invention. It is a basic diagram which shows the general system structure of a FAT file system by a hierarchy model. It is a basic diagram which shows the management structure of an example of the file recorded on the hard disk of a video camera apparatus. It is a basic diagram which shows an example file management form using the index file Findex as exclusive management information applicable to each embodiment of this invention. It is an approximate line figure showing typically an example of synchronous processing in a video camera device by a 1st embodiment of this invention. It is a basic diagram which shows the structure of an example of the information list for difference detection LDd for performing a difference detection. It is a basic diagram which shows and compares two difference detection information lists LDd generated at the time of backup processing. It is an approximate line figure showing typically detection operation of difference information using information Rdy for difference information generation. It is an example flowchart which shows the whole operation | movement of the synchronous process of 1st Embodiment. It is a flowchart which shows the production | generation process of an example of difference information SB. It is a flowchart of an example which shows the difference file group process by the 1st Embodiment in detail. It is an approximate line figure showing typically an example of synchronous processing and restoration processing by a 2nd embodiment of an invention. It is an example flowchart which shows the whole operation | movement of the decompression | restoration process by the 2nd Embodiment. It is a flowchart of an example which shows the difference file group process by the 2nd Embodiment in detail. It is a basic diagram which shows typically the example backup processing by 3rd Embodiment. It is a flowchart of an example which shows the whole operation | movement of the backup process by all the content file preservation | saves by 3rd Embodiment. It is a flowchart of an example which shows the difference file group process by the 3rd Embodiment in detail. It is a basic diagram which shows typically the example backup processing by 4th Embodiment. It is a flowchart of an example which shows the whole operation | movement of the backup process by the synchronous process by the 4th Embodiment, and all the content file preservation | save processes. It is a flowchart of an example which shows the difference file group process by the 4th Embodiment in detail. It is an approximate line figure showing typically an example of backup processing and restoration processing by a 5th embodiment. It is a flowchart of an example which shows the whole operation | movement of the backup process by the 5th Embodiment. It is a flowchart which shows operation | movement of an example of the decompression | restoration process in the arbitrary time points according to Embodiment 5. It is a flowchart of an example which shows the difference file group process by the 5th Embodiment in detail. It is a basic diagram which shows typically the example backup processing by the 6th Embodiment. It is an approximate line figure showing an example of simple difference information list LSB-e. It is a flowchart of an example which shows the whole operation | movement of the backup process using the last recording order by 6th Embodiment. It is a flowchart which shows the production | generation process of an example of simple difference information list LSB-e in detail. It is a flowchart which shows an example of the process with respect to the difference file group by the 6th Embodiment in detail. It is a basic diagram for demonstrating schematically the modification of the 6th Embodiment. It is an approximate line figure for explaining roughly backup processing by a modification of a 6th embodiment.

Explanation of symbols

DESCRIPTION OF SYMBOLS 11 Optical system 12 Case of video camera apparatus 13 Recording medium 14 Drive apparatus 15 Recording medium 100 Video camera apparatus 120 CPU
121 RAM
124 Operation input unit 127 Hard disk 128 Drive device 129 Non-volatile memory 130 Recording medium

Claims (27)

A first recording unit for recording data on a first recording medium;
A second recording unit for recording data on the second recording medium;
The recording of data on the first recording medium by the first recording unit and the recording of data on the second recording medium by the second recording unit are controlled and recorded on the first recording medium The first management information including the identification information that can uniquely identify the data to be recorded and managing the data is generated at least every time data is recorded on the first recording medium. A recording control unit adapted to record on a recording medium,
The recording control unit
In the process of reflecting the recording state of the data on the first recording medium on the second recording medium, information corresponding to the first management information recorded on the first recording medium is stored in the second Is stored as a predetermined management information,
A process of reflecting the recording state of data on the first recording medium on the second recording medium based on difference information obtained by comparing the first management information and the second management information; A recording apparatus for controlling. The recording apparatus according to claim 1,
The recording apparatus, wherein the first management information is generated every time a recording state of data on the first recording medium changes. The recording apparatus according to claim 1,
The recording apparatus, wherein the second recording medium is removable from a housing. The recording apparatus according to claim 1,
The recording apparatus, wherein the first recording medium is detachable from a housing. The recording apparatus according to claim 1,
A communication unit capable of data communication with the outside is further provided.
The recording apparatus, wherein the second recording medium is connected to be controllable by the recording control unit via the communication unit. The recording apparatus according to claim 1,
The recording apparatus, wherein the second management information is recorded on the second recording medium. The recording apparatus according to claim 6, wherein
The difference information is at least
A first difference information type indicating addition of data to the first recording medium; a second difference information type indicating deletion of data recorded on the first recording medium; and the first recording medium. A recording apparatus comprising: a third difference information type indicating update of recorded data. The recording apparatus according to claim 6, wherein
The recording apparatus according to claim 1, wherein the first management information further includes information indicating an update time of data recorded on the first recording medium. The recording apparatus according to claim 6, wherein
The recording control unit
Based on the difference information, the first recording unit and the second recording unit are configured so that the recording state of the data on the second recording medium matches the recording state of the data on the first recording medium. A recording apparatus, wherein the recording state of the data on the first recording medium is reflected on the second recording medium by controlling. The recording apparatus according to claim 9, wherein
The recording control unit is based on the difference information,
Of the data present on the first recording medium, data for which no corresponding data exists on the second recording medium is read from the first recording medium and recorded on the second recording medium,
Of the data present on the second recording medium, the first recording unit and the first so as to delete from the second recording medium data for which no corresponding data exists on the first recording medium. A recording apparatus that controls two recording units. The recording apparatus according to claim 9, wherein
The recording control unit
Based on the difference information, the first recording unit and the second recording unit are configured so that the recording state of the data on the first recording medium matches the recording state of the data on the second recording medium. A recording apparatus, wherein the recording state of the data on the first recording medium is restored to the reflected state on the second recording medium by the process of reflecting by controlling. The recording apparatus according to claim 11,
The recording control unit is based on the difference information,
Of the data present on the second recording medium, data that does not have corresponding data on the first recording medium is read from the second recording medium and recorded on the first recording medium,
Of the data existing on the first recording medium, the first recording unit and the second recording unit are configured to delete data for which no corresponding data exists on the second recording medium from the first recording medium. A recording apparatus for controlling the recording unit. The recording apparatus according to claim 11,
The recording control unit records the second management information recorded on the second recording medium after the restoration by replacing the first management information with the first management information on the first recording medium. A recording apparatus. The recording apparatus according to claim 6, wherein
The recording control unit
Based on the difference information, out of the data present on the first recording medium, data for which no corresponding data exists on the second recording medium is read from the first recording medium and the second recording is performed. By controlling the first recording unit and the second recording unit to record on the medium, the recording state of the data on the first recording medium is reflected on the second recording medium. A recording apparatus characterized by that. The recording apparatus according to claim 14, wherein
Data for which there is no corresponding data on the second recording medium is that data added to data managed in the second management state and data managed in the second management state are changed. A recording apparatus comprising the recorded data. The recording apparatus according to claim 14, wherein
According to the process to reflect, the recording control unit,
A recording apparatus characterized in that, among data recorded on the second recording medium, data for which no corresponding data exists on the first recording medium is managed in a predetermined manner. The recording apparatus according to claim 14, wherein
The recording control unit
A recording apparatus characterized in that the second management information is accumulated and recorded on the second recording medium in association with each process to be reflected. The recording apparatus according to claim 17, wherein
The recording control unit
Based on the difference information obtained by comparing the second management information associated with the selected process to be reflected and the first management information, the recording state of the data on the first recording medium is determined. Recording the data on the first recording medium by controlling the first recording unit and the second recording unit so as to coincide with the recording state of the data managed by the second management information A recording apparatus that restores a state to a state managed by the second management information associated with the selected process to be reflected. The recording apparatus according to claim 1,
The recording apparatus, wherein the identification information includes a value indicating a recording order of data on the first recording medium. The recording apparatus according to claim 19, wherein
The value indicating the recording order is incremented according to data recording on the first recording medium and update of data recorded on the first recording medium. The recording apparatus according to claim 19, wherein
The recording control unit, during the process of reflecting,
A recording apparatus characterized in that, of the first management information, only the identification information having the maximum value is stored as the second management information in a predetermined manner. The recording apparatus according to claim 21, wherein
The recording control unit is based on the difference information,
Data recorded on the first recording medium corresponding to identification information having a value larger than the value indicated by the identification information included in the second management information among the first management information is recorded in the first management information. By controlling the first recording unit and the second recording unit so as to read from the recording medium and record on the second recording medium, the recording state of data on the first recording medium is changed to the first recording unit. A recording apparatus characterized in that the above-mentioned reflection is applied to two recording media. The recording apparatus according to claim 19, wherein
The recording apparatus, wherein the second management information is recorded on the second recording medium. The recording apparatus according to claim 19, wherein
The recording apparatus, wherein the second management information is recorded on the first recording medium. The recording apparatus according to claim 19, wherein
It is further equipped with a non-volatile memory capable of holding stored contents without power supply,
The recording apparatus, wherein the second management information is stored in the nonvolatile memory. The first management information for managing the data including the identification information that can uniquely identify the data recorded on the first recording medium is recorded at least every time data is recorded on the first recording medium. Generated and recorded on the first recording medium,
In the process of reflecting the recording state of the data on the first recording medium on the second recording medium, information corresponding to the first management information recorded on the first recording medium is stored in the second It is to be stored as management information in a predetermined manner,
A process of reflecting the recording state of data on the first recording medium on the second recording medium based on difference information obtained by comparing the first management information and the second management information; Recording method characterized by performing. The first management information for managing the data including the identification information that can uniquely identify the data recorded on the first recording medium is recorded at least every time data is recorded on the first recording medium. Generated and recorded on the first recording medium,
In the process of reflecting the recording state of the data on the first recording medium on the second recording medium, information corresponding to the first management information recorded on the first recording medium is stored in the second It is to be stored as management information in a predetermined manner,
A process of reflecting the recording state of data on the first recording medium on the second recording medium based on difference information obtained by comparing the first management information and the second management information; A recording program for causing a computer device to execute a recording method.

Images