US2016232062A1PendingUtilityA1
Automation of data storage activities
Est. expiryMar 23, 2032(~5.7 yrs left)· nominal 20-yr term from priority
G06F 2201/84G06Q 10/10G06F 9/5072H04L 67/1097G06Q 10/06316H04L 47/70G06F 11/1464
57
PatentIndex Score
0
Cited by
0
References
0
Claims
Abstract
A system receives data storage workflow activities that include computer-executable instructions for carrying out data storage workflow in a network data storage system. Once the workflow is received, the system deploys the workflow to one or more workflow engines that can execute the various data storage activities related to the workflow. Prior to executing a data storage activity, the system can determine which workflow engine to use based on an allocation scheme.
Claims
exact text as granted — not AI-modified1 .- 20 . (canceled)
21 . A method for allocating execution of a data storage workflow suite within a networked data storage system comprising one or more client computing devices having one or more processors and one or more secondary storage devices, the method comprising:
causing a display to display a plurality of data storage display objects, wherein the plurality of data storage display objects are associated with a plurality of data storage activities; receiving relationship data associated with the plurality of data storage display objects, wherein the relationship data indicates an order in which the data storage activities are to be performed; with a first computing system comprising one or more processors, generating a data storage workflow suite based at least in part on the received relationship data, the data storage workflow suite comprising executable instructions for carrying out the plurality of data storage activities, the plurality of data storage activities including at least (i) a backup storage activity in which primary data forming at least a portion of one or more first files residing in primary storage are copied to and stored in secondary storage, and (ii) a restore storage activity in which secondary data residing in the secondary storage is restored to primary storage; deploying the data storage workflow suite to a workflow engine which executes on a second computing system comprising one or more processors; receiving an instruction to initiate the data storage workflow suite; and based at least in part on the instruction to initiate the data storage workflow suite, cause the workflow engine to execute the backup storage activity, wherein executing the backup storage activity comprises:
identifying primary data that does not reside in the secondary storage, wherein the primary data forms at least a portion of one or more first files residing on a primary data store associated with a first client computing device,
copying the primary data from the primary data store, and
storing the copied primary data in the secondary storage.
22 . The method of claim 21 , wherein the workflow engine is a first workflow engine, the method further comprising:
deploying the data storage workflow suite to a second workflow engine which executes on a third computing system comprising one or more processors, wherein said executing the backup storage activity using the first workflow engine is based at least in part on an allocation scheme.
23 . The method of claim 22 , wherein the allocation scheme is based at least in part on at least one of: computing resources associated with the first workflow engine and/or the second workflow engine, physical proximity of the first workflow engine and/or the second workflow engine to other data storage system components, or communication pathway speeds between the other data storage system components and the first workflow engine and/or the second workflow engine.
24 . The method of claim 22 , further comprising based at least in part on the instruction to initiate the data storage workflow suite, executing the restore storage activity using the second workflow engine based at least in part on the allocation scheme.
25 . The method of claim 22 , wherein the first workflow engine and the second workflow engine are selected based at least in part on one or more of computing resources associated with the first workflow engine and/or the second workflow engine and geographic proximity of one or more components in the networked data storage system to the first workflow engine and/or the second workflow engine are selected.
26 . The method of claim 22 , further comprising obtaining information related to activity levels associated with the first workflow engine and the second workflow engine, wherein the allocation scheme and said executing the backup storage activity using the first workflow engine are based at least in part on the obtained information related to activity levels associated with the first workflow engine and the second workflow engine.
27 . The method of claim 26 , wherein the obtained information related to activity levels associated with the first workflow engine and the second workflow engine comprises information related to at least one of: a total number of workflow suites deployed on the first workflow engine and the second workflow engine, a total number of processes active on the first workflow engine and the second workflow engine, or utilization of the first workflow engine and the second workflow engine.
28 . A networked data storage system, comprising:
one or more processors; a storage manager including a workflow manager module executing on the one or more processors and configured to:
cause a display to display a plurality of data storage display objects, wherein the plurality of data storage display objects are associated with a plurality of data storage activities;
receive relationship data associated with the plurality of data storage display objects, wherein the relationship data indicates an order in which the data storage activities are to be performed;
generate a data storage workflow suite based at least in part on the received relationship data, the data storage workflow suite comprising executable instructions for carrying out the plurality of data storage activities, the plurality of data storage activities including at least (i) a backup storage activity in which primary data forming at least a portion of one or more first files residing in primary storage are copied to and stored in secondary storage, and (ii) a restore storage activity in which secondary data residing in the secondary storage is restored to primary storage;
deploy the data storage workflow suite to a workflow engine which executes on a second computing system comprising one or more processors;
receive an instruction to initiate the data storage workflow suite; and
based at least in part on the instruction to initiate the data storage workflow suite, cause the workflow engine to execute the backup storage activity, wherein execution of the backup storage activity causes the workflow engine to:
identify primary data that does not reside in the secondary storage, wherein the primary data forms at least a portion of one or more first files residing on a primary data store associated with a first client computing device,
copy the primary data from the primary data store, and
store the copied primary data in the secondary storage.
29 . The networked data storage system of claim 28 , wherein
the workflow engine is a first workflow engine and the workflow manager module is further configured to deploy the data storage workflow suite to a second workflow engine which executes on a third computing system comprising one or more processors, and wherein the workflow manager module causes the first workflow engine to execute the backup storage activity based at least in part on an allocation scheme.
30 . The networked data storage system of claim 29 , wherein the allocation scheme is based at least in part on at least one of: computing resources associated with the first workflow engine and/or the second workflow engine, physical proximity of the first workflow engine and/or the second workflow engine to other data storage system components, or communication pathway speeds between the other data storage system components and the first workflow engine and/or the second workflow engine.
31 . The networked data storage system of claim 29 , wherein based at least in part on the instruction to initiate the data storage workflow suite, the workflow manager module causes the second workflow engine to execute the restore storage activity based at least in part on the allocation scheme.
32 . The networked data storage system of claim 29 , wherein the first workflow engine and the second workflow engine are selected by the workflow manager module from a pool of workflow engines, and wherein one or more other workflow engines from the pool of workflow engines are not selected.
33 . The networked data storage system of claim 29 , wherein the workflow manager module deploys the data storage workflow suite to the first workflow engine and the second workflow engine based at least in part on at least one of: one or more of computing resources associated with the first workflow engine and/or the second workflow engine, or geographic proximity of one or more components in the networked data storage system to the first workflow engine and/or the second workflow engine are selected.
34 . The networked data storage system of claim 29 , wherein the workflow manager module is further configured to obtain information related to activity levels associated with the first workflow engine and the second workflow engine, wherein the allocation scheme is based at least in part on the obtained information related to activity levels associated with the first workflow engine and the second workflow engine.
35 . The networked data storage system of claim 34 , wherein the obtained information related to activity levels associated with the first workflow engine and the second workflow engine comprises information related to at least one of a total number of workflow suites deployed on the first workflow engine and the second workflow engine, a total number of processes active on the first workflow engine and the second workflow engine, or utilization of the first workflow engine and the second workflow engine.
36 . A non-transitory, computer-readable storage medium comprising computer-executable instructions that when executed by one or more processors cause the one or more processors to:
cause a display to display a plurality of data storage display objects, wherein the plurality of data storage display objects are associated with a plurality of data storage activities; receive relationship data associated with the plurality of data storage display objects, wherein the relationship data indicates an order in which the data storage activities are to be performed; generate a data storage workflow suite based at least in part on the received relationship data, the data storage workflow suite comprising executable instructions for carrying out the plurality of data storage activities, the plurality of data storage activities including at least (i) a backup storage activity in which primary data forming at least a portion of one or more first files residing in primary storage are copied to and stored in secondary storage, and (ii) a restore storage activity in which secondary data residing in the secondary storage is restored to primary storage; deploy the data storage workflow suite to a workflow engine which executes on a second computing system comprising one or more processors; receive an instruction to initiate the data storage workflow suite; and based at least in part on the instruction to initiate the data storage workflow suite, cause the workflow engine to execute the backup storage activity, wherein execution of the backup storage activity causes the workflow engine to:
identify primary data that does not reside in the secondary storage, wherein the primary data forms at least a portion of one or more first files residing on a primary data store associated with a first client computing device,
copy the primary data from the primary data store, and
store the copied primary data in the secondary storage.
37 . The non-transitory, computer-readable storage medium of claim 36 , wherein
the workflow engine is a first workflow engine and the computer-executable instructions when executed by one or more processors further cause the one or more processors to deploy the data storage workflow suite to a second workflow engine which executes on a third computing system comprising one or more processors, and wherein the one or more processors cause the first workflow engine to execute the backup storage activity based at least in part on an allocation scheme.
38 . The non-transitory, computer-readable storage medium of claim 37 , wherein the allocation scheme is based at least in part on at least one of: computing resources associated with the first workflow engine and/or the second workflow engine, physical proximity of the first workflow engine and/or the second workflow engine to other data storage system components, or communication pathway speeds between the other data storage system components and the first workflow engine and/or the second workflow engine.
39 . The non-transitory, computer-readable storage medium of claim 37 , wherein based at least in part on the instruction to initiate the data storage workflow suite, the one or more processors cause the second workflow engine to execute the restore storage activity based at least in part on the allocation scheme.
40 . The non-transitory, computer-readable storage medium of claim 37 , wherein the one or more processors deploy the data storage workflow suite to the first workflow engine and the second workflow engine based at least in part on at least one of: one or more of computing resources associated with the first workflow engine and/or the second workflow engine, or geographic proximity of one or more components of a networked data storage system to the first workflow engine and/or the second workflow engine are selected.Join the waitlist — get patent alerts
Track US2016232062A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.