IP Library Granted Patent US 10,296,423
Granted Patent B2
US 10,296,423 · App. 15/086,356 · Granted May 21, 2019

System and method for live virtual incremental restoring of data from cloud storage

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,296,423
App. No.
15/086,356
Granted
May 21, 2019
Kind
B2
Abstract

A system and method is disclosed for live virtual incremental restoring of data from a cloud storage. An example method includes, in response to detecting a data backup, collecting information by a hardware processor of a computing device for configuring a list of changed sectors (LCS) of a storage medium of the computing device as a result of the data backup. The method further includes virtually restoring at least a portion of electronic data saved in the storage medium of the computing device from the cloud storage, the selected electronic data being previously saved in the cloud storage. The method also includes rebooting the computing device and applying changes to the storage medium of the computing device based on the LCS during a subsequent data backup.

Claims (79)

1. A method for live virtual incremental restoring of data from a cloud storage, the method comprising:

in response to detecting a data backup, collecting information by a hardware processor of a computing device for configuring a list of changed sectors (LCS) of a storage medium of the computing device as a result of the data backup;

virtually restoring at least a portion of electronic data saved in the storage medium of the computing device from the cloud storage, the selected electronic data being previously saved in the cloud storage; and

rebooting the computing device and applying changes to the storage medium of the computing device based on the LCS during a subsequent data backup.

2. The method of claim 1 , further comprising creating a virtual volume set (VVS) by a dedicated boot loader of the computing device in response to the data backup, the VVS being configured to:

detect one or more write requests to the storage medium of the computing device occurred during two consecutive data backups;

store the one or more write requests in a dedicated storage associated with the VVS;

in response to determining that a requested sector corresponding to at least one read request is located in the dedicated storage, obtain information relating to data changes from the dedicated storage;

in response to determining that the requested sector is located in the LCS, obtain information relating to data changes from the cloud storage; and

in response to determining that the requested sector is not located in the LCS, obtain information relating to data changes from an original volume of the requested sector.

3. The method of claim 2 , wherein the dedicated boot loader of the computing device is further configured to:

reboot the computing device by deactivating a default boot loader of the computing device;

establish a connection to the cloud storage;

set hooks to intercept input/output (I/O) requests into the dedicated boot loader and the default boot loader on the VVS; and

activate the default boot loader.

4. The method of claim 3 , further comprising:

running an operating system (OS) of the computing device based on information stored on the VVS for checking applications and data associated with the computing device; and

in response to a command not to restore data, rebooting the computing device using the OS of the computing device.

5. The method of claim 3 , further comprising:

running an operating system (OS) of the computing device based on information stored on the VVS for checking applications and data associated with the computing device; and

in response to a command to restore data, checking one or more restored sectors that are detected based on an indicia;

redirecting the one or more write requests to the storage medium of the computing device and marking corresponding sectors of the storage medium as restored; and

copying sectors from the dedicated storage and the cloud storage and marking the sectors as restored.

6. The method of claim 5 , further comprising: in response to detecting all sectors being marked as restored, disabling the dedicated boot loader and unloading the hooks.

7. The method of claim 6 , further comprising restoring a plurality of sectors of the computing device based on a priority determined based at least upon a usage frequency of each sector.

8. The method of claim 2 , further comprising:

in response to detecting that an activated working mode of the computing device disables the dedicated storage, directing all data requests to the storage medium of the computing device to the dedicated storage before rebooting the computing device, and disabling the dedicated storage by the dedicated boot loader.

9. A system for live virtual incremental restoring of data from a cloud storage, the system comprising:

an electronic memory; and

a hardware processor couple to the electronic memory and configured to:

in response to detecting a data backup, collect information for configuring a list of changed sectors (LCS) of the electronic memory of the computing device as a result of the data backup;

virtually restore at least a portion of electronic data saved in the electronic memory of the computing device from the cloud storage, the selected electronic data being previously saved in the cloud storage; and

reboot the computing device and apply changes to the electronic memory of the computing device based on the LCS during a subsequent data backup.

10. The system of claim 9 , wherein the processor is further configured to create a virtual volume set (VVS) by a dedicated boot loader of the computing device in response to the data backup to:

detect one or more write requests to the electronic memory of the computing device occurred during two consecutive data backups;

store the one or more write requests in a dedicated storage associated with the VVS;

in response to determining that a requested sector corresponding to at least one read request is located in the dedicated storage, obtain information relating to data changes from the dedicated storage;

in response to determining that the requested sector is located in the LCS, obtain information relating to data changes from the cloud storage; and

in response to determining that the requested sector is not located in the LCS, obtain information relating to data changes from an original volume of the requested sector.

11. The system of claim 10 , wherein the dedicated boot loader of the computing device is further configured to:

reboot the computing device by deactivating a default boot loader of the computing device;

establish a connection to the cloud storage;

set hooks to intercept input/output (I/O) requests into the dedicated boot loader and the default boot loader on the VVS; and

activate the default boot loader.

12. The system of claim 11 , wherein the processor is further configured to:

run an operating system (OS) of the computing device based on information stored on the VVS for checking applications and data associated with the computing device; and

in response to a command not to restore data, reboot the computing device using the OS of the computing device.

13. The system of claim 12 , wherein the processor is further configured to:

run an operating system (OS) of the computing device based on information stored on the VVS for checking applications and data associated with the computing device; and

in response to a command to restore data, check one or more restored sectors that are detected based on an indicia;

redirect the one or more write requests to the electronic memory of the computing device and mark corresponding sectors of the storage medium as restored; and

copy sectors from the dedicated storage and the cloud storage and mark the sectors as restored.

14. The system of claim 13 , wherein the processor is further configured to disable the dedicated loader and unload the hooks in response to detecting all sectors being marked as restored.

15. The system of claim 14 , wherein the processor is further configured to restore a plurality of sectors of the computing device based on a priority determined based at least upon a usage frequency of each sector.

16. A non-transitory computer readable medium storing computer executable instructions for live virtual incremental restoring of data from a cloud storage, the instructions being configured for:

in response to detecting a data backup, collecting information by a hardware processor of a computing device for configuring a list of changed sectors (LCS) of a storage medium of the computing device as a result of the data backup;

virtually restoring at least a portion of electronic data saved in the storage medium of the computing device from the cloud storage, the selected electronic data being previously saved in the cloud storage; and

rebooting the computing device and applying changes to the storage medium of the computing device based on the LCS during a subsequent data backup.

17. The non-transitory computer readable medium of claim 16 , further comprising instructions for creating a virtual volume set (VVS) by a dedicated boot loader of the computing device in response to the data backup to:

detect one or more write requests to the storage medium of the computing device occurred during two consecutive data backups;

store the one or more write requests in a dedicated storage associated with the VVS;

in response to determining that a requested sector corresponding to at least one read request is located in the dedicated storage, obtain information relating to data changes from the dedicated storage;

in response to determining that the requested sector is located in the LCS, obtain information relating to data changes from the cloud storage; and

in response to determining that the requested sector is not located in the LCS, obtain information relating to data changes from an original volume of the requested sector.

18. The non-transitory computer readable medium of claim 17 , wherein the dedicated boot loader of the computing device is further configured to:

reboot the computing device by deactivating a default boot loader of the computing device;

establish a connection to the cloud storage;

set hooks to intercept input/output (I/O) requests into the dedicated boot loader and the default boot loader on the VVS; and

activate the default boot loader.

19. The non-transitory computer readable medium of claim 18 , further comprising instructions for:

running an operating system (OS) of the computing device based on information stored on the VVS for checking applications and data associated with the computing device; and

in response to a command not to restore data, rebooting the computing device using the OS of the computing device;

in response to a command to restore data:

checking one or more restored sectors that are detected based on an indicia;

redirecting the one or more write requests to the storage medium of the computing device and marking corresponding sectors of the storage medium as restored; and

copying sectors from the dedicated storage and the cloud storage and marking the sectors as restored.

20. The non-transitory computer readable medium of claim 19 , further comprising instructions for:

in response to detecting all sectors being marked as restored, disabling the dedicated boot loader and unloading the hooks; and

restoring a plurality of sectors of the computing device based on a priority determined based at least upon a usage frequency of each sector.

Assignments (5)
REAFFIRMATION AGREEMENT Recorded Aug 28, 2022
From: ACRONIS AG; ACRONIS INTERNATIONAL GMBH; ACRONIS SCS, INC.; ACRONIS, INC.; GROUPLOGIC, INC.; NSCALED INC.; ACRONIS MANAGEMENT LLC; 5NINE SOFTWARE, INC.; ACRONIS GERMANY GMBH; ACRONIS NETHERLANDS B.V.; ACRONIS BULGARIA EOOD; DEVICELOCK, INC.; DEVLOCKCORP LTD; ACRONIS INC.
To: MIDCAP FINANCIAL TRUST
Reel/Frame 061330/0818 →
SECURITY INTEREST Recorded Dec 19, 2019
From: ACRONIS INTERNATIONAL GMBH
To: MIDCAP FINANCIAL TRUST
Reel/Frame 051418/0119 →
RELEASE OF SECURITY INTEREST Recorded Oct 21, 2019
From: OBSIDIAN AGENCY SERVICES, INC.
To: ACRONIS INTERNATIONAL GMBH; GROUPLOGIC, INC.
Reel/Frame 050783/0893 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 29, 2019
From: SHULGA, VICTOR; SEMYONOV, VASILY; BELOUSSOV, SERGUEI; PROTASOV, STANISLAV; SMULEVICH, MARK; REDKO, ANDREY
To: ACRONIS INTERNATIONAL GMBH
Reel/Frame 048741/0096 →
SECURITY INTEREST Recorded Jul 26, 2017
From: ACRONIS INTERNATIONAL GMBH; GROUPLOGIC, INC.
To: OBSIDIAN AGENCY SERVICES, INC., AS COLLATERAL AGENT
Reel/Frame 043350/0186 →