WO2004109520A1 - バックアップ方法 - Google Patents
バックアップ方法 Download PDFInfo
- Publication number
- WO2004109520A1 WO2004109520A1 PCT/JP2003/007037 JP0307037W WO2004109520A1 WO 2004109520 A1 WO2004109520 A1 WO 2004109520A1 JP 0307037 W JP0307037 W JP 0307037W WO 2004109520 A1 WO2004109520 A1 WO 2004109520A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- backup
- media
- security
- medium
- unique
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
- G06F21/57—Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1456—Hardware arrangements for backup
Definitions
- the present invention relates to a method for backing up data files and the like.
- the backup process indicates that all files on the backup source disk will be copied to the knock-down destination.
- the purpose of the backup process is to copy all files from the backup source to the backup destination.
- the knock-up process may be a process of copying all files at the backup source to a specific folder at the backup destination, comparing the backup source with the backup destination, deleting unnecessary files existing at the backup destination, Differential backup processing that copies files that do not exist in the backup destination may be used.
- An object of the present invention is to provide a backup method that can associate a backup source disk with a backup destination disk without being authenticated by a password.
- the backup method according to the present invention is a backup method in a security medium system in which data cannot be manipulated without authentication using a password, wherein the security medium ID of the medium at the backup destination is added to the security medium ID of the backup source.
- the step of storing the unique ID included in the security media ID of the medium and the correspondence between the backup destination medium and the backup source medium are described in the backup source medium included in the security media ID of the backup destination medium.
- the ID unique to the backup source medium is stored in the security media ID
- the correspondence between the backup source medium and the backup destination medium can be maintained without password authentication. Can be easily attached.
- FIG. 1 is an overall view of the embodiment of the present invention.
- Figure 2 shows the configuration of the security MO disk.
- FIG. 3 is a diagram showing a configuration of the secure ID.
- FIG. 4 is a diagram showing a configuration of a secure ID according to the embodiment of the present invention.
- FIGS. 5 and 6 are diagrams showing the configuration of a secure ID according to another embodiment of the present invention.
- FIG. 7 is a flowchart showing the flow of processing at the time of backup according to the embodiment of the present invention.
- FIG. 8 is a flowchart showing a procedure for creating a backup destination medium.
- FIG. 9 is a flowchart showing the flow of processing at the time of backup when a specific ID is used.
- FIG. 10 is a flowchart illustrating a procedure for creating a backup source medium when a specific ID is used.
- FIG. 11 is a flowchart illustrating a procedure for creating a backup destination medium when a specific ID is used.
- FIG. 12 is a flowchart for explaining a flow at the time of backup in the case of a configuration using a specific ID and an identifier indicating the use of the present embodiment.
- Figure 13 is a flowchart showing the procedure for creating a backup source medium when a specific ID and identifier are used.
- FIG. 14 is a flowchart showing a procedure for creating a backup destination medium when a specific ID and an identifier are used.
- FIG. 1 is an overall view of an embodiment of the present invention.
- 1 is a host PC
- 2 is a security MO drive
- 3 is a backup source security MO disk
- 4 is a backup destination security MO disk.
- security MO security media
- security disk etc. refer to media that require password authentication in order to view the stored data content.
- FIG. 2 shows the configuration of the security M ⁇ disk.
- the security MO disk is composed of a Security Media ID (hereinafter referred to as "secure ID"), an authentication password, and a normal data area.
- secure ID a Security Media ID
- the data area is initialized (formatted) so that files can be read and written from a PC.
- the authentication password includes a read-write RZW password, a read-only read password, an LBA password that allows access to only part of the medium, and a reference to the contents of the medium when the password is forgotten. There is an administrator password to enable this.
- FIG. 3 is a diagram showing a configuration of the secure ID.
- Secure ID is a value of 512 bytes written to the disk by the security M ⁇ drive. Once a secure ID is written, its value cannot be deleted or changed. For the first 64 bytes of the secure ID, a value automatically generated by the security MO drive is used. This is called a unique ID. The unique ID uses the serial number of the MO drive and the serial number of the security MO disk created with that drive, so the unique ID part is unlikely to be duplicated between multiple security MO disks. For the 4448 bytes other than the unique ID, any value can be used by the program. This is called a user-defined ID. Even if the unique ID part is duplicated between multiple security MO disks, the uniqueness of the secure ID is maintained as long as the user-defined ID does not overlap.
- FIG. 4 is a diagram showing a configuration of a secure ID according to the embodiment of the present invention.
- the backup source unique ID is used for 64 bytes of the user-defined ID. For example, as shown in Fig. 4, the backup source unique ID is used for the 64 bytes following the unique ID of the backup destination disk (64 bytes from the beginning of the user-defined ID).
- the backup source and the backup destination can be more reliably matched. For example, if 72 bytes including the time stamp are used for the unique ID shown in the previous example, 72 bytes from the beginning of the backup source secure ID are acquired as the backup destination secure ID, and the backup destination secure ID is acquired. This can be achieved by using 72 bytes of the user-defined ID of the above. With this method, up to 256 bytes of the backup source secure ID can be used.
- 5 and 6 are diagrams showing a configuration of a secure ID according to another embodiment of the present invention.
- the unique ID is the force that is automatically written by the drive when setting the secure ID. It can also be realized by writing to a defined position in the definition area.
- GUI the GUID of Windows® can be used. If the same location is used as the location to embed the specific ID between the backup source and the backup destination, write the backup destination identifier to identify the backup destination at the location where the secure ID is determined. Determine that it is the backup destination disk.
- the specific ID can be set arbitrarily by writing the position information and length information of the specific ID to the determined position of the secure ID.
- the location information may be an offset from the beginning of the secure ID.
- the backup destination disk may have two specific IDs. In this case, write the location information and length information to the secure ID for two locations.
- FIG. 7 is a flowchart showing a flow of a process at the time of backup according to the embodiment of the present invention.
- step S10 the secure ID of the backup source is obtained.
- step S11 the backup source secure ID (Src ID) is extracted, and in step S12, the backup source disk is ejected from the security disk drive.
- step S13 the user inserts the backup destination into the security disk drive, and in step S14, acquires the secure ID of the backup destination.
- step S15 the backup destination A preset backup source unique ID (Trg ID) is extracted from the cure ID, and the Src ID is compared with TrglD in step S16.
- step S17 it is determined whether or not the Src ID and the Trg ID match. If not, the process returns to step S12. If it is determined in step S17 that they match, the backup process is started in step S18. When the backup processing ends, the processing ends.
- the backup process here is the same as the normal secure disk backup process, and is a conventional technique, and therefore will not be described.
- FIG. 8 is a flowchart showing a procedure for creating a backup destination medium.
- a secure ID of a knockup source is obtained.
- the unique ID (Src ID) of the secure ID is extracted, and in step S22, the backup source disk is ejected from the security disk drive.
- the user inserts the medium to be used as the backup destination into the security disk drive, and in step S24, sets the secure ID of the backup destination.
- Src ID is written in the user-defined area of the secure ID, and the processing ends.
- FIG. 9 is a flowchart showing the flow of processing at the time of backup when a specific ID is used.
- step S30 the backup source secure ID is obtained.
- step S31 the secure ID specific ID (Src ID) is extracted.
- step S32 the backup source disk is ejected.
- step S33 the user inserts the backup destination disk, and in step S34 obtains the backup destination secure ID.
- step S35 the backup source secure ID is set in advance from the backup destination secure ID. (T rg ID), and in step S36, compares the S rc ID with T rgl D. Compare.
- step S37 if they do not match, the process returns to step S32, and if they match in step S37, the backup process starts and ends in step S38. Then, the entire process ends.
- FIG. 10 is a flowchart illustrating a procedure for creating a backup source medium when a specific ID is used.
- step S40 the user inserts a medium to be used as a backup source into the security disk drive.
- step S41 a backup source secure ID is set. At this time, Src ID is written to the user-defined area of the secure ID, and the process ends.
- FIG. 11 is a flowchart illustrating a procedure for creating a backup destination medium when a specific ID is used.
- step S45 the secure ID of the backup source is obtained.
- step S46 a specific ID (Src ID) of the secure ID is extracted.
- step S47 the backup source disk is ejected, and in step S48, the user inserts the medium used as the backup destination into the security disk drive.
- step S49 the secure ID of the backup destination is set, and the Src ID is written to the user-defined area of the secure ID.
- FIG. 12 is a flowchart illustrating a flow at the time of backup in a configuration using a specific ID and an identifier indicating the use of the present embodiment.
- step S50 the secure ID of the backup source is obtained.
- step S51 it is determined whether or not the identifier indicates that the system according to the embodiment of the present invention is used (whether or not the system identifier is correct and the method identifier is for a specific ID). If the determination in step 51 is NO, the process ends. If the determination in step S51 is YES, in step S52, the security The specific ID of the key ID (Src ID) is extracted, and in step S53, the backup source disk is ejected from the security disk drive. In step S54, the user inserts the backup destination into the security disk drive, and in step S55, acquires the secure ID of the backup destination.
- step S56 it is determined whether the identifier of the secure ID of the backup destination indicates that the system of the embodiment of the present invention is used (whether the system identifier is correct and the method identifier is for a specific ID). . If the determination in step S56 is NO, the process ends. If the determination in step S56 is YES, in step S57, a preset backup source identification ID (Trg ID) is extracted from the backup destination secure ID, and in step S58, the Src ID and Compare Tr gl D. In step S59, it is determined whether or not these matches are found. If they do not match, the process returns to step S53, and if they match, the backup process is started in step S60. When the backup process ends, the process ends.
- Trg ID preset backup source identification ID
- $ 13 is a flowchart showing the procedure for creating a backup source medium when a specific ID and identifier are used.
- step S65 the user inserts a medium to be used as a backup source into the security disk drive.
- step S66 the secure ID of the backup source is set. At this time, the Src ID, method identifier, and system identifier are written in the user-defined area of the secure ID, and the process ends.
- FIG. 14 is a flowchart showing a procedure for creating a backup destination medium when a specific ID and an identifier are used.
- step S70 the secure ID of the backup source is obtained, and in step S71, the specific ID (Src ID) of the secure ID is extracted, and the In step S72, the disc is ejected from the security disc drive.
- step S73 the user inserts the medium used as the backup destination into the security disk drive, and in step S74, sets the backup destination secure ID.
- the Src ID, the method identifier, and the system identifier are written in the user-defined area of the secure ID, and the process ends.
- the user has to enter the disk password, authenticate the disk, and then determine whether the disk is the correct backup destination disk.
- the authentication eliminates the need for the user to repeatedly enter a password to determine the backup destination disk.
Abstract
Description
Claims
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/JP2003/007037 WO2004109520A1 (ja) | 2003-06-03 | 2003-06-03 | バックアップ方法 |
JP2005500536A JP4252997B2 (ja) | 2003-06-03 | 2003-06-03 | バックアップ方法 |
CNA038260115A CN1745368A (zh) | 2003-06-03 | 2003-06-03 | 备份方法 |
US11/189,653 US20060010490A1 (en) | 2003-06-03 | 2005-07-26 | Backup method |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/JP2003/007037 WO2004109520A1 (ja) | 2003-06-03 | 2003-06-03 | バックアップ方法 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/189,653 Continuation US20060010490A1 (en) | 2003-06-03 | 2005-07-26 | Backup method |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2004109520A1 true WO2004109520A1 (ja) | 2004-12-16 |
Family
ID=33495913
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2003/007037 WO2004109520A1 (ja) | 2003-06-03 | 2003-06-03 | バックアップ方法 |
Country Status (4)
Country | Link |
---|---|
US (1) | US20060010490A1 (ja) |
JP (1) | JP4252997B2 (ja) |
CN (1) | CN1745368A (ja) |
WO (1) | WO2004109520A1 (ja) |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP5878360B2 (ja) * | 2011-12-19 | 2016-03-08 | インターナショナル・ビジネス・マシーンズ・コーポレーションInternational Business Machines Corporation | データのメデイア移行時における改ざんを検出する方法、及び記憶装 |
US9514002B2 (en) * | 2013-09-13 | 2016-12-06 | Vmware, Inc. | Incremental backups using retired snapshots |
US9772907B2 (en) | 2013-09-13 | 2017-09-26 | Vmware, Inc. | Incremental backups using retired snapshots |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH07287655A (ja) * | 1994-04-18 | 1995-10-31 | Ricoh Co Ltd | 情報処理装置 |
JPH0816481A (ja) * | 1994-06-30 | 1996-01-19 | Nec Field Service Ltd | 外部記憶媒体の情報保護システム |
JPH11249967A (ja) * | 1998-02-27 | 1999-09-17 | Fanuc Ltd | Ncデータの不正複写防止方法 |
JP2002312249A (ja) * | 2001-04-12 | 2002-10-25 | Yamaha Corp | コンテンツ再生装置のバックアップ方法およびバックアップ用記憶メディア |
Family Cites Families (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP3389186B2 (ja) * | 1999-04-27 | 2003-03-24 | 松下電器産業株式会社 | 半導体メモリカード及び読み出し装置 |
JP2001014221A (ja) * | 1999-04-27 | 2001-01-19 | Victor Co Of Japan Ltd | コンテンツ情報記録方法及びコンテンツ情報記録装置 |
JP2001022859A (ja) * | 1999-04-27 | 2001-01-26 | Victor Co Of Japan Ltd | コンテンツ情報記録方法、コンテンツ情報記録装置、コンテンツ情報記録再生方法、コンテンツ情報記録再生装置、及びメディア |
JP2001243106A (ja) * | 2000-02-28 | 2001-09-07 | Ricoh Co Ltd | 記録媒体及びそのアクセス制御方法 |
JP4012664B2 (ja) * | 2000-04-11 | 2007-11-21 | 株式会社リコー | 記録媒体及びそのアクセス制御方法 |
US6944662B2 (en) * | 2000-08-04 | 2005-09-13 | Vinestone Corporation | System and methods providing automatic distributed data retrieval, analysis and reporting services |
US20020071567A1 (en) * | 2000-12-12 | 2002-06-13 | Kurn David Michael | Scalable computer system using remote agents to manipulate cryptographic keys |
US8745409B2 (en) * | 2002-12-18 | 2014-06-03 | Sandisk Il Ltd. | System and method for securing portable data |
US7240219B2 (en) * | 2003-05-25 | 2007-07-03 | Sandisk Il Ltd. | Method and system for maintaining backup of portable storage devices |
-
2003
- 2003-06-03 WO PCT/JP2003/007037 patent/WO2004109520A1/ja active Application Filing
- 2003-06-03 CN CNA038260115A patent/CN1745368A/zh active Pending
- 2003-06-03 JP JP2005500536A patent/JP4252997B2/ja not_active Expired - Fee Related
-
2005
- 2005-07-26 US US11/189,653 patent/US20060010490A1/en not_active Abandoned
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH07287655A (ja) * | 1994-04-18 | 1995-10-31 | Ricoh Co Ltd | 情報処理装置 |
JPH0816481A (ja) * | 1994-06-30 | 1996-01-19 | Nec Field Service Ltd | 外部記憶媒体の情報保護システム |
JPH11249967A (ja) * | 1998-02-27 | 1999-09-17 | Fanuc Ltd | Ncデータの不正複写防止方法 |
JP2002312249A (ja) * | 2001-04-12 | 2002-10-25 | Yamaha Corp | コンテンツ再生装置のバックアップ方法およびバックアップ用記憶メディア |
Also Published As
Publication number | Publication date |
---|---|
JPWO2004109520A1 (ja) | 2006-07-20 |
US20060010490A1 (en) | 2006-01-12 |
JP4252997B2 (ja) | 2009-04-08 |
CN1745368A (zh) | 2006-03-08 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
TW563319B (en) | Method and device for controlling distribution and use of digital works | |
TWI239447B (en) | Recordable storage medium with protected data area | |
JP4520755B2 (ja) | データ移行方法およびデータ移行装置 | |
JP3748155B2 (ja) | 改ざん防止/検出機能を有するファイル管理システム | |
US7774610B2 (en) | Method and apparatus for verifiably migrating WORM data | |
TWI221993B (en) | System and method for searching for duplicate data | |
US7913044B1 (en) | Efficient incremental backups using a change database | |
JP2006228203A (ja) | ストレージボリュームのデータ正常性を保証する方法 | |
US20050246392A1 (en) | Data alteration checking apparatus and method and recording medium | |
US20080183771A1 (en) | System and method for managing files | |
US11601281B2 (en) | Managing user profiles securely in a user environment | |
JP4436490B2 (ja) | デジタルデータ記録再生システム | |
JP2008035397A (ja) | 暗号情報処理方法および暗号情報処理装置 | |
US20060123483A1 (en) | Method and system for protecting against illegal copy and/or use of digital contents stored on optical or other media | |
WO2011121927A1 (ja) | デジタルコンテンツ管理システム、装置、プログラムおよび方法 | |
US7017044B1 (en) | Extremely secure method for keying stored contents to a specific storage device | |
US6718466B1 (en) | Data medium with restorable original base data content, and method for its production | |
RU2715288C1 (ru) | Система и способ удаления файлов и противодействия их восстановлению | |
JP4266412B2 (ja) | データ保存システム | |
US20080155319A1 (en) | Methods and systems for managing removable media | |
WO2004109520A1 (ja) | バックアップ方法 | |
US20080226082A1 (en) | Systems and methods for secure data backup | |
US8015342B2 (en) | Method of managing and restoring identifier of storage device and apparatus therefor | |
JP4352601B2 (ja) | データ改竄チェック方法および装置、ならびに、記録媒体 | |
KR20050032016A (ko) | 메모리 카드 내의 파일 구조 관리 방법 및 관련 기술 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): CN JP US |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PT RO SE SI SK TR |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WWE | Wipo information: entry into national phase |
Ref document number: 2005500536 Country of ref document: JP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 11189653 Country of ref document: US |
|
WWE | Wipo information: entry into national phase |
Ref document number: 20038260115 Country of ref document: CN |
|
WWP | Wipo information: published in national office |
Ref document number: 11189653 Country of ref document: US |
|
122 | Ep: pct application non-entry in european phase |