+

WO2014076765A1 - Dispositif de traitement de données, procédé pour le traitement de données, et programme - Google Patents

Dispositif de traitement de données, procédé pour le traitement de données, et programme Download PDF

Info

Publication number
WO2014076765A1
WO2014076765A1 PCT/JP2012/079395 JP2012079395W WO2014076765A1 WO 2014076765 A1 WO2014076765 A1 WO 2014076765A1 JP 2012079395 W JP2012079395 W JP 2012079395W WO 2014076765 A1 WO2014076765 A1 WO 2014076765A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
asynchronous
data processing
target data
generated
Prior art date
Application number
PCT/JP2012/079395
Other languages
English (en)
Japanese (ja)
Inventor
隆佑 佐藤
Original Assignee
三菱電機株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 三菱電機株式会社 filed Critical 三菱電機株式会社
Priority to PCT/JP2012/079395 priority Critical patent/WO2014076765A1/fr
Publication of WO2014076765A1 publication Critical patent/WO2014076765A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/64—Hybrid switching systems
    • H04L12/6418—Hybrid transport
    • 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/2056—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 by mirroring
    • G06F11/2066—Optimisation of the communication load
    • 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/2056—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 by mirroring
    • G06F11/2082—Data synchronisation
    • 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/2056—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 by mirroring
    • G06F11/2071—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 by mirroring using a plurality of controllers
    • G06F11/2074—Asynchronous techniques
    • 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/2056—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 by mirroring
    • G06F11/2071—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 by mirroring using a plurality of controllers
    • G06F11/2076—Synchronous techniques
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes

