JP2008171351A - Backup processor, backup processing method and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To secure already backed-up data even when failing in backup processing and not being able to continue processing. <P>SOLUTION: This backup processor 1 for backing up backup target data stored in a memory card 2 to a CD 3 calculates capacity of the CD 3 necessary when dividing the backup target data into a plurality of sessions and backing up them, and determines a session division number based on free capacity of the CD 3 and the calculated necessary capacity. The backup target data are divided into the session division number, and are copied to the CD 3 from the memory card 2. <P>COPYRIGHT: (C)2008,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 JP 2005-111943 A

  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.

The main invention for achieving the above object is:
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 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;
Is a backup processing apparatus.
Other features of the present invention will become apparent from the description of the present specification and the accompanying drawings.

At least the following matters will become clear from the description of the present specification and the accompanying drawings.
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 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;
A backup processing apparatus comprising:
By doing so, it is possible to secure already backed up data even when the backup process fails and the process cannot be continued.

  In this backup processing apparatus, the second storage medium is controlled by a battery-driven device, and the backup processing device further includes monitoring means for monitoring a remaining battery level of the battery-driven device. desirable. In addition, when the monitoring unit determines that the remaining battery level is sufficient to back up the backup target data to the second storage medium, the dividing unit sets the session division number to 0. It is desirable to decide on. In addition, when the monitoring unit determines that the remaining battery level is not sufficient to complete the copy of the backup target data corresponding to one session, the copy unit determines that the backup target corresponding to the one session It is desirable not to copy data. In addition, the monitoring unit copies the backup target data corresponding to the other session after completing the copy of the backup target data corresponding to the certain session and before copying the backup target data corresponding to the other session. It is desirable to determine whether the battery level is sufficient to complete the process.

Further, it is preferable that the copy unit has information regarding a session of the backup target data that has been copied, and updates the information every time the copy of the backup target data is completed on a session basis. In addition, the copy unit changes the attribute of the backup target data stored in the first storage medium to read only before copying the backup target data to the second storage medium, and It is desirable to change the attribute of the backup target data stored in the first storage medium to an erasable attribute for each session after the copy of the backup target data to the storage medium is completed.
By doing so, it is possible to secure already backed up data even when the backup process fails and the process cannot be continued.

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 for backup;
Determining the number of session divisions based on the calculated required capacity and the free capacity of the second storage medium;
Copying the backup target data into the session division number and copying the data from the first storage medium to the second storage medium;
Backup processing method including.
By doing so, it is possible to secure already backed up data even when the backup process fails and the process cannot be continued.

A program for operating a backup processing apparatus,
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 for backup;
Determining the number of session divisions based on the calculated required capacity and the free capacity of the second storage medium;
Copying the backup target data into the session division number and copying the data from the first storage medium to the second storage medium;
A program for causing the backup processing apparatus to execute
By doing so, it is possible to secure already backed up data even when the backup process fails and the process cannot be continued.

=== First Embodiment ===
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.

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.

=== Second Embodiment ===
<Printer configuration>
FIG. 13 is a perspective view for explaining the overall configuration of the printer 401. FIG. 14 is a block diagram of the overall configuration of the printer 401. Hereinafter, the basic configuration of the printer 401 will be described.

  The printer 401 includes a controller 411, a memory card reader / writer 412, a CD reader / writer 413, a printing unit 414, an interface 415, a hard disk drive 416, a liquid crystal display 417, and an operation panel 418. The printer 401 uses the CD reader / writer 413 to write image data stored in the memory card 2 read from the memory card reader / writer 412 to the CD3 (CD-R) or the hard disk drive 416, or to print the image data. Printing can be performed via the unit 414.

  The controller 411 controls a memory card reader / writer 412, a CD reader / writer 413, a printing unit 414, an interface 415, a hard disk drive 416, a liquid crystal display 417, and an operation panel 418, which will be described later. The controller 411 includes a processing device for processing a program and a memory for storing the program and data. The controller 411 executes the program stored in this memory. By executing the program, for example, the backup target data stored in the memory card 2 as described later is backed up to the CD 3.

  A memory card can be inserted into the memory card reader / writer 412 so that data can be read and written from the memory card 2. The file system of the memory card 2 used here is a FAT file system. The FAT file system reserves an area for storing attributes for making each file read-only. The attribute is read-only (read-only attribute and directory or file cannot be deleted), or read-only attribute is canceled (writeable attribute, directory or file) for each directory and file. Deleteable attributes).

