IP Library Granted Patent US 11,113,152
Granted Patent B1
US 11,113,152 · App. 15/626,202 · Granted Sep 7, 2021

Systems and methods for managing file backup

Inventors: Mohit Jha (Culver City, CA); Vinith Raj (Los Angeles, CA); Chengi Jimmy Kuo (Manhattan Beach, CA); Amitrajit Banerjee (Marina Del Rey, CA)
Assignee: NortonLifeLock Inc.
G06F11/1451G06F16/122G06F2201/84
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 11,113,152
App. No.
15/626,202
Granted
Sep 7, 2021
Kind
B1
Abstract

A computer-implemented method for managing file backup may include (i) detecting, by a computing device, an attempt to upload a file to a backup storage, (ii) calculating a degree of difference between the file and a previous version of the file on the backup storage, (iii) comparing, by the computing device, a list of applications that have written to the file with a list of acceptable applications for the file, (iv) calculating, based on the degree of difference and the comparison of the list of applications, a change score for the file, and (v) applying, based on the change score, a backup policy to the attempt to upload the file. Various other methods, systems, and computer-readable media are also disclosed.

Claims (85)

1. A computer-implemented method for managing file backup, at least a portion of the method being performed by a computing device comprising at least one processor, the method comprising:

detecting, by the computing device, an attempt to upload a file to a backup storage;

calculating a degree of difference indicating changes between the file and a previous version of the file on the backup storage;

comparing, by the computing device, a list of acceptable software applications for the file with a list of software applications that have made the changes to the file, wherein the computing device tracks each software application that writes to the file by adding previously undetected software applications to the list of software applications that have made the changes to the file;

calculating a change score for the file that indicates a likelihood of corruption in the file, wherein the change score is based on:

the degree of difference; and

the comparison of the list of software applications that have made the changes with the list of acceptable software applications; and

applying, based on the likelihood of corruption in the file indicated by the change score, a backup policy to the attempt to upload the file, wherein the backup policy sets a time-to-live period for the previous version of the file.

2. The method of claim 1 , wherein calculating the degree of difference comprises:

scanning the file;

scanning the previous version of the file; and

calculating the degree of difference based on the changes detected in the file.

3. The method of claim 1 , wherein the list of acceptable software applications comprises at least one of:

a software application known to write to a file type of the file;

a software application approved by a user; and

a software application approved by an administrator.

4. The method of claim 1 , wherein applying the backup policy comprises at least one of:

applying a strict backup policy based on the change score, as determined by administrator review in comparison to other change scores; and

applying a lenient backup policy based on the change score, as determined by the administrator review in comparison to the other change scores.

5. The method of claim 4 , wherein applying the strict backup policy comprises at least one of:

requesting confirmation of the attempt to upload the file from a user of the computing device;

adding a new software application from the list of software applications that have made the changes to the file to the list of acceptable software applications; and

setting a longer time-to-live period for the previous version of the file.

6. The method of claim 4 , wherein applying the lenient backup policy comprises at least one of:

automatically completing the attempt to upload the file to the backup storage; and

setting a shorter time-to-live period for the previous version of the file.

7. The method of claim 1 , further comprising at least one of:

monitoring software applications that write to the file; and

adjusting the list of software applications that have made the changes to the file based on detecting a new software application.

8. A system for managing file backup, the system comprising:

a detection module, stored in memory, that detects, by a computing device, an attempt to upload a file to a backup storage;

a calculation module, stored in memory, that calculates a degree of difference indicating changes between the file and a previous version of the file on the backup storage;

a comparison module, stored in memory, that compares, by the computing device, a list of acceptable software applications for the file with a list of software applications that have made the changes to the file, wherein the computing device tracks each software application that writes to the file by adding previously undetected software applications to the list of software applications that have made the changes to the file;

a change module, stored in memory, that calculates a change score for the file that indicates a likelihood of corruption in the file, wherein the change score is based on:

the degree of difference; and

the comparison of the list of software applications that have made the changes with the list of acceptable software applications;

a backup module, stored in memory, that applies, based on the likelihood of corruption in the file indicated by the change score, a backup policy to the attempt to upload the file, wherein the backup policy sets a time-to-live period for the previous version of the file; and

at least one processor that executes the detection module, the calculation module, the comparison module, the change module, and the backup module.

9. The system of claim 8 , wherein the calculation module calculates the degree of difference by:

scanning the file;

scanning the previous version of the file; and

calculating the degree of difference based on the changes detected in the file.

10. The system of claim 8 , wherein the list of acceptable software applications comprises at least one of:

