IP Library Granted Patent US 10,255,137
Granted Patent B1
US 10,255,137 · App. 14/108,032 · Granted Apr 9, 2019

Point-in-time recovery on deduplicated storage

Inventors: Anestis Panidis (Saratoga, CA); Assaf Natanzon (Tel Aviv, IL); Saar Cohen (Moshav, IL)
Assignee: EMC IP Holding Company LLC
G06F11/1453G06F3/067G06F3/0619G06F3/0641
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 10,255,137
App. No.
14/108,032
Granted
Apr 9, 2019
Kind
B1
Abstract

Method and system for point-in-time recovery from a deduplicated data system is discussed. A request specifying a point-in-time may be received. A backup snapshot nearest that point-in-time may be identified, and a recovery snapshot may be synthesized.

Claims (60)

1. A method for point-in-time recovery on deduplicated storage, the method comprising:

receiving a request to recover data, the request specifying a point-in-time;

defining data protection windows wherein a first data protection window protects snapshots and journal entries and has a first defined protection time range, a second data protection window has a second defined protection time range, and a third data protection window has a third defined protection time range, wherein each defined protection time range represents a backup granularity designating how long a stored snapshot or journal entry is to be stored in each respective data protection window;

moving snapshots and journal entries from the first data protection window to the second data protection window, and moving snapshots from the second data protection to the third data protection window as time progresses;

defining respective policies to each data protection window to delete journal entries from the second data protection window after movement from the first data protection window so that only snapshots are stored in the second and third data protection windows, and to delete certain snapshots from the second data protection window so that only prioritized snapshots are stored in the third data protection window;

dynamically changing each of the first, second, and third data protection window time ranges based on available space in the deduplicated storage to optimize a retention time for protected snapshots and journal entries of the first data protection window if the available space is large or to optimize a retention time for the prioritized snapshots of the third data protection window if the available space is small;

identifying a backup snapshot nearest to the point-in-time, wherein the backup snapshot has a defined backup granularity defined by the respective data protection window storing the backup snapshot;

identifying a journal entry nearest to the point-in-time, wherein the journal entry is within a journal;

synthesizing a recovery snapshot from the backup snapshot and the journal entry;

providing the recovery snapshot in response to the request, wherein providing the recovery snapshot comprises exposing the recovery snapshot as a logical unit (“LU”);

mounting the LU on a host device;

receiving IOs for the LU from the host device;

applying the IOs to the recovery snapshot to create a modified recovery snapshot;

identifying a difference between the backup snapshot and the modified recovery snapshot, the difference comprising metadata journal entries associated with the IOs

adding the metadata journal entries to a recovery list; and

transmitting data associated with the metadata entries to a source storage system.

2. The method of claim 1 , wherein synthesizing the recovery snapshot comprises applying DO IOs when the backup snapshot was taken earlier than the point-in-time.

3. The method of claim 1 , wherein the point-in-time exists between existing snapshots, and wherein the first defined protection time range comprises a short-term protection window, the second defined protection time range comprises a mid-term protection window, and the third defined protection time range comprises a long-term protection window.

4. The method of claim 3 , wherein each data protection window of the one or more data protection windows has an associated policy specifying actions to take on any backup snapshot or journal entry in a respective data protection window, and wherein a first associated policy specifies that only certain periodic journal entries be deleted from the first data protection window and a second associated policy specifies that only certain periodic snapshots be retained in the third data protection window.

5. The method of claim 1 , further comprising transmitting the difference to a recovery device in response to the request.

6. The method of claim 1 , wherein providing the recovery snapshot comprises transmitting the recovery snapshot to a recovery device.

7. The method of claim 4 , wherein the backup snapshot nearest to the point-in-time is stored in a short-term protection window.

8. A computer program product for point-in-time recovery on deduplicated storage, the computer program product comprising a non-transitory computer readable medium encoded with computer executable program, the code enabling:

receiving a request to recover data, the request specifying a point-in-time;

defining data protection windows wherein a first data protection window protects snapshots and journal entries and has a first defined protection time range, a second data protection window has a second defined protection time range, and a third data protection window has a third defined protection time range, wherein each defined protection time range represents a backup granularity designating how long a stored snapshot or journal entry is to be stored in each respective data protection window;

moving snapshots and journal entries from the first data protection window to the second data protection window, and moving snapshots from the second data protection to the third data protection window as time progresses;

defining respective policies to each data protection window to delete journal entries from the second data protection window after movement from the first data protection window so that only snapshots are stored in the second and third data protection windows, and to delete certain snapshots from the second data protection window so that only prioritized snapshots are stored in the third data protection window;

dynamically changing each of the first, second, and third data protection window time ranges based on available space in the deduplicated storage to optimize a retention time for protected snapshots and journal entries of the first data protection window if the available space is large or to optimize a retention time for the prioritized snapshots of the third data protection window if the available space is small;

