Methods and apparatus to perform site recovery of a virtual data center
US-2016077919-A1 · Mar 17, 2016 · US
US9977704B1 · US · B1
| Field | Value |
|---|---|
| Publication number | US-9977704-B1 |
| Application number | US-201414497737-A |
| Country | US |
| Kind code | B1 |
| Filing date | Sep 26, 2014 |
| Priority date | Sep 26, 2014 |
| Publication date | May 22, 2018 |
| Grant date | May 22, 2018 |
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.
Embodiments are described for automatic backup and replication of virtual machines in a virtual center. A system or processor-based operation defines policies governing backup conditions and criteria for backing up and recovering the virtual machines, continuously polls the VMs of the virtual center to determine the health or change in each virtual machine. A backup component backs up at least one VM by copying or transferring data including content and state information of the VM to a storage device or other virtual center. The system detects if a failure condition or change in excess of a defined threshold value exists for any virtual machine, and if so, initiates a recovery operation, and then sends a message to the system administrator regarding the backup and recovery.
Opening claim text (preview).
What is claimed is: 1. A computer-implemented method comprising: defining policies in a policy manager component of a manager component having a backup engine, governing backup conditions and criteria for backing up and recovering data between virtual machines (VMs) in a first virtual center having a first hypervisor and VMs in a second virtual center having a different hypervisor; automatically and continuously polling, in a polling agent of the backup engine, the VMs of the first virtual center to determine a health and an amount of changed data blocks in each VM in accordance with a defined polling schedule; backing up, in a backup operation executing the backup engine, at least one VM of the first virtual center by copying or transferring data including content and state information of the VM to a storage box; detecting, through the continuous polling, if a failure condition or change in excess of the threshold value exists for any VM of the first virtual center; and initiating, through a restore component, a recovery operation if the failure condition or the change is detected, wherein the recovery operation is decoupled from the backup operation through the policy manager and polling agent of the backup engine to allow replication of data between the first and second virtual centers having different hypervisors. 2. The method of claim 1 further comprising transmitting a message to a system administrator indicating a status of the any VM if the failure condition or the change is detected, and wherein the policy manager component creates policies including rules and parameter definitions dictating at least one of: backup schedules, restore schedules, alert triggers, and backup methods, and further wherein the policies are based on change block technology (CBT) factors that defines a threshold value for an amount of change in each VM. 3. The method of claim 1 wherein the storage box comprises a backup storage device and media, and the recovery operation comprises a restore operation transferring the copied or transferred data from the backup storage media to the second virtual center. 4. The method of claim 1 further comprising a replicator component configured to perform conversion from the first hypervisor to the second hypervisor. 5. The method of claim 2 wherein the recovery operation is initiated by one of a command from the system administrator, or an automatic process initiated by a backup server. 6. The method of claim 1 wherein the policies comprise rules that determine whether or not the recovery operation should be performed the any VM based on criteria selected from the group consisting of: percentage byte change for files of a VM relative to the threshold value, any change to a minimum number of VMs in the virtual center, a failure indication of a VM, and an unavailable indication of a VM. 7. The method of claim 6 wherein the policies further comprise initiating the recovery operation synchronously or asynchronously after a defined time with respect to any change to the changed data blocks of a VM. 8. The method of claim 1 wherein the polling schedule is a regular periodic schedule defined within a backup server and dependent on one or more characteristics and constraints of a network environment containing the first virtual center and the second virtual center. 9. The method of claim 1 further comprising storing the changed VM data in cache memory of the backup engine. 10. A system comprising: a policy manager having a hardware implemented backup engine and defining policies governing backup conditions and criteria for backing up and recovering data between virtual machines (VMs) in a first virtual center having a first hypervisor and VMs in a second virtual center having a different hypervisor; a hardware implemented polling agent of the backup engine continuously polling the VMs of the first virtual center to determine a health and an amount of changed data blocks in each VM in accordance with a defined polling schedule; the backup engine backing up at least one VM of the VMs of the first virtual center in a backup operation by copying or transferring data including content and state information of the VM to a storage box, the polling agent detecting if a failure condition or change in excess of the threshold value exists for any VM of the first virtual center; a notification engine transmitting a message to a system administrator indicating a status of the any VM if the failure condition or the change is detected; and a restore component initiating the recovery operation if the failure condition or the change is detected, wherein the recovery operation is decoupled from the backup operation through the policy manager and polling agent of the backup engine to allow replication of data between the first and second virtual centers having different hypervisors. 11. The system of claim 10 wherein the storage box comprises a backup storage device and media, and the recovery operation comprises a restore operation transferring the copied or transferred data from the backup storage media to the second virtual center, and wherein the backup storage device is selected from at least one of a magnetic tape device, an optical disk array, a magnetic disk array, and a virtual memory storage. 12. The system of claim 11 wherein the policies are based on change block technology (CBT) factors that defines a threshold value for an amount of change in each VM, and further comprising a cache memory of the backup engine, and storing the changed VM data, and a replicator component configured to perform conversion from the first hypervisor to the second hypervisor. 13. The system of claim 10 wherein the policy manager component creates policies including rules and parameter definitions dictating at least one of: backup schedules, restore schedules, alert triggers, and backup methods. 14. The system of claim 12 wherein the recovery operation is initiated by one of a command from the system administrator, and an automatic process initiated by a backup server. 15. The system of claim 10 wherein the policies comprise rules that determine whether or not the recovery operation should be performed the any VM based on criteria selected from the group consisting of: percentage byte change for files of a VM relative to the threshold value, any change to a minimum number of VMs in the virtual center, a failure indication of a VM, and an unavailable indication of a VM. 16. The system of claim 15 wherein the policies further comprise initiating the recovery operation synchronously or asynchronously after a defined time with respect to any change to the changed blocks of a VM. 17. The system of claim 10 wherein the polling schedule is a regular periodic schedule defined within a backup server and dependent on one or more characteristics and constraints of a network environment containing the first virtual center and the second virtual center. 18. A computer program product comprising a non-transitory computer usable medium having machine readable code embodied therein for: defining policies in a policy manager component of a manager component having a backup engine, governing backup conditions and criteria for backing up and recovering data between virtual machines (VMs) in a first virtual center having a first hypervisor and VMs in a second virtual center having a different hypervisor; automatically and continuously polling, in a polling agent of the backup engine, the VMs of the first virtual center to determine a health and an amount of changed data blocks in eac
Hypervisor-specific management and integration aspects · CPC title
by selection of backup contents · CPC title
Error or fault detection not based on redundancy (power supply failures G06F1/30; network fault management H04L41/06) · CPC title
Memory management, e.g. access or allocation · CPC title
for networked environments · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.