a software application known to write to a file type of the file;

a software application approved by a user; and

a software application approved by an administrator.

11. The system of claim 8 , wherein the backup module applies the backup policy by at least one of:

applying a strict backup policy based on the change score, as determined by administrator review in comparison to other change scores; and

applying a lenient backup policy based on the change score, as determined by the administrator review in comparison to the other change scores.

12. The system of claim 11 , wherein applying the strict backup policy comprises at least one of:

requesting confirmation of the attempt to upload the file from a user of the computing device;

adding a new software application from the list of software applications that have made the changes to the file to the list of acceptable software applications; and

setting a longer time-to-live period for the previous version of the file.

13. The system of claim 11 , wherein applying the lenient backup policy comprises at least one of:

automatically completing the attempt to upload the file to the backup storage; and

setting a shorter time-to-live period for the previous version of the file.

14. The system of claim 8 , further comprising at least one of:

monitoring software applications that write to the file; and

adjusting the list of software applications that have made the changes to the file based on detecting a new software application.

15. A non-transitory computer-readable medium comprising one or more computer-executable instructions that, when executed by at least one processor of a computing device, cause the computing device to:

detect, by the computing device, an attempt to upload a file to a backup storage;

calculate a degree of difference indicating changes between the file and a previous version of the file on the backup storage;

compare, by the computing device, a list of acceptable software applications for the file with a list of software applications that have made the changes to the file, wherein the computing device tracks each software application that writes to the file by adding previously undetected software applications to the list of software applications that have made the changes to the file;

calculate a change score for the file that indicates a likelihood of corruption in the file, wherein the change score is based on:

the degree of difference; and

the comparison of the list of software applications that have made the changes with the list of acceptable software applications; and

apply, based on the likelihood of corruption in the file indicated by the change score, a backup policy to the attempt to upload the file, wherein the backup policy sets a time-to-live period for the previous version of the file.

16. The non-transitory computer-readable medium of claim 15 , wherein the computer-executable instructions cause the computing device to calculate the degree of difference by:

scanning the file;

scanning the previous version of the file; and

calculating the degree of difference based on the changes detected in the file.

17. The non-transitory computer-readable medium of claim 15 , wherein the list of acceptable software applications comprises at least one of:

a software application known to write to a file type of the file;

a software application approved by a user; and

a software application approved by an administrator.

18. The non-transitory computer-readable medium of claim 15 , wherein the computer-executable instructions cause the computing device to apply the backup policy by at least one of:

applying a strict backup policy based on the change score, as determined by administrator review in comparison to other change scores; and

applying a lenient backup policy based on the change score, as determined by the administrator review in comparison to the other change scores.

19. The non-transitory computer-readable medium of claim 18 , wherein applying the strict backup policy comprises at least one of:

requesting confirmation of the attempt to upload the file from a user of the computing device;

adding a new software application from the list of software applications that have made the changes to the file to the list of acceptable software applications; and

setting a longer time-to-live period for the previous version of the file.

20. The non-transitory computer-readable medium of claim 18 , wherein applying the lenient backup policy comprises at least one of:

automatically completing the attempt to upload the file to the backup storage; and

setting a shorter time-to-live period for the previous version of the file.

Assignments (6)
CHANGE OF NAME Recorded Feb 6, 2023
From: NORTONLIFELOCK INC.
To: GEN DIGITAL INC.
Reel/Frame 062714/0605 →
NOTICE OF SUCCESSION OF AGENCY (REEL 050926 / FRAME 0560) Recorded Sep 13, 2022
From: JPMORGAN CHASE BANK, N.A.
To: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
Reel/Frame 061422/0371 →
SECURITY AGREEMENT Recorded Sep 13, 2022
From: NORTONLIFELOCK INC.
To: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
Reel/Frame 062220/0001 →
CHANGE OF NAME Recorded Feb 14, 2020
From: SYMANTEC CORPORATION
To: NORTONLIFELOCK INC.
Reel/Frame 051935/0228 →
SECURITY AGREEMENT Recorded Nov 4, 2019
From: SYMANTEC CORPORATION; BLUE COAT LLC; LIFELOCK, INC,; SYMANTEC OPERATING CORPORATION
To: JPMORGAN, N.A.
Reel/Frame 050926/0560 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 19, 2017
From: JHA, MOHIT; RAJ, VINITH; KUO, CHENGI JIMMY; BANERJEE, AMITRAJIT
To: SYMANTEC CORPORATION
Reel/Frame 042741/0693 →
Cited By (1)
US 12,505,217