System and method for automating formation and execution of a backup strategy
AssigneeAcronis International GmbH
InventorsStanislav Protasov, Serguei Beloussov, Dmitry Martynov, Sergey Ulasen
Life of this patent
Estimating the term…
Abstract
Disclosed herein are systems and method for forming and executing a backup strategy. In one aspect, an exemplary method comprises forming a respective backup strategy for each respective file of a plurality of files stored in a data source based on a frequency of occurrence, a desired recovery time, and a criticality of data loss for the respective file. The method further comprises executing the respective backup strategy for the respective file.
Claims19
A method for forming and executing a backup strategy comprising:
- forming a respective backup strategy for each respective file of a plurality of files stored in a data source, by:
- determining a frequency of occurrence for the respective file by comparing at least a portion of the respective file to a frequency database indicating commonality of various files;
- adding a secure backup strategy to the respective backup strategy for the respective file, when the frequency of occurrence is greater than a frequency of occurrence threshold;
- adding an instant copying to the respective backup strategy, when the respective file is determined as having a desired recovery time less than a predetermined recovery time threshold;
- copying the respective file to a cloud storage, when the instant copying is added to the backup strategy;
- adding a distributed backup to the respective backup strategy, when a criticality of data loss for the respective file is higher than a predetermined criticality threshold;
- and
- executing the respective backup strategy for the respective file.
A system for forming and executing a backup strategy, comprising:
- a hardware processor configured to:
- form a respective backup strategy for each respective file of a plurality of files stored in a data source, by:
- determining a frequency of occurrence for the respective file by comparing at least a portion of the respective file to a frequency database indicating commonality of various files;
- adding a secure backup strategy to the respective backup strategy for the respective file, when the frequency of occurrence is greater than a frequency of occurrence threshold;
- adding an instant copying to the respective backup strategy, when the respective file is determined as having a desired recovery time less than a predetermined recovery time threshold;
- copying the respective file to a cloud storage, when the instant copying is added to the backup strategy;
- adding a distributed backup to the respective backup strategy, when a criticality of data loss for the respective file is higher than a predetermined criticality threshold;
- and
- execute the respective backup strategy for the respective file.
A non-transitory computer readable medium storing thereon computer executable instructions for forming and executing backup strategies, including instructions for:
- forming a respective backup strategy for each respective file of a plurality of files stored in a data source, by:
- determining a frequency of occurrence for the respective file by comparing at least a portion of the respective file to a frequency database indicating commonality of various files;
- adding a secure backup strategy to the respective backup strategy for the respective file, when the frequency of occurrence is greater than a frequency of occurrence threshold;
- adding an instant copying to the respective backup strategy, when the respective file is determined as having a desired recovery time less than a predetermined recovery time threshold;
- copying the respective file to a cloud storage, when the instant copying is added to the backup strategy;
- adding a distributed backup to the respective backup strategy, when a criticality of data loss for the respective file is higher than a predetermined criticality threshold;
- and
- executing the respective backup strategy for the respective file.
Dependencies are inferred from the claim text.