The CD reader / writer 413 writes data into CD3 and reads data from CD3. At this time, data can be written to and read from the CD 3 in accordance with a CD-ROM file system conforming to ISO9660 level 1.
The printing unit 414 forms an image on a medium based on the image data under the control of the controller 411. For example, an image can be printed on paper by ejecting ink droplets.

The interface 415 is an interface for connecting to the computer 19 such as a USB interface. By connecting to a computer, data such as image data can be transmitted and received from the computer 19.
The hard disk drive 416 can write and read data read from the memory card 2 or the CD 3. The file system of the hard disk drive 416 used here is a FAT file system.

The liquid crystal display 417 provides visual information to the user under the control of the controller 411. For example, an image file stored in the memory card 2 is displayed or processing options are shown to the user.
The operation panel 418 is for receiving an instruction from the user. By using this, the user selects, for example, an image file to be copied from the memory card 2 to the hard disk drive 416.

FIG. 15 is a circuit diagram illustrating a power supply system of the printer 401. The printer 1 in this embodiment is a battery-driven printer.
The power line Vcc is supplied with power from an external AC adapter 110 as an external power source of the printer 401 and a lithium ion battery pack 120 (hereinafter referred to as a battery pack 120) as a “battery” detachably built in the printer 1. The The AC adapter 110 performs AC-DC conversion of AC power (such as AC100V) to DC power (DC20V). The DC power output from the AC adapter 110 is supplied to the power supply line Vcc via the diode D1. The battery pack 120 includes a plurality of lithium ion batteries. The DC power output from the battery pack 120 is supplied to the power supply line Vcc via the diode D2.

  The power supply line Vcc is provided with a power switch 135, and the power supply line Vcc is directly connected / disconnected at the contact point of the power switch 135 to turn on / off the electronic device.

The charging circuit 121 performs charging of the battery pack 120 using the DC 20V power supplied from the AC adapter 110 via the diode D3.
The A / D conversion circuit 122 that can acquire information for estimating the remaining amount of power of the battery pack 120 divides the output voltage of the battery pack 120 by a predetermined voltage division ratio, and then converts the voltage to a digital signal voltage value. And output to the controller 411.

  The power supply detection circuit 123 detects the presence / absence of power supply from the battery pack 120 from the presence / absence of power supply from the AC adapter 110 and the attachment / detachment state of the battery pack 120, and detects the respective detection states (power supply detection signals) to the controller 411. Is output.

  The controller 411 determines whether the supplied power is the AC adapter 110 or the battery pack 120 based on the detection state (power supply detection signal) of the power supply from the AC adapter 110 and the power supply from the battery pack 120 in the power supply detection circuit 123. Judging. In addition, the controller 411 estimates the remaining power of the battery pack 120 based on the output signal of the A / D conversion circuit 122.

<Data structure and directory structure>
The data structure and directory structure of the memory card 2 and the CD 3 in the second embodiment are the same as those described in the first embodiment. Therefore, the description is omitted. In the following description, FIGS. 2 to 10 and FIG. 12 for explaining the data structure and the directory structure are referred to as appropriate. Note that, as shown in FIG. 5, an area in which the three storage parts of lead-in, data, and lead-out are combined is called a session.