identifying a backup snapshot nearest to the point-in-time, wherein the backup snapshot has a defined backup granularity defined by the respective data protection window storing the backup snapshot;

identifying a journal entry nearest to the point-in-time, wherein the journal entry is within a journal;

synthesizing a recovery snapshot from the backup snapshot and the journal entry;

providing the recovery snapshot in response to the request, wherein providing the recovery snapshot comprises exposing the recovery snapshot as a logical unit (“LU”);

mounting the LU on a host device;

receiving IOs for the LU from the host device;

applying the IOs to the recovery snapshot to create a modified recovery snapshot;

identifying a difference between the backup snapshot and the modified recovery snapshot, the difference comprising metadata journal entries associated with the IOs

adding the metadata journal entries to a recovery list; and

transmitting data associated with the metadata entries to a source storage system.

9. The computer program product of claim 8 , wherein the point-in-time exists between existing snapshots, and wherein the first defined protection time range comprises a short-term protection window, the second defined protection time range comprises a mid-term protection window, and the third defined protection time range comprises a long-term protection window.

10. The computer program product of claim 9 , wherein each data protection window of the one or more data protection windows has an associated policy specifying actions to take on any backup snapshot or journal entry in a respective data protection window, and wherein a first associated policy specifies that only certain periodic journal entries be deleted from the first data protection window and a second associated policy specifies that only certain periodic snapshots be retained in the third data protection window.

11. The computer program product of claim 10 , wherein providing the recovery snapshot comprises exposing the recovery snapshot as a logical unit (“LU”), wherein the backup snapshot nearest to the point-in-time is stored in a short-term protection window, and wherein, as time progresses, snapshots and journal entries move from the short-term protection window to the long-term protection window through the medium term protection window, and wherein a policy of a final protection window is applied to a moved snapshot or journal entry.

12. A system for point-in-time recovery on deduplicated storage, the system comprising a computer processor configured to execute instructions comprising:

receiving a request to recover data, the request specifying a point-in-time;

defining data protection windows wherein a first data protection window protects snapshots and journal entries and has a first defined protection time range, a second data protection window has a second defined protection time range, and a third data protection window has a third defined protection time range, wherein each defined protection time range represents a backup granularity designating how long a stored snapshot or journal entry is to be stored in each respective data protection window;

moving snapshots and journal entries from the first data protection window to the second data protection window, and moving snapshots from the second data protection to the third data protection window as time progresses;

defining respective policies to each data protection window to delete journal entries from the second data protection window after movement from the first data protection window so that only snapshots are stored in the second and third data protection windows, and to delete certain snapshots from the second data protection window so that only prioritized snapshots are stored in the third data protection window;

dynamically changing each of the first, second, and third data protection window time ranges based on available space in the deduplicated storage to optimize a retention time for protected snapshots and journal entries of the first data protection window if the available space is large or to optimize a retention time for the prioritized snapshots of the third data protection window if the available space is small;

identifying a backup snapshot nearest to the point-in-time, wherein the backup snapshot has a defined backup granularity defined by the respective data protection window storing the backup snapshot;

identifying a journal entry nearest to the point-in-time, wherein the journal entry is within a journal;

synthesizing a recovery snapshot from the backup snapshot and the journal entry;

providing the recovery snapshot in response to the request, wherein providing the recovery snapshot comprises exposing the recovery snapshot as a logical unit (“LU”);

mounting the LU on a host device;

receiving IOs for the LU from the host device;

applying the IOs to the recovery snapshot to create a modified recovery snapshot;

identifying a difference between the backup snapshot and the modified recovery snapshot, the difference comprising metadata journal entries associated with the IOs

adding the metadata journal entries to a recovery list; and

transmitting data associated with the metadata entries to a source storage system.

13. The system of claim 12 , wherein the point-in-time exists between existing snapshots, and wherein the first defined protection time range comprises a short-term protection window, the second defined protection time range comprises a mid-term protection window, and the third defined protection time range comprises a long-term protection window.

14. The system of claim 13 , wherein each data protection window of the one or more data protection windows has an associated policy specifying actions to take on any backup snapshot or journal entry in a respective data protection window.

15. The system of claim 14 , wherein the backup snapshot nearest to the point-in-time is stored in a short-term protection window, and wherein, as time progresses, snapshots and journal entries move from the short-term protection window to the long-term protection window through the medium term protection window, and wherein a policy of a final protection window is applied to a moved snapshot or journal entry.

