Multi-RPO data protection

• US 10,657,006 B2
• Filed: 08/08/2016
• Issued: 05/19/2020
• Est. Priority Date: 03/17/2010
• Status: Active Grant

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Zerto Ltd (Hewlett-Packard Enterprise Company)
• Inventors: Burshan, Chen, Shefi, Omri, Kuszpet, Yair, Kedem, Ziv
• Primary Examiner(s): Asres, Hermon
• Assistant Examiner(s): Bukhari, Sibte H
• Application Number:
  US15/231,388
• Publication Number:
  US 20160357642A1
• Time in Patent Office: 1,380 Days
• Field of Search: 709223
• CPC Class Codes: G06F 11/1451 by selection of backup contents
• CPC Class Codes: G06F 11/1461 Backup scheduling policy
• CPC Class Codes: G06F 11/1469 Backup restoration techniques
• CPC Class Codes: G06F 11/1471 involving logging of persistent data for recovery
• CPC Class Codes: G06F 11/1484 involving virtual machines
• CPC Class Codes: G06F 11/2038 with a single idle spare processing component
• CPC Class Codes: G06F 11/2048 where the redundant components share neither address space nor persistent storage
• CPC Class Codes: G06F 11/2066 Optimisation of the communication load
• CPC Class Codes: G06F 11/2069 Management of state, configuration or failover
• CPC Class Codes: G06F 11/2071 using a plurality of controllers
• CPC Class Codes: G06F 11/2082 Data synchronisation
• CPC Class Codes: G06F 11/2097 maintaining the standby controller/processing unit updated initialisation or re-synchronisation thereof G06F11/1658 and subgroups
• CPC Class Codes: G06F 2009/45579 I/O management, e.g. providing access to device drivers or storage
• CPC Class Codes: G06F 2201/805 Real-time
• CPC Class Codes: G06F 2201/815 Virtual
• CPC Class Codes: G06F 2201/84 Using snapshots, i.e. a logical point-in-time copy of the data
• CPC Class Codes: G06F 2201/855 Details of asynchronous mirroring using a journal to transfer not-yet-mirrored changes
• CPC Class Codes: G06F 9/45533 Hypervisors; Virtual machine monitors

Abstract

A system for disaster recovery including a controller (i) for controlling bandwidth usage of a disaster recovery system in accordance with a plurality of recovery point objectives (RPOs), each RPO designating a maximal time loss constraint for data recovery for an enterprise production system, and a corresponding bandwidth allocation for the disaster recovery system to use in replicating data for the enterprise production system, wherein the RPOs are applied in accordance with a calendar-based schedule of dates and times, and (ii) for issuing an RPO alert when the RPO maximal time loss constraint for a current date and time is not satisfied.

Claims

1. A system for disaster recovery, comprising:

a virtual manager that executes on a computing device having one or more processors and memory to cause the one or more processors to;

control usage of bandwidth by a virtual server in accordance with a calendar- based schedule defining a first recovery point objective for a first time period and a second recovery point objective for a second time period different from the first time period, the first recovery point objective specifying a first maximum loss constraint for data recovery and a first allocation of the bandwidth for data replication for the first time period, the second recovery point objective specifying a second maximum loss constraint for data recovery and a second allocation of the bandwidth for data replication for the second time period, the first allocation of the bandwidth for the first time period different from the second allocation of the bandwidth for the second time period;

adjust the usage of bandwidth by the virtual server in accordance with the first recovery point objective and the second recovery point objective; and

issue an alert, responsive to determination that at least one of the first recovery point objective and the second recovery point objective is not satisfied.

2. The system of claim 1, comprising:

the virtual manager to control the usage of the bandwidth by the virtual server in accordance with the calendar-based schedule, the calendar-based schedule specifying a third allocation of the bandwidth for data production for the first time period and a fourth allocation of the bandwidth for data production for the second time period.

3. The system of claim 1, comprising the virtual manager to:

adjust the calendar-based schedule based on the alert.

4. The system of claim 1, comprising:

the virtual manager to identify one of the first recovery point objective or the second recovery point objective to apply based on a current time.

5. The system of claim 1, comprising:

the virtual manager to increase the first allocation of the bandwidth for data replication for the first time period, the first time period corresponding to a peak usage time period.

6. The system of claim 1, comprising:

the virtual manager to decrease the second allocation of the bandwidth for data replication for the second time period corresponding to an off-peak usage time period.

7. The system of claim 1, comprising:

the virtual manager to share the bandwidth of the virtual server at a first site with a second virtual server at a second site.

8. The system of claim 1, comprising:

the virtual manager to control bandwidth usage of a first type of network traffic in accordance with the first recovery point objective and to control bandwidth usage of a second type of network traffic in accordance with the second recovery point objective.

9. The system of claim 1, wherein the first time period includes a first period of a day and the second time period includes a second period of the day different from the first period of the day.

19. The system of claim 1, comprising:

the virtual manager to control the usage of the bandwidth by the virtual server in accordance with the calendar-based schedule.

20. The system of claim 1, comprising:

the virtual manager in communication with a hypervisor including the virtual server and a virtual data services appliance for virtual data replication.

10. A method of disaster recovery, comprising:

controlling, by a virtual manager executing on a computing device having one or more processors and memory, usage of bandwidth by a virtual server in accordance with calendar- based schedule defining a first recovery point objective for a first time period and a second recovery point objective for a second time period different from the first time period, the first recovery point objective specifying a first maximum loss constraint for data recovery and a first allocation of the bandwidth for data replication for the first time period, the second recovery point objective specifying a second maximum loss constraint for data recovery and a second allocation of the bandwidth for data replication for the second time period, the first allocation of the bandwidth for the first time period different from the second allocation of the bandwidth for the second time period;

adjusting, by the virtual manager, the bandwidth usage of the virtual server in accordance with the first recovery point objective and the second recovery point objective; and

issuing, by the virtual manager, an alert, responsive to determination that at least one of the first recovery point objective and the second recovery point objective is not satisfied.

11. The method of claim 10, comprising:

controlling, by the virtual manager, the usage of the bandwidth by the virtual server in accordance with the calendar-based schedule, the calendar-based schedule specifying a third allocation of the bandwidth for data production for the first time period and a fourth allocation of the bandwidth for data production for the second time period.

12. The method of claim 10, comprising:

adjusting, by the virtual manager, the calendar-based schedule, responsive to the issuing of the alert.

13. The method of claim 10, comprising:

identifying, by the virtual manager, one of the first recovery point objective or the second recovery point objective to apply based on a current time.

14. The method of claim 10, comprising:

increasing, by the virtual manager, the first allocation of the bandwidth for data replication for the first time period corresponding to a peak usage time period.

15. The method of claim 10, comprising:

decreasing, by the virtual manager, the second allocation of the bandwidth for data replication for the second time period corresponding to an off-peak usage time period.

16. The method of claim 10, comprising:

sharing, by the virtual manager, the bandwidth of the virtual server at a first site with a second virtual server at a second site.

17. The method of claim 10, comprising:

controlling, by the virtual manager, a bandwidth usage of a first type of network traffic in accordance with the first recovery point objective and to control a bandwidth usage of a second type of network traffic in accordance with the second recovery point objective.

18. The method of claim 10, comprising controlling, by the virtual manager, the bandwidth usage of the virtual server in accordance with the first recovery point objective and the second recovery point objective, the first time period of the first recovery point objective including a first period of a day, the second time period of the second recovery point objective including a second period of the day different from the first period of the day.