Definitions

  • the present invention relates to a replication technique in a data processing system having a redundant configuration.
  • synchronous replication for example, Non-Patent Document 1 for determining synchronization timing according to processing contents such as VM disk and network I / O (Input / Out), and VM processing
  • asynchronous replication for example, Non-Patent Document 2 in which synchronization is performed in a fixed time without depending on the contents.
  • synchronous replication when data is transmitted from the active system to the standby system, the processing of the active system is temporarily stopped, data is transmitted from the active system to the standby system, and data is received from the standby system. This is a method of restarting the active process when notified.
  • Synchronous replication is highly reliable because the data in the active system is reliably reflected in the standby system, but it takes a long time for the processing in the active system to resume.
  • asynchronous replication is a method in which the active data is unilaterally transmitted to the standby system without stopping the active process.
  • Asynchronous replication is high in processing efficiency because it can continue processing in the active system, but is less reliable than synchronous replication because the data in the active system may not reach the standby system.
  • Such a synchronization method is frequently used for redundancy in a database.
  • synchronous replication is used in Patent Document 1
  • asynchronous replication is used in Patent Document 2.
  • database redundancy since the frequency of database updates is lower than the frequency of CPU register and memory updates in VMs, synchronous replication is widely used.
  • VM redundancy since the frequency of updating the CPU register and memory of the VM is high, if the synchronous replication is applied, the processing of the active system is temporarily stopped, which has a fatal effect on the operation of the VM. For this reason, in the redundancy of VMs, asynchronous replication with high performance has been used at the expense of some reliability.
  • JP 2011-039733 A International Publication 2011-111131
  • This invention mainly aims to solve the above-described problems, and mainly aims to realize high reliability while suppressing standby time due to replication.
  • the data processing apparatus Operates as an active system in a redundant data processing system, Synchronous replication that temporarily stops data processing and transmits data to the standby data processing device of the redundant data processing system, and transmits data to the standby data processing device while continuing the data processing
  • a data processing apparatus that performs asynchronous replication A transmission timing determination unit that determines whether or not to defer transmission of the generated asynchronous target data to the standby data processing device when the asynchronous target data to be subjected to the asynchronous replication is generated;
  • a hold data storage unit that stores asynchronous target data determined to hold transmission to the standby data processing device by the transmission timing determination unit;
  • FIG. 1 is a diagram illustrating a configuration example of a data processing system according to Embodiment 1.
  • FIG. 3 is a diagram illustrating a configuration example of a synchronization processing unit according to the first embodiment.
  • FIG. 3 is a flowchart showing an operation example of an active VM execution unit according to the first embodiment.
  • FIG. 3 is a flowchart showing an operation example of a working synchronization processing unit according to the first embodiment.
  • FIG. 3 is a flowchart showing an operation example of a working synchronization processing unit according to the first embodiment.
  • FIG. 3 is a flowchart showing an operation example of a working synchronization processing unit according to the first embodiment.
  • FIG. 3 is a flowchart showing an operation example of an active VM execution unit according to the first embodiment.
  • FIG. 3 is a flowchart showing an active VM execution unit according to the first embodiment.
  • FIG. 3 is a flowchart showing an operation example of a standby synchronization processing unit according to the first embodiment.
  • FIG. 3 is a flowchart showing an operation example of a standby synchronization processing unit according to the first embodiment.
  • FIG. 3 is a diagram illustrating a hardware configuration example of the data processing device according to the first embodiment.
  • Embodiment 1 a data processing system that uses both synchronous replication and asynchronous replication will be described.
  • the update data of the I / O device is transmitted from the active data processing apparatus to the standby data processing apparatus by synchronous replication.
  • Update data of CPU registers and memories other than I / O devices is transmitted from the active data processing device to the standby data processing device by asynchronous replication.
  • Data targeted for synchronous replication is also referred to as synchronization target data
  • data targeted for asynchronous replication is also referred to as asynchronous target data.
  • Asynchronous target data to be subjected to asynchronous replication is data in the CPU register and memory, and is therefore frequently updated. As a result, asynchronous replication frequently occurs.
  • asynchronous replication occurs frequently, a situation may occur in which transmission of asynchronous target data is not completed when data update of an I / O device occurs. In this case, data transmission by synchronous replication is not started unless transmission of asynchronous target data waiting for transmission is completed. As described above, if asynchronous replication occurs frequently, the start of synchronous replication is delayed, and as a result, it takes a long time to complete synchronous replication, which causes the user to wait for a long time.
  • transmission of asynchronous target data that meets a predetermined condition is reserved, and asynchronous target data whose transmission is suspended is transmitted together with synchronization target data by synchronous replication.
  • the frequency of execution of asynchronous replication and the amount of asynchronous target data to be transmitted in one asynchronous replication can be suppressed, and the transmission of asynchronous target data is not completed when synchronous target data occurs. It can be avoided.
  • delay in starting synchronous replication can be avoided, and standby time due to replication can be suppressed.
  • FIG. 1 shows a configuration example of a redundant data processing system according to the present embodiment.
  • the redundant data processing system includes an active data processing device 11 and a standby data processing device 12.
  • the active data processing apparatus 11 is also referred to as the active system 11
  • the standby data processing apparatus 12 is also referred to as the standby system 12.
  • the active physical computer 1001 and the standby physical computer 1002 are connected by a LAN (Local Area Network) 141.
  • the active data processing device 11 and the standby data processing device 12 have the same configuration. In the following, the configuration of the active data processing apparatus 11 will be described as a representative.
  • the physical computer 1001 includes hardware such as a physical CPU 101, a physical memory 102, a physical disk 103, and a physical NIC (Network Interface Card) 104.
  • a virtual machine 2001 operates on the physical machine 1001.
  • the virtual computer 2001 includes a virtual CPU 105, a virtual memory 106, a virtual disk 107, and a virtual NIC 108 as virtual devices.
  • the virtual CPU 105, virtual memory 106, virtual disk 107, and virtual NIC 108 are realized by programs that emulate the physical CPU 101, physical memory 102, physical disk 103, and physical NIC 104, respectively.
  • the virtual machine 2001 includes a VM execution unit 201 and a synchronization processing unit 211 as processing / control means.
  • the VM execution unit 201 and the synchronization processing unit 211 are realized by a virtual machine monitor, for example.
  • the virtual machine 2001 includes an application program and an OS (Operating System).
  • the application program is also called an application. In the present embodiment, it is not necessary to distinguish between the OS and the application, and therefore, they are collectively referred to as OS / application 221.
  • FIG. 2 shows a configuration example of the synchronization processing unit 211 and the synchronization processing unit 212.
  • the failure detection unit 301 detects a failure of the other data processing apparatus.
  • the transmission timing determination unit 302 determines the transmission timing of the asynchronous target data. Specifically, in the active data processing apparatus 11, when the asynchronous target data is generated by the OS / application 221, the transmission timing determination unit 302 transmits the generated asynchronous target data to the standby system 12. It is decided whether to hold or immediately send to the standby system 12 by asynchronous replication.
  • the data transmission unit 303 transmits synchronization target data and asynchronous target data. Specifically, in the active data processing apparatus 11, the data transmission unit 303 transmits synchronization target data and asynchronous target data to the standby system 12. Transmission of synchronization target data and asynchronous target data to the standby system 12 is performed via the physical NIC 104 and the LAN 141.
  • the control unit 304 performs operations other than the operations of the transmission timing determination unit 302 and the data transmission unit 303.
  • the update data holding area 311 temporarily holds update data.
  • the synchronization history holding area 321 holds the attribute (specifically, address) of the asynchronous target data generated together with the synchronization target data.
  • the transmission timing determination unit 302 described above is asynchronous when the address of the generated asynchronous target data (the address of the virtual CPU register or the address of the virtual memory 106) matches the address held in the synchronization history holding area 321. Suspend transmission of the target data.
  • the synchronization history holding area 321 corresponds to an example of an attribute storage unit.
  • the transmission hold area 331 temporarily holds asynchronous target data whose transmission is held by the transmission timing determination unit 302.
  • the transmission hold area 331 corresponds to an example of a hold data storage unit.
  • the VM execution unit 201 inputs update data from the OS / application 221 to an arbitrary virtual device.
  • the VM execution unit 201 determines whether the input update data includes update data for the virtual I / O device (virtual disk 107 or virtual NIC 108).
  • the VM execution unit 201 attaches a synchronization request flag to the update data and adds a synchronization request flag in S505.
  • the updated data is stored in the update data holding area 311.
  • a synchronization request flag is attached to all the update data and stored in the update data holding area 311.
  • the VM execution unit 201 suspends the processing of the OS / application 221 in S ⁇ b> 506 and also suspends the processing of itself (the VM execution unit 201). .
  • the VM execution unit 201 is ready to input an operation resumption notification described later from the synchronization processing unit 211.
  • the VM execution unit 201 holds all the update data in S502. Store in area 311. When all the update data has been stored in the update data holding area 311, the VM execution unit 201 updates the state of the virtual device according to the update data in S ⁇ b> 503. Thereafter, in S504, the VM execution unit 201 continues the operation of the VM including the OS / application 221.
  • the transmission timing determination unit 302 of the synchronization processing unit 211 detects storage of the update data in the update data holding area 311 in step S601.
  • the transmission timing determination unit 302 extracts one update data from the update data holding area 311 in S602.
  • the transmission timing determination unit 302 determines whether or not a synchronization request flag is attached to the extracted update data.
  • the transmission timing determination unit 302 determines whether the synchronization history holding area 321 includes the address targeted by the update data in S604. When the address targeted for the update data is included in the synchronization history holding area 321 (YES in S604), the transmission timing determination unit 302 stores the update data in the transmission hold area 331 in S606. On the other hand, if the address targeted for the update data is not included in the synchronization history holding area 321 (NO in S604), the data transmission unit 303 transmits the update data to the standby system 12 in S605.
  • the transmission in S605 is transmission by asynchronous replication. Note that, when any of the processes of S605 and S606 is performed, the process returns to the detection process of storing update data in the update data holding area 311 in S601 as soon as the process is completed.
  • the transmission timing determination unit 302 includes the address targeted for the update data in S607 in the synchronization history holding area 321. It is determined whether or not. If the address targeted for the update data is included in the synchronization history holding area 321 (YES in S607), the data transmission unit 303 transmits the update data to the standby system 12 in S609. On the other hand, if the address targeted for the update data is not included in the synchronization history holding area 321 (NO in S607), the transmission timing determination unit 302 sets the address targeted for the update data in the synchronization history holding area 321 in S608. In addition, the data transmission unit 303 transmits the update data to the standby system 12 in S609. Note that the transmission of update data in S609 is transmission in synchronous replication.
  • the transmission timing determination unit 302 confirms whether update data exists in the update data holding area 311 in S610. If the update data exists in the update data holding area 311 (YES in S610), the process returns to S602. If there is no update data in the update data holding area 311 (NO in S610), the data transmission unit 303 confirms whether there is update data in the transmission suspension area 331 in S611.
  • the data transmission unit 303 extracts the update data from the transmission suspension area 331 in S612. In step S613, the data transmission unit 303 determines whether update data overlapping with the update data extracted in step S612 has been transmitted to the standby system 12. For example, when transmitting update data in S609, the data transmission unit 303 stores the address of the update data to be transmitted in a predetermined storage area, and the same address as the update data address extracted in S612 is stored in the storage area. If stored, it can be determined that duplicate update data (update data of a later generation) has already been transmitted to the standby system 12.
  • the process returns to S611.
  • the data transmission unit 303 transmits the update data extracted in S612 to the standby system 12. Then, the data transmission unit 303 transmits all the update data in the transmission suspension area 331 to the standby system 12 by repeating S611 to S614.
  • the data transmission unit 303 transmits a synchronization execution command to the standby system in S613.
  • the control unit 304 temporarily stops the processing of the synchronization processing unit 211 in S614.
  • the synchronization processing unit 211 is in a state in which a synchronization completion notification from the standby system 12 can be input.
  • a series of operations of the synchronization processing unit 211 during synchronization execution in the active system 11 is completed.
  • the update data for which YES is determined in S604 is not transmitted to the standby system 12, but is stored in the transmission suspension area 331, thereby reducing the frequency of transmission by asynchronous replication (S605).
  • the update data that becomes NO in S603 is update data of the virtual CPU register and the virtual memory, and is asynchronous target data that is a target of asynchronous replication.
  • the virtual CPU register and virtual memory update data address generated together with the virtual I / O device update data are also held (S 608). ). If the address of the update data that is NO in S603 is included in the synchronization history holding area 321 (YES in S604), the update data of the previous generation of this update data (update data generated in the past update) ) Is generated together with the update data of the virtual I / O device.
  • update data of a later generation of update data that has become YES in S604 (update data generated at a later update) is generated together with update data of the virtual I / O device.
  • update data (generation 0) for address 100 in the virtual memory is generated at 0:00
  • the generation of the update data (generation 0) and the generation of update data for the virtual I / O device are at the same timing.
  • the virtual memory address 100 is added to the synchronization history holding area 321.
  • the update data (generation 0) and the virtual I / O device update data are transmitted to the standby system 12 in step S609.
  • update data (generation 1) is generated at 0:01 for address 100 of the virtual memory without synchronizing with the update data of the virtual I / O device
  • the update data (generation 1) is determined in step S606.
  • update data (generation 0) for address 100 in the virtual memory is generated at 0:02, and the generation of this update data (generation 2) and the generation of update data for the virtual I / O device are at the same timing.
  • the update data (generation 2) and the update data of the virtual I / O device are transmitted to the standby system 12 in S609.
  • the update data (generation 1) in the transmission suspension area 331 is not transmitted to the standby system 12 because it is overlapped with the transmitted update data (generation 2) (NO in S612).
  • generation 1 transmission of asynchronous target data is suspended, and the frequency of transmission by asynchronous replication (S605) is reduced.
  • the control unit 304 of the synchronization processing unit 211 when receiving the synchronization completion notification from the standby system 12 in S700, the control unit 304 of the synchronization processing unit 211 outputs an operation resumption notification to the VM execution unit 201 in S701. Thereafter, the transmission timing determination unit 302 starts detection of storage of update data in the update data holding area 311 in S702.
  • the VM execution unit 201 when the VM execution unit 201 receives an operation resumption notification from the synchronization processing unit 211 in S703, the VM execution unit 201 updates the state of the virtual device according to the update data before stopping the VM processing in S704. When the update is completed, the VM operation is restarted in S705.
  • the control unit 304 receives data from the active system 11 in S800, and determines in S801 whether the received data is virtual device update data. If the received data is update data (YES in S801), the control unit 304 stores the update data in the update data holding area 311 in S808, and resumes data reception processing from the active system 11 in S809. To do.
  • the control unit 304 determines in S802 whether the received data is a synchronous execution command. If the received data is not a synchronous execution command (NO in S802), the control unit 304 executes processing according to the command content in S803. On the other hand, if the received data is a synchronization execution command (YES in S802), the data transmission unit 303 transmits a synchronization completion notification to the active system 11 in S804. Next, the control unit 304 extracts the update data from the update data holding area 311 in S805, and applies the update to the virtual device in S806 according to the update data.
  • step S807 the control unit 304 determines whether update data exists in the update data holding area 311. If the update data exists, the control unit 304 returns to step S805 to transfer all the update data included in the update data holding area 311 to virtual devices. The process is repeated until the application of is completed. When the application of all the update data in the update data holding area 311 is completed, the data reception process from the active system 11 is resumed in S809, and a series of processes at the time of synchronization execution is completed.
  • the failure detection unit 301 detects a failure of the active system 11 in S900. If a failure is detected, the control unit 304 discards the update data in the update data holding area 311 in S901, and transmits an operation resumption notification to the VM execution unit 202 in S902. When the above processing is completed, the control unit 304 ends all the synchronization processing in S903.
  • the VM execution unit updates the state of the virtual device by the OS or application on the VM by the synchronization processing unit having the update data holding area and the synchronization history holding area separately from the VM execution unit.
  • update data transmission processing and update data transmission suspension processing to the standby system are possible.
  • update data is transmitted in advance to shorten the synchronous processing time, thereby compensating for the decrease in VM processing performance due to an increase in the stop time, which is a drawback of synchronous replication. It is possible to make use of system switching without loss of information when a failure occurs, which is an advantage of replication.
  • the I / O performance required by the user is realized by reducing the time to wait for the VM user in synchronous replication, and restoration is performed without loss of data when a failure occurs. Therefore, higher reliability can be achieved compared to the asynchronous type.
  • An active physical computer that operates a synchronization source VM in VM synchronization, and a standby physical computer that operates a synchronization destination VM in VM synchronization;
  • the VM includes a VM execution unit that executes processing of an OS and an application operating on the VM, and a synchronization processing unit that executes VM synchronization processing,
  • An update data holding area that temporarily holds update data transmitted and received for VM synchronization, a synchronization history holding area that holds a history of update data application locations at the time of past update requests, and update data
  • the transmission hold area that holds the update data that has been determined to be held pending by matching the update application location described in the synchronization history holding area for the update data added to the holding area, and the active physical computer or standby physical Provided with a fault detection unit that detects faults in the computer,
  • the synchronization source VM sends update data for VM synchronization by executing an OS or application
  • the update data is stored in the history by referring to and
  • the memory synchronization system including the synchronization processing unit that reduces the time for stopping the synchronization source VM for synchronization by reducing the amount of update data to be transmitted after synchronization execution has been described.
  • FIG. 10 is a diagram illustrating an example of hardware resources of the active data processing device 11 and the standby data processing device 12 according to the present embodiment.
  • the configuration in FIG. 10 is merely an example of the hardware configuration of the active data processing device 11 and the standby data processing device 12, and the active data processing device 11 and the standby data processing device.
  • the hardware configuration of 12 is not limited to the configuration illustrated in FIG. 10, and may be another configuration.
  • the active data processing apparatus 11 and the standby data processing apparatus 12 include a CPU 911 (also referred to as a processor, a central processing unit, a processing unit, an arithmetic unit, a microprocessor, or a microcomputer) that executes a program.
  • the CPU 911 corresponds to the physical CPU 101 and the physical CPU 121 in FIG.
  • the CPU 911 is connected to, for example, a ROM (Read Only Memory) 913, a RAM 914, a NIC 915, a display device 901, a keyboard 902, a mouse 903, a magnetic disk device 920, and a scanner device 907 via a bus 912, and these hardware devices.
  • ROM Read Only Memory
  • the RAM 914 corresponds to the physical memory 102 and the physical memory 122 of FIG.
  • the magnetic disk device 920 corresponds to the physical disk 103 and the physical disk 123 of FIG.
  • the NIC 915 corresponds to the physical NIC 104 and the physical NIC 124 in FIG.
  • the CPU 911 may be connected to an FDD 904 (Flexible Disk Drive), a compact disk device 905 (CDD), and a printer device 906.
  • FDD 904 Flexible Disk Drive
  • CDD compact disk device
  • SSD Solid State Drive
  • the RAM 914 is an example of a volatile memory.
  • the storage media of the ROM 913, the FDD 904, the CDD 905, and the magnetic disk device 920 are an example of a nonvolatile memory. These are examples of the storage device.
  • the NIC 915, the keyboard 902, the mouse 903, the FDD 904, the scanner device 907, and the like are examples of input devices.
  • the NIC 915, the display device 901, the printer device 906, and the like are examples of output devices.
  • the NIC 915 is connected to the LAN.
  • the NIC 915 can be connected to, for example, the Internet, a WAN (Wide Area Network), or the like via a LAN.
  • WAN Wide Area Network
  • the magnetic disk device 920 stores a virtual machine monitor 921, a host OS 922, a program group 923, and a file group 924. Also, the OS / application 221 and the OS / application 222 in FIG. 1 are included in the program group 923. The virtual machine monitor 921, the host OS 922, and the program group 923 are executed by the CPU 911.
  • the file group 924 includes “determination”, “determination”, “determination”, “change of”, “input of”, and “output” in the description of this embodiment. ”,“ Receiving ”,“ Transmission ”, etc.
  • Information, data, signal values, variable values, and parameters that indicate the results of the processing are displayed as“ ⁇ File ”and“ ⁇ Database ”items. It is remembered.
  • the “ ⁇ file” and “ ⁇ database” are stored in a recording medium such as a disk or a memory.
  • Information, data, signal values, variable values, and parameters stored in a storage medium such as a disk or memory are read out to the main memory or cache memory by the CPU 911 via a read / write circuit, and extracted, searched, referenced, compared, and calculated.
  • Information, data, signal values, variable values, and parameters are stored in the main memory, registers, cache memory, and buffers during the CPU operations of extraction, search, reference, comparison, calculation, processing, editing, output, printing, and display. It is temporarily stored in a memory or the like.
  • the arrows in the flowchart described in this embodiment mainly indicate input / output of data and signals, and the data and signal values are the RAM 914 memory, the FDD904 flexible disk, the CDD905 compact disk, and the magnetic disk device. 920 magnetic disks, other optical disks, Blu-ray (registered trademark) disks, DVDs, and other recording media. Data and signals are transmitted online via a bus 912, signal lines, cables, or other transmission media.
  • the active data processing device 11 and the standby data processing device 12 shown in the present embodiment are output devices such as a CPU as a processing device, a memory as a storage device, a magnetic disk, a keyboard as an input device, a mouse, a NIC, and the like.
  • a computer including a display device, a NIC, and the like, and implements the functions in the virtual computer 2001 and the virtual computer 2002 using these processing devices, storage devices, input devices, and output devices.
  • the data processing method according to the present invention can be realized by the operations of the active data processing apparatus 11 and the standby data processing apparatus 12 described in the present embodiment.
  • 11 active data processing device, 12 standby data processing device, 101 physical CPU, 102 physical memory, 103 physical disk, 104 physical NIC, 105 virtual CPU, 106 virtual memory, 107 virtual disk, 108 virtual NIC, 121 physical CPU, 122 physical memory, 123 physical disk, 124 physical NIC, 125 virtual CPU, 126 virtual memory, 127 virtual disk, 128 virtual NIC, 141 LAN, 201 VM execution unit, 202 VM execution unit, 211 synchronization processing unit, 212 synchronization Processing unit, 301 failure detection unit, 302 transmission timing determination unit, 303 data transmission unit, 311 update data holding area, 321 synchronization history holding area, 331 transmission hold area, 1001 physical computer, 1002 Management computer, 2001 virtual machine, 2002 virtual machine.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Hardware Redundancy (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

Quand des données cible asynchrones, qui doivent être dupliquées de façon asynchrone, sont générées, un module d'exécution d'opération de synchronisation (211) d'un dispositif de traitement de données (11) d'un système actuellement en cours d'utilisation : détermine s'il faut retarder, ou non, la transmission des données cible asynchrones qui ont été générées, à un dispositif de traitement de données (12) d'un système de veille ; et il enregistre les données cible asynchrones dont la transmission au dispositif de traitement de données (12) du système de veille a été retardée. Quand des données cible asynchrones, qui doivent être dupliquées de façon asynchrone, sont générées, le module d'exécution d'opération de synchronisation (211) du dispositif de traitement de données (11) du système actuellement en cours d'utilisation : transmet les données cible asynchrones qui ont été générées, ainsi que les données cible asynchrones dont la transmission a été retardée, au dispositif de traitement de données (12) du système de veille, au moyen d'une opération de duplication synchrone.
PCT/JP2012/079395 2012-11-13 2012-11-13 Dispositif de traitement de données, procédé pour le traitement de données, et programme WO2014076765A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/JP2012/079395 WO2014076765A1 (fr) 2012-11-13 2012-11-13 Dispositif de traitement de données, procédé pour le traitement de données, et programme

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2012/079395 WO2014076765A1 (fr) 2012-11-13 2012-11-13 Dispositif de traitement de données, procédé pour le traitement de données, et programme

Publications (1)

Publication Number Publication Date
WO2014076765A1 true WO2014076765A1 (fr) 2014-05-22

Family

ID=50730709

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2012/079395 WO2014076765A1 (fr) 2012-11-13 2012-11-13 Dispositif de traitement de données, procédé pour le traitement de données, et programme

Country Status (1)

Country Link
WO (1) WO2014076765A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2001337939A (ja) * 2000-05-25 2001-12-07 Hitachi Ltd データ多重化方法およびデータ多重化システム
JP2005018510A (ja) * 2003-06-27 2005-01-20 Hitachi Ltd データセンタシステム及びその制御方法
JP2005267301A (ja) * 2004-03-19 2005-09-29 Hitachi Ltd ログ同期ｄｂデータ非同期転送によるリカバリ方式および装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2001337939A (ja) * 2000-05-25 2001-12-07 Hitachi Ltd データ多重化方法およびデータ多重化システム
JP2005018510A (ja) * 2003-06-27 2005-01-20 Hitachi Ltd データセンタシステム及びその制御方法
JP2005267301A (ja) * 2004-03-19 2005-09-29 Hitachi Ltd ログ同期ｄｂデータ非同期転送によるリカバリ方式および装置

Similar Documents

Publication Publication Date Title
US11507477B2 (en) Virtual machine fault tolerance
US10678655B2 (en) Using RDMA for fast system recovery in virtualized environments
US9575785B2 (en) Cluster system and method for providing service availability in cluster system
US9983935B2 (en) Storage checkpointing in a mirrored virtual machine system
US20140201574A1 (en) System and Method for Writing Checkpointing Data
US20210374155A1 (en) Synchronizing changes to stale components of a distributed object using synchronization bitmaps
US10402264B2 (en) Packet-aware fault-tolerance method and system of virtual machines applied to cloud service, computer readable record medium and computer program product
US20230029074A1 (en) Shadow live migration over a smart network interface card
US8090907B2 (en) Method for migration of synchronous remote copy service to a virtualization appliance
JP5561334B2 (ja) データ転送装置
US9043283B2 (en) Opportunistic database duplex operations
US10341177B2 (en) Parallel computing system and migration method
WO2014076765A1 (fr) Dispositif de traitement de données, procédé pour le traitement de données, et programme
JP6056408B2 (ja) フォールトトレラントシステム
US11669516B2 (en) Fault tolerance for transaction mirroring
KR102472878B1 (ko) 가상 머신 환경에서의 블록 커밋 방법 및 그 방법을 수행하는 가상화 시스템
WO2023030013A1 (fr) Procédé et appareil de traitement de données
JP5335150B2 (ja) 計算機装置及びプログラム
JP5880608B2 (ja) フォールトトレラントサーバ
US10642788B1 (en) Sand timer algorithm for tracking in-flight data storage requests for data replication
JP2018022328A (ja) 処理制御方法及び計算機

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 12888271

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 12888271

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: JP

点击 这是indexloc提供的php浏览器服务，不要输入任何密码和下载