Automatic Selection of Data Movers for Protecting Virtual Machines
US-2023267053-A1 · Aug 24, 2023 · US
US12164387B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12164387-B2 |
| Application number | US-202217694237-A |
| Country | US |
| Kind code | B2 |
| Filing date | Mar 14, 2022 |
| Priority date | Mar 14, 2022 |
| Publication date | Dec 10, 2024 |
| Grant date | Dec 10, 2024 |
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.
A storage cluster may dynamically select a data transport mode for supporting a backup or export job. The storage cluster may receive a trigger indication to create, a backup of data of a source virtual machine. The storage cluster may select a data transport mode to use for reading the data from the source virtual machine to create the backup at the storage cluster. The selection may be from a set of data transport modes that includes a proxy virtual machine mode and a direct-to-host mode. The storage cluster may transmit, to a host for the source virtual machine, a request to activate the selected data transport mode, and receive the data from the source virtual machine via the selected data transport mode. The storage cluster may use the data to create the backup.
Opening claim text (preview).
What is claimed is: 1. A method, comprising: receiving a trigger indication to create, at a storage cluster, a backup of data of a source virtual machine; selecting, after receiving the trigger indication, a data transport mode to use for reading the data from the source virtual machine to create the backup at the storage cluster, wherein the selecting is from among a set of data transport modes that comprises a proxy virtual machine mode and a direct-to-host mode, and wherein the selecting of the data transport mode is based at least in part on whether the backup is a full backup or an incremental backup of the source virtual machine; transmitting, to a host for the source virtual machine and based at least in part on the selected data transport mode, a request to activate the selected data transport mode; receiving, at the storage cluster based at least in part on transmitting the request, the data from the source virtual machine via the selected data transport mode; and using the data received via the selected data transport mode to create the backup at the storage cluster. 2. The method of claim 1 , wherein selecting the data transport mode comprises: selecting the proxy virtual machine mode as the data transport mode based at least in part on the backup being the full backup of the source virtual machine, wherein the data is received from at least one proxy virtual machine based at least in part on selecting the proxy virtual machine mode. 3. The method of claim 2 , wherein the backup is the full backup based at least in part on the backup being an initial backup of the source virtual machine or based at least in part on a user input. 4. The method of claim 1 , wherein the selecting of the data transport mode is further based at least in part on a size of the data to be transferred from the source virtual machine relative to a threshold size, and wherein at least one of the size of the data to be transferred or the threshold size is based at least in part on whether the backup is the full backup or the incremental backup. 5. The method of claim 1 , wherein selecting the data transport mode comprises: selecting the direct-to-host mode based at least in part on the backup being the incremental backup of the source virtual machine, wherein the data from the source virtual machine is received via a secure socket layer established by a centralized management utility of the host. 6. The method of claim 1 , further comprising: calculating, based at least in part on selecting the proxy virtual machine mode, a number of proxy virtual machines to use for the backup of the source virtual machine, wherein the data is received from the source virtual machine via the calculated number of proxy virtual machines. 7. The method of claim 6 , wherein calculating the number of proxy virtual machines comprises: determining a size of a virtual disk corresponding to the source virtual machine; determining a number of child jobs to perform the backup of the source virtual machine based at least in part on the size of the virtual disk; and calculating the number of proxy virtual machines based at least in part on the number of child jobs. 8. The method of claim 7 , wherein: a proxy virtual machine is limited to a maximum number of child jobs based at least in part on a number of ports attachable to the proxy virtual machine, and the number of proxy virtual machines is calculated based at least in part on the maximum number of child jobs. 9. The method of claim 7 , wherein receiving the data comprises: receiving, via a first child job of the number of child jobs, a first portion of the data from a proxy virtual machine of the number of proxy virtual machines, wherein the first child job uses one or more ports of the proxy virtual machine; and receiving, via a second child job of the number of child jobs, a second portion of the data from the proxy virtual machine, wherein the second child job uses at least one other port of the proxy virtual machine or at least one port of the one or more ports after the first child job releases the at least one port. 10. The method of claim 1 , wherein receiving the data comprises: receiving the data from the source virtual machine via at least one proxy virtual machine based at least in part on selecting the proxy virtual machine mode and according to a first backup job. 11. The method of claim 10 , further comprising: receiving additional data from a second source virtual machine via the at least one proxy virtual machine according to a second backup job, wherein the at least one proxy virtual machine is shared by the first backup job and the second backup job. 12. The method of claim 10 , further comprising: transmitting, to the host via the at least one proxy virtual machine, data to recover a second source virtual machine at the host according to a recovery job, wherein the first backup job and the recovery job share the at least one proxy virtual machine. 13. The method of claim 10 , wherein receiving the data via the at least one proxy virtual machine comprises: receiving a first portion of the data via a first proxy virtual machine; and receiving a second portion of the data via a second proxy virtual machine such that the first backup job is allocated to the first proxy virtual machine and the second proxy virtual machine. 14. The method of claim 1 , further comprising: receiving a second trigger indication to recover a second virtual machine at the host; selecting, based at least in part on receiving the trigger indication to recover the second virtual machine, the proxy virtual machine mode to export data for recovering the second virtual machine; and exporting the data for the second virtual machine to the host via at least one proxy virtual machine based at least in part on selecting the proxy virtual machine mode. 15. The method of claim 14 , further comprising: calculating a number of proxy virtual machines for exporting the data based at least in part on a number of virtual disks corresponding to the second virtual machine, a maximum number of data streams, or a combination thereof. 16. The method of claim 1 , further comprising: using an on-demand proxy virtual machine or a persistent proxy virtual machine to receive the data from the source virtual machine based at least in part on selecting the proxy virtual machine mode. 17. The method of claim 1 , wherein selection of the proxy virtual machine mode results in instantiation of a proxy virtual machine at the host and selection of the direct-to-host mode avoids overhead associated with instantiation of the proxy virtual machine. 18. The method of claim 1 , wherein the proxy virtual machine mode is a HotAdd mode that instantiates a proxy virtual machine to transfer the data and the direct-to-host mode is a network block device (NBD) mode that transfers the data without instantiation of the proxy virtual machine. 19. An apparatus, comprising: one or more processors; one or more memories coupled with the one or more processors; and instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to: receive a trigger indication to create, at a storage cluster, a backup of data of a source virtual machine; select, after receiving the trigger indication, a data transport mode to use for reading the data from the source virtual machine to create the backup at the storage cluster, wherein the selecting is from among a set of data transport modes that comprises a proxy v
where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems (multiprogramming arrangements G06F9/46; allocation of resources G06F9/50) · CPC title
Hypervisor-specific management and integration aspects · CPC title
I/O management, e.g. providing access to device drivers or storage · CPC title
by selection of backup contents · CPC title
Hypervisors; Virtual machine monitors · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.