Assignments (12)
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (050724/0466) Recorded Jun 23, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL PRODUCTS L.P.; EMC CORPORATION; EMC IP HOLDING COMPANY LLC; DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO WYSE TECHNOLOGY L.L.C.)
Reel/Frame 060753/0486 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (053546/0001) Recorded Jun 23, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL MARKETING L.P. (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO CREDANT TECHNOLOGIES, INC.); DELL INTERNATIONAL L.L.C.; DELL PRODUCTS L.P.; DELL USA L.P.; EMC CORPORATION; DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO FORCE10 NETWORKS, INC. AND WYSE TECHNOLOGY L.L.C.); EMC IP HOLDING COMPANY LLC
Reel/Frame 071642/0001 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001) Recorded May 20, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO ASAP SOFTWARE EXPRESS, INC.); DELL MARKETING L.P. (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO CREDANT TECHNOLOGIES, INC.); DELL USA L.P.; DELL INTERNATIONAL L.L.C.; DELL PRODUCTS L.P.; DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO FORCE10 NETWORKS, INC. AND WYSE TECHNOLOGY L.L.C.); EMC CORPORATION (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO MAGINATICS LLC); EMC IP HOLDING COMPANY LLC (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO MOZY, INC.); SCALEIO LLC
Reel/Frame 061753/0001 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (040136/0001) Recorded Apr 26, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO ASAP SOFTWARE EXPRESS, INC.); DELL MARKETING L.P. (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO CREDANT TECHNOLOGIES, INC.); DELL USA L.P.; DELL INTERNATIONAL L.L.C.; DELL PRODUCTS L.P.; DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO FORCE10 NETWORKS, INC. AND WYSE TECHNOLOGY L.L.C.); EMC CORPORATION (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO MAGINATICS LLC); EMC IP HOLDING COMPANY LLC (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO MOZY, INC.); SCALEIO LLC
Reel/Frame 061324/0001 →
RELEASE OF SECURITY INTEREST Recorded Nov 3, 2021
From: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: ASAP SOFTWARE EXPRESS, INC.; AVENTAIL LLC; CREDANT TECHNOLOGIES, INC.; DELL USA L.P.; DELL INTERNATIONAL, L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL SOFTWARE INC.; DELL SYSTEMS CORPORATION; EMC CORPORATION; EMC IP HOLDING COMPANY LLC; FORCE10 NETWORKS, INC.; MAGINATICS LLC; MOZY, INC.; SCALEIO LLC; WYSE TECHNOLOGY L.L.C.
Reel/Frame 058216/0001 →
SECURITY AGREEMENT Recorded Apr 22, 2020
From: CREDANT TECHNOLOGIES INC.; DELL INTERNATIONAL L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL USA L.P.; EMC CORPORATION; FORCE10 NETWORKS, INC.; WYSE TECHNOLOGY L.L.C.; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
Reel/Frame 053546/0001 →
PATENT SECURITY AGREEMENT (NOTES) Recorded Oct 15, 2019
From: DELL PRODUCTS L.P.; EMC CORPORATION; EMC IP HOLDING COMPANY LLC; WYSE TECHNOLOGY L.L.C.
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT
Reel/Frame 050724/0466 →
SECURITY AGREEMENT Recorded Mar 21, 2019
From: CREDANT TECHNOLOGIES, INC.; DELL INTERNATIONAL L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL USA L.P.; EMC CORPORATION; FORCE10 NETWORKS, INC.; WYSE TECHNOLOGY L.L.C.; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
Reel/Frame 049452/0223 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 29, 2016
From: EMC CORPORATION
To: EMC IP HOLDING COMPANY LLC
Reel/Frame 040203/0001 →
SECURITY AGREEMENT Recorded Sep 21, 2016
From: ASAP SOFTWARE EXPRESS, INC.; AVENTAIL LLC; CREDANT TECHNOLOGIES, INC.; DELL USA L.P.; DELL INTERNATIONAL L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL SOFTWARE INC.; DELL SYSTEMS CORPORATION; EMC CORPORATION; EMC IP HOLDING COMPANY LLC; FORCE10 NETWORKS, INC.; MAGINATICS LLC; MOZY, INC.; SCALEIO LLC; SPANNING CLOUD APPS LLC; WYSE TECHNOLOGY L.L.C.
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
Reel/Frame 040136/0001 →
SECURITY AGREEMENT Recorded Sep 21, 2016
From: ASAP SOFTWARE EXPRESS, INC.; AVENTAIL LLC; CREDANT TECHNOLOGIES, INC.; DELL USA L.P.; DELL INTERNATIONAL L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL SOFTWARE INC.; DELL SYSTEMS CORPORATION; EMC CORPORATION; EMC IP HOLDING COMPANY LLC; FORCE10 NETWORKS, INC.; MAGINATICS LLC; MOZY, INC.; SCALEIO LLC; SPANNING CLOUD APPS LLC; WYSE TECHNOLOGY L.L.C.
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 040134/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 16, 2013
From: PANIDIS, ANESTIS; NATANZON, ASSAF; COHEN, SAAR
To: EMC CORPORATION
Reel/Frame 031792/0831 →
Cited By (1)
US 12,379,953