WO2001077835A1 - Systeme de sauvegarde/recuperation de donnees - Google Patents
Systeme de sauvegarde/recuperation de donnees Download PDFInfo
- Publication number
- WO2001077835A1 WO2001077835A1 PCT/JP2001/003126 JP0103126W WO0177835A1 WO 2001077835 A1 WO2001077835 A1 WO 2001077835A1 JP 0103126 W JP0103126 W JP 0103126W WO 0177835 A1 WO0177835 A1 WO 0177835A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- data
- backup
- primary
- database
- control mechanism
- Prior art date
Links
Classifications
-
- 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
-
- 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/1471—Saving, restoring, recovering or retrying involving logging of persistent data for recovery
Definitions
- the present invention relates to a data backup / recovery method in a computer, and particularly to a method for providing a computer data backup to a secondary system.
- the present invention relates to a data backup 'recovery method that greatly reduces the time and labor required for recovery by greatly reducing the time and labor required for backup and using the backup data.
- the first conventional data backup method is a method of periodically obtaining a copy of the entire file.
- the second conventional data pack up method is to make a copy of the entire file at regular intervals and to store the updated data in a log file when the file is updated during a period in which no copy is made.
- the third conventional data pack up method is a method for preparing for abnormal termination of a program or transaction 'cancel'.
- the fifth conventional data backup method is to perform backups in order to deal with disasters.
- the conventional sixth data pack up method is a method of performing backup in preparation for destruction of a file medium.
- the conventional seventh data backup method is a method of acquiring a backup when the positive data is updated.
- the normal data refers to so-called production data, that is, data that directly performs processing.
- the first conventional data backup method is a method that periodically acquires a copy of the entire file.
- the first data backup method when the primary data was updated after the primary data was copied, the updated firewood data was not reflected in the backup file. Therefore, in the first data backup method, there was a danger that a large amount of updated data would be lost, depending on the backup interval.
- the conventional second data backup method mainly performs online backup processing, and regularly obtains a copy of the entire file on a magnetic tape, etc., and updates the file during periods when copying is not performed.
- a log file was created, the log file was backed up by using a magnetic disk device or a magnetic tape device. More specifically, the following method is used, although there are some differences in the specific backup method.
- a copy of the entire file is obtained in case the data file is destroyed. This is determined by the operation, but is performed on a daily basis or once a week. At that time, there is also a method of obtaining a copy by dividing the entire file storing the original data without combining them.
- the log data includes a transaction log (hereinafter referred to as “ ⁇ log”), which is the update data itself, an image log before updating the data to be updated (hereinafter “ ⁇ log”), and a log after updating the data to be updated (hereinafter “ ⁇ log”). Log)).
- ⁇ log transaction log
- ⁇ log image log before updating the data to be updated
- ⁇ log log after updating the data to be updated
- the original data is destroyed due to a computer failure for some reason, the original data is restored to the state at the time of copying by using the most recently obtained entire copy or a part of the entire copy corresponding to the destruction. Is being restored. After that, it was restored to the state just before the file was destroyed using the log files after the copy was obtained.
- a conventional second data backup method there is a disadvantage that a considerable amount of time is required for obtaining a copy and restoring when a file is destroyed as the capacity of the primary data increases.
- the data update had to be stopped, and there was an inconvenience that it was difficult to operate for 24 hours.
- the first data knock-up method and the second data backup method described above deal with file or device failures.
- the third conventional data backup method is a method for preparing for abnormal termination of a program / transaction / cancellation.
- the third data backup method for example, in the event that a program terminates abnormally or a transaction 'cancel' occurs, one transaction (a group of processes) is started and then terminated. During this time, save the contents of the data to be updated before the update (the contents are the same as the B log). Abnormal termination of a program or transaction When the cancel occurs, the data updated by the transaction is restored using the contents before the update in order to restore the data to the state before the update.
- the copy data of the original data must be always stored in case of abnormal termination or transaction / cancel that occurs only occasionally.
- the fourth data pack up method is a method for preparing for a case where an update result is incorrect due to a program error.
- This fourth data backup method is problematic if the program is incorrect. For example, assume that if you withdraw “10,000 yen” from a deposit with a balance of “100,000 yen”, the withdrawn balance will be “11,000 yen”. Even in such a case, the fourth data backup method restores the original data to the state immediately before the erroneous program was applied, and then recovers the data by running the correct program based on the T log. Do.
- the fifth data backup method mainly for disaster countermeasures
- the purpose of obtaining the backup is to deal with disasters.
- “disaster” refers to fire, flood, earthquake, etc.
- the fifth conventional data backup method involves copying backup files and log files and placing them in a fireproof safe.
- the sixth data pack-up method is a method of performing a pack-up in preparation for destruction of a file medium.
- a knock-up technique called RAID Redundant Array of Inexpensive Disk
- RAID Redundant Array of Inexpensive Disk
- This sixth data pack-up method is a method of having the same file doubly, a method of writing the contents of a file in a distributed manner to a plurality of storage devices, or a method of dividing a data by creating a parity. And a method of writing data to a storage device.
- this data backup method it appears to CPU ⁇ ⁇ ⁇ ⁇ software that data is written to one disk device, and the production file and the backup file are stored in the same device. For this reason, there was a disadvantage that this method could not respond to disasters at all.
- the sixth data backup method cannot respond to backout in response to online abnormal termination, and cannot respond to returning data to a past time due to a program error. There was an inconvenience.
- this data backup method has the drawback that the writing process takes longer than usual, and the restoration for data destruction is performed in units of disk volumes. There was a drawback of becoming. Also, the raid (RAID) could not be constructed without the exact same equipment. The system which evolved this further is realized. This makes it possible to install a power backup device that mirrors a disk in a remote location. When the production disk device is updated, the address at which the updated data is stored and the updated content are transmitted to the backup device. If necessary,
- Some devices have a function to perform restoration using the update data stored in the backup device and execute it until the content becomes the same as that of the production device.
- the production and knock-up disk devices are configured with exactly the same performance and functions. Needed.
- the seventh conventional data backup method is a method of acquiring a backup when the positive data is updated.
- the seventh data backup method is to acquire all copies of the original data first, and then acquire the A log after that.
- the common features of the first to seventh methods, except for the sixth method, are that it is difficult or time-consuming to back up the index.
- a method called a database has been used online.
- This Inn Decks for example, have several levels, and have a complex format in which a large number of indexes can be updated, so many file formats are not targeted for knockup.
- the ability to write updates to the index to the A-port and enable Guatemalapari to make it possible to perform the backup was the power to make it a perfect mirror.
- Each conventional data backup method has the disadvantage that it takes time to obtain a copy of the entire file, and once the file is broken, it takes more time to repair it than it takes to copy it. .
- the conventional backup method basically acquires all copies of the original data on a regular basis, writes a log for each transaction, and restores the original data when restoring the original data. This is because it is necessary to write the log to a file after returning to the state at the time, and to ensure the latestness.
- the conventional data backup method has a disadvantage that the time required to acquire a copy of the primary data becomes longer in accordance with the data capacity, and the cost required to acquire the backup must be large.
- the costs mentioned here include labor costs for obtaining copies, costs for storage media for storing copies in addition to backup devices, and costs related to storage locations for storage media for storing backup data. I am looking forward to it.
- the present invention has been made in view of the above-described drawbacks, and has as its object to provide one type of data backup and recovery that can perform backup and recovery in a short time and at low cost. Disclosure of the invention
- a primary system that manages the position of this block using a location table that associates the block with the physical address of the random access memory, and manages a database stored in the random access memory;
- the primary system uses a main memory of a primary processing unit that performs application processing as the random access memory, and a database control mechanism that changes contents of a database in the random access memory; A primary backup recovery control mechanism for transmitting data of the changed content when the content of the database is changed,
- the sending system uses a main memory of a secondary processing device as a random access memory, and changes a backup database in the random access memory with the data sent from the primary backup recovery control mechanism.
- the data backup system according to the above-mentioned item 1, which is provided with a control mechanism. 3.
- the primary system is provided with a primary processing device for performing application processing and a primary storage device including a random access memory for storing a database separately from the main memory of the primary processing device. 2.
- the data pack-up * recovery method according to the above-mentioned 1, wherein a secondary processing device for executing the data processing and a secondary storage device comprising a random access memory for storing a database separately from the main memory of the secondary processing device are provided. .
- the primary system is provided with a primary processing device for performing application processing, and a primary storage device including a random access memory for storing a database separately from a main memory of the primary processing device,
- the sending system includes only a secondary storage device including a random access memory for storing a database,
- the sending storage device includes means for communicating backup data, and a secondary pack-up for changing the backup database with the data sent from the primary backup recovery control mechanism via the communication means.
- a recovery control mechanism With a recovery control mechanism,
- the primary system transmits the transaction start information when the transaction processing is started, and transmits to the secondary system the content of the updated data, the content of the update, and the information identifying the block in which the data is stored. And Each time the secondary system receives the updated data information, the secondary system updates the corresponding data based on the updated data information of the transaction,
- the primary system sends the contents of the updated data, the contents of the update, and information specifying the block in which the data is stored to the secondary system, and the secondary system transmits the transaction start information from the primary system.
- the log data in the transaction is received and the data is updated.
- the backup end information is transferred to the primary until the backup update processing ends.
- the primary system transmits transaction start information, and transmits to the secondary system information specifying the content of the updated data, the updated content, and the block in which the data is stored.
- the secondary system receives the updated data information
- the secondary system updates the corresponding data based on the updated data information of the transaction
- the primary system updates the data when the data update of the transaction ends.
- the primary system is responsible for the content of the updated data
- the secondary system transmits the information specifying the stored block to the secondary system, and after receiving the transaction start information from the primary system, receives the log data in the transaction and updates the data, After receiving the transaction end information from the primary system, an asynchronous loosely-coupled system is adopted in which the backup end information is not transmitted to the primary system until the backup update processing is completed. 3.
- the data backup / recovery method according to the item 2.
- the primary processing device includes: a communication unit that communicates backup data; a database control mechanism that changes the content of the database; and a database control mechanism that changes the content of the database when the database control mechanism changes the content of the database.
- a primary backup recovery control mechanism for transmitting data via the communication means, the secondary processing device comprising: a communication means for communicating backup data; and the primary backup recovery control mechanism via the communication means.
- a secondary pack application force parsing control mechanism for changing the pack application database with the transmitted data;
- the primary processing device and the secondary processing device are provided with only communication means for performing backup data communication between them, and
- the primary storage device comprises: a database control mechanism for changing the contents of the database; and a primary pack updater for transmitting the data of the changed contents via the communication means when the database control mechanism changes the contents of the database.
- the secondary storage device stores the pack-up database with the data transmitted from the primary pack-up recovery control mechanism via the communication unit. Equipped with a remote control mechanism,
- the primary system sends transaction start information when transaction processing is started, and sends to the secondary system information identifying the contents of the updated data, the updated contents, and the block in which the data is stored.
- the secondary system updates the relevant data each time the updated data information is received, based on the updated data information of the transaction.
- the primary system sends to the secondary system the content of the updated data, the updated content, and information identifying the block in which the data is stored.
- the secondary system receives the transaction start information from the primary system, receives the log data in the transaction, updates the data, and receives the transaction end information from the primary system, and then performs the backup. 4.
- the primary system transmits transaction start information when transaction processing is started, and updates the contents of the updated data, the updated contents, and information identifying the block in which the data is stored by the secondary system. Send to
- the secondary system Each time the secondary system receives the updated data information, the secondary system The primary system performs update of the transaction data based on the updated data information, and the primary system adopts a synchronous tightly coupled system in which when the data update of the transaction is completed, the update completion information is transmitted to the secondary system. 5.
- the primary system sends the contents of the updated data, the contents of the update, and information specifying the block in which the data is stored to the secondary system, and the secondary system sends the transaction start information from the primary system.
- the pack-up end information is transferred to the primary until the pack-up update processing is completed. 5.
- the data backup / recovery method according to the above item 4 wherein an asynchronous loosely-coupled method that is not transmitted to the system is adopted.
- a data backup / recovery method characterized by a primary system that manages a database stored in the random access memory by using a location table that associates the physical address of the random access memory with a physical address.
- the primary system uses a main memory of a primary processing unit that performs application processing as the random access memory, and a database control mechanism that changes contents of a database in the random access memory; When the contents of the database are changed, 15.
- the primary system is characterized in that a primary processing device for performing application processing and a primary storage device including a random access memory for storing a database separately from a main memory of the primary processing device are provided. 15. The data backup / recovery method according to 15 above.
- the primary processing device includes: a communication unit that performs communication of backup data; a database control mechanism that changes the content of the database; and a database control mechanism that changes the content of the database when the database control mechanism changes the content of the database.
- a communication unit that performs communication of backup data
- a database control mechanism that changes the content of the database
- a database control mechanism that changes the content of the database when the database control mechanism changes the content of the database.
- the primary processing device is provided with only communication means for communicating backup data
- the primary storage device is provided with a database control mechanism for changing the contents of the database
- the database control mechanism is provided with the contents of the database.
- the primary storage device includes: a communication unit that communicates backup data; a database control mechanism that changes the content of the database; and a database control mechanism that changes the content of the database when the database control mechanism changes the content of the database.
- the sending system uses a main memory of a secondary processing device for performing application processing as a random access memory, and uses the data sent from the primary system to be backed up as the random access memory.
- the secondary system is characterized in that a secondary processing device for performing application processing and a secondary storage device comprising a random access memory for storing a database separately from the main memory of the secondary processing device are provided.
- a secondary processing device for performing application processing and a secondary storage device comprising a random access memory for storing a database separately from the main memory of the secondary processing device are provided.
- the sending system has only a secondary storage device consisting of a random access memory for storing a database,
- the secondary storage device includes means for performing communication of backup data, and a secondary backup database for changing the backup database with the data transmitted from the primary system to be backed up via the communication means. Equipped with a remote control mechanism,
- the secondary processing device includes communication means for communicating knockup data, and a secondary means for changing the backup database with the data transmitted from the primary system to be backed up via the communication means.
- pack 26 The data according to the above item 26, comprising an up recovery control mechanism.
- the secondary processing device is provided with only communication means for communicating backup data
- the secondary storage device includes a secondary backup recovery control mechanism that changes the backup database with the data sent from the primary system to be backed up via the communication means.
- the secondary system adopts the synchronous tightly coupled method or the asynchronous loosely coupled method.
- at least one secondary system is prepared, and the blocks of the primary system and the secondary system are associated with each other in the same logical format as the primary data of the primary system.
- the secondary system updates when the primary data is updated, so the latest copy of the primary data is always kept in the backup file. Normally, only one secondary system is required, but multiple secondary systems can be prepared if necessary.
- the format of a file to be backed up is such that records are stored in a block, and management of block positions and the like is called a location table. It is managed by a table.
- the primary system uses a location table and a block as a file storage method
- the secondary system uses a block that uses the backup file of the backup file in the primary system.
- FIG. 1 is a block diagram showing a configuration of a primary system and a secondary system for realizing a data backup / recovery system according to a first embodiment of the present invention.
- FIG. 2 is a block diagram illustrating in more detail a primary system and a secondary system for realizing a data backup / recovery method according to the first embodiment of the present invention.
- FIG. 3 is an explanatory diagram showing a connection table and a database block used in a primary system and a secondary system for realizing a data backup / recovery method according to the first embodiment of the present invention.
- FIG. 4 is a diagram for explaining a configuration of a block used in a primary system for realizing a data backup / recovery method according to the first embodiment of the present invention.
- FIG. 5 is a diagram showing a series of operations from the start to the end of one transaction in the data backup / recovery system that realizes the data backup / recovery system according to the first embodiment of the present invention. This is a chart for explaining the operation.
- FIG. 6 is a chart for explaining the operation of the synchronous tightly coupled system in the data backup / recovery system that realizes the data backup / recovery system according to the first embodiment of the present invention.
- FIG. 7 shows a data backup 'recovery method according to the first embodiment of the present invention. This is a chart to explain the operation of the asynchronous loosely coupled method in the data backup and recovery method that realizes the expression.
- FIG. 8 is a block diagram showing another configuration of the primary system and the secondary system for realizing the data backup and recovery method according to the second embodiment of the present invention.
- FIG. 9 is a block diagram showing another configuration of the primary system and the secondary system for realizing the data backup / recovery method according to the third embodiment of the present invention.
- the present invention proposes a data storage method (Japanese Patent Application Laid-Open No. 11-31096), and this data storage method will be described below as a method for data backup and recovery. However, for convenience of explanation, this data storage method will be described.
- FIG. 1 is a block diagram showing a configuration of a primary system and a secondary system that realize a data backup and recovery method according to an embodiment of the present invention.
- the present invention packs a predetermined area of a main memory of a commonly used computer.
- the backup storage device can be used as an alternative to the conventional hard disk device.
- FIG. 1 shows a case where a predetermined area (part) of a main memory of a commonly used computer is used as a backup storage device.
- reference numeral 1 denotes a primary system constituted by a computer
- reference numeral 2 denotes a secondary system constituted by the same computer
- the primary system 1 is a set of storage devices (memory) for updating data first.
- the secondary system 2 is a system that acquires a backup. Both the primary system 1 and the secondary system 2 use multiple storage devices instead of a single storage device to minimize damage from storage device (memory) failure.
- the primary system 1 and the secondary system 2 are connected via a communication network 3 so that data can be exchanged between the two.
- the primary system 1 uses a CPU 11 and a main memory, and a random access memory 12 that uses a predetermined area of the main memory as a backup storage device, a communication control device 13, It comprises a backup recovery control mechanism 14, a database control mechanism 15, an input / output terminal communication control mechanism 16, an application program 17, and other means (not shown). Further, the random access memory 12 is provided with a database area 12 a for storing the database 18.
- the random access memory 12 may be, for example, a semiconductor memory device or any other random access memory.
- the primary system 1 enters and exits via the I / O terminal communication control mechanism 16. Input terminals 4, ... are connected.
- the secondary system 2 includes a CPU 21, a random access memory 22, a communication control device 23, a backup recovery control mechanism 24, and other means (not shown).
- the random access memory 22 includes a backup database area 22 a for storing the backup database 25, a log history storage area 22 b for storing the log history data 26, and other storage areas (not shown). Zu).
- the random access memory 22 may be, for example, a semiconductor memory device or any other random accessible memory.
- the data input to the input / output terminal 4 is sent to the input / output terminal communication control mechanism 16 (S l).
- this data is received by the application program 17 (S2).
- the application program 17 transmits a series of database operation instructions and the received data (T log) to the database control mechanism 15 (S3).
- data is transmitted from the input / output terminal communication control mechanism 16 to the primary backup recovery control mechanism 14 (S3).
- the number of files can be created as needed, and there is no limit.
- the explanation mainly focuses on online processing, but even batch processing can be executed with the same logic as long as it is a processing that cuts a transaction.
- the database control mechanism 15 updates the target database 18 (S4).
- the primary backup recovery control mechanism 14 transmits log data to the secondary system 2 via the communication control device 13 and the communication network 3 based on these instructions (S5).
- the received various log data is stored in the storage area as log history data 26 by the backup recovery control mechanism 24 (S6).
- the backup recovery control mechanism 24 uses the log data to The database 25 is updated (S7).
- the knock-up processing completion information is notified to the primary system 1 via the communication control device 23 and the communication network 3 by the secondary knock-up recovery control mechanism 24 (S 8).
- the exclusive record of the application program 17 is released from the exclusive record by the primary backup recovery control mechanism 14 (S9).
- the primary system 1 and the secondary system 2 operate, and when the database 18 of the primary system 1 is updated, the backup database 25 of the secondary system 2 is updated.
- the equipment for implementing the above-mentioned data backup and recovery method has one set of storage devices (memory) for production, and one or more sets of storage devices (memory) for backup, and the access speed of those devices.
- Each storage device (memory) is connected to the processing unit, and reads, writes, updates, and deletes it according to the instructions of the processing unit.
- the processing device is independent for each storage device.
- the concept of a set of storage devices (memory) is as follows.
- FIG. 2 is a block diagram illustrating the primary system and the secondary system in more detail.
- the primary system 1 is shown in a configuration in which a CPU 11, a random access memory 12, and a communication controller 13 are connected by a bus line 19.
- the random access memory 12 12a and a program reading area 12b.
- the database 18 is stored in the database area 12a.
- the database 18 stores primary location tapes 5 and primary blocks 6a, 6b, 6c,...
- the secondary system 2 has a configuration in which a CPU 21, a random access memory 22, and a communication control device 23 are connected by a bus line 29.
- the random access memory 22 includes a backup database area 22a, a log history storage area 22b, and a program read area 22c.
- a backup database area 22a In the backup database area 22a, a secondary location table 7 and knockup blocks 8a, 8b, 8c,... Are stored.
- log history data 26 is stored in the log history storage area 22b.
- the primary location tape holder 5 and the primary blocks 6a, 6b, 6c, ... in the primary system 1 correspond to the secondary location table 7 and the backup blocks 8a, 8b, 8c, ... in the secondary system 2. Let me.
- the figure shows only one type of database consisting of the primary location table 5 and the primary blocks 6a, 6b, 6c,...
- the primary system 1 usually there are many databases.
- a human resources management database for example, a salary database, an inventory management database, or a customer management database.
- FIG. 3 is an explanatory diagram showing location tables and database blocks used in the primary system 1 and the secondary system 2.
- the primary location table 5 used in the primary system 1 has block numbers 51 a, 51 b, etc., from the top, such as block “0”, block “1”, block “2”, block “3”,. ... Are allocated, and the physical addresses 52 a, 52 b, 52 c,... of the random access memory 12 are allocated to the block numbers 5 la, 51 b, 51 c,..., respectively. I have.
- the primary blocks 6a, 6b, 6c, ... corresponding to the block numbers 51a, 51b, 51c, ... described in the primary location table 5 are physical addresses described in the table 5. 52a, 52b, 52c,... Are arranged and stored in the database storage area 12a of the random access memory 12.
- the figure shows a state where overflow blocks 9c and 9e are attached to primary blocks 6c and 6e.
- the primary location table 5 and the secondary bite application table 7 need not have the same physical content but have the same logical content.
- the secondary location table 7 used in the secondary system 2 is also block number 0 la, block 1, block 2, block 3, and so on from the top, and the block numbers 7 la, 71 b, 71 are assigned, and the physical addresses 72a, 72b, 72c,... of the random access memory 22 are respectively assigned to the block numbers 71a, 71b, 71c,.
- the backup blocks 8a, 8b, 8c, ... corresponding to the block numbers 71a, 71b, 71c, ... described in the secondary location table 7 are the physical blocks described in the table 7. Are arranged and stored in the random access memory 22 in accordance with the addresses 72a, 72b, 72c,...
- FIG. 4 is a diagram for explaining the configuration of the block used in the primary system.
- the blocks can be classified into a primary block 6 and an overflow block 9.
- the primary block 6 has a block number 61, a primary key value 62, an overflow key value 63, records 64a, 64b ..., and an overflow block address 65.
- the primary key value 62 has FR ⁇ M and TO, and FROM and TO are the keys in the block 6 concerned. The minimum and maximum values are shown.
- the overflow key value 63 is provided with F ROM and T O, and F ROM and T O indicate the minimum value and the maximum value of the key value in the overflow block.
- the key value may have both or one of FROM and T0.
- the primary key value 62 and the overflow key value 63 have FROM and TO, but they can be combined into one set.
- the above overflow block 9 is used when the record 64 cannot be stored in the primary block 6.
- the overflow block 9 is managed as a subordinate block of the primary block 6 and is only pointed to from the primary block 6, but is not managed in the location table 5. If one overflow block 9 is not enough, add one more. In such a situation, the overflow block 'address 91 is used to indicate the position of the first overflow block 9 to the second overflow block 9.
- the record 64 used in the primary system 1 has a unique key (a key value of a different record is not duplicated) in a data record.
- 6 4 1 and zero or more non-numeric keys (the key values of different records may be duplicated, hereinafter referred to as “alternate keys”) 6 4 2 Use a structure with data 6 4 3.
- the database control mechanism 15 of the primary system 1 stores one unique primary key 6 41, an alternate key 6 42, and data 6 43 in the data record. Is stored in the fixed-length block 6 in the order of the primary key 6 4 1 or more. Then, the record 64 is first stored in the primary block 6 by the database control mechanism 15. Record If it becomes impossible to store the data in the primary block 6 due to the input of the mode 6 4 a, 64 b,..., the overflow block 9 is assigned to the primary block 6, and one overflow probe block 9 is assigned. If it cannot be stored, one more overflow block 9 'is allocated, and records 64a, 64b, ... are stored as blocks by linking the blocks 6, 9, 9'.
- each block 6a, 6b, 6c, ... does not need to be created in advance, but can be created as needed, and the physical data storage area becomes full. Up to can be created.
- FIG. 5 is a chart for explaining a series of operations from the start to the end of one transaction.
- data update refers to all operations that change the file, including new addition and deletion of data.
- a “transaction” is a set of related operations on a computer system. For example, a series of processes when one customer withdraws a deposit. If you apply this method, you must first copy the full copy of the primary data only once from the primary system 1 that stores the primary data to the backup database 2 Perform this for the secondary system 2 that stores 5.
- each block 6 has a block number 61 in order, but the secondary system 2 also has a backup block corresponding to the primary system 1 on a one-to-one basis.
- a secondary location table 7 is prepared to manage the backup blocks 8a, 8b, 8c, ....
- the data processing system consisting of the primary system 1 and the input / output terminal 4 is operated. Then, the database control mechanism 15 of the primary system 1 notifies a transaction start (S101), and transfers the data T1 (S102).
- the backup recovery control mechanism 14 of the primary system 1 needs the updated data (A log (A1)) as the updated data.
- a B log (Bl) and a T log (not shown) are transmitted to the secondary system 2 (S104). Storing those logs on the primary system is also useful when needed.
- the backup recovery control mechanism 24 of the secondary system 2 Upon receiving the data T1 (S201), the backup recovery control mechanism 24 of the secondary system 2 stores the data T1 in the log history data 26 (S202). Next, when the backup recovery control mechanism 24 of the secondary system 2 receives the A log (A1) (S203), the backup block 8a, 8b, 8c inside the backup database 25 in which the A log (A1) is to be stored is stored. Look for,.... This can be done by searching for the backup block 8a, 8b, 8c,... Having the same number as the block number 61 of the block 6 of the primary system 1.
- the backup recovery control mechanism 24 searches for the corresponding data in the backup blocks 8a, 8b, 8c,... And rewrites them with the A log (A1) (S204). Further, the backup recovery control mechanism 24 stores the B log (B1) in the log history data 26 (S205). This ensures that the primary system 1 and secondary The data in the primary system 2 is kept in a consistent state, and it is possible to cope with the failure of the primary system.
- the backup control unit 14 of the primary system 1 transmits the additional data (A log (A2 )) To the secondary system 2 (S106).
- the backup recovery control mechanism 24 of the secondary system 2 receives the A log (A2) (S206), the backup block 8a, 8b, 8c, which has the same number as the block number 61 of the block 6 of the primary system 1 (S206). ... are stored in the corresponding backup block 8 (S207).
- the backup recovery control mechanism 24 stores the log (A2) in the log history data 26 (S208). As a result, the data of the primary system 1 and the data of the secondary system 2 are always kept in a consistent state, and it is possible to deal with the failure of the primary system.
- the backup recovery control mechanism 14 of the primary system 1 deletes the deleted data (A log (A3), B log (B3)) is transmitted to the secondary system 2 (S108).
- the backup recovery control mechanism 24 of the secondary system 2 receives the A log (A3, B log (B3)) (S209), the backup recovery control mechanism 24 of the backup system 8 having the same number as the block number 61 of the block 6 of the primary system 1 Search for 8b, 8c, ..., and delete the data in the backup block 8 (S210).
- the backup recovery control mechanism 24 stores the deleted data (A log (A3), B log (B3)) in the log history data 26 (S211).
- the data in the primary system 1 and the data in the secondary system 2 are always kept in a consistent state, and it is possible to deal with the failure of the primary system 1.
- the backup recovery control mechanism 14 of the primary system 1 sends a transaction end notification to the secondary system 2 (S109).
- the backup recovery control mechanism 24 completes all data updates related to the transaction, and immediately after that, updates the backup end information to the primary system 1. (S213).
- the backup recovery control mechanism 14 of the primary system 1 executes an exclusive release process (S110).
- the B log and T log will be described.
- the B log is returned to the past point and the correct program is returned to the T log.
- the retention periods of the B log and T log may be determined individually as needed.
- a backup of the file is always kept in the secondary system 2 and there is no need to copy it to another medium, but obtaining a copy of the file at a certain point in time is contrary to the spirit of the present invention. Not something.
- the index it is not necessary to make a backup because the storage system adopted in the primary system 1 has a simple structure and data can be easily reproduced in a short time. Even if you get, it is easy in the same format as data Can be done.
- the data is stored in the fixed-length primary block 6 without being compressed, and is stored in the overflow block 9 as needed (see FIGS. 3 and 4 (c)). If necessary, an overflow block 9 'is created (see FIGS. 3 and 4 (c)).
- the location table 7 is prepared for the entry prepared in the primary system 1.
- the block lengths of the backup blocks 8a, 8b, 8c,... Change.
- the block lengths of the backup blocks 8a, 8b, 8c,... are variable, and if the primary block 6 of the primary system 1 has an overflow block 9, It is regarded as one backup block 8c, 8e, ... including the floppy block 9.
- the secondary block 2 may adopt the primary block 6 and the overflow block 9 as in the case of the primary system 1.
- the knockup block 8 is managed by the secondary application table 7. To find a specific backup block 8a, 8b, 8c,..., find and access the address of the backup block 8a, 8b, 8c,... from the backup recovery control mechanism 24 of the secondary system 2. I do.
- the alternate key table on the primary system 1 does not need to be backed up because it is easy to restore, but if you want to perform fast recovery, the secondary key table Keep in system 2.
- the substitute key table is described in the data storage method (Japanese Patent Laid-Open No. 11-31096), but is stored in the format shown in FIG.
- the B log which is the information before the update, is acquired first, and then the contents of the update, as in the process when the primary block is updated A log that is sent to the secondary 'system.
- the Secondary 'system updates the secondary / alternate key / table based on the information in the A log. It is preferable to include the block number in the A log because the alternate key 'table has a block number.
- the secondary system detects the target secondary / alternate key table based on the block number and updates the corresponding block.
- pre-alternate key table creates a pre-alternate key table on the secondary 'system' in the same format as the primary 'system.
- the case of updating data will be described. Online data processing is always performed on the primary system 1, and data updates are performed directly on the primary system 1.
- the data communication sequence between the primary system 1 and the secondary system 2 includes a “synchronous tightly coupled system” and an “asynchronous loosely coupled system”.
- the backup by the secondary system 2 is performed in synchronization with the update in the primary system 1, and the secondary system 2 is coupled near the primary system 1 by a high-speed transmission means. This method assumes that the
- the “asynchronous loosely-coupled method” is a secondary system with the primary purpose of disaster response. It is assumed that 2 is installed at a location away from the primary system 1 and connected using a communication line.
- FIG. 6 is a chart for explaining the operation of the synchronous tightly coupled system.
- the transaction start information is transmitted from the primary system 1 to the secondary system 2 (see FIG. 5).
- the information to be transmitted shall include information identifying the transaction. This information shall transmit the transaction number.
- data is updated (including updates, additions, and deletions) after the transaction has started, the data is updated directly to the target database 18 in the random access memory 12 of the primary system 1. It is done on a regular basis.
- the contents of the updated data A log
- the contents of the update discretion, addition, deletion
- file identification the block number where the data is stored
- the beginning address of the record in the block must be added. Is preferred.
- file identification is used to identify multiple files in one system, which makes processing impossible unless it is known which file has been updated. is there.
- the backup recovery control mechanism 14 of the primary system 1 attaches such information to the secondary system 2 as updated data information by attaching information such as transaction number and transmission time so that the order of the data can be distinguished (Fig. 5 And Figure 6
- the primary system 1 acquires the data contents (B log) before the update before updating the primary data.
- the B log may or may not be sent to the secondary system 2 as needed.
- the advantage of sending to the secondary system 2 is that the secondary system 2 also retains the B log, which reduces the risk of losing the log, and in the event of a transaction cancellation, the secondary system 2 Work is faster.
- the secondary system 2 whenever the updated data information (A log) arrives, the corresponding data is immediately updated based on the updated data information of the transaction (S204, S207, S210 in FIG. 5). ).
- the term “data update” refers to rewriting data by replacing the data with the contents of the updated data information.
- the contents may be stored in a compressed state.
- the update completion information is transmitted from the primary system 1 to the secondary system 2 (S213 in FIGS. 5 and 6).
- the same processing is performed for all the secondary systems 2.
- transaction 2 will be described. Again, when the transaction processing is started on the primary system 1 (S121 in FIG. 6), the transaction start information is transmitted from the primary system 1 to the secondary system 2 (S1 in FIG. 6). twenty two). If data is updated (including updates, adds, and deletes) after the transaction has started, the data is updated directly to the target database 18 in the random access memory 12 of the primary system 1. It is done.
- the backup recovery control mechanism 14 of the primary system 1 attaches such information to the secondary system 2 as updated data information by adding information such as a transaction number and transmission time so that the order of the data can be distinguished (FIG. 6). S123, S124, S125, S126).
- the secondary system 2 After the update Whenever the data information arrives, the relevant data is updated immediately based on the updated data information of the transaction (S223, S224, S225, S226 in Fig. 6).
- the primary system 1 locks the data to prevent double updates from occurring.However, when the backup end information from the secondary system 2 becomes available, the lock is released. Yes (S128 in Fig. 6) 0
- the primary system 1 completes the transaction (S127 in Fig. 6) and waits for the next transaction processing before the backup completion information is sent from the secondary system 2 (S128 in Fig. 6). There is no need to start a transaction (S131 in Fig. 6). If it becomes necessary to update the data, another wait occurs when the data is locked, so double update is performed on the primary system 1 before the backup data update on the secondary system 2 is completed. There is no possibility that it will be done.
- the primary system 1 should have received the backup completion information from at least one of the secondary systems 2 among the multiple secondary systems 2 and cancel the other. Is also possible.
- transaction 3 is explained.
- the transaction start information is transmitted from the primary system 1 to the secondary system 2 (see FIG. 6).
- S 1 32 If data is updated (including updates, additions, and deletions) after the transaction has started, the data is updated directly to the target database 18 in the random access memory 12 of the primary system 1.
- the backup recovery control mechanism 14 of the primary system 1 adds the information such as the transaction number and the transmission time, which can distinguish the order of the data, to the secondary system 2 as updated data information with the information (the sixth data).
- S133, S134, S135, S136 in the figure In the secondary system 2, whenever the updated data information arrives, the corresponding data is immediately updated based on the updated data information of the transaction (S233, S234, S235, S236 in Fig. 6). .
- the next transaction processing is performed before the primary system 1 completes the transaction (S127 in Fig. 6) and the backup completion information is sent from the secondary system 2 (S128 in Fig. 6). There is no need to wait, and the transaction starts (S131 in Fig. 6). If it becomes necessary to update the data, the system waits for exclusion at the time of exclusion of the data.Therefore, before the backup data update in the secondary system 2 is completed, the primary system 1 performs double update. There is no possibility to be done. In this way, by performing the processing one after another and performing the processing such as the transaction and the data update, the data backup 'recovery becomes possible.
- the log acquisition method is as follows.
- the B log uses the pre-update information as it is.
- the necessity of the B log is used when returning the positive data for an arbitrary time.
- the T log uses the incoming update data as it is.
- the necessity of the T log is used when a program error requires re-processing.
- the BP logs and T logs may be stored on the primary system 1, but when they are to be backed up, they are transmitted to the secondary system 2 and stored. In the above description, the backup of data blocks is described. A description will be given of the backup of the option table and the alternative key table.
- the primary location tape storage 5 of the primary system 1 is changed as the primary block 6 is added as data is added.
- the backup block 8 is also added in the secondary system 2.
- the secondary location table 7 of the secondary system 2 is also automatically generated, so that direct backup is not required.
- a backup of the alternate key table is not essential, but it is desirable to make it a backup target for fast recovery.
- the storage block of the substitute key table is transmitted from the primary system 1 to the secondary system 2.
- the corresponding substitute key block is updated as it is. It is preferable to detect the corresponding alternate key block by detecting the force by the displacement from the top of the alternate key table or by assigning a number to the alternate key block and detecting it with the number. Is also possible.
- FIG. 7 is a chart for explaining the operation of the asynchronous loosely coupled system.
- the primary system 1 sends the transaction opening information to the secondary system 2 in the same manner as the synchronous tight coupling method (S301 in FIG. 7). ).
- the transaction number is used. If data is updated (including updates, adds, and deletes) after the transaction has started, the data update is This is performed directly on the database 18 of the random access memory 12 of the memory system 1. Contents of data after update (A log) and contents of update (areas of update, addition, and deletion (J), file identification, block number where data is stored, and start address of record in block) This speeds up position detection when writing to the secondary system 2.
- file identification has already been described, it will be described here. If there are multiple files in one system, it is impossible to process them without knowing which file has been updated, but this is to identify them.
- the primary system 1 adds the contents of the updated data (A log) and the contents of the update (discrimination between update, add, and delete), file identification, the block number where the data is stored, and the start address of the record in the block.
- the collected information is transmitted to the secondary system 2 (S302 to S304).
- the primary system 1 attaches such information to the secondary system 2 as updated data information by attaching information such as the transaction number and the transmission time so that the data order can be distinguished.
- the T log and the B log are the same as in the synchronous tightly coupled system. After updating the data, it is possible to send the entire record, but the amount of data sent will increase, so it is also possible to extract only the changed part and send it with an offset value and length It is.
- the secondary system 2 receives the information of the start of the transaction (S401 in FIG. 7) and thereafter receives the log data in the transaction and updates the corresponding data of the secondary system 2 (S4 in FIG. 7). 0 2 to S 4 0 4).
- the backup end information is transmitted to the primary system when all backup update processing in the secondary system is completed (S405 in FIG. 7). ).
- the primary system 1 discards the A log of the transaction in which the information came (S306 in FIG. 7), but it is also possible to keep it if necessary.
- a Log information is 'Since it is directly reflected on the lock, it is not usually necessary to save it, but it is effective when you want to keep the update difference.
- the backup processing in the secondary system 2 and the update processing in the primary system 1 are executed asynchronously, so that the update contents are reflected in the data on the secondary system 2 in reverse. There is a danger that it will not be possible to secure the property, but this can be avoided by the following methods.
- the secondary system 2 whenever the updated data information arrives, the corresponding data is immediately updated based on the updated data information of the transaction (S402 to S404 in FIG. 7).
- Updating the data means rewriting the data by replacing the data with the contents of the updated data information. The contents are stored in a compressed state. When all data updates of the transaction have been completed, the next transaction is processed. Thereafter, by repeating the above processing, data backup and recovery can be performed.
- the primary system 1 Send transaction / cancel information to Danley System 2.
- This information includes pre-update information (B) of all data updated by the transaction, in addition to the information of “which transaction terminated abnormally” or “cancelled”. .
- the secondary system 2 having received the transaction 'cancel information restores all the data to the state before the update based on the information before the update. This is the same as what is done on primary system 1. All secondary systems 2 send an end of repair to primary system 1.
- the primary system 1 be distributed to a plurality of storage devices (memory). In this case, the failure mostly occurs in a part of the primary system 1.
- the recovery method in this case is as follows.
- the spare device is the primary system 1 and has the same capacity and performance as the divided storage device (memory). Disconnect the storage (memory) of the failed primary system 1 and replace the spare with the storage (memory) Appropriate for Copy the data corresponding to the data stored in the failed device from the secondary system 2. During this time, all other processing is stopped. Then, when the copying is completed, the processing is restarted. In this method, processing is interrupted for a certain period of time, but subsequent processing can be performed at a normal speed, and backups can be obtained reliably.
- Hot swapping can be used as this method.
- This hot swap means that the random access memory 22 of the secondary system 2 is used as it is as the storage device (memory) of the primary system 1. In this case, if there are two or more secondary systems 2, no backup problem will occur, but if there is only one secondary system 2, the backup system will be temporarily lost. is necessary.
- the secondary system 2 When a failure occurs, the secondary system 2 is updated to the latest state, and the random access memory 22 of the secondary system 2 is used as a storage device (memory) of the primary system 1.
- the random access memory 12 having a failure in the primary system 1 the failed device is separated and a spare device for the failure is allocated. This is used as a storage device (memory) of the secondary system 2.
- the primary system 1 continues normal operation.
- the data of the spare device of the new secondary system 2 is restored.
- the data of the spare device is read from the primary system 1 in order, sent to the secondary system 2, and written by the secondary system 2.
- the data in the primary system 1 continues to be updated, so the data written in the secondary system 2 may become outdated.
- Block 8 You only need to update, so you can synchronize without any problem.
- the location table and alternate key table there is a method of keeping backups in the secondary system 2 and copying and returning them in the event of a failure, as well as a method of recreating them based on data.
- the data contents of the primary system 1 and the secondary system 2 cannot be synchronized, and the data contents may be shifted. In such a state, if the primary system 1 is destroyed, copying the data of the secondary system 2 to the primary system 1 will result in the data being out of date and not being used. If there is data that has not been updated in the secondary system 2, the T log and the A log are transmitted to the secondary system 2 along with transaction start / end information. If a failure occurs in the primary system 1, the data processing is immediately suspended in the primary system 1.
- the secondary system 2 processes the remaining A logs to make the data content of the secondary system 2 the same as that of the primary system 1, and then If the data necessary for the Dally system 2 is compressed, the data is decompressed and transmitted before compression.
- the process is exactly the same until a spare device is assigned to the failed device.
- the primary system 1 continues the processing.
- the data stored in the device switched to the standby state is in a state where the backup is not performed.
- the data is transferred from the primary system 1 to the spare device of the secondary system 2 and the backup file is restored.
- the data since the data is sequentially transferred, the data of the block whose transfer has been completed may be updated, and there is a possibility that the up-to-dateness may not be ensured.
- the data is updated, when the data is updated, the data is transmitted to the secondary system 2.
- the data is processed in the same manner as in the normal processing to ensure the latestness.
- the data in the block that has not been backed up in the secondary system 2 is updated in the primary system 1, there is no block that applies the data, so logs such as A log Is destroyed in the secondary system 2.
- the data contents of the primary system 1 and the secondary system 2 cannot be synchronized, as in the case described above, and the data contents may be shifted. If a failure occurs in the secondary system 2, the necessary data is copied from the primary system 1 to the secondary system 2, and when the operation is completed, the system starts operation.At that point, the secondary system 2 is switched to the primary system. If there is a difference from the primary system 1, the necessary blocks are first copied from the primary system 1 to the secondary system 2. Thereafter, using the transaction end information from the secondary system 2, a transaction that has been terminated on the primary system 1 and has not been terminated on the secondary system 2 is detected, and the data of the secondary system 2 is detected using the corresponding A log. Update the content.
- the latest backup is always kept on the secondary system 2.
- the data on the secondary system 2 can be used for reference-based transaction processing. It is generally said that the ratio of the update system to the reference system is about 1 to 10. This means that by separating the reference system, the load on the system handling the update system can be reduced.
- the secondary system 2 By using the secondary system 2 as reference data, it is much easier to construct a reference system using real-time data, and the secondary system 2 will be used for more than just backup purposes. The return on investment is greater.
- the secondary system 2 When the secondary system 2 is used as a reference system, it is not preferable to compress the data because the processing takes a long time. Also, according to the data backup / recovery method according to the present embodiment, there are the following advantages.
- FIG. 8 is a block diagram showing another configuration of the primary system and the secondary system for realizing the data backup 'recovery method according to the second embodiment of the present invention.
- the data backup and recovery method according to the second embodiment shown in FIG. 8 also includes a primary system 1a and a secondary system 2a. More specifically, in the primary system 1a, a primary storage device 120 with a built-in random access memory is provided separately from a primary processing device 110 that performs application processing. In addition, the sending system 2 a is provided with a secondary storage device 220 having a built-in random access memory in addition to a secondary processing device 210 that executes various processes.
- the primary processing unit 110 is a communication unit for communicating backup data, a database control mechanism for changing contents of a database in the primary storage device, and the database control mechanism is And a primary backup recovery control mechanism for transmitting the data of the changed content via the communication means when the content of the data is changed.
- the communication means in the second embodiment has the same or the same function as the communication control device 13 in the first embodiment.
- the database control mechanism in the second embodiment has the same or the same function as the database control mechanism 15 in the first embodiment.
- the primary backup recovery control mechanism according to the second embodiment has the same or the same function as the primary backup recovery control mechanism 14 according to the first embodiment.
- the database area in the primary storage device 120 of the second embodiment is performed by the location table 5 and the blocks 6,.
- the secondary processing device 210 communicates with the backup data, and a backup database in the secondary storage device using the data transmitted from the primary backup recovery control mechanism via the communication device. And a secondary backup recovery control mechanism that changes the
- the communication means in the second embodiment has the same or the same function as the communication control device 23 in the first embodiment.
- the secondary backup recovery control mechanism according to the second embodiment has the same or the same function as the secondary backup recovery control mechanism 24 according to the first embodiment.
- a backup operation is performed by the location table 7 and the blocks 8,..., As in the first embodiment.
- the backup recovery operation by the synchronous close coupling method or the asynchronous loose coupling method in the first embodiment can be realized.
- the addition and modification of the storage device can be easily performed.
- the data backup / recovery method according to the modified example of the second embodiment can be represented by the same configuration diagram as FIG. 9, but the contents processed by each block are different from those of the second embodiment.
- the data backup / recovery method according to the modified example of the second embodiment also includes a primary system and a seconder, as in the second embodiment.
- the primary system separately provides a primary storage device having a built-in random access memory for a primary processing device that performs application processing.
- the second embodiment is different from the second embodiment in that the sending system is provided with a secondary storage device having a built-in random access memory for a secondary processing device that executes various processes. It is the same in form and outer shape.
- a modified example of the second embodiment is that a communication means is provided in the primary storage device 1b, and a communication means is provided in the secondary storage device, and the backup data is transferred between the two by both communication means. It is the same as the second embodiment in that communication is performed.
- the modification of the second embodiment is different from the second embodiment in that a primary storage device changes the content of a database in the primary storage device, A primary backup recovery control mechanism for transmitting data of the changed content via the communication means when the mechanism changes the content of the database; and A secondary recovery control mechanism for changing a backup database in the secondary storage device with the data transmitted from the control mechanism via the communication means is provided.
- a backup operation is performed by a location table and one or more blocks, as in the first embodiment. I have.
- a backup operation is performed by a location table and one or more blocks as in the first embodiment. .
- the backup recovery operation by the synchronous tightly-coupled method or the asynchronous loosely-coupled method in the first embodiment can be realized.
- FIG. 9 is a pack diagram showing another configuration of the primary system and the secondary system for realizing the data backup / recovery method according to the third embodiment of the present invention.
- the data backup / recovery system of the third embodiment shown in FIG. 9 also includes a primary system 1b and a secondary system 2b. More specifically, in the primary system 1b, a primary storage device 12Ob having a built-in random access memory is provided separately from a primary processing device 110b that performs application processing.
- the sending system 2b includes only a secondary storage device 220b with a built-in random access memory.
- a communication unit is provided in the primary storage device 120b, and a communication unit is provided in the secondary storage device 220b, and a communication device is provided between the primary storage device 120b and the secondary storage device 220b.
- the backup data can be communicated between them.
- the primary storage device 120b includes a database control mechanism for changing the content of the database in the primary storage device 120b, and a content of the changed content when the database control mechanism changes the content of the database.
- the communication means in the third embodiment has the same or the same function as the communication control device 13 in the first embodiment.
- the database control mechanism in the third embodiment has the same or the same function as the database control mechanism 15 in the first embodiment.
- the primary backup recovery control mechanism according to the third embodiment has the same or the same function as the primary backup recovery control mechanism 14 according to the first embodiment.
- the secondary storage device 220b is configured to change a backup data base in the secondary storage device 220b with the data transmitted from the primary backup recovery control mechanism via the communication unit. It has a back-up recovery control mechanism.
- the secondary backup recovery control mechanism in the third embodiment has the same or the same function as the secondary backup recovery control mechanism 24 in the first embodiment.
- a backup operation is performed by the location table 5 and the blocks 6,..., As in the first embodiment. .
- the backup operation is performed by the location table 7 and the blocks 8,... As in the first embodiment. Have been done.
- the pack-up recovery operation by the synchronous tightly-coupled method or the asynchronous loosely-coupled method in the first embodiment can be realized.
- the third embodiment in addition to the advantages of the first embodiment, it is possible to easily add or change storage devices, and to provide a communication unit in each processing device. Pack-up is possible without having a pack-up mechanism.
- the exclusion is released based on the backup end information from the secondary system, but this is performed in the same manner as in the asynchronous loosely coupled system.
- the secondary system After receiving the backup suspension information, the secondary system starts the reference batch processing. When the reference system patch processing is completed, the secondary system performs the backup update manually or automatically based on the log for which the backup update processing has been suspended. In the secondary system, when the backup update processing pending log disappears, the backup suspension release information is transmitted from the secondary system to the primary system, and the system returns to the normal backup mode. In the case of this method, the primary system and the secondary system are temporarily out of sync. Therefore, when importance is placed on safety, it is preferable to prepare a plurality of secondary systems.
- the primary backup recovery control mechanism transmits data of the changed content when the database control mechanism changes the content of the database.
- the data of the changed content may not be transmitted at the same time, and the data of the changed content may be transmitted at another timing.
- both the primary system 1 and the secondary system 2 are installed in Japan.
- the primary system 1 is installed in Japan and the secondary system 2 is installed in a foreign country for backup, or the primary system 1 is installed in a foreign country and the secondary system 2 is installed in Japan. It may be configured to be installed in Japan for backup, and these are all included in the scope of the present invention.
- the data backup and recovery method according to the present invention has the following advantages.
- Non-stop operation can be realized by switching to the secondary power system when the primary system fails.
- the equipment for backup does not need to be the same type of equipment as the primary system.
Description
Claims
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/980,619 US6934877B2 (en) | 2000-04-12 | 2001-04-11 | Data backup/recovery system |
EP01921812A EP1209569A1 (en) | 2000-04-12 | 2001-04-11 | Data backup/recovery system |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2000111299 | 2000-04-12 | ||
JP2000-111299 | 2000-04-12 | ||
JP2001094678A JP2001356945A (ja) | 2000-04-12 | 2001-03-29 | データバックアップ・リカバリー方式 |
JP2001-094678 | 2001-03-29 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2001077835A1 true WO2001077835A1 (fr) | 2001-10-18 |
Family
ID=26589985
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2001/003126 WO2001077835A1 (fr) | 2000-04-12 | 2001-04-11 | Systeme de sauvegarde/recuperation de donnees |
Country Status (3)
Country | Link |
---|---|
US (1) | US6934877B2 (ja) |
JP (1) | JP2001356945A (ja) |
WO (1) | WO2001077835A1 (ja) |
Families Citing this family (131)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP4689137B2 (ja) * | 2001-08-08 | 2011-05-25 | 株式会社日立製作所 | リモートコピー制御方法、及びストレージシステム |
US20060195667A1 (en) * | 2001-05-10 | 2006-08-31 | Hitachi, Ltd. | Remote copy for a storage controller with consistent write order |
CN1241120C (zh) * | 2001-08-31 | 2006-02-08 | 联想(北京)有限公司 | 计算机硬盘数据备份及恢复方法 |
JP2004005500A (ja) * | 2002-03-28 | 2004-01-08 | Matsushita Electric Ind Co Ltd | 情報処理装置及び情報処理プログラム |
US7778958B2 (en) * | 2002-04-11 | 2010-08-17 | Quantum Corporation | Recovery of data on a primary data volume |
JP2004005222A (ja) | 2002-05-31 | 2004-01-08 | Internatl Business Mach Corp <Ibm> | 格納形式が異なる記録装置のためのバックアップ技術 |
JP2004013271A (ja) * | 2002-06-04 | 2004-01-15 | Aiful Corp | バックアップサービサーシステム、バックアップサービシング方法、これらに用いて好適なバックアップサービサー装置、オリジネーター装置 |
US7086034B2 (en) * | 2002-06-28 | 2006-08-01 | Canon Kabushiki Kaisha | Method, program, and storage medium for acquiring logs |
US7844577B2 (en) | 2002-07-15 | 2010-11-30 | Symantec Corporation | System and method for maintaining a backup storage system for a computer system |
EP1387269A1 (en) * | 2002-08-02 | 2004-02-04 | Hewlett Packard Company, a Delaware Corporation | Backup system and method of generating a checkpoint for a database |
AU2003262065A1 (en) * | 2002-09-10 | 2004-04-30 | Annex Systems Incorporated | Database re-organizing system and database |
JP4393762B2 (ja) * | 2002-12-19 | 2010-01-06 | 株式会社日立製作所 | データベース処理方法及び装置並びにその処理プログラム |
JP4290975B2 (ja) | 2002-12-19 | 2009-07-08 | 株式会社日立製作所 | データベース処理方法及び装置並びにその処理プログラム及びディザスタリカバリ方法及びシステム |
JP2004259079A (ja) | 2003-02-27 | 2004-09-16 | Hitachi Ltd | データ処理システム |
JP4301849B2 (ja) * | 2003-03-31 | 2009-07-22 | 株式会社日立製作所 | 情報処理方法及びその実施システム並びにその処理プログラム並びにディザスタリカバリ方法およびシステム並びにその処理を実施する記憶装置およびその制御処理方法 |
US9678967B2 (en) | 2003-05-22 | 2017-06-13 | Callahan Cellular L.L.C. | Information source agent systems and methods for distributed data storage and management using content signatures |
US7178055B2 (en) * | 2003-06-06 | 2007-02-13 | Hewlett-Packard Development Company, L.P. | Method and system for ensuring data consistency after a failover event in a redundant data storage system |
US7120825B2 (en) * | 2003-06-06 | 2006-10-10 | Hewlett-Packard Development Company, L.P. | Adaptive batch sizing for asynchronous data redundancy |
US7152182B2 (en) * | 2003-06-06 | 2006-12-19 | Hewlett-Packard Development Company, L.P. | Data redundancy system and method |
US7165187B2 (en) * | 2003-06-06 | 2007-01-16 | Hewlett-Packard Development Company, L.P. | Batch based distributed data redundancy |
US20040254962A1 (en) * | 2003-06-12 | 2004-12-16 | Shoji Kodama | Data replication for enterprise applications |
US7130975B2 (en) * | 2003-06-27 | 2006-10-31 | Hitachi, Ltd. | Data processing system |
JP4124348B2 (ja) | 2003-06-27 | 2008-07-23 | 株式会社日立製作所 | 記憶システム |
JP2005309550A (ja) | 2004-04-19 | 2005-11-04 | Hitachi Ltd | リモートコピー方法及びリモートコピーシステム |
JP4374953B2 (ja) | 2003-09-09 | 2009-12-02 | 株式会社日立製作所 | データ処理システム |
JP2005031716A (ja) | 2003-07-07 | 2005-02-03 | Hitachi Ltd | データバックアップの方法及び装置 |
US8214588B2 (en) * | 2003-11-05 | 2012-07-03 | International Business Machines Corporation | Parallel asynchronous order-preserving transaction processing |
JP2005062928A (ja) * | 2003-08-11 | 2005-03-10 | Hitachi Ltd | 複数のサイトにリモートコピーを行うシステム |
US7219201B2 (en) * | 2003-09-17 | 2007-05-15 | Hitachi, Ltd. | Remote storage disk control device and method for controlling the same |
JP2005108098A (ja) | 2003-10-01 | 2005-04-21 | Hitachi Ltd | データi/o装置及びデータi/o装置の制御方法 |
US7818530B2 (en) * | 2003-11-26 | 2010-10-19 | Hewlett-Packard Development Company, L.P. | Data management systems, articles of manufacture, and data storage methods |
US7657533B2 (en) * | 2003-11-26 | 2010-02-02 | Hewlett-Packard Development Company, L.P. | Data management systems, data management system storage devices, articles of manufacture, and data management methods |
JP4412989B2 (ja) | 2003-12-15 | 2010-02-10 | 株式会社日立製作所 | 複数の記憶システムを有するデータ処理システム |
US20050149554A1 (en) * | 2003-12-29 | 2005-07-07 | Chong Fay Jr. | One-way data mirror using write logging |
US7200603B1 (en) * | 2004-01-08 | 2007-04-03 | Network Appliance, Inc. | In a data storage server, for each subsets which does not contain compressed data after the compression, a predetermined value is stored in the corresponding entry of the corresponding compression group to indicate that corresponding data is compressed |
JP4477370B2 (ja) * | 2004-01-30 | 2010-06-09 | 株式会社日立製作所 | データ処理システム |
JP4551096B2 (ja) * | 2004-02-03 | 2010-09-22 | 株式会社日立製作所 | ストレージサブシステム |
JP2005242403A (ja) * | 2004-02-24 | 2005-09-08 | Hitachi Ltd | 計算機システム |
WO2005086003A1 (ja) * | 2004-03-08 | 2005-09-15 | Annex Systems Incorporated | データベース・システム |
US7277997B2 (en) | 2004-03-16 | 2007-10-02 | International Business Machines Corporation | Data consistency for mirroring updatable source data storage |
JP4452533B2 (ja) | 2004-03-19 | 2010-04-21 | 株式会社日立製作所 | システムおよび記憶装置システム |
US7197520B1 (en) * | 2004-04-14 | 2007-03-27 | Veritas Operating Corporation | Two-tier backup mechanism |
US20050235017A1 (en) * | 2004-04-15 | 2005-10-20 | Jeff Ashman | System and method for high availability of data in a disaster recovery system |
JPWO2005103901A1 (ja) * | 2004-04-19 | 2008-03-13 | アネックスシステムズ株式会社 | コンピューター・システム |
JP4455927B2 (ja) * | 2004-04-22 | 2010-04-21 | 株式会社日立製作所 | バックアップ処理方法及び実施装置並びに処理プログラム |
JP4624829B2 (ja) * | 2004-05-28 | 2011-02-02 | 富士通株式会社 | データバックアップシステム及び方法 |
US20060004879A1 (en) * | 2004-05-28 | 2006-01-05 | Fujitsu Limited | Data backup system and method |
US8112584B1 (en) * | 2004-06-28 | 2012-02-07 | Cisco Technology, Inc | Storage controller performing a set of multiple operations on cached data with a no-miss guarantee until all of the operations are complete |
JP4477950B2 (ja) * | 2004-07-07 | 2010-06-09 | 株式会社日立製作所 | リモートコピーシステム及び記憶装置システム |
JP4484618B2 (ja) * | 2004-07-30 | 2010-06-16 | 株式会社日立製作所 | ディザスタリカバリシステム、プログラム及びデータの複製方法 |
JP4519563B2 (ja) * | 2004-08-04 | 2010-08-04 | 株式会社日立製作所 | 記憶システム及びデータ処理システム |
CA2580239C (en) * | 2004-09-21 | 2016-04-26 | Timeplay Entertainment Corporation | System, method and handheld controller for multi-player gaming |
JP2006127028A (ja) * | 2004-10-27 | 2006-05-18 | Hitachi Ltd | 記憶システム及び記憶制御装置 |
US20060174051A1 (en) * | 2005-02-02 | 2006-08-03 | Honeywell International Inc. | Method and apparatus for a redundancy approach in a processor based controller design |
WO2006085357A1 (ja) * | 2005-02-08 | 2006-08-17 | Fujitsu Limited | ディスクアレイ装置の記憶制御装置および冗長性復旧方法 |
US7475281B2 (en) * | 2005-03-10 | 2009-01-06 | International Business Machines Corporation | Method for synchronizing replicas of a database |
JP4699091B2 (ja) * | 2005-05-31 | 2011-06-08 | 株式会社日立製作所 | ディザスタリカバリ方法およびシステム |
US7617149B2 (en) | 2005-05-31 | 2009-11-10 | Rosenthal Collins Group, Llc | Method and system for electronically inputting, monitoring and trading spreads |
US7613747B1 (en) * | 2005-06-08 | 2009-11-03 | Sprint Communications Company L.P. | Tiered database storage and replication |
US7933987B2 (en) * | 2005-09-30 | 2011-04-26 | Lockheed Martin Corporation | Application of virtual servers to high availability and disaster recovery solutions |
US7934116B2 (en) * | 2005-09-30 | 2011-04-26 | Lockheed Martin Corporation | Disaster recover/continuity of business adaptive solution framework |
US7577868B2 (en) * | 2005-09-30 | 2009-08-18 | Lockheed Martin Corporation | No data loss IT disaster recovery over extended distances |
WO2007075587A2 (en) * | 2005-12-19 | 2007-07-05 | Commvault Systems, Inc. | Systems and methods for performing data replication |
TWI332612B (en) * | 2006-02-21 | 2010-11-01 | Asia Optical Co Inc | Memory access method |
US8131860B1 (en) * | 2006-03-30 | 2012-03-06 | Emc Corporation | Serialization and deserialization |
JP4921013B2 (ja) * | 2006-03-30 | 2012-04-18 | 日本電気株式会社 | メールサーバのバックアップシステム、メールサーバのバックアップ方法、プログラム及び記録媒体 |
JP4940730B2 (ja) * | 2006-03-31 | 2012-05-30 | 富士通株式会社 | データベースシステム運用方法,データベースシステム,データベース装置及びバックアッププログラム |
US9015520B2 (en) | 2006-06-29 | 2015-04-21 | Dssdr, Llc | Data transfer and recovery |
US7487383B2 (en) | 2006-06-29 | 2009-02-03 | Dssdr, Llc | Data transfer and recovery process |
US8990613B2 (en) | 2006-06-29 | 2015-03-24 | Dssdr, Llc | Data transfer and recovery |
US7865471B1 (en) * | 2006-06-30 | 2011-01-04 | Symantec Operating Corporation | Apparatus and method for accelerating database recovery |
US20080059846A1 (en) * | 2006-08-31 | 2008-03-06 | Rosenthal Collins Group, L.L.C. | Fault tolerant electronic trading system and method |
US7840537B2 (en) | 2006-12-22 | 2010-11-23 | Commvault Systems, Inc. | System and method for storing redundant information |
JP5029685B2 (ja) * | 2007-02-28 | 2012-09-19 | 富士通株式会社 | バックアップ装置 |
JP5049618B2 (ja) * | 2007-03-15 | 2012-10-17 | 株式会社日立製作所 | ディザスタリカバリシステムおよび方法 |
WO2008120277A1 (ja) * | 2007-03-29 | 2008-10-09 | Fujitsu Limited | サーバ・クライアントシステム、及びサーバ・クライアントシステムにおける警報データ送受信方法 |
JP5156310B2 (ja) * | 2007-09-19 | 2013-03-06 | 株式会社日立製作所 | バックアップ構成の構築を支援する方法及び計算機 |
JP4958722B2 (ja) * | 2007-10-19 | 2012-06-20 | 株式会社日立製作所 | 記憶システム及びデータ転送方法 |
US7933902B2 (en) * | 2008-02-05 | 2011-04-26 | International Business Machines Corporation | Data repair method and system |
US7962782B2 (en) * | 2008-05-20 | 2011-06-14 | International Business Machines Corporation | Modifying connection records |
DE102008035601A1 (de) * | 2008-07-31 | 2010-02-04 | Walter, Thomas, Dr.-Ing. | System zum Verwalten von Dateien |
US8762347B1 (en) | 2008-09-22 | 2014-06-24 | Symantec Corporation | Method and apparatus for processing transactional file system operations to enable point in time consistent file data recreation |
US20100198872A1 (en) * | 2009-01-25 | 2010-08-05 | Thomas Norwin Walter | System for the Management of Files |
US8401996B2 (en) | 2009-03-30 | 2013-03-19 | Commvault Systems, Inc. | Storing a variable number of instances of data objects |
US8578120B2 (en) | 2009-05-22 | 2013-11-05 | Commvault Systems, Inc. | Block-level single instancing |
US20110238781A1 (en) * | 2010-03-25 | 2011-09-29 | Okun Justin A | Automated transfer of bulk data including workload management operating statistics |
US11449394B2 (en) | 2010-06-04 | 2022-09-20 | Commvault Systems, Inc. | Failover systems and methods for performing backup operations, including heterogeneous indexing and load balancing of backup and indexing resources |
US8504526B2 (en) * | 2010-06-04 | 2013-08-06 | Commvault Systems, Inc. | Failover systems and methods for performing backup operations |
US8935492B2 (en) | 2010-09-30 | 2015-01-13 | Commvault Systems, Inc. | Archiving data objects using secondary copies |
US8516270B2 (en) * | 2010-11-18 | 2013-08-20 | Apple Inc. | Incremental and bulk storage system |
US9298707B1 (en) * | 2011-09-30 | 2016-03-29 | Veritas Us Ip Holdings Llc | Efficient data storage and retrieval for backup systems |
US9020890B2 (en) | 2012-03-30 | 2015-04-28 | Commvault Systems, Inc. | Smart archiving and data previewing for mobile devices |
US9256472B2 (en) * | 2012-07-10 | 2016-02-09 | Sears Brands, Llc | System and method for economical migration of legacy applications from mainframe and distributed platforms |
CN102902593B (zh) * | 2012-09-28 | 2016-05-25 | 方正国际软件有限公司 | 基于缓存机制的协议分发处理系统 |
US9633022B2 (en) * | 2012-12-28 | 2017-04-25 | Commvault Systems, Inc. | Backup and restoration for a deduplicated file system |
US9317423B2 (en) * | 2013-01-07 | 2016-04-19 | Hitachi, Ltd. | Storage system which realizes asynchronous remote copy using cache memory composed of flash memory, and control method thereof |
US11733908B2 (en) | 2013-01-10 | 2023-08-22 | Pure Storage, Inc. | Delaying deletion of a dataset |
US10908835B1 (en) * | 2013-01-10 | 2021-02-02 | Pure Storage, Inc. | Reversing deletion of a virtual machine |
CN104426926B (zh) * | 2013-08-21 | 2019-03-29 | 腾讯科技(深圳)有限公司 | 定时发布数据的处理方法及装置 |
US10324897B2 (en) | 2014-01-27 | 2019-06-18 | Commvault Systems, Inc. | Techniques for serving archived electronic mail |
US20170132095A1 (en) * | 2014-03-28 | 2017-05-11 | Hewlett Packard Enterprise Development Lp | Data restoration |
US9811427B2 (en) | 2014-04-02 | 2017-11-07 | Commvault Systems, Inc. | Information management by a media agent in the absence of communications with a storage manager |
US9934008B2 (en) * | 2014-06-18 | 2018-04-03 | Netapp, Inc. | Methods for facilitating persistent storage of in-memory databases and devices thereof |
US9753955B2 (en) | 2014-09-16 | 2017-09-05 | Commvault Systems, Inc. | Fast deduplication data verification |
US9632713B2 (en) | 2014-12-03 | 2017-04-25 | Commvault Systems, Inc. | Secondary storage editor |
CN104536846A (zh) * | 2014-12-17 | 2015-04-22 | 杭州华为数字技术有限公司 | 一种备份数据的方法及装置 |
CN104598168B (zh) * | 2015-01-23 | 2017-09-29 | 华为技术有限公司 | 一种数据恢复方法及对象存储设备 |
US9639274B2 (en) | 2015-04-14 | 2017-05-02 | Commvault Systems, Inc. | Efficient deduplication database validation |
US10324914B2 (en) | 2015-05-20 | 2019-06-18 | Commvalut Systems, Inc. | Handling user queries against production and archive storage systems, such as for enterprise customers having large and/or numerous files |
US10474548B2 (en) | 2016-09-30 | 2019-11-12 | Commvault Systems, Inc. | Heartbeat monitoring of virtual machines for initiating failover operations in a data storage management system, using ping monitoring of target virtual machines |
CN108243209A (zh) * | 2016-12-23 | 2018-07-03 | 深圳市优朋普乐传媒发展有限公司 | 一种数据同步方法及装置 |
CN106874133B (zh) * | 2017-01-17 | 2020-06-23 | 北京百度网讯科技有限公司 | 流式计算系统中计算节点的故障处理 |
US10956079B2 (en) | 2018-04-13 | 2021-03-23 | Hewlett Packard Enterprise Development Lp | Data resynchronization |
US10673943B2 (en) | 2018-05-02 | 2020-06-02 | Commvault Systems, Inc. | Network storage backup using distributed media agents |
US11321183B2 (en) | 2018-05-02 | 2022-05-03 | Commvault Systems, Inc. | Multi-tiered backup indexing |
US11249863B2 (en) * | 2018-05-02 | 2022-02-15 | Commvault Systems, Inc. | Backup-based media agent configuration |
US11126505B1 (en) * | 2018-08-10 | 2021-09-21 | Amazon Technologies, Inc. | Past-state backup generator and interface for database systems |
US11200124B2 (en) | 2018-12-06 | 2021-12-14 | Commvault Systems, Inc. | Assigning backup resources based on failover of partnered data storage servers in a data storage management system |
JP7164175B2 (ja) * | 2018-12-10 | 2022-11-01 | Necソリューションイノベータ株式会社 | 分散ファイル装置、フェイルオーバ方法、プログラム及び記録媒体 |
US11500664B2 (en) | 2019-04-30 | 2022-11-15 | Rubrik, Inc. | Systems and method for continuous data protection and recovery by implementing a set of algorithms based on the length of I/O data streams |
US11663092B2 (en) | 2019-04-30 | 2023-05-30 | Rubrik, Inc. | Systems and methods for continuous data protection |
US11663089B2 (en) * | 2019-04-30 | 2023-05-30 | Rubrik, Inc. | Systems and methods for continuous data protection |
US11106545B2 (en) | 2019-04-30 | 2021-08-31 | Rubrik, Inc. | Systems and methods for continuous data protection |
US11609775B2 (en) | 2019-04-30 | 2023-03-21 | Rubrik, Inc. | Systems and methods for continuous data protection comprising storage of completed I/O requests intercepted from an I/O stream using touch points |
US11341106B2 (en) | 2019-07-19 | 2022-05-24 | Commvault Systems, Inc. | Deduplication system without reference counting |
US11263173B2 (en) | 2019-07-30 | 2022-03-01 | Commvault Systems, Inc. | Transaction log index generation in an enterprise backup system |
US10657018B1 (en) | 2019-08-26 | 2020-05-19 | Coupang Corp. | Systems and methods for dynamic aggregation of data and minimization of data loss |
TWI719609B (zh) * | 2019-08-28 | 2021-02-21 | 威進國際資訊股份有限公司 | 異地備援系統 |
US11099956B1 (en) | 2020-03-26 | 2021-08-24 | Commvault Systems, Inc. | Snapshot-based disaster recovery orchestration of virtual machine failover and failback operations |
CN111813598A (zh) * | 2020-06-08 | 2020-10-23 | 广东东水工程项目管理有限公司 | 一种工程管理信息备份系统 |
US11645175B2 (en) | 2021-02-12 | 2023-05-09 | Commvault Systems, Inc. | Automatic failover of a storage manager |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPS60103461A (ja) * | 1983-11-10 | 1985-06-07 | Fujitsu Ltd | 複数項目による代替キ−管理処理方式 |
US5544347A (en) * | 1990-09-24 | 1996-08-06 | Emc Corporation | Data storage system controlled remote data mirroring with respectively maintained data indices |
JP3345628B2 (ja) * | 1997-07-11 | 2002-11-18 | アネックスシステムズ株式会社 | データ格納及び検索方法 |
JP2000181768A (ja) * | 1998-12-15 | 2000-06-30 | Anetsukusu Syst Kk | デ―タ格納検索方式 |
-
2001
- 2001-03-29 JP JP2001094678A patent/JP2001356945A/ja active Pending
- 2001-04-11 US US09/980,619 patent/US6934877B2/en not_active Expired - Fee Related
- 2001-04-11 WO PCT/JP2001/003126 patent/WO2001077835A1/ja not_active Application Discontinuation
Non-Patent Citations (3)
Title |
---|
J. GRAY ET AL., TRANSLATION: EICHI WATANABE: "OLTP system", 25 July 1991, MCGRAW-HILL, XP002944124 * |
MAMORU MAEKAWA ET AL.: "Bunsan operating system: UNIX no tsugi ni kurumono", 25 December 1991, KYOURITSU SHUPPAN, XP002944126 * |
MASAHIRO NAKAMURA: "Fukusei file no hidouki koushin ga bunsan database no chuushin gijutsu ni; 2 sou commit no daikou shudan to shite fujou", NIKKEI ELECTRONICS, no. 609, 6 June 1994 (1994-06-06), pages 101 - 110, XP002944125 * |
Also Published As
Publication number | Publication date |
---|---|
US6934877B2 (en) | 2005-08-23 |
US20030074600A1 (en) | 2003-04-17 |
JP2001356945A (ja) | 2001-12-26 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2001077835A1 (fr) | Systeme de sauvegarde/recuperation de donnees | |
JP4624829B2 (ja) | データバックアップシステム及び方法 | |
US6983295B1 (en) | System and method for database recovery using a mirrored snapshot of an online database | |
JP2894676B2 (ja) | 非同期式遠隔コピー・システム及び非同期式遠隔コピー方法 | |
US7103619B1 (en) | System and method for automatic audit data archiving within a remote database backup system | |
US7925633B2 (en) | Disaster recovery system suitable for database system | |
CA2376242C (en) | Improved remote data copy using a prospective suspend command | |
US6957221B1 (en) | Method for capturing a physically consistent mirrored snapshot of an online database from a remote database backup system | |
US7565572B2 (en) | Method for rolling back from snapshot with log | |
EP1569120A1 (en) | Computer system for recovering data based on priority of the data | |
US20060253731A1 (en) | Data Backup System and Method | |
CN107038091B (zh) | 一种基于异步远程镜像的数据安全性保护系统与电力应用系统数据保护方法 | |
EP1209569A1 (en) | Data backup/recovery system | |
US20060184502A1 (en) | Method for file level remote copy of a storage device | |
CN115481417A (zh) | 基于链的数据快照、归档、完整恢复上链方案的方法 | |
US6424999B1 (en) | System and method for restoring previously backed-up data in a mass storage subsystem | |
CN106874141A (zh) | 一种数据存储负载的容错方法及iptv系统 | |
US6968347B2 (en) | Data recovery method and apparatus | |
JP5154843B2 (ja) | クラスタシステム、計算機、および障害回復方法 | |
JPH1115604A (ja) | データ多重化方法 | |
JPH03256146A (ja) | 並列動作型データベース管理方式 | |
CN110196788B (zh) | 一种数据读取方法、装置、系统及存储介质 | |
US20210240351A1 (en) | Remote copy system and remote copy management method | |
JPH08278909A (ja) | 高信頼化システムおよび方法 | |
WO2006049202A1 (ja) | データ多重化システム |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): US |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2001921812 Country of ref document: EP |
|
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: 09980619 Country of ref document: US |
|
WWP | Wipo information: published in national office |
Ref document number: 2001921812 Country of ref document: EP |
|
WWW | Wipo information: withdrawn in national office |
Ref document number: 2001921812 Country of ref document: EP |