Virtual mode execution manager
US-12118376-B2 · Oct 15, 2024 · US
US8997098B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-8997098-B2 |
| Application number | US-201313759336-A |
| Country | US |
| Kind code | B2 |
| Filing date | Feb 5, 2013 |
| Priority date | Oct 31, 2012 |
| Publication date | Mar 31, 2015 |
| Grant date | Mar 31, 2015 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Disclosed herein are a server duplication system and method and a storage medium storing a server duplication computer program. The server duplication system includes a primary server including a hypervisor including a hypervisor-based fault tolerance module and a first file system virtual machine (FS VM), and a first standby server including a hypervisor including a hypervisor-based fault tolerance module that exchanges data with a fault tolerance module provided on the hypervisor of the primary server and duplicates the primary server. The first FS VM provides a first file system that is shared by a user virtual machine (USER VM), and a buffer cache that is used in conjunction with the first file system is provided on virtual memory. The first FS VM is duplicated into the standby server using the hypervisor-based fault tolerance module of the primary server and the hypervisor-based fault tolerance module of the standby server.
Opening claim text (preview).
What is claimed is: 1. A non-transitory computer-readable storage medium storing a computer program that enables a computer system to perform operations comprising: generating a first file system virtual machine (FS VM) on a respective hypervisor of a primary server; installing a file system in the first FS VM; disposing a buffer cache, operating in conjunction with the file system installed in the first FS VM, in a virtual memory allocated to the first FS VM; generating a user virtual machine (USER VM) on the respective hypervisor of the primary server so that the USER VM shares the file system of the first FS VM; and duplicating the buffer cache into a buffer cache of a second FS VM generated on a respective hypervisor of a standby server, wherein the disposing of the buffer cache, in the virtual memory, comprises: receiving information about resources allocated to the file system; allocating resources to the first FS VM according to the information about the resources; and allocating a storage area of the virtual memory, to the buffer cache, of a size allocated to the first FS VM based on a predetermined ratio and on the information about the resources. 2. The non-transitory computer-readable storage medium of claim 1 , wherein the operations further comprise managing, by the first FS VM, the buffer cache in a write-back manner. 3. The non-transitory computer-readable storage medium of claim 1 , wherein the second FS VM is generated by duplicating the first FS VM into the standby server. 4. The non-transitory computer-readable storage medium of claim 1 , wherein: the respective hypervisor of the primary server and the respective hypervisor of the standby server comprise hypervisor-based fault tolerance modules, respectively; and the duplicating of the buffer cache further comprises duplicating the buffer cache of the first FS VM into the buffer cache of the second FS VM using the respective fault tolerance module of the respective hypervisor of the primary server and the respective fault tolerance module of the respective hypervisor of the standby server. 5. The non-transitory computer-readable storage medium of claim 4 , wherein the duplicating of the buffer cache further comprises: when the USER VM invokes a data write call, loading write target data in the buffer cache of the first FS VM; loading the write target data in the buffer cache of the second FS VM via the respective fault tolerance module of the respective hypervisor of the primary server and the respective fault tolerance module of the respective hypervisor of the standby server; and once the loading of the write target data in the buffer cache of the second FS VM has been completed, returning a response to the data write call. 6. The non-transitory computer-readable storage medium of claim 1 , wherein the duplicating of the buffer cache is performed by duplicating the FS VM generated on the primary server into the standby server. 7. The non-transitory computer-readable storage medium of claim 1 , wherein the operations further comprise adjusting a size of the buffer cache depending on a number of user virtual machines (USER VMs) generated on the primary server. 8. The non-transitory computer-readable storage medium of claim 1 , wherein the operations further comprise adjusting a size of the buffer cache depending on a number of data write calls made by all USER VMs generated on the primary server. 9. The non-transitory computer-readable storage medium of claim 1 , wherein the operations further comprise requesting, by the first FS VM, the hypervisor of the primary server to cause data, loaded in the buffer cache, to be flushed based on at least one of an amount of I/O of the primary server and an amount of use of the buffer cache. 10. A method of duplicating a primary server into a standby server that is a fault tolerance partner of a primary server, comprising: generating a first FS VM on a hypervisor of the primary server that provides a file system that is outsourced by a USER VM generated on the respective hypervisor of the primary server; generating a second FS VM on a respective hypervisor of the standby server that provides the same file system that is outsourced by the USER VM that is duplicated on the respective hypervisor of the standby server; disposing a first buffer cache, that the first FS VM manages in conjunction with the file system, in a virtual memory allocated to the first FS VM; and duplicating the buffer cache into a second buffer cache that the second FS VM manages in conjunction with the file system, wherein the disposing of the first buffer cache in the virtual memory comprises: receiving information about resources allocated to the file system; allocating resources to the first FS VM according to the information about the resources; and allocating a storage area of the virtual memory, to the first buffer cache, of a size allocated to the first FS VM based on a predetermined ratio and on the information about the resources. 11. The method of claim 10 , wherein: the respective hypervisor of the primary server and the respective hypervisor of the standby server comprise hypervisor-based fault tolerance modules, respectively; and the duplicating of the first buffer cache comprises duplicating the first buffer cache of the first FS VM into the second buffer cache of the second FS VM using the respective fault tolerance module of the respective hypervisor of the primary server and the respective fault tolerance module of the respective hypervisor of the standby server. 12. The method of claim 10 , further comprising disposing, by the first FS VM and the second FS VM, the buffer caches in their respective virtual memory areas. 13. The method of claim 12 , wherein: the respective hypervisor of the primary server and the respective hypervisor of the standby server comprise hypervisor-based fault tolerance modules, respectively; and the duplicating of the first buffer cache comprises duplicating, by a respective fault tolerance module of a respective hypervisor of the primary server, the respective virtual memory area of the first FS VM into the respective virtual memory area of the second FS VM using the respective fault tolerance module of the respective hypervisor of the standby server. 14. A server duplication system, comprising: a primary server comprising a respective hypervisor including a respective hypervisor-based fault tolerance module and a first file system virtual machine (FS VM); and a first standby server comprising a respective hypervisor including a respective hypervisor-based fault tolerance module that exchanges data with a fault tolerance module provided on the respective hypervisor of the primary server and duplicates the primary server, wherein: the first FS VM provides a first file system that is shared by a USER VM generated on the respective hypervisor of the primary server, and disposes a buffer cache that is used in conjunction with the first file system on virtual memory allocated to the first FS VM; the first FS VM is duplicated into the standby server using the respective hypervisor-based fault tolerance module of the primary server and the respective hypervisor-based fault tolerance module of the standby server; and the first FS VM disposes the buffer cache on the virtual memory by receiving information about resources allocated to the first file system, allocating resources to the first FS VM according to the information about the resources, and allocating a storage area of the virtual memory, to the buffer cache, of a size allocated to the first FS VM based on a predetermined ratio an
with more than one idle spare processing component · CPC title
with a single idle spare processing component · CPC title
Hypervisors; Virtual machine monitors · CPC title
Hypervisor-specific management and integration aspects · CPC title
Virtual · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.