<Backup processing to CD3>
16 and 17 are flowcharts showing the procedure of backup processing for backing up the data in the memory card 2 to the CD3.

  First, the controller 411 determines whether or not the remaining battery level of the printer 401 is sufficient to copy the file on the memory card 2 to the CD 3 (S505). Here, the remaining battery level is the remaining battery level required to write the data in the memory card 2 to the CD 3 in one session without dividing into a plurality of sessions. When an image file for writing is created on the hard disk drive 416 before writing the data to be backed up on the CD 3, the power required at this time is also taken into consideration.

  If it is determined in step S505 that the remaining battery level is sufficient, the data is written to CD3 in one session without being divided into a plurality of sessions (S508). This is for the following reason. If the session is not completely closed, the data included in the session cannot be read from the CD 3. In the processing after step S511, in order to reduce the risk that all data cannot be read, writing is performed by dividing into a plurality of sessions. By doing so, data written before an incomplete session can be read from the CD 3. However, here, in step S505, it is determined that the battery will not run out during writing. Therefore, the number of session divisions is set to 0 (division pattern A) in step S508 to write all files in one session.

  Once step S508 has been performed, the controller 411 next determines whether or not the total capacity of the backup target data is larger than the free capacity of the CD3 that is the backup destination medium (S510). If the total capacity of the data to be backed up is larger than the free capacity of CD3 (S510: Yes), the capacity of the CD is insufficient and cannot be backed up. On the other hand, when the total capacity of the data to be backed up is not larger than the free capacity of the CD3 (S510: No), the controller 411 next executes step S526.

  If it is determined in step S505 that the remaining battery level of the printer 401 is not sufficient to copy the file on the memory card 2 to the CD3, the processes in and after step S511 are performed.

  The operations in steps S511 to S523 are the same as the operations in steps S11 to S23 in the first embodiment. In the second embodiment, this is expressed by adding “5” to the third digit of the step number of the first embodiment. Therefore, since the operation | movement of step S511-step S523 in 2nd Embodiment has already been described in 1st Embodiment, description is abbreviate | omitted.

  In this way, when step S523 or step S508 is performed, the session is divided by any one of the division patterns A to D.

  When the division pattern is determined, an image file for each session is created in the hard disk drive 16. In this image file, data written to the CD 3 is provisionally collected into one file. For example, when the data shown in FIG. 4A is written to the CD 3, a file in which these data are collected into one is created. By reading this data and writing it to CD3, continuous data can be written without delaying the CD writing speed.

  When divided by any one of the above-described division patterns, the remaining number N of write sessions indicating how many sessions are written to the CD 3 is determined.

  Next, data to be written to CD3 is set to a read-only attribute (S526). Specifically, the attribute of the file to be written to the CD 3 in the memory card 2 is set to the read only attribute. Also, the attribute is set to a read-only attribute for an image file created in the hard disk drive 16 for each session.

  Next, the controller 411 creates a file in which “write end information” is recorded (S528). The write end information includes the number N of remaining write sessions, information on the data structure in each divided session (for example, the data structure as shown in FIGS. 4A and 4B), and writing to CD3 for each session. Contains information on whether or not is completed. This “write end information” is a text file or binary file and is created in the hard disk drive 16 with a predetermined file name.

  Next, the image file of one session among the divided sessions is written to CD3 (S530). When the writing for one session is completed on the CD 3 and the session is closed, the controller 411 releases the read-only attribute of the memory card 2 for the file included in the written session (S532). In addition, the read-only attribute of the image file of the written session is also released. Then, the controller 411 deletes the session image file written to the CD 3.

  Next, among the plurality of sessions, the write end information is updated in order to distinguish between the sessions for which writing to CD3 has been completed and the sessions for which writing has not been completed (S534). Specifically, information indicating that writing has been completed is added to a session for which writing has been completed.

  Next, the write session remaining number N of the write end information is decremented (S536). Then, the controller 11 determines whether or not the remaining number N of write sessions is greater than 0 (S538). Here, when the remaining number N of write sessions is not larger than 0 (that is, when N = 0) (S538: No), since there are no more sessions to be written, this backup processing is terminated.

  On the other hand, when the remaining number N of write sessions is greater than 0 (S538: Yes), the controller 11 acquires the remaining battery level (S540). The memory in the controller 11 stores the remaining battery level corresponding to the output voltage signal sent from the A / D conversion circuit 122. Therefore, the controller 11 can obtain the remaining battery level based on the output voltage signal from the A / D conversion circuit. Then, the controller 11 determines whether or not there is sufficient remaining battery charge to write an image file for one session on the CD (S542).

  If the remaining battery level is sufficient (S542: Yes), the process returns to step S530 to write the image file of another session to the CD3. On the other hand, when the remaining battery level is not sufficient (S542: No), the controller 11 displays to the user that the remaining session cannot be written to the CD 3 because the remaining battery level is insufficient, thereby displaying to the user the liquid crystal display 17. Notification is made (S544). Then, this backup process is terminated.

  As described above, the reason for determining whether or not there is a sufficient remaining battery charge for writing the next one session is as follows. That is, if writing is interrupted due to a failure such as battery exhaustion before the session is closed, there is a possibility that additional writing cannot be performed on this CD3. As a result, the CD 3 cannot be additionally recorded while leaving a capacity for additional recording, resulting in waste. Therefore, here, in order to reliably complete writing for each session and not cause such waste, it is determined whether or not there is a sufficient remaining battery level.

  In step S544, the user is notified that the remaining session cannot be written to CD3 because the remaining battery level is not sufficient. At this time, the user may be asked whether or not the remaining session is still written. This is because the estimation of the remaining battery capacity may not be accurate and the remaining sessions may be written. In this way, the user can be given a degree of freedom in determining whether to write a session to CD3.

  Further, when it is determined in step S538 that writing for all the sessions has been completed, the selected file in the memory card 2 may be deleted. In this case, the file is safely “moved” from the memory card 2 to the CD 3.

  As described above, the attribute of the data to be copied is rewritten to read-only in the memory card 2 before writing to the CD 3 is performed. Then, in the memory card 2, the read-only attribute for the file included in the session for which copying has been completed is cancelled. By doing so, it is possible to delete the file of the session that has been properly copied in the memory card 2, while the file of the session that has not been properly written to the CD 3 may be deleted. Can not be. In this case, it can be considered that the memory card 2 corresponds to the first storage medium and the CD 3 corresponds to the second storage medium.

  For example, it is assumed that a plurality of files are divided into three sessions in order to back up a plurality of files to CD3. These sessions are referred to as a first session, a second session, and a third session. It is assumed that the backup of the first session is completed and the battery runs out during the backup of the second session. In that case, the read-only attribute is canceled in the memory card 2 for the file included in the first session. On the other hand, for the files included in the second session and the third session, the attribute in the memory card 2 is a read-only attribute.

  Under such circumstances, the user may forget for some reason that only the backup of the first session was performed among the backups that were divided into these three sessions. In such a case, it is conceivable that the user tries to delete all the files on the memory card 2. If all the files can be deleted, the files included in the second session and the third session that are not backed up will be lost. However, in the present embodiment, the read-only attribute is maintained in the memory card 2 for files included in the second session and the third session that have not been backed up. Therefore, even if the user tries to delete the file by mistake, the files included in the second session and the third session that have not been backed up are protected without being deleted.

  Further, every time writing for each session is completed, the read-only attribute is canceled in the hard disk 16 for the image file of the session for which writing has been completed. In addition, “write end information” including information on which session has been written is updated. Therefore, the image file of the session for which the read-only attribute has been canceled can be deleted, but the image file of the session for which writing has not been properly completed is not deleted. In this way, after restarting the printer 1, by referring to the “writing end information” again, a session that has not been properly written can be used to record the CD using the image file left on the hard disk drive 16. Writing to can be resumed. In this case, it can be considered that the hard disk drive 16 corresponds to the first storage medium and the CD 3 corresponds to the second storage medium.

  In this example, data is written to CD3 using an image file. However, it is also possible to directly write lead-in, file data, lead-out, etc. to CD3 without creating an image file. Good. When the image file is not created in this way, the data structure of each session in the “write end information” described above is referred to as appropriate, and data is written while data other than the file body is created.

  Even when the image file is not created, the “write end information” is updated as appropriate. In this “write end information”, up to which session writing is completed and the data structure of each session are recorded. Therefore, even when the image file is not created and writing to the CD 3 is not completed for all sessions, the writing of the session that has not been written is resumed with reference to the writing end information. be able to.

  Further, before the memory card 2 is inserted into the memory card reader / writer 412, the file on the memory card 2 may have a read-only attribute. In this case, the file name having the read-only attribute is stored in the memory of the controller 411 before performing the backup. Then, after the backup is completed, the files having the read-only attribute from the beginning are not deleted and are left in the memory card 2 with the read-only attribute.

