Data synchronization using redundancy detection
US-2016380840-A1 · Dec 29, 2016 · US
US10579488B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10579488-B2 |
| Application number | US-201715713714-A |
| Country | US |
| Kind code | B2 |
| Filing date | Sep 25, 2017 |
| Priority date | Jul 31, 2017 |
| Publication date | Mar 3, 2020 |
| Grant date | Mar 3, 2020 |
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.
One or more embodiments provide techniques for migrating virtual machines (VMs) from a private data center to a cloud data center. A hybrid cloud manager determines a scope of migration from the private data center to the cloud data center. The hybrid cloud manager groups each VM included in the scope of migration into one or more clusters. The hybrid cloud manager defines one or more migration phases. Each migration phase comprises a subset of the one or more clusters. The hybrid cloud manager generates a migration schedule based on at least the one or more migration phases. The hybrid cloud manager migrates the VMs from the private data center to the cloud data center in accordance with the migration schedule.
Opening claim text (preview).
What is claimed is: 1. A method of migrating virtual machines (VMs) from a private data center to a cloud data center, comprising: determining a scope of migration from the private data center to the cloud data center; grouping each VM included in the scope of migration into one or more clusters; defining one or more migration phases, wherein each migration phase comprises a subset of the one or more clusters; generating a migration schedule based on at least the one or more migration phases; and migrating the VMs from the private data center to the cloud data center in accordance with the migration schedule. 2. The method of claim 1 , wherein determining the scope of migration from the private data center to the cloud data center, comprises: identifying those VMs marked as protected for disaster recovery scenarios. 3. The method of claim 1 , wherein determining the scope of migration from the private data center to the cloud data center, comprises: identifying those VMs selected by a user for selective migration. 4. The method of claim 1 , wherein grouping each VM included in the scope of migration into one or more clusters, comprises: parsing a profile of each VM searching for an application signature associated with the VM. 5. The method of claim 1 , wherein grouping each VM included in the scope of migration into one or more clusters, comprises: identifying network connectivity of each VM. 6. The method of claim 1 , wherein grouping each VM included in the scope of migration into one or more clusters, comprises: identifying a location of each VM. 7. The method of claim 1 , wherein grouping each VM included in the scope of migration into one or more clusters, comprises: identifying security data for each VM. 8. The method of claim 1 , wherein grouping each VM included in the scope of migration into one or more clusters, comprises: identifying user input denoting in which cluster to group each VM. 9. A non-transitory computer readable medium having instructions stored thereon that when executed by a processor cause the processor to perform a method of migrating virtual machines (VMs) from a private data center to a cloud data center, comprising: determining a scope of migration from the private data center to the cloud data center; grouping each VM included in the scope of migration into one or more clusters; defining one or more migration phases, wherein each migration phase comprises a subset of the one or more clusters; generating a migration schedule based on at least the one or more migration phases; and migrating the VMs from the private data center to the cloud data center in accordance with the migration schedule. 10. The non-transitory computer readable medium of claim 9 , wherein determining the scope of migration from the private data center to the cloud data center, comprises: identifying those VMs marked as protected for disaster recovery scenarios. 11. The non-transitory computer readable medium of claim 9 , wherein determining the scope of migration from the private data center to the cloud data center, comprises: identifying those VMs selected by a user for selective migration. 12. The non-transitory computer readable medium of claim 9 , wherein grouping each VM included in the scope of migration into one or more clusters, comprises: parsing a profile of each VM searching for an application signature associated with the VM. 13. The non-transitory computer readable medium of claim 9 , wherein grouping each VM included in the scope of migration into one or more clusters, comprises: identifying network connectivity of each VM. 14. The non-transitory computer readable medium of claim 9 , wherein grouping each VM included in the scope of migration into one or more clusters, comprises: identifying a location of each VM. 15. The non-transitory computer readable medium of claim 9 , wherein grouping each VM included in the scope of migration into one or more clusters, comprises: identifying security data for each VM. 16. The non-transitory computer readable medium of claim 9 , wherein grouping each VM included in the scope of migration into one or more clusters, comprises: identifying user input denoting in which cluster to group each VM. 17. A computer system, comprising: a processor; and a memory storing program code, which, when executed on the processor, performs a method of migrating virtual machines (VMs) from a private data center to a cloud data center, comprising: determining a scope of migration from the private data center to the cloud data center; grouping each VM included in the scope of migration into one or more clusters; defining one or more migration phases, wherein each migration phase comprises a subset of the one or more clusters; generating a migration schedule based on at least the one or more migration phases; and migrating the VMs from the private data center to the cloud data center in accordance with the migration schedule. 18. The computer system of claim 17 , wherein determining the scope of migration from the private data center to the cloud data center, comprises: identifying those VMs marked as protected for disaster recovery scenarios. 19. The computer system of claim 17 , wherein determining the scope of migration from the private data center to the cloud data center, comprises: identifying those VMs selected by a user for selective migration. 20. The computer system of claim 17 , wherein grouping each VM included in the scope of migration into one or more clusters, comprises: parsing a profile of each VM searching for an application signature associated with the VM.
involving logging of persistent data for recovery · CPC title
resumption being on a different machine, e.g. task migration, virtual machine migration (G06F9/5088 takes precedence) · CPC title
Hypervisor-specific management and integration aspects · CPC title
using migration · CPC title
Distribution of virtual machine instances; Migration and load balancing · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.