Abstract:
In the security media ID of a security MO disk, a unique ID of a backup source disk is written in 64 bytes following the unique ID of the security media ID of the backup destination disk. When using a security MO disk, the security media ID can be seen even before performing password authentication. Accordingly, by comparing the unique ID of the backup source disk in the security media ID of the backup destination disk to a unique ID of another disk, it is possible to quickly find the backup source disk of the backup destination disk.

Description:
CROSS REFERENCE TO RELATED APPLICATION  
       [0001]     This application is a continuation of international PCT application No. PCT/JP2003/007037 filed on Jun. 3, 2003. 
     
    
     BACKGROUND OF THE INVENTION  
       [0002]     1. Field of the Invention  
         [0003]     The present invention relates to a method for backup of data files and so forth.  
         [0004]     2. Description of the Related Art  
         [0005]     Backup processing refers to copying all files in a backup source disk to a backup destination disk. The backup processing intends to copy all files in the backup source disk to the backup destination disk. For that reason, the backup processing can be either processing of copying all files in the backup source to a specific folder of the backup destination, or difference backup processing in which the backup source is compared with the backup destination, unnecessary files in the backup destination are deleted, and files not present in the backup destination are copied.  
         [0006]     In carrying out backup, it is necessary to correspond a backup source disk to a backup destination disk. As one of the means for realizing this correspondence, there is a method for writing information for specifying the backup destination in the backup source. In the information for specifying disks, files with a volume serial number, a volume label, and special information written in are used.  
         [0007]     In a case of security disks, the above determination is possible, if it is authenticated based on password. However, in the state in which the password is not authenticated, the information for specifying the disk is not accessible at all. Therefore, in the state that the password is not authenticated, the backup source could not be corresponded to the backup destination.  
       SUMMARY OF THE INVENTION  
       [0008]     It is an object of the present invention to provide a backup method for making correspondence between the backup source disk and the backup destination disk in the state that password is not authenticated.  
         [0009]     The backup method in the present invention is a backup method, which cannot manipulate data content without authentication based on password, comprising a step of storing a unique ID comprised in a security media ID of a backup source media in a security media ID of a backup destination media and a step of making correspondence between a backup destination media and a backup source media by verifying a unique ID of the backup source media comprised in a security media ID of the backup destination media and a unique ID of the backup source media comprised in a security media ID of the backup source.  
         [0010]     According to the present invention, because an ID unique to backup source media is stored in a security media ID, the backup source media can be readily corresponded to the backup destination media without password authentication. 
     
    
     BRIEF DESCRIPTION OF THE DRAWINGS  
       [0011]      FIG. 1  is an overall view of the embodiment of the present invention;  
         [0012]      FIG. 2  is a configuration diagram of the security MO disk;  
         [0013]      FIG. 3  is a diagram showing structure of the secure ID;  
         [0014]      FIG. 4  is a diagram showing a structure of the secure ID according to the embodiment of the present invention;  
         [0015]      FIG. 5  and  FIG. 6  are diagrams showing other structures of the secure ID according to the embodiment of the present invention;  
         [0016]      FIG. 7  is a flowchart showing processing flow in backup according to the embodiment of the present invention;  
         [0017]      FIG. 8  is a flowchart showing generation procedure of the backup destination media;  
         [0018]      FIG. 9  is a flowchart showing the processing flow in backup when using the specific ID;  
         [0019]      FIG. 10  is a flowchart explaining generation procedures of the backup source media when using the specific ID;  
         [0020]      FIG. 11  is a flowchart explaining generation procedures of the backup destination media when using the specific ID;  
         [0021]      FIG. 12  is a flowchart explaining flow in backup in a case of a configuration using the specific ID and an identifier indicating the use of the present embodiment;  
         [0022]      FIG. 13  is a flowchart showing generation procedures of the backup source media when using the specific ID and the identifier; and  
         [0023]      FIG. 14  is a flowchart showing generation procedures of the backup destination media in the use of the specific ID and the identifier.  
     
    
     DESCRIPTION OF THE PREFERRED EMBODIMENTS  
       [0024]      FIG. 1  is an overall view of the embodiment of the present invention.  
         [0025]     In  FIG. 1, 1  indicates a host PC,  2  indicates a security MO drive,  3  indicates a security MO disk of backup source, and  4  indicates a security MO disk of backup destination.  
         [0026]     In this description, a security MO, security media, a security disk and so forth refer to media etc., which requires authentication based on password in order for users to see the content of the stored data.  
         [0027]      FIG. 2  is a configuration diagram of the security MO disk.  
         [0028]     In  FIG. 2 , the security MO disk comprises security media ID (hereinafter referred to as a secure ID), password for authentication and normal data domain. The normal data domain, by being formatted, reads and writes files originated from PC. In order to write the normal data domain in the security MO disk, the user must be authenticated based on one of four kinds of authentication passwords. Authentication passwords are a R/W password for reading/writing, a read password, which is read-only, an LBA password, which is accessible only from a section of the media, and an administrator password for allowing reference of the content of the media even when the user forgot the password.  
         [0029]      FIG. 3  is a diagram showing structure of the secure ID.  
         [0030]     The secure ID is 512-byte value, written in a disk by the security MO drive. Once the secure ID is written in, the value cannot be deleted or changed. In the secure ID, a value automatically generated by the security MO drive is used for 64 bytes from the top. This is called a unique ID. Because the unique ID uses a serial number of the MO drive and a serial number of the security MO disk created in the drive, it is less likely to have unique ID sections overlapped between a plurality of security MO disks. For 448 bytes other than the unique ID, any value can be used depending on programs. This is called a user-defined ID. Even when the unique ID sections duplicate between a plurality of the security MO disks, uniqueness of the secure ID can be maintained as long as the user-defined IDs do not duplicate. As an example for maintaining uniqueness, there is a method that creation timestamp is made for a value of 8 bytes in the user-defined ID. It can be said that uniqueness of 72-byte value, a combination of the unique ID of 8 bytes and 64 bytes, can be maintained. Also, the secure ID can be read out even if the user is not authenticated based on the authentication password.  
         [0031]      FIG. 4  is a diagram showing a structure of the secure ID according to the embodiment of the present invention.  
         [0032]     In carrying out backup of the security MO disk, the secure ID of its own disk is written on other MO disk, and it is used as a security MO disk. When generating the secure ID, the unique ID of the backup source is used for the 64 bytes of the user-defined ID. For example, as shown in  FIG. 4 , the unique ID of the backup source is used for 64 bytes (64 bytes from the top of the user-defined ID) following the unique ID of the backup destination.  
         [0033]     When carrying out backup to the backup destination disk with the secure ID set in the manner described above, whether or not it is the backup destination disk can be determined without the entry of authentication password.  
         [0034]     In the backup source ID used for the user-defined domain of the secure ID of the backup destination, by adding a part of the user-defined ID to the backup source unique ID, the backup source can unfailingly correspond to the backup destination. For example, when using 72 bytes including the timestamp in the unique ID as shown in the above example, it can be realized by acquiring 72 bytes from the top of the backup source secure ID for the backup destination secure ID, and by using 72 bytes among the backup destination user-defined ID. With this method, maximum of 256 bytes of the backup secure ID can be used.  
         [0035]      FIG. 5  and  FIG. 6  are diagrams showing other structures of the secure ID according to the embodiment of the present invention.  
         [0036]     The unique ID is written in automatically by the drive in setting of the secure ID; however, it can also be realized by writing a unique specific ID in a predetermined position of the user-defined domain when setting the secure ID, and then writing a specific ID of the backup source to a predetermined position of the user-defined domain of the backup destination. As for the specific ID, GUID of Windows (registered trademark) etc. can be used.  
         [0037]     When the backup source and the backup destination use the same position as the insertion position of the specific ID, by writing a backup destination identifier, for identifying the backup destination, in a predetermined position of the secure ID, the backup destination disk can be identified.  
         [0038]     By writing a system identifier, indicating that the backup source disk and the backup destination disk uses the system of the present embodiment, in a predetermined position of the secure ID, the disk not using the present system can be distinguished.  
         [0039]     By writing a method identifier, indicating that the backup source disk and the backup destination disk uses the unique ID method of the present invention, in a predetermined position of the secure ID, the disk not using the present system can be distinguished.  
         [0040]     When using the specific ID, by writing position information and length information of the specific ID into a predetermined position of the secure ID, the specific ID can be arbitrarily set. The position information can be an offset from the top of the secure ID. The backup destination disk may have the specific IDs in two separate positions; however in such a case, the position information and the length information of both positions are written in the secure ID.  
         [0041]      FIG. 7  is a flowchart showing processing flow in backup according to the embodiment of the present invention.  
         [0042]     In the step S 10 , the backup source secure ID is acquired. In the step S 11 , the backup source secure ID (Src ID) is extracted, and in the step S 12 , the backup source disk is ejected from the security drive. In the step S 13 , a user inserts the backup destination into the security disk drive, and in the step  14 , the secure ID of the backup destination is acquired. In the step S 15 , a preset backup source unique ID (Trg ID) is extracted, and in the step S 16  the Src ID and the Trg ID are compared. In the step S 17 , whether the Src ID and the Trg ID correspond or not is determined. When they do not correspond to each other, the processing goes back to the step S 12 . When the correspondence is determined in the step S 17 , in the step S 18 , backup processing starts. When the backup processing is completed, the processing is terminated. The backup processing in this description is the same as in the regular backup processing of the secure disk, and the explanation is omitted, as it is conventional art.  
         [0043]      FIG. 8  is a flowchart showing generation procedures of the backup destination media.  
         [0044]     First, in the step S 20 , the backup source secure ID is acquired. In the step S 21 , the unique ID (Src ID) of the secure ID is extracted, and in the step S 22 , the backup source disk is ejected from the security disk drive. In the step S 23 , the user inserts media used as the backup destination into the security disk drive, and in the step S 24 , sets the backup destination secure ID. At that time, the Src ID is written in the user-defined domain of the secure ID, and the processing is terminated.  
         [0045]      FIG. 9  is a flowchart showing the processing flow in backup when using the specific ID.  
         [0046]     In the step S 30 , the backup source secure ID is acquired, in the step S 31  the specific ID (Src ID) of the secure ID is extracted, and in the step S 32  the backup source disk is ejected. In the step S 33  the user inserts the backup destination disk, in the step S 34  the backup destination secure ID is acquired, in the step S 35  a preset backup source specific ID (Trg ID) is extracted from the backup destination secure ID, and in the step S 36  the Src ID and the Trg ID are compared with each other. In the step S 37 , when they did not correspond, the processing goes back to the step S 32 , whereas, when they correspond in the step S 37 , in the step S 38 , the backup processing starts, and when the backup processing is completed, the whole processing is terminated.  
         [0047]      FIG. 10  is a flowchart explaining generation procedures of the backup source media when the specific ID is used.  
         [0048]     In the step S 40 , media, which a user uses as the backup source is inserted in the security disk drive. In the step S 41 , the backup source secure ID is set. At that time, the Src ID is written in the user-defined domain of the secure ID, and the processing terminates.  
         [0049]      FIG. 11  is a flowchart explaining generation procedures of the backup destination media when the specific ID is used.  
         [0050]     In the step S 45 , the backup source secure ID is acquired. In the step S 46 , the specific ID (Src ID) of the secure ID is extracted. In the step S 47 , backup source disk is ejected, and in the step S 48 , a user inserts the media used as the backup destination. In the step S 49 , the backup destination secure ID is set, and Src ID is written in the user-defined domain of the secure ID.  
         [0051]      FIG. 12  is a flowchart explaining flow of backup in a case of a configuration using the specific ID and an identifier indicating the use of the present embodiment.  
         [0052]     In the step S 50 , the backup source secure ID is acquired. In the step S 51 , whether or not the identifier indicates the use of the system of the embodiment of the present invention (whether a system identifier is accurate and a method identifier is for the specific ID or not) is determined. When the determination of the step S 51  is NO, the processing terminates. When the determination in the step S 51  is YES, in the step S 52 , the specific ID (Src ID) of the secure ID is extracted, and in the step S 53 , the backup source disk is ejected from the security disk drive. In the step S 54 , a user inserts the backup destination into the security disk drive, and in the step S 55 , the backup destination secure ID is acquired. In the step S 56 , whether or not the identifier of the backup destination secure ID indicates the use of the system of the embodiment of the present invention (whether a system identifier is accurate and a method identifier is for the specific ID or not) is determined. When the determination of the step S 56  is NO, the processing terminates. When the determination of the step S 56  is YES, in the step S 57 , a preset backup source specific ID (Trg ID) is extracted, and in the step S 58 , the Src ID and the Trg ID are compared to each other. In the step S 59 , correspondence in these IDs are determined, and when they do not correspond, the processing goes back to the step S 53 , whereas when they correspond, in the step S 60 , the backup processing is started. When the backup processing is completed, the processing terminates.  
         [0053]      FIG. 13  is a flowchart showing generation procedure of the backup source media when using the specific ID and the identifier.  
         [0054]     In the step S 65 , a user inserts media used as the backup source into the security disk drive. In the step S 66 , the backup source secure ID is set. At that time, the Src ID, the method identifier and the system identifier are written into the user-defined domain of the secure ID, and the processing terminates.  
         [0055]      FIG. 14  is a flowchart showing generation procedures of the backup destination media in the use of the specific ID and the identifier.  
         [0056]     In the step S 70 , the backup source secure ID is acquired, in the step S 71 , the specific ID (Src ID) of the secure ID is extracted, and in the step S 72 , the disk is ejected from the security disk drive. In the step S 73 , the user inserts media used as the backup destination into the security disk drive, and in the step S 74 , the backup destination secure ID is set. At that time, after writing the Src ID, the method identifier and system identifier into the user-defined domain of the secure ID, the processing terminates.  
         [0057]     Users had been required, after the entry of password of the disk and authentication of the disk, to determine whether the disk is the correct backup destination disk or not; however, in the present invention, because password authentication is performed after determining the correct backup destination disk, the users are not required to repeat the entry of password for determining the backup destination disk.