=== Other Embodiments ===
The above-described embodiments are for facilitating the understanding of the present invention, and are not intended to limit the present invention. The present invention can be changed and improved without departing from the gist thereof, and it is needless to say that the present invention includes equivalents thereof. In particular, the embodiments described below are also included in the present invention.

=== Summary ===
(1) The printer 401 serving as the backup processing apparatus in the second embodiment, which is a more detailed embodiment, stores a backup target file (backup target data) stored in the memory card 2 (first storage medium) on a CD3. This is a backup processing device for backing up to (second storage medium).

  The printer includes a dividing unit and a copying unit. The dividing means is constituted by a controller 411. The copy means includes at least a controller 411, a memory card reader / writer 412 and a CD reader / writer 413. Further, a hard disk drive 416 is included in the copying means as necessary.

The dividing means calculates the capacity of the CD3 required when the backup target file is divided into a plurality of sessions for backup, and determines the number of divided sessions based on the calculated required capacity and the free capacity of the CD3. To do.
The copy means divides the backup target file into the number of divided sessions and copies it from the memory card 2 to the CD 3.

If all files are written to CD3 in one session without being divided into a plurality of files, and writing fails in the middle, all files cannot be read. On the other hand, when writing into the CD3 by dividing into a plurality of sessions as in the present embodiment, even if the writing fails in the middle, the file of the session written before the failure can be read from the CD3. It becomes possible. In this way, already backed up data can be secured.
Here, CD3 is exemplified as the second storage medium, but a DVD may be used.

