US2021279217A1PendingUtilityA1

Predicting scale of data migration

Assignee: COMMVAULT SYSTEMS INCPriority: May 20, 2015Filed: Mar 9, 2021Published: Sep 9, 2021
Est. expiryMay 20, 2035(~8.8 yrs left)· nominal 20-yr term from priority
G06F 16/134G06F 16/2264G06F 16/283G06F 16/182G06F 16/2452G06F 16/2455G06F 16/22G06F 16/24575G06F 16/219G06F 3/0482G06F 16/248G06F 16/252G06F 16/2423G06F 16/214
73
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

This application discloses a system for presenting data to a user based on requests to move data from primary storage to secondary storage. The system receives a request to move data that satisfies at least one criterion, from primary to secondary data storage. The system then identifies an initial database query from the request, and further builds a nested database query from the initial database query according to a database schema. Next, the system estimates a size of a result of executing the nested database query. Finally, the system provides for display to the user the estimated size.

Claims

exact text as granted — not AI-modified
What is claimed is: 
     
         1 . A computer-implemented method of predicting an amount of data storage needed when moving data from primary data storage to secondary or archive data storage, the method comprising:
 receiving a request to move data from a primary data storage system to a secondary data storage system;   translating the request to a nested database query based on a database schema, wherein translating the request comprises referencing the database schema to determine which tables are to be queried to satisfy the request to move data;   predicting a size of data that will be returned as a result of executing the nested database query; and,   providing the predicted size before moving the data from the primary data storage system to the secondary data storage system.   
     
     
         2 . The computer-implemented method of  claim 1 , wherein the request received is chosen by a user from a list of predetermined requests. 
     
     
         3 . The computer-implemented method of  claim 1 , wherein the translating includes traversing the database schema according to foreign keys. 
     
     
         4 . The computer-implemented method of  claim 1 , further comprising determining whether the secondary storage system has sufficient data storage space based on the predicted size. 
     
     
         5 . The computer-implemented method of  claim 1 , wherein the predicting includes computing a count of records that match the nested database query, and wherein the predicting includes computing an aggregate size from sizes of the records that match the nested database query. 
     
     
         6 . The computer-implemented method of  claim 1 , wherein the predicting includes computing a count of records in a database table referenced in the nested database query and a size of a record in the database table. 
     
     
         7 . The computer-implemented method of  claim 1 , further comprising determining whether to satisfy the request based on the predicted size, and wherein the determining is based on a computing load of the primary data storage system, a computing load of the secondary data storage system, an amount of free space on the primary data storage system, an amount of free space on the secondary data storage system, or a user need of data affected by the request. 
     
     
         8 . A system for predicting an amount of data storage needed when moving data from primary data storage to secondary or archive data storage, the system comprising:
 one or more non-transitory, computer-readable mediums having computer-executable instructions stored thereon; and,   one or more processors that, having executed the computer-executable instructions, configure the system to perform a plurality of operations comprising:
 receiving a request to move data from a primary data storage system to a secondary data storage system; 
 translating the request to a nested database query based on a database schema, wherein translating the request comprises referencing the database schema to determine which tables are to be queried to satisfy the request to move data; 
 predicting a size of data that will be returned as a result of executing the nested database query; and, 
 providing the predicted size before moving the data from the primary data storage system to the secondary data storage system. 
   
     
     
         9 . The system of  claim 8 , wherein the request received is chosen by a user from a list of predetermined requests. 
     
     
         10 . The system of  claim 8 , wherein the translating includes traversing the database schema according to foreign keys. 
     
     
         11 . The system of  claim 8 , wherein the plurality of operations further comprises determining whether the secondary storage system has sufficient data storage space based on the predicted size. 
     
     
         12 . The system of  claim 8 , wherein the predicting includes computing a count of records that match the nested database query, and wherein the predicting includes computing an aggregate size from sizes of the records that match the nested database query. 
     
     
         13 . The system of  claim 8 , wherein the predicting includes computing a count of records in a database table referenced in the nested database query and a size of a record in the database table. 
     
     
         14 . The system of  claim 8 , wherein the plurality of operations further comprises determining whether to satisfy the request based on the predicted size, and wherein the determining is based on a computing load of the primary data storage system, a computing load of the secondary data storage system, an amount of free space on the primary data storage system, an amount of free space on the secondary data storage system, or a user need of data affected by the request. 
     
     
         15 . A non-transitory, computer-readable medium having computer-executable instructions stored thereon that, when executed by one or more processors, causes a system to perform a method for predicting an amount of data storage needed when moving data from primary data storage to secondary or archive data storage, the method comprising:
 receiving a request to move data from a primary data storage system to a secondary data storage system;   translating the request to a nested database query based on a database schema, wherein translating the request comprises referencing the database schema to determine which tables are to be queried to satisfy the request to move data;   predicting a size of data that will be returned as a result of executing the nested database query; and,   providing the predicted size before moving the data from the primary data storage system to the secondary data storage system.   
     
     
         16 . The non-transitory, computer-readable medium of  claim 15 , wherein the request received is chosen by a user from a list of predetermined requests. 
     
     
         17 . The non-transitory, computer-readable medium of  claim 15 , wherein the translating includes traversing the database schema according to foreign keys. 
     
     
         18 . The non-transitory, computer-readable medium of  claim 15 , wherein the method further comprises determining whether the secondary storage system has sufficient data storage space based on the predicted size. 
     
     
         19 . The non-transitory, computer-readable medium of  claim 15 , wherein the predicting includes computing a count of records that match the nested database query, and wherein the predicting includes computing an aggregate size from sizes of the records that match the nested database query. 
     
     
         20 . The non-transitory, computer-readable medium of  claim 15 , wherein the predicting includes computing a count of records in a database table referenced in the nested database query and a size of a record in the database table.

Join the waitlist — get patent alerts

Track US2021279217A1 — get alerts on status changes and closely related new filings.

We store only your email — no account needed. See our privacy policy.