Dynamic triggering of block-level backups based on block change thresholds and corresponding file identities using indexing in a data storage management system
First Claim
Patent Images
1. A method for triggering block-level backups based on block change thresholds and corresponding file identities, the method comprising:
- receiving, by a first computing device, a threshold measure of changed data blocks, wherein the first computing device is configured to monitor changed data blocks against the threshold measure;
receiving, by the first computing device, a plurality of point-in-time representations of changed data blocks stored in one or more first data storage devices,wherein the changed data blocks result from write operations performed by an application that executes on a second computing device in communication with the one or more first data storage devices,wherein the plurality of point-in-time representations of changed data blocks are received from a first data agent that tracks data block changes generated by the application, andwherein the first data agent executes on the second computing device;
by the first computing device, receiving from a second data agent, file-to-data-block relationship information that identifies second data blocks that store contents of a first data file accessible to the application,wherein the second data agent tracks a file system comprising one or more data files accessible to the application including the first data file, andwherein the second data agent executes on the second computing device;
by the first computing device, indexing the file-to-data-block relationship information into a data-block-to-file mapping that identifies the first data file based on a given one of the second data blocks;
determining, by the first computing device, that the threshold measure has been passed relative to the first data file by a first set of changed data blocks on the one or more first data storage devices,by (i) analyzing the plurality of point-in-time representations of changed data blocks received from the first data agent and (ii) further by determining based on the data-block-to-file mapping that the first set of changed data blocks correspond to the first data file; and
based on determining that the threshold measure has been passed relative to the first data file,causing, by the first computing device, a block-level backup of the first set of changed data blocks to be performed at least in part by the first data agent, wherein a secondary copy that results from the block-level backup is associated with the first data file and not with other data files accessible to the application.
3 Assignments
0 Petitions
Accused Products
Abstract
A data storage management approach is disclosed that performs backup operations flexibly, based on a dynamic scheme of monitoring block changes occurring in production data. The illustrative system monitors block changes based on certain block-change thresholds and triggers block-level backups of the changed blocks when a threshold is passed. Block changes may be monitored in reference to particular files based on a reverse lookup mechanism. The illustrative system also collects and stores historical information on block changes, which may be used for reporting and predictive analysis.
-
Citations
20 Claims
-
1. A method for triggering block-level backups based on block change thresholds and corresponding file identities, the method comprising:
-
receiving, by a first computing device, a threshold measure of changed data blocks, wherein the first computing device is configured to monitor changed data blocks against the threshold measure; receiving, by the first computing device, a plurality of point-in-time representations of changed data blocks stored in one or more first data storage devices, wherein the changed data blocks result from write operations performed by an application that executes on a second computing device in communication with the one or more first data storage devices, wherein the plurality of point-in-time representations of changed data blocks are received from a first data agent that tracks data block changes generated by the application, and wherein the first data agent executes on the second computing device; by the first computing device, receiving from a second data agent, file-to-data-block relationship information that identifies second data blocks that store contents of a first data file accessible to the application, wherein the second data agent tracks a file system comprising one or more data files accessible to the application including the first data file, and wherein the second data agent executes on the second computing device; by the first computing device, indexing the file-to-data-block relationship information into a data-block-to-file mapping that identifies the first data file based on a given one of the second data blocks; determining, by the first computing device, that the threshold measure has been passed relative to the first data file by a first set of changed data blocks on the one or more first data storage devices, by (i) analyzing the plurality of point-in-time representations of changed data blocks received from the first data agent and (ii) further by determining based on the data-block-to-file mapping that the first set of changed data blocks correspond to the first data file; and based on determining that the threshold measure has been passed relative to the first data file, causing, by the first computing device, a block-level backup of the first set of changed data blocks to be performed at least in part by the first data agent, wherein a secondary copy that results from the block-level backup is associated with the first data file and not with other data files accessible to the application. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11)
-
-
12. A non-transitory computer-readable medium storing instructions that, when executed by a first computing device comprising one or more hardware processors, cause the first computing device to perform operations for triggering block-level backups based on block change thresholds and corresponding file identities, the operations comprising:
-
receiving a threshold measure of changed data blocks; monitoring changed data blocks against the threshold measure; receiving from a first data agent a plurality of point-in-time representations of changed data blocks stored in one or more first data storage devices, wherein the changed data blocks result from write operations performed by an application that executes on a second computing device in communication with the one or more first data storage devices, wherein the first data agent tracks data block changes generated by the application, and wherein the first data agent executes on the second computing device; receiving from a second data agent file-to-data-block relationship information that identifies second data blocks that store contents of a first data file accessible to the application, wherein the second data agent tracks a file system comprising one or more data files accessible to the application including the first data file, and wherein the second data agent executes on the second computing device; indexing the file-to-data-block relationship information into a data-block-to-file mapping that identifies the first data file based on a given one of the second data blocks; based on (i) the plurality of point-in-time representations of changed data blocks received from the first data agent, and (ii) the data-block-to-file mapping indicating that a first set of changed data blocks correspond to the first data file, determining that the threshold measure has been passed relative to the first data file by the first set of changed data blocks on the one or more first data storage devices; and based on determining that the threshold measure has been passed relative to the first data file, causing a block-level backup of the first set of changed data blocks to be performed at least in part by the first data agent, wherein a secondary copy that results from the block-level backup is associated with the first data file and not with other files accessible to the application. - View Dependent Claims (13, 14, 15, 16, 17, 18, 19, 20)
-
Specification