(2) CD3 is controlled for writing by a battery-driven CD-R drive. The CD-R drive may be built in the printer 201 or may be externally attached.
The printer 201 further includes monitoring means for monitoring the remaining battery level of the printer 201 incorporating the CD-R drive or the CD-R drive. The monitoring means includes a controller 411 and an A / D conversion circuit 122.
In this way, data can be written to the CD 3 while monitoring the remaining battery level.

(3) In addition, when the monitoring unit determines that the remaining battery capacity is sufficient to back up the file to be backed up to CD3, the controller 411 determines the number of divided sessions to be zero.
In this way, when the remaining battery capacity is sufficient, all files to be backed up can be written to CD3 in one session.

(4) When the monitoring unit determines that the remaining battery level is not enough to complete copying of the backup target file corresponding to one session, the copy unit performs backup corresponding to the one session. Do not copy the target file.
In this way, it is possible to prevent the session from being properly closed due to battery exhaustion, and to avoid a situation in which additional writing cannot be performed because the closing has not been performed properly.

(5) In addition, the monitoring unit described above supports a different session after copying a backup target file corresponding to a certain session and before copying a backup target file corresponding to another session. It is determined whether or not the remaining battery capacity is sufficient to complete the copy of the file to be backed up.
In this way, it is possible to determine whether or not the remaining battery capacity is sufficient to write one session, so that it is possible to prevent the session from being properly closed due to battery exhaustion. Note that if the session is not properly closed, there is a possibility that additional recording cannot be performed on the CD. As a result, the CD cannot be additionally written while leaving a capacity for additional writing, resulting in waste. In the present embodiment, the session is properly closed by the method described above.

(6) Further, the above copy means has “write end information” regarding the session of the backup target file that has been copied, and this “write end information” every time the copy of the backup target file is completed in session units. ”Is updated.
Due to reasons such as insufficient battery, writing to CD3 may not be completed for all sessions. Even in such a case, the updated “write end information” can be referred to, and the session write can be resumed based on this information.

