IP Library Granted Patent US 9,442,748
Granted Patent B2
US 9,442,748 · App. 13/367,448 · Granted Sep 13, 2016

Multi-RPO data protection

Inventors: Chen Burshan (Tel Aviv, IL); Omri Shefi (Qiryat Ono, IL); Yair Kuszpet (Netanya, IL)
Assignee: ZERTO, LTD.
G06F9/45533G06F11/2066G06F11/2082G06F11/2097G06F11/1471G06F11/1484G06F11/2038G06F11/2048G06F11/2069G06F11/2071G06F2009/45579G06F2201/815G06F2201/855
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,442,748
App. No.
13/367,448
Granted
Sep 13, 2016
Kind
B2
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 (34)

1. A system for disaster recovery, comprising:

a controller for a server having at least one processor, the controller having a virtual manager configured to cause the at least one processor to manage at least one hypervisor and to cause the at least one processor to:

(i) control bandwidth usage of a disaster recovery system in accordance with a plurality of recovery point objectives (RPOs), each of the plurality of RPOs designating a maximal time loss constraint for data recovery for an enterprise production system, wherein the enterprise production system includes a hypervisor system comprising multiple virtual protection groups, and a corresponding bandwidth allocation for the disaster recovery system to use in replicating data for the enterprise production system, wherein each of the plurality of RPOs are applied in accordance with a calendar-based schedule of dates and times, wherein multiple calendar-based schedules are used to schedule each of the RPOs and bandwidth allocations to control issuance of RPO alerts and the bandwidth usage for data replication for a corresponding virtual protection group of the enterprise production system, and

(ii) issue an RPO alert when the maximal time loss constraint for a current date and time for one of the plurality of RPOs is not satisfied when the maximal time loss constraint exceeds a bandwidth constraint.

2. The system of claim 1 wherein bandwidth is shared between the disaster recovery system and the enterprise production system, and wherein the bandwidth allocation for each RPO is an allocation of the shared bandwidth.

3. The system of claim 2 , wherein the calendar-based schedule allocates more bandwidth to the disaster recovery system during off-peak production times for the enterprise production system, and allocates less bandwidth to the disaster recovery system during peak production times for the enterprise production system.

4. The system of claim 1 wherein said controller adjusts the calendar-based schedule in response to having issued multiple RPO alerts.

5. A method for disaster recovery, comprising:

accessing a calendar-based schedule of a plurality of recovery point objectives (RPOs) and corresponding bandwidth allocations for a disaster recovery system, each RPO of the plurality of RPOs designating a maximal time loss constraint for data recovery for an enterprise production system, wherein the enterprise production system includes a hypervisor system comprising multiple virtual protection groups, and each bandwidth allocation constraining bandwidth usage for replicating data for the enterprise production system, wherein multiple calendar-based schedules are used to schedule each of the RPOs and bandwidth allocations to control issuance of RPO alerts and the bandwidth usage for data replication for a corresponding virtual protection group of the enterprise production system;

retrieving, by the disaster recovery system at any given date and time, the recovery point objective (RPO) and the corresponding bandwidth allocation for the given date and time, from the calendar-based schedule;

limiting, by the disaster recovery system at the given date and time, bandwidth usage of the disaster recovery system in accordance with the retrieved bandwidth allocation;

determining, by the disaster recovery system, a current RPO; and

issuing, by the disaster recovery system, an RPO alert based on the current RPO exceeding the retrieved RPO.

6. The method of claim 5 wherein bandwidth is shared between the disaster recovery system and the enterprise production system, and wherein the bandwidth allocation for each RPO is an allocation of the shared bandwidth.

7. The method of claim 6 , wherein the calendar-based schedule allocates more bandwidth to the disaster recovery system during off-peak production times for the enterprise production system, and allocates less bandwidth to the disaster recovery system during peak production times for the enterprise production system.

8. The method of claim 5 further comprising adjusting the calendar-based schedule in response to multiple occurrences of said issuing an RPO alert.

9. The system of claim 1 , wherein the controller reduces a data replication rate for the enterprise production system during off-peak production times.

10. The system of claim 1 , wherein the controller increases a data replication rate for the enterprise production system during peak production times.

11. The system of claim 1 , wherein the controller reduces an RPO objective for the enterprise production system during off-peak production times.

12. The system of claim 1 , wherein the controller increases an RPO objective for the enterprise production system during peak production times.

13. The system of claim 1 , wherein the controller establishes at least four timeframes for a weekly calendar schedule, wherein each of the at least four timeframes has a unique RPO objective and bandwidth limit.

14. The system of claim 2 , wherein the controller reduces an RPO objective for the enterprise production system during peak production times and increases an RPO objective for the enterprise production system during off-peak production times to enable the enterprise production system to share bandwidth with the disaster recovery system.

15. The method of claim 5 , comprising:

reducing a data replication rate for the enterprise production system during off-peak production times.

16. The method of claim 5 , comprising:

increasing a data replication rate for the enterprise production system during peak production times.

17. The method of claim 5 , comprising:

reducing an RPO objective for the enterprise production system during off-peak production times.

18. The method of claim 5 , comprising:

increasing an RPO objective for the enterprise production system during peak production times.

19. The method of claim 5 , comprising:

establishing at least four timeframes for a weekly calendar schedule, wherein each of the at least four timeframes has a unique RPO objective and bandwidth limit.

20. The method of 6 , comprising:

reducing an RPO objective for the enterprise production system during peak production times and increasing an RPO objective for the enterprise production system during off-peak production times to enable the enterprise production system to share bandwidth with the disaster recovery system.

Assignments (4)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 10, 2024
From: ZERTO LTD.
To: HEWLETT PACKARD ENTERPRISE DEVELOPMENT LP
Reel/Frame 066269/0960 →
SECURITY INTEREST Recorded Nov 19, 2019
From: ZERTO LTD.
To: KREOS CAPITAL VI (EXPERT FUND) L.P.
Reel/Frame 051044/0213 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded Nov 13, 2019
From: ZERTO LTD
To: SILICON VALLEY BANK
Reel/Frame 050998/0757 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 8, 2012
From: BURSHAN, CHEN; SHEFI, OMRI; KUSZPET, YAIR
To: ZERTO LTD.
Reel/Frame 027668/0263 →
Continuity (4)
Continuation In Part 13175898 · Jul 4, 2011
Continuation In Part 13039446 · Mar 3, 2011
Provisional Application 61314589 · Mar 17, 2010
Related Publication 20120137173A1 · May 31, 2012