WO2006049202A1 - データ多重化システム - Google Patents
データ多重化システム Download PDFInfo
- Publication number
- WO2006049202A1 WO2006049202A1 PCT/JP2005/020197 JP2005020197W WO2006049202A1 WO 2006049202 A1 WO2006049202 A1 WO 2006049202A1 JP 2005020197 W JP2005020197 W JP 2005020197W WO 2006049202 A1 WO2006049202 A1 WO 2006049202A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- dbms
- data
- operation information
- application
- backup
- 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/1479—Generic software techniques for error detection or fault masking
- G06F11/1482—Generic software techniques for error detection or fault masking by means of middleware or OS functionality
-
- 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/16—Error detection or correction of the data by redundancy in hardware
- G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
- G06F11/202—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant
- G06F11/2038—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant with a single idle spare processing component
-
- 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/16—Error detection or correction of the data by redundancy in hardware
- G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
- G06F11/2097—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements maintaining the standby controller/processing unit updated
-
- 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/16—Error detection or correction of the data by redundancy in hardware
- G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
- G06F11/2053—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant
- G06F11/2094—Redundant storage or storage space
Definitions
- the present invention relates to a data multiplexing system, a data multiplexing method, and a data multiplexing program for multiplexing (duplicating) data in preparation for loss of data stored in a database storage.
- Patent Document 1 An example of a conventional data multiplexing system of this type is described in Patent Document 1.
- the data multiplexing system described in Patent Document 1 includes an application program (hereinafter referred to as application) 1100 that provides a service, and a database management system (hereinafter referred to as DBMS) that manages data necessary for processing of the application 1100. ) It is composed of 1200, primary disk array device 1300, backup disk array device 1400, and communication line 1500 connecting them!
- application application program
- DBMS database management system
- the primary disk array device 1300 includes a cache 1301 for temporarily recording data input / output, a transmission unit 1302 for copying cached data and transferring it to the backup disk array device 1400, and the data actually A recording unit 1303 for storing data and a control unit 1304 for controlling them are provided.
- the knock-up disk array device 1400 includes a cache 1401 that temporarily records data input / output, a receiving unit 1402 that receives data transferred from the primary disk array device 1300, and copies the data to the cache 1401. It has a recording unit 1403 that actually stores it, and a control unit 1404 that controls them.
- a conventional data multiplexing system having such a configuration operates as follows. That is, when data is written to the primary disk array device 1300 via the application 1100 power BMS1200, the data is first written to the cache 1301 and then stored in the storage unit 1303. The transmission unit 1302 copies the data in the cache 1301 and transfers it to the backup disk array device 1400 via the communication line 1500. The data transferred to the knock-up disk array device 1400 is received by the receiving unit 1402 and copied to the cache 1401. Data copied to the cache 1401 is stored in the storage unit 1403. In this way, the same data is stored in the primary disk array device 1300 and the backup disk array device 1400.
- Such a data multiplexing system is generally called a mirroring system.
- the data multiplexing system described in Patent Document 2 and Patent Document 3 includes a primary system 2100, a backup system 2200, and a communication line 2300 connecting them.
- the primary system 2100 includes an application 2110 that provides a service, a primary DBMS 2120 that manages data necessary for processing the application, and a storage unit 2130 that actually stores the data.
- the backup system 2200 includes a backup DBMS 2220 that manages data, and a storage unit 2230 that actually stores data.
- the knock-up DBMS 2220 includes a reception unit 2222 that receives operation logs transferred from the primary system 2100, and these. And a control unit 2223 for controlling.
- the data multiplexing system having such a configuration operates as follows. That is, when the application 2110 performs operations such as writing data to the storage unit 2130 via the primary DBMS 2120 in the primary system 2100, the operation information is stored in the operation log 2121.
- the transmission unit 2122 transfers the operation information stored in the operation log 2121 to the backup system 2200 via the communication line 2300.
- the operation information transferred to the backup system 2200 is received by the receiving unit 2222.
- the backup DBMS 2220 performs operations such as writing data in the storage unit 2230 according to the received operation information.
- Such a data multiplexing system is generally called a replication system.
- Patent Document 1 Japanese Patent Application Laid-Open No. 2003-167684
- Patent Document 2 JP 2002-108681
- Patent Document 3 Japanese Unexamined Patent Publication No. 2000-47919
- a first problem is that the performance of the entire system is greatly reduced.
- replication is a function provided by a DBMS.
- a DBMS has a high processing load, and it is the component that is most likely to become a bottleneck in the system. Therefore, if processing is performed to achieve the replication function, This is because the processing performance of the DBMS is greatly reduced.
- the processing load is not imposed on the DBMS, but because the amount of data to be transferred is enormous, the transfer process takes time.
- the second problem is that the DBMSs that can be replicated are limited.
- the reason is that the replication function is a function unique to each DBMS, so it is incompatible with the replication function, and DBMS cannot perform replication! /.
- replication systems operation port format, transfer protocol, etc. are different even between DBMSs that support replication, so replication cannot be performed between different types of DBMS!
- a first data multiplexing system of the present invention includes a DBMS that manages storage data, middleware that has a standard interface and has a function of converting access from an application to access to the DBMS.
- the computer system also includes an acquisition means for acquiring data operation information for the DBMS issued to the middleware, and multiplexes the data operation information for the DBMS. It is characterized by.
- a second data multiplexing system is different from the DBMS in the first data multiplexing system based on operation information of data to the DBMS acquired by the acquiring unit. It is characterized by operating storage data managed by other DBMS in the same way as storage data managed by the DBMS.
- the third data multiplexing system of the present invention is the first data multiplexing system, wherein the operation information used for multiplexing is identified from the operation information of the data to the DBMS acquired by the acquiring means. Based on the operation information identified by the identification means, the storage data managed by another DBMS different from the DBMS is treated in the same way as the storage data managed by the DBMS. It is a thing to operate.
- a fourth data multiplexing system is the first data multiplexing system, wherein the data operation information for the DBMS acquired by the acquisition means is transferred to another DBMS different from the DBMS.
- Change means for changing the data to be suitable for the operation information of the data, and storage data managed by the other DBMS based on the operation information changed by the change means is changed to storage data managed by the DBMS. It is characterized by being operated in the same way.
- a fifth data multiplexing system includes a verification unit that compares response information about the same operation by the DBMS and the other DBMS in the second to fourth data multiplexing systems. And a notification means for notifying the verification result of the verification means.
- the sixth data multiplexing system of the present invention is the second to fifth data multiplexing systems, wherein the application power is a storage operation by the DBMS based on the operation information issued to the middleware. Is characterized by confirming the completion of the operation on the storage by the other DBMS based on the operation information, and also performing power.
- a seventh data multiplexing system of the present invention is the first data multiplexing system, wherein the operation information of the data to the DBMS acquired by the acquiring means is recorded in a storage different from the storage Means are provided.
- An eighth data multiplexing system of the present invention is a computer system in which a primary system and a backup system are connected via a communication line.
- a middleware having an interface and a function of converting an access from an application to an access to the DBMS; an acquisition means for acquiring operation information of data to the DBMS issued from the application to the middleware; An identification unit for identifying the operation information to be transmitted to the backup system among the operation information of the data acquired by the acquisition unit to the DBMS, and the operation information identified by the identification unit are transmitted to the backup system.
- a backup device and other storage data are transmitted to the backup system.
- Other DBMS that manages data, receiving means for receiving the operation information transmitted by the transmitting means, and changing the operation information received by the receiving means to be suitable for the operation information of the data to the other DBMS And changing means for reproducing the operation information changed by the changing means and issuing it to the other DBMS.
- the ninth data multiplexing system of the present invention is a computer system in which a primary system and a backup system are connected via a communication line.
- the primary system includes a DBMS for managing storage data, a standard specification A middleware having an interface and a function of converting an access from an application to an access to the DBMS; an acquisition means for acquiring operation information of data to the DBMS issued from the application to the middleware; The identification means for identifying the operation information to be transmitted to the backup system among the operation information of the data acquired by the acquisition means to the DBMS, and the operation information identified by the identification means to the backup system DBMS.
- a transmission means for transmitting the operation information changed by the change means to the backup system, and the knock-up system manages other storage data. It comprises a DBMS, receiving means for receiving operation information transmitted by the transmitting means, and reproducing means for reproducing the operation information received by the receiving means and issuing it to the other DBMS.
- a tenth data multiplexing system of the present invention is a DBMS for managing storage data in a primary system in a computer system in which a primary system and a backup system are connected via a communication line.
- Middleware having a standard interface and a function of converting access from the application to access to the DBMS;
- An acquisition unit that acquires operation information of data to the DBMS issued from the application to the middleware, and an operation to be transmitted to the backup system among the operation information of data to the DBMS acquired by the acquisition unit
- An identification means for identifying information
- a change means for changing the operation information identified by the identification means to be suitable for the data operation information to the DBMS on the backup system side, and reproducing the operation information changed by the change means.
- reproducing means for issuing to another DBMS that manages the storage of the backup system through the middleware.
- the eleventh data multiplexing system of the present invention compares the data operation response information in the primary system with the data operation response information in the backup system in the eighth to tenth data multiplexing systems. It is characterized by comprising verification means and notification means for notifying the verification result of the verification means.
- the twelfth multiplexing system of the present invention is a computer system in which a primary system and a backup system are connected via a communication line, and a DBMS that manages storage data in the primary system and a standard specification.
- Middleware having a function of converting access from an application to access to the DBMS, and obtaining means for obtaining operation information of data to the DBMS issued from the application to the middleware, Identification means for identifying operation information to be transmitted to the backup system among the operation information of data to the DBMS acquired by the acquisition means;
- a transmission means for transmitting the operation information identified by the identification means to the backup system, and receiving in the knock-up system the operation information transmitted by the transmission means; and the operation received by the reception means
- one primary system and a plurality of backup systems are also configured, and a plurality of backup system powers are combined with one primary system. It is characterized by storing each copy of system data.
- a fourteenth data multiplexing system includes, in the eighth to twelfth data multiplexing systems, a plurality of primary systems and one backup system, and one knock-up system includes a plurality of It is characterized by collecting and storing data copies of the primary system.
- a fifteenth data multiplexing system includes, in the eighth to twelfth data multiplexing systems, a plurality of primary systems and a plurality of backup systems, each having a plurality of backup system capabilities. It is characterized in that a plurality of data copies of any of the primary systems are aggregated and stored.
- the sixteenth data multiplexing system of the present invention is the eighth to twelfth data multiplexing system, which is composed of one primary system and a plurality of backup systems, and has a copy of the primary system. It is characterized in that the backup data is stored in a chained manner so that the backup data of the backup system is stored in another backup system.
- a seventeenth data multiplexing system of the present invention is characterized in that, in the eighth to twelfth data multiplexing systems, a plurality of system powers are configured to mutually store data copied from other systems. To do.
- An eighteenth data multiplexing system is characterized in that, in the eighth to twelfth data multiplexing systems, a plurality of system forces are configured to store copies of the same data. .
- a first data multiplexing method of the present invention includes a DBMS that manages storage data.
- Middleware having a standard interface and a function of converting access from an application to access to the DBMS is provided in the computer system, and the application power is data to the DBMS issued to the middleware.
- the operation information is acquired by an acquisition means, and the operation information of the data to the DBMS is multiplexed.
- a second data multiplexing method of the present invention is the first data multiplexing method according to the first data multiplexing method, wherein the other data different from the DBMS is obtained based on the operation information of the data to the DBMS acquired by the acquiring means.
- the storage data managed by the DBMS is operated in the same manner as the storage data managed by the DBMS.
- the third data multiplexing method of the present invention is the first data multiplexing method, wherein the operation information used for multiplexing is identified among the operation information of the data to the DBMS acquired by the acquiring means.
- the storage data managed by another DBMS different from the DBMS is operated in the same way as the storage data managed by the DBMS based on the operation information identified by the identifying means. It is characterized by doing.
- a fourth data multiplexing method of the present invention is the first data multiplexing method, wherein the operation information of the data to the DBMS acquired by the acquiring means is transferred to another DBMS different from the DBMS.
- the storage unit managed by the other DBMS is the same as the storage data managed by the DBMS based on the operation information changed by the changing unit. It is characterized by operating as follows.
- a fifth data multiplexing method of the present invention is the second to fourth data multiplexing methods, in which response information about the same operation by the DBMS and the other DBMS is compared by a verification means. The verification result of the verification unit is notified by the notification unit.
- a sixth data multiplexing method of the present invention is the second to fifth data multiplexing methods, in which the application operation on the storage by the DBMS based on the operation information issued to the middleware is: It is characterized by checking the completion of the operation for the storage by the other DBMS based on the operation information.
- a seventh data multiplexing method of the present invention is different from the storage in the first data multiplexing method in that operation information of data to the DBMS acquired by the acquiring means is different from the storage. Recording is performed on the storage by a recording unit.
- a first primary computer system of the present invention is connected to a knock-up system via a communication line, and a DBMS that manages storage data in the primary computer system and a standard specification Middleware having a function of converting access from the application to access to the DBMS, and acquisition means for acquiring operation information of data to the DBMS issued to the middleware Identification means for identifying operation information to be transmitted to the backup system among the operation information of the data acquired by the acquisition means to the DBMS, and transmitting the operation information identified by the identification means to the backup system. And transmitting means for transmitting.
- the second primary computer system of the present invention is connected to the knock-up system via a communication line, and the primary computer system manages the storage data and the standard specification.
- Middleware having a function of converting access from the application to access to the DBMS, and acquisition means for acquiring operation information of data to the DBMS issued to the middleware
- Identification means for identifying the operation information to be transmitted to the backup system among the operation information of the data to the DBMS acquired by the acquisition means, and the operation information identified by the identification means as the DBMS on the backup system side
- Change means for changing the data to be suitable for the operation information of the data, and the operation information changed by the change means backed up.
- a transmission means for transmitting to the backup system.
- the third primary computer system of the present invention is connected to the knock-up system via a communication line.
- the primary computer system manages the storage data in the primary computer system and the standard specification.
- Middleware having a function of converting access from the application to access to the DBMS, and acquisition means for acquiring operation information of data to the DBMS issued to the middleware
- Identification means for identifying the operation information to be transmitted to the backup system among the operation information of the data to the DBMS acquired by the acquisition means, and the operation information identified by the identification means as the DBMS on the backup system side Suitable for data manipulation information
- And changing means for changing, and reproducing means for reproducing the operation information changed by the changing means and issuing the operation information to another DBMS managing the storage of the backup system through the middleware.
- the first to third primary computer systems compare the response information of the data operation in the own system with the response information of the data operation in the backup system. It is characterized by comprising verification means and notification means for notifying the verification result of the verification means.
- the first knock-up computer system of the present invention is connected to the primary system via a communication line, and has a standard interface in the knock-up computer system and is accessible from an application.
- Application to middleware that has a function to convert access to DBMS.
- the second knock-up computer system of the present invention is connected to the primary system via a communication line, and has a standard interface and access from an application in the knock-up computer system.
- Application to middleware that has a function to convert access to DBMS Operation data issued to the DBMS Operation that has been changed to be suitable for data operation information to the DBMS on the backup system side
- a third knock-up computer system of the present invention includes a storage and a backup system-side DBMS in a backup computer system connected to a primary system via a communication line, and the backup system side DBMS.
- the DBMS on the system side develops the application power into middleware that has a standard interface on the primary system side and has a function of converting access from the application to access to the DBMS.
- the received operation information of the data to the DBMS that has been changed to be suitable for the data operation information to the DBMS on the backup system side, reproduced by the reproduction means, and issued through the middleware is received, It is characterized by managing storage data.
- the fourth knock-up computer system of the present invention is connected to the primary system via a communication line, and has a standard interface in the knock-up computer system and is accessible from an application.
- Application to middleware that has a function to convert access to DBMS.Receiving means for receiving data operation information for the DBMS from the primary system and storage of operation information received by the receiving means. And recording means for recording in the recording medium.
- application power is issued to middleware that has a standard interface and has a function of converting access from an application to access to a DBMS. It is acquired by the acquisition means and used for multiplexing.
- the operation information is applied to another DBMS different from the DBMS, and the database data managed by the other DBSM is managed by the backup source DBSM. Operates in the same way as database data.
- the first effect is that data can be multiplexed without degrading the performance of the system.
- the reason for this is that the operation information of data from the application to the DBMS issued to the middleware is multiplexed, and since this operation information is abstracted and the amount of data is small, it does not require a broadband communication line in a short time. This is because it can be done and does not place a processing load on the DBMS.
- the second effect is that data can be multiplexed without limiting the DBMS.
- the reason is that there is a middleware with a standard interface between the application and the DBMS, without limiting the application or DBMS, and the operation information issued from the application to the DBMS is independent of the application and DBMS. It is because it becomes the same.
- FIG. 1 is a block diagram showing a configuration of a conventional data multiplexing system.
- FIG. 2 is a block diagram showing another configuration of a conventional data multiplexing system.
- FIG. 3 is a block diagram showing a configuration of the first exemplary embodiment of the present invention.
- FIG. 4 is a flowchart showing the operation of the first exemplary embodiment of the present invention.
- FIG. 5 is an explanatory diagram of an acquisition unit according to the first embodiment of the present invention.
- FIG. 6 is a block diagram showing a 1-to-N configuration, which is a modification of the first embodiment of the present invention.
- FIG. 7 is a block diagram showing an N-to-1 configuration that is a modification of the first embodiment of the present invention.
- FIG. 8 is a block diagram showing an N-to-M configuration that is a modification of the first embodiment of the present invention.
- FIG. 9 is a block diagram showing a chain configuration that is a modification of the first embodiment of the present invention.
- FIG. 10 is a block diagram showing a mutual configuration which is a modification of the first embodiment of the present invention.
- FIG. 11 is a block diagram showing a parallel configuration which is a modified example of the first embodiment of the present invention.
- FIG. 12 is a block diagram showing a configuration of the second exemplary embodiment of the present invention.
- FIG. 13 is a flowchart showing the operation of the second exemplary embodiment of the present invention.
- FIG. 14 is a block diagram showing a configuration of a third exemplary embodiment of the present invention.
- FIG. 15 is a block diagram showing another configuration example of the third embodiment of the present invention.
- FIG. 16 is a flowchart showing the operation of the third exemplary embodiment of the present invention.
- FIG. 17 is a block diagram showing a configuration of a fourth exemplary embodiment of the present invention.
- FIG. 18 is a flowchart showing the operation of the fourth exemplary embodiment of the present invention.
- the first embodiment of the present invention includes a primary system 3100, a knock It consists of an up system 3200 and a communication line 3300 connecting them!
- the primary system 3100 includes an application server 3101 that provides a service, and a database server 3121 that provides data to the application server 3101.
- the database server 3121 includes a storage 3123 for storing data, and a DBMS 3122 for managing data in the storage 3123.
- the application server 3101 includes an application 3102 that provides a service, and middleware 3103.
- the middleware 3103 is a program that provides a common function to a plurality of application programs including the application 3102 running on the application server 3101.
- the middleware 3103 converts the access from the application 3102 into the access to the DBMS 3122 of the database server 3121, and conversely converts the response from the DBMS 3122 into the response to the application 3102. Is provided.
- a standard standard interface such as JDBCOava (registered trademark) Database Connectivity) is used for example.
- an interface unique to the DBMS 3122 is used as an interface with the DBMS 3122 in the DB access means 3104.
- the application server 3101 further includes an acquisition unit 3105 for acquiring operation information issued from the application 3102 to the DB access unit 3104 of the middleware 3103 for access to the database server 3121, and the acquisition unit 3105
- the identification means 3106 for identifying the operation information to be transmitted to the knock-up system 3200 among the operation information acquired by the identification information storage unit 3107 for storing the information necessary for this identification, and the identification information storage section 3107 for identifying the information to be transmitted.
- Transmission means 3108 for transmitting the operation information to the backup system 3200 and a transmission information storage unit 3109 for storing information necessary for transmission such as a transmission destination address.
- the backup system 3200 includes an application server 3201 that is a backup of the application server 3101, and a database server 3221 that is a backup of the database server 3121.
- the database server 3221 includes a storage 3223 for storing data, and a DBMS 3222 for managing data in the storage 3223.
- Storage 3223 and DBMS3222 The storage 3123 and DBMS 3122 of the database server 3121 may be exactly the same, or the storage 3123 and DBMS 3122 may be of different manufacturers and different specifications.
- the application server 3201 receives the operation information transmitted from the application server 3101, and the operation information received by the reception unit 3208 is originally transmitted to the DBMS 3122 of the database server 3121. Based on the change information storage unit 3207 for storing the change information necessary to make this the operation information for the DBMS 3222 of the database server 3221 and the change information stored in the change information storage unit 3207! / The changing means 3206 for changing the operation information received by the receiving means 3206, the middleware 3203 having the application 3202 and the DB access means 3204 similar to the application 3102, and the changing means 3206 are changed as necessary. A reproduction means 3205 for receiving the received operation information and issuing it to the DB access means 3204.
- the communication line 3300 is an arbitrary communication line such as a bus, serial, parallel, LAN, wireless LAN, Internet, public line, etc., or may be a multiplexed communication line combining a plurality.
- the application 3102 of the application server 3101 connects to the DBMS 3122 of the database server 3121 via the DB access means 3104 of the middleware 3103 as necessary. Issue operation information to perform reference update of data necessary for processing (step 401).
- the DBMS 3122 Based on the operation information issued from the application 3102, the DBMS 3122 performs operations such as referring to and updating stored data for the storage 3123, and returns response information as a result (step 402).
- the application 3102 receives the response information from the DBMS 3122 via the DB access means 3104 (step 403).
- step 401 Upon execution of step 401, the acquisition means 3105 is issued by the application 3102 to the DBMS 3122. Acquired operation information is acquired (step 404).
- the application 3102 and the DBM S3122 try to connect to the DB access means 3104 only as usual. Therefore, the acquisition unit 3105 acquires operation information by transparently trapping connections from the application 3102 and the DBMS 3122 to the DB access unit 3104. A specific example will be described with reference to FIG.
- the acquisition unit 3105 When the acquisition unit 3105 is not provided, the application 3102, the DB access unit 3104, and the DBMS 3122 are connected to each other with an interface relationship as shown in FIG. Fig. 5 (2) is an implementation example of the so-called wrapper acquisition means 3105.
- the acquisition means 3105 is connected to the application 3102 through the same interface as the AP-DB access means interface of the DB access means 3104.
- the DB access means 3104 is connected with the same interface as the AP-DB access means interface that the application 3102 has. For this reason, the acquisition means 3105 looks like the DB access means 3104 from the application 3102 and looks like the application 3102 from the DB access means 3104, so the connection from the application 3102 to the DB access means 3104 is transparently trapped. can do.
- FIG. 5 (3) shows an example of transparently trapping the connection to the DB access means 3104 from the application 3102 and DBMS 3122 by providing the DB access means 3104 with the function of the acquisition means 3105.
- the function of the acquisition unit 3105 is implemented in a JDBC driver or the like that constitutes the middleware 3103.
- the acquisition of operation information by the acquisition unit 3105 may be performed for all applications connected to the DBMS 3122 via the DB access unit 3104, or may be performed only for a specific application.
- the operation from the application 3102 to the DBMS3122 is [connection authentication (user's connection destination)] ⁇ [operation (target / operation)] b ⁇ Only the operation information with the application power authenticated by the connection destination (DBMS) is acquired, or only the operation information from the application that performs the operation for the specific target (schema) in the operation is acquired.
- the data is not the same in the storages 3123 and 3223 as a whole, and the data is the same regarding the data in the storage related to the application for multiplexing the operation information.
- the identification unit 3106 based on the identification information stored in the identification information storage unit 3107, among the operation information acquired by the acquisition unit 3105, the operation information transmitted to the knock-up system 3200. Is identified (step 405). For example, in order to further reduce the amount of data to be transmitted, the identification unit 3106 may transmit only the update operation and discard the reference operation without transmitting it. This is because if the operation information issued from the application 3102 includes an SQL statement (character string), if it is an update operation, it includes a character string (SQL command) that means an update such as “UPDATE” or “INSERT”. These commands are stored in the identification information storage unit 3107 as identification information, and the identification means 3106 analyzes the operation information, and only backups the operation information in which the command character string registered in the identification information appears. This can be done by identifying the operation information to be transmitted to.
- the transmission means 3108 communicates the operation information identified by the identification means 3106 to be transmitted based on the transmission information (for example, the IP address of the backup system 3200) stored in the transmission information storage unit 3109.
- the data is transmitted to the backup system 3200 via the circuit 3300 (step 406).
- reception means 3208 of application server 3201 receives the operation information transmitted from primary system 3100 (step 407).
- the changing unit 3206 analyzes the operation information received by the receiving unit 3208, and changes a necessary part based on the change information stored in the change information storage unit 3207 (step 408).
- the following cases (1) to (4) can be considered as examples of changes.
- the operation information issued by the application 3102 that accesses the DBMS 3122 includes the IP address.
- the backup system accesses DBMS3222, it is necessary to convert the address. Therefore, assuming that the IP address of DBMS3222 is 192.168.0.2, the correspondence between 192.168.0.1 and 192.168.0.2 is stored in the change information storage unit 3207, and the change unit 3206 includes the operation information acquired by the reception unit 3208. Change the included IP address 192.168.0.1 to 192.168.0.2.
- operation information issued by the application 3102 that accesses DBMS3122 must be changed to the operation information of the DBMS3222 version.
- operation information expressed as ⁇ DECODE (key, vall, resl, val 2, res2, res3) '' in DBMS3122, ⁇ CASE WHEN key vall TH EN resl WHEN '' in DBMS3222
- the operation information issued by the application 3102 that accesses the database server 3121 is accessed at the appropriate location on the database server 3221. It is necessary to change the operation information. For example, if the table name tablel and record name recodel on the database server 3121 side correspond to the table name table2 and record name recode2 on the database server 3221, the corresponding relationship is stored in the change information storage unit 3207.
- the reproducing unit 3205 reproduces the operation information changed by the changing unit 3206 as necessary, and issues it to the DBMS 3222 of the database server 3221 via the DB access unit 3204 (step 409).
- the interface relationship between the reproduction unit 3205, the application 3202, and the DB access unit 3204 is the same as the interface relationship between the acquisition unit 3105, the application 3102, and the DB access unit 3104 described with reference to FIG. Therefore, from the DB access means 3204, the operation information issued from the reproduction means 3205 appears to be operation information issued from the application 3202.
- the DBMS 3322 performs an operation such as updating the stored data on the storage 3223 based on the operation information regenerated and issued by the regenerating means 3205, and returns the response information as a result ( Step 410).
- the playback unit 3205 receives the response information from the DBMS 3222 via the DB access unit 3204 and discards it (step 411).
- the data power of the storage 3223 of the backup system 3200 is operated in the same manner as the data of the storage 3123 of the primary system 3100, so that the same data is stored in both storages 3 123 and 3223.
- the application 3102 of the primary system 3100 is the backup system 32.
- the service can be continued by controlling the route of operation information and response information to refer to the data in storage 3223 of 00.
- the application 3202 can be started and the service can be continued only by the backup system 3200.
- the communication line 3300 does not require a wide band.
- the primer When operating the storage data of the database server 3121 with the operation information issued from the application 3102 running on the application server 3101 of the re-system 3100, the operation information is transferred to the backup system 3200 and the storage data on the backup system 3200 side.
- data multiplexing is achieved, and the amount of data transferred from the primary system 3100 to the backup system 3200 is the same as the replication method explained in Figure 2, This is because it is less than the amount of data transferred by mirroring described in Fig. 1.
- Data multiplexing can be performed without imposing a load on DBMS processing. This is because the DBMS is not deeply involved in the data multiplexing process as in the replication method described in Fig. 2.
- Data can be multiplexed between different DBMSs that do not create ad hoc functions for each application or DBMS, even between DBMSs that do not support the replication function.
- the reason is that the middleware 3103 DB access means 3104 with a standard interface that does not limit the application or DBMS is provided between the application and the DBMS, and the application information operation information issued to the DBMS Application This is because it is the same regardless of the DBMS.
- steps 402 to 403 are performed independently of steps 404 to 411.
- steps 402 to 403 are performed after waiting for step 411. That is, after the completion of the data operation to the storage 3 223 is confirmed in the backup system 3200, the data operation to the storage 3123 is performed in the primary system 3100. V, you can do so-called synchronous multiplexing! /.
- Figure 6 shows an overview of this modification.
- the present modification example is composed of one primary system 510 and a plurality of backup systems 520-1, 520-2,... 520-n.
- Multiple backup systems 520-1, 520-2, ... 520-n storage 521-1, 521-2, 521-n all store the same data as storage 511 on primary system 510 Do
- the transmission means 412 of the primary system 510 (corresponding to the transmission means 3108 in Fig. 3) force Operation information is sent to each of the backup systems 520-1, 520-2, ..., 520-n. This can be realized by sending.
- the destination address of each backup system 520-1, 520-2,..., 520-n is stored in a portion corresponding to the transmission information storage unit 3109 in FIG.
- Figure 7 shows an overview of this modification.
- the present modification example is composed of a plurality of primary systems 610-1, 610-2,..., 610-n, and one backup system 620.
- ⁇ 611-n data is aggregated and replicated in storage 621 of backup system 620
- This modification is based on the change means 622 of the backup system 620 (corresponding to the change means 3206 in Fig. 3).
- the operation transmitted from the multiple primary systems 610-1, 610-2, ..., 610-n This can be achieved by changing the information to apply to different areas of storage 611, different schemas at the DBMS layer.
- Such changes are stored in the change information shown in Figure 3.
- the change as described in the embodiment of FIG. 3 corresponding to the information (for example, IP address) for identifying each primary system 610-1, 610-2,.
- the information can be stored, and the change means 622 can change the operation information based on the change information corresponding to the primary system that is the transmission source of the operation information.
- the changing means 622 is changing the operation information.
- the primary systems 610-1, 610-2, ... 6 10-n may be provided with changing means so that the operation information is changed in advance and then transmitted to the knock-up system 620.
- FIG. 8 shows an overview of this modification.
- this modification example includes a plurality of primary systems 710-1, 710-2, 710-n and a plurality of backup systems 720-1, 720-2,. -Consists of m.
- This modification is different from the primary system 710-1, 710-2, ..., 710-n transmission means 712-1, 712-2, ... 712-n (transmission means 3108 in Fig. 3
- the operation information is sent to any one of the multiple backup systems 720-1, 720-2, 720-m, and the knockup systems 720-1, 720-2, 720-m changing means 722-1, 722-2, ... 722-m (corresponding to changing means 3206 in Fig. 3) It can be realized by changing the storage 721-1, 721-2, ..., 721-m to different schemas in the DBMS layer.
- the transmission information storage unit (corresponding to the transmission information storage unit 3109 in Fig. 3) has a plurality of operation information to be transmitted.
- the destination address, etc. of the backup system is stored, and the transmission means 712-1, 712-2, ..., 712-n refer to that for transmission.
- 3 corresponds to the information (eg, IP address) for identifying each primary system 610-1, 610-2,..., 610-n in the portion corresponding to the change information storage unit 3207 in FIG.
- the change information as described in the embodiment is stored, and the change means 722-1, 722-2,..., 722-m are change information corresponding to the primary system that is the source of the operation information. Based on!, Change the operation information.
- This variation increases the fault tolerance because there are multiple backup systems as in the 1-to-N configuration.
- the number of backup systems is reduced because data is aggregated and replicated as in the N-to-1 configuration. By reducing the number, system construction costs can be reduced.
- the present modification example includes one primary system 810 and at least two or more backup systems 820-1, 820-2, cascading to the primary system 810.
- the backup systems 820-1, 820-2,..., 820-n are receiving means 823-1, 823-2,...
- the receiving means 3208 in FIG. ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇
- This modification is highly fault-tolerant due to the presence of multiple backup systems as in a one-to-one configuration, and each system always transmits and receives only to one knock-up system. , You can avoid concentrating the load on one system.
- Figure 10 shows an overview of this modification. Referring to FIG. 10, this variation is configured with system ⁇ 910 and system ⁇ 920.
- system A910 is the primary system and system ⁇ 920 is the backup system.
- system 920 is the primary system and the system A910 is the backup system. That is, in the system A 910, the application A 911 operates using the data A 914 stored in the storage 913.
- the operation information issued by the application A911 is transmitted to the system B920, and the system B920 stores data A925, which is a copy of the data A914, in the storage 923 according to the received operation information.
- the application B921 operates using the data B924 stored in the storage 923.
- the operation information issued by the application B921 is transmitted to the system A910, and the system A910 stores data B915, which is a copy of the data B924, in the storage 913 according to the received operation information.
- This modification can be realized by operating with each other as a backup system as described above.
- the system can be used without waste by operating the application even in the knock-up system and providing the service.
- this system is composed of two system powers, but more than that is acceptable.
- Figure 11 shows an overview of this modification.
- the present modification example includes a system A 1010 and a system B 1020.
- the two systems are equivalent and are both primary and backup systems.
- the application 1011 operates using the data 1014 stored in the storage 1013.
- the operation information issued by the application 1011 is transmitted to the system B 1020, and the system B 1020 stores data 1024 which is a copy of the data 1014 in the storage 1023 according to the received operation information.
- the application 1021 operates using the data 1024 stored in the storage 1023.
- the operation information issued by the application 1021 is transmitted to the system A1010, and the system A1010 stores the data 1014 that is a copy of the data 1024 in the storage 1013 according to the received operation information.
- system A1010 and system B1020 include synchronization means 1012, 1022 that do not allow the other party to update data while updating the data.
- This modification can be realized by operating the two systems in parallel so as to synchronize data as described above. [0121] In this modification, by operating an application even in a knock-up system and providing a service, the system can be utilized without waste, and the processing load of the application can be distributed.
- the present embodiment includes a primary system 11100, a knock-up system 11200, and a communication line 3300 similar to that of the first embodiment.
- the primary system 11100 includes an application server 11101 that provides a service, and a database server 3121 including a DBMS 3122 and a storage 3123 similar to those in the first embodiment.
- the application server 11101 is similar to the application server 3101 in the first embodiment.
- the application 3102, middleware 3103 having DB access means 3104, acquisition means 3105, identification means 3106, and identification information storage
- a change unit 3206, a change information storage unit 3207, and a playback unit 3205 which are the same as those of the application server 3201 in the first embodiment.
- the backup system 11200 includes a database server 3221 including a DBMS 3222 and a storage 3223 similar to those in the first embodiment.
- the operations of the application 3102, DBMS 3122, acquisition unit 3105, and identification unit 3106 in the present embodiment indicated by steps 1201 to 1205 in FIG. 13 are the first implementation indicated by steps 401 to 405 in FIG.
- the operations of the application 3102, DBMS 3122, acquisition unit 3105, and identification unit 3106 are the same as those in the configuration of FIG.
- the changing means 3206 changes the operation information identified by the identifying means 3106 based on the change information 3207, if necessary (step 1206), and transmits it to the reproducing means 3205.
- the reproduction means 3205 reproduces the operation information changed by the changing means 3206 as necessary, as if it were the operation information issued by the application 3102, and through the DB access means 3104, Issued to DBMS3222 of database server 3221 of backup system 11200 (step 1207). Since the connection information of the reproduced operation information is changed to DBMS3222 by the changing means 3206, it is connected to DBMS3222 which is not DBMS3122 even through the same DB access means 3104.
- the DBMS 3322 performs an operation such as updating the stored data on the storage 3223 based on the operation information that the reproduction means 3205 reproduces and issues, and returns the response information as a result ( Step 1208).
- the playback unit 3205 receives the response information from the DBMS 3222 via the DB access unit 3104 and discards it (step 1209).
- the same data is stored in the storage 3123 of the primary system 11100 and the storage 3223 of the backup system 11200.
- the application server is not required for the knock-up system, so that the cost of system construction can be reduced.
- steps 1202-1203 are performed independently of steps 1204-1209. That is, because of so-called asynchronous multiplexing, there may be a state in which data operation to the storage 3223 is not performed in the backup system 11200 even if data operation to the storage 3123 is performed in the primary system 11100. As a result, data and data operation information immediately before the failure may be lost. Therefore, perform steps 1202 to 1203 after waiting for step 1209, that is, confirm that the data operation to the storage 3223 is completed in the backup system 11200, and then perform the data operation to the storage 3123 in the primary system 11100. V, you can do so-called synchronous multiplexing! / ⁇
- the present embodiment is different from the first embodiment in that a backup system 13200 is provided instead of the backup system 3200, and the other configurations are the same.
- Knock-up system 13200 includes storage storage 13201 for storing operation information.
- the storage server 13201 includes receiving means 13202 for receiving the operation information transmitted from the application server 3101 of the primary system 3100, recording means 13203 for recording the received operation information, and a storage 13204 for storing the operation information. Is provided.
- the receiving means 13202 of the storage sano 13201 receives the operation information transmitted from the primary system 3100 (step 1407).
- the recording unit 13203 stores the operation information acquired by the receiving unit 13202 in the storage 13204.
- the record management means 13213 is the storage 1320.
- the transmission / reception unit 13212 transmits the operation information read by the recording management unit 13213 to the primary system 13100 based on the communication address of the primary system 13100 stored in the transmission information storage unit 13211.
- transmission / reception means 131 of application server 13101 In primary system 13100, transmission / reception means 131 of application server 13101
- the acquisition / reproduction means 13105 reproduces the operation information received by the transmission / reception means 13018 as if it were operation information issued by the application 3102, and via the DB access means 3104. Issued to DBMS3122 of database server 3121.
- the DBMS 3122 performs an operation such as updating the stored data on the storage 3123 based on the operation information issued by the acquisition “reproduction means 13105”, and returns response information as a result of the operation.
- the acquisition 'reproducing unit 13105 receives the response information from the DBMS 3122, and the DB access unit 3
- steps 1401 to 1403 are performed independently of steps 1404 to 1408. That is, because of so-called asynchronous multiplexing, even if data operation to the storage 3123 is performed in the primary system 13100, the operation information may be stored in the storage 13204 in the backup system 13200. for that reason The operation information immediately before the occurrence of the failure may be lost. Therefore, steps 1402 to 1403 are performed after waiting for step 1408, that is, the backup system 13200 confirms the completion of the recording of the operation information to the storage 13204, and then the primary system 3100, 13100 stores the storage 3123. You may perform what is called synchronous multiplexing which performs data operation.
- the existing data multiplexing technology such as mirroring, which does not record all the operation information, is used in combination to periodically back up the storage 3123, and then to the storage 3123. It is also possible to record only the operation information that has been transferred as a difference.
- the knock-up system does not require a component such as a DBMS, so the cost of system construction can be reduced.
- the fourth embodiment of the present invention includes a primary system 15100, a backup system 15200, and a communication line 3300 similar to the first embodiment.
- the primary system 15100 includes an application server 15101 that provides a service, and a database server 3121 including a DBMS 3122 and a storage 3123 similar to those in the first embodiment.
- the application server 15101 acquires both operation information issued from the application 3102 and response information from the DBMS 3122
- the identification unit 15106 for identifying the operation information and the response information to be transmitted to the backup system 15200 among the operation information and the response information acquired by the acquisition unit 3105
- an identification information storage unit 15107 for storing information necessary for identifying response information in addition to the identification of operation information and a function for both transmission and reception instead of the transmission means 3108 Transmission / reception means 15108, a verification means 15110 for comparing and verifying response information, and a notification means 1511 for notifying the verification result
- the configuration differs from the application server 3100 of the first embodiment. Other configurations are the same.
- the backup system 15200 includes an application sano 15201 that is a backup of the application sano 15101, and a database server 3121 including a DBMS 3222 and a storage 3223 similar to those of the first embodiment.
- the application server 15201 plays back the operation information changed by the change means 3206 and the playback / acquisition means 152 05 for acquiring response information from the DBMS 3222 and the reception means 3208.
- Transmission / reception means 15208 having both transmission and reception functions, transmission information storage section 15209 for storing information necessary for transmission such as the communication address of the primary system 15100, and reproduction / acquisition means 15205
- the application according to the first embodiment is provided with an identification unit 15210 for identifying response information to be transmitted to the primary system 15100 and an identification information storage unit 15211 for storing information necessary for the identification.
- the configuration is different from the Chillon server 3201, and the other configurations are the same.
- the operation of DBMS 3222 is the application 3102, DBMS 3122, acquisition means 3105, identification means 3106, transmission means 3108, reception means 3208, modification means 3206 in the first embodiment shown in steps 401 to 410 of FIG. Since the operation is the same as that of the playback means 3205 and DBMS3222, description thereof will be omitted.
- the reproduction 'acquisition unit 15205 acquires the response information from the DBMS 3222 via the DB access unit 3204 (step 1611).
- the identification unit 15210 sends a response to the primary system 151 00 for verification out of the response information acquired by the reproduction 'acquisition unit 15205. Identify the information (step 1612). For example, in order to reduce the amount of data to be transmitted, an operation response may be encoded and transmitted, or response information may be transmitted every certain number of times. The following is an example of encoding the operation response and sending it.
- a correspondence table indicating which object is true or false is stored in the identification information storage unit 15211 as identification information.
- a simple numeric value (primitive value) smaller than the object may be returned as a response, but such a response is transmitted as it is.
- the transmission / reception means 15208 sends the response information identified by the identification means 15210 to be transmitted via the communication circuit 3300 based on the communication address of the primary system 15100 stored in the transmission information storage unit 15209. To the primary system 15100 (step 1613).
- transmission / reception means 15108 receives the response information transmitted from backup system 15200 (step 1614) and transmits the response information to verification means 15110.
- acquisition means 15105 acquires this response information (step 1615) and transmits it to identification means 15106. Based on the identification information stored in the identification information storage unit 1510 7, the identification unit 15106 verifies the response information acquired by the acquisition unit 15105. Response information necessary for the authentication is identified (step 1616) and transmitted to the verification means 15110.
- the identification method is the same as in Step 1612.
- verification means 15110 compares and verifies the response information of primary system 15100 identified by identification means 15106 and the response information of backup system 15200 received by transmission / reception means 15108 (step 1617).
- the notification unit 15111 performs notification (step 161).
- the notification destination may be a system administrator or a means for performing some control using the notification result, for example, a means for canceling and retrying the corresponding data operation.
- Step 1603 is performed independently of Steps 1610 to 1618. For this reason, even if an abnormality is detected, the processing of the application 3102 proceeds regardless. Therefore, step 1603 may be performed after waiting for steps 1610 to 1618, that is, after confirming that the data multiplexing process has been completed normally, response information may be returned to the application 3102.
- the response information is transmitted from the knock-up system 15200 to the primary system 15100 for verification.
- the verification information is backed up by providing the backup system with a verification means. It may be sent to the system 15200 and verified by the backup system 15200.
- verification may be performed on different systems on the communication line 300 or on a plurality of these systems.
- comparison and verification of DBMS response information can detect normality / abnormality of data operations, thus ensuring more certainty.
- Data can be multiplexed.
- each component realizing the data multiplexing function in each embodiment of the present invention can be realized by a computer and a program as well as by realizing the function in the form of software.
- the program is provided by being recorded on a computer-readable recording medium such as a magnetic disk or a semiconductor memory, read by the computer at the time of starting up the computer, etc., and controlling the operation of the computer. It functions as a component in the embodiment.
- the present invention can be applied to the use of constructing a highly reliable system in a system that provides services using a DBMS.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
Description
Claims
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2006542419A JP4844743B2 (ja) | 2004-11-08 | 2005-11-02 | データ多重化システム |
US11/667,181 US20070266061A1 (en) | 2004-11-08 | 2005-11-02 | Data Multiplexing System |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2004323688 | 2004-11-08 | ||
JP2004-323688 | 2004-11-08 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2006049202A1 true WO2006049202A1 (ja) | 2006-05-11 |
Family
ID=36319207
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2005/020197 WO2006049202A1 (ja) | 2004-11-08 | 2005-11-02 | データ多重化システム |
Country Status (3)
Country | Link |
---|---|
US (1) | US20070266061A1 (ja) |
JP (1) | JP4844743B2 (ja) |
WO (1) | WO2006049202A1 (ja) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2008009814A (ja) * | 2006-06-30 | 2008-01-17 | Nec Corp | データレプリケーションシステム及びデータレプリケーション方法 |
JP2009181308A (ja) * | 2008-01-30 | 2009-08-13 | Hamamatsu Photonics Kk | ストレージシステム |
US10022245B2 (en) | 2012-12-17 | 2018-07-17 | DePuy Synthes Products, Inc. | Polyaxial articulating instrument |
JP2019114240A (ja) * | 2017-12-22 | 2019-07-11 | ウェアヴァリー カンパニー リミテッドWarevalley Co., Ltd. | Sqlパケット分析を通じての異機種データベースのデータ複製および同期化エラー探知方法およびシステム |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8095684B2 (en) * | 2009-09-15 | 2012-01-10 | Symantec Corporation | Intelligent device and media server selection for optimized backup image duplication |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2000132435A (ja) * | 1998-10-29 | 2000-05-12 | Hitachi Ltd | 異種データベース管理システム間のデータ整合処理装置 |
JP2001265803A (ja) * | 2000-03-22 | 2001-09-28 | Mitsubishi Electric Corp | データベースアクセス高速化システム及びデータベースアクセス高速化方法 |
JP2001350777A (ja) * | 2000-06-05 | 2001-12-21 | Mitsubishi Electric Corp | 分散データベースシステム |
Family Cites Families (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5987452A (en) * | 1997-01-22 | 1999-11-16 | At&T Corp | Query translation system |
JP2000112801A (ja) * | 1998-09-30 | 2000-04-21 | Toshiba Corp | データベースバックアップシステム及びバックアップ方法 |
JP4282030B2 (ja) * | 1999-06-03 | 2009-06-17 | 株式会社日立製作所 | データ二重化制御方法および二重化した記憶サブシステム |
US6901380B1 (en) * | 1999-09-10 | 2005-05-31 | Dataforce, Inc. | Merchandising system method, and program product utilizing an intermittent network connection |
JP3686564B2 (ja) * | 1999-12-21 | 2005-08-24 | 株式会社日立製作所 | データベースシステム、データベースのレプリカ生成方法およびデータベースのレプリカ生成プログラムを記録したコンピュータ読み取り可能な記録媒体 |
US6611834B1 (en) * | 2000-01-12 | 2003-08-26 | International Business Machines Corporation | Customization of information retrieval through user-supplied code |
US6963875B2 (en) * | 2000-03-23 | 2005-11-08 | General Atomics | Persistent archives |
US6505200B1 (en) * | 2000-07-06 | 2003-01-07 | International Business Machines Corporation | Application-independent data synchronization technique |
US20040162836A1 (en) * | 2001-02-06 | 2004-08-19 | Eyal Aronoff | System and method for altering database requests and database responses |
WO2003036521A1 (en) * | 2001-10-24 | 2003-05-01 | Bea Systems, Inc. | Data synchronization |
JP2003316522A (ja) * | 2002-04-26 | 2003-11-07 | Hitachi Ltd | 計算機システムおよび計算機システムの制御方法 |
JP4283576B2 (ja) * | 2003-03-27 | 2009-06-24 | 株式会社日立製作所 | トランザクション同期方法、データベースシステム及びデータベース装置 |
GB0323780D0 (en) * | 2003-10-10 | 2003-11-12 | Ibm | A data brokering method and system |
US7487188B2 (en) * | 2004-09-07 | 2009-02-03 | Computer Associates Think, Inc. | System and method for providing increased database fault tolerance |
-
2005
- 2005-11-02 WO PCT/JP2005/020197 patent/WO2006049202A1/ja active Application Filing
- 2005-11-02 US US11/667,181 patent/US20070266061A1/en not_active Abandoned
- 2005-11-02 JP JP2006542419A patent/JP4844743B2/ja not_active Expired - Fee Related
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2000132435A (ja) * | 1998-10-29 | 2000-05-12 | Hitachi Ltd | 異種データベース管理システム間のデータ整合処理装置 |
JP2001265803A (ja) * | 2000-03-22 | 2001-09-28 | Mitsubishi Electric Corp | データベースアクセス高速化システム及びデータベースアクセス高速化方法 |
JP2001350777A (ja) * | 2000-06-05 | 2001-12-21 | Mitsubishi Electric Corp | 分散データベースシステム |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2008009814A (ja) * | 2006-06-30 | 2008-01-17 | Nec Corp | データレプリケーションシステム及びデータレプリケーション方法 |
JP2009181308A (ja) * | 2008-01-30 | 2009-08-13 | Hamamatsu Photonics Kk | ストレージシステム |
US10022245B2 (en) | 2012-12-17 | 2018-07-17 | DePuy Synthes Products, Inc. | Polyaxial articulating instrument |
JP2019114240A (ja) * | 2017-12-22 | 2019-07-11 | ウェアヴァリー カンパニー リミテッドWarevalley Co., Ltd. | Sqlパケット分析を通じての異機種データベースのデータ複製および同期化エラー探知方法およびシステム |
Also Published As
Publication number | Publication date |
---|---|
JP4844743B2 (ja) | 2011-12-28 |
US20070266061A1 (en) | 2007-11-15 |
JPWO2006049202A1 (ja) | 2008-05-29 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11921679B2 (en) | Synchronizing configuration of partner objects across distributed storage systems using transformations | |
CN100472463C (zh) | 用于对存储区中的选定数据执行操作的方法和设备 | |
KR100983300B1 (ko) | 데이터 처리 시스템 내에서의 고장 복구 | |
US7958372B1 (en) | Method and apparatus to convert a logical unit from a first encryption state to a second encryption state using a journal in a continuous data protection environment | |
CN103226502B (zh) | 一种数据灾备控制系统及数据恢复方法 | |
US6581143B2 (en) | Data processing method and apparatus for enabling independent access to replicated data | |
US8839031B2 (en) | Data consistency between virtual machines | |
CN106407040A (zh) | 一种远程数据复制方法及系统 | |
US8626722B2 (en) | Consolidating session information for a cluster of sessions in a coupled session environment | |
US20030204609A1 (en) | Method and apparatus for bandwidth-efficient and storage-efficient backups | |
JP2006209775A (ja) | データ追跡を有するストレージ複製システム | |
JP2007164769A (ja) | ミラーリングされたシステム内の障害を管理するための方法、システム、およびプログラム(ミラーリングされたシステム内の障害の管理) | |
US20130282653A1 (en) | Initializing replication in a virtual machine | |
JP2007518195A (ja) | リモートデータミラーリングを用いたクラスタデータベース | |
CN105373340A (zh) | 用于提供安全多租赁的系统、装置和方法 | |
US10372554B1 (en) | Verification and restore of replicated data using a cloud storing chunks of data and a plurality of hashes | |
EP2191375A1 (en) | Converting backup copies of objects created using a first backup program to backup copies created using a second backup program | |
CN106528338A (zh) | 一种远程数据复制方法、存储设备及存储系统 | |
WO2006049202A1 (ja) | データ多重化システム | |
US6424999B1 (en) | System and method for restoring previously backed-up data in a mass storage subsystem | |
US9858209B1 (en) | Method and apparatus for restoring de-duplicated data | |
WO2018156503A1 (en) | Methods for performing data deduplication on data blocks at granularity level and devices thereof | |
KR101748913B1 (ko) | 분산 저장 환경에서 게이트웨이를 선택하기 위한 클러스터 관리 방법 및 데이터 저장 시스템 | |
JP2011253400A (ja) | 分散ミラードディスクシステム、コンピュータ装置、ミラーリング方法およびそのプログラム | |
JP3598202B2 (ja) | オンラインシステム |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KM KN KP KR KZ LC LK LR LS LT LU LV LY MA MD MG MK MN MW MX MZ NA NG NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SM SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): BW GH GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LT LU LV MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
DPE1 | Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101) | ||
WWE | Wipo information: entry into national phase |
Ref document number: 11667181 Country of ref document: US |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2006542419 Country of ref document: JP |
|
WWP | Wipo information: published in national office |
Ref document number: 11667181 Country of ref document: US |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 05800547 Country of ref document: EP Kind code of ref document: A1 |