(7) Further, the above-described copying unit changes the attribute of the backup target file stored in the memory card 2 to read only before copying the backup target file to the CD 3. Further, the copy means changes the attribute of the backup target file stored in the memory card 2 to an erasable attribute for each session after the copying of the backup target file to the CD 3 is completed.
In this way, it is possible to prevent data that has not been copied to the CD 3 from being accidentally deleted from the memory card 2.

(8) Needless to say, there is the following backup processing method. That is, this backup processing method includes a step of calculating the capacity of the CD 3 required when the backup target file stored in the memory card 2 is divided into a plurality of sessions for backup. The backup processing method includes a step of determining the number of divided sessions based on the calculated necessary capacity and the free capacity of the CD3. Further, this backup processing method includes a step of copying the file to be backed up into the determined number of session divisions and copying it from the memory card 2 to the CD 3.
By writing to the CD 3 divided into a plurality of sessions as in this embodiment, even if the writing fails in the middle, the file of the session written before the failure can be read from the CD 3. In this way, already backed up data can be secured.

(9) Needless to say, there is a program for causing the backup processing apparatus to perform the above-described backup processing method.

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. FIG. 2 is a perspective view for explaining the overall configuration of the printer 401. 2 is a block diagram of an overall configuration of a printer 401. FIG. 3 is a circuit diagram illustrating a power supply system of a printer 401. FIG. It is a flowchart which shows the procedure of the backup process which backs up the data of the memory card 2 to CD3. It is a flowchart which shows the procedure of the backup process which backs up the data of the memory card 2 to CD3.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Backup processing apparatus, 2 Memory card, 3 CD, 11 Backup management part, 12 Memory card reader / writer, 13 CD reader / writer, 19 Computer,
30, 31, 32 Backup data,
110 AC adapter, 120 battery pack, 121 charging circuit,
122 A / D conversion circuit, 123 power supply detection circuit, 130 DC-DC converter,
135 switch, 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 401 printer, 411 controller, 412 memory card reader / writer,
413 CD reader / writer, 414 printing unit, 415 interface,
416 hard disk drive, 417 liquid crystal display, 418 operation panel

Claims (9)

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 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;
A backup processing apparatus comprising: The second storage medium is controlled by a battery-powered device;
The backup processing apparatus according to claim 1, further comprising a monitoring unit that monitors a remaining battery level of the battery-driven apparatus.   When the monitoring unit determines that the remaining battery capacity is sufficient to back up the backup target data to the second storage medium, the dividing unit determines the session division number to be 0. The backup device according to claim 2.   When the monitoring unit determines that the remaining battery level is not sufficient to complete the copy of the backup target data corresponding to one session, the copy unit stores the backup target data corresponding to the one session. The backup device according to claim 2, wherein no copying is performed.   The monitoring unit completes copying of backup target data corresponding to another session after copying backup target data corresponding to one session and before copying backup target data corresponding to another session. The backup device according to claim 4, wherein it is determined whether or not the remaining battery capacity is sufficient to perform the operation.   The copy unit has information on a session of the backup target data that has been copied, and updates the information every time the copy of the backup target data is completed on a session basis. The backup device described. The copy unit changes the attribute of the backup target data stored in the first storage medium to read-only before copying the backup target data to the second storage medium,
The attribute of the backup target data stored in the first storage medium is changed to an attribute that can be deleted on a session basis after the copy of the backup target data to the second storage medium is completed. The backup processing apparatus in any one of -6. 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 for backup;
Determining the number of session divisions based on the calculated required capacity and the free capacity of the second storage medium;
Copying the backup target data into the session division number and copying the data from the first storage medium to the second storage medium;
Backup processing method including. A program for operating a backup processing apparatus,
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 for backup;
Determining the number of session divisions based on the calculated required capacity and the free capacity of the second storage medium;
Copying the backup target data into the session division number and copying the data from the first storage medium to the second storage medium;
A program for causing the backup processing apparatus to execute

Images