JP2007241790A - Data backup processing unit and method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To secure data already backed up even when processing cannot be continued due to a failure in backup processing. <P>SOLUTION: A backup processing unit 1 for backing up backup object data stored in a memory card 2, to a CD 3, computes the capacity of the CD 3 required when backing up the backup object data by dividing it into a plurality of sessions, determines the divided number of sessions based on the computed required capacity and the free space of the CD 3, and divides the backup object data into the divided number of sessions to copy it from the memory card 2 to the CD 3. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a technique for backing up data stored in a certain recording medium to another recording medium, and more particularly to a technique for reducing the risk of data loss when backup fails.

  Image data taken by an electronic still camera (so-called digital camera), a digital video camera, or the like is first stored in a semiconductor memory or the like stored in the camera. Then, after the user backs up the image data stored in the semiconductor memory to another recording medium such as a CD or a DVD, the user erases the image data and repeatedly uses the semiconductor memory.

  In other words, with the widespread use of electronic still cameras and digital video cameras, opportunities for general users to back up large amounts of data are rapidly increasing.

  For example, when backing up to a CD or the like and erasing the original data from the storage medium storing the original data, if an error occurs during the backup and the backup process is not completed, the data written to the CD is All will be lost.

Therefore, Patent Document 1 discloses a system for automatically continuing the backup process so that the logical alignment of data is maintained in such a case.
JP-A-9-305974

  In recent years, battery-driven portable terminals capable of backup processing have been put into practical use. When this terminal is used, there is a high probability that an error will occur due to the battery running out in the middle of the backup process or an external impact. In such a case, the backup process cannot be continued as in Patent Document 1.

  Therefore, an object of the present invention is to ensure data that has already been backed up even when backup processing fails and processing cannot be continued.

  Another object of the present invention is to make it possible to read a part of data even when the backup is completed normally or when the recording medium is physically damaged due to scratches or dirt.

  A backup processing apparatus according to an embodiment of the present invention is a backup processing apparatus for backing up backup target data stored in a first storage medium to a second storage medium, and the backup processing data is stored in a plurality of backup target data. Division for calculating the capacity of the second storage medium required for backup by dividing into sessions, and determining the number of divided sessions based on the calculated necessary capacity and the free capacity of the second storage medium Means, and copy means for copying the backup target data from the first storage medium to the second storage medium in accordance with the number of divided sessions.

  As a result, the backup target data can be backed up in a plurality of sessions, and the risk of losing data even if a trouble occurs during the backup is reduced.

  In a preferred embodiment, the dividing unit may determine the number of divisions by dividing the backup target data into sessions for each subdirectory of the first hierarchy in the root directory.

  In a preferred embodiment, the dividing unit may further divide a session for each subdirectory under the second hierarchy under the subdirectory of the first hierarchy to determine the number of divisions.

  In a preferred embodiment, when a plurality of files are included in the same directory, the number of divided sessions may be determined by further dividing sessions according to the creation date of each file.

  In a preferred embodiment, when a plurality of image files taken with a digital camera are included in the same directory, the session division is further performed by dividing the session according to incidental information relating to the shooting conditions included in each image file. The number may be determined.

  In a preferred embodiment, the second storage medium may follow a CD-ROM file system.

  Hereinafter, a backup processing apparatus according to an embodiment of the present invention will be described with reference to the drawings.

  FIG. 1 is a functional configuration diagram of a backup processing apparatus 1 according to the present embodiment.

  That is, the backup processing device 1 performs data backup by copying the backup target data stored in the first storage medium to the second storage medium. In the present embodiment, a case where data stored in the memory card 2 is backed up to a CD will be described as an example. However, the first and second storage media may be other than these.

  The backup processing apparatus 1 is configured by, for example, a general-purpose computer system, and individual components or functions in the backup processing apparatus 1 described below are realized by executing, for example, a computer program.

  Further, the backup processing apparatus 1 can be realized as a single apparatus, or can be incorporated into another apparatus such as a printer, a digital multifunction peripheral, a viewer, and can be realized as a partial function of the apparatus. It can also be realized in combination with an electronic still camera or digital video camera by using a part of functions such as a still camera or a digital video camera.

  The backup processing apparatus 1 shown in FIG. 1 includes a backup management unit 11, a memory card reader / writer 12, and a CD reader / writer 13.

  The memory card reader / writer 12 reads data stored in the memory card 2 and writes data to the memory card 2.

  The CD reader / writer 13 reads data stored in the CD 3 and writes data to the CD 3.

  The backup management unit 11 performs processing for backing up the backup target data stored in the memory card 2 to the CD 3. For example, when the capacity of the backup target data is large and the backup process takes time, the backup management unit 11 divides the data based on a predetermined rule. Then, backup is performed by dividing the divided data into a plurality of sessions, each as a unit. The division of the backup target data will be described later.

  FIG. 2 shows an example of a directory structure stored in the memory card 2.

  As shown in the figure, the memory card 2 has a “DCIM” directory 211 and a “MISC” directory 212 as subdirectories in the first hierarchy 21 immediately below the root directory 200. In the second hierarchy 22 under the “DCIM” directory 211, there are a “100ABCDE” directory 221 and a “101ABCDE” directory 222 which are subdirectories. Then, five image files 251 exist in the “100ABCDE” directory 221, and two image files 252 exist in the “101ABCDE” directory 222. Furthermore, one text file (“AUTPRINT.MRK”) 253 exists in the “MISC” directory 212.

  The data structure of CD3 when the data included in the directory structure shown in FIG. 2 is backed up to CD3 as backup target data will be described.

  FIG. 3 shows a data structure of the backup data 30 when the backup target data shown in FIG. 2 is backed up to the CD 3 in one session.

  CD3 has a structure according to the CD-ROM file system. Therefore, management areas 301 and 302 according to the CD-ROM file system are provided at the beginning and end of the backup data 30.

  In the present embodiment, a CD conforming to the ISO9660 level 1 standard will be described as an example. However, the present invention can be applied to other standards (for example, ISO9660 level 2, Joliet, etc.) that are expanded. .

  The backup data 30 is provided with a root directory entry 310, subdirectories “DCIM” directory 211, and “MISC” directory 212 directory entries 311 and 312 following the top management area 301.

  Since there is no subdirectory in the “MISC” directory 212, the data body 353 of the text file 253 is stored following the directory entry 312.

  Subsequently, the directory entry 321 of the “100ABCDE” directory 221 and the data body 351 of the image file 251 in the “100ABCDE” directory 221, the directory entry 322 of the “101ABCDE” directory 222, and the “101ABCDE” directory 222 The data body 352 of the image file 252 is stored.

  In the range described above, all of the directory and data body of the backup target data are included. In the case of the CD-ROM file system, a path table 330 indicating the directory structure of all data stored in the CD 3 is further provided.

  The path table 330 is for representing all data included in the CD3 in a tree structure as shown in FIG. 2 when the backup data 30 is stored in the CD3. Therefore, for example, when the backup data 30 is written to a new CD 3, the path table 330 represents the tree structure shown in FIG.

  FIGS. 5 to 9 show the data structures of the directory entries 310, 311, 312, 321, and 322 of the root directory, “DCIM” directory, “MISC” directory, “100ABCDE” directory, and “101ABCDE” directory.

  Each directory entry 310, 311, 312, 321, 322 has a pointer record 3101, 3111, 3121, 3211, 3221 pointing to its own sector and a pointer record 3102, 3112, 3122, 3212 pointing to the sector of the parent directory. , 3222 are included, and the data length of each is fixed to 34 bytes.

  Furthermore, when each directory entry 310, 311, 312, 321, 322 includes a subdirectory directly under each directory, subdirectory records 3103, 3113 are included, and a file immediately below each directory is included. When there is, file records 3124, 3214, 3224 are included.

  Each of the subdirectory records 3103 and 3113 includes a pointer indicating a sector in which the directory entry of the subdirectory is stored and a subdirectory name. The record length is variable and has a maximum length of 46 bytes.

  The file records 3124, 3214, and 3224 include a pointer and a file name that point to the sector in which the file body is stored, and the record length is variable and has a maximum length of 46 bytes.

  For example, the root directory entry 310 shown in FIG. 5 includes a directory record 3103 of the “DCIM” directory 211 and a directory record 3103 of the “MISC” directory 221. The directory entry 312 of the “MISC” directory shown in FIG. 7 includes a file record 3124 of the text file 253.

  FIG. 10 shows the data structure of the path table 330.

  The path table 330 includes a root directory record 3301 and a subdirectory record 3303 including a pointer and a directory name indicating each parent directory for each subdirectory record.

  The root directory record 3301 is fixed to 10 bytes, and the subdirectory record 3303 has a variable length and a maximum of 18 bytes.

  Here, one sector of CD3 is 2048 bytes. Therefore, even when the amount of data to be stored in each directory entry 310, 311, 312, 321, 322 and path table 330 is less than 2048 bytes, when storing one directory entry or path table, it is a multiple of 2048 bytes. Storage space is consumed. This also applies to the case where the data body is stored. That is, when the data body is stored in the CD3, the storage area is consumed in units of 2048 bytes according to the size of the data body.

  Next, FIG. 4 shows the data structure of backup data 31 and 32 when the backup target data shown in FIG. 2 is divided into two sessions and backed up to CD3.

  That is, here, it is divided into a first session including the “DCIM” directory 211 of the first hierarchy 21 and its subdirectories and files, and a second session including the “MISC” directory 212 and its subordinate files, The data structure of backup data 31 and 32 when backup is performed in two steps is shown.

  FIG. 4A shows the backup data 31 after the first session is backed up.

  The backup data 31 is configured by removing the “MISC” directory entry 312 and the text file body 353 from the backup data 30 shown in FIG. However, the contents of the path table 330 a are different from the path table 330 of the backup data 30. That is, since the “MISC” directory 212 has not been copied, the path table 330a includes information indicating the directory structure excluding the “MISC” directory 212 and its subordinate text file 253 in the directory structure shown in FIG. It is.

  FIG. 4B shows the backup data 32 when the backup of the second session is executed following the first session.

  The backup data 32 includes a directory entry 312b and a text file body 353b of the “MISC” directory 212 to be backed up in this session. In addition, management areas 301b and 302b, a root directory entry 310b, and a path table 330b are included.

  Here, the path table 330b includes information indicating the directory structure shown in FIG. This is because the “DCIM” directory 211 was backed up in the first session and the “MISC” directory 212 was copied in the second session, so that all data shown in FIG. Because.

  As a result, even when the same data is backed up, it can be seen that the required capacity varies depending on the session. That is, if the session is divided into a plurality of as shown in FIG. 4, only the capacity of the management areas 301b and 302b, the root directory entry 310b, and the path table 330b is compared with the case where the backup is performed without dividing the session as shown in FIG. A lot is needed.

  FIG. 11 is a flowchart showing the procedure of the divided backup process performed by the backup management unit 11.

  FIG. 12 is a diagram showing the relationship between the directory structure and the division pattern.

  Here, a case will be described as an example in which backup target data having the directory structure shown in FIG. 12 is backed up according to the flowchart shown in FIG.

  First, the backup management unit 11 sets the division number A as the division pattern A (S11). That is, consider a case where backup is performed in one session without dividing the backup target data.

  Here, the backup management unit 11 determines whether or not the total capacity of the backup target data is larger than the free capacity of the CD 3 as the backup destination medium (S12). When the total capacity of the data to be backed up is larger than the free capacity of CD3 (S12: Yes), the capacity cannot be backed up because the capacity of CD3 is insufficient, and the processing is terminated at this point.

  When the total capacity of the backup target data is not larger than the free capacity of the CD3 (S12: No), the backup management unit 11 is necessary for dividing the session into sub-directory units of the first hierarchy as the division pattern B. The capacity of CD3 is calculated (S13).

  In the example of FIG. 12, the “DCIM” directory 211 is a first session, and the “MISC” directory 212 is a second session.

  As described above, when a session is divided, the management area and the like increase, so that the capacity required for backup as a whole increases. Furthermore, the required number of sectors may differ depending on the number of directories or files, the size of the file, and the like.

  For example, one sector is required as a directory entry for each subdirectory. In each directory entry, the maximum length of the directory record is 46 bytes, so that a maximum of 44 directory records can be stored in one sector. That is, depending on the number of subdirectories directly under a certain directory, the number of sectors required as a directory entry may differ. Alternatively, since the maximum length of the directory record is 18 bytes in the path table, a maximum of 113 directory records can be stored in one sector. That is, the number of sectors required for the path table may differ depending on the total number of directories included in one session.

  Therefore, the backup management unit 11 calculates the total capacity required for backup according to the directory structure and the number of directories included in each session.

  Next, the backup management unit 11 determines whether or not the total capacity required for the division pattern B is larger than the free capacity of the CD 3 that is the backup destination medium (S14). When the total capacity required for the division pattern B is larger than the free capacity of the CD3 (S14: Yes), the division pattern A is selected (S15).

  When the total capacity required for the division pattern B is not larger than the free capacity of the CD3 (S14: No), the backup management unit 11 is necessary for dividing the session into sub-directory units of the second hierarchy as the division pattern C. The capacity of CD3 is calculated (S16).

  In the example of FIG. 12, the “100ABCDE” directory 221 and the “101ABCDE” directory 222 are further divided into different sessions.

  The backup management unit 11 determines whether or not the total capacity required for the division pattern C is larger than the free capacity of the CD3 that is the backup destination medium (S17). When the total capacity required for the division pattern C is larger than the free capacity of the CD3 (S17: Yes), the division pattern B is selected (S18).

  When the total capacity required for the division pattern C is not larger than the free capacity of the CD3 (S17: No), the backup management unit 11 sets two files in the subdirectory of the second hierarchy as two division patterns D. The data is divided into groups, and the capacity of CD3 required at this time is calculated (S19).

  Here, when there are subdirectories below the third hierarchy, they may be further divided into subdirectories. Here, since there are no sub-directories below the third layer, a large number of files existing in the sub-directory of the second layer which is the lowest layer are divided into a plurality of groups.

  Here, a plurality of files existing in the same directory may be divided as follows. For example, when the file creation date is the same as one group, or when the file name is a sequential number, the file is divided when the sequential number is interrupted, or additional information included in the image file (for example, Exif format) Or may be divided based on shooting information included in the file.

  Then, the backup management unit 11 determines whether or not the total capacity required for the division pattern D is larger than the free capacity of the CD 3 (S20). When the total capacity required for the division pattern D is larger than the free capacity of the CD3 (S20: Yes), the division pattern C is selected (S21).

  When the total capacity required for the division pattern D is not larger than the free capacity of the CD3 (S20: No), the division pattern D is selected (S22).

  And the backup management part 11 backs up backup object data for every session according to the division | segmentation pattern selected by said process (S23).

  As a result, even if a trouble occurs during backup, all data is not lost, and more data can be backed up.

  In the above processing procedure, when the data to be backed up is a single directory and its subordinate files, there are no division patterns B and C, and the processing related to this is skipped.

  The above-described embodiments of the present invention are examples for explaining the present invention, and are not intended to limit the scope of the present invention only to those embodiments. Those skilled in the art can implement the present invention in various other modes without departing from the gist of the present invention.

