IP Library Granted Patent US 10,768,987
Granted Patent B2
US 10,768,987 · App. 16/009,135 · Granted Sep 8, 2020

Data storage resource allocation list updating for data storage operations

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 10,768,987
App. No.
16/009,135
Granted
Sep 8, 2020
Kind
B2
Abstract

A system and method to perform data management operations in a data management system assigns the data management request to one or more available data management resources. If the data management request fails, at least one data management resource at least partially responsible for the failure is determined, as is a category associated with the one data management resource at least partially responsible for the failure. Other data management requests are identified in a list of data management requests that request data management resources having the same category and the list of data management requests is updated to indicate that the data management system should not perform the other identified data management requests.

Claims (42)

1. A non-transitory computer-readable medium storing instructions that, when executed by at least one computing device in a data management system, cause the computing device to perform operations comprising:

assigning a category code to data management requests that have similar data management resource requirements for performing data management operations in the data management system;

from a list of data management requests pending in the data management system,

attempting to perform a first data management request by assigning the first data management request to one or more data management resources in the data management system; and

if the first data management request fails,

determining at least one data management resource that is at least partially responsible for the failure of the first data management request,

identifying other data management requests having the category code of the failed first data management request, and

updating the list of data management requests to indicate that the data management system should not perform the identified other data management requests having the category code of the failed first data management request and wherein the updating of the list of data management requests comprises removing from the list the identified other data management requests having the category code of the failed first data management request.

2. The computer-readable medium of claim 1 , wherein the data management requests having the category code also have similar rules governing how to allocate the data management resources.

3. The computer-readable medium of claim 1 , wherein the associating of the category code with the data management requests that have similar data management resource requirements is also based on the data management requests having similar rules governing how to allocate the data management resources.

4. The computer-readable medium of claim 1 , wherein the category code corresponds to a storage policy.

5. The computer-readable medium of claim 1 , wherein the category code corresponds to a storage policy, which defines at least one of:

a storage location for a secondary copy generated in a data management operation,

preferences about how the data management system transfers data to the storage location in the data management operation, and

what processes are performed on the data before, during, or after the data transfer.

6. The computer-readable medium of claim 1 , wherein each data management request in the list of data management requests is associated with a category code.

7. The computer-readable medium of claim 1 , wherein the operations further comprise:

receiving the list of data management requests to be performed by the data management system.

8. The computer-readable medium of claim 1 , wherein the list of data management requests is updated to indicate that the data management system should not perform the identified other data management requests having the category code of the failed first data management request only when the first data management request failed because of a resource for which other similar resources are not available in the data management system.

9. The computer-readable medium of claim 1 , wherein the updating of the list of data management requests is not performed when the first data management request failed because of a resource for which other similar resources are available in the data management system.

10. The computer-readable medium of claim 1 , wherein the operations further comprise:

receiving a data management request for performing one or more data management operation, wherein the data management request indicates one or more data management resources to assign for performing the one or more data management operations.

11. A method performed in a data management system, the method comprising:

assigning, by a computing device operating in the data management system,

a category code to data management requests that have similar data management resource requirements for performing data management operations in the data management system,

wherein the computing comprises one or more processors and computer memory;

from a list of data management requests pending in the data management system,

assigning by the computing device a first data management request to one or more data management resources in the data management system; and

if the first data management request fails,

determining by the computing device at least one data management resource that is at least partially responsible for the failure of the first data management request,

identifying by the computing device other data management requests having the category code of the failed first data management request, and

indicating by the computing device that the data management system should not perform the identified other data management requests having the category code of the failed first data management request and removing from the list of data management requests, by the computing device, the identified other data management requests having the category code of the failed first data management request.

12. The method of claim 11 , wherein the indicating comprises updating by the computing device the list of data management requests.

13. The method of claim 11 , wherein the data management requests having the category code also have similar rules governing how to allocate the data management resources.

14. The method of claim 11 , wherein the category code corresponds to a storage policy.

15. The method of claim 11 , wherein the category code corresponds to a storage policy, which defines at least one of:

a storage location for a secondary copy generated in a data management operation,

preferences about how the data management system transfers data to the storage location in the data management operation, and

what processes are performed on the data before, during, or after the data transfer.

16. The method of claim 11 , wherein each data management request in the list of data management requests is associated with a category code.

17. The method of claim 11 , wherein the computing device indicates that the data management system should not perform the identified other data management requests having the category code of the failed first data management request only when the first data management request failed because of a resource for which other similar resources are not available in the data management system.

18. The method of claim 11 , wherein the computing device does not indicate that the data management system should not perform the identified other data management requests having the category code of the failed first data management request when the first data management request failed because of a resource for which other similar resources are available in the data management system.

Assignments (3)
SUPPLEMENTAL CONFIRMATORY GRANT OF SECURITY INTEREST IN UNITED STATES PATENTS Recorded Apr 16, 2025
From: COMMVAULT SYSTEMS, INC.
To: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 070864/0344 →
SECURITY INTEREST Recorded Dec 13, 2021
From: COMMVAULT SYSTEMS, INC.
To: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 058496/0836 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 18, 2018
From: GOKHALE, PARAG; KOTTOMTHARAYIL, RAJIV; KARANDIKAR, AMEY; WANG, YU
To: COMMVAULT SYSTEMS, INC.
Reel/Frame 046122/0345 →