It is a functional lineblock diagram of backup processing device 1 concerning one embodiment of the present invention. An example of the directory structure stored in the memory card 2 is shown. The data structure when backing up to CD3 in one session is shown. The data structure when backing up to CD3 in two sessions is shown. The data structure of the root directory entry is shown. The data structure of the “DCIM” directory entry is shown. The data structure of the “MISC” directory entry is shown. The data structure of the “100ABCDE” directory entry is shown. The data structure of the “101ABCDE” directory entry is shown. The data structure of a path table is shown. It is a flowchart which shows the procedure of a division | segmentation backup process. It is a figure which shows the relationship between a directory structure and a division | segmentation pattern.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 ... Backup processing apparatus, 2 ... Memory card, 3 ... CD, 11 ... Backup management part, 30, 31, 32 ... Backup data, 301, 302 ... Management area, 310 ... Root directory entry, 311 ... "DCIM" directory entry 312 ... "MISC" directory entry, 321 ... "100ABCDE" directory entry, 322 ... "101ABCDE" directory entry, 330 ... path table.

Claims (7)

A backup processing device for backing up backup target data stored in a first storage medium to a second storage medium,
The capacity of the second storage medium required when the backup target data is divided into a plurality of sessions for backup is calculated, and based on the calculated required capacity and the free capacity of the second storage medium A dividing means for determining the number of session divisions;
A backup processing apparatus comprising: a copy unit that divides the backup target data into the number of divided sessions and copies it from a first storage medium to a second storage medium.   2. The backup processing apparatus according to claim 1, wherein the dividing unit divides the backup target data into sessions for each first-level subdirectory in a root directory and determines the number of divisions.   3. The backup processing apparatus according to claim 2, wherein the dividing unit further divides a session for each subdirectory below the second hierarchy under the subdirectory of the first hierarchy to determine the number of divisions.   4. The backup processing apparatus according to claim 2, wherein when a plurality of files are included in the same directory, the number of divided sessions is determined by further dividing sessions according to the creation date of each file.   When a plurality of image files photographed with a digital camera are included in the same directory, the number of session divisions is determined by further dividing the session according to incidental information relating to the photographing conditions included in each image file. 4. The backup processing apparatus according to claim 2, wherein the backup processing apparatus is a backup processing apparatus.   The backup processing apparatus according to claim 1, wherein the second storage medium conforms to a CD-ROM file system. Calculating the capacity of the second storage medium required when the backup target data stored in the first storage medium is divided into a plurality of sessions and backed up to the second storage medium;
Determining the number of session divisions based on the calculated required capacity and the free capacity of the second storage medium;
A step of dividing the backup target data into the number of divided sessions and copying the data from a first storage medium to a second storage medium.

Images